0% found this document useful (0 votes)
6 views2 pages

1

this is just sample
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
0% found this document useful (0 votes)
6 views2 pages

1

this is just sample
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

1.

Class Diagrams

 What They Show: Class diagrams are like blueprints for a system. They show different types
of objects (called classes) and how they relate to each other.

 Analogy: Think of a class diagram as the floor plan of a house. It tells you about the rooms
(classes) and how they connect, but it doesn’t show the furniture (actual objects).

2. Object Diagrams

 What They Show: Object diagrams show actual instances of the classes and how they relate
at a specific time.

 Analogy: If the class diagram is the blueprint, the object diagram is a snapshot of the
decorated house at a particular moment.

3. Use Case Diagrams

 What They Show: Use case diagrams illustrate how users (called actors) interact with the
system and what functions they can perform.

 Analogy: Imagine a theater script. The use case diagram shows the actors (users) and the
scenes (functions) they participate in.

4. Interaction Diagrams

 What They Show: Interaction diagrams (which include sequence and collaboration diagrams)
explain how objects communicate with each other over time.

o Sequence Diagrams: Focus on the order of messages exchanged between objects.

o Collaboration Diagrams: Focus on how objects are related and work together.

 Analogy: Picture a group conversation. A sequence diagram shows who talks when, while a
collaboration diagram shows who is in the conversation and their relationships.

5. Statechart Diagrams

 What They Show: Statechart diagrams display different states an object can be in and the
events that trigger changes.

 Analogy: Think of a traffic light. The statechart shows the light being green, yellow, or red,
and how it changes based on time or traffic.

6. Activity Diagrams

 What They Show: Activity diagrams outline the flow of tasks and activities within a system.

 Analogy: Imagine following a recipe. The activity diagram shows each step needed to make a
dish and how they connect.

7. Component Diagrams

 What They Show: Component diagrams show how different parts of a system are organized
and how they depend on each other.

 Analogy: Think of a car. A component diagram shows the various parts (like the engine and
wheels) and how they fit together to make the car function.
8. Deployment Diagrams

 What They Show: Deployment diagrams illustrate where software is installed on hardware
(like servers).

 Analogy: Consider how a concert is set up. A deployment diagram shows where each
musician (software) is positioned on stage (servers) and how the equipment (nodes) is
arranged.

You might also like