BILLING AND PAYMENT SYSTEM 5
Stage02: Billing and Payment System
Stage2 Billing and Payment System
Introductionand Background
Inthe recent past, UMUC has been experiencing increased installationand service orders. These orders show an increased demand and callfor a manufacturing expansion for the related services. The increasedorders have been coupled with increased demand and expandedproduction of the related services. UMUC has welcomed increasedbusiness. Nevertheless, there are concerns about the length of timeof the existing process that can sustain and support a viable servicelevel. For the company to benefit from creating new payment andbilling system of the customers, a context diagram of how thepayments and billing are managed, are described below
Contextdiagram
A
VP, Business Admin
CFO
ccounts received
aretranslated as sales
Sales
Invoice Dept
Cust Billing
Acc Received
Cust Payment
Monthly Report
Microsoft Access Based Solution
Ordering and Shipping department
IT Dept
Monthlyreport
generatesinvoice
Accare transferred to ordering and shipping dept
Thecontext diagram describes the overview of how each of the entitiesnetwork with the new system whether by deriving system information ordistributing it. These entities intermingle and re described in thelarger boxes where the arrows present information flow. How they aredirected describes the transfer of information. Right in the middleis the primary system of UMUC.
Atparent level, there are two fundamental information entities sent bythe parent to UMUC information system. These are the accountsreceived and invoicing department. To begin with the billing andpayment procedure, a customer needs to supply information to theinvoicing and accounts collected department. When UMUC sends a bill,the parent makes an order where payment is made to the UMUC system.
Theprocesses are labeled correctly. The IT department access theMicrosoft access based solution after the central system invoices andreceive accounts of the customers. The entity then orders the productand prepares a monthly report which is then sent to the invoicingdepartment and finally to the admin.
Thecontext diagram adequately depicts the data flows and the systems. The reported data includes the financial information such as salesdata that may be needed by other departments for review. Therefore,we can say that the external entities are labeled and named correctlyusing nouns symbols
Diagram0
Startingwith customer payment entity information is sent, and registrationof data is made. At the marketing department, the only output data isthe sales information sent to generate a drop in the report. Thesales information is transmitted to make drop in the release process.Time is created for a given frame for payment, and billing and theoutput of the process are forwarded to the IT department.
Thenew system has been designed professionally based on technologicalstandards available today. Based on the initiatives done by thecompany, it is imperative to improve the security of the enterpriseto ensure that payment is secure. There is a proper arrow usage, andthus, the new system will be able to offer payment and bills optionto the customers under their account. As a result, this assists thecustomers to access the products and make purchases at any giventime.
Theexternal entities are properly labeled to ensure that these changesare achieved by integrationof different information from the users. The diagram is complete tomake sure that various departments are under a single financial tab
References
Dixit,J. B. (2007). Structuredsystem analysis and design.Firewall Media.
Rosenblatt,H. J. (2013). Systemsanalysis and design.Cengage Learning.
Scholz-Reiter,B., & Stickel, E. (Eds.). (2012). Businessprocess modeling.Springer Science & Business Media
Kendall,K. E., & Kendall, J. E. (2010). Systemsanalysis and design.Prentice Hall Press