requirement Comparison Table

subject > requirement

Next subject: resource Up: subject Previous subject: representation

requirement comparison table

Subject discover when be is a subtopic of describe restrict has definition

functional requirement consistent with project plan 4.5 - Types of Requirements what the system should do, i.e. the services provided for the users and for other systems A requirement that describes a service provided by a system

implicit requirement a user or tester runs the system verifiable 10.1 - Basic Definitions the domain A requirement not stated explicitly in the requirements document

non-functional requirement verifiable by measuring various aspects of the system and seeing if the measurements conform with the requirement 4.5 - Types of Requirements a constraint that must be adhered to during development the freedom of software engineers as they make design decisions because it limits what resources can be used and sets bounds on aspects of the software's quality A requirement that constrains design of a system, but does not describe a service that the system is to provide

realistic requirement verifiable 4.8 - Reviewing Requirements the domain A requirement that the development team has the expertise and technology to implement on the required platform within the budget and time available

Subject	discover when	be	is a subtopic of	describe	restrict	has definition
functional requirement		consistent with project plan	4.5 - Types of Requirements	what the system should do, i.e. the services provided for the users and for other systems		A requirement that describes a service provided by a system
implicit requirement	a user or tester runs the system	verifiable	10.1 - Basic Definitions	the domain		A requirement not stated explicitly in the requirements document
non-functional requirement		verifiable by measuring various aspects of the system and seeing if the measurements conform with the requirement	4.5 - Types of Requirements	a constraint that must be adhered to during development	the freedom of software engineers as they make design decisions because it limits what resources can be used and sets bounds on aspects of the software's quality	A requirement that constrains design of a system, but does not describe a service that the system is to provide
realistic requirement		verifiable	4.8 - Reviewing Requirements	the domain		A requirement that the development team has the expertise and technology to implement on the required platform within the budget and time available

Next subject: resource Up: subject Previous subject: representation