UML+ROOM as a standard ADL?

Designing a software system's architecture properly is one of the most important tasks of any software engineering project. Nevertheless there exists no common definition of the term "software architecture" and no standard software architecture description language (ADL). The paper discusses whether the standard OO modeling language UML is a standard ADL, explains some deficiencies if used for this purpose, and makes a proposal of how to eliminate these deficiencies. The proposal is based on the widely accepted idea that elements of the component based OO modeling language, ROOM, should be integrated with UML. It explains why the idea of merging static structure diagrams of ROOM with behaviour-describing collaboration diagrams of UML is not sufficient and presents an additional approach for the integration problem.

[1]  William E. Lorensen,et al.  Object-Oriented Modeling and Design , 1991, TOOLS.

[2]  Richard N. Taylor,et al.  A Classification and Comparison Framework for Software Architecture Description Languages , 2000, IEEE Trans. Software Eng..

[3]  Ivar Jacobson,et al.  The Unified Modeling Language User Guide , 1998, J. Database Manag..

[4]  Bernhard Rumpe,et al.  The UML as a formal modeling notation , 1998, Comput. Stand. Interfaces.

[5]  Bran Selic,et al.  Real-time object-oriented modeling , 1994, Wiley professional computing.

[6]  Bran Selic,et al.  Using UML for Modeling Complex Real-Time Systems , 1998, LCTES.

[7]  Matthias Radestock,et al.  Formalising system structure , 1996, Proceedings of the 8th International Workshop on Software Specification and Design.

[8]  Paul Clements,et al.  Software architecture in practice , 1999, SEI series in software engineering.

[9]  Nenad Medvidovic,et al.  Integrating architecture description languages with a standard design method , 1998, Proceedings of the 20th International Conference on Software Engineering.

[10]  Ted G. Lewis,et al.  Visual Object-Oriented Programming: Concepts and Environments , 1995 .

[11]  Susan Eisenbach,et al.  Formalizing System Structure , 1996 .

[12]  Hartmut Ehrig,et al.  Fundamentals of Algebraic Specification 1: Equations and Initial Semantics , 1985 .

[13]  Bernhard Rumpe,et al.  Refinement of information flow architectures , 1997, First IEEE International Conference on Formal Engineering Methods.

[14]  Manfred Nagl.  Softwaretechnik - methodisches Programmieren im Großen , 1990, Springer Compass.

[15]  David Harel,et al.  Statecharts: A Visual Formalism for Complex Systems , 1987, Sci. Comput. Program..

[16]  Jos Warmer,et al.  The object constraint language , 1998 .

[17]  Bernhard Rumpe,et al.  Towards a Formalization of the Unified Modeling Language , 1997, ECOOP.

[18]  David C. Luckham,et al.  An Event-Based Architecture Definition Language , 1995, IEEE Trans. Software Eng..

[19]  Mary Shaw,et al.  Software architecture - perspectives on an emerging discipline , 1996 .

[20]  Anthony Finkelstein,et al.  A constructive approach to the design of distributed systems , 1990, Proceedings.,10th International Conference on Distributed Computing Systems.

[21]  Hartmut Ehrig,et al.  Fundamentals of Algebraic Specification 1 , 1985, EATCS Monographs on Theoretical Computer Science.

[22]  Bernhard Rumpe,et al.  Towards a Formalization of theUni ed Modeling Language ? , 1997 .

[23]  Ivar Jacobson,et al.  The unified modeling language reference manual , 2010 .

[24]  David Garlan,et al.  A formal basis for architectural connection , 1997, TSEM.

[25]  강문설.  [서평]「The Unified Modeling Language User Guide」 , 1999 .

[26]  Desmond D'Souza,et al.  Objects, Components, and Frameworks with UML: The Catalysis Approach , 1998 .