Professional Documents
Culture Documents
Database Management Systems - CS403 Fall 2004 Assignment 01 Solution
Database Management Systems - CS403 Fall 2004 Assignment 01 Solution
01 (Solution)
Voucher Slip
Admission System
Accommodation system
Deposit Bank
Accommodation Form
Student vouchers
submit Dues
Level 0 DFD
List of Students
Vouchers slip
Bank
Application form Allocation
Update File
Vouchers Hostel
Allocation File
Student
Deposit
Student Record
Check for Applied
forms & merit list
Admission System Student
Hostel
Allocation file
List of available allocation
List of Students
Top positions
Cubicle allocation Cubicle data
Student
Check Mess
Allocation details
option
details of allocation
Voucher slip
Level 0 Diagram
Shows all the processes that comprise the overall system
Shows how information moves from and to each process
Adds data stores
Level 1 Diagrams
Shows all the processes that comprise a single process on the level 0 diagram
Shows in more detail the content of higher level process
Level 1 diagram may not be needed for all level 0 processes
External Entities
Receive info from system
Trigger system into motion
Provide new information to system
Like Customers, managers. Not clerks or other staff who simply move data
Data Stores
Internal to the system
Include in system if the system processes transform the data like Store, Add, Delete,
Update
Data stores can come in many forms
Hanging file folders
Computer-based files
Notebooks
Data cannot be moved directly from one store to another
Data cannot move directly from an outside source to a data store
Data cannot move directly from a data store to a data sink
Data store has a noun phrase label
Data Flows
Data in motion, moving from one place to another in the system
From external entity (source) to system
From system to external entity (sink)
From internal symbol to internal symbol, but always either start or end at a
process
A data flow has a noun phrase label
A data flow to a data store means update
Processes
Always internal to system
Must have at least 1 input data flow (to avoid miracles)
Must have at least 1 output data flow (to avoid black holes)
Should have sufficient inputs to create outputs (to avoid gray holes)
Perform computations (e.g., calculate grade point average)
Sort, filter or otherwise summarize data (identify overdue invoices)
Organize data into useful information (e.g., generate a report)
Activate other processes
Use stored data (create, read, update or delete a record)
General Rules for DFD
Inputs to a process are always different than outputs
Objects always have a unique name