Executable requirements for embedded systems
International Conference on Software EngineeringPublished 9 March 1981
Pamela Zave, Raymond T. Yeh
Citations50
Generate an AI Snapshot to get a quick, structured summary of this paper.
Study Snapshot
ObjectiveStudy objective
MethodsResearch methodology
PopulationPopulation studied
Sample sizeSample sizes
OutcomesStudy outcomes here
ResultsStudy results comes here
LimitationsResearch study limitations comes here
A concise AI-generated summary of the paper will appear here once you click Generate AI Snapshot.
TL;DR
An approach to requirements specification for embedded systems, based on constructing an executable model of the proposed system interacting with its environment, is proposed, which is explained, motivated, and related to data-oriented specification techniques.
Abstract
An approach to requirements specification for embedded systems, based on constructing an executable model of the proposed system interacting with its environment, is proposed. The approach is explained, motivated, and related to data-oriented specification techniques. Portions of a specification language embodying it are introduced, and illustrated with an extended example in which the requirements for a process-control system are developed incrementally.
Keywords
Computer Science
Communications of the ACMCan programming be liberated from the von Neumann style?
2,582 Citations1978John Backus
A new class of computing systems uses the functional programming style both in its programming language and in its state transition rules; these systems have semantics loosely coupled to states—only one state transition occurs per major computation.
IEEE Transactions on Software EngineeringStructured Analysis (SA): A Language for Communicating Ideas
860 Citations1977Douglas T. Ross
The paper describes the rationalization behind some 40 features of the SA language, and shows how they enable rigorous communication which results in disciplined, recursive application of theSA maxim: "Everything worth saying about anything worth saying something about must be expressed in six or fewer pieces."
IEEE Transactions on Software EngineeringSpecifying Software Requirements for Complex Systems: New Techniques and Their Application
497 Citations1980Kathryn L. Heninger
The purpose of the paper is to introduce the A-7 document as a model of a disciplined approach to requirements specification and the document is available to anyone who wishes to see a fully worked-out example of the approach.
IEEE Transactions on Software EngineeringA Requirements Engineering Methodology for Real-Time Processing Requirements
294 Citations1977Mack Alford
This paper describes a methodology for the generation of software requirements for large, real-time unmanned weapons systems and how to use automated aids to improve the quality of the product.
IEEE Transactions on Software EngineeringAn Operational Approach to Requirements Specification for Embedded Systems
283 Citations1982Pamela Zave
The approach to requirements specification for embedded systems described in this paper is called "operational" because a requirements specification is an executable model of the proposed system interacting with its environment, embodied by the language PAISLey, which is motivated and defined herein.
IEEE Transactions on Software EngineeringAn Extendable Approach to Computer-Aided Software Requirements Engineering
149 Citations1977Thomas E. Bell, David C. Bixler +1 more
A computer-aided system for maintaining and analyzing system requirements, which 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.
Principles of good software specification and their implications for specification languages
120 Citations1981Robert Balzer, Neil Goldman
These principles result in eighteen implications for specification languages that strongly constrain the set of adequate specification languages and identify the need for several novel capabilities such as historical and future references, elimination of variables, and result specification.
ComputerDoD's Common Programming Language Effort
48 Citations1978David Fisher
DoD's common programming language effort is aimed at reducing the development and maintenance cost and improving the quality of software for embedded computer systems.
IEEE Transactions on Software EngineeringBehavior Modeling During Software Design
38 Citations1978William E. Riddle, Jack C. Wileden +3 more
A modeling scheme is presented which provides a medium for the rigorous, formal, and abstract specification of large-scale software system components, and allows the description of component behavior without revealing or requiring thedescription of a component's internal operation.
A Data Base Approach to Software Specification
21 Citations1980John Miles Smith, Diane C. P. Smith
A data base is a simulation of some real-world phenomena that is represented on a computing machine that is oriented towards applications where large quantities of intricately interrelated data are manipulated by multiple users.
Defense Technical Information Center (DTIC)'Real-World' Properties in the Requirements for Embedded Systems,
1 Citations1979Pamela Zave