blob: 9876d2d5ec9f627a9072caf0ddbe27547e867d20 [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\disciplines\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: requirements.xmi<br/><br/>
<!-- END NON-TRANSLATABLE -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: presentationName<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:presentationName,_0TR2ZMlgEdmt3adZL5Dmdw CRC: 1754233426 -->Requirements<!-- END:presentationName,_0TR2ZMlgEdmt3adZL5Dmdw -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: briefDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:briefDescription,_0TR2ZMlgEdmt3adZL5Dmdw CRC: 4273847759 -->This discipline defines the minimal tasks required to elicit, analyze, specify, validate and manage the requirements for the system to be developed.<!-- END:briefDescription,_0TR2ZMlgEdmt3adZL5Dmdw -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: mainDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:mainDescription,__rFCULv9EdmmUvZAZjqE3g CRC: 2365414637 --><p>
The purpose of this discipline is to:
</p>
<ul>
<li>
Understand the problem to be solved
</li>
<li>
Understand stakeholder needs (what users want)&nbsp;
</li>
<li>
Define the requirements for the solution (what the system must do)
</li>
<li>
Define the boundaries (scope) of the system
</li>
<li>
Identify external interfaces for the system
</li>
<li>
Identify technical constraints on the solution
</li>
<li>
Provide the basis for planning iterations
</li>
<li>
Provide the initial basis for estimating cost and schedule
</li>
</ul>
<p>
To achieve these goals, it is important to understand the definition and scope of the problem&nbsp;that we are trying
to solve.&nbsp; <a class="elementLinkWithUserText" href="./../../openup_basic/roles/stakeholder,_dTa6gMAYEdqX-s4mWhkyqQ.html" guid="_dTa6gMAYEdqX-s4mWhkyqQ">Stakeholders</a>&nbsp;are identified and the problem to be solved is defined.
</p>
<p>
Having agreed on the problem to be solved, the <a class="elementLink" href="./../../openup_basic/guidances/concepts/requirements,_0Wh-sMlgEdmt3adZL5Dmdw.html" guid="_0Wh-sMlgEdmt3adZL5Dmdw">Requirements</a>&nbsp;for the system are elicited, organized, analyzed, validated and
specified.
</p>
<p>
Throughout the lifecycle, changes to the requirements are managed.
</p>
<p>
The Requirements discipline is related to the other disciplines in the following ways:
</p>
<ul>
<li>
The <a class="elementLink" href="./../../openup_basic/disciplines/analysis_and_design,_0TX9AMlgEdmt3adZL5Dmdw.html" guid="_0TX9AMlgEdmt3adZL5Dmdw">Analysis & Design</a>&nbsp;discipline gets its primary input from the
Requirements discipline
</li>
<li>
The <a class="elementLink" href="./../../openup_basic/disciplines/test,_0TkKQMlgEdmt3adZL5Dmdw.html" guid="_0TkKQMlgEdmt3adZL5Dmdw">Test</a>&nbsp;discipline validates the system against the requirements
</li>
<li>
The <a class="elementLink" href="./../../openup_basic/disciplines/config_and_change_management,_0TwXgMlgEdmt3adZL5Dmdw.html" guid="_0TwXgMlgEdmt3adZL5Dmdw">Configuration & Change Management</a>&nbsp;discipline provides the mechanisms to
manage changes to the requirements
</li>
<li>
The <a class="elementLink" href="./../../openup_basic/disciplines/project_management,_0TqQ4MlgEdmt3adZL5Dmdw.html" guid="_0TqQ4MlgEdmt3adZL5Dmdw">Project Management</a>&nbsp;discipline plans the project and assigns
requirements&nbsp;to each iteration by analyzing the prioritized requirements and assigning work.&nbsp;
</li>
</ul><!-- END:mainDescription,__rFCULv9EdmmUvZAZjqE3g -->
</body>
</html>