INT22ISD IS Development

Suggested Solutions Data Flow Diagrams (tutorial questions)

Question 1

(a) Partial level 0 diagram is

acc# + amount

customer 3. Cheque
Cashing
System

amount + acc-balance
+ acc#
amount
valid acc# + amount

Diagram 3 (DFD) 3.2 update

3.1 customer
acc# + amount enter balance
data
(customer) valid acc# + amount
master file
3.3
produce
transactio
amount + acc- n acc-balance
balance + acc# slip
 (b)
Diagram 3.1 ( DFD)

Daily tally totals file daily totals

(experimenters)

history
totals
observations
3.1.2
produce
reports

Hybrid master
file
3.1.1 updated
tally totals
updated
totals summary
daily report
exp.
report

(experimenters)
 (c) Diagram 2 ( DFD)

(vendor) new game

2.1 Create
Software
description
skeleton letter
software
description

software descriptions
skeleton letter

software
description 2.2
Merge
letter

merged letter
mailing list

(game 2.33. Edit

Edit client details
buyer: merged
merged
client) letter
letter
personalized
letter

Note: Both the data stores mailing list and skeleton letter could be considered external
to this diagram thus be represented as (mailing list) and (skeleton letter) respectively

or

skeleton letter mailing list

(d) A partial diagram 2 is shown below (only process 2.1 is shown, not process 2.2
which would be presents in the diagram).

purchase
parts /invoice request
(purchasing
(supplier) office)

2.1
unordered parts + Inventory
invalid invoice system parts unavailable slip

payments requisition
(shop
floor)
 Note: The data flow appearing italics is revealed through the narrative for question
2.

Diagram 2.1 DFD (from question 1d and question 2)

That part of the diagram in italics is from the narrative for question 2
parts/invoice
(purchasing
(supplier) office)
orders

purchase
order details request
unordered
parts +
payments 2.1.2
invalid 2.1.1
invoice create
check in
new qty purchas
received
e
goods
payment details request
part
details

General ledger inventory

exisiting
stock
levels new stock
outstanding levels
requisitions filled req. file
2.1.3.fill
shop
floor filled requisition
requisitio
outstanding req. file
n
requisition
(shop floor)

unfilled requisition
parts unavailable slip

Comments:

There are many outstanding issues that need to be resolved.

For example:
 Should general ledger be considered external to this DFD? If it is a data store then it
should be internal to the system. In other words you would need to identify processes
(relevant to what you are modeling) that use data from this data store. Clearly such
processes exist but perhaps they are part of the accounting function and are external to
the inventory system. If this is the case then it can be represented as being external
(and perhaps named (Accounting)). A similar argument could be used when
considering the Orders data store.

What happens to the filled requisitions?. Currently they are stored in a data store.
Perhaps there is a reporting process that uses this data?

This data flow diagram could now be levelled. Process 2.1.1 (check in received
goods) and process 2.1.3 (fill shop floor requisition) appear quite complex (i.e. there
are several data flows in and out of each). A suggested diagram 2.1.1 and diagram
2.1.3 are shown below.

Diagram 2.1.1 (check in received goods)

(orders)

(supplier) order
parts/invoice

2.1.1.1 valid parts

validate
invoice
unordered parts
+ invalid invoice 2.1.1.3
update
inventory
valid invoice

payment
new qty
2.1.1.2
prepare
payment

payment details
(inventory)

(oustanding
(general ledger) req. file)
 Diagram 2.1.3 (fill shop floor requisition)
(inventory)
unfilled existing
requisition stock levels

new stock
levels
(outstanding req.
file) 2.13.1 Check valid
parts requisition
outstanding availability
requisition

2.1.3.2
requisition Check parts
parts out of
unavailable slip inventory

(shop floor)
 Question 3

From narrative 1

Context diagram
order

Customer purchase order

invoice
Supplier

Universal Inc
goods

Note: only two external entities are shown. Most of the narrative is talking about
what happens within Universal Inc

Level 0 Data flow diagram

It is easiest to consider each of the departments to a be a major process

i.e. order processing, warehouse shipping and purchasing

Customer

order shipping request

invoice 2.
1. order
warehouse
processing
shippling
shipping notification

goods
low stock levels
low stock notification
notification

goods received
receipt

3. purchasing Supplier

purchase order

Note: You could have included a data flow from warehouse shipping to customer
showing the ordered goods being delivered. This would also have to appear on the
context diagram. However it the invoice that is important.

Narrative 2
 This will result in the levelling of process 1, so you are now drawing diagram 1,
Order processing. It is at this level that the data stores begin to appear
Note that is may be necessary to modify the existing context and level zero DFDs also

Diagram 1 [any new data flows that will affect the existing context and level 0 DFD
are shown in italics]

1.5
(customer) EE customer payment + invoice#+ details update
custome
r
order account level account
invalid order
Validate updated account
Order level

customer file
valid order

new
account
level
unfilled orders valid orders

1.2
order details
prepare 1.3
shipping prepare
requests invoice

shipping shipping
request notification invoice

(customer) EE
low inventory notes

prepare
low stock
low inventory notes
notification

(warehouse shipping) low stock (purchasing)

There are many commentslevels
that can be made regarding diagram 1.
notification
What happens to the stored low inventory notes? Do they just accumulate?
The process 1.4 prepare low stock notification low stock to be independent of the other
seems
notification
other processes

The context and level 0 DFD have to be re-drawn to include some of the extra
information from diagram 1. They are shown below.
 order

Customer purchase order

invoice
Supplier

Universal Inc
invalid order goods

customer payment + invoice#+ details Customer

customer payment + invoice#+ details

Customer

order shipping request

invoice 2.
1. order
warehouse
processing
shippling

shipping notification

invalid order

goods
low stock levels
low stock notification
notification

goods received
receipt

3. purchasing Supplier

purchase order

Narrative 2 part (ii) --- Further information about the warehouse shipping department

We will now introduce diagram 2 warehouse shipping, any new components are in
italics

shipping notice (customer) EE

(order processing) +
goods
shipping request

2.1
Ship
goods
 stock levels

shipping notice
copy

inventory

new stock levels

shipping notices

shipping notices current stock

details Update
inventory

2.3 goods
Produce
current inventory reports
listing

weekly shipping
(supplier) EE
notice

(management) EE

Note: the above will have an influence on both the level 0 DFD and the context
diagram. There is new information.

See next page

Updated Context diagram and Level 0 DFD

Context diagram

There is an extra external entity, Management. There are some extra data flows

order

Customer purchase order

invoice
Supplier

Universal Inc
invalid order goods

Customer
 shipping notice
and goods
weekly shipping report

Management customer payment + invoice#+ details

current inventory
listing

Level 0 Data Flow Diagram

Management

customer payment + invoice#+ details

weekly shipping
report
Customer
current inventory
listing

order shipping request

invoice 2.
1. order
warehouse
processing
shippling
Supplier
3. purchasing shipping notification
low stockgoods
levelsreceived
purchase
notification order
receipt goods
invalid order

shipping notice
and goods low stock
notification

Customer