Prototype Report. CRCD Management System. Team 11

Transcription

1 Prototype Report CRCD Management System Team 11 Erik Frimodig - Project Manager Yazeeed Alabdulkarim - Operational Engineer Muzzammil Imam - System Architect Jason Loewy - Prototyper Fan Xu - Requirements Engineer Daniela Gergley - Integrated Independent Verification & Validation October 24th 2011

2 Version History Date Author Version Changes made Rationale 10/10/11 JL 1.0 Original template 10/18/11 JL 1.1 Changed navigation flow to better illustrate the future system Added second prototype of the inventory portion of the system Changed status of the prototype to reflect current status Initial draft for CRCD Management System. Initial prototyping of the system. Navigation flow did not correctly represent site map like flow Prototype of inventory portion of the system needed 10/24/11 JL 1.2 More clarification about what are product-employee transactions Added description regarding navigation flow. Updated navigation flow to add generate reports Updated Inventory system GUI prototypes to reflect navigation flow update Made updates/changes based on ARB feedback and evaluation ii

3 Table of Contents Table of Tables... 3 Table of Figures Introduction Purpose of the prototype report Status of the prototype Navigation Flow Prototype Time log to ADP Parser Inventory System... 3 iii

4 Table of Tables Table 1: Code block.txt to ADP Parser... 3 Table 2:.zip Of Prototype Documents... 4 Table 3: Inventory System Overview... 4

5 Table of Figures Figure 1: Navigation Flow of System... 2 Figure 2: While loop of Code block.txt to ADP Parser...3 Figure 3: Products List...5 Figure 4: Product Details...6 Figure 5: Inventory Management Systems Data Definitions...7 v

6

7 1. Introduction 1.1 Purpose of the prototype report This document is responsible for outlining the current version of the system throughout the various prototype iterations. This document supplies all necessary documents corresponding to the various elements used in developing the prototype of the future system. 1.2 Status of the prototype This is the second iteration of the prototype report. Currently we have developed a basic Biometric Handpunch output to ADP format parser that demonstrates the ability to create a system that converts from one to the other. We have learned the output data types and format of the data collected from the Biometric Handpunch system as well as gaining knowledge about the input format to the ADP system. Knowing those two data sets, and although we still need to research the physical ordering of the data output from the Biometric Handpunch system, we have created a mapping between the two systems. We have also developed a first draft GUI representation and function representation of the inventory system. The two prototypes give a solid understanding of both the GUI and functionality, which provides a rich understanding of the look, feel and flow of the system in development. 1

8 2. Navigation Flow The system itself is broken into two sub-systems. Upon logging into the system the user can select which sub-system they wish to continue on to, Inventory or Payroll. In the inventory system each user has the same view but is provided with different performable actions based on their user permission level. In the inventory system you have the inventory manager who has the ability to add/edit/delete the employee-product transactions, as well as generate reports based off of the transaction history. You also have the inventory admin who has the ability to add/edit/delete products and their corresponding quantity and description criteria from the inventory system. All those actions can be seen in Figure 3 and Figure 4. The payroll system has three permission level roles. The payroll manager who can edit/approve/view weekly time sheets, as well as generate reports based on historical and current timesheet data. Second you have the payroll admin who can also view the weekly time sheets but is the permission group responsible for physically submitting the weekly payroll information into the ADP system. Lastly is the timesheet admin permission group which will be a member of human resources that will have complete control over personal manipulation throughout the system. They will be responsible for deleting/adding/editing the information of a user in the system as well as assigning permission levels to users of the system. Figure 1: Navigation Flow of System 2

9 3. Prototype 3.1 Time log to ADP Parser The result of this prototype was to help alleviate the concern revolving around the risk associated with hand punch output compatibility to the ADP system. Based on the Biometric Handpunch output format specified in the user manual along with the known ADP output format the parser successfully converted a user generated time log input file into an ADP formatted output file. The one lingering problem with this prototype is while we know the output fields of the Handpunch system, we don t know there ordering. This is not much of a risk as an easy mitigation plan is to rearrange how the parser grabs for specific fields based on the true ordering of the Biometric Handpunch output. Thanks to this prototype and the research that went into developing it we now know that conversion from Handpunch data to ADP format is possible. Description Related Capbility Pre-condition Table 1: Code block.txt to ADP Parser The following is a block of code used in a.txt to ADP format parser. Ideally, the text files contents will be populated with data obtained from the hand punch into a single file. At the end of a bi-weekly pay period the populated text file will be uploaded to the parser and ADP output file generated. Integration between current ADP system / 291 Bi weekly time log text is available. When the manager uploads the bi weekly time log text file this code will run to parse into ADP format. Post condition This block of code the ADP output file is generated and displayed through the browser and stored on the server in the current directory. while ($strpos!== FALSE) { // Get the employee id $dashpos = strpos($filecontents, '-'); $empid = substr($filecontents, 0, $dashpos); $filecontents = substr($filecontents, $dashpos + 1, strlen($filecontents)); // Get the clock time $dashpos = strpos($filecontents, '-'); $clocktime = substr($filecontents, 0, $dashpos); $filecontents = substr($filecontents, $dashpos + 1, strlen($filecontents)); // Get the function - IN/OUT 3

10 Description Related Capbility Pre-condition Table 2:.zip of Prototype documents The following is a.zip file containing the standard text document used when modeling the prototype.txt to ADP parser, as well as including a ReadMe which contains a link to the working prototype and instructions. Integration between current ADP system / 291 The text file bw20timesheet.txt will have been generated by the Biometric hand punch system. Post condition After running the parser the file will be ready to be uploaded to the ADP system. The.zip file is located at Inventory System The inventory system will allow managers to insert/delete/edit employee-product transactions. Employee-product transactions are the relevant information surrounding the allocation of product resources to individual employees and the way that it was put to use. This will allow CRCD staff to keep track of their various products and their use localized to each individual employee. This prototype is a high level presentation of the view and structure of the system. Figure 4 is a representation of the detailed view revolving around a specific products employee-product transaction history. The employee field is the name of who took out the amount of that product and the specified date. The notes field is used to store any note worthy information regarding this specific employee-product transaction. Description Related Capbility Pre-condition Table 3: Inventory System Overview The following are screenshots from the inventory system aspect of the system. They illustrate the capabilities of the system. Inventory tracking Employees have documented their product transactions and provided Managers with that data. Post condition All product information will be up to date and available to anyone throughout the system. 4

11 Figure 3: Products List 5

12 Figure 4: Product Details 6

13 Figure 5 is a prototype of the table definitions of the inventory management system NDI that we plan to use for our inventory management system implementation. The inventory management system NDI comes standard with this schema and will need to be customized in regards to both table definitions and table attributes in order to fit the clients exact needs for both storing data and executing queries to generate reports. Figure 5: Inventory Management System Data Definitions 7