• Corpus ID: 14462601

A Reference Model for Requirements and Speciications Bell Labs

@inproceedings{GunterBell1998ARM,
  title={A Reference Model for Requirements and Speciications Bell Labs},
  author={Elsa L. GunterBell and T LaboratoriesApril},
  year={1998}
}
We deene a reference model for applying formal methods to the development of user requirements and their reduction to behavioral speciication of a system. The approach is characterized by its focus on the shared phenomena that deene the interface between the system and the environment in which it will operate and on how the parts of this interface are controlled. This paper extends our previous work on this model by representing it in higher-order logic and determining some of its key… 

References

SHOWING 1-10 OF 32 REFERENCES

A Reference Model for Requirements and Specifications

A new form of refinement is introduced, which is pivotal to defining the desired soundness and consistency properties precisely and represents it in higher-order logic and some of its key mathematical ramifications are determined.

The Village Telephone System: A Case Study in Formal Software Engineering

A new HOL theory of inductive sequences that is suited to modelling reactive systems and provides a common basis for interoperability between HOL and Mocha is developed.

HOL: A Proof Generating System for Higher-Order Logic

This paper starts with a tutorial introduction to the meta-language ML and describes the version of higher-order logic implemented in the HOL system, followed by an introduction to goal-directed proof with tactics and tacticals.

Reactive Modules

  • R. AlurT. Henzinger
  • Computer Science, Mathematics
    Proceedings 11th Annual IEEE Symposium on Logic in Computer Science
  • 1996
The model represents synchronous and asynchronous components in a uniform framework that supports compositional (assume-guarantee) and hierarchical design and verification and uses a hiding operator that may turn a synchronous system into an asynchronous one.

Four dark corners of requirements engineering

It is shown that all descriptions involved in requirements engineering should be descriptions of the environment, and certain control information is necessary for sound requirements engineering, and the close association between domain knowledge and refinement of requirements is explained.

The temporal logic of actions

This report introduces TLA and describes how it is used to specifying and verify concurrent algorithms and the use of TLA to specify and reason about open systems will be described elsewhere.

Domain descriptions

  • M. JacksonP. Zave
  • Computer Science
    [1993] Proceedings of the IEEE International Symposium on Requirements Engineering
  • 1993
It is argued that current formal specification techniques are inadequate in this respect, and therefore cannot offer a satisfactory foundation for automated support of software development.

Documentation of requirements for computer systems

A functional approach to specifying the requirements of a computer system is discussed, a refinement of the method used in the A-7 aircraft software requirements model document.

MOCHA: Modularity in Model Checking

This paper presents a parallel version of the Celada–Seiden cellular automaton that automates the very labor-intensive and therefore time-heavy and therefore expensive and expensive and therefore computationally burdensome process of integrating these two systems.

Debugging the development process : practical strategies for staying focused, hitting ship dates, and building solid teams

In Debugging the Development Process, Maguire describes the sometimes controversial but always effective practices that enabled his software teams at Microsoft to develop high-quality software - on