Week-4 (UML)

CE204 Object-Oriented Programming¶

Week-4 (UML-Unified Modelling Language)¶

Spring Semester, 2021-2022¶

Download DOC-PDF, DOC-DOCX, SLIDE, PPTX,

UML-Unified Modelling Language¶

Outline¶

UML Overview
UML Tools
UML Building Blocks
UML Architecture
UML Diagrams Overview
UML Relationship
UML Association vs. Aggregation vs. Composition

Outline¶

UML- Association
UML-Dependency
UML-Generalization
UML-Realization
UML Class Diagram
UML Object Diagram
UML Component Diagram

Outline¶

UML Deployment Diagram
UML Interaction Diagram
UML Use Case Diagram
UML Sequence Diagram
UML Collaboration Diagram
UML State Machine Diagram
UML Activity Diagram
UML Timing Diagram

UML Overview¶

UML (Unified Modeling Language) is a general-purpose, graphical modeling language in the field of Software Engineering.
UML is used to specify, visualize, construct, and document the artifacts (major elements) of the software system.
It was initially developed by Grady Booch, Ivar Jacobson, and James Rumbaugh in 1994-95 at Rational software,
and its further development was carried out through 1996.
In 1997, it got adopted as a standard by the Object Management Group.

What is UML¶

The UML stands for Unified modeling language, is a standardized general-purpose visual modeling language in the field of Software Engineering.
It is used for specifying, visualizing, constructing, and documenting the primary artifacts of the software system.
It helps in designing and characterizing, especially those software systems that incorporate the concept of Object orientation.
It describes the working of both the software and hardware systems.

Goals of UML¶

Since it is a general-purpose modeling language, it can be utilized by all the modelers.
UML came into existence after the introduction of object-oriented concepts to systemize and consolidate the object-oriented development, due to the absence of standard methods at that time.
The UML diagrams are made for business users, developers, ordinary people, or anyone who is looking forward to understand the system, such that the system can be software or non-software.
Thus it can be concluded that the UML is a simple modeling approach that is used to model all the practical systems.

Characteristics of UML¶

The UML has the following features:
It is a generalized modeling language.
It is distinct from other programming languages like C++, Python, etc.
It is interrelated to object-oriented analysis and design.
It is used to visualize the workflow of the system.
It is a pictorial language, used to generate powerful modeling artifacts.

Conceptual Modeling¶

Before moving ahead with the concept of UML, we should first understand the basics of the conceptual model.
A conceptual model is composed of several interrelated concepts. It makes it easy to understand the objects and how they interact with each other. This is the first step before drawing UML diagrams.

Conceptual Modeling¶

Following are some object-oriented concepts that are needed to begin with UML:
Object: An object is a real world entity. There are many objects present within a single system. It is a fundamental building block of UML.
Class: A class is a software blueprint for objects, which means that it defines the variables and methods common to all the objects of a particular type.

Conceptual Modeling¶

Abstraction: Abstraction is the process of portraying the essential characteristics of an object to the users while hiding the irrelevant information. Basically, it is used to envision the functioning of an object.
Inheritance: Inheritance is the process of deriving a new class from the existing ones.
Polymorphism: It is a mechanism of representing objects having multiple forms used for different purposes.
Encapsulation: It binds the data and the object together as a single unit, enabling tight coupling between them.

OO Analysis and Design¶

OO is an analysis of objects, and design means combining those identified objects.
So, the main purpose of OO analysis is identifying the objects for designing a system.
The analysis can also be done for an existing system.
The analysis can be more efficient if we can identify the objects. Once we have identified the objects, their relationships are then identified, and the design is also produced.

OO Analysis and Design¶

The purpose of OO is:
To identify the objects of a system.
To identify their relationships.
To make a design that is executable when the concepts of OO are employed.

OO Analysis and Design¶

Step 1: OO Analysis¶

The main purpose of OO analysis is identifying the objects and describing them correctly.
After the objects are identified, the designing step is easily carried out. It is a must to identify the objects with responsibilities.
Here the responsibility refers to the functions performed by the objects.
Each individual object has its own functions to perform.
The purpose of the system is fulfilled by collaborating these responsibilities.

OO Analysis and Design¶

Step 2: OO Design¶

This phase mainly emphasizes on meeting the requirements.
In this phase, the objects are joined together as per the intended associations.
After the association is completed, the designing phase also gets complete.

OO Analysis and Design¶

Step 3: OO Implementation¶

This is the last phase that comes after the designing is done.
It implements the design using any OO languages like C++, Java, etc.

Role of UML in OO design¶

As the UML is a modeling language used to model software as well as non-software systems,
but here it focuses on modeling OO software applications.
It is essential to understand the relation between the OO design and UML.
The OO design can be converted into the UML as and when required.
The OO languages influence the programming world as they model real world objects.

Role of UML in OO design¶

The UML itself is an amalgamation of object-oriented notations like
Object-Oriented Design (OOD),
Object Modeling Technique (OMT), and
Object-Oriented Software Engineering (OOSE).
The strength of these three approaches is utilized by the UML to represent more consistency.

