Add Thesis

Salary Management System

Written by Muhammad Azeem, Masud Ur Rehman

Paper category

Master Thesis

Subject

Computer Science

Year

2011

Abstract

Thesis: Why customized solutions There are many software tools on the market that can calculate employee salaries. Now the question is, why do we need to build a customized software? 2.1.1 Software available on the market There are many software available on the market, and organizations are using them to calculate the salaries of their employees. Here we take two software examples for discussion. 2.1.2 Analysis of different salary calculators Salary calculation software This software can calculate employee salaries based on the data provided by the job tracking system. It is basically a combination of "work management software" and "salary calculation" two systems. The second is completely dependent on the first system, which uses data as input to the work management software and calculates wages based on these data. The software has the following functions: • "Planning projects", "tracking work results, helping managers define work results" • "Helping to calculate wages from work results" [1] Wage calculation software analysis • The software is promoting work management and task scheduling More than salary calculation. Salary calculation is one of its secondary features, and work management is its main feature, which is not required by the Swedish Sports Academy. They work well, are satisfied with AMGs, the existing employee management system, and are planning, scheduling, and task management. • The software does not provide any functions for calculating taxes and social security. • The software cannot generate payroll and bank/invoiceslips. • The company must purchase a license for each user to use the software. • The software does not provide any interfaces or plug-ins that can be used to merge it with existing systems used in the organization. • As the company develops, the system may need to be strengthened, or if the company needs to make any changes to the system, it is difficult to achieve the goal of always delivering the purchased software in the form of .exe. Spine Payroll "This is a very simple, flexible and user-friendly payroll management software designed for India, which can meet all requirements related to employee payroll accounting and management. Spine payroll stores the complete records of employees, generates payroll, Attendance register, calculate all allowances, deductions, and generate all statutory and MIS reports." [2] Spine Payroll System analyzed that the software may be a substitute for our software to some extent, but the organization still does not need it for the following reasons it. • The organization needs a customized solution that can perform the tasks discussed earlier. 2.2 Employee Salary Management System The system we will develop according to user needs will perform salary calculation, tax calculation and document processing, such as payroll and bank invoices. In addition, the system will be user-friendly and flexible enough to be enhanced according to user needs in the future. Requirements analysis In this chapter, we will discuss requirements, system design, and analyze them using some appropriate software models. 3.1 Methodology We found that the software development method most suitable for our software development is the waterfall software development model, which gives us a clear view of our software and helps us achieve our goals. 3.2 SDLC Waterfall Small and medium-sized software is usually divided into six stages, these stages are related to each other in a top-down manner, called waterfalls. The input of a particular stage is the output of the previous stage, which initiates the next stage. At each step or stage of the model, some additional information is also added to the input of that stage and the result is generated. But the additional information is limited in scope, and the previous stage can be traced directly from that stage. The first stage of the waterfall model is the planning stage, where the most critical task is to clearly mention the high-level requirements or goals of the software. It helps to formulate the feasibility and risks associated with the project and provides the basic project structure. The next stage is the requirements definition stage, from the planning stage to the goals as input, and then define these goals as a group or multiple requirements. Define the main functions, initial data entities and operating data areas at this stage. The input of the design phase is the output of the requirements phase, and the requirements phase is the approved requirements document. At this stage, design elements are defined with the help of interviews, prototypes and workshops. These design elements include functional hierarchies, business flowcharts, pseudo code, and entity relationship diagrams. These design elements provide a detailed description of the software, and each element is related to a specific requirement. The development phase is initiated by the previous design phase. At this stage, the code of the software design elements is written and the functional software components are provided. The integration and testing phases provide the output of the development phase. At this stage, the different software functional components developed in the previous stage are integrated with each other to provide a complete software project which provides all the high-level requirements. The software also passed different test cases to check the validity, correctness, and completeness, so that we can achieve the goals of our project. Read Less