Practical 1

Aim: Draw the structural view diagram for the system: Class Diagram, Object Diagram
Class Diagram
Description:

A Class Diagram is a type of static structure diagram in UML (Unified Modeling Language) that
describes the structure of a system by representing its classes, their attributes, methods, and the
relationships among objects. It is one of the most commonly used diagrams to model the design of an
object-oriented system.
1. Classes:
Represent the blueprint of objects in the system. A class is shown as a rectangle with three
sections:
o Top Section: The class name.
o Middle Section: The attributes (fields) of the class.
o Bottom Section: The methods (functions or operations) of the class.
2. Attributes:
Variables that store the data for an object of the class. They are listed in the middle section of the
class box. Each attribute has:
o Visibility: Determines whether the attribute is public (+), private (-), protected (#), or package (~).
o Name: The name of the attribute.
o Type: The data type of the attribute (e.g., int, String).
o Default Value (optional): The initial value of the attribute.
3. Methods:
Functions or operations that define the behavior of the class. They are listed in the bottom section
of the class box. Each method has:
o Visibility: Similar to attributes, it determines if the method is public, private, etc.
o Name: The name of the method.
o Parameters (optional): The parameters that the method takes.
o Return Type: The type of value that the method returns.
4. Relationships:
o Association: A relationship between two classes, usually represented by a line connecting them.
An arrow can indicate the direction of the relationship, and multiplicity (e.g., 1..*, 0..1) shows how
many instances of one class can be associated with instances of the other class.
o Inheritance (Generalization): A relationship where a subclass inherits from a superclass. It’s
represented by a solid line with a closed arrow pointing from the subclass to the superclass.
o Aggregation: A type of association where one class is a part of another, but both can exist
independently. It is shown by a hollow diamond at the end of the line pointing to the "whole" class.
o Composition: A stronger form of aggregation where the part cannot exist without the whole. It is
represented by a filled diamond at the end of the line.
o Dependency: A relationship where one class depends on another, shown by a dashed arrow
pointing from the dependent class to the class it depends on.
o Realization: Often used in interfaces, this relationship indicates that a class provides an
implementation for an interface. It’s represented by a dashed line with a hollow triangle arrow
pointing to the interface.
Diagram:

Object Diagram
Description:
An object diagram is a type of UML (Unified Modeling Language) diagram that shows instances of
classes, which are referred to as objects. It captures the static structure of a system at a particular point in
time by illustrating the objects (instances of classes) and their relationships. Object diagrams can be
considered as snapshots of class diagrams, but they focus on the specific state of the system rather than its
structure.
1. Objects (Instances): Represent specific instances of classes. Objects are shown with the format objectName
: ClassName, where the object name is underlined.
2. Links: These represent relationships between objects. A link is similar to an association in a class diagram
but denotes a particular instance of the relationship between two objects.
3. Attributes: The attributes of an object are shown with their current values, like attributeName = value.
Purpose:
 Representation of Object States: It shows the state of objects at a certain moment.
 Clarification of Class Diagram: Helps clarify the structure and relationships shown in a class diagram by
providing real instances and their values.
 Modeling of Real-Time Scenarios: Object diagrams are often used in system simulations or to show
specific examples of object interactions at certain points in time.
When to Use:
 Debugging: To visualize the objects and their relationships at runtime.
 Testing: To model various states of a system for test cases.
  Real-world Examples: To showcase real-life examples of how a system behaves with actual object
instances.
Diagram:
 Practical 2
Aim: Draw the user’s view analysis for the system: Use Case Diagram
Description:
A use case diagram is a type of UML (Unified Modeling Language) diagram that shows the interactions between
users (also known as actors) and a system. It provides a high-level overview of the system's functionality and
describes the major use cases or scenarios that the system supports.
Here's a breakdown of its components:
1. Actors: These are the external entities (users or systems) that interact with the system. They can be
primary actors (who initiate a use case) or secondary actors (who provide services or support to the
system).
2. Use Cases: These are the functions or processes that the system performs in response to an actor's request.
They represent the interaction between the actor and the system.
3. System Boundary: This is a rectangle that defines the system's scope, indicating what is part of the system
and what is external.
4. Associations: These are lines that connect actors to use cases, indicating which actors are involved with
which use cases.
5. Relationships:
o Include: A relationship where one use case always includes the behavior of another use case.
o Extend: A relationship where one use case optionally extends another.
o Generalization: A relationship where an actor or use case can inherit behavior from a more general
actor or use case.
Diagram:
 Practical 3
Aim: Draw the diagram to implement ER Diagram.
Description:

Diagram:

Practical 4
Aim: Draw the behavioral view diagram for the suggested system: Sequence Diagram
Description:

Diagram:

Practical 5
Aim: Draw the behavioral view diagram: State-Chart Diagram
Description:

Diagram:

Practical 6
Aim: Draw the function oriented diagram: Data Flow Chart
Description:

Diagram:

Practical 7
Aim: Draw the behavioral view diagram for the suggested system: Collaboration
Description:

Diagram:

Practical 8
Aim: Draw the behavioral view diagram: Activity Diagram
Description:

Diagram:

Practical 9
Aim: Draw the implementation and environmental view diagram: Component Diagram
Description:

Diagram:

Practical 10
Aim: Draw the implementation and environmental view diagram: Deployment Diagram
Description:

Diagram:
1. Class Diagram , Object Diagram
2. Use Case
3. ER Diagram
4. Sequence Diagram
5. State Chart Diagram
6. Data Flow Diagram
7. Collaboration
8. Activity
9. Component
10. Deployment