blob: 1420d15c67d60ff23a91537f9e6394ece23c1210 [file] [log] [blame]
<?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_basic\tasks\detail_requirements.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: detail_requirements.xmi<br/><br/>
<!-- END NON-TRANSLATABLE -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: presentationName<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:presentationName,_0e1mIMlgEdmt3adZL5Dmdw CRC: 3482111992 -->Detail Requirements<!-- END:presentationName,_0e1mIMlgEdmt3adZL5Dmdw -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: briefDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:briefDescription,_0e1mIMlgEdmt3adZL5Dmdw CRC: 3172934708 -->This task describes how to detail one or more requirements for the system.<!-- END:briefDescription,_0e1mIMlgEdmt3adZL5Dmdw -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: purpose<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:purpose,_Nqwi8KeqEdmKDbQuyzCoqQ CRC: 26759261 --><p>
The purpose of this task is to describe one or more requirements&nbsp;in sufficient detail to validate understanding of
the requirement, to ensure concurrence with stakeholders expectations, and to permit software development&nbsp;to
begin.
</p><!-- END:purpose,_Nqwi8KeqEdmKDbQuyzCoqQ -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: name<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:name,_vWeHMCxSEdqjsdw1QLH_6Q CRC: 733310024 -->Detail Use Cases and Scenarios<!-- END:name,_vWeHMCxSEdqjsdw1QLH_6Q -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: sectionDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:sectionDescription,_vWeHMCxSEdqjsdw1QLH_6Q CRC: 1909911892 --><p>
Some <a class="elementLink" href="./../../openup_basic/workproducts/use_case,_0VGbUMlgEdmt3adZL5Dmdw.html" guid="_0VGbUMlgEdmt3adZL5Dmdw">Use Case</a>s and Scenarios may need to be described in more detail to validate our
understanding of the requirement and to permit software development to begin. This does not imply that all&nbsp;use
cases and scenarios&nbsp;will be detailed prior to commencing implementation.&nbsp;&nbsp;Work with stakeholders to
detail only those that are prioritized for implementation in the next iteration or two (see <a class="elementLinkWithType" href="./../../openup_basic/workproducts/work_items_list,_rGNWsCbSEdqh1LYUOGRh2A.html" guid="_rGNWsCbSEdqh1LYUOGRh2A">Artifact: Work Items List</a>), or those that are deemed architecturally significant
(see <a class="elementLinkWithType" href="./../../openup_basic/guidances/concepts/architecturally_significant_requirements,_HrZGIA4MEduibvKwrGxWxA.html" guid="_HrZGIA4MEduibvKwrGxWxA">Concept: Architecturally Significant Requirements</a>.)
</p>
<p>
The level of detail captured will vary depending upon the needs of the project and the complexity of the use
case.&nbsp; For a discussion of the different levels of detail that may be applicable see <a class="elementLinkWithType" href="./../../openup_basic/guidances/guidelines/use_case_formats,_qq0GMAXkEduj_7BEUj1JfQ.html" guid="_qq0GMAXkEduj_7BEUj1JfQ">Guideline: Use Case Formats</a>.
</p>
<p>
Capture the use case&nbsp;details in <a class="elementLinkWithType" href="./../../openup_basic/workproducts/use_case,_0VGbUMlgEdmt3adZL5Dmdw.html" guid="_0VGbUMlgEdmt3adZL5Dmdw">Artifact: Use Case</a>.&nbsp; For additional information on detailing use cases and scenarios, see&nbsp;<a class="elementLinkWithType" href="./../../openup_basic/guidances/guidelines/detail_ucs_and_scenarios,_4BJ_YCxSEdqjsdw1QLH_6Q.html" guid="_4BJ_YCxSEdqjsdw1QLH_6Q">Guideline: Detail Use Cases and Scenarios</a>.&nbsp; For assistance in assessing the
quality of your use cases see <a class="elementLinkWithType" href="./../../openup_basic/guidances/checklists/use_case,_0kNwINk1Edq2Q8qZoWbvGA.html" guid="_0kNwINk1Edq2Q8qZoWbvGA">Checklist: Use Case</a>.
</p><!-- END:sectionDescription,_vWeHMCxSEdqjsdw1QLH_6Q -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: name<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:name,_B47VwCxTEdqjsdw1QLH_6Q CRC: 1322327703 -->Detail supporting requirements<!-- END:name,_B47VwCxTEdqjsdw1QLH_6Q -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: sectionDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:sectionDescription,_B47VwCxTEdqjsdw1QLH_6Q CRC: 2781639432 --><p>
Some&nbsp;<a class="elementLink" href="./../../openup_basic/workproducts/supporting_requirements,_BVh9cL-CEdqb7N6KIeDL8Q.html" guid="_BVh9cL-CEdqb7N6KIeDL8Q">Supporting Requirements</a> may need to be clarified or described in more detail, new
requirements&nbsp;may have been discovered as we detailed the use cases and scenarios, and new requirements may have
been submitted as <a class="elementLink" href="./../../openup_basic/guidances/concepts/change_requests,_6jdvECb3Edqh1LYUOGRh2A.html" guid="_6jdvECb3Edqh1LYUOGRh2A">Change Requests</a>.&nbsp;Work with stakeholders to capture, refine and validate those
requirements that will have an impact on near term work (see <a class="elementLinkWithType" href="./../../openup_basic/workproducts/work_items_list,_rGNWsCbSEdqh1LYUOGRh2A.html" guid="_rGNWsCbSEdqh1LYUOGRh2A">Artifact: Work Items List</a>) or are deemed architecturally significant (see <a class="elementLinkWithType" href="./../../openup_basic/guidances/concepts/architecturally_significant_requirements,_HrZGIA4MEduibvKwrGxWxA.html" guid="_HrZGIA4MEduibvKwrGxWxA">Concept: Architecturally Significant Requirements</a>).
</p>
<p>
Capture these requirements in&nbsp;the <a class="elementLinkWithType" href="./../../openup_basic/workproducts/supporting_requirements,_BVh9cL-CEdqb7N6KIeDL8Q.html" guid="_BVh9cL-CEdqb7N6KIeDL8Q">Artifact: Supporting Requirements</a>.&nbsp; For additional guidance on detailing
supporting requirements see <a class="elementLinkWithType" href="./../../openup_basic/guidances/guidelines/supporting_requirements,_wr24gNcGEdqz_d2XWoVt6Q.html" guid="_wr24gNcGEdqz_d2XWoVt6Q">Guideline: Supporting Requirements</a>.&nbsp; For assistance in assessing the quality of
your supporting requirements see <a class="elementLinkWithType" href="./../../openup_basic/guidances/checklists/supporting_requirements,_Vael8CGMEdu3VKXZx45D3A.html" guid="_Vael8CGMEdu3VKXZx45D3A">Checklist: Supporting Requirements</a>.
</p><!-- END:sectionDescription,_B47VwCxTEdqjsdw1QLH_6Q -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: name<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:name,_2389cOz2Edq2wJOsmRwmhg CRC: 4140312912 -->Detail glossary terms<!-- END:name,_2389cOz2Edq2wJOsmRwmhg -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: sectionDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:sectionDescription,_2389cOz2Edq2wJOsmRwmhg CRC: 30940822 -->Review the use case&nbsp;flow of events. If information is exchanged, be specific about what is passed back and
forth.&nbsp; Work with stakeholders to ensure that you define newly discovered domain terms, or ambiguous
terms&nbsp;properly in the <a class="elementLink" href="./../../openup_basic/workproducts/glossary,_Wn7HcNcEEdqz_d2XWoVt6Q.html" guid="_Wn7HcNcEEdqz_d2XWoVt6Q">Glossary</a>.
If your understanding of the domain has improved,&nbsp;refine existing glossary terms.<!-- END:sectionDescription,_2389cOz2Edq2wJOsmRwmhg -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: name<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:name,_BYbboN-bEdqiM_wFaqLjNg CRC: 832005153 -->Achieve concurrence<!-- END:name,_BYbboN-bEdqiM_wFaqLjNg -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: sectionDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:sectionDescription,_BYbboN-bEdqiM_wFaqLjNg CRC: 4193235022 -->Conduct a review&nbsp;of the&nbsp;requirements (<a class="elementLinkWithType" href="./../../openup_basic/workproducts/use_case,_0VGbUMlgEdmt3adZL5Dmdw.html" guid="_0VGbUMlgEdmt3adZL5Dmdw">Artifact: Use Case</a> and <a class="elementLinkWithType" href="./../../openup_basic/workproducts/supporting_requirements,_BVh9cL-CEdqb7N6KIeDL8Q.html" guid="_BVh9cL-CEdqb7N6KIeDL8Q">Artifact: Supporting Requirements</a>)&nbsp;with relevant&nbsp;<a class="elementLinkWithUserText" href="./../../openup_basic/roles/stakeholder,_dTa6gMAYEdqX-s4mWhkyqQ.html" guid="_dTa6gMAYEdqX-s4mWhkyqQ">Stakeholders</a> and the development team to ensure consistency with the <a class="elementLink" href="./../../openup_basic/workproducts/vision,_0WVxcMlgEdmt3adZL5Dmdw.html" guid="_0WVxcMlgEdmt3adZL5Dmdw">Vision</a>, assess quality, and identify required changes. See&nbsp;<a class="elementLinkWithType" href="./../../openup_basic/guidances/guidelines/effective_req_reviews,_E-dPIL-GEdqb7N6KIeDL8Q.html" guid="_E-dPIL-GEdqb7N6KIeDL8Q">Guideline: Effective Requirement Reviews</a>&nbsp;for more information.<!-- END:sectionDescription,_BYbboN-bEdqiM_wFaqLjNg -->
</body>
</html>