Please enable JavaScript.
Coggle requires JavaScript to display documents.
(6) Requirements Prioritization
also referred to TRIAGE, (7) Requirements…
-
(7) Requirements Specification
Functional & Non-Functional Req. are stored in a Software Requirements Specification (SRS)
can be represented by:
(1) well-structured written natural language
(2) visual models
(3) formal specifications by using mathematically precise language --> provide the greates rigor and precision
(1) states the functions, capabilities, system's characteristics, and constraints.
(2) describes the system's behaviors under various conditions
(3) basis for project planning, foundation for system testing and user documentation
Labeling Requirements
req. need a unique and persistent identifier
(1) helps refer to specific re. in change requests
(2) helps reuse req. in different projects
1st Method: Sequence Number
- gives every re. a unique sequence. e.g. UC-9
- prefix indicate the req. type
- number is not reused if a re. is deleted
PROS:
- make it easy to retain a unique identifies if you move the req. around in a document
CONS:
- number doesn't imply any order
-
3rd Method: Hierarchical Textual Tags
- structured, meaningful, and unaffected by adding or moving other req.