| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:TaskDescription 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="_5rJ78Lj3Edmy88CC3LfB_w" |
| name="define_vision,_0fOAoMlgEdmt3adZL5Dmdw" guid="_5rJ78Lj3Edmy88CC3LfB_w" changeDate="2007-02-28T06:02:00.035-0800" |
| version="1.0.0"> |
| <sections xmi:id="_tvzDULwPEdm6DujQZORGLQ" name="Identify Stakeholders" guid="_tvzDULwPEdm6DujQZORGLQ"> |
| <sectionDescription><p>
 |
| Identify the decision-makers, customers, potential users, partners, domain experts, industry analysts and other
 |
| interested parties (see <a class="elementLinkWithType" href="./../../openup/roles/stakeholder_9FFD4106.html" guid="_dTa6gMAYEdqX-s4mWhkyqQ">Role: Stakeholder</a>). Develop profiles of potential (or actual) users of the system
 |
| that map to the roles of human actors of the system that you are developing. Document the initial information on key
 |
| users and their environment in the <a class="elementLink" href="./../../openup/workproducts/vision_2E71B03C.html" guid="_0WVxcMlgEdmt3adZL5Dmdw">Vision</a>.
 |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_sa5F4LwPEdm6DujQZORGLQ" name="Gain agreement on the problem to be solved" |
| guid="_sa5F4LwPEdm6DujQZORGLQ"> |
| <sectionDescription>Avoid rushing into defining the solution. First, gain agreement on the definition of the problem by asking the stakeholders
 |
| what they see as the problem. Then search for root causes, or the “problem behind the problem.”
 |
| Use&nbsp;techniques&nbsp;like the ones&nbsp;described in&nbsp;<a class="elementlinkwithtype" href="./../../openup/guidances/guidelines/req_gathering_techniques_8CB8E44C.html" guid="_OnoNQNSAEdmLhZ9H5Plxyw">Guideline: Requirements Gathering Techniques</a>. Formulate the problem statement, and then fill in the corresponding section from <a class="elementlinkwithtype" href="./../../openup/guidances/templates/vision_C2DEEF73.html" guid="_0cW54MlgEdmt3adZL5Dmdw">Template: Vision</a>. The purpose of this is to help you distinguish solutions and answers
 |
| from problems and questions.<br />
 |
| <br /></sectionDescription> |
| </sections> |
| <sections xmi:id="_rliOAOz2Edq2wJOsmRwmhg" name="Capture a common vocabulary" guid="_rliOAOz2Edq2wJOsmRwmhg"> |
| <sectionDescription>Every project has its own specialized terminology that everyone on the team must understand well to communicate effectively
 |
| with stakeholders. Work with stakeholders to&nbsp;create a glossary that defines acronyms, abbreviations, and&nbsp;relevant
 |
| business and technical terms. Work with stakeholder to continually expand and refine the&nbsp;glossary throughout the
 |
| project life cycle.</sectionDescription> |
| </sections> |
| <sections xmi:id="_vGg-oLwPEdm6DujQZORGLQ" name="Gather stakeholder requests" guid="_vGg-oLwPEdm6DujQZORGLQ"> |
| <sectionDescription><p>
 |
| Use the most appropriate method to gather information, such as the ones in <a class="elementLinkWithType"
 |
| href="./../../openup/guidances/guidelines/requirements_gathering_techniques_8CB8E44C.html"
 |
| guid="_OnoNQNSAEdmLhZ9H5Plxyw">Guideline: Requirements Gathering Techniques</a>. Each one is applicable in a particular
 |
| situation or to a certain type of stakeholder.
 |
| </p>
 |
| <p>
 |
| If you can meet stakeholders in person, then you can conduct an interview or a brainstorming session. This face-to-face
 |
| collaboration is extremely valuable and reduces the chances of the project team misunderstanding the needs of the
 |
| stakeholders.
 |
| </p>
 |
| <p>
 |
| Some requirements may already be documented in an existing Work Item List. This can often be used as a solid starting
 |
| position from which a full set of requirements can be created.
 |
| </p>
 |
| <p>
 |
| Any requirements gathered during this step should be captured in the <a class="elementLink"
 |
| href="./../../openup/workproducts/work_items_list_39D03CC8.html" guid="_rGNWsCbSEdqh1LYUOGRh2A">Work Items List</a>.
 |
| </p>
 |
| <p>
 |
| For more information, see <a class="elementLinkWithType"
 |
| href="./../../openup/tasks/find_and_outline_requirements_90D272B9.html" guid="_P9cMUPV_EdmdHa9MmVPgqQ">Task: Find and
 |
| Outline Requirements</a>.
 |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_z7ZC4LwPEdm6DujQZORGLQ" name="Define the system boundaries" guid="_z7ZC4LwPEdm6DujQZORGLQ"> |
