Scribd
Upload
2K views2 pages

Payroll System Requirements Overview

Here are the key actors and use cases identified for the payroll system: Actors: - Employee - Payroll Administrator Use Cases: - Enter Timecard Information - View Paystub/Reports - Change Payment Preferences - Add/Remove Employees - Run Payroll - Maintain Employee Records Relationships: - Employee can enter timecard information - Employee can view paystubs and reports - Employee can change payment preferences - Payroll Administrator can add/remove employees - Payroll Administrator can maintain employee records - Payroll system runs payroll Use Case Diagram: [DIAGRAM OF PAYROLL SYSTEM USE CASES] The

Uploaded by

Nikhil Satav
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
2K views2 pages

Payroll System Requirements Overview

Here are the key actors and use cases identified for the payroll system: Actors: - Employee - Payroll Administrator Use Cases: - Enter Timecard Information - View Paystub/Reports - Change Payment Preferences - Add/Remove Employees - Run Payroll - Maintain Employee Records Relationships: - Employee can enter timecard information - Employee can view paystubs and reports - Employee can change payment preferences - Payroll Administrator can add/remove employees - Payroll Administrator can maintain employee records - Payroll system runs payroll Use Case Diagram: [DIAGRAM OF PAYROLL SYSTEM USE CASES] The

Uploaded by

Nikhil Satav
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
  • Payroll System Case Study

Payroll System Case Study

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 hopelessly out of date. Acme needs a new system to allow
employees to record time card information electronically and automatically generate paychecks 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 timecard information, enter purchase orders, change employee preferences (such as
payment method), and create various reports. The system will run on individual employee desktops
throughout 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 (Acme currently has around 5,000
employees world-wide). The system must pay each employee the correct amount, on time, by the
method that they specify (see possible payment methods described later). Acme, for cost reasons, does
not want to replace one of their legacy databases, the Project Management Database, which contains all
information regarding projects and charge numbers. The new system must work with the existing Project
Management Database, which is a DB2 database 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 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 8
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 sale. The commission rate is determined for each
employee, and is one of 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 paychecks 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 paychecks up at the office.

The Payroll Administrator maintains employee information. The Payroll Administrator is responsible for
adding new employees, deleting 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.
task:
Identify Actors, Use cases, relationships, draw use case diagram,

Identify scenario and write for all use cases.

Common questions

Powered by AI

Overtime pay is calculated at 1.5 times the normal hourly rate for hours worked beyond eight in a day. The system automatically computes this based on timecard entries, ensuring employees are compensated accurately on each payroll cycle .

The payroll system must access the DB2 Project Management Database without making updates, as the legacy system is not to be replaced. It should retrieve necessary charge numbers for timecards and ensure compatibility with the mainframe hosting the database . This requires careful integration planning to ensure seamless data retrieval and proper use of charge numbers for billing .

The system maintains data integrity and security by allowing employees to access and edit only their own timecards and purchase orders, preventing unauthorized access to sensitive data. All access is restricted to ensure employees cannot view or alter other employees' records . Additionally, it interfaces with the existing Project Management Database for charge numbers without modifying it, ensuring that external data remains consistent .

Employee self-service features, such as the ability to query hours worked, project billing totals, total pay, and remaining vacation time, empower employees to manage their own payroll information. This reduces administrative burden and errors by allowing direct employee interaction with the system for accuracy in timesheets and purchase orders .

Hourly employees are paid every Friday, with overtime given at 1.5 times the normal rate. Salaried employees are paid at the end of the month and can include commissions based on sales. Employees may choose payment via mailing, direct deposit, or in-person pickup .

The Payroll Administrator is responsible for maintaining employee information, including adding and deleting employees and updating details such as names, addresses, and payment classifications. They also run administrative reports to ensure payroll operations are conducted smoothly and accurately .

The new payroll system for Acme, Inc. must include the functionality for employees to electronically record time card information and automatically generate paychecks based on hourly work and sales commissions. It should have a Windows-based desktop interface for entering timecard information, purchase orders, changing payment preferences, and generating reports. It must ensure data security by allowing employees access only to their own information. The system retains all employee information and interfaces with the existing Project Management Database without updating it. Employees are paid based on set schedules, with hourly employees paid weekly and salaried employees paid monthly .

The system provides robust reporting capabilities, enabling employees to track hours worked, project billing totals, year-to-date pay, and vacation time. This empowers employees with transparency and fosters accountability, enhancing performance tracking and planning .

Key challenges include ensuring real-time accuracy in data entry, especially for timecards and purchase orders that directly affect payroll calculations. Integration with the existing database poses a risk if any system changes disrupt data flows. The system also needs robust error handling and verification processes to address discrepancies promptly. Lack of manual oversight requires stringent security protocols to prevent unauthorized data access .

Potential enhancements include mobile access for remote timecard submissions, advanced analytics for workforce planning, customization of reporting templates, and integration with human resources systems for seamless data transfer. Enhanced user interfaces with intuitive dashboards could improve user experience and reduce training time .

Payroll System Case Study As the head of Information Technology at Acme, Inc., you are tasked with building a new payroll sys
task: Identify Actors, Use cases, relationships, draw use case diagram, Identify scenario and write for all use cases.

You might also like