Basic Structural Modeling

Basic Structural Modeling (continued)

C. Common Mechanisms

Terms and Concepts

Notes

A note is a graphical symbol for rendering constraints or comments attached to an element or a collection of elements.

Named compartment

Stereotype

A stereotype is an extension of the vocabulary of the UML, to allow creating new kinds of building blocks.

Tagged Values

A tagged value is en extension of the properties of a UML element to allow creating new information in the specification of that element.

A tagged value is metadata.

Constraints

A constraint is an extension of the semantics of a UML element to allow adding or modifying rules.

Common Modeling Techniques

Modeling Comments

Put a comment in a note and link the note to the corresponding

element using dependency.

Make a note visible or invisible
Embed external document in a note.

Modeling New Building Block with Standard Blocks and Stereotypes

Modeling New Properties for a UML element

Using stereotypes, and tagged values

Modeling New Semantics for a UML element using constraints

D. UML Diagrams

Terms and Concepts

Structural Diagrams

Class diagram shows classes, interfaces, and their collaboration relationships

For illustrating the static design view of a system.

Object diagram shows a set of objects and their relationships.

For illustrating data structures, the static snapshots of class instances.

Component Diagram shows a set of components and their relationships.

For illustrating the static implementation view of a system

Deployment diagram shows a set of nodes and their relationships.

For illustrating the static deployment view of an architecture.

Behavioral Diagrams

Use case diagram shows a set of use cases and actors and their relationships.

For illustrating the static use case view of a system.

Sequence diagram shows a set of objects and messages sent and received by those objects, with emphasis on the time ordering of messages.

For illustrating the dynamic view of a system

Collaboration diagram shows a set of objects that send and receive messages, with emphasis on the structural organization of the collaboration objects.

For illustrating the dynamic view of a system

Statechart diagram shows a state machine of a class, consisting of states, transitions, and activities, with emphasis on the event-ordered behavior of an object.

For illustrating the dynamic view of a system

Activity diagram shows the flow from activity to activity within a system.

For illustrating the dynamic view of a system

Common Modeling Techniques

Modeling Different Views of a System

Views

Use case view:

The use of use cases that describe the behavior of the system as seen by its end users, analysts, and testers.

Design View:

The classes, interfaces, and collaborations that form the vocabulary of the problem and its solution.

Supporting the functional requirements of the system.

Process View:

The threads and processes that form the concurrency and synchronization of the system.

Addressing the performance, scalability, and throughput of the system.

Implementation View:

The components and files that are used to assemble and release the physical system

Addressing the configuration of the system.

Deployment View:

The nodes that form the hardware topology of the system on which the system executes

Addressing the distribution, delivery, and installation of parts that make up the physical system.

Modeling the views using UML diagrams

Use case view:

Use case diagrams, interaction diagrams, activity diagrams

Design view:

Class diagrams, interaction diagrams, statechart diagrams

Process view:

Class diagrams (with active classes), interaction diagrams

Implementation view:

Component diagrams

Deployment view

Deployment diagram

Simple monolithic application

Use case view, design view

Client/server systems

Use case view, design view, component view, deployment view

Modeling Different Levels of Abstraction

Presenting diagrams with different levels of detail in a single model

Creating models at different levels of abstraction

E. Class Diagrams

Terms and Concepts

Contents of class diagrams

Classes
Interfaces
Collaborations
Dependency, Generalization, and association relationships

Notes
Constraints

Packages
Subsystems

Common Modeling Techniques

Modeling Simple Collaborations

Identify the mechanism to be modeled

Mechanism represents some function or behavior of the part of the system from interaction of classes, interfaces, and others.

For each mechanism, identify the participating classes, interfaces, and others.
Use scenarios to walk through these things to discover missing and wrong.

Modeling a Logical Database Schema

Identify those classes whose state must transcend the lifetime of their applications.
Create a class diagram that contains these classes and mark them as persistent (a standard tagged value)
Specify the details of their attributes, associations, and cardinalities.
Use intermediate abstractions to solve cyclic, one-to-one, and n-ary associations.
Expanding operations for data access and data integrity. (No business rules in this layer)

Forward and Reverse Engineering

Forward engineering

The process of transforming a model into code through a mapping to an implementation language.

Result in a loss of information (structural and behavioral features)

Forward engineering a class diagram:

Identify the rules for mapping to the implementation language
Constrain the use of certain UML features because of language limitation
Use tagged values to specify the target language
Use a tool to forward engineer the model.

Reverse engineering

The process of transforming code into a model through a mapping from the implementation language.

Result in a flood of low-level information.