| <sectionDescription><p>
 |
| Find and define the line that divides the solution and the real world that surrounds the solution. Identify interfaces,
 |
| as well as input and output information exchanged with users, machines, or systems.
 |
| </p>
 |
| <p>
 |
| Collaborate with the <a class="elementLink" href="./../../openup/roles/project_manager_E657F936.html" guid="_0a0o0MlgEdmt3adZL5Dmdw">Project Manager</a>&nbsp;and the <a class="elementLink" href="./../../openup/roles/architect_E7A12309.html" guid="_0X9iEMlgEdmt3adZL5Dmdw">Architect</a>&nbsp;since decisions
 |
| concerning system boundaries will have a major impact on cost, schedule and system architecture.
 |
| </p>
 |
| <p>
 |
| A&nbsp;<a class="elementLink" href="./../../openup/workproducts/uc_model_85965D1B.html" guid="_W2SgEDR5EdutE_HNDTJk5Q">Use-Case Model</a> is one technique that can prove useful in defining the system
 |
| boundaries. For more information, see <a class="elementLinkWithType" href="./../../openup/tasks/find_and_outline_requirements_90D272B9.html" guid="_P9cMUPV_EdmdHa9MmVPgqQ">Task: Find and Outline Requirements</a>.
 |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_1LVn0LwPEdm6DujQZORGLQ" name="Identify constraints on the system" |
| guid="_1LVn0LwPEdm6DujQZORGLQ"> |
| <sectionDescription><p>
 |
| Consider the various sources of constraints that can impact the design or the project itself:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Political
 |
| </li>
 |
| <li>
 |
| Economic (budget, licensing)
 |
| </li>
 |
| <li>
 |
| Environmental (regulatory constraints, legal, standards)
 |
| </li>
 |
| <li>
 |
| Technical (platforms, technology)
 |
| </li>
 |
| <li>
 |
| Feasibility (schedule, resources allocation, outsourcing)
 |
| </li>
 |
| <li>
 |
| System (solutions compatibility, support of operating systems and environments).
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| Collaborate with the <a class="elementLink" href="./../../openup/roles/project_manager_E657F936.html" guid="_0a0o0MlgEdmt3adZL5Dmdw">Project Manager</a>&nbsp;and the <a class="elementLink" href="./../../openup/roles/architect_E7A12309.html" guid="_0X9iEMlgEdmt3adZL5Dmdw">Architect</a>&nbsp;since decisions
 |
| concerning system&nbsp;constraints will have a major impact on cost, schedule and system architecture.
 |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_2VixILwPEdm6DujQZORGLQ" name="Define features of the system" |
| guid="_2VixILwPEdm6DujQZORGLQ"> |
| <sectionDescription><p>
 |
| 
 |
| Work with stakeholders to capture&nbsp;a list&nbsp;of&nbsp;<a class="elementlinkwithusertext" href="./../../openup/guidances/termdefinitions/feature_4ED64AEE.html" guid="_PgYREAeYEduWycDgioo5rg">features</a> that
 |
| 
 |
| stakeholders want in the system, briefly describing them and giving <a class="elementLinkWithUserText" href="./../../openup/guidances/concepts/requirement_attributes_4AC73153.html" guid="_VQ268O0KEdqHTdbLTmC5IQ">attributes</a> to help define their general status and priority in the project.
 |
| 
 |
| </p>
 |
| 
 |
| <p>
 |
| 
 |
| Update the <a class="elementLink" href="./../../openup/workproducts/vision_2E71B03C.html" guid="_0WVxcMlgEdmt3adZL5Dmdw">Vision</a>&nbsp;to capture the features identified&nbsp;and their attributes.
 |
| 
 |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_AhjmAL-GEdqb7N6KIeDL8Q" name="Achieve concurrence" guid="_AhjmAL-GEdqb7N6KIeDL8Q"> |
| <sectionDescription>Conduct a review&nbsp;of the project vision with relevant Stakeholders and the development team to ensure agreement, assess
 |
| quality, and identify required changes. See&nbsp;<a class="elementLinkWithType"
 |
| href="./../../openup/guidances/guidelines/effective_requirements_reviews_5913D369.html"
 |
| guid="_E-dPIL-GEdqb7N6KIeDL8Q">Guideline: Effective Requirement Reviews</a> for more information.</sectionDescription> |
| </sections> |
| <purpose>The solution is proposed for a problem that everybody agrees on. Stakeholders collaborate with the development team to
 |
| 
 |
| 
 |
| express and document their problems, needs, and potential features for the system to be, so the project team can better
 |
| 
 |
| 
 |
| understand what has to be done.</purpose> |
| </org.eclipse.epf.uma:TaskDescription> |
