Using the UML for Architectural Description?

Keywords Using the UML for Architectural Description? IEEE P1471 architectural description multiple views viewpoints Uni ed Modeling Language
Standards groups

The central abstraction, and primary focus, of the standard is Architectural
Description. In P1471, an Architectural Description is a collection of products
to document the architecture of a system. P1471 does not specify the format
or media for an architectural description. What P1471 does specify is certain
minimal required content of an AD re ecting current practices and industry
consensus.

A key tenet of that consensus is the notion of multiple views. In P1471, an
Architectural Description is organized into one or more architectural Views. Most
architectural methods and frameworks advocate the use of one or more views of
the system as a part of the architectural description. However, the exact views
used vary from technique to technique. Rather than require a particular set of
views, P1471 leaves this selection to users of the standard.

One of P1471's contributions is to make explicit the notion of an architectural
Viewpoint to embody the rules governing a view. It is anticipated that this
will allow the denition and reuse of viewpoints, so that varying approaches to
architecture may better be able to exchange results, and that in general the
growth of the discipline will be facilitated by codifying certain useful patterns
of description.

Metadata
Date published
UNKNOWN
Document type
technical white paper
Pages
17
Defines standard
Replaced/Superseded by document(s)
Cancelled by
Amended by
File MIME type Size (KB) Language Download
Paper-hilliard99a-using-uml-for-AD.pdf application/pdf   229.33 KB English DOWNLOAD!
File attachments
Abstract

Abstract. There is much interest in using the Unied Modeling Language (UML) for architectural description { those techniques by which architects sketch, capture, model, document and analyze architectural knowledge and decisions about software-intensive systems. IEEE P1471, the Recommended Practice for Architectural Description, represents an emerging consensus for specifying the content of an architectural description for a software-intensive system. Like the UML, IEEE P1471 does not prescribe a particular architectural method or life cycle, but may be used within a variety of such processes. In this paper, I provide an overview of IEEE P1471, describe its conceptual framework, and investigate the issues of applying the UML to meet the requirements of IEEE P1471.

Visit also