Analytical class diagram II
PB007 Software engineering I
Marián Macik
originally by Stanislav Chren
Week 06
Software engineering I (PB007) Class diagram II Week 06 1 / 8
Relationships between classes
The basic relationships include:
Generalization
Association
Dependency
Software engineering I (PB007) Class diagram II Week 06 2 / 8
Association
Asociation is a relationship between classes.
represents a long-time relationship (i.e. there is a reference between
instances of the given classes)
the reference is often expressed by the presence of the attribute
having the type of the other class
relationship 1:1 corresponds to a simple attribute reference
relationship 1:N corresponds to an array or collection
the direction of the association (navigability) indicates the class that
will contain the attribute.
Software engineering I (PB007) Class diagram II Week 06 3 / 8
Association - Navigability
Both Company and Employee have references to each other
The Company has a reference (collection attribute) to its Employees. The
Employee does not have reference to the Company
The Company does not have reference to its Employees. The Employee
has an attributed ot the type Company as reference.
Software engineering I (PB007) Class diagram II Week 06 4 / 8
Dependency
Dependency is a relationship between two classes(client and provider),
where change in provider may force change in the client. In other words,
the client somehow depends on the provider.
The semantics of this dependency can be speciﬁed by diﬀerent stereotypes.
The most common stereotype is use . It indicates that some of the
client operations use the provider object as input argument or as return
value, or it is used in its implementation and at the same time, there is no
attribute/reference to that class.
Software engineering I (PB007) Class diagram II Week 06 5 / 8
Tasks
Finalize the analytical class diagram
The diagram should contain the analytical classes, attributes, operations and the
diﬀerent relationships (inheritance, association, dependencies)
The associations should specify name, multiplicity and navigability
Add manager classes which manipulate with the base analytical classes (maintaining
the list of objects, lifecycle management, ...). Move the appropriate responsibilities.
Update the use case diagram. For each analytical class, there should
be a use case that manipulates with its instances.
Think about the interaction between diﬀerent class instances. Based
on your class diagram, can you represent all use cases?
Generate a PDF report and upload it to the homework vault
(Week 06).
Software engineering I (PB007) Class diagram II Week 06 6 / 8
Rules for report submission
1 Submit the PDF report, not the VP source ﬁle and not an exported image.
2 PDF report must be created using the procedure shown on the seminars
including the report settings.
3 The name of the PDF report ﬁle should be lastname1-lastname2-lastname3
of the team members.
4 PDF report must contain all diagrams modelled until now.
5 PDF report must be uploaded to the homework vault by the speciﬁed
deadline.
6 PDF report must be uploaded to the correct homework vault. The name of
the homework vault is always speciﬁed on the slides.
7 Each team uploads only a single PDF report for the whole team.
8 Submitted diagrams must be clear and readable.
9 Submitted diagrams should not contain serious mistakes. At least, they
should not contain mistakes mentioned in the Catalogue of common
mistakes.
Software engineering I (PB007) Class diagram II Week 06 7 / 8
VP report settings
Software engineering I (PB007) Class diagram II Week 06 8 / 8