| <?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.5/uma.ecore" |
| xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.0" xmlns:epf="http://www.eclipse.org/epf" |
| epf:version="1.5.0" xmi:id="_NqSB0KeqEdmKDbQuyzCoqQ" |
| name="build,_0YuXEMlgEdmt3adZL5Dmdw" guid="_NqSB0KeqEdmKDbQuyzCoqQ" changeDate="2008-08-15T12:25:59.843-0700" |
| version="7.5.0"> |
| <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. 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> |
| <impactOfNotHaving><p> Without this artifact, there is no operational version of the system. </p></impactOfNotHaving> |
| <reasonsForNotNeeding><p>
 |
| This artifact is not needed if the development of an application is not within the scope of the solution.
 |
| </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 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. </p></representationOptions> |
| </org.eclipse.epf.uma:ArtifactDescription> |
