Archived Content: This information is no longer maintained and is provided "as is" for your convenience.
Summary
IT4IT Reference Architecture Functional Component
Reference
Purpose
- Receive the Source data object from the Source Control functional component andmanage the creation, implementation, automation, and security and storage of all Builds.
- Create Build from the Source data object for a particular service component.
- Automate the Build process to support the Build schedule and build frequency requirements in order to support daily Build and smoke test plans or continuous integration plans.
- Run dynamic application security testing no later than when the final Build data object is received and before the RFCs are created for moving the new or changed service into production.
- Manage Builds and versioning in a Definitive Media Library (DML).
- Develop automated Build storage procedures and automated compilation techniques and tools.
- Monitor and report on the results of each integration Build.
- Initiate or automate the delivery of Builds to the Build Package functional component for validation by the acceptance testing team as candidate release builds.
Main Functions
The Build functional component:
- Shall be the system of record (authoritative source) for all Builds.
- Shall manage the version of each individual Build.
- Shall associate a Build to a service.
If a Source Control functional component exists, the Build functional component:
- Shall associate Source to one or many Builds.
If a Test functional component exists, the Build functional component:
- Shall associate one or many Builds to one or many Test Cases which are executed as part of the Build creation.
If a Build Package functional component exists, the Build functional component:
- Shall associate one or many Builds to a Build Package.
Example of HPE Products that may contribute to this Functional Component
- Application Lifecycle Intelligence
Generated: 1/11/2017 8:07:31 AM