Please enable JavaScript.
Coggle requires JavaScript to display documents.
Validation and Traceability (Questions to ask (Is each requirement…
- Validation and Traceability
Requirements validation
Process of checking that requirements defined for development, define the system that the customer really wants
To check issues related to requirements, we perform requirement validation
As each element of the requirements model is created, it is examined for
-
-
-
-
-
Questions to ask
-
Have all requirements been specified at the proper lvel of abstraction? That is, do some requirements provide a level of technical detail that is inappropriate at this stage?
Is the requirement really necessary or does it represent an add-on feature that may not be essential to the objective of the system?
-
-
-
Is each requirement testable, once implemented?
Does the requirements model properly reflect the information, function, and behavior of the system to be built?
Has the requirements model been "patitioned" in a way that exposes progessively more detailed information about the system?
-
-
Bad software
Factors of bad software
-
-
Immature, undisciplined practices / using less qualified SE => badly engineering software
-
-
-
-
-
Software quality
Quality of design encompasses the degree to which the design meets the functions and features specified in the requirements model
Quality of conformance focuses on the degree to which the implementation follows the design and the resulting system meets its requirements and performance goals
-
Validation process
-
-
Guidelines
Identify objective facts, not opinions
Constructive criticism, not offensive
-
-
-
-
-
-
Traceability
-
-
-
-
Traceability links
-
-
-
Use
-
Changing A makes B incomplete, inadequate, inconsistent, ambiguous
-