The Unified Modeling Language (UML)- part 1

UML is an industry standard modeling language with a rich graphical notation, and comprehensive set of diagrams and elements. A comprehensive UML modeling tool is Enterprise Architect . With UML you can :

  • Build highly detailed UML 2.1 models.
  • Manage project complexity.
  • Reverse engineer legacy code and database schema.
  • Produce great looking reports.
  • Track change.
  • Involve the whole team.

UML 2 defines 13 diagrams:

  • Package diagrams.
  • Class or Structural diagrams.
  • Object diagrams.
  • Composite Structure.
  • Component diagrams.
  • Deployment diagrams.
  • Use Case Diagrams.
  • Activity diagrams.
  • State Machine diagrams.
  • Communication diagrams.
  • Sequence diagrams.
  • Timing diagrams.
  • Interaction Overview diagrams.

We discuss all diagrams below:

Package Diagrams
Package diagrams are used to reflect the organization of packages and their elements. When used to represent class elements, package diagrams provide a visualization of the namespaces. The most common use for package diagrams is to organize use case diagrams and class diagrams, although the use of package diagrams is not limited to these UML elements.

The following is an example of a package diagram.

Elements contained in a package share the same namespace. Therefore, the elements contained in a specific namespace must have unique names.

Packages can be built to represent either physical or logical relationships. When choosing to include classes in specific packages, it is useful to assign the classes with the same inheritance hierarchy to the same package. There is also a strong argument for including classes that are related via composition, and classes that collaborate with them, in the same package.

Packages are represented in UML 2.1 as folders and contain the elements that share a namespace; all elements within a package must be identifiable, and so have a unique name or type. The package must show the package name and can optionally show the elements within the package in extra compartments.

Package Merge
A «merge» connector between two packages defines an implicit generalization between elements in the source package, and elements with the same name in the target package. The source element definitions are expanded to include the element definitions contained in the target. The target element definitions are unaffected, as are the definitions of source package elements that don’t match names with any element in the target package.

Package Import
The «import» connector indicates that the elements within the target package, which in this example is a single class, use unqualified names when being referred to from the source package. The source package’s namespace gains access to the target classes; the target’s namespace is not affected.

Nesting Connectors
The nesting connector between the target package and source packages shows that the source package is fully contained in the target package.

This tutorial is collected from following Source and use as it is: Sparxsystems.com

Advertisements

One Response

  1. […] links >> uml The Big Picture? It’s Not an Oil Painting Saved by jcyrus on Fri 24-10-2008 The Unified Modeling Language (UML)- part 1 Saved by alexandersmit on Thu 23-10-2008 During the first Olympic Games human Fact spain were […]

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: