Scribd
Upload
9 views

Topic 2 - Using OOP Concepts and UML Modelling

Uploaded by

n0233305r
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
9 views

Topic 2 - Using OOP Concepts and UML Modelling

Uploaded by

n0233305r
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 14

Using OOP Concepts

and UML Modelling


TOPICS 2
2.1 Introduction
• Unified Modelling Language (UML) is inherently object-oriented
modelling language and was designed for use in object-oriented
software applications.
• Software architects and developers should be familiar with general
concepts and methods of object-oriented analysis and design (OOAD)
and/or of the object-oriented development (OOD), and how those
were applied to UML itself.
• UML specifications use OOAD concepts which have no clear and
generally accepted definitions without providing own interpretations
or definitions of those concepts.
2.2 UML Diagrams
• General-purpose modelling language.
• Main aim of UML is to define a standard way to visualize the way a
system has been designed.
• Software system artifacts can be specified, visualized, built, and
documented with the use of UML.
• We use UML diagrams to show the behaviour and structure of a
system.
• We use UML (Unified Modelling Language) to visually represent and
communicate complex system designs
2.3 Types of UML Diagrams
UML is linked with object-oriented design and analysis. UML makes use
of elements and forms associations between them to form diagrams.
Diagrams in UML can be broadly classified as:
2.3.1 Structure UML Diagrams
2.3.1.1 Class Diagram: depict the static structure of a system by
showing system’s classes, their methods and attributes.
• 2.3.1.2 Object Diagram: An object diagram is similar to a class
diagram except it shows the instances of classes in the system.
• 2.3.1.3 Component Diagram: Component diagrams are used to
represent how the physical components in a system have been
organized.
• 2.3.1.4 Deployment Diagram: Deployment Diagrams are used to
represent system hardware and its software.
• 2.3.1.6 Package Diagram: A package diagram simply shows us the
dependencies between different packages and internal composition
of packages.
2.3.2 Behavioural UML Diagrams
2.3.2.1 State Machine Diagrams: A state diagram is used to represent
the condition of the system or part of the system at finite instances of
time. It’s a behavioural diagram and it represents the behaviour using
finite state transitions.
2.3.2 Behavioural UML Diagrams
2.3.2.2 Activity Diagrams: We use Activity Diagrams to illustrate the
flow of control in a system.
2.3.2 Behavioural UML Diagrams
2.3.2.3 Use Case Diagrams: Use Case Diagrams are used to depict the
functionality of a system or a part of a system.
2.3.2 Behavioural UML Diagrams
2.3.2.4 Sequence Diagrams: A sequence diagram simply depicts
interaction between objects in a sequential order i.e. the order in which
these interactions take place.
2.3.2 Behavioural UML Diagrams
2.3.2.5 Communication Diagram: A Communication Diagram (known as
Collaboration Diagram in UML 1.x) is used to show sequenced
messages exchanged between objects.

You might also like