s You are here: Home > Product > UMP Toolkit contents > Visio templates
UMP slogan Home | About UMP | FAQ | Discuss | Contacts | Site map
  Life cycle model   Development process   Support process   Organizational process   Product    
Contents | Download




References:

UMP glossary
Bibliography
Conventions & Notation

Visio stencils to support UMP

Unified Modeling Language

UML notation according the UML Specification Version 1.5, March 2003.

Stencil Description
UML Static Structure diagram
UML Static Structure diagram - Visio stencil Static structure model elements are used to describe the system structure. According to the defined UML profile for the project, the models could be of different types. These models are presented using variations of the Class diagrams.

Class diagrams show the static structure of the model, in particular, the things that exist (such as classes and types), their internal structure, and their relationships to other things.

Class diagrams do not show temporal information, although they may contain reified occurrences of things that have or things that describe temporal behavior.

An object diagram shows instances compatible with a particular class diagram.


Download stencil (Zip file 0.04Mb).
UML Use Case diagram
UML Use Case diagram - Visio stencil Use case diagrams show actors and use cases, as well as their relationships. The use cases represent functionality of a system or a classifier, like a subsystem or a class, as manifested to external interactors with the system or the classifier.

Download stencil (Zip file 0.02Mb).
UML Collaboration diagram
UML Collaboration diagram - Visio stencil Collaboration is a static construct which is used to model the behavior of the system. A Collaboration describes realization of an Operation or a Classifier. A Collaboration may be attached to an Operation or a Classifier, like a UseCase, to describe the context in which their behavior occurs.

Behavior is implemented by ensembles of Instances that exchange Stimuli within an overall interaction to accomplish a task.

An Interaction is defined in the context of a Collaboration. It specifies the communication patterns between the roles in the Collaboration. The Interactions defined within the Collaboration specify the communication pattern between the Instances when they perform the behavior specified in the Operation or the UseCase.

Download stencil (Zip file 0.02Mb).
UML Sequence diagram
UML Sequence Diagram - Visio stencil A sequence diagram presents an Interaction, which is a set of Messages between Classifier Roles within a Collaboration, or an InteractionInstanceSet, which is a set of Stimuli between Instances within a CollaborationInstanceSet to effect a desired operation or result.

Download stencil (Zip file 0.02Mb).
UML Statechart diagram stencil
UML Satechart - Visio stencil Statechart diagrams represent dynamic behavior of entities by specifying their responses to the receipt of event instances. Typically, they are used for describing behavior of class instances, but statecharts may also describe behavior of other entities such as use-cases, actors, subsystems, operations, or methods.

Download stencil (Zip file 0.02Mb)
UML Activity diagram
UML Actvity Diagram - Visio stencil An activity graph is a variation of the state machine in which states represent performance of actions or subactivities and the transitions are triggered by completion of the actions or subactivities.

The entire activity diagram is attached (through the model) to a classifier, such as a use case, or to a package, or to the implementation of an operation. The purpose of this diagram is to focus on flows driven by internal processing (as opposed to external events). Activity diagrams should be used in situations where all or most of the events represent the completion of internally-generated actions (that is, procedural flow of
control). Use ordinary state diagrams in situations where asynchronous events occur.

Download stencil (Zip file 0.03Mb)
UML Implementation diagram
UML Implementation diagram - Visio stencil Implementation diagrams show aspects of physical implementation, including the structure of components and the run-time deployment system. They come in two forms:

1) component diagrams show the structure of components, including the classifiers that specify them, and the artifacts that implement them; and

2) deployment diagrams show the structure of the nodes on which the components are deployed.

These diagrams can also be applied in a broader way to business modeling where the components represent business procedures and artifacts, and the deployment nodes represent the organization units and resources (human and otherwise) of the business.

Download stencil (Zip file 0.01Mb)

 

Structured Analysis and Design (SAD)

For description of the SAD notation used here please refer to E.Yourdon's "Modern Structured Analysis" book.

Stencil Description
SAD Dataflow diagram
Structured Analysis Dataflow diagram - Visio stencil Dataflow diagram is a model, which provides function-oriented view of a system.

Download stencil (Zip file 0.02Mb)
SAD Structure Chart
Structured Design Structure Chart - Visio stencil Structure chart shows the hierarchical organization of modules within one task.

Download stencil (Zip file 0.02Mb)

 

UMP additional stencils

Stencil Description
Entity-Relationship diagram
Entity-Relationship diagram - Visio stencil Entity-Relationships (ER) diagrams are used to produce a graphical information model which represents the structure and semantics of information within an environment or system. The ER diagrams permit the construction of semantic data models to build databases.

Stencil is designed according notation defined in Integration Definition for Information Modeling (IDEF1X) standard (Federal Information Processing Standards Publication 184), issued by the National Institute of Standards and Technology 1993 December 21.

Download stencil (Zip file 0.01Mb)
User Interface diagram
UMP user interface diagram - Visio stencil User interface diagram presents the user's external view on the system. Use this type of diagram to mockup the system's view to specify the requirements with the project participants, especially with the end users.

The User interface diagram concentrates on the content of the input / output forms rather than the graphics design and branding of the interface. For the last user interface builders and graphics tools shall be used instead.

Download stencil (Zip file 0.01Mb)

 

 

Last modified: 07-Jan-2005
Copyright © 2003—2005 Alexander Kozlinski. All rights reserved.
Use of this website signifies your agreement to the Terms of Use