Modeling enterprise software architectures using UML

The distributed enterprise systems encountered in domains such as finance, telecommunications, health, and aerospace tend to be large, complex and resource intensive. It is crucial that these systems are designed with robust and resilient software architectures that are efficient to construct and flexible to change. This paper describes the requirements of enterprise software architectures and examines the Unified Modeling Language (UML) constructs and techniques that specify them. These constructs, derived from field-proven methods such as Objectory, Booch, OMT, RSEB and the Unified Software Development Process, can be used to specify various enterprise architecture structures and behavior. It explains how UML can be used to model architectural views, and discusses the role of process in architectural modeling. After summarizing outstanding issues, the discussion concludes with recommendations to refine and extend UML to provide better support for architectural modeling.

[1]  Philippe Kruchten,et al.  The 4+1 View Model of Architecture , 1995, IEEE Softw..

[2]  Ivar Jacobson,et al.  Object-oriented software engineering - a use case driven approach , 1993, TOOLS.

[3]  Mary Shaw,et al.  Software architecture: the next step for object technology (panel) , 1993, OOPSLA '93.

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

[5]  R. J. A. Buhr,et al.  Use Case Maps for Object-Oriented Systems , 1995 .

[6]  Ivar Jacobson,et al.  Software Reuse: Architecture, Process And Organization For Business Success , 1998, Proceedings. Technology of Object-Oriented Languages. TOOLS 26 (Cat. No.98EX176).

[7]  Zoran Milosevic,et al.  Enterprise modelling and QoS for command and control systems , 1998, Proceedings Second International Enterprise Distributed Object Computing (Cat. No.98EX244).

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

[9]  G. G. Stokes.  "J." , 1890, The New Yale Book of Quotations.

[10]  Richard N. Taylor,et al.  A framework for classifying and comparing architecture description languages , 1997, ESEC '97/FSE-5.

[11]  David Garlan,et al.  Formal Connectors , 1994 .

[12]  Grady Booch,et al.  Object-oriented analysis and design with applications (2nd ed.) , 1993 .

[13]  Ivar Jacobson,et al.  The Unified Software Development Process , 1999 .

[14]  Richard N. Taylor,et al.  Formal Modeling of Software Architectures at Multiple Levels of Abstraction , 1996 .