ALLOCATE
To map or assign to.
CHILD
A child requirement has a hierarchical relationship to its parent. The parent requirement is not satisfied (met) until all of its children are satisfied.
DECOMPOSE
To break down into component parts. For example, ABCD decomposes to AB and CD. AB then decomposes to A and B, and CD decomposes to C and D. See Magic Square.
DERIVED
After some design, new requirements may be identified as a result of the design. These are derived requirements. Interfaces with other systems are an example. Some authors use derive to mean decompose.
DESIGN
Design requirements address how the system will accomplish the functional requirements.
FUNCTIONAL PRIMITIVE
In a data flow diagram, the bottom-most bubble, which is reached when further decomposition would yield the function's logic (if then or case,case) rather than child functions.
GAP ANALYSIS
An analysis of the gap between requirements that are met and not met; a deficiency assessment.
INVERSE
A requirement stated as a negative proposition (shall not). An inverse requirement is untestable.
NON-FUNCTIONAL
These requirements include areas such as performance, reliability, design and implementation constraints.
NON-TECHNICAL REQUIREMENTS
Agreements, conditions, and/or contractual terms that affect and determine the management activities of a project.
PARENT
Parent and child requirements have a hierarchical relationship. In functional decomposition, a parent may have many children, but a child can have only one parent. Where there is more than one level of decomposition, some requirements will be both parent and child. Functional primitives have no children. Parent-child is also used to describe traceable relationships. There can be more than one parent to a child in traceability.
PROCESS SPECIFICATION
Describes what is happening inside the functional primitive.
PROXY
May be used in place of an untestable requirement. For example, the requirement to be "user friendly" could have a proxy that online help be available.
REQUIREMENTS DEFINITION
An assessment of the needs a system is to fulfill, including why the system is needed; what features will service or satisfy the need; and how the system is to be constructed.
SYSTEM-LEVEL
Requirements that address an entire system, a major system division (e.g., hardware or software), or more than one subsystem; global requirements. It is not the breadth of the wording that makes a requirement system-level, but the extent of its impact on the system.
SYSTEM REQUIREMENT
Usually used as shorthand for "system functional requirement" but, depending on the speaker's perspective, could also mean "system-level," operating system, or something else. Clarify what the speaker means to avoid miscommunication.
SYSTEM FUNCTIONAL REQUIREMENTS
Are what a system must do to satisfy user requirements. System functional requirements include functional and non-functional requirements.
TRACEABLE
The origin of each requirement or requirement satisfier is clear (backwards trace); the allocation or satisfier of a requirement is clear (forwards trace).
USER REQUIREMENTS
Address what the users need to do their jobs. These requirements are implementation independent and are sometimes called "business requirements."
VALIDATION
Includes what is commonly thought of as testing and comparing test results to expected results.
VERIFICATION
Uses reviews, inspections, and demonstrations throughout development to ensure the quality of the product of that phase, including that it meets the requirements from the previous phase. Various authors define verification and validation somewhat differently.
|
