VISION

FOR

EMPLOYEE MANAGEMENT SYSTEM

Version 1.1

Prepared by
Sana Zulfiqar
&
Fasiha Rasool
22nd Jan,2019

1
 Revision History

Version Description Author Date

This document covers

1.0 Sana Zulfiqar 31st Dec, 2018
the vision of the EMS

This document covers

1.1 Sana Zulfiqar 22nd Jan, 2019
the vision of the EMS

2
 Table of Contents

1. Introduction --------------------------------------------------------------------------------------------------------------------------- 4
1.1 Purpose ---------------------------------------------------------------------------------------------------------------------------- 4
1.2 Scope ------------------------------------------------------------------------------------------------------------------------------- 4
1.3 Definitions, Acronyms and Abbreviations -------------------------------------------------------------------------------- 4
1.4 References ------------------------------------------------------------------------------------------------------------------------ 5
1.5 Overview --------------------------------------------------------------------------------------------------------------------------- 5
2. Positioning ----------------------------------------------------------------------------------------------------------------------------- 5
2.1 Business Opportunity ---------------------------------------------------------------------------------------------------------- 5
2.2 Problem Statement ------------------------------------------------------------------------------------------------------------- 5
2.3 System Position Statement --------------------------------------------------------------------------------------------------- 6
3. Stakeholder and User Descriptions -------------------------------------------------------------------------------------------- 6
3.1 Stakeholder Summary ---------------------------------------------------------------------------------------------------------- 6
3.2 User Summary -------------------------------------------------------------------------------------------------------------------- 7
3.3 Stakeholder Profiles ------------------------------------------------------------------------------------------------------------ 7
3.3.1 Administrator -------------------------------------------------------------------------------------------------------------- 7
3.3.2 DEO --------------------------------------------------------------------------------------------------------------------------- 8
3.4 Key Stakeholder / User Needs ----------------------------------------------------------------------------------------------- 8
4. System Overview -------------------------------------------------------------------------------------------------------------------- 8
4.1 System Perspective ------------------------------------------------------------------------------------------------------------- 9
4.2 Summary of Capabilities ------------------------------------------------------------------------------------------------------- 9
4.3 Assumptions and Dependencies -------------------------------------------------------------------------------------------- 9
4.4 Cost and Pricing ------------------------------------------------------------------------------------------------------------------ 9
4.5 Licensing and Installation ----------------------------------------------------------------------------------------------------- 9
5. System Main Features-------------------------------------------------------------------------------------------------------------- 9
6. System Priorities ------------------------------------------------------------------------------------------------------------------- 10
7. Constraints -------------------------------------------------------------------------------------------------------------------------- 10
8. Quality Ranges --------------------------------------------------------------------------------------------------------------------- 11
9. Other Item Requirements ------------------------------------------------------------------------------------------------------- 11
9.1 System Requirements -------------------------------------------------------------------------------------------------------- 11
9.1.1 Platform ------------------------------------------------------------------------------------------------------------------- 11
9.1.2 Printer ---------------------------------------------------------------------------------------------------------------------- 11
9.1.3 Hardware requirements ----------------------------------------------------------------------------------------------- 11

3
1. Introduction
Employees are the backbone of any company, management of employee Performance
plays a major role in deciding the success of the organization. In many organizations the
current system is paper based. That is the organizations are still using cabinet files to
store employee information. Useful data is scattered all over the place. And at times is
difficult to find relevant files. Records are also not always filed correctly and thus
information is not centralized and not easily accessible.
We are proposing a desktop application for such organizations. The system will be able to provide
a Department, Employees information and their Salary, Attendance and Performance .
It will provide security and easy access to the employees that are currently at work and
what they are working on. Also easy to allocate jobs to the employees that are done
with what they were doing. The system will provide quick and reliable access to
Employee’s information lots of time will be saved.
1.1 Purpose
We are developing this system for those companies which have manual system and
facing following problems.
 It is time consuming.
 No proper record for maintaining.
 It is space consuming for files and folders.
 It has data duplication, robustness, too much paper work and slow retrieval of
data.
 It has no proper security (unauthorized user can access easily).
So, our purpose is to solve these problems and provide ease to daily operations and
management.

1.2 Scope
In our EMS the old and manual system is transitioned to a new computerized system.
Different modules will be constructed based on the requirements gathered from
personal observations. Main entities like Department and Employee will have separate
modules and will be managed by the Administrator by using their corresponding
modules
1.3 Definitions, Acronyms and Abbreviations

Term/ Abbreviation Description

EMS Employee Management System

DEO Data Entry Operator

4
1.4 References
Websites
 http://sce.uhcl.edu/helm/RUP_course_example/courseregistrationproject/artifa
cts/requirements/vision.htm#_Toc485116512

1.5 Overview
This document provides the introduction of the EMS, stakeholders and the description
of their interaction with the desktop Based system, and system overview and the
market assumptions about the cost of the system being developed.

2. Positioning
2.1 Business Opportunity
The previous system in use is totally manual and it is hard to use and manage. To keep track of
simple tasks it requires an immense amount of time and energy. So, to fulfill the requirements of
the stakeholders we are developing a computerized EMS. By doing this the productivity of the
business will increase and the overall procedure to manage all information will be simplified.

2.2 Problem Statement

Previous EMS is totally manual which leads to the mishandling of the records of
Employee. Overall procedure of maintaining record is very time consuming and
The problem of complex, specially while making a report to make any decision and there is no
sense of security. All the files are in a drawer and if a person can access the
drawer he can access everything leaving the business vulnerable

Effects Administrator and DEO as they have to tackle all the information manually

