UML

Created by:
Sakshi Pandhi
Priyanka Gaba
Jeetender
 Introduction:-

 UML stands for Unified Modeling Language.

 Unified Modeling Language (UML) provides a variety of diagrams to represent the
represent the structure and design of a software system.
 It helps project teams to communicate, explore potential designs, and validate the
architectural design of the software.
 Unified Modeling Language (UML) is a standard language for creating blueprints tha
depict the structure and design of the software design of the software system.
 You can use UML for modeling systems than can range between enterprise informatio
system to distributed Web-based architecture of the system from various perspectives
 Scope of UML:-
 The Unified Modeling Language (UML) is a language for specifying, constructing,
visualizing, and documenting the artifacts of a software-intensive system.
 The artifacts might include requirements, architecture, design in terms of classes,
objects or interfaces, source code, tests, prototypes, and the software releases of a
software system.
 You can further divide the definition of UML into the following sub-parts:

 UML is a language for specifying artifacts:

This means that UML provides the notations for classes, objects, and interfac
which enable the development team to define the scope and content
of a software system.

 UML is a language for visualizing artifacts:

This means that UML allows you to create diagrams to visualize a software
system. Creating diagrams provides a better understanding of the structure
and content of the software system.
 UML is a language for constructing artifacts :
This means that UML allows code generation from a UML model. Generating
code from a UML model is called forward engineering. In addition, UML enables
reverse engineering, which means it allows you to reconstruct a model from code

 UML is a language for documenting artifacts:

This means that you can use the diagrams as input documents for the
subsequent phases of SDLC.
Building Blocks of UML:
The building blocks of UML include the components that are necessary for
creating models of the software systems. The three types of UML
building blocks are:
 Basic UML constituents:
Include the static, dynamic, grouping, and annotational constituents
of UML.
 Relationships:
Depict the relations between the various constituents of a UML
model.
 Diagrams:
Represent the various artifacts of a system graphically. Diagrams
enables you
to visualize a system from all the aspects of software development.
Identifying the Types of UML Diagrams:
UML provides the following thirteen diagrams to represent the structure and desig
of a software system:
Use case diagrams
Class diagrams
Object diagrams
Communications diagrams
Sequence diagrams
State Machine diagrams
Activity diagrams
Package diagrams
Component diagrams
Deployment diagrams
Timing diagrams
Composite diagrams
Interaction Overview diagrams
 Defining Use Case Diagrams:
• A use case diagram depicts the various operations that a system performs.
• It contains use cases, actors, and their relationships.
• Use cases are the sequence of actions that form a single unit of work for the actor.
• An actor represents a user who is external to the system and interacts with the use cas
• A use case diagram can be drawn for any given software system.
 Defining Class Diagrams:
• A class diagram represents a set of classes, interfaces, and their relationships.
• You can represent a class in a rectangular box with three compartments.
• The first compartment shows the classes name.
• The second compartment shows the attributes of the class and the third compartment
shows the methods associated with the classes.
• You can draw a class diagram by identifying the classes in the system.
 Defining Object Diagrams:
• An object diagram represents instances of a class diagram.
• You represent an object in a rectangular box with two compartments.
• The object name appears before the class name in the first compartment.
• The second compartment shows the attributes of the objects.
• You can draw an object diagram by identifying the classes in the system.
 Defining Communication Diagrams:
• Communication diagrams represent an interaction between objects in the form of
message.
• Communication diagram are also called as collaboration diagrams.
 Defining Sequence Diagrams:
• Sequence diagrams represent an interaction between objects in the form of message
ordered in a sequence by time.
• The difference between the sequence and communication diagrams is that communica
diagrams emphasize on the structural organization of objects as opposed to sequence
diagrams that show the messages exchanged between objects ordered in a sequence b
time.
• You can draw a sequence diagram for any given system by using the classes and use c
identified for the system.
 Defining State Machine Diagrams:
