requirements document Comparison Table

Object Oriented Software Engineering View all facts Glossary Help

subject > representation > document > requirements document

Next document: specification Up: document Previous document: release notes

requirements document comparison table

Subject include be is a subtopic of consist of describe lead to mirror has definition contain

functional requirements
everything that a user of the system would need to know regarding what the system does, and
everything that would concern any other system that will have to interface to this system
well organized 4.5 - Types of Requirements particular algorithms to be used
What inputs the system should accept, and under what conditions
What outputs the system should produce, and under what conditions
What data the system should store that other systems might use
What computations the system should perform
The timing and synchronization of the above

non-functional requirements well organized 4.5 - Types of Requirements constraints that must be adhered to during development requirements in the introduction and conclusion to avoid the problem of changing the requirements in one place and forgetting to change them in another place

requirements definition well organized 4.7 - Types of Requirements Document A high-level requirements document that describes requirements using language understandable by customers and end users requirements in the introduction and conclusion to avoid the problem of changing the requirements in one place and forgetting to change them in another place

requirements document derived from use cases well organized 7.3 - Developing Use Case Models of Systems innovative solutions mirror the way users worked before the software was developed requirements in the introduction and conclusion to avoid the problem of changing the requirements in one place and forgetting to change them in another place

requirements document for a large system more detailed than the requirements document for a small system because there is more to say and because the system will need to be divided into subsystems so that different teams can work on each part 4.7 - Types of Requirements Document a series of documents arranged in a hierarchy requirements in the introduction and conclusion to avoid the problem of changing the requirements in one place and forgetting to change them in another place

Subject	include	be	is a subtopic of	consist of	describe	lead to	mirror	has definition	contain
functional requirements	everything that a user of the system would need to know regarding what the system does, and everything that would concern any other system that will have to interface to this system	well organized	4.5 - Types of Requirements		particular algorithms to be used				What inputs the system should accept, and under what conditions What outputs the system should produce, and under what conditions What data the system should store that other systems might use What computations the system should perform The timing and synchronization of the above
non-functional requirements		well organized	4.5 - Types of Requirements		constraints that must be adhered to during development				requirements in the introduction and conclusion to avoid the problem of changing the requirements in one place and forgetting to change them in another place
requirements definition		well organized	4.7 - Types of Requirements Document					A high-level requirements document that describes requirements using language understandable by customers and end users	requirements in the introduction and conclusion to avoid the problem of changing the requirements in one place and forgetting to change them in another place
requirements document derived from use cases		well organized	7.3 - Developing Use Case Models of Systems			innovative solutions	mirror the way users worked before the software was developed		requirements in the introduction and conclusion to avoid the problem of changing the requirements in one place and forgetting to change them in another place
requirements document for a large system		more detailed than the requirements document for a small system because there is more to say and because the system will need to be divided into subsystems so that different teams can work on each part	4.7 - Types of Requirements Document	a series of documents arranged in a hierarchy					requirements in the introduction and conclusion to avoid the problem of changing the requirements in one place and forgetting to change them in another place

Next document: specification Up: document Previous document: release notes