Results 1 -
3 of
3
SIFT: Design and Analysis of a Fault-Tolerant Computer for Aircraft Control
- Proceedings of the IEEE
, 1978
"... Abstmt-SIFT (Softwue Implemented Fault Tolerance) is an upon active controls derived from computer outputs. Com ldtmdme Coreputer fa criticd.ircnlt caltrd appkdom that puters for this application must have a reliability that i! rhievesf.ulttdenncebytherep€hthoft&aamongproedng units. The rmin procesi ..."
Abstract
-
Cited by 76 (5 self)
- Add to MetaCart
Abstmt-SIFT (Softwue Implemented Fault Tolerance) is an upon active controls derived from computer outputs. Com ldtmdme Coreputer fa criticd.ircnlt caltrd appkdom that puters for this application must have a reliability that i! rhievesf.ulttdenncebytherep€hthoft&aamongproedng units. The rmin procesing units are off-the-shelf minicomputers, with comparable with other parts of the aircraft. The frequent13 sturdud microcomputers serving as the interface to the YO systean. quoted reliability requirement is that the probability o
Writing Larch Interface Language Specifications
- ACM Transactions on Programming Languages and Systems
, 1987
"... Current research in specifications is emphasizing the practical use of formal specifications in program design. One way to encourage their use in practice is to provide specification languages that are accessible to both designers and programmers. With this goal in mind, the Larch family of formal s ..."
Abstract
-
Cited by 68 (2 self)
- Add to MetaCart
Current research in specifications is emphasizing the practical use of formal specifications in program design. One way to encourage their use in practice is to provide specification languages that are accessible to both designers and programmers. With this goal in mind, the Larch family of formal specification languages has evolved to support a two-tiered approach to writing specifications. This approach separates the specification of state transformations and programming language dependen-cies from the specification of underlying abstractions. Thus, each member of the Larch family has a subset derived from a programming language and another subset independent of any programming languages. We call the former interface languages, and the latter the Larch Shared Language. This paper focuses on Larch interface language specifications. Through examples, we illustrate some salient features of Larch/CLU, a Larch interface language for the programming language CLU. We give an example of writing an interface specification following the two-tiered approach and discuss in detail issues involved in writing interface specifications and their interaction with their Shared Language components.
Maintaining Configurations of Evolving Software Systems
- IEEE Transactions on Software Engineering
, 1987
"... Abstract-Software configuration management (SCM) is an emerging discipline. An important aspect of realizing SCM is the task of maintaining the configurations of evolving software systems. In this paper, we provide an approach to resolving some ofthe conceptual and technical problems in maintaining ..."
Abstract
-
Cited by 24 (5 self)
- Add to MetaCart
Abstract-Software configuration management (SCM) is an emerging discipline. An important aspect of realizing SCM is the task of maintaining the configurations of evolving software systems. In this paper, we provide an approach to resolving some ofthe conceptual and technical problems in maintaining configurations of evolving software systems. The approach provides a formal basis for existing notions of system architecture. The formal properties of this view of configurations provide the underpinnings for a rigorous notion of system integrity, and mechanisms to control the evolution of configurations. This approach is embodied in a language, NuMIL, to describe software system configurations, and a prototype environment to maintain software system configurations. We believe that the approach and the prototype environment offer a firm base to maintain software system configurations and, therefore, to implement SCM. Index Terms-Configuration, module and subsystem families, module and subsystem interfaces, software configuration maintenance system, upward compatibility. I.