• A state machine diagram shows how a class reacts when an event occurs.
• You can draw state machine diagram by using the classes and the use cases indentified
for the system.
• A state diagram is also called as a state diagram or a state chart diagram.
 Defining Activity Diagrams:
• Activities are a representation of the various operations performed by a class.
• An activity diagram depicts the flow of control from one activity to another.
• You can draw an activity diagram by identifying the activities performed by the classes
of the system.
 Defining Package Diagrams:
• All the interrelated classes and interfaces of the system when grouped together form a
package.
• To represent all these interrelated classes and interfaces UML provide package diagram
• Package diagrams help in representing the various package of a software system and th
dependencies between them.
• It is also gives a high-level impression of use case and class diagrams.
• A package is depicted as shown in the following figure.
 Defining Component Diagrams:
• You combine packages or individual entities to form components.
• You can depict various components and their dependencies using a component diagram
• To understand how a component diagram depicts the components and their
dependencies, consider an example of the orderprocess executable component that
regulates the order and supply procedure.
• The orderprocess executeable component depends on the order. cs file for placing an
order for the machine parts.
• Similarly, the orderprocess executable component depends on the processsupply. cs fil
for processing the supply received.
• The following diagram shows the component diagram for the order processing system
 Defining Deployment Diagrams:
• A deployment diagram shows the physical placement of components in nodes over a
network.
• A deployment diagram can be drawn by identifying nodes and components.
• In this diagram the order processing system, the orderprocess. Exe component is place
on the Client node and the database component is placed on the Database Server node
• The request for the data for the order processing system is routed to the Database Serv
through the Processor Server.
• The following diagram shows the deployment diagram for the order processing system
 Defining Timing Diagrams:
• Timing diagrams are used to represent the changes in state and value of one or more
objects over a period of time.
• Timing diagrams are often used to design embedded software.
• Timing diagrams are two types:
 Concise notation
 Robust notation

Concise Notation
 In the concise notation, a value lifetime is used to represents the changes in the
value of objects over a period of time.
 The time elapsed is represented on the X-axis and the value is shown between
the pair of horizontal lines which cross over at each change in value.
 The following timing diagram depicts the value lifeline of a printer.
Robust Notation
 In the robust notation, a state lifeline is used to represent the changes in the state
of objects over a period of time.
 The X-axis represents the time elapsed and the Y-axis depicts a set of states.
 The following figure depicts the state lifeline for a printer.
 Defining Composite Structure Diagrams:
• A composite structure diagram represents the internal structure and interaction points
of a classifier.
• Interaction points refer to the points within a classifier using which the classifier intera
with other parts of the system.
• Composite structure diagrams are used to explore run-time instances of interconnected
classifier collaborating over communications links.
• A composite structure diagram is made up of several elements, such as parts, ports, an
interfaces.
• A part is an element that represents a set of one or more instances owned by the
containing classifier instance.
• You depict a part as a rectangle contained within the body of a class or component
element.
• The following figure shows parts of the Car class connected through.
• A port is an interaction point between a classifier instance and its environment or betwee
the behavior of the classifier and its internal parts.
• A classifier can have multiple ports to shows different interactions.
• You depict a port as a small, named square on the boundary of the owning classifier.
• A port can interact in both directions. Therefore, a port can be used to specify the service
provided by a classifier to its environment and the services required by the classifier fro
its environment.
• The services provided and required by a classifier are represented as interfaces owned by
the classifier.
• A provided interface is represented as a ball on a stick and a required interface is
represented as a socket on a stick.
• The following figure depicts a port on the Engine class with provided and required
interfaces.
 Defining Interaction Overview Diagrams:
• Interaction overview diagrams give an overview of interaction diagrams.
• Interaction diagrams include the following types of diagrams:
 Sequence diagram
 Communication diagram
 Timing diagram
 Interaction overview diagram
