<?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.3/uma.ecore" rmc:version="7.1.0" epf:version="1.0.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>&lt;p&gt;
    Identify the decision-makers, customers, potential users, partners, domain experts, industry analysts and other
    interested parties (see &lt;a class=&quot;elementLinkWithType&quot;
    href=&quot;./../../openup_basic/roles/stakeholder,_dTa6gMAYEdqX-s4mWhkyqQ.html&quot; guid=&quot;_dTa6gMAYEdqX-s4mWhkyqQ&quot;&gt;Role:
    Stakeholder&lt;/a&gt;). 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 &lt;a
    class=&quot;elementLinkWithType&quot; href=&quot;./../../openup_basic/workproducts/vision,_0WVxcMlgEdmt3adZL5Dmdw.html&quot;
    guid=&quot;_0WVxcMlgEdmt3adZL5Dmdw&quot;&gt;Artifact: Vision&lt;/a&gt;.
&lt;/p&gt;</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&amp;nbsp;techniques&amp;nbsp;like the ones&amp;nbsp;described in&amp;nbsp;&lt;a class=&quot;elementlinkwithtype&quot;
href=&quot;./../../openup_basic/guidances/guidelines/req_gathering_techniques,_OnoNQNSAEdmLhZ9H5Plxyw.html&quot;
guid=&quot;_OnoNQNSAEdmLhZ9H5Plxyw&quot;&gt;Guideline: Requirements Gathering Techniques&lt;/a&gt;. Formulate the problem statement, and then
fill in the corresponding section from &lt;a class=&quot;elementlinkwithtype&quot;
href=&quot;./../../openup_basic/guidances/templates/vision,_0cW54MlgEdmt3adZL5Dmdw.html&quot;
guid=&quot;_0cW54MlgEdmt3adZL5Dmdw&quot;&gt;Template: Vision&lt;/a&gt;. The purpose of this is to help you distinguish solutions and answers
from problems and questions.&lt;br /&gt;
&lt;br /&gt;</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&amp;nbsp;create a glossary that defines acronyms, abbreviations, and&amp;nbsp;relevant
business and technical terms. Work with stakeholder to continually expand and refine the&amp;nbsp;glossary throughout the
project life cycle.</sectionDescription>
  </sections>
  <sections xmi:id="_vGg-oLwPEdm6DujQZORGLQ" name="Gather stakeholder requests" guid="_vGg-oLwPEdm6DujQZORGLQ">
    <sectionDescription>&lt;p&gt;
    Use the most appropriate method to gather information, such as the ones in &lt;a class=&quot;elementLinkWithType&quot;
    href=&quot;./../../openup_basic/guidances/guidelines/req_gathering_techniques,_OnoNQNSAEdmLhZ9H5Plxyw.html&quot;
    guid=&quot;_OnoNQNSAEdmLhZ9H5Plxyw&quot;&gt;Guideline: Requirements Gathering Techniques&lt;/a&gt;. Each one is applicable in a particular
    situation or to a certain type of stakeholder.
&lt;/p&gt;
&lt;p&gt;
    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.
&lt;/p&gt;
&lt;p&gt;
    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.
&lt;/p&gt;
&lt;p&gt;
    Any requirements gathered during this step should be captured in the Work Item List.
&lt;/p&gt;
&lt;p&gt;
    For more information, see &lt;a class=&quot;elementLinkWithType&quot;
    href=&quot;./../../openup_basic/tasks/find_and_outline_requirements,_P9cMUPV_EdmdHa9MmVPgqQ.html&quot;
    guid=&quot;_P9cMUPV_EdmdHa9MmVPgqQ&quot;&gt;Task: Find and Outline Requirements&lt;/a&gt;.
&lt;/p&gt;</sectionDescription>
  </sections>
  <sections xmi:id="_z7ZC4LwPEdm6DujQZORGLQ" name="Define the system boundaries" guid="_z7ZC4LwPEdm6DujQZORGLQ">
    <sectionDescription>&lt;p&gt;
    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.
