A standard for architecture description

IBM Systems Journal

Volumn 38, Issue 1, 1999, Pages 32-50

  Youngs, R ^a,b   Redmond Pyle, D ^b,c,d   Spaas, P ^a,b   Kahan, E ^e,f,g  

^a IBM   (United Kingdom)

^b IBM United Kingdom Object Technology Practice   (United Kingdom)

^c Sunny Croft   (United Kingdom)

^d PostModern Solutions   (United Kingdom)

^e IBM   (United States)

^f National Systems Integration Application Development

^g ESS ^*

Author keywords

[No Author keywords available]

Indexed keywords

INFORMATION SERVICES; INFORMATION TECHNOLOGY; STANDARDS; TERMINOLOGY;

ARCHITECTURE DESCRIPTION STANDARDS (ADS);

COMPUTER ARCHITECTURE;

EID: 0032678706     PISSN: 00188670     EISSN: None     Source Type: Journal    
DOI: 10.1147/sj.381.0032     Document Type: Article

References (8)

1. L. Bass, P. Clements, and R. Kazman, Software Architecture in Practice, Addison-Wesley Publishing Co., Reading, MA (1998).
2. In this context, infrastructure consists of those components (usually, but not exclusively, application-independent services) that may be used by many applications.
3. The Object Management Group, http://www.omg.org/. The UML notation and semantics guides are available from this site.
4. M. Fowler, K. Scott, and G. Booch, UML Distilled: Applying the Standard Object Modeling Language, Addison-Wesley Publishing Co., Reading, MA (1997).
5. Although the majority of components will be software, it is sometimes necessary to model hardware as components. This will generally be the case if software components use specialized hardware interfaces directly (for example, an encryption device, a pager, or an interactive voice response unit).
6. E. Gamma, R. Helm, R. Johnson, and J. Vlissides, Design Patterns: Elements of Reusable Object-Oriented Software, Addison-Wesley Publishing Co., Reading, MA (1995).
7. The Workflow Management Coalition is a nonprofit, international organization of workflow vendors, users, analysts, and university or research groups. Its mission is to promote and develop the use of workflow through the establishment of standards for software terminology, interoperability, and connectivity among workflow products. See http:/www.aiim.org/wfmc/ for more information.
8. It is expected that these elaboration points will be identified in a later version.