IFSM 461: System Analysis and Design Stage 2 Requirements Report

This report details the Stage 2 requirements specification for a new billing and payment system for Precision Electronic Parts (PEP). It outlines functional requirements, including output, input, and processing needs for invoice, accounts receivable, and overdue reports. Technical requirements cover security, system control, performance, and business continuity. The report includes system scope diagrams like context and use case diagrams, data flow diagrams, and process models using structured English, decision tables, and decision trees. The aim is to improve business operations, especially in the ordering, shipping, and inventory management departments, with the goal of better tracking invoices, inventory results, and efficient payment collection.

Running head: SYSTEM ANALYSIS AND DESIGN
Stage 2: Requirement Specification
Name of the Student
Name of the University
Author Note

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

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

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

4
SYSTEM ANALYSIS AND DESIGN
3.1. Invoice process: In order to process the data for the purpose of generating invoice report it is
important to process all the data of the customers within the database on 15th of every month.
Once the data is processed it becomes easy to calculate the invoice.
3.2. Billing process: For processing the accounts receivable report is important to observe the
data that is managed within the invoice statements.
3.3. Payment process: payment process is carried out for the purpose of understanding the
overdue cases. For managing the business performance it is important to have proper control
over overdue reports.
Technical requirements
Security requirements:
Use of encryption: With the use of encryption it will become easy to protect the data stored
within PEP. This will also ensure that proper confidentiality is maintained.
Firewall implementation: Firewall will provide proper protection towards the network.
Access control: Access towards the system will be restricted from unauthorized users.
System control requirements:
Network administration: Proper control over the network is needed for protecting the data sets.
System performance monitoring: System performance must be monitored for avoiding issues.
Auditing: Every system must be audited for ensuring proper flow of activities.
Performance requirements:

5
SYSTEM ANALYSIS AND DESIGN
Accessible: the data are easily accessible by the users
Reliable: The user is capable of relying on the data for the purpose of executing the output.
Secured: the system is secured enough for data transactions.
Business continuity requirements:
Backup: Every data needs to be maintained with proper backup
Restart: whenever any issue is faced by the user it is important to restart the system
Recovery: Recovery is carried out in case of data loss.

6
SYSTEM ANALYSIS AND DESIGN
System scope diagrams
Context diagram

7
SYSTEM ANALYSIS AND DESIGN
Use case diagram

8
SYSTEM ANALYSIS AND DESIGN
Data flow diagram

9
SYSTEM ANALYSIS AND DESIGN
Process models
Structure English
Structured English is used for explaining the sequence, selection and iteration associated with a
process. For example:
If the customer buys 5 or more
Then give 2% discount
Else
If less than 5 No discount
End if
Decision table
Conditions 1-4 items
purchased
5-9 items
purchased
10-14 items
purchased
Customer Y Y Y
Due for 30 days N Y N
Due for 60 days N N Y
Actions No discount N N N
2% discount y

10
SYSTEM ANALYSIS AND DESIGN
5% discount y
10% discount
Decision tree

11
SYSTEM ANALYSIS AND DESIGN
Bibliography
Dennis, A., Wixom, B. H., & Roth, R. M. (2018). Systems analysis and design. John wiley &
sons.
Guariniello, C., & DeLaurentis, D. (2017). Supporting design via the system operational
dependency analysis methodology. Research in Engineering Design, 28(1), 53-69.
Huang, X. P., & Leng, J. (2019). Design of Database Teaching Model Based on Computational
Thinking Training. International Journal of Emerging Technologies in Learning (iJET), 14(08),
52-69.
Pedrycz, W. (2018). Granular computing: analysis and design of intelligent systems. CRC press.