UML MODELING

UML Diagrams
What is UML?
• An industry-standard graphical language for specifying, visualizimg ,
constructing, and documenting the artifacts of software systems as
well as business modeling.
• The UML uses mostly graphical notations to express the analysis and
design of software projects.
Why a UML for modeling ?
• Uses graphical notations to communicate more clearly than netural
language and code.
• Make it easier for programmers and software architects to
communicate.
• UML is not dependent on any one language or technology.
. UML
Diagram

Behavior
diagram Structure diagram

Activity Use case State Class

diagram diagram diagram Component Object
machine Deployment
Interaction diagram
diagram
diagram
Use Case Diagram :
• Use-case diagrams model the behavior of a system .
• Used to illustrate the functional requirements of the system and its
interactions with external agents (actors).
• A use case diagram gives us high level views of the system without
going into implementation detail.
 Search
Example:
Show time Manage
booking

Booking

Manage show time

Payment
Admin
Customer
Generate reports

Cancel
booking
Activity Diagram:
• The activity diagram is a flowchart to represent the flow of control
among the activities in a System.
• The flow of operation can be a sequential,brunched or concurrent
.the activity of diagram sometimes considered as the flowchart.
 Insert card

Enter pin

Checking

enter money
Transaction failed

Submit

Message on mobile Balance on screen

Money withdrawing

Take your card

Class Diagram:
• Static relationship between classes .
• Describe the types of objects in the system and various kinds of
statics relationship that exist among them.
 Account
Bank BRANCH _account no
_branch code _balance
name _city
Cose 1 0…* +deposit()
+addBranch() 1 * +addAccount() +withdraw()
+removeBranch() +removeAcount() +AddLoan()
+getBranch() +removeLoan()
+getAllBranches

Loan SAVING ACCOUN Current account

_loan_no _MIN BALANCE _int-rate
_amount _opening-date _opening date
_type
+addcustom +add customer () +AddCustomer ()
er() +remove +remove
+getEMI() Customer() customer ()

0……..1 0………………1
0….* 1
1 Customer 1
BENEFITS OF UML I SOFTWARE MODELLING :
Standardized Language: UML provides a common language for software
modeling, ensuring clarity and consistency.

Visual Representation: UML diagrams offer a visual means of representing

complex software concepts andrelationships.

Design Validation: UML enables validation of system design before

implementation, identifying potential issues early on.

Documentation: UML diagrams serve as documentation artifacts, aiding

in maintenance, reusability, and knowledge transfer.
SOFTWARE PROCESS USED IN UML :
1. Identify Requirements: Understand and gather requirements for the software system.

1. Create Use Case Diagrams: Capture system functionality and user interactions.

1. Develop Class Diagrams: Define classes, relationships, and attributes.

1. Create Activity Diagrams: Represent system workflows and processes.

1. Optional: State Machine Diagrams, Component Diagrams, and others as needed.

1. Design Sequence Diagrams: Model object interactions and message flows.

1. Validate and Refine: Review and refine the models to ensure accuracy and completeness.
 TYPES OF UML IN SOFTWARE MODELLING :
Diagram

Structure
Behavior diagram
diagram

class Object Component Activity Use case

Profile Composite Deployment Package Interaction State machine

Sequence Interaction Communication Timing

STRUCTURE DIAGRAMS :
Structure diagrams show the static structure of the system and its parts on
different abstraction and implementation levels and how they are related to
each other. The elements in a structure diagram represent the meaningful
concepts of a system, and may include abstract, real world and
implementation concepts, there are seven types of structure diagram as
follows:

Class Diagram
Component Diagram
Deployment Diagram
Object Diagram
Package Diagram
Composite Structure Diagram
Profile Diagram
BEHAVIORAL DIAGRAMS :
Behavior diagrams show the dynamic behavior of the objects in a system, which can be
described as a series of changes to the system over time, there are seven types of behavior
diagrams as follows:

Use Case Diagram

Activity Diagram
State Machine Diagram
Sequence Diagram
Communication Diagram
Interaction Overview Diagram
Timing Diagram
UML Diagram Types
 LIMITATION OF UML :

➡️ UML is very complex and heterogeneous.

➡️ A large part of UML does not yet have precise semantics.

➡️ Problems in learning and adopting.

 APPLICATIONS OF UML :
➡️Designing software. Communicating software or business
processes.

➡️ Capturing the details about a system for requirements or analysis.

➡️ Documenting an existing system, process or organization.

➡️ UML provides a vocabulary of diagrams and chart types to

describe almost any application in almost any domain.
 CHARACTERISTICS OF UML:
➡️ It is standardized and widely accepted today.

➡️ It is conceptually rich.

➡️ It is extensible in a standardized, controlled way.

➡️ It’s concise.

➡️ It’s comprehensive.

➡️ It’s scalable
 UML Diagram
• UML include the following nine diagrams ;
• UML standard diagrams
• Structural modelling
• class diagram
• object
• Implementation
• component
• deployment
• Behavioral diagram
• Behavioral diagram
• Use case diagram
• Interaction diagram
• sequence diagram
• collaboration diagram
• Statechart diagram
• Activity diagram
Common uses of UML diagram
• Class diagrams
• model the vocabulary of the system
• Model simple collaburations
• Model a logical database schema
• Object diagrams
• Model object structures
• Primary support of the functional requirements of the system
• Use case diagrams
• Model the context of the system
• Model requirements of the system
Common uses of UML diagram (contd)
Interaction diagrams
Sequence diagram
• model interaction among object in time sequence
Collaboration diagram
• Model flow of control by the organization
State chart diagrams
• Model dynamic aspects event-ordered behavior of singal use case
• Model reactive objects
 Activity diagrams
• Model a work flow of a singal use case or for the entire software
• Model an operation
• Common uses of UML diagrams (contd)
• Implementation diagrams
• Component diagrams
• Model static implementation view
• Model source code
• Model executable releases
• Model physical database
• Model adaptable systems
• Deployment diagrams
• Model embedded system
• Model client server system