| <?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\guidances\concepts\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,_0Wh-sMlgEdmt3adZL5Dmdw CRC: 1754233426 -->Requirements<!-- END:presentationName,_0Wh-sMlgEdmt3adZL5Dmdw --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: briefDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:briefDescription,_0Wh-sMlgEdmt3adZL5Dmdw CRC: 2398827048 -->This page provides an informal definition of a requirement and explains how the concept is related to the process.<!-- END:briefDescription,_0Wh-sMlgEdmt3adZL5Dmdw --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: mainDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:mainDescription,_eUfzwMMyEdmdo9HxCRR_Gw CRC: 4040077616 --><p> |
| Requirements are the project team's to-do list. |
| </p> |
| <p align="left"> |
| Requirements define what is needed and focus the project team. They are the primary method used to communicate the |
| goals of the project to everyone on the team. |
| </p> |
| <div class="O" v:shape="_x0000_s1026"> |
| <div style="mso-line-spacing: '100 30 0'"> |
| Requirements define: |
| </div> |
| </div> |
| <ul> |
| <li> |
| What the stakeholders need; and |
| </li> |
| <li> |
| What the system must include to satisfy the stakeholder needs. |
| </li> |
| </ul> |
| <p align="left"> |
| Requirements are the basis for capturing and communicating needs, managing expectations, prioritizing and assigning |
| work, verifying and validating the system (acceptance), and managing the scope of the project. |
| </p> |
| <p align="left"> |
| Requirements may take different forms, including Use Cases and Scenarios, unstructured text, structured text, or a |
| combination, and they may be stated at different levels of granularity. At the highest level of granularity, <a |
| class="elementLink" href="./../../../openup_basic/guidances/termdefinitions/feature,_PgYREAeYEduWycDgioo5rg.html" |
| guid="_PgYREAeYEduWycDgioo5rg">Feature</a>s define the services that the system must provide to solve the customer's |
| problem. These are captured as structured or unstructured text in the <a class="elementLinkWithType" |
| href="./../../../openup_basic/workproducts/vision,_0WVxcMlgEdmt3adZL5Dmdw.html" |
| guid="_0WVxcMlgEdmt3adZL5Dmdw">Artifact: Vision</a>. At the next level of granularity, Use Cases define the |
| functionality that the system must provide to deliver the required features. These are captured as Use Cases |
| (see <a class="elementLinkWithType" href="./../../../openup_basic/workproducts/use_case,_0VGbUMlgEdmt3adZL5Dmdw.html" |
| guid="_0VGbUMlgEdmt3adZL5Dmdw">Artifact: Use Case</a>) that describe the sequence of actions performed by the |
| system to yield an observable result of value. |
| </p> |
| <p> |
| A system must perform according to the behavior that Use Cases specify. However, there are system requirements that do |
| not represent a specific behavior: |
| </p> |
| <ul> |
| <li> |
| Legal and regulatory requirements, as well as application standards |
| </li> |
| <li> |
| Quality attributes of the system to be built, including usability, reliability, performance, and supportability |
| requirements |
| </li> |
| <li> |
| Interface requirements to be able to communicate with external systems |
| </li> |
| <li> |
| Design constraints, such as those for operating systems and environments and for compatibility with other software |
| </li> |
| </ul> |
| <p> |
| These quality requirements are often referred to as <strong>non-functional</strong> requirements. |
| </p> |
| <p> |
| Quality requirements that apply to the system as a whole are captured as structured text in <a |
| class="elementLinkWithType" |
| href="./../../../openup_basic/workproducts/supporting_requirements,_BVh9cL-CEdqb7N6KIeDL8Q.html" |
| guid="_BVh9cL-CEdqb7N6KIeDL8Q">Artifact: Supporting Requirements</a>. Quality requirements that are closely |
| associated with a particular Use Case are often captured in the Use Case itself to simplify review, understanding, and |
| maintenance. |
| </p><!-- END:mainDescription,_eUfzwMMyEdmdo9HxCRR_Gw --> |
| </body> |
| </html> |
