5CI002

Systems Design
Input Output Descriptions
data design
Updates and Enquiries

Learning outcomes

To understand what inputs and outputs and their

descriptions are
To understand the purpose and where inputs
and outputs fit in the design process
To identify and describe inputs and outputs from
DFDs
To understand what updates and enquiries are
To identify updates and enquiries from DFDs
2

Inputs and Outputs

Input/output context:
What are the main stages in data design?

We must cover 5 main stages:

1) Pinning down key inputs and outputs
2) Performing normalisation on the I/Os
3) Rationalising the 3NF tables
4) Creating the required Logical Data Structure
5) Setting up the database tables and links

INPUT/OUTPUT DESCRIPTIONS
Where do they fit in Systems design?
Current
Logical
DFDs

I/O
Descriptions

Required
Logical DFDs
User Views/
Roles

Screen Design: menus,

dialogues, displays.
Reports
5

What are inputs and outputs?

Student

input
1

output

Process
student results

Inputs (to the system) data flow from an entity to a process

Outputs (from the system) data flow from a process to an entity
Note Data flows from and to data stores are not inputs and outputs
6

What is the purpose of

Input Output descriptions?
They

provide more details about

the data flows between processes
and external entities on DFD
diagrams
What data is being input to the
system and what is being output
7

Input Output Descriptions

Developed using DFDs as a basis

Lists all the data items in each data flow

that crosses the system boundary.

Covers screen displays (both for input and

output) & printed reports.

Precedes the design of screens & reports.

8

What information is held in the data flow booking?

Booking (input)

D3

a
Customer
Booking
confirmation

(output)

1.3

Customer
Customer details
(not I/O)

Create Confirmed
Booking
Booking details
(not I/O)
D1 Booking Detail
9

Input/output (I/O) Description

5CI002 Input Output Descriptions

10

Contents of Input-Output Entry

From: Either the Process or External
Entity.
To: Either the Process or External
Entity.
Data Flow Name: As it appears on
the DFD
Data Content: The items that make
up the data flow name/description.
Comments: Anything that aids
comprehension.

11

How do we pin down the I/Os?

Firstly create a set of DFDs which
correctly show the required system
From the Context DFD identify the data
flows which enter and leave the system
these are the input and output flows
For each I/O flow make sure you have a
full list of attributes all the data items
which make up that flow

Getting the attributes of the I/O

flows

For each I/O flow get hold of a sample

document if possible

For each of the sample documents;

Ignore

all data items which dont change for

example heading
List the names of all variable data items

Example 1: A simple Context DFD for a

mail order system
Customer

Customer

order
invoice
TOOLS-R-US
Mail order system

Monthly
statement

What are the I/O flows?

Customer

Task: Complete the I/Os descriptions

table for the context DFD diagram
Customer

order

TOOLS-R-US
Mail order system

From

To

Customer

invoice

Monthly
statement
Data flow
name

Customer

Data content

Comments

15

Example 2: A level 1 DFD for

purchase orders
D3
Purchaser
Purchase
order quantity
(input)

1.1

Product
Product details
(not I/O)

Create Proposed
Purchase Order
Purchase order
details (not I/O)
D1 Purchase Order
16

I/O Descriptions - Example 2

17

Example 3: What Input-Output descriptions will be needed?

1
A s s is t a n t

M e m b e r D e t a ils

A d d /
A m e n d
M e m b e r s h ip

M e m b e r N o

A s s is t a n t

M e m b e r D e t a ils

4
D 1

M e m b e r

M e m b e r D e t a ils

R e tu rn
V id e o

R e t u r n V id e o

A s s is t a n t

V id e o T o B e
R e tu rn e d

D a te R e tu rn e d ,
S ta tu s
M e m b e r D e t a ils
3
A s s is t a n t

I s s u e V id e o

V id e o T o
B e Is s u e d

Is s u e
L o a n

V id e o N o

D 2

V id e o

V id e o D e t a ils

A d d /
A m e n d
V id e o

V id e o D e t a ils

R e tu r n D a te ,
S ta tu s
O v e r D u e L o a n s
D 1

A s s is t a n t

M e m b e r

M e m b e r s w it h
O v e rD u e L o a n s

5
C re a te
L o a n O ve r
D u e R e p o rt

L o a n O ve r D u e

C u s to m e r

18

VIDEO EXAMPLE 3

19

Updates and Enquiries

20

What are updates and enquiries?

1

Update
Process
student results

Enquiry

D1

Student details

Updates (updating a data store with data) data flow from

a process to a data store
Enquiries (enquiring about data stored) data flow from a
data store to a process
Note data flows to and from entities are not updates and
enquiries

An example
customer

order
1
process
orders

orders
*

D1

custdetails

sales details
D2

Customers

customerdetails

Sales

D3

sales details

products

product details
Process
invoices
*

sales details

paymentrequest

customer

account details
provide
monthly
statements

customer
details

Updates and enquiries

From the dfd it is possible to see updates
and enquiries for the proposed system.
Each process updates/enquires.
Process 1:
reads customer details
updates customer details (balance)
Updates sales details

Process 2:
Reads sales details
Reads customer details
Reads product details
(Prints invoice)

Process 3:
Reads sales details
Reads customer details
(Prints monthly account)

Summary

I/O Descriptions - created for data flows that cross the system
boundary

They list all the data items contained in each flow

Are used later to define how system interfaces with the

outside world (dialogue design and report design)

I/O descriptions MUST be written before designing the User

Interface
Updates show data that is stored

Enquiries show data that is retrieved

25