ROHANI BINTI ABU BAKAR

SYSTEM BOUNDARIES FAKULTI KOMPUTERAN

UNIVERSITI MALAYSIA
(CONTEXT DIAGRAM AND USE CASE DIAGRAM) PAHANG AL-SULTAN
ABDULLAH
What Does Meant By System
Boundary?
There TWO different boundaries to understand:
1. System Boundary – When defining the system boundary, a decision has
to be made. Which aspects pertain to the system to be developed (e.g
function) and which aspects belong to system context.
2. Context Boundary – When defining the context boundary, the question
to be answered is Which aspects pertain to the system context (e.g:
have a relation to the system to be developed) and which aspects are
part of the irrelevant environment?
Now, Where Do We Are?
Two Major Approaches in Structuring the
Requirements
Structural Approach Object Oriented Approach
• Context Diagram • Use Case Diagram
• Data Flow Diagram (Level O) • Use Case Descriptions
• Decompose DFD Level-n • Activity Diagram
• Sequence Diagram
• Class Diagram
• …..
Deliverables and Outcomes
Process Structured
Context Diagram
Modellin DFD Level 0
g Approach
Decompose Level n

Use Case Diagram

Object Oriented Use Case Descriptions
Approach Activity Diagram
Sequence Diagram
Where we are?

1. CONTEXT DIAGRAM
2. USE CASE DIAGRAM
What is a Context Diagram
1. Outline how external entity interact
with the internal software system.
2. It is high level diagram – Don’t go
into the details of in’s and out’s.
3. It’s consist of system/product name,
external entity or agent, flow line (in
and out), as well as data input and data
output.
 Sample of Context Diagram -
Components
External
Entity – can
be users,
external
system,
hardware,
API’s and etc

Data in/out System

(from/to) Name
system - (normally
Nouns marked as 0
on the top)
Exercise 1 – Find the Error
 Why Context Diagram?
Show the scope
Easy to draw and
and boundaries of No technical
amend – limited
system at the knowledge require
notation
glance

Benefit to wide
Easy to expend – range of audience
by adding level – no require prior
information
How to Create Context Diagram?
Establish the Identify and
Start initial list down all
boundary external entity

Complete Determine
End /review the data flows
diagram (in/out)
 Exercise 2 - Case Study
Consider the Open Registration (OR) System.
The objective of OR system is to allow student manage their course registration through out of
student study duration in the university. Student will automatic registered to the OR system when
their student status is active and registered for the current semester in the IMS system. All the
adding or withdrawal courses need to get approval from the Academic Advisor before student
able to print their timetable. If the Academic Advisor did not approve the request from the
students in certain period, the academic office will approve it behalf of the faculty.

Academic office is responsible to input the list of courses offered for two semester in the row
with their assigned lecturer and timetable. Course catalogue is the document which student
should refer to in order to plan for their own timetable for the course registration processes.

1. Based on given scenario, propose the Context Diagram to show the boundary of the propose
system.
Where we are?

1. CONTEXT DIAGRAM
2. USE CASE DIAGRAM
What is a Use Case Diagram
1. Shows the behavior or functionality of the system.
2. Simplest model to systematically document the functions of the system
from the user’s perspective.
3. Consist of a set of possible sequences on interactions between system and a
user (actor) in the particular environment.
4. This possible sequence that are related to a particle goal.
5. Use case diagram normally that are used in conjunction with one another:
i. Use case diagram
ii. Use case description
What is a Use Case Diagram
An effective use case diagram can help us in representing
1. Scenario in which the system or application interacts with people,
organizations or external systems.
2. Goals that the system or application helps those entities (actor) achieve.
3. The scope/boundaries of the system
When to Uses Use Case Diagram?
It is ideal for
1. Representing the goals of the system-user interactions
2. Defining and organizing functional requirements in a system.
3. Specifying the context and requirements of a system.
4. Modeling basic flow of events in a use case.
Use Case
Diagram
Compone
nts
 Use Case Diagram Components
Use Case(s) –
represent a function
or group of function
to achieve some
objective
The Actor(s)-
represent the role
Connections : NOT individual.
i. Solid line – shows that the actor is
involved in that particular system
function
ii. Extend relationship – by adding
new behaviors or actions (option).
iii. Include relationship – an
association between two use cases
where one use case uses the System Boundary – The
functionality contained in the other actor is outside of the
(share with other) system boundary.
Example of <<include>>
Relationship
Example of <<extend>>
Relationship
How to Identify the ACTOR?
These questions are useful for identifying Actors:
1. Who will supply, use, or remove information from the system?
2. Who will use the system?
3. Who is interested in a certain feature or service provided by the system?
4. Who will support and maintain the system?
5. What are the system's external resources?
6. What other systems will need to interact with the system under
development?
 How to Identify the USE CASE?Use Case
1. What are the goals that the Actor will attempt to achieve with the
system?
2. What are the primary tasks that the Actor wants the system to perform?
3. Will the Actor create, store, change, remove, or read data in the system?
4. Will the Actor need to inform the system about sudden external changes?
5. Does the Actor need to be informed about certain occurrences in the
system, such as unavailability of a network?
6. Will the Actor perform a system startup or shutdown?
Guideline/Steps for Finding USE
CASES
1. For each actor, find the tasks and functions that the actor should be able to
perform or that the system needs tha actor to perform. – Use case should
present a course of event that leads to a clear goal.
2. Name the use cases- should provide general description of the use case
function. The use case name should express what happens when an instance
of the use case is performed – descriptive and consistence.
3. Describe the use cases briefly by applying terms with which the user is
familiar. This makes the description less ambiguous.
The Identify all the
stakeholders and Determine what each
Steps to users who would
benefit by having the
stakeholder or user
needs – function(s)
Develop system

Use
Case For each potential
Carefully name each
Diagram communication need,
select the use cases
component of the use
case diagram
and actors.
 Exercise 3 - Case Study
Consider the Open Registration (OR) System.
The objective of OR system is to allow student manage their course registration through out
of student study duration in the university. Student will automatic registered to the OR
system when their student status is active and registered for the current semester in the IMS
system. All the adding or withdrawal courses need to get approval from the Academic
Advisor before student able to print their timetable. If the Academic Advisor did not approve
the request from the students in certain period, the academic office will approve it behalf of
the faculty.
Academic office is responsible to input the list of courses offered for two semester in the row
with their assigned lecturer and timetable. Course catalogue is the document which student
should refer to in order to plan for their own timetable for the course registration processes.

1. Based on given scenario, draw a use case diagram to show the boundary of the propose
system.