Specifying software requirements
- 1 January 1980
- journal article
- Published by Institute of Electrical and Electronics Engineers (IEEE) in Proceedings of the IEEE
- Vol. 68 (9) , 1077-1085
- https://doi.org/10.1109/proc.1980.11806
Abstract
Many of the problems of software system development can be traced to poor understanding or specification of what the system is supposed to do. Much attention is now being given to producing requirements specifications that are understandable, formal, complete, and modifiable. The structure and content of conceptual models for problem understanding are discussed; such models can form the basis for requirements analysis. Techniques for "tuning" and formally specifying the conceptual model are surveyed, and the proper scope of a software requirements document-including nonfunctional requirements such as performance-is explained.Keywords
This publication has 10 references indexed in Scilit:
- A comprehensive approach to requirements problemsPublished by Institute of Electrical and Electronics Engineers (IEEE) ,2005
- Principles of good software specification and their implications for specification languagesPublished by Association for Computing Machinery (ACM) ,1981
- Communication Port: A Language Concept for Concurrent ProgrammingIEEE Transactions on Software Engineering, 1980
- Petri NetsACM Computing Surveys, 1977
- A Requirements Engineering Methodology for Real-Time Processing RequirementsIEEE Transactions on Software Engineering, 1977
- PSL/PSA: A Computer-Aided Technique for Structured Documentation and Analysis of Information Processing SystemsIEEE Transactions on Software Engineering, 1977
- Structured Analysis (SA): A Language for Communicating IdeasIEEE Transactions on Software Engineering, 1977
- Software EngineeringIEEE Transactions on Computers, 1976
- The entity-relationship model—toward a unified view of dataACM Transactions on Database Systems, 1976
- A relational model of data for large shared data banksCommunications of the ACM, 1970