An approach to writing requirements when you have to define a number of possible alternative courses of action.
Tabular specification
A chapter of SRS which provides detailed, specific information that is related to the application being developed
Appendices
Requirements documents standards have been designed by?
IEEE
An approach to writing requirements where information about the information needed for the computation and other entities are used.
Form-based specification
A chapter of SRS which describes the functional and non-functional requirements in more detail.
System requirements specification
A way of writing SRS that is written in natural language or standard form template.
– Structured natural language
Statements of services the system should provide, how the system should react to particular inputs and how the system should behave in particular situations.
– Functional requirements
Defines what should be implemented so may be part of a contract between client and contractor.
– System requirements
The process of establishing the services that the customer requires from a system and the constraints under which it operates and is developed
Requirements Engineering
A chapter of SRS which describes the need for the system
Introduction
Should include descriptions of all facilities required.
Requirements completeness
A chapter of SRS which describes the fundamental assumptions on which the system is based, and any anticipated changes
System Evolution
Statements in natural language plus diagrams of the services the system provides and its operational constraints.
User requirements
A process activity which includes prioritizing requirements and resolving requirements conflicts
Prioritization and negotiation
An approach to writing requirements where the freedom of the requirements writer is limited and requirements are written in a standard way.
Structured specification
A type of user of requirements document who use the SRS to understand what system is to be developed.
System Engineers
Requirements which arise from the factors which are external to the system and its development process.
None of the above
A type of user of requirements document who use the SRS to plan a bid for the system and to plan the system development process.
Managers
A type of user of requirements document who use the SRS to understand the system and the relationship between its parts
System Maintenance Engineers
A process activity which includes interacting with stakeholders to discover their requirements.
Requirements discovery
A way of writing SRS which use models such as UML to define the functional requirements for the system.
Graphical Notations
A chapter of SRS which includes graphical system representation such as object models, data-flow models, or semantic data models
System models
Constraints on the system from the domain of operation.
Domain requirements
A chapter of SRS which defines the technical terms used in the document.
– Glossary