non-functional requirement Comparison Table

Object Oriented Software Engineering View all facts Glossary Help

subject > requirement > non-functional requirement

Next requirement: realistic requirement Up: requirement Previous requirement: implicit requirement

non-functional requirement comparison table

Subject observe by specify as is a subtopic of be often not included in affect by measure depends on evaluate on specify have example specify in terms of improve by allow appear affect indirectly by has definition describe have a direct impact on be

allowance for maintainability and enhancement 4.5 - Types of Requirements changes that are anticipated for subsequent releases verifiable by measuring various aspects of the system and seeing if the measurements conform with the requirement

allowance for reusability 4.5 - Types of Requirements the percentage of the system, measured in lines of code, that must be designed generically so that it can be reused verifiable by measuring various aspects of the system and seeing if the measurements conform with the requirement

availability 4.5 - Types of Requirements the amount of time that a server is running and available to respond to users A quality that measures the amount of time that a system is running and able to provide services to its users a constraint that must be adhered to during development verifiable by measuring various aspects of the system and seeing if the measurements conform with the requirement

cost and delivery date 4.5 - Types of Requirements the requirements document, but left to a separate project plan document a constraint that must be adhered to during development verifiable by measuring various aspects of the system and seeing if the measurements conform with the requirement

development process to be used 4.5 - Types of Requirements certain approaches to testing a constraint that must be adhered to during development verifiable by measuring various aspects of the system and seeing if the measurements conform with the requirement

platform 4.5 - Types of Requirements the least powerful platforms and declares that it must work on anything more recent or more powerful what hardware and operating system the software must be able to work on verifiable by measuring various aspects of the system and seeing if the measurements conform with the requirement

recovery from failure the maximum-allowed impact of a failure 4.5 - Types of Requirements for a word processing program: The system will allow users to continue their work after a failure with the loss of no more than 20 words of typing or 20 formatting commands a constraint that must be adhered to during development verifiable by measuring various aspects of the system and seeing if the measurements conform with the requirement

reliability stakeholders the average amount of time between failures or the probability of a failure in a given period 4.5 - Types of Requirements complexity of code the number of mistakes made by the software engineers who developed the software ensuring the software is easy to implement and change, and also ensuring that if failures occur, the system can handle them or can recover easily commenting An important quality of software that measures the frequency of failures, as encountered by testers and end-users a constraint that must be adhered to during development stakeholders more important than efficiency in a safety-critical system

resource usage 4.5 - Types of Requirements you could specify that no more than a certain amount of memory is to be used by the system, and that the system must consume less than 10% of the CPU's time the maximum amount of these resources that the system will consume others to efficiently plan hardware upgrades a constraint that must be adhered to during development verifiable by measuring various aspects of the system and seeing if the measurements conform with the requirement

response time 7.5 - Usability Principles the slowest hardware that end-users are likely to encounter instantaneous for some operations such as tracking the cursor, popping up of menus and echoing of input The time that elapses from when a user issues a command to when the system provides enough results so the user can continue his or her work a constraint that must be adhered to during development more than 15-20 seconds unless the user interface warns the user so the user can do something else while waiting or choose not to perform the operation

technology to be used 4.5 - Types of Requirements to ensure that all systems in an organization use the same technology the programming language or database system a constraint that must be adhered to during development verifiable by measuring various aspects of the system and seeing if the measurements conform with the requirement

throughput 4.5 - Types of Requirements computations or transactions per minute a constraint that must be adhered to during development verifiable by measuring various aspects of the system and seeing if the measurements conform with the requirement

Next requirement: realistic requirement Up: requirement Previous requirement: implicit requirement

Subject	observe by	specify as	is a subtopic of	be often not included in	affect by	measure	depends on	evaluate on	specify	have example	specify in terms of	improve by	allow	appear	affect indirectly by	has definition	describe	have a direct impact on	be
allowance for maintainability and enhancement			4.5 - Types of Requirements														changes that are anticipated for subsequent releases		verifiable by measuring various aspects of the system and seeing if the measurements conform with the requirement
allowance for reusability			4.5 - Types of Requirements														the percentage of the system, measured in lines of code, that must be designed generically so that it can be reused		verifiable by measuring various aspects of the system and seeing if the measurements conform with the requirement
availability			4.5 - Types of Requirements			the amount of time that a server is running and available to respond to users										A quality that measures the amount of time that a system is running and able to provide services to its users	a constraint that must be adhered to during development		verifiable by measuring various aspects of the system and seeing if the measurements conform with the requirement
cost and delivery date			4.5 - Types of Requirements	the requirements document, but left to a separate project plan document													a constraint that must be adhered to during development		verifiable by measuring various aspects of the system and seeing if the measurements conform with the requirement
development process to be used			4.5 - Types of Requirements							certain approaches to testing							a constraint that must be adhered to during development		verifiable by measuring various aspects of the system and seeing if the measurements conform with the requirement
platform			4.5 - Types of Requirements						the least powerful platforms and declares that it must work on anything more recent or more powerful								what hardware and operating system the software must be able to work on		verifiable by measuring various aspects of the system and seeing if the measurements conform with the requirement
recovery from failure		the maximum-allowed impact of a failure	4.5 - Types of Requirements							for a word processing program: The system will allow users to continue their work after a failure with the loss of no more than 20 words of typing or 20 formatting commands							a constraint that must be adhered to during development		verifiable by measuring various aspects of the system and seeing if the measurements conform with the requirement
reliability	stakeholders	the average amount of time between failures or the probability of a failure in a given period	4.5 - Types of Requirements		complexity of code		the number of mistakes made by the software engineers who developed the software					ensuring the software is easy to implement and change, and also ensuring that if failures occur, the system can handle them or can recover easily			commenting	An important quality of software that measures the frequency of failures, as encountered by testers and end-users	a constraint that must be adhered to during development	stakeholders	more important than efficiency in a safety-critical system
resource usage			4.5 - Types of Requirements							you could specify that no more than a certain amount of memory is to be used by the system, and that the system must consume less than 10% of the CPU's time	the maximum amount of these resources that the system will consume		others to efficiently plan hardware upgrades				a constraint that must be adhered to during development		verifiable by measuring various aspects of the system and seeing if the measurements conform with the requirement
response time			7.5 - Usability Principles					the slowest hardware that end-users are likely to encounter						instantaneous for some operations such as tracking the cursor, popping up of menus and echoing of input		The time that elapses from when a user issues a command to when the system provides enough results so the user can continue his or her work	a constraint that must be adhered to during development		more than 15-20 seconds unless the user interface warns the user so the user can do something else while waiting or choose not to perform the operation
technology to be used			4.5 - Types of Requirements						to ensure that all systems in an organization use the same technology	the programming language or database system							a constraint that must be adhered to during development		verifiable by measuring various aspects of the system and seeing if the measurements conform with the requirement
throughput			4.5 - Types of Requirements								computations or transactions per minute						a constraint that must be adhered to during development		verifiable by measuring various aspects of the system and seeing if the measurements conform with the requirement