OpenUP/OpenUP_baseline_EN/exported_HTML_1_0/openup/tasks/define_vision.html - epf/org.eclipse.epf.nl-libraries - Git at Google

 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE html PUBLIC "-//W3C/DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd">
 <!-- VERSION rmc:7.1.0 -->
 <html xmlns="http://www.w3.org/1999/xhtml">
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
 <!-- START NON-TRANSLATABLE -->
 <title>openup&amp;#92;tasks&amp;#92;&amp;#92;define_vision.xmi</title>
 </head>
 <!-- WARNING: do not modify the generated comments in this file below this line.  They are used as markers for the import process. -->
 <body>
 Element Name: define_vision.xmi<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: presentationName<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:presentationName,_0fOAoMlgEdmt3adZL5Dmdw CRC: 2887983663 -->Define Vision<!-- END:presentationName,_0fOAoMlgEdmt3adZL5Dmdw -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: briefDescription<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:briefDescription,_0fOAoMlgEdmt3adZL5Dmdw CRC: 2748033547 -->Define the vision for the future system. Describe the problem and features based on Stakeholder requests.<!-- END:briefDescription,_0fOAoMlgEdmt3adZL5Dmdw -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: purpose<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:purpose,_5rJ78Lj3Edmy88CC3LfB_w CRC: 1070376138 -->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.<!-- END:purpose,_5rJ78Lj3Edmy88CC3LfB_w -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: name<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:name,_tvzDULwPEdm6DujQZORGLQ CRC: 4020447428 -->Identify Stakeholders<!-- END:name,_tvzDULwPEdm6DujQZORGLQ -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: sectionDescription<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:sectionDescription,_tvzDULwPEdm6DujQZORGLQ CRC: 949225215 --><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><!-- END:sectionDescription,_tvzDULwPEdm6DujQZORGLQ -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: name<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:name,_sa5F4LwPEdm6DujQZORGLQ CRC: 3957171804 -->Gain agreement on the problem to be solved<!-- END:name,_sa5F4LwPEdm6DujQZORGLQ -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: sectionDescription<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:sectionDescription,_sa5F4LwPEdm6DujQZORGLQ CRC: 2045030396 -->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/requirements_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 /><!-- END:sectionDescription,_sa5F4LwPEdm6DujQZORGLQ -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: name<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:name,_rliOAOz2Edq2wJOsmRwmhg CRC: 2019227070 -->Capture a common vocabulary<!-- END:name,_rliOAOz2Edq2wJOsmRwmhg -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: sectionDescription<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:sectionDescription,_rliOAOz2Edq2wJOsmRwmhg CRC: 2505467041 -->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.<!-- END:sectionDescription,_rliOAOz2Edq2wJOsmRwmhg -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: name<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:name,_vGg-oLwPEdm6DujQZORGLQ CRC: 1906815529 -->Gather stakeholder requests<!-- END:name,_vGg-oLwPEdm6DujQZORGLQ -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: sectionDescription<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:sectionDescription,_vGg-oLwPEdm6DujQZORGLQ CRC: 460762192 --><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 Work Item List.
 </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><!-- END:sectionDescription,_vGg-oLwPEdm6DujQZORGLQ -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: name<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:name,_z7ZC4LwPEdm6DujQZORGLQ CRC: 3642748269 -->Define the system boundaries<!-- END:name,_z7ZC4LwPEdm6DujQZORGLQ -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: sectionDescription<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:sectionDescription,_z7ZC4LwPEdm6DujQZORGLQ CRC: 2899881365 --><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/use_case_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><!-- END:sectionDescription,_z7ZC4LwPEdm6DujQZORGLQ -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: name<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:name,_1LVn0LwPEdm6DujQZORGLQ CRC: 3411033524 -->Identify constraints on the system<!-- END:name,_1LVn0LwPEdm6DujQZORGLQ -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: sectionDescription<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:sectionDescription,_1LVn0LwPEdm6DujQZORGLQ CRC: 1784410595 --><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><!-- END:sectionDescription,_1LVn0LwPEdm6DujQZORGLQ -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: name<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:name,_2VixILwPEdm6DujQZORGLQ CRC: 233204114 -->Define features of the system<!-- END:name,_2VixILwPEdm6DujQZORGLQ -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: sectionDescription<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:sectionDescription,_2VixILwPEdm6DujQZORGLQ CRC: 2100849161 --><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><!-- END:sectionDescription,_2VixILwPEdm6DujQZORGLQ -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: name<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:name,_AhjmAL-GEdqb7N6KIeDL8Q CRC: 832005153 -->Achieve concurrence<!-- END:name,_AhjmAL-GEdqb7N6KIeDL8Q -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: sectionDescription<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:sectionDescription,_AhjmAL-GEdqb7N6KIeDL8Q CRC: 1395791106 -->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.<!-- END:sectionDescription,_AhjmAL-GEdqb7N6KIeDL8Q -->
 </body>
 </html>
	<?xml version="1.0" encoding="UTF-8"?>
	<!DOCTYPE html PUBLIC "-//W3C/DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd">
	<!-- VERSION rmc:7.1.0 -->
	<html xmlns="http://www.w3.org/1999/xhtml">
	<head>
	<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
	<!-- START NON-TRANSLATABLE -->
	<title>openup&#92;tasks&#92;&#92;define_vision.xmi</title>
	</head>
	<!-- WARNING: do not modify the generated comments in this file below this line. They are used as markers for the import process. -->
	<body>
	Element Name: define_vision.xmi<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: presentationName<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:presentationName,_0fOAoMlgEdmt3adZL5Dmdw CRC: 2887983663 -->Define Vision<!-- END:presentationName,_0fOAoMlgEdmt3adZL5Dmdw -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: briefDescription<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:briefDescription,_0fOAoMlgEdmt3adZL5Dmdw CRC: 2748033547 -->Define the vision for the future system. Describe the problem and features based on Stakeholder requests.<!-- END:briefDescription,_0fOAoMlgEdmt3adZL5Dmdw -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: purpose<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:purpose,_5rJ78Lj3Edmy88CC3LfB_w CRC: 1070376138 -->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.<!-- END:purpose,_5rJ78Lj3Edmy88CC3LfB_w -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: name<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:name,_tvzDULwPEdm6DujQZORGLQ CRC: 4020447428 -->Identify Stakeholders<!-- END:name,_tvzDULwPEdm6DujQZORGLQ -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: sectionDescription<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:sectionDescription,_tvzDULwPEdm6DujQZORGLQ CRC: 949225215 --><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><!-- END:sectionDescription,_tvzDULwPEdm6DujQZORGLQ -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: name<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:name,_sa5F4LwPEdm6DujQZORGLQ CRC: 3957171804 -->Gain agreement on the problem to be solved<!-- END:name,_sa5F4LwPEdm6DujQZORGLQ -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: sectionDescription<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:sectionDescription,_sa5F4LwPEdm6DujQZORGLQ CRC: 2045030396 -->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 techniques like the ones described in <a class="elementlinkwithtype" href="./../../openup/guidances/guidelines/requirements_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 /><!-- END:sectionDescription,_sa5F4LwPEdm6DujQZORGLQ -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: name<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:name,_rliOAOz2Edq2wJOsmRwmhg CRC: 2019227070 -->Capture a common vocabulary<!-- END:name,_rliOAOz2Edq2wJOsmRwmhg -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: sectionDescription<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:sectionDescription,_rliOAOz2Edq2wJOsmRwmhg CRC: 2505467041 -->Every project has its own specialized terminology that everyone on the team must understand well to communicate effectively
	with stakeholders. Work with stakeholders to create a glossary that defines acronyms, abbreviations, and relevant
	business and technical terms. Work with stakeholder to continually expand and refine the glossary throughout the
	project life cycle.<!-- END:sectionDescription,_rliOAOz2Edq2wJOsmRwmhg -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: name<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:name,_vGg-oLwPEdm6DujQZORGLQ CRC: 1906815529 -->Gather stakeholder requests<!-- END:name,_vGg-oLwPEdm6DujQZORGLQ -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: sectionDescription<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:sectionDescription,_vGg-oLwPEdm6DujQZORGLQ CRC: 460762192 --><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 Work Item List.
	</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><!-- END:sectionDescription,_vGg-oLwPEdm6DujQZORGLQ -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: name<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:name,_z7ZC4LwPEdm6DujQZORGLQ CRC: 3642748269 -->Define the system boundaries<!-- END:name,_z7ZC4LwPEdm6DujQZORGLQ -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: sectionDescription<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:sectionDescription,_z7ZC4LwPEdm6DujQZORGLQ CRC: 2899881365 --><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> and the <a class="elementLink" href="./../../openup/roles/architect_E7A12309.html" guid="_0X9iEMlgEdmt3adZL5Dmdw">Architect</a> since decisions
	concerning system boundaries will have a major impact on cost, schedule and system architecture.
	</p>
	<p>
	A <a class="elementLink" href="./../../openup/workproducts/use_case_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><!-- END:sectionDescription,_z7ZC4LwPEdm6DujQZORGLQ -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: name<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:name,_1LVn0LwPEdm6DujQZORGLQ CRC: 3411033524 -->Identify constraints on the system<!-- END:name,_1LVn0LwPEdm6DujQZORGLQ -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: sectionDescription<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:sectionDescription,_1LVn0LwPEdm6DujQZORGLQ CRC: 1784410595 --><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> and the <a class="elementLink" href="./../../openup/roles/architect_E7A12309.html" guid="_0X9iEMlgEdmt3adZL5Dmdw">Architect</a> since decisions
	concerning system constraints will have a major impact on cost, schedule and system architecture.
	</p><!-- END:sectionDescription,_1LVn0LwPEdm6DujQZORGLQ -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: name<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:name,_2VixILwPEdm6DujQZORGLQ CRC: 233204114 -->Define features of the system<!-- END:name,_2VixILwPEdm6DujQZORGLQ -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: sectionDescription<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:sectionDescription,_2VixILwPEdm6DujQZORGLQ CRC: 2100849161 --><p>

	Work with stakeholders to capture a list of <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> to capture the features identified and their attributes.

	</p><!-- END:sectionDescription,_2VixILwPEdm6DujQZORGLQ -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: name<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:name,_AhjmAL-GEdqb7N6KIeDL8Q CRC: 832005153 -->Achieve concurrence<!-- END:name,_AhjmAL-GEdqb7N6KIeDL8Q -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: sectionDescription<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:sectionDescription,_AhjmAL-GEdqb7N6KIeDL8Q CRC: 1395791106 -->Conduct a review of the project vision with relevant Stakeholders and the development team to ensure agreement, assess


	quality, and identify required changes. See <a class="elementLinkWithType" href="./../../openup/guidances/guidelines/effective_requirements_reviews_5913D369.html" guid="_E-dPIL-GEdqb7N6KIeDL8Q">Guideline: Effective Requirement Reviews</a> for more information.<!-- END:sectionDescription,_AhjmAL-GEdqb7N6KIeDL8Q -->
	</body>
	</html>