UML Tools¶

Plantuml¶

Plantuml is an open-source online and offline modeling tool with textual inputs to create flowcharts, process diagrams, UML, ER, and network diagrams.
PlantUML diagrams are “Diagrams as Code” in PlantUML syntax.
https://crashedmind.github.io/PlantUMLHitchhikersGuide/C4/C4Stdlib.html
https://en.wikipedia.org/wiki/4%2B1_architectural_view_model
https://c4model.com/img/c4-overview.png
https://plantuml.com/
https://crashedmind.github.io/PlantUMLHitchhikersGuide/about/AboutPlantUML.html
https://github.com/jupe/puml2code
http://static.codingthearchitecture.com/visualising-software-architecture.pdf
http://static.codingthearchitecture.com/documenting-software-architecture.pdf
https://en.wikipedia.org/wiki/C4_model

UML Tools¶

Draw.IO¶

Draw.io is an open-source modeling tool to create flowcharts, process diagrams, UML, ER, and network diagrams.

UML Tools¶

Draw.IO¶

Features:
Since it is very easy to use, it provides an intuitive interface, drag& drop functionality, a huge amount of templates, and also, it does not need to install.
It offers security and reliability.
It can be used anywhere, both online and offline.
It is compatible with every browser.
Download link: https://www.draw.io

UML Tools¶

Umple¶

Umple is an object-oriented and modeling language that textually supports state diagrams and class diagrams. It adapts JAVA, C++, and PHP, which results in more readable and short lines of code.

UML Tools¶

Umple¶

Features:
It includes Singleton pattern, keys, immutability, mixins, and aspect-oriented code injection, which makes UML more understandable to the users.
It enforces referential integrity by supporting UML multiplicity.
Download link: https://cruise.eecs.uottawa.ca/umple/

UML Tools¶

Visual Paradigm¶

A visual Paradigm is a tool that supports SysML, UML2, and Business Process Modeling Notation from Object Management Group. It involves report generation as well as code generation.

UML Tools¶

Visual Paradigm¶

Features:
It supports all of the 14 UML2 diagrams.
It supports BPMN 2.0, ERD, ORMD, SysML.
Download link: https://www.visual-paradigm.com

UML Tools¶

StarUML¶

StarUML is an open-source software modeling tool, which is provided by MKLab. It has come up with eleven different types of modeling diagrams. It also supports UML2.0 specified diagrams.

UML Tools¶

StarUML¶

Features:
It let you create Object, Use case, Deployment, Sequence, Collaboration, Activity, and Profile diagrams.
It is a UML 2.x standard compliant.
It offers multiplatform support (MacOS, Windows, and Linux).
Download link: http://staruml.io

UML Tools¶

Umbrello¶

Umbrello is a Unified Modeling language tool, which is based on KDE technology. It supports both reverse engineering and code generation for C++ and Java.

UML Tools¶

Umbrello¶

Features:
It implements both structural and behavioral diagrams.
It imports C++ and can export up to a wider range of languages.
Download link: https://umbrello.kde.org

UML Tools¶

UML designer tool¶

The UML designer tool helps in modifying and envisioning UML2.5 models. It allows you to create all of the UML diagrams.

UML Tools¶

UML designer tool¶

Features:
It provides transparency to work on DSL as well as UML models.
With the UML designer tool, the user can reuse the provided presentations.
It implements Component, Class, and Composite structure diagrams.
To start working with DSL, you can use UML legacy models.
Download link: http://www.umldesigner.org/download/

UML Tools¶

Altova¶

Altova has provided UModel, which is another UML software modeling tool. It supports all types of 14 UML2 diagrams as well as SysML for the embedded systems.
It also holds up for business process modeling for enterprise analysts.
It generates visually designed software models by incorporating Java, C++, and C #or Visual Basic .NET.

UML Tools¶

Altova¶

Features:
It provides a dedicated toolbar for an individual diagram.
It offers unlimited undo/redo, which inspires to discover new ideas.
In UML diagrams, you can easily add a hyperlink to any element.
It also provides an intuitive color-coding, icons, customized alignment grid, and cascading styles for colors, fonts line size.
Download link: https://www.altova.com/umodel

UML Tools¶

WhitestarUML¶

Whitestar UML is a division of StarUML 5.0 that offers bug fixes and has improved its compatibility with the latest operating systems, i.e., support of Unicode strings or simply being developed and tested on Windows 7 and 8.

UML Tools¶

WhitestarUML¶

Features:
It offers a refreshed user interface.
It completely handles the functioning of Unicode strings.
It provides support on Windows 7, 8, and 10.
On-demand upload and download of units.
It directly integrates the ERD profile and extends to generate and parse the SQL tables.
Download link: http://whitestaruml.sourceforge.net

UML Tools¶

GenMyModel¶

GenMyModel is an online modeling platform that offers Business (Archimate, BPMN, flowcharts support) as well as IT modeling (RDS, UML2.5 class diagrams).

UML Tools¶

GenMyModel¶

