Cited By
View all- Avrunin GWileden J(1985)Describing and analyzing distributed software system designsACM Transactions on Programming Languages and Systems10.1145/3916.39897:3(380-403)Online publication date: 1-Jul-1985
DREAM - an approach to designing large scale, concurrent software systems
Pages 88 - 94
Abstract
The Design Realization, Evaluation And Modelling (DREAM) system is an automated support system for designers of large-scale, concurrent software systems. DREAM is intended to facilitate the orderly development of such software systems by supporting high-level, abstract design descriptions and the successive modification and elaboration of incomplete descriptions. DREAM also provides a basis for formulating arguments regarding the correctness of an evolving design at any stage during its development.
We begin this paper by presenting a viewpoint which has served to motivate our work in developing the DREAM system. Next we will describe DREAM itself, and its associated design language (the DREAM Design Notation or DDN). This discussion will highlight the major features of DREAM and the approach to software system design which DREAM supports. Finally, we will present a simple example of a DREAM design description. This should serve to illustrate both the specifics of the DREAM Design Notation and also the application of DDN to the description of concurrent software system designs.
References
[1]
A. Ambler et al. GYPSY: A Language for Specification and Implementation of Verifiable Programs. ICSCA-CMP-2, Certifiable Minicomputer Project, Univ. of Texas, Austin, January 1977.
[2]
J. Cuny. A DREAM Model of the RC4000 Multiprogramming System. RSSM/48, Dept. of Computer and Comm. Sciences, Univ. of Mich., Ann Arbor, July 1977.
[3]
J. Cuny. The GM Terminal System. RSSM/63, Dept. of Computer and Comm. Sciences, Univ. of Mich., Ann Arbor, August 1977.
[4]
J. Feldman. High Level Programming for Distributed Computing. Comm. ACM, 22, 6 (June 1979), 353-368.
[5]
C. Hoare. Monitors: An Operating System Structuring Concept. Comm. ACM, 17, 10 (October 1974), 549-557.
[6]
D. Parnas. Information Distribution Aspects of Design Methodology. Proc. IFIP Congress 71, Ljubljana, August 1971, pp. TA-3-26-TA-3-30.
[7]
W. Riddle and J. Wileden. Languages for Representing Software Specifications and Designs. Software Engineering Notes, 3, 5 (October 1978), pp. 1-5.
[8]
W. Riddle, J. Wileden, J. Sayler, A. Segal and A. Stavely. Behavior Modelling During Software Design. IEEE Transactions on Software Engineering, SE-4, 4 (July 1978), 283-292.
[9]
W. Riddle. Hierarchical Description of Software System Structure. @ RSSM/40, Dept. of Computer Science, Univ. of Colorado at Boulder, November 1977.
[10]
W. Riddle. Abstract Process Types. RSSM/42, Dept. of Computer Science, Univ. of Colorado at Boulder, December 1977 (revised July 1978).
[11]
W. Riddle, J. Sayler, A. Segal, A. Stavely and J. Wileden. Abstract Monitor Types. Proc. Specifications of Reliable Software, Boston, April 1979.
[12]
W. Riddle. DREAM Design Notation Example: The T.H.E. Operating System. RSSM/50, Dept. of Computer Science, Univ. of Colorado at Boulder, April 1978.
[13]
W. Riddle. An Approach to Software System Modelling and Analysis. J. of Computer Languages, to appear.
[14]
A. Segal. DREAM Design Notation Example: A Multiprocessor Supervisor. RSSM/53, Dept. of Computer and Comm. Sciences, Univ. of Mich., Ann Arbor, August 1977.
[15]
A. Stavely. DREAM Design Notation Example: An Aircraft Engine Monitoring System. RSSM/ 49, Dept. of Computer and Comm. Sciences, Univ. of Mich., Ann Arbor, July 1977.
[16]
J. Wileden. Behavior Specification in a Software Design Aid System. RSSM/43, Dept. of Computer and Information Science, Univ. of Massachusetts, August 1978.
[17]
J. Wileden. DREAM Design Notation Example: Scheduler for a Multiprocessor System. RSSM/51, Dept. of Computer and Comm. Sciences, Univ. of Mich., Ann Arbor, October 1977.
Index Terms
- DREAM - an approach to designing large scale, concurrent software systems
Recommendations
Designing real-time, concurrent, and embedded software systems using UML and Ada
SIGAda 2010The domain of real-time, concurrent, and embedded software is becoming increasing complex. To effectively develop these systems, greater care must be taken to construct adequate models of the software and to effectively analyze these designs prior to ...
Comments
Please enable JavaScript to view thecomments powered by Disqus.Information & Contributors
Information
Published In
Copyright © 1979 ACM.
Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for components of this work owned by others than ACM must be honored. Abstracting with credit is permitted. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from [email protected]
Publisher
Association for Computing Machinery
New York, NY, United States
Publication History
Published: 01 January 1979
Check for updates
Qualifiers
- Article
Contributors
Other Metrics
Bibliometrics & Citations
Bibliometrics
Article Metrics
- View Citations1Total Citations
- 266Total Downloads
- Downloads (Last 12 months)43
- Downloads (Last 6 weeks)4
Reflects downloads up to 14 Dec 2024
Other Metrics
Citations
Cited By
View all- Avrunin GWileden J(1985)Describing and analyzing distributed software system designsACM Transactions on Programming Languages and Systems10.1145/3916.39897:3(380-403)Online publication date: 1-Jul-1985
View Options
Login options
Check if you have access through your login credentials or your institution to get full access on this article.
Sign in