Context

and Data Flow Diagram

Context Diagram
Context diagram is a high level representation of the business processes. It
defines the entities and their interaction in the system. This is one of the
important tools for stakeholders to understand the required process.
The objective of the system context diagram is to focus attention on
external factors and events that should be considered in developing a
complete set of systems requirements and constraints.
Building Blocks
Context diagrams can be developed with the use of two types of building
blocks:
Entities (Actors): labeled boxes; one in the center representing the system,
and around it multiple boxes for each external actor.
Represented

Name

as

Relationships: labeled lines between the entities and system

Represented as
Process:

Name

Achieve desired functionality for some specific business reason.

Represented

Number

as

Name

Data store: Collection of data which form starting point of a data model
and principal link between data model and process model
Represented

D1

as

Types of External Entities in Bide-A-While case

1) Active:

Entities which are dynamic to achieve purpose

Example: Customer, Receptionist and Manager

2) Passive: Static External entities that interact infrequently with the

system.

Example:

Quality assurance team, Audit manager etc.

3) Cooperative:
Example:

Entities that are used by system for desired outcome.

Internet Service Provider, Net Banking services

4) Autonomous: Entities that are separated from the system affecting

indirectly.
Example: Media partners, advertising agencies etc.

Context Diagram of Bide-A-While

Fig 1: Bide-A-While Electronic Reservation System Context

Diagram

Data Flow Diagram

Data Flow Diagram a graphical representation of the flow of data through the
system. This is an intuitive way to analyze data processed in the system
In this system there are three major processes. Below are the fragmented
processes (Fig: 2 to Fig: 4) and Fig 5 is the Level 0 Data Flow Diagram for
Bide-A-While Electronic Reservation System Project.

1] Process 1: Book A Reservation

UseCaseName:BookingaReservation

ID:UC1

Priority:High

Actor:Receptionist/Manager
Description:Customerrequestsforreservation,receptionist,managerchecksroomsavailabity
andbookstheroom.
Trigger:Customerenquiresaboutroom
Type:External
Normalcourse:Refertofig2,BookAReservation.
Inputs

Source

Outputs

Destination

1.Customername

Electronic
reservationofBide
AWhile

Reservation
confirmationdetails
suchasreservation
code,roomnoetc.

Customer

2.Address
3.Creditcarddetails
4.Occupancy

1.Book A Reservation

Fig 2: Bide-A-While Electronic Reservation System Fragmented Process 1Book A Reservation

2] Process 2: Change The Reservation (if there is any change from

Customer)

UseCaseName:Changethereservation

ID:UC2

Priority:High

Actor:Receptionist/Manager
Description:Customerrequeststochangereservation,receptionist,managerchecksnew
reservationavailability
Trigger:Customerrequestsforreservationchange
Type:External
NormalCourse:Refertofig3,Changethereservation
Inputs

Source

Outputs

Destination

1.Customername

Electronic
reservationofBide
AWhile

Reservation
confirmationdetails
suchasreservation
code,roomnoetc.

Customer

2.Address
3.Creditcarddetails
4.No.Ofpersons
5.Newarrivaland
departuredate

2.Change The Reservation

Fig 3: Bide-A-While Electronic Reservation System Fragmented Process 2Change The Reservation

3] Process 3: Generate The Bill

UseCaseName:Generatethebill

ID:UC3

Priority:High

Actor:Receptionist/Manager
Description:Manager/Receptionistgeneratesthebillforcustomerstay
Trigger:Billgenerationinitiated
Type:Temporal
Normalcourse:Refertofig4,Generatethebill
Inputs

Source

Outputs

Destination

Paymentdetails

Electronic
reservationofBide
AWhile

BideAWhile
Receipt

Customer

Creditcard,
NetBanking

Process 3: Generate The Bill

Fig 4: Bide-A-While Electronic Reservation System Fragmented Process 3

- Generate The Bill

Level 0 Data Flow Diagram:

The Level 0 DFD shows how the system is divided into 'sub-systems'
(processes), each of which deals with one or more of the data flows to or
from an external agent, and which together provide all of the functionality of
the system as a whole.

Fig 5: Bide-A-While Electronic Reservation System Level 0 Data Flow

Diagram

Limitations of Data Flow Diagrams

DFD are time consuming where analysts have to be in wait until entire
process is represented by management.
Physical considerations are not accounted in DFD.

References:
1. Systems Analysis and Design - Dennis. Wixom. Roth

2. http://en.wikipedia.org/wiki/System_context_diagram