Cited By
View all- Nakanishi TSaeki M(1999)Using Multiple Graphs of Programs to Modify SpecificationsProceedings of the Sixth Asia Pacific Software Engineering Conference10.5555/518898.785699Online publication date: 7-Dec-1999
Traceability and Modularity in Software Design
Page 87
Abstract
A software design specification consists of a number of documents that describe various aspect of the design at different levels of detail, that are linked in many ways. This paper shows how different designs may use different modularization criteria, and how documents describing these designs may be linked in a coherent way, even if the designs use techniques borrowed from structured as well as object-oriented analysis and design. Illustrations are taken from the meeting scheduler case study.
References
[1]
{1} S. Cook and J. Daniels. Designing Object Systems: Object-Oriented Modelling with Syntropy. Prentice-Hall, 1994.
[2]
{2} A. M. Davis. Software Requirements: Objects, Functions, States. Prentice-Hall, 1993.
[3]
{3} F. Dehne and R. J. Wieringa. The Yourdon Systems Method and the Toolkit for Conceptual Modeling. Technical Report IR-414, Faculty of Mathematics and Computer Science, Vrije Universiteit, De Boelelaan 1081a, 1081 HV Amsterdam, December 1996.
[4]
{4} F. Dehne and R. J. Wieringa. Toolkit for Conceptual Modeling (TCM): User's Guide. Technical Report IR- 401, Faculty of Mathematics and Computer Science, Vrije Universiteit, De Boelelaan 1081a, 1081 HV Amsterdam, 1996. http://www.cs.vu.nl/~tcm.
[5]
{5} T. DeMarco. Structured Analysis and System Specification . Yourdon Press/Prentice-Hall, 1978.
[6]
{6} B. Duterte and V. Stavridou. Formal requirements analysis of an avionics control system. IEEE Transactions on Software Engineering, 23(5), 1997.
[7]
{7} O. Gotel and A. Finkelstein. Contribution structures. In Second IEEE International Symposium on Requirements Engineering. IEEE Computer Society Press, 1995.
[8]
{8} D. Harel. On visual formalisms. Communications of the ACM, 31:514-530, 1988.
[9]
{9} M. Jackson. System Development. Prentice-Hall, 1983.
[10]
{10} M. Jackson. Software Requirements and Specifications: A lexicon of practice, principles and prejudices. Addison-Wesley, 1995.
[11]
{11} I. Jacobson, M. Christerson, P. Johnsson, and G. Övergaard. Object-Oriented Software Engineering: A Use Case Driven Approach. Prentice-Hall, 1992.
[12]
{12} G. LeLann. The arianne 5 flight 501 failure - a case study in system engineering for computing systems. Technical Report 3079, INRIA, December 1996. http://www.inria.fr/RRRT/RR-3079.html.
[13]
{13} J. Martin. Information Engineering. Prentice-Hall, 1989. Three volumes.
[14]
{14} S. M. McMenamin and J. F. Palmer. Essential Systems Analysis. Yourdon Press/Prentice Hall, 1984.
[15]
{15} S. Shlaer and S. J. Mellor. Object Lifecycles: Modeling the World in States. Prentice-Hall, 1992.
[16]
{16} K. Shumate. Structured analysis and object-oriented design are compatible. Ada Letters, 11(4):78-90, May/June 1991.
[17]
{17} R. J. Wieringa. A survey of structured and object-oriented software specification methods and techniques. Technical report, Faculty of Mathematics and Computer Science, Vrije Universiteit, De Boelelaan 1081a, 1081 HV Amsterdam, 1997. To be published, ACM Computing Surveys.
[18]
{18} R. J. Wieringa. Using the tools in TRADE, II: Specification and design of a meeting scheduler system. Technical Report IR-436, Faculty of Mathematics and Computer Science, Vrije Universiteit, November 1997. ftp://ftp.cs.vu.nl/pub/roelw/97- TRADE02.ps.Z.
[19]
{19} Yourdon Inc. Yourdon¿ Systems Method: Model-Driven Systems Development. Prentice-Hall, 1993.
Recommendations
A combined functional and object-oriented approach to software design
ICECCS '95: Proceedings of the 1st International Conference on Engineering of Complex Computer SystemsLarge and complex software systems contain a variety of entities (objects) and a complex control system (transformation function). The pure object-oriented design and structured design approaches concentrate on either objects or the transformation ...
Design module: a modularity vision beyond code: not only program code but also a design model is a module
MiSE '13: Proceedings of the 5th International Workshop on Modeling in Software EngineeringWe propose a new modularity vision to integrate design modeling with programming. A system consists of not only program code but also design models. However, design models such as UML diagrams have been treated as not modules but complementary ...
An analysis of modularity in aspect oriented design
AOSD '05: Proceedings of the 4th international conference on Aspect-oriented software developmentWe present an analysis of modularity in aspect oriented design using the theory of modular design developed by Baldwin and Clark [10]. We use the three major elements of that theory, namely: i) Design Structure Matrix (DSM), an analysis and modeling ...
Comments
Please enable JavaScript to view thecomments powered by Disqus.Information & Contributors
Information
Published In
April 1998
164 pages
ISBN:0818684399
Copyright © Copyright (c) 1998 Institute of Electrical and Electronics Engineers, Inc. All rights reserved.
Sponsors
Publisher
IEEE Computer Society
United States
Publication History
Published: 16 April 1998
Check for updates
Author Tags
Qualifiers
- Article
Conference
IWSSD98
Sponsor:
Contributors
Other Metrics
Bibliometrics & Citations
Bibliometrics
Article Metrics
- View Citations1Total Citations
- 584Total Downloads
- Downloads (Last 12 months)26
- Downloads (Last 6 weeks)10
Reflects downloads up to 26 Sep 2024
Other Metrics
Citations
Cited By
View all- Nakanishi TSaeki M(1999)Using Multiple Graphs of Programs to Modify SpecificationsProceedings of the Sixth Asia Pacific Software Engineering Conference10.5555/518898.785699Online publication date: 7-Dec-1999
View Options
Get Access
Login options
Check if you have access through your login credentials or your institution to get full access on this article.
Sign in