UNIT - II

UML Diagrams
UML diagrams are the ultimate output of the entire discussion. All the elements, relationships are
used to make a complete UML diagram and the diagram represents a system.
The visual effect of the UML diagram is the most important part of the entire process. All the
other elements are used to make it complete.
UML includes the following nine diagrams, the details of which are described in the subsequent
chapters.
● Class diagram
● Object diagram
● Use case diagram
● Sequence diagram
● Collaboration diagram
● Activity diagram
● Statechart diagram
● Deployment diagram
● Component diagram
 Structural Diagrams
The structural diagrams represent the static aspect of the system. These static
aspects represent those parts of a diagram, which forms the main structure and are
therefore stable.
These static parts are represented by classes, interfaces, objects, components, and
nodes. The four structural diagrams are −
● Class diagram
● Object diagram
● Component diagram
● Deployment diagram
 Class Diagrams

Class diagram is a static diagram. It represents the static view of an

application. Class diagram is not only used for visualizing, describing, and
documenting different aspects of a system but also for constructing executable
code of the software application.
Class diagram describes the attributes and operations of a class and also the
constraints imposed on the system. The class diagrams are widely used in the
modeling of object oriented systems because they are the only UML diagrams,
which can be mapped directly with object-oriented languages.
Class diagram shows a collection of classes, interfaces, associations,
collaborations, and constraints. It is also known as a structural diagram.
Essential elements of A UML class diagram
Essential elements of UML class diagram are:

1. Class Name
2. Attributes
3. Operations
Class Name

The name of the class is only needed in the graphical representation of the class.
It appears in the topmost compartment. A class is the blueprint of an object which
can share the same relationships, attributes, operations, & semantics. The class is
rendered as a rectangle, including its name, attributes, and operations in separate
compartments.

Following rules must be taken care of while representing a class:

1. A class name should always start with a capital letter.

2. A class name should always be in the center of the first compartment.
3. A class name should always be written in bold format.
4. An abstract class name should be written in italics format.
Attributes:
An attribute is named property of a class which describes the object being
modeled. In the class diagram, this component is placed just below the name-
compartment.

Attributes characteristics:

● The attributes are generally written along with the visibility factor.
● Public, private, protected and package are the four visibilities which are
denoted by +, -, #, or ~ signs respectively.
● Visibility describes the accessibility of an attribute of a class.
● Attributes must have a meaningful name that describes the use of it in a
class.
Class Operations (Methods)
❖ Operations are shown in the third partition. They are services the
class provides.
❖ The return type of a method is shown after the colon at the end of
the method signature.
❖ The return type of method parameters is shown after the colon
following the parameter name.
❖ Operations map onto class methods in code.
Relationships in Class Diagrams
Classes are interrelated to each other in specific ways. In particular, relationships in
class diagrams include different types of logical connections. The following are such
types of logical connections that are possible in UML:

● Dependency
● Association
● Directed Association
● Reflexive Association
● Multiplicity
● Aggregation
● Composition
● Inheritance/Generalization
● Realization
Dependency
A dependency means the relation between two or more classes in which a change in
one may force changes in the other. However, it will always create a weaker
relationship. Dependency indicates that one class depends on another.

In the following example, Student has a dependency on College

Generalization:

A generalization helps to connect a subclass to its superclass. A sub-class is inherited from

its superclass. Generalization relationship can't be used to model interface implementation.
Class diagram allows inheriting from multiple superclasses.

In this example, the class Student is generalized from Person Class.

Association:
This kind of relationship represents static relationships between classes A and B. For
example; an employee works for an organization.
Here are some rules for Association:
● Association is mostly verb or a verb phrase or noun or noun phrase.
● It should be named to indicate the role played by the class attached at the end of the
association path.
● Mandatory for reflexive associations
In this example, the relationship between student and college is shown which is studies.
Multiplicity
A multiplicity is a factor associated with an attribute. It specifies how many instances of
attributes are created when a class is initialized. If a multiplicity is not specified, by default
one is considered as a default multiplicity.

Let's say that that there are 100 students in one college. The college can have multiple
students.
Aggregation