Features:
It provides an online platform.
It generates online code.
It provides a centralized repository for easy and simultaneous model collaboration.
You can import or export as a PDF.
Download link: https://www.genmymodel.com

UML Tools¶

Umletino¶

It is an online platform that offers UML tools for faster development of UML diagrams. It is based on UMLet, which is an eclipse plugin or work as a standalone tool.

UML Tools¶

Umletino¶

Features:
It allows you to export the diagram as XML or any other image file such as Gif, JPEG, or SVG format.
It is an installation free web application.
Download link: http://www.umlet.com/umletino/umletino.html

UML Tools¶

Diagramo¶

Diagramo is an online open-source HTML5 software that allows you to build flowcharts. It allows easy download and installation on the servers.

UML Tools¶

Diagramo¶

Features:
It saves diagrams as images.
It is a kind of UML diagram as it offers a flowchart focused software.
It offers lifetime support and storage.
Download link: http://diagramo.com

UML Tools¶

Astah¶

Astah, which was previously known as JUDE (Java and UML Developer's Environment) is a UML modeling tool.

UML Tools¶

Astah¶

Features:
It import XML file and export HTML, RTF, and image files.
It intuitively works with Windows, Mac, and Linux operating systems.
Download link: http://astah.net

UML Tools¶

BOUML¶

BOUML is a UML diagram designer which is programmed in Qt and C++. It permits you to specify and generate code in C++, Java, Idl, Php, Python, and MySQL.

UML Tools¶

BOUML¶

Features:
It supports code generation, reverse engineering, and it is multilingual.
It runs on Windows, Linux, and MacOS X.
Since it is very fast, it does not necessitate much memory to handle thousands of classes.
Download link: https://www.bouml.fr

UML Tools¶

ConceptDraw¶

ConceptDraw is a software, which is used in diagraming for creating business graphics that include diagrams, flowcharts, Infographics, data envisioning, data presentation, and project management documentation.

UML Tools¶

ConceptDraw¶

Features:
It is used for creating UML diagrams, DFD, ERD, computer network topology, etc.
It improves the interaction by empowering technical representation techniques.
It provides a powerful and inclusive drawing tool.
Download link: https://www.conceptdraw.com/products/drawing-tool

UML Tools¶

Dia¶

Dia is an open-source general-purpose drawing tool, which is licensed under GPL. It let you create flow charts, UML diagrams, network diagrams, circuit diagrams, and many more. It allows you to incorporate a subset of Scalable Vector Graphics (SVG) while writing a simple XML file for drawing new shapes.

UML Tools¶

Dia¶

Features:
Dia can export diagrams to several formats, which include EPS (Encapsulated PostScript), SVG (Scalable Vector Graphics), DXF (AutoCAD's Drawing Interchange Format), CGM (Computer Graphics Metafile defined by ISO standards), WMF (Windows Meta File), PNG (Portable Network Graphics), JPEG (Joint Photographic Experts Group), and VDX (Microsoft's XML for Visio drawing).
It let you create many different types of diagrams as it incorporates special objects that help you in drawing ER diagrams, UML diagrams, network diagrams, flowcharts, etc.
Download link: http://dia-installer.de

UML Tools¶

Sparxsystems¶

Sparxsystems is a diagram designing tool that helps in visualizing, analyzing, modeling, testing, and maintain software, system, processes, and architectures. It builds a robust and maintainable software.

UML Tools¶

Sparxsystems¶

Features:
It integrates and connects a wide range of structural and behavioral information in a visual format to create a logical and justified model.
It builds strategic and business level models.
It provides domain-specific profiles and reusable model patterns.
It also provides role-based security.
Download link: https://sparxsystems.com

UML Tools¶

Gliffy¶

Gliffy is an open-source software that designs UML diagrams, floor plans, Venn diagrams, flowcharts, and much more. It allows the user to share and edit Gliffy diagrams dynamically.

UML Tools¶

Gliffy¶

Features:
It constitutes a drag and drop interface.
It exports diagrams in various formats that are; PDF, JPEG, PNG, and SVG.
It is supported by all web browsers such as Google Chrome, Firefox, Safari, and Internet Explorer 9+.
Download link: https://www.gliffy.com

UML Tools¶

Lucidchart¶

Lucidchart is an HTML-5 based UML tool that allows user interaction while drawing, editing, and sharing diagrams and charts. With Lucidchart, you can create simple flowcharts as well as complex technical diagrams.

UML Tools¶

Lucidchart¶

Features:
It works faster with keyboard shortcuts.
It constitutes the concept of containerization as the complex diagram involves several steps and people.
It manages user account by increasing security.
It is platform-independent.
Download link: https://www.lucidchart.com/pages/

UML Tools¶

Magic Draw¶

Magic Draw is used to model UML diagrams, SysML, BPMN, and UPDM that supports the dynamic collaboration of the team. This tool is meant for business analysts, software analysts, programmers, and QA engineers. It facilitates analyzing and designing object-oriented systems and databases.

UML Tools¶

Magic Draw¶

Features:
It provides round-trip support for programming languages (J2EE, C#, C++, COBRA IDL), .NET, XML Schema, DDL generation, and database schema.
It incorporates the concept of reverse engineering.
It is a domain-specific language.
It constitutes model decomposition that categorizes the main project into several distinct independents parts.
It encompasses model refactoring to improve the existing model.
Download link: https://www.nomagic.com/products/magicdraw

UML Tools¶

Visio¶

Visio is a part of the Microsoft family, which is a diagramming software. It is helpful in drawing building plans, floor charts, data flow diagrams, process flow diagrams, business process modeling, swimlane diagrams, and many more.

UML Tools¶

Visio¶

Features:
It connects the diagrams and the flowcharts to real-time data.
Since it is a platform-independent, it can be accessed from anywhere.
Download link: https://products.office.com/en-in/visio/flowchart-software

UML Tools¶

Modelio¶

Modelio is an open-source UML tool that amalgamates UML2 and BPMN standards to support an inclusive range of models and diagrams.

UML Tools¶

Modelio¶

Features:
It provides support to Jython, which is a scripting language.
It provides a BPMN integrated support with UML.
It offers XMI import/export.
Download link: https://www.modelio.org

UML Tools¶

Nclass¶

Nclass is an open-source tool, used to create class diagrams that support #C and Java. It requires a framework of .NET 4.0. It has designed a simple and user-friendly user interface for fast and easy development.

UML Tools¶

Nclass¶

Features:
It provides a simple and easy user interface.
It offers a multilingual user interface.
It provides mono support for the non-windows user.
It has come up with inline class editors for fast and easy editing.
It incorporates source code generation and reverse engineering from .Net assemblies.
Download link: http://nclass.sourceforge.net

UML Tools¶

Open ModelSphere¶

Open ModelSphere, which is written in Java, is an open-source data, process, and UML modeling tool. It supports forward and reverse engineering.

UML Tools¶

Open ModelSphere¶

Features:
It provides support to the user interface written in English and French language.
It provides an in-built interface to connect to the SQL database via JDBC/ODBC drivers.
It has come up with a bi-directional plug-in database interface.
It supports physical, logical, and database modeling.
Download link: http://www.modelsphere.com/org/

UML Tools¶

Systems design rhapsody¶

System design rhapsody provides a collaborative design and modeling environment, which is based on UML for creating real-time, embedded systems. It helps in managing complex issues such as product system development.

UML Tools¶

Systems design rhapsody¶

Features:
For the system and software engineers, it has come up with a collaborative design, development, and a test environment based on UML, SysML, and AUTOSAR.
It helps in analyzing and elaborating project requirements.
It outperforms in the real-time, embedded, agile engineering environment.
It generates documentation after automating design reviews.
Download link: https://www.ibm.com/in-en/marketplace/systems-design-rhapsody

UML Tools¶

Reactive Blocks¶

A visual model-driven environment is based on the activity diagram that is supported by reactive blocks. Since it is a UML tool, it incorporates code generation, hierarchical modeling, and an extensive library of ready-to-use components for the Java platform.

UML Tools¶

Reactive Blocks¶

Features:
It helps in creating complex graphical applications by amalgamating reusable blocks.
It provides support to Java, Open Services Gateway Initiative, Eclipse Kura, and ESF.
Download link: http://www.bitreactive.com/reactive-blocks/

UML Tools¶

Software Ideas Modeler¶

Software Ideas Modeler is the CASE and designing tool written in C# that supports all of the 14 diagrams specified by UML2.5, SysML, ERD, Archimate, flowcharts, DFD, wire frames, user stories, and much more.

UML Tools¶

Software Ideas Modeler¶

Features:
It can be used for creating infographics, which is used for data visualization.
It involves automatic scrolling, drag and drop, undo/ redo facilities.
It offers simple task management.
It supports reverse engineering.
It also supports SVN.
Download link: https://www.softwareideas.net

UML Building Blocks¶

UML is composed of three main building blocks, i.e.,
Things,
Relationships, and
Diagrams.
Building blocks generate one complete UML model diagram by rotating around several different blocks.

Things¶

Anything that is a real world entity or object is termed as things. It can be divided into several different categories:
Structural things
Behavioral things
Grouping things
Annotational things

Structural things¶

Nouns that depicts the static behavior of a model is termed as structural things.
They display the physical and conceptual components.
They include class, object, interface, node, collaboration, component, and a use case.

Structural things¶

Class:
A Class is a set of identical things that outlines the functionality and properties of an object.
It also represents the abstract class whose functionalities are not defined. Its notation is as follows

bg right:50% h:500px

Structural things¶

Object:
An individual that describes the behavior and the functions of a system.
The notation of the object is similar to that of the class; the only difference is that the object name is always underlined and its notation is given follow;

bg right:50% h:500px

Structural things¶

Interface:
A set of operations that describes the functionality of a class, which is implemented whenever an interface is implemented.

bg right:50% h:200px

Structural things¶

Collaboration:
It represents the interaction between things that is done to meet the goal.
It is symbolized as a dotted ellipse with its name written inside it.

bg right:50% h:300px

Structural things¶

Use case:
Use case is the core concept of object-oriented modeling.
It portrays a set of actions executed by a system to achieve the goal.

bg right:50% h:300px

Structural things¶

Actor:
It comes under the use case diagrams.
It is an object that interacts with the system, for example, a user.

bg right:50% h:400px

Structural things¶

Component:
It represents the physical part of the system.

bg right:50% h:400px

Structural things¶

Node:
A physical element that exists at run time.

bg right:50% h:400px

Behavioral Things¶

They are the verbs that encompass the dynamic parts of a model.
It depicts the behavior of a system.
They involve
state machine,
activity diagram,
interaction diagram,
grouping things,
annotation things

Behavioral Things¶

State Machine:
It defines a sequence of states that an entity goes through in the software development lifecycle.
It keeps a record of several distinct states of a system component.

bg right:50% h:600px

Behavioral Things¶

Activity Diagram:
It portrays all the activities accomplished by different entities of a system.
It is represented the same as that of a state machine diagram. It consists of an initial state, final state, a decision box, and an action notation.

bg right:50% h:600px

Behavioral Things¶

Interaction Diagram:
It is used to envision the flow of messages between several components in a system.

bg right:50% h:600px

Grouping Things¶

It is a method that together binds the elements of the UML model.
In UML, the package is the only thing, which is used for grouping.

Grouping Things¶

Package: Package is the only thing that is available for grouping behavioral and structural things.

bg right:50% h:400px

Annotation Things¶

It is a mechanism that captures the remarks, descriptions, and comments of UML model elements.
In UML, a note is the only Annotational thing.

Annotation Things¶

Note:
It is used to attach the constraints, comments, and rules to the elements of the model.
It is a kind of yellow sticky note.

bg right:50% h:200px

Relationships¶

It illustrates the meaningful connections between things. It shows the association between the entities and defines the functionality of an application. There are four types of relationships
Dependency
Association
Generalization
Realization

Relationships¶

Dependency:
Dependency is a kind of relationship in which a change in target element affects the source element, or simply we can say the source element is dependent on the target element.
It is one of the most important notations in UML. It depicts the dependency from one entity to another.
It is denoted by a dotted line followed by an arrow at one side as shown below,

bg right:30% h:50px

Relationships¶

Association:
A set of links that associates the entities to the UML model.
It tells how many elements are actually taking part in forming that relationship.
It is denoted by a dotted line with arrowheads on both sides to describe the relationship with the element on both sides.

bg right:30% h:40px

Relationships¶

Generalization:
It portrays the relationship between a general thing (a parent class or superclass) and a specific kind of that thing (a child class or subclass).
It is used to describe the concept of inheritance.
It is denoted by a straight line followed by an empty arrowhead at one side.

bg right:30% h:70px

Relationships¶

Realization:
It is a semantic kind of relationship between two things, where one defines the behavior to be carried out, and the other one implements the mentioned behavior.
It exists in interfaces.
It is denoted by a dotted line with an empty arrowhead at one side.

bg right:30% h:70px

Diagrams¶

The diagrams are the graphical implementation of the models that incorporate symbols and text.
Each symbol has a different meaning in the context of the UML diagram.
There are thirteen different types of UML diagrams that are available in UML 2.0, such that each diagram has its own set of a symbol.
And each diagram manifests a different dimension, perspective, and view of the system.

Diagrams¶

UML diagrams are classified into three categories that are given below:
Structural Diagram
Behavioral Diagram
Interaction Diagram

Diagrams¶

Structural Diagram:
It represents the static view of a system by portraying the structure of a system.
It shows several objects residing in the system. Following are the structural diagrams given below:
- Class diagram
- Object diagram
- Package diagram
- Component diagram
- Deployment diagram

Diagrams¶

Behavioral Diagram:
It depicts the behavioral features of a system.
It deals with dynamic parts of the system.
It encompasses the following diagrams:
- Activity diagram
- State machine diagram
- Use case diagram

Diagrams¶

Interaction diagram:
It is a subset of behavioral diagrams.
It depicts the interaction between two objects and the data flow between them.
Following are the several interaction diagrams in UML:
- Timing diagram
- Sequence diagram
- Collaboration diagram

UML Architecture¶

Software architecture is all about how a software system is built at its highest level.
It is needed to think big from multiple perspectives with quality and design in mind. The software team is tied to many practical concerns, such as:
The structure of the development team.
The needs of the business.
Development cycle.
The intent of the structure itself.

UML Architecture¶

Software architecture provides a basic design of a complete software system.
It defines the elements included in the system, the functions each element has, and how each element relates to one another.
In short, it is a big picture or overall structure of the whole system,
- how everything works together

UML Architecture¶

To form an architecture, the software architect will take several factors into consideration:
What will the system be used for?
Who will be using the system?
What quality matters to them?
Where will the system run?

UML Architecture¶

The architect plans the structure of the system to meet the needs like these.
It is essential to have proper software architecture, mainly for a large software system.
Having a clear design of a complete system as a starting point provides a solid basis for developers to follow

UML Architecture¶

Each developer will know what needs to be implemented and how things relate to meet the desired needs efficiently.
One of the main advantages of software architecture is that it provides high productivity to the software team. The software development becomes more effective as it comes up with an explained structure in place to coordinate work, implement individual features, or ground discussions on potential issues.
With a lucid architecture, it is easier to know where the key responsibilities are residing in the system and where to make changes to add new requirements or simply fixing the failures.

UML Architecture¶

a clear architecture will help to achieve quality in the software with a well-designed structure using principles like separation of concerns;
the system becomes easier to maintain, reuse, and adapt. The software architecture is useful to people such as software developers, the project manager, the client, and the end-user.
Each one will have different perspectives to view the system and will bring different agendas to a project. Also, it provides a collection of several views

UML Architecture¶

It can be best understood as a collection of five views:
Use case view
Design view
Implementation view
Process view
Development view

UML Architecture¶

center h:550px

UML Architecture¶

Use case view¶

It is a view that shows the functionality of the system as perceived by external actors.
It reveals the requirements of the system.
With UML, it is easy to capture the static aspects of this view in the use case diagrams, whereas it?s dynamic aspects are captured in interaction diagrams, state chart diagrams, and activity diagrams.

UML Architecture¶

Design View¶

It is a view that shows how the functionality is designed inside the system in terms of static structure and dynamic behavior.
It captures the vocabulary of the problem space and solution space.
With UML, it represents the static aspects of this view in class and object diagrams, whereas its dynamic aspects are captured in interaction diagrams, state chart diagrams, and activity diagrams.

UML Architecture¶

Implementation View¶

It is the view that represents the organization of the core components and files.
It primarily addresses the configuration management of the system?s releases.
With UML, its static aspects are expressed in component diagrams, and the dynamic aspects are captured in interaction diagrams, state chart diagrams, and activity diagrams.

UML Architecture¶

Process View¶

It is the view that demonstrates the concurrency of the system.
It incorporates the threads and processes that make concurrent system and synchronized mechanisms.
It primarily addresses the system's scalability, throughput, and performance.
Its static and dynamic aspects are expressed the same way as the design view but focus more on the active classes that represent these threads and processes.

UML Architecture¶

Deployment View¶

It is the view that shows the deployment of the system in terms of physical architecture.
It includes the nodes, which form the system hardware topology where the system will be executed.
It primarily addresses the distribution, delivery, and installation of the parts that build the physical system.

UML Diagrams Overview¶

The UML diagrams are categorized into
structural diagrams,
behavioral diagrams, and also
interaction overview diagrams.

UML Diagrams Overview¶

center h:500px

Structural Diagrams¶

Structural diagrams depict a static view or structure of a system. It is widely used in the documentation of software architecture. It embraces class diagrams, composite structure diagrams, component diagrams, deployment diagrams, object diagrams, and package diagrams. It presents an outline for the system. It stresses the elements to be present that are to be modeled.

Structural Diagrams¶

Class Diagram:

Class diagrams are one of the most widely used diagrams. It is the backbone of all the object-oriented software systems.
It depicts the static structure of the system.
It displays the system's class, attributes, and methods.
It is helpful in recognizing the relation between different objects as well as classes.

Structural Diagrams¶

Composite Structure Diagram:

The composite structure diagrams show parts within the class.
It displays the relationship between the parts and their configuration that ascertain the behavior of the class.
It makes full use of ports, parts, and connectors to portray the internal structure of a structured classifier.
It is similar to class diagrams, just the fact it represents individual parts in a detailed manner when compared with class diagrams.

Structural Diagrams¶

Object Diagram:

It describes the static structure of a system at a particular point in time.
It can be used to test the accuracy of class diagrams.
It represents distinct instances of classes and the relationship between them at a time.

Structural Diagrams¶

Component Diagram:

It portrays the organization of the physical components within the system.
It is used for modeling execution details.
It determines whether the desired functional requirements have been considered by the planned development or not, as it depicts the structural relationships between the elements of a software system.

Structural Diagrams¶

Deployment Diagram:

It presents the system's software and its hardware by telling what the existing physical components are and what software components are running on them.
It produces information about system software.
It is incorporated whenever software is used, distributed, or deployed across multiple machines with dissimilar configurations.

Structural Diagrams¶

Package Diagram:

It is used to illustrate how the packages and their elements are organized.
It shows the dependencies between distinct packages.
It manages UML diagrams by making it easily understandable.
It is used for organizing the class and use case diagrams.

Behavioral Diagrams¶

Behavioral diagrams portray a dynamic view of a system or the behavior of a system, which describes the functioning of the system.
It includes use case diagrams, state diagrams, and activity diagrams.
It defines the interaction within the system.

Behavioral Diagrams¶

State Machine Diagram:

It is a behavioral diagram.
it portrays the system's behavior utilizing finite state transitions.
It is also known as the State-charts diagram.
It models the dynamic behavior of a class in response to external stimuli.

Behavioral Diagrams¶

Activity Diagram:

It models the flow of control from one activity to the other.
With the help of an activity diagram, we can model sequential and concurrent activities.
It visually depicts the workflow as well as what causes an event to occur.

Behavioral Diagrams¶

Use Case Diagram:

It represents the functionality of a system by utilizing actors and use cases.
It encapsulates the functional requirement of a system and its association with actors.
It portrays the use case view of a system.

Interaction Diagrams¶

Interaction diagrams are a subclass of behavioral diagrams that give emphasis to object interactions and also depicts the flow between various use case elements of a system.
In simple words, it shows how objects interact with each other and how the data flows within them.
It consists of communication, interaction overview, sequence, and timing diagrams

Interaction Diagrams¶

Sequence Diagram:

It shows the interactions between the objects in terms of messages exchanged over time.
It delineates in what order and how the object functions are in a system.

Interaction Diagrams¶

Communication Diagram:

It shows the interchange of sequence messages between the objects.
It focuses on objects and their relations.
It describes the static and dynamic behavior of a system.

Interaction Diagrams¶

Timing Diagram:

It is a special kind of sequence diagram used to depict the object's behavior over a specific period of time.
It governs the change in state and object behavior by showing the time and duration constraints.

Interaction Diagrams¶

Interaction Overview diagram:

It is a mixture of activity and sequence diagram that depicts a sequence of actions to simplify the complex interactions into simple interactions.

UML Relationship¶

Relationships depict a connection between several things, such as structural, behavioral, or grouping things in the unified modeling language.
Since it is termed as a link, it demonstrates how things are interrelated to each other at the time of system execution.
It constitutes four types of relationships, i.e.,
dependency,
association,
generalization, and
realization.

UML Relationship¶

Dependency¶

Whenever there is a change in either the structure or the behavior of the class that affects the other class, such a relationship is termed as a dependency.
Or, simply, we can say a class contained in other class is known as dependency.
It is a unidirectional relationship.

UML Relationship¶

Association¶

Association is a structural relationship that represents how two entities are linked or connected to each other within a system.
It can form several types of associations, such as
one-to-one,
one-to-many,
many-to-one, and
many-to-many.
A ternary association is one that constitutes three links.
It portrays the static relationship between the entities of two classes.

UML Relationship¶

Association¶

An association can be categorized into four types of associations, i.e.,
bi-directional,
unidirectional,
aggregation (composition aggregation), and
reflexive,
such that an aggregation is a special form of association and
composition is a special form of aggregation.
The mostly used associations are unidirectional and bi-directional.

UML Relationship¶

Aggregation¶

An aggregation is a special form of association.
It portrays a part-of relationship.
It forms a binary relationship, which means it cannot include more than two classes.
It is also known as Has-a relationship.
It specifies the direction of an object contained in another object.
In aggregation, a child can exist independent of the parent.

UML Relationship¶

Composition¶

In a composition relationship, the child depends on the parent.
It forms a two-way relationship.
It is a special case of aggregation.
It is known as Part-of relationship.

UML Relationship¶

Aggregation vs Composition Relationship¶

Features	Aggregation Relationship	Composition Relationship
Dependency	In an aggregation relationship, a child can exist independent of a parent.	In a composition relationship, the child cannot exist independent of the parent.
Type of Relationship	It constitutes a Has-a relationship.	It constitutes Part-of relationship.
Type of Association	It forms a weak association.	It forms a strong association.
Examples	A doctor has patients when the doctor gets transfer to another hospital, the patients do not accompany to a new workplace.	A hospital and its wards. If the hospital is destroyed, the wards also get destroyed.

UML Relationship¶

Generalization¶

The generalization relationship implements the object-oriented concept called inheritance or is-a relationship.
It exists between two objects (things or entities), such that one entity is a parent (superclass or base class), and the other one is a child (subclass or derived class
These are represented in terms of inheritance.
Any child can access, update, or inherit the functionality, structure, and behavior of the parent.

UML Relationship¶

Realization¶

It is a kind of relationship in which one thing specifies the behavior or a responsibility to be carried out, and the other thing carries out that behavior.
It can be represented on a class diagram or component diagrams.
The realization relationship is constituted between interfaces, classes, packages, and components to link a client element to the supplier element.

UML Association vs. Aggregation vs. Composition¶

In UML diagrams, relationships are used to link several things. It is a connection between structural, behavioral, or grouping things. Following are the standard UML relationships enlisted below:
Association
Dependency
Generalization
Realization

UML Association vs. Aggregation vs. Composition¶

Association¶

Association relationship is a structural relationship in which different objects are linked within the system. It exhibits a binary relationship between the objects representing an activity. It depicts the relationship between objects, such as a teacher, can be associated with multiple teachers.
It is represented by a line between the classes followed by an arrow that navigates the direction, and when the arrow is on both sides, it is then called a bidirectional association. We can specify the multiplicity of an association by adding the adornments on the line that will denote the association.

UML Association vs. Aggregation vs. Composition¶

Association¶

A single teacher has multiple students.

bg right:50% h:180px

UML Association vs. Aggregation vs. Composition¶

Association¶

A single student can associate with many teachers.

bg right:50% h:180px

UML Association vs. Aggregation vs. Composition¶

The composition and aggregation are two subsets of association.
In both of the cases, the object of one class is owned by the object of another class;
the only difference is that in composition,
the child does not exist independently of its parent, whereas in aggregation,
the child is not dependent on its parent i.e., standalone.
An aggregation is a special form of association, and
composition is the special form of aggregation.

UML Association vs. Aggregation vs. Composition¶

center h:500px

UML Association vs. Aggregation vs. Composition¶

Aggregation¶

Aggregation is a subset of association, is a collection of different things.
It represents has a relationship.
It is more specific than an association.
It describes a part-whole or part-of relationship.
It is a binary association,
i.e., it only involves two classes.
It is a kind of relationship in which the child is independent of its parent.

UML Association vs. Aggregation vs. Composition¶

Aggregation¶

Here we are considering a car and a wheel example.
A car cannot move without a wheel.
But the wheel can be independently used with the bike, scooter, cycle, or any other vehicle.
The wheel object can exist without the car object, which proves to be an aggregation relationship.

center h:200px

UML Association vs. Aggregation vs. Composition¶

Composition¶

The composition is a part of aggregation, and it portrays the whole-part relationship.
It depicts dependency between a composite (parent) and its parts (children),
which means that if the composite is discarded, so will its parts get deleted. It exists between similar objects.

UML Association vs. Aggregation vs. Composition¶

Composition¶

the composition association relationship connects the Person class with Brain class, Heart class, and Legs class.
If the person is destroyed, the brain, heart, and legs will also get discarded.

bg right:50% h:400px

UML Association vs. Aggregation vs. Composition¶

Association	Aggregation	Composition
Association relationship is represented using an arrow.	Aggregation relationship is represented by a straight line with an empty diamond at one end.	The composition relationship is represented by a straight line with a black diamond at one end.
In UML, it can exist between two or more classes.	It is a part of the association relationship.	It is a part of the aggregation relationship.

UML Association vs. Aggregation vs. Composition¶

Association	Aggregation	Composition
It incorporates one-to-one, one-to-many, many-to-one, and many-to-many association between the classes.	It exhibits a kind of weak relationship.	It exhibits a strong type of relationship.
It can associate one more objects together.	In an aggregation relationship, the associated objects exist independently within the scope of the system.	In a composition relationship, the associated objects cannot exist independently within the scope of the system.

UML Association vs. Aggregation vs. Composition¶

Association	Aggregation	Composition
In this, objects are linked together.	In this, the linked objects are independent of each other.	Here the linked objects are dependent on each other.
It may or may not affect the other associated element if one element is deleted.	Deleting one element in the aggregation relationship does not affect other associated elements.	It affects the other element if one of its associated element is deleted.

UML Association vs. Aggregation vs. Composition¶

Association	Aggregation	Composition
Example: A tutor can associate with multiple students, or one student can associate with multiple teachers.	Example: A car needs a wheel for its proper functioning, but it may not require the same wheel. It may function with another wheel as well.

UML- Association¶

Association is the semantic relationship between classes that shows how one instance is connected or merged with others in a system.
The objects are combined either logically or physically.
Since it connects the object of one class to the object of another class, it is categorized as a structural relationship

UML- Association¶

Following are the constraints applied to the association relationship
{implicit}: As the name suggests, the implicit constraints define that the relationship is not visible, but it is based on a concept.
{ordered}: It describes that the set of entities is in a particular way at one end in an association.
{changeable}: The changeable constraint ensures that the connections between several objects within a system are added, improved, and detached, as and when required.
{addOnly}: It specifies that any new connection can be added from an object located at the other end in an association.
{frozen}: The frozen constraint specifies that whenever a link is added between objects, it cannot be altered by the time it is activated over the connection or given link

Reflexive Association¶

In the reflexive associations, the links are between the objects of the same classes.
In other words, it can be said that the reflexive association consists of the same class at both ends.
An object can also be termed as an instance.

Reflexive Association¶

The vegetable class has two objects, i.e., onion and eggplant. According to the reflexive association's definition, the link between the onion and eggplant exist, as they belong to the same class, i.e., vegetable.

bg right:50% h:550px

Directed Association¶

The directed association is concerned with the direction of flow inside association classes.
The flow of association can be shown by employing a directed association.
The directed association between two classes is represented by a line with an arrowhead, which indicates the navigation direction.
The flow of association from one class to another is always in one direction

Directed Association¶

It can be said that there is an association between a person and the company.
The person works for the company.
Here the person works for the company, and not the company works for a person

bg right:50% h:190px

UML-Dependency¶

Dependency depicts how various things within a system are dependent on each other.
In UML, a dependency relationship is the kind of relationship in which a client (one element) is dependent on the supplier (another element).
It is used in class diagrams, component diagrams, deployment diagrams, and use-case diagrams, which indicates that a change to the supplier necessitates a change to the client.

bg right:40% h:170px