The PIOCO model for information systems design
MIS Quarterly
Origins of Software Performance Engineering: Highlights and Outstanding Problems
Performance Engineering, State of the Art and Current Trends
Origins of Software Performance Engineering: Highlights and Outstanding Problems
Performance Engineering, State of the Art and Current Trends
Capturing more world knowledge in the requirements specification
ICSE '82 Proceedings of the 6th international conference on Software engineering
Automatic Generation of Formal Specification from Requirements Definition
ICFEM '97 Proceedings of the 1st International Conference on Formal Engineering Methods
The software configuration management database
AFIPS '81 Proceedings of the May 4-7, 1981, national computer conference
AFIPS '83 Proceedings of the May 16-19, 1983, national computer conference
Introduction to software performance engineering: origins and outstanding problems
SFM'07 Proceedings of the 7th international conference on Formal methods for performance evaluation
Seven basic principles of software engineering
Journal of Systems and Software
Systems Analysis and Design Models Revisited: A Case Study
Information Resources Management Journal
| Hi-index | 0.00 |
The development of system requirements has been recognized as one of the major problems in the process of developing data processing system software. We have developed a computer-aided system for maintaining and analyzing such requirements. This system includes the Requirements Statement Language (RSL), a flow-oriented language for the expression of software requirements, and the Requirements Engineering and Validation System (REVS), a software package which includes a translator for RSL, a data base for maintaining the description of system requirements, and a collection of tools to analyze the information in the data base. The system emphasizes a balance between the use of the creativity of human thought processes and the rigor and thoroughness of computer analysis. To maintain this balance, two key design principles-extensibility and disciplined thinking-were foliowed throughout the system. Both the language and the software are easily user-extended, but adequate locks are placed on extensions, and limitations are imposed on use, so that discipline is augmented rather than decreased.