Sunteți pe pagina 1din 11

VISION

For

PAYROL MANAGEMENT SYSTEM

Version 1

Prepared by
Shah Qasim
&
Salahudin Akram
Revision History

Version Description Author Date


1.0 First Release/Initial Release Shah Qasim 21 Dec,2019
&
Salahudin Akram
Table Contents

1. Introduction ----------------------------------------------------------------------------------------------------------------------------
1.1 Purpose-----------------------------------------------------------------------------------------------------------------------------
1.2 Scope--------------------------------------------------------------------------------------------------------------------------------
1.3 Definitions, Acronyms and Abbreviations----------------------------------------------------------------------------------
1.4 References-------------------------------------------------------------------------------------------------------------------------
1.5 Overview---------------------------------------------------------------------------------------------------------------------------

2. Positioning---------------------------------------------------------------------------------------------------------------------------------

2.1 Business opportunity--------------------------------------------------------------------------------------------------------

2.2 Problem statement----------------------------------------------------------------------------------------------------------

2.3 System Positioning Statement--------------------------------------------------------------------------------------------

3. Stakeholder and User Descriptions--------------------------------------------------------------------------------------------------

3.1 Stakeholder Summary-----------------------------------------------------------------------------------------------------------

3.2 User Summary---------------------------------------------------------------------------------------------------------------------

3.3 Stakeholder Profiles--------------------------------------------------------------------------------------------------------------

3.3.1 Administrator---------------------------------------------------------------------------------------------------------------
3.3.2 Data Entry operator-------------------------------------------------------------------------------------------------------
3.4 Key Stakeholder / User Needs-------------------------------------------------------------------------------------------------
4. System Overview------------------------------------------------------------------------------------------------------------------------
4.1 System Perspective--------------------------------------------------------------------------------------------------------------
4.2 Summary of Capabilities--------------------------------------------------------------------------------------------------------
4.3 Assumptions and Dependencies----------------------------------------------------------------------------------------------
4.4 Cost and Pricing-------------------------------------------------------------------------------------------------------------------
4.5 licensing and Installation-------------------------------------------------------------------------------------------------------
5. System Main Features-----------------------------------------------------------------------------------------------------------------
6. System Priorities-------------------------------------------------------------------------------------------------------------------------
7. Constraints--------------------------------------------------------------------------------------------------------------------------------
8. Quality Ranges---------------------------------------------------------------------------------------------------------------------------
9. Other Item Requirements------------------------------------------------------------------------------------------------------------
9.1 System Requirements ---------------------------------------------------------------------------------------------------------
9.1.1 Platform--------------------------------------------------------------------------------------------------------------------
9.1.2 Printer----------------------------------------------------------------------------------------------------------------------
9.1.3 Hardware Requirements-----------------------------------------------------------------------------------------------
Introduction

Payroll System is the heart of any Human Resource System of an organization. It is understood that we
are tired of managing thousands of odd papers. Pay slips, payroll reports, and salary details and so on.
Imagine that we have a payroll processing system which will generate our pay slips and pay reports
within seconds .We can help others automated your payroll system by developing a customized payroll
application that suits your specific requirements.
1. Purpose
Main aim of developing employee payroll Management is to provide an easy way not only to automate
all functionalities involved managing leaves and payroll for the employees of company. But also to
provide full functional reports to management of company with the details about usage of leave facility.
2. Scope
This application works in multiple PC’s installed on multiple Computers but sharing same database by
which users of different departments can use it sitting at different location simultaneously.
3. Definitions, Acronyms and Abbreviations
Term/Abbreviation Description
PMS Payroll Management System
RUP Rational Unified Process
UML Unified Modeling Language
DEO Data Entry Operator

4. References
Website
www.youtube.com/watch?v=4hN_vZ0NnQU
5. Overview
This document describes a compelling idea or values or future state for payroll management system. It
defines the stakeholder view of the product and for every to be developed. Specified in term of the
stakeholder key needs and features.
6. Positioning

Business Opportunity

Businesses can be thankful who handle the payroll management .Generally business owners are
spending their time to manage peoples, employee salary management, client management etc. We can
handle up to 20 employees using MYOB Payroll because it allows to creating payroll data file which
can pay.
Problem Statement

The problem of Previous PMS is totally manual which leads to the mishandling of the
records of employees overall procedure of maintaining records is very
time consuming and complex. Specially while making an employee’s
pay slip etc. It is very difficult and time consuming and there is no
sense of security. And difficult to maintain the deduction information.
Effects Users records 0f the employee etc, are often misplaces the data so the
security is not maintained and its hard keeping track of the payments
and often gives errors in manual calculations.
The Impact of which is Paying employees consistently and with no delays not only impacts
their morale, but it also reflects the company’s financial stability ….In
essence ,the payroll management process refers to the administration of
an employee’s financial records which includes the salaries , wages,
bonuses, deductions, and net pay.
A successful solution would A system which provides simplicity and efficiency with compromising
be the security of the business.
An error free system and will providing best management of employees
etc. This system will be reliable and efficient.
2.3. System Positioning Statement

For Semester Based Project


