The Software Development System

Davis, Carl G.; Vick, Charles R.

doi:10.1109/tse.1977.233839

Cited by 77 publications

(6 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This is particularly exemplified by: the Requirements Statement Language [Davis & Vick 1977]; process entity-relationship models [Hamilton & Beeby 1991]; the DesignNet model [Liu & Horowitz 1989]; the Planning and Design Methodology [Mays et al 1985]; formal methods [Cooke & Stone 1991]; objectoriented methods [Henderson-Sellers & Edwards 1990]; and Quality Function Deployment [West 1991]. Here, requirements traceability is dependent on the use of distinct procedures and notations, and the end results will vary according to how rigidly these are adhered to.…”

Section: Basic Techniquesmentioning

confidence: 99%

An analysis of the requirements traceability problem

Gotel

Finkelstein

Proceedings of IEEE International Conference on Requirements Engineering

799

533

View full text Add to dashboard Cite

In this paper, we investigate and discuss the underlying nature of the requirements traceability problem. Our work is based on empirical studies carried out with over a hundred practitioners and an evaluation of current support for requirements traceability. We introduce the distinction between pre-requirements specification traceability and post-requirements specification traceability, to demonstrate why an all-encompassing solution to the problem is unlikely, and to provide a framework through which to understand its multifaceted nature. We report how the majority of the problems attributed to poor requirements traceability are mainly due to the lack of (or inadequate) pre-RS traceability and explain the fundamental need for improvements here. In the remainder of the paper, we present an analysis of the main barriers confronting such improvements in practice, identify relevant areas in which advances have been (or can be) made, and make recommendations for further research.

show abstract

Section: Basic Techniquesmentioning

confidence: 99%

An analysis of the requirements traceability problem

Gotel

Finkelstein

Proceedings of IEEE International Conference on Requirements Engineering

799

533

View full text Add to dashboard Cite

show abstract

“…These requirements are expressed in the Requirements State Language (RSL), and analyzed with the tools of the Requirements Engineering Validation System (REVS) (Bell et al 1977;Davis and Vick 1977). The tools are used to perform automated consistency and completeness analysis, produce documentation, and generate simulators for the specification requirements of a system (Alford 1985).…”

Section: Sremmentioning

confidence: 99%

Real-time software methodologies: Are they suitable for developing Manufacturing control software?

Chaar

Teichroew

Volz

1993

Int J Flex Manuf Syst

View full text Add to dashboard Cite

Abstract. Computer-Integrated Manufacturing (CIM) systems may be classified as real-time systems. Hence, the applicability of methodologies that are developed for specifying, designing, implementing, testing, and evolving real-time software is investigated in this article.The paper highlights the activities of the software development process. Among these activities, a great emphasis is placed on automating the software requirements specification activity, and a set of formal models and languages for specifying these requirements is presented. Moreover, a synopsis of the real-time software methodologies that have been implemented by the academic and industrial communities is presented together with a critique of the strengths and weaknesses of these methodologies.The possible use of the real-time methodologies in developing the control software of efficient and dependable manufacturing systems is explored. In these systems, efficiency is achieved by increasing the level of concurrency of the operations of a plan, and by scheduling the execution of these operations with the intent of maximizing the utilization of the devices of their systems. On the other hand, dependability requires monitoring the operations of these systems. This monitoring activity facilitates the detection of faults that may occur when executing the scheduled operations of a plan, recovering from these faults, and, whenever feasible, resuming the original schedule of the system. The paper concludes that the set of surveyed methodologies may be used to develop the real-time control software of efficient and dependable manufacturing systems. However, an integrated approach to planning, scheduling, and monitoring the operations of these systems will significantly enhance their utility, and no such approach is supported by any of these methodologies.

show abstract

“…Current technology includes the ISDOS system developed by Teichroew and his group at the University of Michigan [4], the Software Requirements Engineering Program (SREP) developed by TRW for the U.S. Army Ballistic Missile Defense Advanced Technology Center [5,6,7], the work on Structured Systems Requirements by Ken Orr & Associates in the commercial sector, and various efforts for developing "Programming Environments" including Unix, Interlisp, and the Ada Integrated Environment (per "Stonemmn").…”

Section: Structured Systems Requirementsmentioning

confidence: 99%