https://training-course-material.com/index.php?action=history&feed=atom&title=Requirements_ManagementRequirements Management - Revision history2026-05-02T17:15:13ZRevision history for this page on the wikiMediaWiki 1.45.1https://training-course-material.com/index.php?title=Requirements_Management&diff=61780&oldid=prevFilip Stachecki: /* Requirements Management⌘ */2017-10-07T16:35:15Z<p><span class="autocomment">Requirements Management⌘</span></p>
<p><b>New page</b></p><div>[[Category:UML|05]]<br />
<br />
==Requirements Management⌘==<br />
[[File:HowProjectsReallyWork.png]]<br />
===Requirement⌘===<br />
* A '''requirement''' is a singular documented physical and functional need that a particular design, product or process must be able to perform.<br />
* A Requirements specification is the direct result of a requirements analysis.<br />
* A Software requirements specification (SRS) is a complete description of the behavior of a system to be developed and may include a set of use cases and non-functional requirements.<br />
<br />
===Recommended Practice⌘===<br />
IEEE Recommended Practice for Software Requirements Specifications (IEEE Std 830-1998)<br />
<br />
====Characteristics of a good SRS⌘====<br />
# '''Correct''' - every requirement is one that the software shall meet;<br />
# '''Unambiguous''' - every requirement has only one interpretation;<br />
# '''Complete''': <br />
#* contains all significant requirements, specifies all responses to valid and invalid input values<br />
#* includes references to all figures, tables, and diagrams in the SRS and definition of all terms;<br />
# '''Consistent''' - internal consistency, if an SRS does not agree with some higher-level document, such as a system requirements specification, then it is not correct<br />
# '''Ranked for importance and/or stability''' - each requirement in it has an identifier to indicate either the importance or stability of that particular requirement;<br />
# '''Verifiable''' - every requirement is verifiable;<br />
# '''Modifiable''' - its structure and style are such that any changes to the requirements can be made easily, completely, and consistently;<br />
# '''Traceable''' - the origin of each of its requirements is clear and if it facilitates the referencing of each requirement in future development or enhancement documentation.<br />
<br />
===FURPS⌘===<br />
[[File:FURPS.png]]<br />
<br />
FURPS is an acronym representing a model for classifying requirements.<br />
<br />
'''Usability''' - UX, Human Factors, Aesthetics, Consistency, Documentation<br />
<br />
'''Reliability''' - Availability, Robustness/Durability, Recoverability, Stability, Accuracy<br />
<br />
'''Performance''' - Speed, Efficiency, Resource Consumption<br />
<br />
===Requirements Management <br/>with Enterprise Architect⌘===<br />
<br/><br />
[[File:RequirementsInEA.png]]</div>Filip Stachecki