Alhir Guide to Applying the UML

1. Auflage 2006
ISBN: 978-0-387-21513-6
Verlag: Springer US
Format: PDF
Kopierschutz: 1 - PDF Watermark

E-Book, Englisch, 431 Seiten, eBook

Reihe: Springer Professional Computing

Guide to Successfully Applying the UML offers a tool-independent and process-independent roadmap for successfully applying the Unified Modeling Language (UML). The UML is a modeling language for specifying, visualizing, constructing, and documenting the artifacts of a system-intensive process. It was originally conceived by Rational Software Corporation and three of the most prominent methodologists in the information systems and technology industry: Grady Booch, James Rumbaugh, and Ivar Jacobson. The language has gained significant industry support from various organizations via the UML Partners Consortium and has been submitted to and approved by the Object Management Group as a standard. This book works in concordance with references to offer a suite of practical real-world examples to help novice and expert users of the UML to understand the whole language (holistically and cohesively), including rules of usage and principles of composition, style guidelines, and a roadmap for successfully applying the UML. The examples are presented in a "fairly intuitive/evolutionary" manner that demonstrate the key concepts of the UML and help readers explore the wide range of uses of the UML.

Zielgruppe

Professional/practitioner

Autoren/Hrsg.

Alhir, Sinan Si

Inhaltsverzeichnis

to the Unified Modeling Language (UML).- Modeling.- Object Orientation.- The Roadmap.- Use-Case (User) Modeling.- Structural (Static) Modeling.- Behavioral (Dynamic) Modeling.- Component (Implementation) Modeling.- Deployment (Environment) Modeling.- Extension Mechanisms.- The Object Constraint Language (OCL).

Leseproben

CHAPTER 6 Structural (Static) Modeling (p.212)
This chapter provides essential rules, principles, and style guidelines for composing UML structural or static models within the context of the roadmap, including class and object diagrams and their elements. Structural modeling is concerned with modeling the structural or static dimension of a system - the elements and their relationships that constitute a system - and is used for system, subsystem, and class speci.cation within the roadmap to capture in a speci.cation model how the construct will satisfy its requirements. Structural modeling is also used to determine which elements and their relationships collaborate to constitute the construct, and how these elements interact to provide functionality to end users. A speci.cation model consists of class, object, sequence, collaboration, state, and activity diagrams and their model elements. Our goal, in this chapter, is to gain more depth in understanding the UML notation and the roadmap concerning the structural or static aspect of speci.cation models.


6.1. Class Diagrams

A class diagram depicts the static structure of an entity using classi.ers and relationships. An entity is a classiffer, for example, a system, subsystem, or class.
6.1.1. CLASSIFIERS
A classiffer is a concept that de.nes structural features and behavioral features, and has various types of relationships. A feature is a property encapsulated within a model element, an atomic constituent of a model. Structural features de.ne the static features of a model element. Behav ioral features de.ne the dynamic features of a model element. A classiffer may contain other classiffers. It owns its contents and de.nes a namespace, a part of a model in which a name may be uniquely de.ned and used. An element may access any contents of its own namespace or a containing namespace. Specific types of classi.ers include classes, actors, use cases, data types, interfaces, components, nodes, subsystems, and artifacts.

A classiffer is depicted as a vertex or node, including an icon or twodimensional symbol that may contain other elements. Other information is depicted as strings or sequences of characters attached to nodes. A classi.er is named using an optional stereotype or list of stereotypes followed by an optional visibility symbol followed by the classiffer name string followed by an optional property. Not all details of a modeling element need to be depicted on a diagram, only those that are relevant to the purpose of the diagram.

A stereotype is used to classify (brand) or mark a model element so that it may be given a speci.c meaning. A stereotype is depicted as a text string keyword enclosed in guillemets («») or double-angle brackets preceding or above the name of the element. Multiple stereotypes may be applied to an elements depicted vertically one below the other or preceding each other. A user-de.ned icon may be used to signify a stereotype. The guillemets and the stereotype icon may be depicted simultaneously; however only one is required. The icon is placed in the upper right corner near the name of the element, or the entire base model element symbol is collapsed into an icon containing the element name or with the name above or below the icon, and other information contained by the base model element symbol is suppressed. When multiple stereotypes are used for an element, the icons are omitted.