blob: 9534a3058ab7bb542afe2eda73fa58a65037cf4c [file] [log] [blame]
<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:ContentDescription xmi:version="2.0"
xmlns:xmi="" xmlns:org.eclipse.epf.uma=""
xmlns:epf="" epf:version="1.5.0" xmi:id="_qktWQMM0EdmSIPI87WLu3g"
name="vision,_0WoFUMlgEdmt3adZL5Dmdw" guid="_qktWQMM0EdmSIPI87WLu3g" changeDate="2005-07-07T13:30:32.042-0700"
<sections xmi:id="_VwoioAeiEduWycDgioo5rg" name="Have you fully explored what the problem behind the problem is?"
Make sure that you have found the root cause of the Stakeholder's problem or need. Often, Stakeholders define solutions&#xD;
rather than stating the problem that they are experiencing or the pain they are experiencing. Subsequently, they may&#xD;
not have identified the problem correctly or the correct solution for it.&#xD;
For example, &quot;We can't support customers who want to buy online&quot; is better than &quot;We need an on-line purchasing system&quot;.&#xD;
<sections xmi:id="_dBs8gAeiEduWycDgioo5rg" name="Is the problem statement correctly formulated?"
<sectionDescription>Make sure that you have agreement on the problem to be solved.</sectionDescription>
<sections xmi:id="_jGUxYAeiEduWycDgioo5rg" name="Is the list of Stakeholders complete and correct?"
<sectionDescription>Make sure you didn't miss any Stakeholders. If you did, you probably do not yet have all of the perspectives that you need&#xD;
to consider.</sectionDescription>
<sections xmi:id="_s-be8AeiEduWycDgioo5rg" name="Does everyone agree on the definition of the system boundaries?"
<sectionDescription>Define what is &lt;strong>in&lt;/strong> and what is &lt;strong>out&lt;/strong> of system boundaries. This is a critical step in&#xD;
defining the scope of work.</sectionDescription>
<sections xmi:id="_z1uG4AeiEduWycDgioo5rg" name="Have you sufficiently explored constraints to put on the system?"
<sectionDescription>Don't forget about the non-functional requirements and constraints. These are often the largest cost of development.</sectionDescription>
<sections xmi:id="_7KzeEAeiEduWycDgioo5rg" name="Have you covered all kinds of constraints, including political, economic, and environmental?"
These non-technical constraints often lead to problems later.&#xD;
<sections xmi:id="_DymaUAejEduWycDgioo5rg" name="Have all key features of the system been identified and defined?"
<sectionDescription>Do a completeness check, comparing the features with the problem statement, to make sure that you didn't miss a critical&#xD;
<sections xmi:id="_LRX5AAejEduWycDgioo5rg" name="Will the features solve the problems that are identified?"
<sectionDescription>Are all the features really necessary?&amp;nbsp; Perhaps you can reduce the scope.</sectionDescription>
<sections xmi:id="_UGRdIAejEduWycDgioo5rg" name="Are the features consistent with constraints that you've identified?"
Check that conflicting requirements do not exist. If you find conflicts, resolve them now.&#xD;
<sections xmi:id="_5y4uAAhUEduRe8TeoBmuGg" name="Can someone who is not familiar with the project understand what you hope the project will achieve by reading the Vision document?"
<sectionDescription>The purpose of the Vision document is to describe the objectives of the project in terms that non-technical people, who are&#xD;
not closely involved with the project, can understand.</sectionDescription>