Scribd
Upload
3 views

Lecture Software Modelling - UML 1

Uploaded by

Laiba Anwaar
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
3 views

Lecture Software Modelling - UML 1

Uploaded by

Laiba Anwaar
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/ 16

Lecture

-19
University of Management & Technology
School of Systems and Technology

Software Engineering
CC-2101

Software Modelling by using


UML
Context Models & Interaction
Models
Somerville | Ch-5 (Pg.
139)
What is System modeling?
• System modeling is the process of developing
abstract models of a system, with each model
presenting a different view or perspective of that
system.

• System modeling has now come to mean representing


a system using some kind of graphical notation,
which is now almost always based on notations in the
Unified Modeling Language (UML).

• Systemmodelling helps the analyst to understand


the functionality of the system and models are used
to communicate with customers.
Unified Modelling Language (UML)
• UML (Unified Modelling Language) is a standard language
for specifying, visualizing, constructing, and
documenting the artifacts of software systems.

• UML stands for Unified Modelling Language.

• UML is different from the other common programming


languages such as C++, Java, COBOL, etc.

• UML is a pictorial language used to make software


blueprints.

• UML can be described as a general-purpose visual


modelling language to visualize, specify, construct, and
document software system.
System perspectives
• An external perspective, where you model the
context or environment of the system.

• An interaction perspective, where you model the


interactions between a system and its
environment, or between the components of a system.

• A structural perspective, where you model the


organization of a system or the structure of the data
that is processed by the system.

• A behavioral perspective, where you model the


dynamic behavior of the system and how it responds to
events.
UML diagram types
• Activity diagrams, which show the activities involved in a process or
in data processing .

• Use case diagrams, which show the interactions between a system


and its environment.

• Sequence diagrams, which show interactions between actors and


the system and between system components.

• Class diagrams, which show the object classes in the system and
the associations between these classes.

• State diagrams, which show how the system reacts to internal and
external events.

• Collaboration diagrams, another form of interaction diagram. It


represents the structural organization of a system and the messages
sent/received.
Context models
• Context models are used to illustrate the
operational context of a system - they show
what lies outside the system boundaries.

• Social and organisational concerns may affect


the decision on where to position system
boundaries.

• Architectural models show the system and its


relationship with other systems.
The context of the Hospital system – An example
Interaction models
• Modeling user interaction is important as it helps to
identify user requirements.

• Modeling system-to-system interaction highlights the


communication problems that may arise.

• Modeling component interaction helps us understand


if a proposed system structure is likely to deliver the
required system performance and dependability.

• Use case diagrams and sequence diagrams may be


used for interaction modelling.
Activity diagrams
• Activity diagram is basically a flowchart to represent
the flow from one activity to another activity.

• The activity can be described as an operation of the


system.

• Draw the activity flow of a system.

• Describe the sequence from one activity to another.

• Describe the parallel, branched and concurrent flow


of the system.
Activity diagrams -
Examples

Elements

⮚ Activities

⮚ Association

⮚ Conditions

⮚ Constraints
Use case modeling
• Use cases were developed originally to support
requirements elicitation and now incorporated into
the UML.
• Each use case represents a discrete task that
involves external interaction with a system.
• Actors in a use case may be people or other systems.

• Represented diagrammatically to provide an


overview of the use case and in a more detailed textual
form.
Use Case Diagram
– Shapes &
Symbols

By: Dr. Arfan


Arshad
Use cases (Examples)
Sequence diagrams
• Sequence diagrams are part of the UML and are
used to model the interactions between the actors
and the objects within a system.

• A sequence diagram shows the sequence of


interactions that take place during a particular use
case or use case instance.

• The objects and actors involved are listed along the


top of the diagram, with a dotted line drawn
vertically from these.

• Interactions between objects are indicated by


annotated arrows.
Sequence diagram for Student registration
Thankyou
Q&A

You might also like