Employee records are often misplacing the data, so the security is not
The impact of maintained & it’s hard keeping track of the salary and Performance of
which is Employee and often gives errors in manual calculations

A system which provides simplicity and efficiency with compromising the

A successful
security of the business. An error free system and will providing best
solution would be
management of Employee. This system will be reliable, and efficient

5
 2.3 System Position Statement

For BSCS OOSE Project

The existing environment has no such system being used, which provides
Who automatic management of employee, salary, department, attendance and
performance record

The
(Product Employee Management System (EMS)
name)

Keeps many records Department, Employees information and their Salary,

That
Attendance and Performance

Manual EMS, that is not suitable for holding large number of records due
Unlike
to storage problems, lack of security, Performance issues

Uses new technologies for development. This system is going to be built

by keeping in mind the latest business requirements. By providing better
Our Product
Performance, security, reliability so that the business runs efficient and
fast.

3. Stakeholder and User Descriptions

3.1 Stakeholder Summary

Name Represents Role

No contribution in the
Administrator Primary Actor
development, just user
No contribution in the
DEO Primary Actor
development, just user

6
 3.2 User Summary

Name Description

It will interact with system after installation he/she can add,

Administrator
update, search & generate report in each module

Will enter data and manipulate that data according to the

DEO
privileges given by the Administrator

3.3 Stakeholder Profiles

3.3.1 Administrator

Representative Not defined

Type Primary Actor

This stakeholder must be enough educated to fully understand and

Description able to use the system.
This stakeholder will use the system to update, search and generate
Responsibilities report of the entries in the EMS

The Administrator is the stakeholder who will define the success if he

Success Criteria will totally satisfy with the system

Involvement Nil

Deliverables There will be no deliverables provided to and by this stakeholder

With respect to this stakeholder this project is reliable that it should

Comments Issues always deliver the correct and timely Information

7
 3.3.2 DEO

Representative Not Defined

Type Primary Actor

This stakeholder must be able to understand the system and able to do

Description data entry in system

Responsibilities A person who will use the system could add, search and generate reports

Success Criteria Successful and satisfactory entry and retrieval of data

Involvement Nil

Deliverables There will be no deliverables provided to and by this stakeholder

With respect to this stakeholder this project is reliable that it should

Comments Issues always deliver the correct information

3.4 Key Stakeholder / User Needs

Existing system manages records manually and can’t be updated efficiently as required.
EMS will provide, maintain, efficiently update handling different situations etc. and will
be easy to access each record available in EMS when needed at once or at different
times

4. System Overview
This system is being made to replace the old manual system. The main idea is to have
easy access to the records and managing them efficiently. This alternate to the manual
system will provide the main feature of digitally accessing the different records, which
was not possible before. The users will have their own accounts, separate according to
user category, where they will be able to enter records according to privileges

8
 4.1 System Perspective
This EMS is a completely new system for the users of Business Community. It has the
database of Employees and Departments.

4.2 Summary of Capabilities

Benefit Supporting Features

Users will digitally access

Digital information is easy to access
information

Computerized system plus digital

Administrator would manage the
information management using
system easily as compared to
computers makes management
existing manual system
easier

System can generate different Computerized system settings will

types of reports according to always make the business running
given criteria efficiently

4.3 Assumptions and Dependencies

The Default language of the EMS is English, so the user of the system should be able to
read, write and perceive the proper meaning and should be able to understand
On the developing side the implementers should be familiar with the programming
languages used

4.4 Cost and Pricing

This is our Semester Project & have no Cost & Pricing

4.5 Licensing and Installation

All the installation rights will be mentioned in the license agreement. Installation of the
system will take place after complete development

5. System Main Features

 Security management
 Department management
 Employee management
 Salary Management
 Attendance Management

9
6. System Priorities

1. Security Management
 Process Login  Priority: High
 Change Password  Priority: High

2. Department management
 Add Department  Priority: High
 Search Department  Priority: High
 Update Department  Priority: High
 Generate Department  Priority: High
Information
3. Employee management
 Add Employee  Priority: High
 Search Employee  Priority: High
 Update Employee  Priority: High
 Generate Employee  Priority: High
Information

4. Salary Management  Priority:

High
 Add Salary  Priority:
High
 Search Salary  Priority:
High
 Update Salary  Priority: High
 Generate Pay Slip

5. Attendance Management
 Add Attendance
 Priority: High
 Search Attendance
 Priority: High
 Update Attendance
 Priority: High
 Generate Monthly  Priority: High
Attendance Report
 Priority High
 Generate Annual
Attendance Report

7. Constraints
The system is only compatible for the Windows Platform. Since we are using powerful
tools i.e. Visual Studio 2017 with C# and MS SQL Server therefore the system on which
this whole EMS is installed must be at least single core 2 GHZ.

10
 8. Quality Ranges
 Accuracy
Our system will meet the specified requirements. The result generated will be
consistent and according to the requirements.

 Performance
The EMS has a simple GUI, so that the users of the system will not have any
problem in handling the system. The overall experience of the usage will be satisfactory.
Standard queries will take no longer than 2-3 second
 Security
Our EMS provides better security by authenticating users and giving them access
to the system according to their privileges. Without proper authentication no one can
access the system

 Usability
The system will be easy to use. The EMS has a simple GUI, which is menu based
and has all of the components arranged logically so that the users of the system will not
have any problem in handling the system. The overall experience of the usage will be
satisfactory
 Availability
As the system is a desktop application it will run for as long as the user wants it
to run

9. Other Item Requirements

9.1. System Requirements
9.1.1. Platform
The system must use windows platform
9.1.2. Printer
Printer is used to print the required form or and reports (if required)
9.1.3. Hardware requirements
Pentium IV or above

11