Вы находитесь на странице: 1из 8

In documenting the first step could look at the Data Flow Diagram and document the Entity, Data

Flows, Processes and Stores. This would be valuable during development. I am documenting a more finished system. I can include a systems flow chart or some other means of showing the relationships, I can also document the input, output, database/files, and programs that make up the system. People have their own favorite way of doing this. This is just one possible way of doing it. Your textbook discusses other techniques that you may prefer.

Overview of Payroll System

The payroll system keeps accurate employee data stored in an easily accessible database. The system has the ability to update and maintain employee information and to generate required outputs including paychecks, reports to management and reports to the government. Each week, data on the current pay period is entered into the system and verified. This data is used to update the employee master file with appropriate additions, changes and deletions and to generate required output. Obviously a more detailed description would be done if I were actually documenting a system. I would include a systems flowchart at this point Sample documentation can include: Description/overview of system, systems flowchart, list of program in system, program descriptions, list of tables/files in system, file layouts and description, data dictionary for fields, list of reports in system and report layouts and description, list of screens in system and screen layouts and descriptions, controls. For each program the programmer could be asked to include program description, program specifications, logic flowchart, code, test data and sample run. Note if you are using a database such as Access, much of the documentation can be gotten from the structure of the database.

List of Programs
Program Code Name TMCDEDIT TMCDUPDT PAYCHK GOVTW2 Program Name Time Card Edit Program Time Card Update Program Paycheck Program W-2 Program Function Production: Edits time card information keyed in from the time card screen Production: updates current and YTD pay on Employee Master File (EMPMSTR) Production: Generates paychecks Generates W-2 forms at end of year Maintenance: Edits the screen transactions used to update the Employee Master File (EMPMSTR) Maintenance: Updates the Employee Master File (EMPMSTR)

Other report programs would be included EMPEDIT Employee Edit Program


Employee Update Program

Time Card Edit Program: TMCDEDIT

Production Program: This program edits time card information keyed in from the time card screen. Program Name: Input: Output: Functions: TMCDEDIT Time Card Edit Program Time Card Screen (TMCDSCR) Time Card Transactions Table (TMCDTRAN) Time Card Error Report (TMCDRPT) Edits input data according to the following specifications: Identification number is present, numeric with valid check digit Department is present and valid department Regular hours is present, numeric and not over 40 Continue with other fields that are to be edited Interactive with user: Messages are posted and corrections are edited User can determine that record cannot be corrected and send to the Time Card Error Report (TMDCRPT) Counts number of employees processed Counts number of transactions written to Time Card Transactions table (TMCDTRAN) Run weekly after time cards have been collected

Controls: Comments:

Tables in Payroll System

Table Code Name TMCDTRAN EMPMSTR Table Name Time Card Transactions Employee Master Type Trans Programs Output: TMCDEDIT Input: TMCDUPDT Master List programs using the table specifying Input, Output and I/O meaning both

Data Dictionary Record Description: TMCDTRAN (Time Card Transactions)

Database System: Table Code Name: Alternative Name(s): Organization: Primary Key: Alternate Key(s): Foreign Keys: Number records: Field Name Type Length Source Comments Identification Text 5 Screen: TMCDSCR Keyed in from Number screen Note that you want to provide information in the source to trace problems when they are found on the table. Comments should include format etc Payroll Database TMCDTRAN Time Card Transactions Database Table organized by primary key Identification Number Department Number Project Number

Data Dictionary Data Element Description: Identification Number

Database System: Field Name: Alternative name or Alias: Definition: Type: Length: Configuration: Default Value: Output Format: Source: Security: Standard Codes: Derivation Formula: Prompt/Column Header: Comments: Appears on: Payroll Database IDNO Identification Number Employee identification number generated by the company Text 5 If there is a particular code involved I would explain it here None Display Tell where the field originates Some of these things may not be needed if not applicable

List the files where this field exists

List of Screens in Payroll System Screen Documentation

Layout of the screen and explanation of each field on the screen

List of Reports in Payroll System

Layout of the report and explanation of each field in the report Explanation for both would include columns such as: Field, length, editing, source and comments If totals are included they should be described

Example Program: Payroll System

Project Brief Design a program that will accept as data input the hours worked and the hourly rate of an employee and calculates the overtime pay and gross pay. The program should display the hours worked, the net pay and the gross pay. Employees are paid time and a half for any hours worked over the basic forty. A structure chart has been developed for this system, showing the payroll system calling three procedures. Each procedure is numbered in the hierarchy. This general layout follows the idea of Input, Process and Output.

1.1 Definition of Problem

In XP, the user story serves the purpose of the problem statement and the specifications. The user story provided by the client was as follows: You are to design and implement a payroll system that should accept employee hours worked, compute net pay and record all the payroll data for subsequent processing. The system should prepare pay cheques and a payroll ledger, and maintain data on a sequential payroll file. Non-statutory deductions such as union dues and pension plans to be made. The payroll data are employee number, employee name, pay rate, and union member flag. The year-to-date total should contain earnings, federal tax, pension plan, and union dues To accomplish these tasks, we had to meet with the client to find out exactly what the program is meant to do. Here are the sub stories that we were able to get from the client: The program accepts employee hours worked The program computes net pay The program record all the payroll data for subsequent processing The program should prepare pay cheques The program should prepare a payroll ledger The program should maintain data on a sequential payroll file Non-statutory deductions such as union dues and pension plans to be made Year-to-date total should contain earnings, federal tax, pension plan, and union dues Payroll data are employee number, employee name, pay rate, and union member flag