0% found this document useful (0 votes)
15 views29 pages

Uml Class Diagrams

UML class diagrams visually represent the structure of a system by illustrating classes, interfaces, and their relationships, akin to a family tree. They serve to convert system requirements into detailed designs by breaking down use cases into fundamental components. Examples provided include scenarios from university teams, degrees, and organizations to demonstrate the application of class diagrams.

Uploaded by

ahamed.tanjir
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
15 views29 pages

Uml Class Diagrams

UML class diagrams visually represent the structure of a system by illustrating classes, interfaces, and their relationships, akin to a family tree. They serve to convert system requirements into detailed designs by breaking down use cases into fundamental components. Examples provided include scenarios from university teams, degrees, and organizations to demonstrate the application of class diagrams.

Uploaded by

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

UML CLASS DIAGRAMS

Basics of UML Class Diagrams


• What is a UML class diagram?
• Imagine you were given the task of drawing a
family tree. The steps you would take would
be:
– Identify the main members of the family
– Identify how they are related to each other
– Find the characteristics of each family member
– Determine relations among family members
– Decide the inheritance of personal traits and
characters
Basics of UML Class Diagrams
• A UML class diagram is similar to a family tree.
• A class diagram consists of a group of classes and
interfaces reflecting important entities of the business
domain of the system being modeled, and the
relationships between these classes and interfaces.
• The classes and interfaces in the diagram represent the
members of a family tree and the relationships between
the classes are analogous to relationships between
members in a family tree.
• Interestingly, classes in a class diagram are interconnected
in a hierarchical fashion, like a set of parent classes (the
grand patriarch or matriarch of the family, as the case
may be) and related child classes under the parent
classes.
Basics of UML Class Diagrams
• Similarly, a software application is comprised of classes
and a diagram depicting the relationship between each
of these classes would be the class diagram.
• By definition, a class diagram is a diagram showing a
collection of classes and interfaces, along with the
collaborations and relationships among classes and
interfaces
• A class diagram is a pictorial representation of the
detailed system design
• Now you now know what a class diagram is. But, how
does a class diagram relate to the use case diagrams
that that we learned before?
Basics of UML Class Diagrams
• When you designed the use cases, you must
have realized that the use cases talk about
"what are the requirements" of a system.
• The aim of designing classes is to convert this
"what" to a "how" for each requirement
• Each use case is further analyzed and broken
up into atomic components that form the
basis for the classes that need to be designed
Set of Operations for the Classes
Class Diagram
Example 2: University Teams Scenario
• In the project analysis course at UvA, students are
members of teams.
• Each team has 2 or 3 members.
• Each team completes 0 to 3 assignments.
• Each student takes exactly one midterm test.
• Computer Science students have a single account
on the CDF facility, while each engineering student
has an account on the Engineering facility.
• Each assignment and midterm is assigned a mark

Design a Class Diagram for the scenario


Example 3: University 2 Scenario
• A university offers degrees to students.
• The university consists of faculties each of which consists of
one or more departments.
• Each degree is administered by a single department.
• Each student is studying towards a single degree.
• Each degree requires one to 20 courses.
• A student enrolls in 1-5 courses (per term.)
• A course can be either graduate or undergraduate, but not
both.
• Likewise, students are graduates or undergraduates but not
both.
Draw a class diagrams which represents the generic objects and
relationships described above. Make sure to specify
multiplicities for all associations shown in your diagrams.
Example 4: Organization Scenario
• Consider the world of companies:
• Companies employ employees (who can only work
for one company), and consist of one or more
departments.
• Each company has a single president, who is an
employee.
• Departments have employees as members and run
projects (one or more.)
• Employees can work in 1 to 3 projects, while a project
can have 2 to 50 assigned employees.
• You may assume that companies have a name and
address, while employees have a emp# and a salary
QUESTIONS

You might also like