Aggregation is a special type of association that models a whole- part

relationship between aggregate and its parts.

For example, the class college is made up of one or more student. In

aggregation, the contained classes are never totally dependent on the
lifecycle of the container. Here, the college class will remain even if the
student is not available.
Composition:
The composition is a special type of aggregation which denotes strong ownership
between two classes when one class is a part of another class.

For example, if college is composed of classes student. The college could contain
many students, while each student belongs to only one college. So, if college is
not functioning all the students also removed .
 Purpose of Class Diagrams

The purpose of class diagram is to model the static view of an application. Class
diagrams are the only diagrams which can be directly mapped with object-oriented
languages and thus widely used at the time of construction.
UML diagrams like activity diagram, sequence diagram can only give the sequence
flow of the application, however class diagram is a bit different. It is the most popular
UML diagram in the coder community.
The purpose of the class diagram can be summarized as −
● Analysis and design of the static view of an application.
● Describe responsibilities of a system.
● Base for component and deployment diagrams.
● Forward and reverse engineering.
How to Draw a Class Diagram?

Basically, Class diagrams are the most popular UML diagrams used for
construction of software applications. It is very important to learn the drawing
procedure of class diagram.
Class diagrams have a lot of properties to consider while drawing but here the
diagram will be considered from a top level view.
Class diagram is basically a graphical representation of the static view of the
system and represents different aspects of the application. A collection of class
diagrams represent the whole system.
The following points should be remembered while drawing a class
diagram −
● The name of the class diagram should be meaningful to describe the
aspect of the system.
● Each element and their relationships should be identified in advance.
● Responsibility (attributes and methods) of each class should be clearly
identified
● For each class, minimum number of properties should be specified, as
unnecessary properties will make the diagram complicated.
● Use notes whenever required to describe some aspect of the diagram. At
the end of the drawing it should be understandable to the developer/coder.
● Finally, before making the final version, the diagram should be drawn on
plain paper and reworked as many times as possible to make it correct.
Where to Use Class Diagrams?

Class diagrams are used for −

● Describing the static view of the system.
● Showing the collaboration among the elements of the
static view.
● Describing the functionalities performed by the system.
● Construction of software applications using object
oriented languages.
Benefits of Class Diagram
● Class Diagram Illustrates data models for even very complex
information systems
● It provides an overview of how the application is structured before
studying the actual code. This can easily reduce the maintenance time
● It helps for better understanding of general schematics of an application.
● Allows drawing detailed charts which highlights code required to be
programmed
● Helpful for developers and other stakeholders.
Class Diagram in Software Development Lifecycle
Class diagrams can be used in various software development phases. It helps in modeling
class diagrams in three different perspectives.

1. Conceptual perspective: Conceptual diagrams are describing things in the real world.
You should draw a diagram that represents the concepts in the domain under study. These
concepts related to class and it is always language-independent.

2. Specification perspective: Specification perspective describes software abstractions or

components with specifications and interfaces. However, it does not give any commitment
to specific implementation.

3. Implementation perspective: This type of class diagrams is used for implementations in

a specific language or application. Implementation perspective, use for software
implementation.
Visibility IN CLASS DIAGRAMS
The visibility of the attributes and operations can be represented in the following ways:
❖ Public − A public member is visible from anywhere in the system. In class
diagram, it is prefixed by the symbol ‘+’.
❖ Private − A private member is visible only from within the class. It cannot be
accessed from outside the class. A private member is prefixed by the symbol ‘−’.
❖ Protected − A protected member is visible from within the class and from the
subclasses inherited from this class, but not from outside. It is prefixed by the
symbol ‘#’.
CLASS DIAGRAM
EXAMPLES
EXAMPLEs OF CLASS DIAGRAM
The following diagram is an example of an Order System of an application. It
describes a particular aspect of the entire application.
● First of all, Order and Customer are identified as the two elements of the
system. They have a one-to-many relationship because a customer can have
multiple orders.
● Order class is an abstract class and it has two concrete classes (inheritance
relationship) SpecialOrder and NormalOrder.
● The two inherited classes have all the properties as the Order class. In
addition, they have additional functions like dispatch () and receive ().
The following class diagram has been drawn considering all the points
mentioned above.
Conclusion
❖ UML is the standard language for specifying, designing, and visualizing the artifacts of
software systems
❖ A class is a blueprint for an object
❖ A class diagram describes the types of objects in the system and the different kinds of
relationships which exist among them
❖ It allows analysis and design of the static view of a software application
❖ Class diagrams are most important UML diagrams used for software application
development
❖ Essential elements of UML class diagram are 1) Class 2) Attributes 3) Relationships
❖ Class Diagram provides an overview of how the application is structured before
studying the actual code. It certainly reduces the maintenance time
❖ The class diagram is useful to map object-oriented programming languages like Java,
C++, Ruby, Python, etc.
 Object Diagrams
