G data models a data flow diagram the data flow

This preview shows page 11 - 16 out of 24 pages.

G. Data Models a. Data flow diagram - The data flow diagram (DFD) depicts how the information is to actually flow, step by step, and not just in general formatting, but the actual process from beginning to end. By using the DFD, PEP can have a visualization of how the work is to flow not only within the IT system, but also within the confines of the daily business practices, such as from one department to the next, as well as the creation of the required monthly reports. 11
b. Use Case Diagram – will better demonstrate how the information being processed is routed the current system, it will also highlight where changes can be made in an effort to increase productivity and aid in the elimination of delays. H. Process Models In order for PEP to make a more informed decision about what requirements they would need to in order to successfully launch this upgrade BBISAC has provided three processing models. These models detail the processing of information that leaves no room for misinterpretation to the analyst and the user of the system. a. Structured English - this tool is used to describe the sequence, selection and iteration involved in the process. The following examples show how the data will flow: REPEAT IF dimensions not OK Reject product ELSE (dimensions ok) 12
IF mechanical test OK IF electrical test OK Pass product ELSE (electrical test not ok) Repair product ENDIF ELSE (mechanical test not ok) IF electrical test OK Repair product ELSE (electrical test no ok) Repair product ENDIF ENDIF ENDIF UNTIL No more Product Reports in batch b. Decision Table – is a matrix table that displays a myriad of alternatives and payoffs for a set of decisions made by the system. This example contains the same information used in the Structured English format: Alternative s Dimensions Mechanical Test Electrica l Test Payof Pathway 1 Y Y Y Pass Pathway 2 Y N Y Repair Pathway 3 Y Y N Repair Pathway 4 Y N N Reject Pathway 5 N - - Reject 13
c. Decision Tree – a graphical representation that shows a technique for estimating the expected values of each yes/no decision point. I. System Design Specification 1. Output Layout PEP works off of a monthly reporting schedule, these reports include every department, however their main desire is to keep informed of how the invoices are maintained and the collection of customer payments. These functional requirements for the new system will briefly describe the systems core functionality of proposed solution as far as information received from the system, information input into the system and how the information is processed. a. Output requirements 1. Monthly Invoicing Report – this report will display the current status from the Marketing department as 14
they maintain the product codes and pricing used by the invoicing database on the 15th of each calendar month. 2. Accounts Receivable Report - Customer payments, which are received in lump sum payments, are due to PEP by the 10th of each month. Payments are processed through the Accounts Receivable (AR) department. AR is responsible for updating customer account records once payments are received.

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture