ESSS

ESSS
Employee Self Service System

Sean Murphy
Nate Orso
Nickolaos Bocolos
Rob Anderson
 ISOM313 Spring 2008
Term Project Presentation Instructions

Assignment: Perform an analysis and make a recommendation to A-1 Information Systems

regarding their perceived need for an Employee Self Service System (ESSS). During this project
you will discover and analyze users’ requirements and wants, build a variety of analysis models
and present a system proposal.

This assignment will help you develop your system analysis skills by actually performing many of
the steps involved in the system analysis and design process. Additionally, this assignment will
also help you develop presentation skills and confidence in communicating system analysis-
related material to non-technical colleagues in the workplace.

Specifics: This project must be completed by three to four member teams. The logical
system design and recommendation will be presented to the class.

A team leader will be nominated to lead each of the four groups. The leaders are responsible for
directing the work of the analysis team and communicating with the System Owner and Users
(Professor Mee).

Each group is responsible for completing and turning in milestones 1 - 8 for Case Study 2 the
Employee Self Service System (ESSS). Your presentation will cover the logical design and
System Proposal. System Analysis is an incremental, evolving process and will therefore require
you to complete the milestones in sequence. Milestones one through three should be submitted
to the System Owner by April 1, 2008 for review and feedback.

All milestone submissions should be submitted on paper in a neatly organized package including
the assumptions that you have made in the process.

For the presentation, consider the audience to be the system owner and users who are
requesting this system. Remember, that while the new system is highly desired, it must be
justified on a cost analysis basis and will be weighed against other projects in the pipeline.

In addition to the presentation, all milestones assigned above should be handed in with your
system proposal report. This report should follow the “System Proposal” organization presented
in Chapter 11 and be targeted at supervisory-level managers.

Schedule: On April 29, 2008 each team will present their logical model and proposal. The
presentation should last at least 15 minutes but try not to exceed the 25 minute mark.

Grading: The bulk of the grade (70%) is for the development and submission of the
analysis and proposal package The rest of the grade will come from presentation content and
style: was the presentation media appropriate, professional and well organized; and did the
students speak using the PowerPoint slides rather than from a prepared script.

Last Revised: 2/15/2009 ISOM 313 Spring 2005

 A-1 Information Systems

Phone: Fax:
555-555-5555 555-555-5555

DATE OF REQUEST SERVICE REQUESTED FOR DEPARTMENT(S)

03/26/2008 Human Resources

SUBMITTED BY (key user contact) EXECUTIVE SPONSOR (funding authority)

Name Team #1 Name Mr. Joe Turner
Title Systems Analyst Title President
Office Boston, MA Office Orlando, FL
Phone 555-555-5555 Phone 555-555-5555

TYPE OF SERVICE REQUESTED:

