Scribd
Upload
19 views2 pages

UML_Symbols_Case_Study

This case study explores the various symbols used in Unified Modeling Language (UML) for system modeling, including Use Case, Class, Sequence, and Activity diagrams. Each diagram serves a specific purpose, depicting functionalities, structure, interactions, and workflows of a system. Understanding these symbols enables software engineers to effectively visualize and design system architectures.

Uploaded by

kalkihimanshu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
19 views2 pages

UML_Symbols_Case_Study

This case study explores the various symbols used in Unified Modeling Language (UML) for system modeling, including Use Case, Class, Sequence, and Activity diagrams. Each diagram serves a specific purpose, depicting functionalities, structure, interactions, and workflows of a system. Understanding these symbols enables software engineers to effectively visualize and design system architectures.

Uploaded by

kalkihimanshu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Case Study: Different Symbols of UML and Their Usage

Introduction
Unified Modeling Language (UML) is a standard modeling language used in software
engineering to visualize and design system architectures. Various symbols in UML represent
different components of a system. This case study explores different UML symbols and their
significance in system modeling.

1. UML Use Case Diagram Symbols

Purpose:
Use Case Diagrams depict system functionalities and user interactions.

Symbols and Their Meaning:


• Actor (Stick Figure): Represents a user or external system interacting with the system.

• Use Case (Oval): Represents a specific functionality or process in the system.

• Association (Line): Shows the relationship between actors and use cases.

• Include (Dashed Arrow with <<include>>): Represents a mandatory dependency between


use cases.

• Extend (Dashed Arrow with <<extend>>): Represents an optional extension of a base use
case.

2. UML Class Diagram Symbols

Purpose:
Class Diagrams show the structure of a system, including classes, attributes, and
relationships.

Symbols and Their Meaning:


• Class (Rectangle with Three Sections): Represents a class with name, attributes, and
methods.

• Association (Line): Connects classes that have a relationship.

• Generalization (Arrow with Empty Triangle): Represents inheritance.

• Composition (Filled Diamond with Line): Represents a strong relationship where the
contained object cannot exist without the container.

• Aggregation (Empty Diamond with Line): Represents a weak relationship where the
contained object can exist independently.
3. UML Sequence Diagram Symbols

Purpose:
Sequence Diagrams model interactions between objects over time.

Symbols and Their Meaning:


• Lifeline (Dashed Vertical Line): Represents an object's existence during the interaction.

• Activation Box (Thin Rectangle on Lifeline): Shows when an object is active.

• Message (Arrow): Represents communication between objects.

• Return Message (Dashed Arrow): Shows the return of a response.

• Self-Message (Looped Arrow): Represents a recursive call.

4. UML Activity Diagram Symbols

Purpose:
Activity Diagrams illustrate workflows or business processes.

Symbols and Their Meaning:


• Start Node (Black Circle): Represents the beginning of a process.

• Action (Rounded Rectangle): Represents a step in the process.

• Decision (Diamond): Represents a conditional branch.

• Merge Node (Diamond): Merges multiple paths into one.

• End Node (Black Circle with Outline): Represents the termination of the process.

Conclusion
UML symbols provide a standardized way to model and visualize system components and
workflows. By using different UML diagrams, software engineers can design efficient and
structured systems.

You might also like