&lt;/p&gt;
&lt;p&gt;
    A Use Case Model is one technique that can prove useful in defining the system boundaries.
&lt;/p&gt;
&lt;p&gt;
    For more information, see &lt;a class=&quot;elementLinkWithType&quot;
    href=&quot;./../../openup_basic/tasks/find_and_outline_requirements,_P9cMUPV_EdmdHa9MmVPgqQ.html&quot;
    guid=&quot;_P9cMUPV_EdmdHa9MmVPgqQ&quot;&gt;Task: Find and Outline Requirements&lt;/a&gt;.
&lt;/p&gt;</sectionDescription>
  </sections>
  <sections xmi:id="_1LVn0LwPEdm6DujQZORGLQ" name="Identify constraints on the system" guid="_1LVn0LwPEdm6DujQZORGLQ">
    <sectionDescription>&lt;p&gt;
    Consider the various sources of constraints that can impact the design or the project itself:
&lt;/p&gt;
&lt;ul&gt;
    &lt;li&gt;
        Political
    &lt;/li&gt;
    &lt;li&gt;
        Economic (budget, licensing)
    &lt;/li&gt;
    &lt;li&gt;
        Environmental (regulatory constraints, legal, standards)
    &lt;/li&gt;
    &lt;li&gt;
        Technical (platforms, technology)
    &lt;/li&gt;
    &lt;li&gt;
        Feasibility (schedule, resources allocation, outsourcing)
    &lt;/li&gt;
    &lt;li&gt;
        System (solutions compatibility, support of operating systems and environments).
    &lt;/li&gt;
&lt;/ul&gt;</sectionDescription>
  </sections>
  <sections xmi:id="_2VixILwPEdm6DujQZORGLQ" name="Define features of the system" guid="_2VixILwPEdm6DujQZORGLQ">
    <sectionDescription>&lt;p&gt;
    Work with stakeholders to capture&amp;nbsp;a list&amp;nbsp;of&amp;nbsp;&lt;a class=&quot;elementlinkwithusertext&quot;
    href=&quot;./../../openup_basic/guidances/termdefinitions/feature,_PgYREAeYEduWycDgioo5rg.html&quot;
    guid=&quot;_PgYREAeYEduWycDgioo5rg&quot;&gt;features&lt;/a&gt; that stakeholders want in the system, briefly describing them and giving &lt;a
    class=&quot;elementLinkWithUserText&quot;
    href=&quot;./../../openup_basic/guidances/concepts/requirement_attributes,_VQ268O0KEdqHTdbLTmC5IQ.html&quot;
    guid=&quot;_VQ268O0KEdqHTdbLTmC5IQ&quot;&gt;attributes&lt;/a&gt; to help define their general status and priority in the project.
&lt;/p&gt;
&lt;p&gt;
    Update the &lt;a class=&quot;elementLinkWithType&quot;
    href=&quot;./../../openup_basic/workproducts/work_items_list,_rGNWsCbSEdqh1LYUOGRh2A.html&quot;
    guid=&quot;_rGNWsCbSEdqh1LYUOGRh2A&quot;&gt;Artifact: Work Items List&lt;/a&gt;&amp;nbsp;to capture the features identified&amp;nbsp;and their
    attributes.
&lt;/p&gt;</sectionDescription>
  </sections>
  <sections xmi:id="_AhjmAL-GEdqb7N6KIeDL8Q" name="Achieve concurrence" guid="_AhjmAL-GEdqb7N6KIeDL8Q">
    <sectionDescription>Conduct a review&amp;nbsp;of the project vision with relevant Stakeholders and the development team to ensure agreement, assess
quality, and identify required changes. See&amp;nbsp;&lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../openup_basic/guidances/guidelines/effective_req_reviews,_E-dPIL-GEdqb7N6KIeDL8Q.html&quot; guid=&quot;_E-dPIL-GEdqb7N6KIeDL8Q&quot;&gt;Guideline: Effective Requirement Reviews&lt;/a&gt; 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>