• Interaction overview diagrams represent the logical interaction between the interaction
diagrams and the process flows in between the set of interaction diagrams.
• Interaction overview diagrams are a variant of activity diagrams.
• Most of the diagram notation used for interaction overview diagrams is similar to the
diagram notation used for activity diagrams.
• Instead of activity elements, interaction overview diagrams use one of the following:
 Interaction elements:
 Interaction elements display an inline interaction diagram, which can be a
sequence diagram, communication diagram, timing diagram, or interaction
overview diagram.
 Interaction occurrence elements are references to an existing interaction
diagram.
  Interaction occurrence elements:

 Interaction occurrence elements are visually represented by a frame,

with
”ref” in the frame’s title space.
• The following figure depicts
 The diagram name isthe interaction
indicated in theoverview diagram for an
frame contents.
Inventory
Management System.
Visio:

• Microsoft Visio marketed as Microsoft Office Visio , is a diagramming

program for
Microsoft Windows that uses vector graphics to create diagrams.
• Visio is a Microsoft tool that facilitates object-oriented design using
UML.
• Its also helps in generating C#, C++, or Visual Basic code for the UML
diagrams.
• Visio diagrams that display data, are easy to refresh, and dramatically
increase
your productivity.
• Microsoft Office Visio makes it easy for IT and business professionals to

visualize, explore, and communicate complex information.

• Office Visio provides a wide range of templates- business process
flowcharts,
network diagrams, workflow diagrams, database models, and software
diagrams.
Enterprise architecture:
• Enterprise architecture (EA) is the art and science of enterprise design.
• The hope for enterprise architecture is that applying systematic rational methods to
the product one that more effectively and efficiently pursues its purposes.
• The phrase “enterprise architecture” can refer to both the process and the product
of systematic methods.
• As a complex process, enterprise architecture may use a framework of methods and
conceptual tools.
• The concept of Enterprise Architecture goes back at least to the early 1980’s when it
entered the research scope of Nolan, Norton & Co.
• The enterprise architecture defines how information and technology will support the
business operations and provide benefit for the business.
• It illustrates the organization’s core mission, each component critical to performing th
missions, and how each of these components is interrelated.
• These components include: *Guiding principles * Organization structure * Business
processes* People or stakeholders * Applications, data, and infrastructure.
Responsibilities of enterprise architects
• Alignment of IT strategy and planning with company’s business goals.
• Long-term strategic responsibility for the company’s IT systems.
• Direct or indirect involvement in the development of policies, standard and
guidelines that direct the selection, development, implementation and use of
Information Technology within the enterprise.
• Build employee knowledge and skills in specific areas of expertise.
Jude:
• JUDE is a UML Modeling tool created by the Japanese Company Change Vision .
The ‘Community’ version is free to use and offer the following functionality:
 Support of UML
 Class diagram
 Use Case diagram
 Sequence diagram
 Collaboration diagram
 State diagram
 Activity diagram
 Deployment diagram
 Component diagram
JUDE /Professional began to support the part of diagrams expressions of UML:
 Frame
 Navigable Association ( Class , Use Case, Deployment Diagram)
 Required Interface (Class Diagram)
 Provided Interface (Class Diagram)
 Combined Fragment(Sequence Diagram)
 Found Message (Sequence Diagram)
  Lost Message (Sequence Diagram)
 State Invariant (Sequence Diagram)
Vertical and Horizontal Partitions (Activity Diagram)
 Component Diagram
 Composite Structure Diagram

History
 JUDE development was originally started by Kenji Hiranabe, CEO of
Change
Vision, Inc , in 1996, around the time that UML, Java and some design
patterns
began appearing.
 He sensed that a radical UML tool for Object-Oriented Development was
going
to be in demand in the future and this idea spurred him to start creating
JUDE.
 JUDE started to be provided as a free software in 1999.
 Then 5 years later was reached the decision to start selling JUDE in the
Japanese
market.