2

Requirements Specification

UMGC

IFSM 461

Requirements Specification

Background:

The proposed system is an automated billing and payment system that will replace the manual process currently used at Precision Electronics Parts, Inc. The system will automate the billing and payment process and integrate with the company's existing inventory management system. The system will include automatic billing generation, electronic payment processing, and real-time billing and payment status reporting. The system will also include a customer self-service portal for viewing and paying bills (Shylesh,2017).

I. Functional Requirements.

a. Output requirements.

i. electronic payment confirmation: An electronic confirmation of payment that is sent to the customer upon completion of payment.

ii. Billing/payment report: A report that will be generated monthly that provides a breakdown of all billing and payments that were processed in that month.

iii. Payment status report: A report that will be generated on demand that provides the current payment status of a customer's account.

b. Input requirements.

i. Customer data: This includes the customer’s name, address, phone number, and other contact information.

ii. Payment information: This includes the payment amount, payment method, and payment date.

iii. Invoice data: This includes the invoice number, invoice date, and invoice amount.

c. Processing requirements.

i. Generate invoice: This process will generate an invoice based on the customer’s purchase data.

ii. Process payment: This process will process the payment information and update the customer’s account with the payment amount.

iii. Send payment confirmation: This process will send an electronic payment confirmation to the customer upon completion of payment.

II. Technical Requirements

a. Security requirements: The system must be secure and protect the data from unauthorized access.

b. System control requirements: The system must provide an audit trail of all transactions and must be able to be monitored and controlled.

c. Performance requirements: The system should be able to process payments promptly and should be able to generate reports quickly.

d. Business continuity requirements: The system should have backup and recovery processes in place to ensure that data is not lost in the event of a system failure.

III. System Scope Diagrams

a. Context Diagram: The diagram below shows the context of the system and the external entities that interact with the system.

Fig1. Context of the system and the external entities that interact with the system

Initial discussions with users about issues with the current system and the requirements for the new system are required as part of the process of developing the analytical framework by drawing and analyzing the context diagram. They are formally recorded alongside any identified system needs from prior research (Mall,2018).

b. Use Case Diagram: The diagram below shows the actors and use cases of the system.

IV. Data Flow Diagram

a. Data Flow Diagram: The diagram below shows the flow of data through the system.

Process Models

Structured English

If the customer account has an outstanding balance IF the payment method is a credit card

THEN process payment

THEN generate invoice

THEN process payment

ELSE IF payment method is electronic payment

References

Kramer, A. F. (2020). Physiological metrics of mental workload: A review of recent progress.  Multiple-task performance, 279-328.

Mall, R. (2018). Fundamentals of software engineering. PHI Learning Pvt. Ltd.

Roleda, M. Y., & Hurd, C. L. (2019). Seaweed nutrient physiology: application of concepts to aquaculture and bioremediation.  Phycologia,  58(5), 552-562.

Shylesh, S. (2017). A study of software development life cycle process models. In National Conference on Reinventing Opportunities in Management, IT, and Social Sciences (pp. 534-541).

image1.png

image2.png