| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:ArtifactDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="_NqSB0KeqEdmKDbQuyzCoqQ" name="build,_0YuXEMlgEdmt3adZL5Dmdw" guid="_NqSB0KeqEdmKDbQuyzCoqQ" changeDate="2007-01-30T15:24:06.639-0500"> |
| <mainDescription><p> |
| 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.&nbsp; This |
| executable version of the system will typically have a number of supporting files that are also considered part of this |
| composite artifact. |
| </p></mainDescription> |
| <keyConsiderations><p> |
| In an iterative lifecycle, each build must evolve from the previous iteration's build, adding more functionality and |
| improving quality. |
| </p> |
| <p> |
| The purpose of early builds that minimize or eliminate a risk or verify architectural decisions is to achieve |
| consistently stable builds in later iterations. |
| </p></keyConsiderations> |
| <purpose>Deliver incremental value to the user and customer, and provide a testable artifact for verification.</purpose> |
| <reasonsForNotNeeding><p> |
| There will always need to be an&nbsp;operational version of the system. |
| </p></reasonsForNotNeeding> |
| <representationOptions><p> |
| This work product is&nbsp;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 additionally includes such things as configuration |
| files, help files, and data repositories that will be put together resulting in the product that will be run by the |
| users. The specifics of those parts will vary by technology in use. |
| </p></representationOptions> |
| </org.eclipse.epf.uma:ArtifactDescription> |