Information Strategy Planning Existing Application Enhancement
Business Process Analysis and Redesign Existing Application Maintenance (problem fix)
X New Application Development Not Sure
Other (please specify _______________________________________________________________________

BRIEF STATEMENT OF PROBLEM, OPPORTUNITY, OR DIRECTIVE (attach additional documentation as necessary)

Current practices now have employee information changes being processed by an extensive manual effort in which Human Resource
administrators fill out forms and input the data. This manual effort often results in a time lag of several days between the time the employee
submits the forms and the update of the information in the computer. This delay has caused several problems, including unacceptable lag time in
implementing payroll deduction changes and company mailings (including pay checks) being sent to the wrong address. Another problem of the
present system is the employee directory, which is printed every six months. It seems to be out-of-date as soon as it arrives with missing
information on new employees, and incorrect information on employees who have changed addresses or been transferred.

BRIEF STATEMENT OF EXPECTED SOLUTION

To ensure the continued success of servicing internal as well as external customers, the company needed to develop a strategic plan and vision for
the use and modernization of its computing resources. In January 2005 a strategic plan to modernize the company’s resources was presented to
executive management. This document included a multi-phased plan to reengineer the current systems to use state-of-the-art technology and to
provide a showcase of systems that eventually could be delivered across the whole corporation.

Phase 1 of the plan consisted of reengineering all systems related to Human Resources, which included employee information, time and
attendance, and payroll. Task 1 of this phase is the development of the Employee Self-Service System (ESSS), a system that will house the
repository of employee master data. This system will provide the capability for each employee to maintain his or her own information regarding
address and telephone numbers, emergency contact information, payroll deduction options, and savings bond purchases. In addition this solution
will provide the means to host an online version of the employee directory and alleviate the problems of out of date information and its associated
expense.

ACTION (ISS Office Use Only)

X Feasibility assessment approved Assigned to Team #1

Feasibility assessment waived Approved Budget $ 225,000.00____

Start Date __ _____ Deadline _ ___

Request delayed Backlogged until date: ______________

Request rejected Reason: ________________________________________________

Authorized Signatures:
_____________________________________ _______Mr. Joe Turner____________________________
Project Executive Sponsor
 PROBLEM STATEMENT MATRIX
PROJECT: ESSS PROJECT MANAGER: Professor Mee
CREATED BY: Team #1 LAST UPDATED BY: Team #1
DATE CREATED: 03/26/2008 DATE LAST UPDATED: 03/26/2008

Brief Statements of Problem, Urgency Visibility Annual Priority Proposed Solution

Opportunity, or Directive Benefits or Rank
1. The current system has obsolete 6 months High Undefined. 1 Off the shelf purchase,
database and file technology for (Phase 1) (Corporate adaptation &
personnel forms and info causing Wide) implementation.
redundant and manual inputs which Homogeneous web based
lead to untimely and enterprise-level database
unsynchronized files, the proposed application. Emphasize
system will allow disparate ease of use as well as
databases to be integrated allowing security features.
file/data synchronization.
2. Employee roster is costly to 6 months High $27,000 2 Pull’ data from shared
produce in terms of time and database (with data that
money as well as frequently out of has been input by users)
date. (inaccurate) via simple GUI with a
‘front end’ designed “in
house” tooperate like a
phone book.
3. Corporate chain of command / 3 months Medium 30 Human 3 ‘Pull’ data from shared
organization chart production is Resource database (with data that
done manually. Chart information technician has been input by users)
is inefficiently produced and work hours via simple GUI and a
frequently inaccurate. (cash salary chart that is set up for
value) per dynamic change based on
year (est.) position –not a static
graphic.
4. The proposed system will allow 6 months High $172,500 2 Off the shelf purchase,
employees to enter and maintain adaptation &
personal data online saving implementation.
administrative overhead and
providing increased efficiency.
5. There is an opportunity for 1 months High Undefined 1 Utilize technology
Excellent PC / Network / Server properly that is already in
structure funded & in place. place by allowing web-
based applications to
capitalize on current PC
performance and network
redundancy.
6. Employee data on mainframe is 6 months High Possibly up 1 Tailor off-the-shelf
redundant, outdated, and frequently to $300,000 software to purge
inadequate (does not meet HR’s for annual redundant files & allow
needs). mainframe employees / customers to
overhead validate data. Add data
fidelity to current
database via simple GUI.
Solicit employee-wide
buy in and seek high
customer satisfaction.
7. Employee data on mainframe is 6 months Low Intangible 4 Create data fields in
redundant, outdated, and frequently
inadequate (does not meet HR’s
needs).
master database for
charity contribution
information / tracking.
Create tiered web access
for select leaders to view
results.
 PROBLEMS, OPPORTUNITIES, OBJECTIVES AND CONSTRAINTS MATRIX
Project: ESSS
Created by: Team #1
Date Created: 03/26/2008
CAUSE AND EFFECT ANALYSIS
Problem or Opportunity
1. Employee directory is continuously
out of date.
2. New system should be online and
integrated with email.
3. Employees can update their own da-
ta.
Causes and Effects
1. The company has a separate em-
ployee information system, payroll sys-
tem, time and attendance system, and
labor system, with its own database of
employee data.
2. Hardcopies of employee directory are
printed every quarter and cannot be
updated till the next issue is printed.
3. Employee Directory consumes a
great deal of time to enter data, update
and maintain as the data is entered ma-
nually.
1. Changes are difficult to maintain and
update since they are done in the hard-
copy.
2. Being online will show the changes
in real time.
3. To publish 5000 copies of an em-
ployee telephone directory quarterly
costs $27,000 per year.
1. This would cut HR administration
time from 12 to 1.5 hours per week.
Project Manager: Professor Mee
Last Updated by: Team #1
Date Last Updated: 03/26/2008
SYSTEM IMPROVEMENT OBJECTIVES
System Objective System Constraint
1. Create a system with GUI to allow 1. Employees should not be able to
employees to change their directory change their job titles, locations etc.
information.
2. Managers must have tools to run
2. Create a single-shared database for queries and monitor employee data.
all systems to pull employee data from.
3. Authorized users should be allowed
3. The proposed system will allow dis- to run queries on the data.
parate databases to be integrated allow-
ing file/data synchronization.
4. System must be flexible and easily
adaptable to changes.
1. Make the new system online with 1. The system needs to be secure with
web-based interface and integrate it state-of-the-art security system to allow
with email. remote access.
2. Eliminate the quarterly hard copy
employee telephone directory.
1. Creating an interface that allows 1. Employees should be able to see and
employees to update their own data. change their own data.

4. Current mainframe system is too
costly and difficult to maintain. 11,500
transactions per year. System is over ten
years old.
5. System does not have ad-hoc query
and reporting facility that users can use.
6. Simple online Graphical User Inter-
face will potentially increase employee
participation in charitable campaigns.
2. Changes would be available real-
time.
1. It cost $15 per in labor and compu-
ting costs process to change. The com-
pany processed 11,500 changes in the
last year alone which adds up to sub-
stantial costs.
2. There is no automated interface be-
tween the mainframe and the micro-
computer.
1. Creates faster searches for users.
2. Cuts down on Information Services
workload.
1. Employees will be able to make and
manage deductions from their desktop.
2. Managers will be able to see the
overall contributions being made.
2. Eliminate the need for an administra- 2. System must be secured with state-of-
tor to manually enter basic employee the-art security for remote access.
information, including error correction.
1. Off the shelf purchase of software, 1. Emphasize ease of use as well as
adaptation & implementation homoge- security features.
neous web based enterprise-level data-
base application.
1. Tiered web access. Restricting em- 1. Employees should not be able to see
ployees to certain fields. someone else’s data.
2. Access for managers only.
1. The Customer web interface should 1. System must be secured.
provide easy tools for employees to sign
up for and manage deductions from
their desk.
Requirement Classification
Input: web-based from remote or local host, multiple logins, Functional
accessible by all employees(personal data only), automation between micro-computer and
mainframe, all sites must be able to access data, folder-type directory structure, GUI interface,
Able to access from Desktop machines
Output: ad-hoc queries, up to date telephone directory, managerial use employee queries, HR Functional
administrators able see all employees information, Show who manages who, Reports on
contributions by employee, Reduce excessive interfaces, Real-time availability
Performance: Constant synchronization Non-functional
Ease of learning: PC based, tied into company Email system Non-functional
Process: Nightly database synchronization and backups, remote secure login, tracking and Functional
management, one input into one system
Ease of use: Employees able to be trained on material, and useof system within 2-3 weeks of Non-functional
implementation
Budget and costs: Budget for this phase is $225,000 Non-functional
Cost savings: Estimated savings per year of over $500,000 Non-functional
Data: centralized database, Employee information, State-of-the-art security, Main system in Functional
Orlando
Timetables: Phase 1 must complete within six months. Non-functional
Documentation: Project report and training materials Non-functional
Training needs: Training materials for staff and employees Non-functional
 Current Employee

/ Update Telephone #
/ Confirm Update
New Employee
/ Receive Benefits

/ Register w/HR

/ Run Query
/ DB Sync Human
Resources / Query Results
/ Access Database
ESSS
Employee Manager
Remote Site
/ Run Query
/ Query Results

HR Employee
 Write Access Read Access

View Employee
Directory Data
Update Employee Personal
Information (non–secure
data)

Employee
«uses» View Employee
Detailed Data

Enter New Employee

Profile
United Way
Manager
«uses» Contributions

Update Employee
View Employee
Personal Information (secure
Group Data
data)
Human Resources

«uses» «uses»

Logon
Authentication
 Use-Case Glossary
Participating
Use-Case Name Use-Case Description
Actors and Roles
1. Enter New Employee A new employee must complete forms and be HR
Profile entered into the system by HR on first day of
work.
2. View Employee Part of the online directory, any employee can Employees
Directory Data (non-secure view any other employee basic information, i.e. HR
data) telephone number, name, office and building. Managers
3. View Employee Detailed Detailed employee info such as salary, payroll HR
Data (secure data) deductions, job title, and supervisor. HR has over Manager
riding administrative access. Managers have view Employee (self only)
only privileges of their respective supervised
employees.
4. Update Employee Any employee may update their own phone Employees
Personal Information number, emergency contact, optional payroll HR
(non–secure data) deductions. HR has over riding administrative
access.
5. Update Employee Only HR may make changes to salary, job title HR
Personal Information and supervisor info.
(secure data)
6. View Employee Group Direct and indirect supervisors may view HR
Data employee data. This is grouped by department Managers
and capable of drilling down to individual
employee detail data. HR has over riding
administrative access.
7. Logon Authentication System requires authenticated use and HR
authorized privilege level identification by all. Managers
Employee
8. United Way Employees may view or edit as payroll deduction HR
Contributions option. HR has overriding administrative access. Manager
Managers may view generated reports of Employee (self only)
participation by department.
 ESSS
Author (s): ___Team #1_________ Date: __0326/2008
Version: ___01______
USE CASE NAME: Search Employee Directory USE CASE TYPE
USE CASE ID: ESSS-006 Business Requirements: 
PRIORITY: High
SOURCE: Requirement – MSS-R1.00
PRIMARY BUSINESS Employee
ACTOR
PRIMARY SYSTEM Human Resources, Employees and Management
ACTOR
OTHER PARTICIPATING • Human Resources, Management
ACTORS:
OTHER INTERESTED •
STAKEHOLDERS:
DESCRIPTION: This use case describes the event of searching the employee directory for viewing information.
Any employee may view the directory information of any other employee. This directory will be
driven by a searchable query based upon the information contained within i.e., first or last name,
department, location, job title, or supervisor or combinations of them.
PRE-CONDITION: The user must have previously logged on so that the system can identify the user as an authorized
user and validated privilege level i.e. particular employee, manager, HR or admin.
TRIGGER: The use case is initiated when the user selects this option from the user interface.
TYPICAL COURSE Actor Action System Response
OF EVENTS: Step 1: This use case is initiated when a Step 2: The system responds by displaying an
user selects the option to view the interface into the directory database requesting query
employee directory. input.
Step 3: The user inputs the appropriate Step 4: The system displays a list of everyone who
requested data into the corresponding matches that criteria and provides links on each
query fields. person to go view the complete information.
Step 5: The user clicks on the individual Step 6: The system will verify that this user has the
link to view more complete information right to view the given level of information and
of that employee. display that data.

ALTERNATE COURSES: Alt Step 4a: If user selects self, they are provided access to a more detailed view of their
information.
Alt Step 4b: If the user is management then the system displays an option to view a more detailed
version of all employees under their supervision listed by division.
Alt Step 6b: If the user does not have the right to view the selected data, an error screen appears
with appropriate no access message.
CONCLUSION: This use case concludes when the user exits the unresolved request list screen.
POST-CONDITION: None
BUSINESS RULES • None
IMPLEMENTATION • Data base programming to be used to provide a variety of searchable criteria.
CONTRAINTS AND
SPECIFICATIONS
ASSUMPTIONS: • None
OPEN ISSUES: 1. Need to determine whether or not a manager has write access.
 Entity/Definition Matrix
ENTITY BUSINESS DEFINITION
Employee An active employee of one or more business unit.
Emergency Contact An employee’s emergency contact information.
Department A business unit at the company identified by a series of non-specific, non-
unique numbers.

Building A physical structure owned, leased, or rented by the company.

Room A physical location within a building.
Site A location owned, leased, or rented by the company. Currently five remote
site besides the headquarters in Maryland, including Orlando, Denver,
Sunnyvale, Valley Forge, and Marietta.
Deduction A monetary amount taken from employee salary for a purpose.
United Way A business that can receive money from a deduction.
Mail Stop A physical location identified for delivery and pick-up of External and Internal
company related mail.
Salary Employee A salaried employee.
Contract Employee An employee that under contract.
Hourly Employee An employee that is paid by the hour.

Context Data Model

EmergencyContact
4/19/2008

Site
ContractEmployee

is Department

declares

has

HourlyEmployee
Employee MailStop Building
is
has contains

is

SalaryEmployee has

Room

contributes assigned assigned

UnitedWay
MiscDeduction
elects
 Key Based Data Model
EmergencyContact

PK ContactFirstName 4/19/2008
PK ContactMiddleName
PK ContactLastName
PK,FK1 EmployeeID
declares Site
Department

PK DeptID PK SiteID

has

ContractEmployee has
PK,FK1 EmployeeID is
MailStop Building

PK MailStopID PK,FK1
contains
Employee PK BuildingID
HourlyEmployee
is FK1 BuildingID
PK,FK1 EmployeeID PK EmployeeID

is FK1 RoomNum
FK2 DeptID has

SalaryEmployee
Room
PK,FK1 EmployeeID
PK RoomNum
assigned
assigned
FK2 MailStopID
BuildingID

contributes
elects

MiscDeduction
UnitedWay
PK,FK1 EmployeeID
PK,FK1 EmployeeID PK ReqDedDate
PK UWYear

Fully Attributed Data Model

SalaryEmployee HourlyEmployee ContractEmployee

PK,FK1 EmployeeID PK,FK1 EmployeeID PK,FK1 EmployeeID 4/19/2008

Department Site

PK DeptID PK SiteID
has
is DeptName SiteName

is has
is Employee

PK EmployeeID Building
EmergencyContact MailStop
FK1 RoomNum PK,FK1
PK ContactFirstName FK2 DeptID PK MailStopID contains PK BuildingID
PK ContactMiddleName EmpFirstName
PK ContactLastName EmpMiddleName FK1 BuildingID BuildingName
PK,FK1 EmployeeID EmpLastName
declares EmpNickName
ContactStreetAddress EmpHomePhone has
ContactCity EmpStreetAddress
ContactState EmpCity
ContactZip assigned Room
EmpState
ContactHomePhone EmpZip
ContactWorkPhone PK RoomNum
EmpJobTitle assigned
ContactCellPhone
FK2 MailStopID
BuildingID

MiscDeduction
elects
UnitedWay
PK,FK1 EmployeeID
PK,FK1 EmployeeID PK ReqDedDate
PK UWYear contributes
DedName
UWType DedAmount
UWAmount DedFrequency
 Context Diagram

4/19/2008

Employee Employee Detail Lookup on Self

Company directory
Search Results HR
Administrators

Update Employee Profile Employee Group

lookup on all
Company Directly
employees
Search Criteria
Employee Self Service
Employee Detail lookup on all employees
System

New Employee Profile

Update Secure
Employee Data

United Way
Participation
Ad-hoc query
and reporting
Info about
reporting employees
Manager
Employee Group
Staffing Dept. lookup on reporting
Employees
 Event Decomposition Diagram

4/19/2008

Employee Info Employee

Room Info Room

Search
Search Criteria Employee Building Info Building
Employee Directory
Search Results
Site Info
Site

Department Info Department

Update Employee Info Employee

Update Contribution Info United Way

Contribution

Update Emergency
Update Contact Info
Employee Update Profile Info Employee Contact
Profile Update Deduction Info MiscDeduct.

New Employee Info Employee

Emergency
New Contact Info
Contact

United Way
Staffing Dept. New Contribution Info
Update Profile Info Enter New Contribution
Employee
Profile New Deduction Info MiscDeduct.
New Contract Info
New Hourly Info

New Salary Info

Contract Employee Salary Employee Hourly Employee

 Event Decomposition Diagram Cont.

4/19/2008
Employee name and supervisor info Employee

Report Request View United

Manager Way
Report Results Participation
Contribution Info United Way
Contribution

Update Employee Info Employee

Update Contract Info Contract Employee

Staffing Dept, Promotion Job Change
Update Update Salary Info Salary Employee
or relocation info Employee
Secure Data Update Hourly Info

Hourly Employee

Room Site

Employee

Building Data Data

Data

Data Contract Employee

Data Hourly Employee

Manager SQLData Perform Ad-Hoc
Query and
Results
Reporting Data Salary Employee

Data Emergency Contact

Data
MiscDeduct Data
Data Data

Department MailStop
United Way Cont.
 Analyzing the Potential Object List
Potential Object Notes Obj Reason
Annual Salary The yearly salary of a N Attribute in EMPLOYEE or
salaried employee. PAYCHECK
Building A building where Y BUILDING
employees work in
various rooms.
Calendar Year The year for which a N Attribute in UNITED WAY
United Way
contribution applies.
Contact Address The street address, N Attribute in EMERGENCY
city, state, and zip of CONTACT
an emergency contact.
Contact Home Phone The home phone N Attribute in EMERGENCY
number of an CONTACT
emergency contact.
Contact Name The first name, middle N Attribute in EMERGENCY
name, and last name of CONTACT
an emergency contact.
Contact Work Phone The work phone N Attribute in EMERGENCY
number of an CONTACT
emergency contact.
Contract Employee A temporary employee. N Attribute in PAYCHECK
Department An organizational Y DEPARTMENT
grouping of employees
that fulfills a business
function.
Dept ID An abbreviated N Attribute in DEPARTMENT
identifier for a
department.
Dept Name The full name of a N Attribute in DEPARTMENT
department.
DOB An employee’s date of N Attribute in EMPLOYEE
birth.
Emergency Contact A person who should Y EMERGENCY_CONTACT
be contacted
concerning a particular
employee in case of
emergency.
Emp ID A unique, sequentially- N Attribute in EMPLOYEE
assigned identifier for
an employee.
Employee A person who works for Y EMPLOYEE
the organization.
Employee Address The street address, N Attribute in EMPLOYEE
city, state, and zip of
an employee.
Employee Home Phone The home phone N Attribute in EMPLOYEE
number of an
employee.
 Analyzing the Potential Object List
Potential Object Notes Obj Reason
Employee Name The first name, middle N Attribute in EMPLOYEE
name, and last name of
an employee.
Employee Office Phone The office phone N Attribute in EMPLOYEE
number of an
employee.
Hire Date The date an employee N Attribute in EMPLOYEE
was hired.
Hourly Employee An employee who is N Attribute in PAYCHECK
paid a hourly wage.
Hourly Wage The hourly wage of an N Attribute in PAYCHECK
hourly employee or a
contract employee.
Job Title An employee’s job title. N Attribute in EMPLOYEE
Life Insurance A miscellaneous N Attribute in PAYCHECK
deduction.
Location Where an employee N Synonym of Remote Site
can be found.
Mail Stop A room or an area of Y MAIL_STOP
an office where
employees can go and
retrieve their mail.
Martial Status The marital status N Attribute in EMPLOYEE
(married, single) of an
employee.
Maximum Weekly Hours The maximum hours N Attribute in PAYCHECK
per week that is
scheduled for each
hourly employee.
Misc Deduction A miscellaneous N Attribute in PAYCHECK
deduction elected by
an employee.
Permanent Employer The permanent N Attribute in PAYCHECK
employer of a contract
employee.
Request Date The date of a N Attribute of an object
Miscellaneous
Deduction request.
Room A room where N Attribute of an object
employees may work.
Salary Employee An employee who is N Attribute of an object
paid a salary.
Site A company location Y
consisting of one or
more buildings.
SSN An employee's Social N Attribute of an object
Security Number.
Supervisor An employee's Y
supervisor
 Analyzing the Potential Object List
Potential Object Notes Obj Reason
United Way Contribution A contribution pledged Y
to the United Way by
an employee.

Activity Diagram

4/19/2008

Actor System

Search the
employee directory

Display search
A
User decides to screen w/ options
cancel search
& exits
Display all
Fill in search
employees
criteria
matching criteria

User returns to
search screen
Returns to employee
list
Returns to
search screen

Click on detail link for

an employee

Display employee
View info. on detailed info.
selected employee

Exit

A
 Sequence Diagram

4/19/2008

ESSS

User

viewEmployeeDirectory

Search Directory

enterEmployeeCriteria

Employee Criteria Matches

viewSelectedEmployee

Class Diagram

4/21/2008

User Site
-UserId 0...1 Department
1 -SiteName
-Password -DeptName
Emergency Contact -RoomNum has
-ContactName -DeptId
-ContactAddress 0...* -EmpName 1
1 0...* contains
-ContactCity -EmpHomephone 1
-ContactState -EmpAddress United Way
has contributes
-ContactZip -EmpCity -UWType Building
1
-ContactPhone -EmpState 1 -UWAmount
-EmpZip -BuildingName
-EmpJobTitle
+Login()
+Detail lookup Self() 1 Room 1 1
+Update Profile() has
1
-RoomNum
assigned
assigned 1 MailStop
-MailStopId

Employee Staffing Dept. HR Admin. Manager

+New Employee Profile() +Group detail lookup() +Ad-hoc reporting ()

+Update Secure data() +Group lookup()
+United Way Partcipation()
 Candidate Matrix
Characteristics Candidate 1 – Candidate 2 – COTS Candidate 3 –
COTS w/ major w/ minor Custom built
customization customization solution
System facet utilizing This solution would This solution would use This solution would
computer automation. use a module of a module of PeopleSoft involve writing a
PeopleSoft as a web as a web interface to the solution using common
interface to the main main ESSS. web services products.
ESSS. Customization Customization of
includes new interface management tasks
for micro computer (United Way View).
system and HR
department and
management specific
tasks.
Benefits that would be Peoplesoft APIs and Peoplesoft APIs and This solution would
realized for this data structure, data structure, enabling allow maximum
candidate. enabling easier easier integration with flexibility, since there
integration with future future RDBM. Minor would be no existing
RDBM. Successful customization data models or
implementation history necessary. Successful processes in the
and team experience. implementation history software and the
and team experience. requirements could be
Less service interruption followed exactly.
likely.
Servers and A Dell DL360/40GB Same as Candidate 1 Two Dell servers to
Workstations needed might be necessary if host Web Server, and
to support this the module is installed RDBMs capable
candidate. separately. application hardware
Existing workstations required.
would be adequate.
Software Tools Existing Peoplesoft Same as Candidate 1 LAMP technology, 37
needed to design and integration Toolset, Signals architecture,
build the candidate. Java Apache 1.3.22 or up,
OSCommerce, MySql
3.23, Perl5.3 Library,
Java JDK 2, RedHat
8.2 or up.
Application Software to PeopleSoft module Same as Candidate 1 Custom solution
be purchased, built,
integrated, or some
combination of these
techniques.

Method of Data On line, real-time Same as Candidate 1 Same as Candidate 1

Processing.
Implications of output Existing LAN Printers Same as Candidate 1 Same as Candidate 1
devices that would be Email
used, special output Web Browser
requirements, and
output considerations.
 Candidate Matrix
Characteristics Candidate 1 – Candidate 2 – COTS Candidate 3 –
COTS w/ major w/ minor Custom built
customization customization solution
Implications of data Oracle 8.1.6 RDBMS Same as Candidate 1 MySQL 3.23 RDBMS
stored, what data with 36 GB disk space 50 GB disk drive
would be accessed Some backup to tape All employee location
from existing stores, software data on ERD
what storage media Data: All employee Data: All employee
would be used, how location data on ERD. location data on ERD.
much storage capacity Data would use Develop in-house data
would be needed, and existing PeopleSoft model
how data would be data model.
organized.

Feasibility Matrix

Feasibility Criteria Wt Candidate1 Candidate 2 Candidate 3

Description COTS w/ major COTS w/ minor Custom built solution

customization customization
Operational Feasibility 20% Fully supports user- Mostly supports Fully supports user-
required user-required required functionality,
functionality, current functionality, current concern about
business process business process security in system.
must be modified to must be modified to Score: 80
take advantage of take advantage of
functionality. functionality.
Score: 90 Score: 70
Technical Feasibility 20% Current staff is Current staff is Requires staff and
comfortable with comfortable with support personnel
solution, able to solution, able to training on LAMP and
maximize maximize Open Source
productivity. productivity. systems.
Required to Required to Security and product
hire/train on Java- hire/train on Java- maturity could
J2EE for system J2EE for system present risk.
modifications. modifications. Score: 50
Score: 80 Score: 80
Cultural Feasibility 10% Possible user Possible user Less possible user
resistance to new, resistance to new, resistance to new,
non-standard user non-standard user non-standard user
interface. interface. interface.
Score: 60 Score: 60 Score: 80
Legal Feasibility 10% No foreseeable No foreseeable No foreseeable
problems problems problems
Score: 100 Score: 100 Score: 100
Economic Feasibility 30%
Cost to develop:
Payback period:
Net present value:
Approx. $225,000 Approx. $225,000 Approx. $225,000
Approx. 4.5 years Approx. 3.5 years Approx. 5 years
Approx. $90,000 Approx. $90,000 Approx. $150,000
Score: 60 Score: 80 Score: 50

Schedule Feasibility 10% 120 days 90 days 179 days

Score: 70 Score: 95 Score: 20

Ranking 100% 90(20%) + 80(20%) 70(20%) + 80(20%) 80(20%) + 50(20%) +

+ 60(10%) + + 60(10%) + 80(10%) + 100(10%)
100(10%) + 60(30%) 100(10%) + 80(30%) + 50(30%) + 20(10%)
+ 95(10%) =
+ 70(10%) = 75 = 61
79.5