| <?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.6/uma.ecore" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="_NqSB0KeqEdmKDbQuyzCoqQ" name="build,_0YuXEMlgEdmt3adZL5Dmdw" guid="_NqSB0KeqEdmKDbQuyzCoqQ" changeDate="2011-04-01T14:55:14.512-0700" version="7.5.0"> |
| <mainDescription><p>
 |
| This working version of the system or part of the system&nbsp;is the result of putting the implementation through a
 |
| build process (typically an automated build script) that creates an executable version, or one that runs. This
 |
| executable version will typically have a number of supporting files that are also considered part of this artifact.
 |
| </p></mainDescription> |
| <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 almost always a 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> |
