IT510 Advanced Information TechnologyOF U
tarstr
payroll_management_system_final_project.docxSouthern New Hampshire University
T 510 Homework Activity Module 4-2
Professor Chakib Chraibi
By: Tyrone Armstrong
Payroll Management System
Introduction:
It is obvious that want to get rid of managing millions of salary details, odd papers, payroll reports, and pay slips and so on. So we need a payroll processing system that can generate payroll reports and pay slips within seconds. This can be done by automating the existing payroll system using a fully customized application that fits to the specific set of requirements. (Tom, 2012)
Purpose of the Payroll automation:
Main purpose of managing employee payroll system is to create an easy and simple way not just to automate all of the functionalities that are involved in payroll and managing leaves for the employees, but also to keep reports of each and every transaction for company management department with all of the details regarding practice of leave facility.
The purpose of this project is to bring out the best management methods in different forms of EPM that is in not a product that can be sold, but a tool for managing the inner operations of Company regarding Payroll and employee leave. (Tom, 2012)
Performance of existing information technology systems:
(a) Present state: Presently salary collection is done manually. Through cross check and direct cash. All the record is maintained in MS Excel and this cause record Duplication and mixing etc. Sometimes the client forgot to save the record in excel sheet and the record is to be entered again.
(b) Problem Statement: composing salary of all employees is a time taking process; also it takes a lot more time to prepare salary slips in manual systems. As a result a huge delay in salary distribution is faced by employees. This is a big problem to manage when salary is not generated in time; the other main problem is error. The chances of error are more in manual system. To solve all these problem we have to develop a software which will take good care of these problems.
(c) Audience:
1) Employees
2) Cashier
3) Manager
(d) Systems Requirements:
1. User interfaces:
The software will provide a responsive graphical interface on the front end that is self explanatory.
2. Hardware interfaces :-
· Memory of at least 1GB RAM
· With a Hard disk (40 GB)
· A Monitor (interactive system are preferred)
· A Mouse (pointing device)
· A Keyboard (keypad)
· A Printer
3. Software interfaces :
· Operating System: Windows 7.
· For Front End : Microsoft VB.Net 2008
· At Back-end : MS SQL Server 2008
4. Communication interface:
· Windows Forms
Functional requirements:
· Masters:
· Employee
· Search
· Attendance
· Salary
· Report
Performance requirements:
· Entire system as a whole should be error free and efficient
· It must have built in correction and error checking facilities.
· The system can handle a huge amount of data easily.
Data Process Model:
Data Flow Diagram:-
Level 1 (High Level Diagram
2nd Level DFD
2nd Level DFD
2nd Level DFD
Data Dictionary
B.Circular Details
c. list of amendments done on previous version no.
Data Dictionary
1. Table Name: PAY_ALLOWANCE_DEDUCTION
Purpose:
|
Sl. |
Field Name Data Type Size Is Required/Not |
Key |
Description |
||
|
1 |
[ALLOW_DEDUC_ID] [int] NOT NULL |
P |
U |
|
Allowance and Deduction id |
|
2 |
[ALLOW_DEDUC_NAME] [varchar50) NULL |
|
U |
|
Allowance and deduction name |
|
3 |
[DESCRIPTION] [varchar50) NULL |
|
|
|
Description of the Allowance and Deduction |
|
4 |
[AllowanceDeductionType] [varchar10) NULL |
|
U |
|
Allowance and deduction type |
|
5 |
[APPLICABLE] [bit] NULL |
|
|
|
Allowance or Deduction is applicable or not |
|
6 |
[VW_ORDER] [int] NULL |
|
|
|
Vworder |
|
7 |
[CreatedBy] [int] NULL |
|
|
|
Data Creation User ID |
|
8 |
[CreatedDate] [datetime] NULL |
|
|
|
Data Creation Date |
|
9 |
[UpdateBy] [int] NULL |
|
|
|
Data Updating User ID |
|
10 |
[UpdateDate] [datetime] NULL |
|
|
|
Data Updating Date |
2. Table Name: PAY_Bonus
Purpose:
|
Sl. |
Field Name Data Type Size Is Required/Not |
Key |
Description |
||
|
1 |
[BonusId] [int] NOT NULL |
P |
|
|
ID of the Bonus |
|
2 |
[BonusName] [varchar50) NOT NULL |
|
U |
|
Name of the Bonus |
|
3 |
[ALLOW_DEDUC_ID] [int] NOT NULL |
|
U |
FK |
Allowance and Deduction id |
|
4 |
[CompanyId] [int] NULL |
|
U |
FK |
Company Id |
|
5 |
[CalculationId] [int] NULL |
|
U |
FK |
Calculation Id |
|
6 |
[CreatedBy] [int] NULL |
|
|
|
Data Creation User ID |
|
7 |
[CreatedDate] [datetime] NULL |
|
|
|
Data Creation Date |
|
8 |
[UpdateBy] [int] NULL |
|
|
|
Data Updating User ID |
|
9 |
[UpdateDate] [datetime] NULL |
|
|
|
Data Updating Date |
3. Table Name: PAY_BonusEmployeeMapping
Purpose:
|
Sl. |
Field Name Data Type Size Is Required/Not |
Key |
Description |
||
|
1 |
[MappingId] [int] NOT NULL |
P |
|
FK |
ID of the Mapping |
|
2 |
[MappingType] [varchar20) NULL |
|
U |
|
Mapping Type |
|
3 |
[MappingRefId] [varchar30) NULL |
|
U |
|
Mapping Reference ID |
|
4 |
[BonusId] [int] NULL |
|
U |
FK |
Bonus Id |
|
5 |
[BranchId] [nvarchar4) NULL |
|
U |
FK |
Branch Id |
|
6 |
[CreatedBy] [int] NULL |
|
|
|
Data Creation User ID |
|
7 |
[CreatedDate] [datetime] NULL |
|
|
|
Data Creation Date |
|
8 |
[UpdateBy] [int] NULL |
|
|
|
Data Updating User ID |
|
9 |
[UpdateDate] [datetime] NULL |
|
|
|
Data Updating Date |
4. Table Name: PAY_DisburseMain
Purpose:
|
Sl. |
Field Name Data Type Size Is Required/Not |
Key |
Description |
||
|
1 |
[DisburseId] [bigint] NOT NULL |
P |
U |
|
ID of the Disburse |
|
2 |
[DisburseDate] [datetime] NULL |
|
|
|
Disburse Date |
|
3 |
[VoucherNo] [varchar30) NULL |
|
U |
|
Voucher No |
|
4 |
[BranchId] [nvarchar4) NULL |
|
U |
FK |
ID of the Branch |
|
5 |
[CreatedBy] [int] NULL |
|
|
|
Data Creation User ID |
|
6 |
[CreatedDate] [datetime] NULL |
|
|
|
Data Creation Date |
5. Table Name: PAY_DisburseSData Updation User ID
Purpose:
|
Sl. |
Field Name Data Type Size Is Required/Not |
Key |
Description |
||
|
1 |
[DisburseId] [bigint] NOT NULL |
|
U |
FK |
ID of the Disburse |
|
2 |
[EmployeeId] [int] NOT NULL |
|
U |
FK |
ID of the employee |
|
3 |
[PaymentMethod] [varchar50) NOT NULL |
|
|
|
Payment Method |
|
4 |
[Amount] [decimal18 2) NOT NULL |
|
|
|
Disburse Amount |
|
5 |
[ReferenceId] [nvarchar50) NULL |
|
U |
|
Reference ID |
|
6 |
[BankAccountSerialNo] [int] NULL |
|
U |
|
Bank Account Serial No. |
6. Table Name: PAY_SALARY_SHEET_MAIN
Purpose:
|
Sl. |
Field Name Data Type Size Is Required/Not |
Key |
Description |
||
|
1 |
[SALARY_SHEET_ID] [bigint] NOT NULL |
P |
U |
|
ID of the Salary Sheet |
|
2 |
[SALARY_YEAR] [int] NOT NULL |
|
U |
|
SALARY YEAR |
|
3 |
[SALARY_MONTH] [int] NOT NULL |
|
U |
|
Salary Month |
|
4 |
[VARIFIED_BY] [varchar50) NULL |
|
|
|
Verified by User |
|
5 |
[APPROVED_BY] [varchar50) NULL |
|
|
|
Approved by User |
|
6 |
[VARIFIED_DATE] [datetime] NULL |
|
|
|
Verified Date |
|
7 |
[APPROVED_TIME] [datetime] NULL |
|
|
|
Approval Time |
|
8 |
[BranchId] [nvarchar4) NULL |
|
U |
FK |
ID of the Branch |
|
9 |
[CreatedBy] [int] NULL |
|
|
|
Data Creation User ID |
|
10 |
[CreatedDate] [datetime] NULL |
|
|
|
Data Creation Date |
7. Table Name: PAY_SALARY_SHEET_SDATA UPDATION USER ID
Purpose:
|
Sl. |
Field Name Data Type Size Is Required/Not |
Key |
Description |
||
|
1 |
[IntermediateId] [int] NOT NULL |
P |
U |
|
ID of the employee |
|
2 |
[ALLOW_DEDUC_HEAD] [int] NOT NULL |
P |
U |
|
Head of the Allowance or Deduction |
|
3 |
[AMOUNT] [decimal18 2) NOT NULL |
|
|
|
Amount of the pay salary |
|
4 |
[BonusId] [int] NULL |
|
U |
FK |
ID of the Bonus |
8. Table Name: PaymentMain
Purpose:
|
Sl. |
Field Name Data Type Size Is Required/Not |
Key |
Description |
||
|
1 |
[PaymentId] [nvarchar16) NOT NULL |
P |
|
|
ID of the payment |
|
2 |
[PaymentDate] [datetime] NOT NULL |
|
|
|
Payment Date |
|
3 |
[BranchId] [char4) NOT NULL |
|
U |
FK |
ID of the Branch |
|
4 |
[SupplierId] [int] NOT NULL |
|
U |
|
ID of the Supplier |
|
5 |
[Amount] [decimal18 2) NOT NULL |
|
|
|
Amount of the payment |
|
6 |
[CashAmount] [decimal18 2) NOT NULL |
|
|
|
Cash Amount of the payment |
|
7 |
[ChequeAmount] [decimal18 2) NOT NULL |
|
|
|
Cheque Amount of the payment |
|
8 |
[CreatedBy] [int] NOT NULL |
|
|
|
Data Creation User ID |
|
9 |
[CreatedDate] [datetime] NOT NULL |
|
|
|
Data Creation Date |
|
10 |
[UpdateBy] [int] NOT NULL |
|
|
|
Data Updating User ID |
|
|
[UpdateDate] [datetime] NOT NULL |
|
|
|
Data Updating Date |
9. Table Name: PaymentSData Updation User IDSData Updation User ID
Purpose:
|
Sl. |
Field Name Data Type Size Is Required/Not |
Key |
Description |
||
|
1 |
[PaymentId] [nvarchar16) NOT NULL |
|
U |
FK |
ID of the Payment |
|
2 |
[PaymentMethodId] [int] NOT NULL |
|
|
|
Method of the Payment |
|
3 |
[GLCode] [varchar50) NOT NULL |
|
|
|
Code of the GL |
|
4 |
[Amount] [decimal18 2) NOT NULL |
|
|
|
Payment Amount |
|
5 |
[RefNo] [varchar15) NULL |
|
U |
|
Reference No. |
|
6 |
[RefDate] [datetime] NULL |
|
|
|
Reference Date |
|
7 |
[BankBranchId] [varchar4) NULL |
|
U |
FK |
ID of the Bank Branch |
|
8 |
[CreatedBy] [int] NOT NULL |
|
|
|
Data Creation User ID |
|
9 |
[CreatedDate] [datetime] NOT NULL |
|
|
|
Data Creation Date |
|
10 |
[UpdateBy] [int] NOT NULL |
|
|
|
Data Updating User ID |
|
11 |
[UpdateDate] [datetime] NOT NULL |
|
|
|
Data Updating Date |
|
12 |
[VoucharNo] [varchar50) NULL |
|
U |
FK |
Vouchar No. |
FEASIBILITY ANALYSIS:
We have analyzed the feasibility of the system in terms of following spans:
1. Technical Feasibility
2. Feasibility 3.
3. Economical Feasibility
4. 4. Scheduled Feasibility
Technical Feasibility: The advance process of payroll the Management structure would be helpful to the organization since we would create use of one of the presently available reserves of organization. All tool required for development of are previously available for organization and the organization does not ensure to acquire new reserves. The technical possibility is also ascribing to fact that system does not create use of any extra or extra third party components, which can lead to, increased load on the system.
Operational Feasibility: Payroll Management the System is proposed to give a very accessible and easy to usage interface. Which is helpful for mutually the operators and visitors who support in delivering help for system. This system would be without difficulty acceptable between the visitor and the administrator, as there is no requirement of any distinct skill set for operating application. This system also advantages the handlers, as they do not require downloading everything on their terminals rising their proficiency and comfort of use.
Economic Feasibility: Payroll Management the System has a extremely less development the cost. The less cost is ascribed to use of current resources of organization. As website is extremely user responsive and simple to use, here is not essential to give extraordinary training to users of website, therefore saving precious money and time.
Scheduled feasibility: The Projects are continuously provided the deadlines. Each project is finished in a particular duration. I was the only functioning on this project and I had project period of three months only. Thus I have attempted best to complete each and every necessity. I had to finish project on the time and if it were not promising to complete software on the time in that case I would attempt to satisfy client requirements.
Work Breakdown Structure:-
The Project Monitoring plus the Control Plan:
First 3 weeks we had to do meetings with the client and gather as much requirements as the want to be in software. Afterward we will arrange about it that in what way to start. After finishing step 1 just become the calculations that how far it will take to finish and how far resources would be used up.
In this phase we will monitor our project that how is it going and if there are some issues then we will try to control them for achieving successful results.
Timeline/ Gantt chart:-
Use Case Diagram:-
Data Design:-
ER diagram:
References:
· (n.p) “GITL Products – Payroll” retrieved on 23rd May 2015 from:
http://www.godrejinfotech.com/products/payrollb2e.html
· Tom Jhons Bolipata, 14 November 2012, “AUTOMATED PAYROLL SYSTEM OF TRECE MARTINES CITY NATIONAL HIGH SCHOOL “retrieved on 23rd May 2015 from: https://prezi.com/gqrsj7vc0e9g/chapter-iii/
