| <?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.4/uma.ecore" |
| xmlns:epf="http://www.eclipse.org/epf" epf:version="1.2.0" xmlns:rmc="http://www.ibm.com/rmc" |
| rmc:version="7.2.0" xmi:id="_zHTQUKYSEdmvhNXG0Oc2uA" |
| name="vision,_0WVxcMlgEdmt3adZL5Dmdw" guid="_zHTQUKYSEdmvhNXG0Oc2uA" changeDate="2007-10-24T09:47:27.000-0700" |
| version="1.0.0"> |
| <keyConsiderations><p> |
| 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 features and avoiding details of requirements. |
| </p> |
| <p> |
| Projects with a focus on product development may extend the marketing section and include a more detailed product |
| position statement based on their needs and research. |
| </p></keyConsiderations> |
| <purpose><p> |
| This artifact provides a high-level basis for the more detailed technical requirements. It captures the essence of the |
| technical solution by describing high-level stakeholder requests and constraints that give an overview of the |
| reasoning, background and context for detailed requirements. It serves as input for communicating the fundamental "what |
| and why" for the project, and provides a strategy against which all future decisions should be validated. |
| </p> |
| <p> |
| The vision should rally team members behind an idea and give them the context for decision-making in the requirements |
| area. The vision must therefore be visible to everyone on the team.<br /> |
| </p></purpose> |
| <impactOfNotHaving>If this artifact is not used, there is a high risk that stakeholders and the development team will have different
 |
| expectations. This could lead to cancellation of the project. Misunderstandings and miscommunication about the strategy may
 |
| cause the project to move away from the original vision and create a discrepancy in stakeholder expectations.&nbsp;</impactOfNotHaving> |
| <reasonsForNotNeeding>This artifact is generally recommended for all but trivial projects.</reasonsForNotNeeding> |
| <representationOptions><p>
 |
| The vision is usually captured as a document.&nbsp;If key stakeholder needs are captured in a requirements management
 |
| tool, then this part of the document may be generated using reporting capabilities.
 |
| </p>
 |
| <p>
 |
| If the vision serves a set of projects or an entire program, the overall vision may be divided into several vision work
 |
| products. The vision of the program then brings the visions together by providing program-specific content and
 |
| referencing the subordinate visions.<br />
 |
| </p></representationOptions> |
| </org.eclipse.epf.uma:ArtifactDescription> |
