Package, Component and Deployment
Diagrams
PB007 Software Engineering I
Bruno Rossi
19. 12. 2016
Software Engineering I (PB007) Packages, Components, Deployment 19. 12. 2016 1 / 11
Package Diagrams
Package diagrams display groups (packages) of related elements and the
dependencies between them.
The basic elements:
Packages - represent a logical mechanism for grouping related model
elements (classes, objects, instances of use, ...), plus they deﬁne their
namespace.
Dependencies - indicate that the elements in one package depend on
elements in another package. Depending on the type it can be further
speciﬁed as stereotype (use, import,...)
Software Engineering I (PB007) Packages, Components, Deployment 19. 12. 2016 2 / 11
Package Diagrams - example 1
Software Engineering I (PB007) Packages, Components, Deployment 19. 12. 2016 3 / 11
Package Diagrams - example 2
Software Engineering I (PB007) Packages, Components, Deployment 19. 12. 2016 4 / 11
Package Diagrams - circular dependencies
Software Engineering I (PB007) Packages, Components, Deployment 19. 12. 2016 5 / 11
Component diagram
Component diagrams show how to (hierarchically) distribute the system
into separate parts and communication links between them, that all deﬁne
the system architecture.
The basic elements:
Component - software components physically separate parts of the
system that are internally coherent and externally communicate only
through deﬁned interfaces.
Can be physical (e.g. EJB) or logical (e.g. subsystem)
Can be composed of other, nested, components
Interfaces - interfaces for communication between components.
We distinguish required interfaces and provided interfaces
Relations between interfaces - connection between the required
interface and the provided interface.
Software Engineering I (PB007) Packages, Components, Deployment 19. 12. 2016 6 / 11
Component Diagram - example
Software Engineering I (PB007) Packages, Components, Deployment 19. 12. 2016 7 / 11
Deployment Diagram
Deployment diagrams show the way in which the software architecture
will be mapped to the hardware.
Basic elements:
Nodes - critical computing resources that will be placed on diﬀerent
parts of the system. Can be further speciﬁed with stereotypes, for
example device or execution environment
Components/artefacts
Interfaces – interfaces for communication with components
Associations/dependencies - connections between nodes
(communication channels) and dependencies between components /
artifacts. May contain the name of the communication protocol.
Software Engineering I (PB007) Packages, Components, Deployment 19. 12. 2016 8 / 11
Deployment Diagram - example
Software Engineering I (PB007) Packages, Components, Deployment 19. 12. 2016 9 / 11
Tasks
Divide the class into packages according to the type of usage and
draw dependencies between packages. Use stereotypes.
Think about what components / subsystems will comprise your
system and by means of which interfaces they will communicate.
Create a deployment diagram of the proposed system.
Finalize the project - remove old diagrams, check all the charts for
consistency.
Upload the FINAL PDF report into folder for (Week 12). PLEASE
ensure all diagrams are included!
Deadline: Saturday, 17.12.16 23:59
Software Engineering I (PB007) Packages, Components, Deployment 19. 12. 2016 10 / 11
Customization of PDF Reports
Software Engineering I (PB007) Packages, Components, Deployment 19. 12. 2016 11 / 11