| <?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:epf="http://www.eclipse.org/epf" epf:version="1.5.0" xmi:id="_zHTQUKYSEdmvhNXG0Oc2uA" |
| name="vision,_0WVxcMlgEdmt3adZL5Dmdw" guid="_zHTQUKYSEdmvhNXG0Oc2uA" changeDate="2007-02-28T05:55:39.149-0800" |
| version="1.0.0"> |
| <mainDescription><p>
 |
| This artifact&nbsp;provides a complete vision for the software system under development and supports the contract
 |
| between the customer and the development organization. Every project needs a source for capturing all Stakeholders'
 |
| expectations.
 |
| </p>
 |
| <p>
 |
| This artifact&nbsp;is written from the customers' perspective, focusing on the essential features of the system and
 |
| acceptable levels of quality. The artifact should include a description of what <a class="elementLinkWithUserText" href="./../../openup/guidances/termdefinitions/feature_4ED64AEE.html" guid="_PgYREAeYEduWycDgioo5rg">features</a>&nbsp;will be included, as well as those considered but not included.
 |
| </p></mainDescription> |
| <purpose><p>
 |
| This artifact&nbsp;provides a high-level, sometimes contractual, basis for the more detailed technical requirements
 |
| that are visible to the Stakeholders. It captures the essence of the system by describing high-level requirements and
 |
| design constraints that give the reader an overview of the system from a behavioral requirements perspective. It serves
 |
| as input for the project-approval process, communicates the fundamental "what and why" for the project, and provides a
 |
| plan against which all future decisions should be validated.
 |
| </p></purpose> |
| <impactOfNotHaving>If this artifact is not used, there is a high risk that Stakeholders and the development 
 |
| team will have different expectations.&nbsp;This could lead to cancellation of 
 |
| the project.</impactOfNotHaving> |
| <representationOptions>Tailor this artifact as necessary for your project's needs. It is generally good 
 |
| practice to keep this artifact brief so you can release 
 |
| it to Stakeholders as soon as possible, and to make it easy for Stakeholders to 
 |
| read and understand. You can 
 |
| accomplish this by including only the most important Stakeholder requests 
 |
| and features and avoiding details of requirements. 
 |
| You can describe details in the other requirement 
 |
| artifacts.</representationOptions> |
| </org.eclipse.epf.uma:ArtifactDescription> |
