Summary of Models Supported By Uml

Posted by admin on July 3, 2009 under Software Architect | Be the First to Comment

The following UML diagrams provide multiple viewpoints of the system under development.

Use Case Diagrams

• Use case defines the scenarios in which the system is used. The inputs and possible outcomes of the system
• Analyst uses use case diagram to represent possible usages of the application
• We can also see the relationships among the use cases and understand the application functionalities.
• How external entities interact with the application could also be seen here.

Class Diagrams

• Describes one structure aspect of the application.
• Represents possible classes and their relationships.
• Reveals the attributes and their types, methods and their signatures.

Behavior Diagrams

• Explains behavioral aspects of the applications.

Statechart Diagram

• Models the behavior of large, complex systems. UML statecharts are based on David Harel’s statecharts.

Interaction Diagrams

are of two types.

1. Sequence Diagrams – Record design decisions by examining the interaction between objects in the application in a timely, ordered manner
2. Collaboration Diagrams – Show how objects interact and send messages to each other. Concurrent threads of execution can also be represented

Implementation Diagrams

• Capture the runtime view of the application.

Component Diagram

• Shows the application components and how they interact.

Deployment Diagram

• Shows the system’s physical architecture in terms of nodes and their relationships.

Reference: Pattern-Oriented Analysis and Design: Composing Patterns to Design Software Systems By Sherif M. Yacoub [ISBN=0201776405], Addison Wesley