Scribd
Upload
17 views4 pages

Unit-1-2-3 Uml

The document provides an introduction to Unified Modeling Language (UML), detailing its purpose as a graphical language for modeling software systems and the various types of diagrams it includes, such as class diagrams. It explains the relationships in class diagrams, including dependency, generalization, association, aggregation, and composition, with examples for each. Additionally, it discusses the application of UML in real-life scenarios, such as library and order management systems.

Uploaded by

tovilas
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
17 views4 pages

Unit-1-2-3 Uml

The document provides an introduction to Unified Modeling Language (UML), detailing its purpose as a graphical language for modeling software systems and the various types of diagrams it includes, such as class diagrams. It explains the relationships in class diagrams, including dependency, generalization, association, aggregation, and composition, with examples for each. Additionally, it discusses the application of UML in real-life scenarios, such as library and order management systems.

Uploaded by

tovilas
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

UNIT-1

Unified Modeling Language (UML): Introduction to UML & class diagrams


What is UML(Unified Modeling Language)?
UML stands for Unified Modeling Language and is a graphical language used to describe, design, and document
complex software systems. It is a standard modeling language that provides a common vocabulary and set of symbols
for software developers and designers to use when modeling software systems.

UML provides a wide range of diagram types that can be used to visualize various aspects of a software system, such
as class diagrams, sequence diagrams, state diagrams, activity diagrams, and others. These diagrams are used to
communicate the design of a system to stakeholders, to document the system for future reference, and to help identify
potential problems or areas for improvement.
UML is widely used in the software industry and is supported by many software development tools. It is also commonly
taught in computer science and software engineering courses, making it a valuable skill for software professionals.

Class Diagram:
A class diagram consists of class objects represented as boxes with three compartments. The top compartment contains
the name of the class, the middle compartment contains the class's attributes (instance variables), and the bottom
compartment contains the methods (operations) of the class.

UNIT-2
Modeling Relationships in Class Diagrams: Association, Aggregation Composition and examples
covering these principles

Modeling relationships:
Modeling relationships between classes in class diagrams is a fundamental aspect of UML and is used to
represent the relationships between classes in a software system. UML provides several types of
relationships that can be used to model different types of connections between classes, including:

In UML, relationships are of three types:

● Dependency: A dependency is a relationship between two classes where a change in one class may
affect the other class. It is represented by a dashed arrow pointing from the dependent class to the
class it depends on.
In the following example, Student_Name is dependent on the Student_Id.

● Generalization: A generalization is a relationship between a parent class (superclass) and a


child class (subclass). In this, the child class is inherited from the parent class.
For example, The Current Account, Saving Account, and Credit Account are the generalized
form of Bank accounts.
● Association: It represents a simple, bi-directional relationship between two classes. It is
represented by a line connecting the two classes. The ends of the line can be labeled with
multiplicity to indicate the number of instances of one class that can be associated with
instances of another class.
For example, a department is associated with the college.

Aggregation: An aggregation is a subset of association, which represents has a


relationship. It is more specific then association. It defines a part-whole or part-of
relationship. In this kind of relationship, the child class can exist independently of
its parent class.

The company encompasses a number of employees, and even if one employee


resigns, the company still exists.

Composition: The composition is a subset of aggregation. It portrays the dependency


between the parent and its child, which means if one part is deleted, then the other
part also gets discarded. It represents a whole-part relationship.

A contact book consists of multiple contacts, and if you delete the contact book, all
the contacts will be lost.

Multiplicity: It defines a specific range of allowable instances of attributes. In case if a range


is not specified, one is considered as a default multiplicity.

For example, multiple patients are admitted to one hospital.


UNIT-3
Applying OOP to solve real-life applications: To cover case studies like library management, order
management, etc. to design classes covering all relationships

Real-Life Examples on UML:


UML diagram-Library management system:
UML diagram-Order Management System:

You might also like