❖ Objects are the real-world entities whose behavior is defined by the classes.
Objects are used to represent the static view of an object-oriented system. We
cannot define an object without its class. Object and class diagrams are
somewhat similar.
❖ In other words, “An object diagram in the Unified Modeling Language (UML), is a
diagram that shows a complete or partial view of the structure of a modeled system at a
specific time.”
❖ An object diagram shows this relation between the instantiated classes and the defined
class, and the relation between these objects in the system. They are be useful to explain
smaller portions of your system, when your system class diagram is very complex, and
also sometimes modeling recursive relationship in diagram.
❖ Object diagrams are used to render a set of objects and their relationships as an
instance.
Basic Object Diagram Symbols and Notations

Object Names:

● Every object is actually symbolized like a rectangle, that offers the name from the object and its class

underlined as well as divided with a colon.

Object Attributes:

● Similar to classes, you are able to list object attributes inside a separate compartment. However,

unlike classes, object attributes should have values assigned for them.
Links:

● Links tend to be instances associated with associations. You can draw a link while

using the lines utilized in class diagrams.

Notation of an object diagram:
Purpose of an object diagram:

1. It is used to describe the static aspect of a system.

2. It is used to represent an instance of a class.
3. It can be used to perform forward and reverse engineering on
systems.
4. It is used to understand the behavior of an object.
5. It can be used to explore the relations of an object and can be
used to analyze other connecting objects.
How to draw an object diagram?

1. Before drawing an object diagram, one should analyze all the objects
inside the system.
2. The relations of the object must be known before creating the diagram.
3. Association between various objects must be cleared before.
4. An object should have a meaningful name that describes its
functionality.
5. An object must be explored to analyze various functionalities of it.
Applications of Object Diagrams:
1. Object diagrams play an essential role while generating a
blueprint of an object-oriented system.
2. Object diagrams provide means of modeling the classes, data
and other information as a set or a single unit.
3. It is used for analyzing the online or offline system. The
functioning of a system can be visualized using object diagrams.
Where to Use Object Diagrams?

It can be said that object diagrams are used for −

● Making the prototype of a system.
● Reverse engineering.
● Modeling complex data structures.
● Understanding the system from practical perspective.
EXAMPLES:
The following diagram is an example of an object diagram. It represents the Order
management system which we have discussed in the chapter Class Diagram. The following
diagram is an instance of the system at a particular time of purchase. It has the following
objects.
● Customer
● Order
● SpecialOrder
● NormalOrder
Now the customer object (C) is associated with three order objects (O1, O2, and O3). These order
objects are associated with special order and normal order objects (S1, S2, and N1). The customer has
the following three orders with different numbers (12, 32 and 40) for the particular time considered.
The customer can increase the number of orders in future and in that scenario the object diagram will
reflect that. If order, special order, and normal order objects are observed then you will find that they
have some values.
Object Diagram Example II - POS
Summary OF OBJECT DIAGRAM

1. Class groups together things that share similar behavior.

2. A class represents a bird's eye view of a system, i.e., an abstraction
which is an object-oriented programming concept.
3. An object represents a static view of an object-oriented system.
4. One class can refer to multiple classes.
5. A single class can have any number of objects.
6. Objects are related to one another because they share the same class.
7. The object of different classes can also be connected.