Files
wiki-hoist/docs/hub-documentation/delivery/approvals.md
T

2.8 KiB

sidebar_position, title
sidebar_position title
3 Approvals & Deliverables

Approvals & Deliverables

Approvals

This section is mandatory and must be completed in accordance with the established process for every specification, as it captures the initial approval. The Hoist Business Analyst is responsible for obtaining this sign-off. Any approvals for subsequent changes will be recorded in the Change Log section.

Functional Design Definition Approved

Approver Date Approved Artifact Change No.

Technical Design & Estimate Approved

The TSM is responsible for getting this sign-off.

Approver Date Approved Artifact Change No.

Deliverables

This section, owned by the developer, documents the final deliverables of the task. It must specify:

  • The components included in the delivery
  • The delivery format (e.g., Delivery Build, Application Configuration Package (ACP), or Manual Deployment with instructions)
  • For ACP deliveries: the name of the ACP
  • For deliveries uploaded to DevOps (IFS Cloud): the specific folder within the Build Home structure where the files are located

Delimitations & Dependencies

The configurations in this specification have been configured as documented. Requests for changes in the configuration necessary to fulfil (or prepare for future fulfilment of) any requirements not explicitly described in the business requirements specification will be considered outside the scope of this configuration.

The following are excluded from this specification:

  • Translations other than stated under the translations chapter
  • Changes or extensions on Online Help (F1 Help), e-learning material, or process models

Document what is NOT covered by this specification, including functionality that will not be implemented. If you refer to external documents, make sure to include them either in the Appendices or in the Foundation for Functional Specification section.


Go-Live Information / Upgrade Issues

Enter vital go-live information if appropriate, e.g.:

  • Basic data setup
  • Scheduled tasks
  • Permission Sets
  • Whether upgrade scripts are required or manual data updates in IFS Applications are needed when the configuration is installed

Delete this section if not applicable.


Performance Considerations

This section is owned by the developer. Provide guidance on data volumes for the main tables. Does not need to be precise but should give an order of magnitude.

Example: The volume of data within the new functions is unlikely to be high. Typically, there could be several hundred X records and up to 10,000 Y entries each. There are no expected issues with high volume processing or large tables to be considered in the design and coding.

Delete this section if not applicable.