|
ABSTRACT
When a complex system is to be realized as a combination of interacting components, development of those components should commence from a specification of the behavior required of the composite system. A separate specification should be used to describe the decomposition of that system into components. The first phase of implementation from a specification in this style is the derivation of the individual component behaviors implied by these specifications.
The virtues of this approach to specification are expounded, and specification language features that are supportive of it are presented. It is shown how these are incorporated in the specification language Gist, which our group has developed. These issues are illustrated in a development of a controller for elevators serving passengers in a multistory building.
REFERENCES
Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.
| |
1
|
BALZER, R. Transformational implementation: An example. IEEE Trans. Softw. Eng. SE-7, 1 (1981), 3-14.
|
| |
2
|
BALZER, R., AND GOLDMAN, N. Principles of good software specification and their implications for specification languages. In Specification o{ Reliable So{tware. IEEE Computer Society, 1979, 58-67.
|
 |
3
|
|
| |
4
|
BARTLETT, A. J., CHERRIE, B. H., LEHMAN, M. M., MAcLEAN, R. I., AND POTTS, C. The role of executable metric models in the programming process--fina/ report. Tech. Rep., Dept. of Computing and Control, Imperial College, London, 1984.
|
| |
5
|
DARLINGTON, J. A synthesis of several algorithms. Acta In{. 11, 1 (Dec. 1978), 1-30.
|
| |
6
|
|
| |
7
|
GREEN, C., LUCKHAM, D., BALZER, R., CHEATHAM, T., AND RICH, C. Report on a knowledge based software assistant. Tech. Rep. RADC-TR-83-195, Rome Air Development Center, Aug. 1983.
|
 |
8
|
|
 |
9
|
|
| |
10
|
|
| |
11
|
LONDON, P. E., AND FEATHER, M. S. Implementing specification freedoms. Sci. Comput. Program. 2 (1982), 91-131.
|
 |
12
|
|
| |
13
|
|
 |
14
|
|
 |
15
|
|
| |
16
|
ZAVE, P. An operational approach to requirements specification for embedded systems. IEEE Trans. So{tw. Eng. SE-8, 3 (May 1982), 250-269.
|
 |
17
|
|
CITED BY 50
|
|
|
|
|
Eric S. K. Yu , John Mylopoulos, Understanding “why” in software process modelling, analysis, and design, Proceedings of the 16th international conference on Software engineering, p.159-168, May 16-21, 1994, Sorrento, Italy
|
|
|
|
|
|
|
|
|
|
|
|
Bashar Nuseibeh , Jeff Kramer , Anthony Finkelstein, Expressing the relationships between multiple views in requirements specification, Proceedings of the 15th international conference on Software Engineering, p.187-196, May 17-21, 1993, Baltimore, Maryland, United States
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Emmanuel Letier , Jeff Kramer , Jeff Magee , Sebastian Uchitel, Monitoring and control in scenario-based requirements analysis, Proceedings of the 27th international conference on Software engineering, May 15-21, 2005, St. Louis, MO, USA
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
REVIEW
"John D. McLean : Reviewer"
This paper presents the specification language Gist and its accompanying
philosophy, the closed system> specification. Such a specification
describes the behavior of a total system without decomposing the system
into components, as opp
more...
|