04-08-2012, 02:52 PM
PAYROLL MANAGEMENT SYSTEM
Payroll-Management-System.pdf (Size: 385.93 KB / Downloads: 1,023)
INTRODUCTION TO PROJECT
Domain Description
Industry employs full-time and casual (contractual) academics. Employees in the
Personnel Department will use the system to maintain employee information, manage
leave, and make payments to the academics every fortnight.
The Payroll system can add new employees and delete employees. It can manage annual
and long-service leave as well as record any sick leave. The system must pay each
academic the correct amount, on time, and by the payment method requested by an
academic.
Employees in the Personnel Department will access system via a Windows-based
desktop interface.
However, the system will also provide a web-based access (called Academic Kiosk)to
full-time academics to view their payment details, leave balances, and personal
information. Some of this information, such as personal details and payment method, can
be updated by academics using the web-based interface.
The Payroll system verifies if the total hours worked so far do not exceed the number of
hours agreed in the contract. The contract information is maintained by another system
called Contracts Management, however the Payroll system stores basic information about
contracts, in particular hourly rate for each contract. The industry deducts standard tax
rates from payments made to full-time academics.
Casual academics can request receiving payment notifications by mail or by email. Fulltime
academics employees do not receive payment notifications but they can use
Academic Kiosk to query the system about fortnightly payments, total salaries received
year-to-date, tax and other deductions, leave balances, etc. As mentioned, Academic
Kiosk can be used to modify personal details and payment method.
The academics can choose the payment method. The payments can be mailed (as bank
cheques) to academics to the postal address of their choice. Alternatively, the payments
can be directly deposited into an academic’s bank account.
Objectives
Employees are the backbone of any company; their management pays a major role in
deciding the success of the organization. Employee information management helps in
deciding the future management needs and any changes that has to be made for greater
productivity. It keeps the records of the functions performed by the individual employee
playing a vital role at the time of performance appraisal. Employee management software
can carry out many functions like employee data analysis, employee monitoring,
centralized employee database, management of the time sheet, etc.
The usage of payroll management system would ultimately reduce the overall
management costs thus ensuring greater profits and reduced burdens. The system is very
easy to use and can adjust into any business frame.
Limitations of the existing system
The institute doesn’t have any software application which maintains data of the
employees. The record keeping is done manually. This leads to great difficulty when
certain needs arrive of looking into employees’ past data.
The institute uses a payroll application which has limited features and doesn’t work
efficiently and effectively. It doesn’t fulfill many requirement of the administrative
department. The application just keeps very trivial information of the employees and
doesn’t facilitate with any kind of analytical ability.
.FEASIBILITY ANALYSIS
We have analyzed the feasibility of the system in terms of following spans:
1. Technical Feasibility
2. Operational Feasibility
3. Economical Feasibility
4. Scheduled Feasibility
2.1 Technical Feasibility: The development process of Payroll Management System
would be advantageous to the organization because we would make use of only the
currently available resources of the organization. All the tools needed for the
development are already available with the organization and the organization does not
have to acquire any new resources. The technical feasibility is also attributed to the fact
that the system does not make use of any additional or external third party components
which can lead to increased load on the system.
Operational Feasibility: The Payroll Management System is intended to provide a
very user-friendly and easy to use interface which is beneficial for both the visitors as
well as the operators who help in providing support for the system. This system would
also be easily acceptable among the visitor and administrator, as there is no need of any
special skill set for using the application. This system also benefits the users as they do
not have to download anything on their terminals increasing their efficiency and ease of
use.
Economic Feasibility: The Payroll Management System has a very low
development cost. The low cost is attributed to the usage of the existing resources of the
organization. As the website is very user friendly and easy to use, there is no need to
provide special training to the users of the website, thus saving valuable time and money.
Scheduled feasibility: Projects are always given deadlines. Every project is
completed in a specific duration. I was the only working on the project and I had the
project duration of four months only. So i have tried our level best to fulfill each and
every requirement. I had to complete the project in time and if it is not possible to
complete the software in time then I would try our best to fulfill client requirements.
DEVELOPMENT MODEL
The Payroll Management System is a database software application which is developed
using a waterfall software developing model.
The waterfall model is a popular version of the systems development life cycle model for
software engineering. Often considered the classic approach to the systems development
life cycle, the waterfall model describes a development method that is linear and
sequential. Waterfall development has distinct goals for each phase of development.
Imagine a waterfall on the cliff of a steep mountain. Once the water has flowed over the
edge of the cliff and has begun its journey down the side of the mountain, it cannot turn
back. It is the same with waterfall development. Once a phase of development is
completed, the development proceeds to the next phase and there is no turning back.
The advantage of waterfall development is that it allows for departmentalization and
managerial control. A schedule can be set with deadlines for each stage of development
and a product can proceed through the development process like a car in a carwash, and
theoretically, be delivered on time. Development moves from concept, through design,
implementation, testing, installation, troubleshooting, and ends up at operation and
maintenance. Each phase of development proceeds in strict order, without any
overlapping or iterative steps.