CMS 4050 Project 2 Employee Self Service System

1
CMS 4050 Project 2Employee SelfService System

• By Caleb Anthony, Chris Buirge, James Carlson,
  Richard Rice

2
A1 Corporation Introduction

• 5 Regional Offices
• Orlando, FL (Headquarters)
• Denver, CO
• Sunnyvale, CA
• Valley Forge, PA
• Marietta, GA
• Currently 4,100 Employees
• 15 Increase in Work Force over Next 3 Years
• Projected 6,200 Employees in 2007

3
Current Human Resources Employee Profile Process

• New and Existing Employees Complete Forms
• Employee Profile Form
• United Way Contribution Form
• US Savings Bond Contribution Form
• HR Administrator manually inputs Completed Forms
  into HR Database (legacy system)
• Employee Data must be manually input into all
  other systems requiring Employee Data
• Payroll
• Time and Attendance
• Company Phone Listing

4
Current Company Phone Listing Process

• Company Phone Listing Published Quarterly
• 5,000 copies printed per quarter
• Annual Cost 27,000
• New Hire and Changes to Employee Data input
  manually
• Requires 30 of Staff Members Time
• Due to Large Volume of Changes, Listing Outdated
  at release

5
Costs of Inefficiency

• Manual Data Entry
• 11,500 trans / yr 15 / trans 172,500 Annual
• Multiple Employee Data Databases
• Significant Lag Time from Form Completion to All
  Systems Updated
• Mismatched Data / Errors
• Lower Participation
• United Way Contributions
• US Savings Bond Contributions
• Outdated Company Phone Listing

6
(No Transcript)
7
Problem Analysis Phase

• Problem Analysis Phase Has 3 Purposes
• Gain an Understanding of the Problem
• Are the Problems Worth Solving?
• Is the System Worth Developing?

• Approximately 200,000 Annual Savings

• Reduce Inefficiencies and Errors

• Increase Contribution Participation

• Usable, Updated Company Phone Book

8
Database Design

• Data Attribute Dictionary
• Attributes, Description, Data Type, Constraints
• Logical Data Model (Entity Relationship Diagram)
• Entities, Attributes, Relationships, Cardinality
• Physical Database Schema
• ERD plus Data Types and Referential Integrity
  Constraints

9
(No Transcript)
10
Context Level Data Flow Diagram
11
Functional Decomposition Diagram
12
System LevelData Flow Diagram
13
Data Flow DiagramFor Company Phone Listing
Process
14
Psuedocode

• 4 Radio Buttons
• Show
• Department
• Location
• Name
• All

15
Psuedocode

• Procedure Call PopulateDept()
• dbConn.open()
• sql.commandText Select dept_name
• From department Order By Dept_name
• DataSetDept.clear()
• DataAdapterdept.fill(dataSetDept,
  DEPT_NAME)
• cboDept.DataSourceDataSetDept.tables(
  DEPT_NAME)
• cbodept.DisplayMember DEPT_NAME
• cboDept.DataBindings.add(TEXT, DataSetDept,
  DEPT_NAME)
• cboDept.Enabled True
• cboDept.DataBindings.Clear()
• dbConn.close()

16
Psuedocode

• ReturnAll()
• dbConn.Open()
• SQL.CommandText SELECT emp_last, emp_first,
• Emp_middle, employee_id, dept_name
• Work_phone, work_site, Work_build,
• Work_room, mail_stop
• FROM (employee LEFT JOIN employee_listing
• ON employee.emp_id employee_listing.emp_id)
• LEFT JOIN department ON
• Employee.emp_dept_code department.dept_code
• ORDER BY emp_last
• DataSetAll.Clear()
• DataAdapterAll.Fill(DataSetAll, Results Table)
• Db.Conn.Close()

17
Object Class Diagram
18
Sequence Diagram
19
Use Case Dependency DiagramFor US Savings Bond
Purchase
20
Use Case Model DiagramFor US Savings Bond
Purchase
21
State DiagramFor US Savings Bond Purchase
22
Architecture Design
23
Internet Design
24
Security Design
25
(No Transcript)
26
Recommendations

• Develop and Implement the ESSS system
• Use ASP.Net and ADO.Net Technology
• Implement using Parallel Conversion

27
Prototype Demonstration