Software Requirements Specification Standard
Jump to navigation
Jump to search
See: Documentation Standard, Software Requirements Document.
References
2011
- http://en.wikipedia.org/w/index.php?title=Software_Requirements_Specification&oldid=429590713
- A Software Requirements Specification (SRS) - a requirements specification for a software system - is a complete description of the behavior of a system to be developed. It includes a set of use cases that describe all the interactions the users will have with the software. In addition to use cases, the SRS also contains non-functional (or supplementary) requirements. Non-functional requirements are requirements which impose constraints on the design or implementation (such as performance engineering requirements, quality standards, or design constraints). The most general organization of an SRS is as follow ...
2008
- (Melli & McQuinn, 2008) ⇒ Gabor Melli, and Jerre McQuinn. (2008). “Requirements Specification Using Fact-Oriented Modeling: A Case Study and Generalization.” In: Proceedings of Workshop on Object-Role Modeling (ORM 2008). doi:10.1007/978-3-540-88875-8_98
- QUOTE: Fact-oriented Modeling [3], [4], [7] is an technique that assists with the conceptual modeling of an IT Solution. The approach however has not yet been fully incorporated into software requirement specification standards [8], [9], [10], [12], [13], [14], [2]. With the introduction of such standards as Structured Business Vocabulary and Rules (SBVR) [5], [7] it is now possible to consistently employ Fact-oriented Modeling in the delivery of enterprise solutions.