SUPPORT P1

DELIVERABLE B

May 23, 1999

Project Team:

Juan Casillas

Sophia Clay

Zeeshan Khan

Adam Oxer

Julio Salazar

System Documents:

Overview

Entity Relationship Diagram

Data Flow Diagrams

User Interface Screens

Database Schema

Data Dictionary

CRUD Matrix

Overview:

The following document provides a framework for creating the Support P1 System. The diagrams and charts included in this document give the coders the necessary information to complete this project. This project is based on the needs of Zurich Kemper Life and its use of the PeopleSoft Financial Module to manage the financial operations of the company. The software maintains the General Ledger and Accounts Payable functions for financial reporting and check generation. Support P1 is a tracking system project to document the requests to create and modify software for the PeopleSoft Financial Module.

Entity Relationship Diagram:

The Entity Relationship Diagram for Support P1 is a graphical representation of the various entities in this project, including their attributes.

Data Flow Diagrams:

Purpose:

The Data Flow Diagrams for this project are separated into 3 level - 0, 1 and 2. Level 0 is also known as the context diagram. Level 1 shows the six main processes. Level 2 shows the further details of two of those six processes. It is expected that these documents will serve as the technical blueprints that will guide the development of the Support P1 System processes. These documents represent the planned implementation of the Support P1 System processes, showing inputs to and outputs from processes, database actions, as well as the data flows between processes or functions.

Dataflow Diagram  Level 0

Dataflow Diagram Level 1

Level 1 - Notes

• There are only six data stores, data stores that are repeated are exactly the same and are used twice just to make the DFD more readable.
• There are only three external agents and Technical Lead is used twice just to make the DFD more readable.
• Data flow names, which are the same, are exactly similar in all nature and contain exactly the same number of fields with the same description.
• Data flows contain all of the respective attributes of the entity - those that are mentioned in entity relationship diagram and explained in Data dictionary for the ERD.

Level 2 Data Flow Diagram for Process 4

Process 4.0 Maintain Static Tables is exploded into four more processes in level 2:

4.1 Maintain Process

4.2 Maintain Employee

4.3 Maintain Priority

4.4 Maintain Department

The Static Tables are the source for information that is used on each new request. Each of these processes will Create, Read, Update and Delete data from their respective data stores.

Level 2 Data Flow Diagram for Process 6

Process 6.0 Generate Report is exploded into three more processes in level 2:

6.1 Generate manager’s open request report

6.2 Generate work assignment report

6.3 Generate close notification report

These three processes generate the reports needed by the Technical Resource to manage the upport P1 System. Each process reads data from the six data stores.

User Interface Screens:*

The included interface screens show what the user will experience when moving from screen to screen in this system. The Technical Lead will be the most intensive user of the screens, relying heavily on the Request status Screen.

The Requester will use the Ticket Request Screen

The Maintenance Screens (Employee Details, Priority Description and Process Description) will be used by the Technical Lead.

Data Base Schema and Data Dictionary contains the details regarding the data attributes in Entity Relation Diagram.

Curd Matrix helped us in balancing and syncronizing our database and dataflows.

* Updated screens are fully functional model is posted under deliverable C