Ex: 1

IMPLEMENTATION OF SOFTWARE DEVELOPMENT LIFECYCLE USING PAYROLL SYSTEM

Roll: 279047 AIM: To implement all the phases of software development lifecycle using any of commercial project PROBLEM STATEMENT: As the head of information technology at Acme Inc., you are tasked with the building a new payroll system to replace the existing system, which is hopelessly out of date. Acme needs a new system to allow employees to record timecard information electronically and automatically generate pay checks based on the number of hours worked and total amount of sales (for commissioned employees). The new system will be state of the art and will have a windows-based desktop interface to allow employees to enter time card information enter purchase orders change employee preference (such as payment method), and create various reports. The system will run on individual employee desktops throughput the entire company. For reasons of security and auditing, employees can only access and edit their own timecards and purchase orders. The system will retain information on all employees in the company. The system must pay each employee the correct amount on time by the method that they specify Acme for cost reasons does not want to replace one of their legacy databases the project management database which a DB2 database is running on an IBM mainframe. The payroll system will access but not update information stored in the project management database. Some employees work by the hour and they are paid in an hourly rate. They submit timecards that record the date and number of hours worked for a particular charge number. If someone works for more than hours, Acme pays them 1.5 times their normal rate for those extra hours. Hourly workers are paid every Friday. Some employees are paid a flat salary, even though they are paid a flat salary, they submit timecards that record the date and hours worked. This is so the system can keep track of the hours worked against particular charge numbers. They are paid on the last working day of the month. Some of the salaried employees also receive a commission based on their sales. They submit purchase orders that reflect the date and amount of the sales. The 1

commission rate is determined for each employee, and is one of the 10%, 15%, 25%, or 35%. One of the most requested features of the new system is employee reporting. Employees will be able to query the system for number of hours worked, totals of all hours billed to a project (i.e., charge number), total pay received year-to-date, remaining vacation time, etc. Employees can choose their method of payment. They can have their paycheck mailed to the postal address of their choice, or they can request direct deposit and have their paycheck deposited into a bank account of their choosing. The employee may also choose to pick their paycheck up at the office. The payroll administrator maintains employee informati9on. The payroll administration is responsible for adding new employees and changing all employee information such as name, address and payment classification (hourly salaried, commissioned), as well as running administrative reports. The payroll application will run automatically every Friday and on the last working day of the month. It will pay the appropriate employees on those days. The system will be told what date the employees are to be paid so it will generate payments for records from the last time the employee was paid to the specified date. The new system is being designed so that the payroll will always be generated automatically, and there will be no need for any manual intervention.

USECASE DIAGRAM: Usecase diagram is the typical diagram of the class diagram. It deals with the attribute and properties. It deals with attributes the employee is one of the actor, the commissioned employee. This above usecase diagram describes with the actors and usecases.

login database employee entering empl details bank

employee information maintantenance

automatic generating payroll

payroll login

timecard maintenance printer report

payment choice comissioned empl system timing

maintain purchase order

system

CLASS DIAGRAM: A class diagram comprises of number of classes each with its own attributes and operations. We can represent inherited classes based upon the requirements with the arrow head representation. We can implement the concept of aggregation and generalization in the class diagram.

EmployeeClass name address enter timecard info() employee details() commissioned empl purchase order() choose payment method()

acme location windows based desktop payroll adminstration() employee() database maintains()

Payroll administrator name location maintains employee info() adding, deleting, changing empl info() payment classification() automatic generation of payment() paycheck providence() report delivery()

SEQUENCE DIAGRAM: Sequence diagram includes various entities interacting with each other. Each interaction is aided by a solid arrow head. The corresponding reply/response is given by dotted arrow lines. The life time of each object is represented by a vertical dotted line.

: EmployeeClass login

DATABASE

SYSTEM TESTING

BANK

PRINTER

SYSTEM

enter employeer details

timecard maintanence updation automatically generated sending time info

printing time time report

comission empl-purchase order

flat salary emp-purchase order provide details printing details

COLLABORATION DIARAM: We can automatically generate the collaboration diagram with the help of the function key F5. It represents the entity interaction as more generalized information.
: EmployeeClass BANK

PRINTER 5: sending time info 8: comission empl-purchase order 1: login 2: enter employeer details 3: timecard maintanence 9: flat salary emp-purchase order 6: printing time

SYSTEM TESTING 11: printing details 7: time report

4: updation automatically generated

DATABAS E 10: provide details

SYSTEM

ACTIVITY DIAGRAM: An activity diagram illustrates the various points as an individual state or an activity in which each state is represented by a rounded rectangle. Starting point is signaled by start symbol and ended by a rounded solid circle. The flow between them is represented by means of arrow heads. All activities are represented by a rounded rectangle and states are represented by an elliptical rectangle. Login activity diagram:

start

enter username and password

if username and password are correct yes no

login to proceed

incorrect, not allowed

Method of payment:

start

employee payment

choosing method

mart to postal address

pick up paycheck

Purchase order:
start

purchase order submission

comission rate calculation

end

Timecard activity

start

employee time card information calculating time and payment on every friday employee work by hour employee works more than 8 hrs

record date number of hrs worked

record the datre no of hours worked payment 1.5 times than normal rate

payment for worked hours

10

COMPONENT DIAGRAM: In the component diagram all the individual components are described as individual interacting components. Each component is correlated to its corresponding classes, in order to generate the code for each component.

Acme system

pay roll employe e details

time card

commissioned employee

11

DEPLOYMENT DIAGRAM: In a deployment diagram the processor system is represented by a shaded cuboids and other systems are linked to the processor system are represented by a normal cuboids. Deployment is the process of assembling the system as an application that is to be installed and assembled.

Acme system

System monitor

Databas e

12

RESULT: Thus various phases of software development lifecycle is implemented for the payroll system using the rational software.

13