Who The existing environment has no such system being used, which provides automatic
management of salary records, employee‘s record.
The Payroll management system
That Keeps a large number of records of employees, salaries and employee’s dues.
Unlike Manual PMS, that is not suitable for holding large number of record due to storage
problems, lack of security, performance issue.
Our Product Uses new technology for development. This system is going to be built by keeping in
mind the latest business requirements. By providing better performance, security,
reliability so that the business runs efficient and fast.
Stakeholder and User Descriptions
3.1 Stakeholder Summary
Name Represents Role
Administrator(Primary Actor) It will provide all requirements Ensure that the system will have
that are required to complete the all records. Also add, update &
product. search a record of an employee.
DEO(Primary Actor) No contribution in the Ensure that the system will have
development ,just user all records.

3.2 User Summary

Name Description
Administrator It will interact with system after installation he can
add, update and search the data from the system.
DEO(Primary Actor) Will enter data and manipulate that data according
to the privileges given by the administrator
3.3 Stakeholder Profiles

3.3.1 Administrator

Representative Not defined


Type Primary Actor
Description He must be an educated and expert enough to tackle with the system.
Responsibilities Enter correct entries and also make change in data if required.
Success Criteria The administrator is a stakeholder who will define the success if he will totally
satisfy with the system
Involvement The administrator is a stakeholder who is involved in the project by entering
correct information in the setup screen/roles and manages all records of these
setup screens and of roles.
Deliverables There will be no deliverables provided by the stakeholder
Comment Issues With respect to this stakeholder this project is reliable that it should always
deliver the correct and timely information.
3.3.2 DEO

Representative Not defined


Type Primary Actor
Description A person who will use the system could enter
different records
Responsibilities After the system has been developed , he will be
able to only add, update and search entries as
defined by the administrator
Success Criteria Successful and Satisfactory entry of data
Involvement The data entry operator is the stakeholder who is
involved in the project by entering entries of
different things like employee’s their salary and
their dues etc.
Deliverables There will be no deliverables provided by this
stakeholder
Comment Issues With respect to this stakeholder this project is
reliable that it should always deliver the correct
information.

3.4 Key Stakeholder/User Needs

Existing manages records manually and can’t be updated efficiently as required.PMS will provide
,maintain, efficiently update handling different situations etc. and will be easy to access each and every
record available in PMS 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 user will have their own
accounts, separate according to user category, where they will be able to enter records according to
privileges.
5. System Perspective

This PMS is a completely new system for the users of Business Community. It has the database of
employee’s record salary record etc.

6. Summary of Capabilities

Benefits Supporting Features


User will digitally access information Digital information is easy to access
Administrator would manage the system easily as Computerized system plus digital information
compared to existing manual system management using computers makes management
easier
System can generate different types of reports Computerized system settings will always make
according to given criteria the business running efficiently.

4.3 Assumptions and Dependencies

Assumptions:

 It should be free with compilation errors/syntax errors.


 The product must have an interface which is simple enough to understand.
Dependencies:
 All necessary hardware and software are available for implementing and use if the tool.
 The proposed system would be designed, developed and implemented based on the software
requirement specification document.
 End users should have basic knowledge of computer and we also assure that the users will be
given software training documentation and reference material.
 The system is not required to save generate reports.

4.4 Cost and Pricing

This is our Semester project and have no cost & pricing.


4.5 Licensing and Installation

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

5. System Main Features

 Security Management System


 User Management
 Employee Management
 Reports Management
 Attendance Management
 Salary Management
 Department Management

6. System Priorities

1. Security Management

 Process Login Priority : High


 Change Password Priority : Low

2. User Management

 Register User
 Update User
 Search User

3. Department Management

 Add Department
 Update Department
 Search Department

4. Employee Management

 Add Employee
 Update Employee
 Search Employee
 Employee Salary
 Employee Attendance

5. Salary Management

 Add Salary
 Update Salary
 Search Salary

6. Attendance Management

 Add Attendance
 Update Attendance
 Search Attendance
7. Constraints
The system is only compatible for the windows platform. Since we are using powerful tools i.e. Visual Studio
2016 with c# and MS SQL server therefore the system on which this whole PMS is installed must be at least
single core 2 GHZ.
8. Quality Ranges
 Accuracy
To ensure accuracy, the payroll process can’t be rushed. Our system will meet the specified requirements.
The result generated will be consistent and according to the requirements gathered by the stakeholders.
 Performance
The PMS increase the efficiency and accuracy of the most complex and time consuming payroll processes
and it simplify the administration of your payroll process and improve the productivity. The PMS has a
simple GUI, so that the users of the system will not have any problem in handling the system. Standard
queries will take no longer than 2-3 seconds.
 Security
The crucial function of the payroll department coupled with the sensitive employee information involved
means security is a key concern. The type of information and the manner in which it is stored plays a role in
how well you keep your employee’s financial information, legal issues and personal information.
Our PMS provides better security by authenticating users and giving them access to the system according to
privileges. Without proper authentication no one can access the system.
 Usability
The system will be easy to use. The PMS 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 Requirement

9.1.1 Platform

The system must use window 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

S-ar putea să vă placă și