logo

Design of Database Teaching Model

Tips for creating a Data Flow Diagram (DFD) including the process-to-process, external entity-to-data store, process-to-data store, data store-to-data store, and external entity-to-external entity relationships. Also includes tips for labeling inputs and outputs and assigning identifiers to processes.

12 Pages868 Words18 Views
   

Added on  2022-09-18

Design of Database Teaching Model

Tips for creating a Data Flow Diagram (DFD) including the process-to-process, external entity-to-data store, process-to-data store, data store-to-data store, and external entity-to-external entity relationships. Also includes tips for labeling inputs and outputs and assigning identifiers to processes.

   Added on 2022-09-18

ShareRelated Documents
Running head: SYSTEM ANALYSIS AND DESIGN
Stage 2: Requirement Specification
Name of the Student
Name of the University
Author Note
Design of Database Teaching Model_1
1
SYSTEM ANALYSIS AND DESIGN
Table of Contents
Functional requirements..................................................................................................................2
Technical requirements....................................................................................................................4
System scope diagrams....................................................................................................................6
Context diagram...........................................................................................................................6
Use case diagram.........................................................................................................................7
Data flow diagram...........................................................................................................................8
Process models.................................................................................................................................9
Structure English.........................................................................................................................9
Decision table..............................................................................................................................9
Decision tree..............................................................................................................................10
Bibliography..................................................................................................................................11
Design of Database Teaching Model_2
2
SYSTEM ANALYSIS AND DESIGN
Functional requirements
The main objective of PEP is to track the invoice and inventory results and to ensure that all the
payments of customers are collected efficiently. With the use of functional requirements it will
become easy to design the new system that will enhance the overall business activities.
1. Output requirements
Invoicing report: Displays the status of the marketing department on the monthly basis.
Accounts receivable report: the payments processed by the customers are processed within the
Accounts receivable department.
Overdue report: Invoice associates are responsible for finding the accounts that haven’t paid the
money.
2. Input requirements
2.1. For invoice report the data that are needed includes o Customer Organization Name
Customer Street Address
Products Ordered
Product Ordered Date
Quantity
Product Pricing
2.2. Accounts receivable report requires certain data for proper processing. This includes:
Customer Organization Name
Quantity
Design of Database Teaching Model_3
3
SYSTEM ANALYSIS AND DESIGN
Products Ordered
Quantity Discount (Calculated Field
Electronic Invoicing (Check Box)
Electronic Payment (Check Box)
Product Pricing
Products Shipped
Product Ship Date
Amount Paid
2.3. For the purpose of managing data in overdue report, the data elements required are:
Customer Organization Name
Product Ordered Date
Amount Due (Calculated Field)
Amount 30 Days Overdue (Calculated Field)
Amount 60 Days Overdue (Calculated Field)
Amount Greater Than 60 Days Overdue (Calculated Field)
2% Overdue Amount (Calculated Field)
Product Ship Date
Quantity
Product Pricing
Calculated Price (Calculated Field)
3. Processing requirements
Design of Database Teaching Model_4

End of preview

Want to access all the pages? Upload your documents or become a member.

Related Documents
Preliminary Investigation Report on Proposal to Replace Customer Billing and Payment System Processes at PEP
|4
|944
|149

Preliminary Investigation Report
|4
|944
|180

Preliminary Investigation Report for PEP's Billing and Payment System
|4
|948
|53

Desklib - Online Library for Study Material with Solved Assignments, Essays, Dissertation
|9
|753
|140

System Design and Specification Assignment
|7
|804
|151

Billing System | Database Management System Assignment
|9
|1695
|157