10-04-2012, 04:31 PM
payroll system
repot.doc (Size: 192.5 KB / Downloads: 59)
. Introduction
The “payroll system” is a useful software for maintaining the employees overall record in an company. It makes easy to retrieve and manipulate the employee’s information. It maintains the database for employees. These database are related with employee’s academic as well as personal information. This software helps it’s users to easily access the employee record. It uses the different authentication level to access and manipulate the information. In this way it also acts as a secure software. To maintain the security this software provide different authentication to different user. If an user want to change the personal information of a employee then he does not provided the authority to make changes in the personal information , this authority is given only to the employees can only see that information.
The system will retain information on all employee in the company (Acme currently has around 5000 employees word-wide ) The system must pay each employee the correct amount, on time, by the method that they specify (see possible payment methods described later).
Problem definition
As the head of Information Technology at Acme, Inc you are tasked with building a new payroll system to replace the existing system which is hopeless out of date. Acme needs a new system to allow employees to record time card information electronically and automatically generates paychecks based on the numbers of hour’s worked and total amount of sales (for commercial employees).
Problem Solution
To recover all the problems mentioned above the software should be provided with different accessing rights to different users of the software. All users have different user authentications related to the sections to modify existing data and enter the new data in the database. It maintains multiple databases related to the particular section. The “payroll system” is the software which uses multiple user authentications, every authorized user of any section can enter and modify the database related to that particular section only, but it can only see the other section’s databases.
Need & Scope of the project
This Supplementary Specification applies to the payroll System which will be developed by the developer.
This Specification defines the non-functional requirements of the system such as rehabilitee, usability, performance and supportability as well as functional requirements that are common across a number of use-cases. (The functional requirements are defined as the Use Case Specifications).
Requirement Analysis
Software Engineering Paradigm Applied
Rapid application development is a software development methodology, which involves iterative development and the construction of prototypes. It is a merger of various structured techniques, especially the data driven Information Engineering with prototyping techniques to accelerate software systems development.[1]
FUNCTIONALITY OF CURRENT EXISTING SYSTEM
The current existing system for retrieving information of employee is quit similar than my software works. But old application needs to open one and more than one application for getting the Employees information Form different different database. But with the existence of New student information System some what problem is solved. The software operators some time do some mistakes because of the complexity of the software.
PRIMARY JOB BY CURRENT SYSTEM
The primary job by the current system is:
Maintain the record of the Employees of different different Section.
Making a simple list of employee name, employee address and contact no. for faster access when user require particular information about Employee form different databases.
Types of Risk
Project Risk:
Project risks threaten the Project Plan. For example, if a project risk occurs in reality, it is likely that the project schedule will slip and that the costs will increase. It identifies project budgetary, schedule, personnel, resources, customer and requirements problem and their impact on software project.
Technical Risk:
Technical risks threaten the quality and the timeliness of the software to be produced. A technical risk makes implementation difficult or at times, impossible, It identifies potential design, implementation, interface, verification and maintenance problems. It occurs because the problem is harder to solve than we thought it would be.
Business Risk:
Business risks threaten the viability of the software to be built. This risk occurs when a product or a system is built correctly but is not wanted in the market (known as Market Risk). (1) building a product that no larger fits into the overall business strategy for the company (strategic risk), (2) building a product that the sales force does not understand how to sell, (3) losing the support of senior management due to a change in people (management risk), and (4) losing budgetary or personnel commitment (budget risk).
Known Risk:
Known risks are those risks that are previously known to the developers. These risks include the delays related to the delivery related to the delivery date of the project.
Limitation & Future Enhancements
8.1 Limitation of Project
1.Confined to only company.
2.Skilled and well educated users are required to work on the software.
3.Advanced hardware configuration is required.
4.Chance of data redundancy.
Conclusion-
This Application provides facility to maintain the employees overall record in a company. It makes easy to retrieve and manipulate the employee’s information. These database are related with employee’s academic as well as personal information. This software helps it’s users to easily access the employee record. This test System is developed using Java.