| Artifact: Build |
 |
 |
|
| Deliver incremental value to the user and customer, and provide a testable artifact for verification. |
| Fulfilled Slots | ||
|---|---|---|
| Roles | Responsible: | Modified By: |
| Tasks | Input To:
| Output From: |
| Main Description | This working version of the system is the result of putting the implementation of the system through a build process (typically an automated build script) that creates an executable version of the system, or one that runs. This executable version of the system will typically have a number of supporting files that are also considered part of this composite artifact. |
|---|
In an iterative lifecycle, each build must evolve from the previous iteration's build, adding more functionality and improving quality. The purpose of early builds that minimize or eliminate a risk or verify architectural decisions is to achieve consistently stable builds in later iterations. |
| Impact of not having | Without this artifact, there is no operational version of the system. |
|---|---|
| Reasons for not needing | This artifact is not needed if the development of an application is not within the scope of the solution. |
| Representation Options | This work product is almost always a composite product made up of numerous parts required to make the executable system. Therefore, a build is more than just executable files; it also includes such things as configuration files, Help files, and data repositories that will be put together, resulting in the product that the users will run. The specifics of those parts will vary by technology in use. |
| Guidelines |
|---|
This program and the accompanying materials are made available under the |