Bài giảng Introduction to Software Engineering - Week 5: System Modeling - Nguyễn Thị Minh Tuyền
Week 5:
System Modeling
Nguyễn Thị Minh Tuyền
Adapted from slides of Ian Sommerville
Topics covered
1. Context models
2. Interaction models
3. Structural models
4. Behavioral models
5. Model-driven engineering
2
System modeling
£ Is the process of developing abstract models
of a system
p each model presents a different view or
perspective of that system.
£ Represent a system using some kind of
graphical notation
p based on notations in the Unified Modeling
Language (UML).
£ Helps the analyst to understand the
functionality of the system and models are
used to communicate with customers.
3
Existing and planned system models
£ Models of the existing system are used during
requirements engineering.
p Clarify what the existing system does and
p Are used as a basis for discussing its strengths and
weaknesses.
£ Models of the new system are used during
requirements engineering
p Help explain the proposed requirements to other system
stakeholders.
p Are used for discussing design proposals and for
documenation.
£ In a model-driven engineering process, it is possible to
generate a complete or partial system implementation
from the system model.
4
Model the interactions
between a system and its
System perspecenvironment, or between the
nts of a system
Model the conte
environment of t
system
external
perspective
interaction
perspective
System
behavioral
perspective
structural
perspective
del the organization
system or the
cture of the data
that is processed by the
system.
Model the dynam
behavior of the
system and how
responds to events.
5
NGUYỄN Thị Minh
UML diagram types
The UML has many diagram types and supports many different types of system model.
Five diagram types could represent the essentials of a system:
Activity diagram
Show the activities involved in a process or in data processing.
Use case diagram
Show the inteactions between a ytem and ts environment.
Sequence diagram
Show interactions between actors and the system and between system
components.
Class diagram
Show the object classes in the system and the associations between
these classes.
State diagram
7
Show how the system reacts to internal and external events.
Teamwork: 30 minutes
£ Each group chooses one of five diagrams in
previous slide: Activity diagram, Use case
diagram, Sequence diagram, Class Diagram, State
Diagram and make a presentation:
1. What is it ?
2. When we use it ?
3. What are main elements of this diagram ?
4. Give an example and explanation.
Use of graphical models
£ As a means of facilitating discussion about an
existing or proposed system
p Incomplete and incorrect models are OK as their role is
to support discussion.
£ As a way of documenting an existing system
p Models should be an accurate representation of the
system but need not be complete.
£ As a detailed system description that can be used
to generate a system implementation
p Models have to be both correct and complete.
9
Topics covered
1. Context models
2. Interaction models
3. Structural models
4. Behavioral models
5. Model-driven engineering
10
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.
11
System boundaries
£ System boundaries are established to define what
is inside and what is outside the system.
p They show other systems that are used or depend on
the system being developed.
£ The position of the system boundary has a
profound effect on the system requirements.
£ Defining a system boundary is a political judgment
p There may be pressures to develop system boundaries
that increase / decrease the influence or workload of
different parts of an organization.
12
The context of the Mentcare
system
«system»
Patient record
system
«system»
«system»
Admissions
system
Management
reporting
system
«system»
Mentcare
«system»
Prescription
system
«system»
HC statistics
system
«system»
Appointments
system
13
The context of the ATM system
<<system>>
Security system
<<system>>
Branch Accounting
<<system>>
Account DB
system
<<system>>
ATM System
<<system>>
Branch counter
system
<<system>>
Usage DB
Mantainance
system
Nguyễn Thị Minh Tuyền
14
Process perspective
£ Context models simply show the other systems in
the environment, not how the system being
developed is used in that environment.
£ Process models reveal how the system being
developed is used in broader business processes.
£ UML activity diagrams may be used to define
business process models.
15
Process model of involuntary detention
Transfer to
police station
[not available]
Confirm
detention
decision
Find secure
place
Transfer to
cre hopial
Inform
social care
[dangerous]
Inform
patient of
rights
Inform next
of kin
Update
register
Record
detention
decision
Admit to
hospital
dangerous]
«system»
Mentcare
«system»
Admissions
system
«system»
Mentcare
16
Topics covered
1. Context models
2. Interaction models
3. Structural models
4. Behavioral models
5. Model-driven engineering
17
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.
£ Two approaches to interaction modeling:
p Use case diagrams and
p sequence diagrams.
18
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.
19
Transfer-data use case
£ A use case in the Mentcare system
Transfer data
Medical receptionist
Patient record system
20
Tải về để xem bản đầy đủ
50 trang
20020
Free
Bạn đang xem 20 trang mẫu của tài liệu "Bài giảng Introduction to Software Engineering - Week 5: System Modeling - Nguyễn Thị Minh Tuyền", để tải tài liệu gốc về máy hãy click vào nút Download ở trên
File đính kèm:
- bai_giang_introduction_to_software_engineering_week_5_system.pdf
