0% found this document useful (0 votes)
21 views

SE-Unit-4

Uploaded by

vinaydodiya22
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
21 views

SE-Unit-4

Uploaded by

vinaydodiya22
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 15

Unit – 4 UML

What is Uml
● Uml Stands for unified modeling language .
● It was created by the Object Management Group (OMG) and first proposed
in 1997.
● UML is a standard language for specifying, visualizing, constructing, and
documenting the artifacts of software systems.
● UML is different from the other common programming languages such as
C++, Java, COBOL, etc.
● UML is a pictorial language used to make software blueprints.
Goal of UML
● The main goal of UML is to create a general-purpose modeling language
that is easy for all users to understand.
● UML diagrams are useful for developers, business users, and anyone
interested in understanding a system, whether software or non-software.
● With the help of uml you can better understand the software system and
its functionality.
Conceptual Model of UML
● A conceptual model is a simple representation of concepts and how they
are related.
● It is the first step before creating a UML diagram, helping to understand
real-world entities and their interactions.
● To master UML's conceptual model, focus on three main elements.
1. UML building blocks
2. Rules for connecting these blocks
3. Common features used in UML
UML Building Blocks
a.)Things
1.)Structural Things
- Class
- Interface
- Collaboration
- Use-Case
- Component
- Node
2.) Behavioral Things
- Interaction
- State Machine
3.) Grouping Things
- Package
4.) Annotational things
- Note
b.) Relationship
- Dependency
- Association
- Generalization
- Realization

c.) UML Diagrams


1. Structural things.

Structural things define the static part of the model. They represent the physical and
conceptual elements. Following are the brief descriptions of the structural things.

:- Class − Class represents a set of objects having similar responsibilities.

:- Interface − Interface defines a set of operations, which specify the functionality of a


class.

:- Collaboration −Collaboration defines an interaction between elements.


:- Use case −Use case represents a set of actions performed by a system for a specific
user.

:- Component −Component describes the different part of a system.

:- Node − A node can be defined as a physical element that exists at run time.
- it represent the physical part such as server, network etc.
2. Behavioral Things
A behavioral thing consists of the dynamic parts of UML models. Following are the
behavioral things −

:- Interaction − Interaction is defined as a behavior that consists of a group of messages


exchanged among elements to accomplish a specific task.

:- State machine − It provides a different phase of life cycle of different elements..


3. Grouping Things
Grouping things can be defined as a mechanism to group elements of a UML model
together. There is only one grouping thing available −

Package − Package is the only one grouping thing which use to gather both structural
and behavioral things in one package.

4. Annotational Things
The Annotational thing contains only one point is called as “Note”. The note contains
comments, constraints, and methods which used in particular module.
2. Relationships.
In UML (Unified Modeling Language) relationships are most important part of uml building
blocks, relationships show how different parts of a system are connected and work
together.

Dependency
This is a one-way relationship, meaning one element depended on another to work. It’s
called a "supplier-client" relationship because the supplier provides something that the
client needs. If the supplier changes it, it could affect the client. Dependency can happen
between many types of elements like classes, interfaces, components, etc
Association
Association is used to represent the relationship between two elements of system. It also
describe how many elements are tacking part in that relationship.

Generalization.
This is similar to inheritance in programming. A base (or parent) class has certain
properties or functions, and a new class (child) inherits these. The child class can use or
change what it inherited from the base class. It's also called an "is-a" relationship
because the child class is a type of the base class. For example, if "Animal" is the base
class, "Dog" is a child class because a dog is a kind of animal.
Realization.
Realization can be defined as a relationship in which two elements are connected. One
element describes some functionality , which is not implemented and the other one
implements them. This usually happens between an interface and the class that
implements it.
UML Diagram
UML Diagram

Structure-Diagram Behavior-diagram

Object- Activity-
Use-Case
Class-Diagram Diagram Diagram
Diagram

Component- Interaction-Diagram
Deployment- State-Machine
Diagram
Diagram Diagram
Structural diagrams
● Structural diagrams in UML (Unified Modeling Language) represent the static
structure of a system.
● They represent the components of the system and their relationships.
● Structural diagrams are used to visualize the organization, composition, and
relationships between the different elements in a system.

Behavioral diagrams
● Behavioral diagrams in UML represent the dynamic behavior of a system.
● They represent how the components of a system interact with each other and how
the system responds to external user.
● Behavioral diagrams are used to visualize the behavior of a system over time.

You might also like