Absence Credit Tracking System

April 10, 2002

Team Members:

Joshua Allen

Dave Kristensen

Greg Ludwinski

Samantha Ratnapuli

ClientRegional Municipality of Durham,

Whitby, Ontario

Stakeholders• Jennifer A. Purrott, Computer Support

Coordinator• Emily Mckay, Employee Services

Assistant• Teresa Shepperdson, Co-ordinator,

Disability and Pensions• Ron Blakey, IT Project Manager

What is the Business Problem?

Need to Track and Manage Employee:

• Absences • Absence Credit Balances

How is the problem currently being resolved?

• Sick Leave System (SLS)• Cobol and Powerhouse System• Data Stored in a Flat File • Text Based User Interface• Batch File Processing• Text Based Reports

What is Wrong With the Current System?

• Data in Flat File Getting out of Hand• Affiliation rules have changed

• Old system does not have enough floating point precision

• System is at End of lifecycle• Maintenance Costs becoming too Large• Batch File Processing

• Cannot tell if an employee is out of credits until file is batch processed at the end of the week

What is Wrong With the Current System?

• No Source Code Documentation• GUI not User Friendly• No User Access Permission Levels• Poor Output, Reports/ Statistics• HR Department requested a new System

Solution: Developed New System

Absence Credit Tracking System (ACTS)

How does ACTS solve existing problems?

• Ease of Use• Swing GUI • Windows Look and Feel• User Friendly• User Options (Date Formats Etc.)• ACTS Processes Transactions immediately

Documentation

• Online User Documentation• Manuals

• System• Administrative• User

• JavaDoc Used to Document Source Code

Report Generation

• Generates HTML Based Reports• Generates Tab Delimited Text Based Reports

for Exporting Data• Reports on Employees and Absences.• Report Requests Queued• Reports sent by E-mail

RMI Object Server

• Data Stored in Oracle Database• Automated Table Creation• Automated Flat File Integration• Embedded Jython Interpreter• Trace Tab shows Debugging Output

System Architecture

• 3 Tiered system • Separates Business Rules, Interface and

Persistence Store• Java Remote Method Invocation (RMI)• Java DataBase Connectivity (JDBC)

Workstation

CLIENT

APPLICATION SERVER

Data

DBMS SERVER

DBMS

REQUEST/RMI

RESULTS

JDBC/SQL RESULTS

Security

• Network Security through SSL• Application Security Through Username

Password• Passwords are saved in Encrypted Format• Authentication for all Remote Method Calls• All Security Implemented on Server Side• Audit Trail Tracks all System Transactions• User Management and access levels

Who will use ACTS?

Durham Region

• Human Resources: ACTS System Administrators, approximately four

• Designated Department: Regular Users, approximately 25

Added Functionality

• Web Based Software Distribution• Using Java WebStart

• Automatic Software Updates• Flexible Business Rule Management

Software Design

• Object Oriented Design• Class Diagram and CRC Cards• Object Interfaces• Direct Mapping Between Objects and

Database

Class Diagram

Department

Reason

Affiliation

JobClass

EmpStatus

EmpActivity WorkLocation

EmpTransaction

Employee

DepartmentAccess

User

Proje ct Ste ps Aug Se p O ct N ov D e c Jan Fe b M ar Apr

Pro p o sa l

R e q u ire m e n ts g a th e r in g

Hig h le ve l re q u ire m e n tsd o cu m e n t

R e q u ire m e n ts d o cu m e n t

F e a s ib ility

Sch e d u le a n d G ANNT ch a r t

W e b s ite d e s ig n a n d u p d a te s

G UI d e s ig n

D a ta b a se d e s ig n

Pro g ra m D e s ig n

Pro to typ e

Use r M a n u a l a n d o n lin e d o c

T e s t P la n n in g

D a ta b a se c re a tio n

C o d in g a n d d o cu m e n ta tio n

T e s tin g (4 0 0 So lu tio n s)

Im p le m e n ta tio n a n dd e b u g g in g

Q u a lity a ssu ra n ce a n a lys is

P re se n ta tio n P re p a ra tio n

Pre se n ta tio n

P ro ject D ev elo p m en t S ch ed u le

Jo sh, Dave, G reg, S am

Jo sh, Dave, G reg, S am

G reg

G reg, Dave

Jo sh, G reg

Jo sh, G reg, S am

Dave

Jo sh

Dave, Jo sh

Jo sh, Dave, G reg, S am

Jo sh, Dave, G reg, S am

Dave, S am

Dave, S am

Jo sh

Jo sh, G reg

Dave, S am

Jo sh, Dave, G reg, S am

S am

Jo sh, Dave, G reg, S am

D e v e lo pm e n t

Q u a lity A s s u ra n ce

D o cu m e n ta t io n/A n a ly s is

Pre s e n ta t io n

Software Process Model

Waterfall Model with Prototype

Requirements Definition

System and Software Design

Implementation and Unit Testing

Integration and System Testing

Operation and Maintenance

Prototype

• Used Visual Basic

Implementation and Unit Testing

• Java Programming Language• Portability• Ease of installation

• Programming Environment: JDK 1.4, Forte as IDE

• JUnit Testing Technique Used for White box Testing

• Java Help and HelpBreeze used for Online Help

• Light Weight Persistence Library• from: www.imaginary.com

Conclusion

What’s Left?

• Interface Adjustments• Installation• Black Box Testing

Please visit the 400 Solutions Web Site

http://www.400solutions.com