ACM Home Page
Please provide us with feedback. Feedback
Modeling software architectures in the Unified Modeling Language
Full text PdfPdf (780 KB)
Source ACM Transactions on Software Engineering and Methodology (TOSEM) archive
Volume 11 ,  Issue 1  (January 2002) table of contents
Pages: 2 - 57  
Year of Publication: 2002
ISSN:1049-331X
Authors
Nenad Medvidovic  University of Southern California
David S. Rosenblum  University of California, Irvine
David F. Redmiles  University of California, Irvine
Jason E. Robbins  CollabNet, Inc.
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 76,   Downloads (12 Months): 616,   Citation Count: 31
Additional Information:

abstract   references   cited by   index terms   review   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/504087.504088
What is a DOI?

ABSTRACT

The Unified Modeling Language (UML) is a family of design notations that is rapidly becoming a de facto standard software design language. UML provides a variety of useful capabilities to the software designer, including multiple, interrelated design views, a semiformal semantics expressed as a UML meta model, and an associated language for expressing formal logic constraints on design elements. The primary goal of this work is an assessment of UML's expressive power for modeling software architectures in the manner in which a number of existing software architecture description languages (ADLs) model architectures. This paper presents two strategies for supporting architectural concerns within UML. One strategy involves using UML "as is," while the other incorporates useful features of existing ADLs as UML extensions. We discuss the applicability, strengths, and weaknesses of the two strategies. The strategies are applied on three ADLs that, as a whole, represent a broad cross-section of present-day ADL capabilities. One conclusion of our work is that UML currently lacks support for capturing and exploiting certain architectural concerns whose importance has been demonstrated through the research and practice of software architectures. In particular, UML lacks direct support for modeling and exploiting architectural styles, explicit software connectors, and local and global architectural constraints.


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
ABI-ANTOUN,M.AND MEDVIDOVIC, N. 1999. Enabling the refinement of a software architecture into a design. In Proceedings of the Second International Conference on the Unified Modeling Language (UML'99, Fort Collins, CO). IEEE Computer Society Press, Los Alamitos, CA, 17-31.
 
2
 
3
4
 
5
 
6
7
 
8
EGYED,A.AND MEDVIDOVIC, N. 1999. Extending architectural representation in UML with view integration. In Proceedings of the Second International Conference on the Unified Modeling Language (UML'99, Fort Collins, CO). IEEE Computer Society Press, Los Alamitos, CA, 2-16.
 
9
 
10
 
11
12
13
 
14
GARLAN,D.AND KOMPANEK, A. 2000. Reconciling the needs of architectural description with objectmodeling notations. In Proceedings of the Third International Conference on the Unified Modeling Language (UML 2000, York, UK, October), Springer-Verlag, Berlin, Germany.
 
15
16
 
17
GARLAN,D.AND SHAW, M. 1993. An Introduction to Software Architecture: Advances in Software Engineering and Knowledge Engineering, Vol. I. World Scientific Publishing, Singapore.
 
18
19
 
20
 
21
 
22
 
23
 
24
25
 
26
 
27
28
29
30
31
 
32
MEDVIDOVIC,N.AND ROSENBLUM, D. S. 1997. Domains of concern in software architectures and architecture description languages. In Proceedings of the USENIX Conference on Domain Specific Languages (Santa Barbara, CA, Oct.), Usenix Association, Berkeley, CA, 199-212.
 
33
34
35
 
36
 
37
MEDVIDOVIC, N., TAYLOR,R.N.,AND WHITEHEAD,JR., E. J. 1996. Formal modeling of software architectures at multiple levels of abstraction. In Proceedings of the California Software Symposium 1996 (Los Angeles, CA, Apr.). University of Southern California, Center for Software Engineering and University of California, Irvine, Irvine Research Unit in Software, Los Angels, 28-40.
38
 
39
 
40
OBJECT MANAGEMENT GROUP. 2000. OMG UML Specification Version 1.3. Object Management Group, Needham, MA.
41
 
42
 
43
ROSCOE, A. W. 1998. Two Papers on CSP. Technical monograph PRG-67, Oxford University Computing Laboratory, Oxford, UK.
 
44
 
45
SCATTERGOOD, B. 1998. The Semantics and Implementation of Machine-Readable CSP. Ph.D. dissertation, Oxford University, Oxford, UK.
46
 
47
 
48
SELIC,B.AND RUMBAUGH, J. 1998. Using UML for Modeling Complex Real-Time Systems. ObjectTime white paper, March 11, 1998. Accessed June 2000 at Web site http://www. objectime.com/otl/technical/umlrt.pdf.
 
49
 
50
 
51
SHAW,M.AND GARLAN, D. 1995. Formulations and formalisms in software architecture. In Computer Science Today: Recent Trends and Developments, J. van Leeuwen (Ed.), Lecture Notes in Computer Science, No. 1000. Springer-Verlag, Berlin, Germany, 307-323.
 
52
SHAW, M., GARLAN, D., ALLEN, R., KLEIN, D., OCKERBLOOM, J., SCOTT,C.,AND SCHUMACHER, M. 1995. Candidate model problems in software architecture. Unpublished manuscript. Available from http://www.cs.cmu.edu/afs/cs/project/compose/www/html/ModProb/.
53
 
54
TAYLOR,R.N.,MEDVIDOVIC, N., ANDERSON, K. M., WHITEHEAD,JR., E. J., ROBBINS, J. E., NIES,K.A.,
 
55
 
56
TIGRIS. 2000. Design your UML models with ArgoUML. http://argouml.tigris.org/v08/press-release. html.
57
 
58
VESTAL, S. 1996. MetaH Programmer's Manual, Version 1.09. Technical report, Honeywell Technology Center.
59
 
60
 
61
WOLF, A. L. (Ed.). 1996. Proceedings of the Second International Software Architecture Workshop (ISAW-2, San Francisco, CA, Oct.).

CITED BY  31


REVIEW

"Nancy R. Mead : Reviewer"

This is a very interesting technical paper that examines ways in which Unified Modeling Language (UML) provides support for architectural description languages (ADLs). The authors examine two different approaches: one that attempts to use UML R  more...

Collaborative Colleagues:
Nenad Medvidovic: colleagues
David S. Rosenblum: colleagues
David F. Redmiles: colleagues
Jason E. Robbins: colleagues