Good Buy, Inc. (a fictitious company) sells a variety Of consumer products through its Web site, good-buy.com.Good Buy's IT infrastructure consists of a front-end Web server that interacts with customers and a back-end ERP system that manages the inventory and performs other typical ERP functions. The sales order process begins when a customer logs on to the good-buy.com Web site. The Web server requests the Current Good Buy online catalog from the ERP System, which sends the catalog to the Web server and the server displays it to the customer. The customer selects the items and quantities that he wants to purchase; the Web server edits the customer input for accuracy (e.g., ensures that all required fields have been selected or filled in) and sends this list on to the ERP system, where the requested quantities of inventory are allocated for the sale. The ERR sends back to the Web server the quantities that have been allocated, and the Web server displays this information on the customer's screen. The customer verifies that the order is correct and completes the sale by entering his shipping and credit card information. The Web server edits this data for accuracy (e.g., ensures that all required fields have been selected or filled in and that the length of the entered credit card number is correct) and sends the credit card information and amount of the sale on to the credit card company_ The credit card company sends back a verification number, and the Web server notifies the customer that the sale has been completed by displaying a confirmation number on the customer's screen. The Web server also notifies the ERP system that the sale has been completed, and the CRP system changes the status of the inventory from allocated to sold, prints a picking ticket or packing slip in the warehouse, and records (on the enterprise database) a sale and an account receivable from the credit card company,

CentralRisk Insurance Company

CentralRisk Insurance Company of Indianapolis, Indiana, processes its automobile insurance polices on a batch-oriented computer system with magnetic disk storage. Customers send requests for auto insurance into the Asheville sales Office, where sales clerks prepare policy request forms. They file a copy of the form and forward the original to the input preparation section, where data entry clerks use PCs to key and key-verify the data contained on the documents to a disk (policy requests).

Each evening computer operations retrieves the policy request data from the network edits the data on the computer for accuracy (e.g... all required fields completed), sorts the data in policy number sequence, and prints a summary report listing the edited policy requests (there is an error routine, not described here, for those requests that do not pass the computer edits). The summary report is sent to the sales Office. Where the sales clerks compare the report to the copy of the policy request form that they previously filed, if everything checks out, they notify computer operations to go ahead with processing When notified, computer operations processes the correct policy request data against the policyholder master data to create a new policy record. Each evening, a disk, which was created during the processing run, is used to print premium notices that are sent to the customer,

Figure 1: Physical DFD

Figure 2: Logical DFD

Flow Chart

a. Prepare a table of entities and activities for Good Buy, Inc. or CentralRisk Insurance Company.

b. Construct a context diagram based on the table you prepared in part (a). Use Microsoft Visio or other diagraming software.

Customer Email acknowledgement Annotated picking ticket (copy 2)-paper 3.0 Warehouse Customer telephone order Picking ticket (2-part) 1.0 Sales office - Annotated picking ticket (copy 1) Packing slip (copy 1) Carrier 4.0 Shipping Order data Order acceptance 2.0 Computer Packing slip (copy 2). Annotated picking ticket (copy 1)-paper Inventory master data-disk Customer master data-disk Accounts receivable master data-disk Customer Monthly electronic statement Service request Contract (copy) Contract file 1.0 Prepare and record contract 3.0 Prepare monthly statements Accounts receivable master data 2.0 Record hours worked Hours worked file Hours worked report Contracts not billed report Operations office Sales office CENTRAL SALES OFFICE Customer Customer order Key order Accepted order Log order Compare Clerk's log Daily event log Error routine not shown CORPORATE OFFICE 1 + I Review order, check credit, log order Check inventory, record order, print packing slip Warehouse COMPUTER Accounts receivable master data System log Customer master data Sales arder master data hventory master data Printed at regional warehouse Print daily event log (at the end of each day) Daily event log Record shipment Sales journal I REGIONAL WAREHOUSE WAREHOUSE SUPERVISOR Warehouse Filled order Enter order number and quantities shipped Accepted input Filled order Filled orders \N,