Skip to content

An Implementation of a Payroll Application for comparison and show of good design

Notifications You must be signed in to change notification settings

shivu2507/payroll-in-python

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

4 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Use Cases:
  1. Add a new employee
  2. Delete an employee
  3. Post a time card
  4. Post a sales receipt
  5. Post a union service charge
  6. Change employee details
  7. Run the payroll for today

Use Case 1: Add new Employee

A new employee is added by the receipt of an AddEmp Transaction. This
Transaction contains the employee's name, address, and assigned
employee number. The transaction has three forms:

1. AddEmp <EmpID> "<name>" "<address>" H <hrly-rate>
2. AddEmp <EmpID> "<name>" "<address>" S <mtly-slry>
3. AddEmp <EmpID> "<name>" "<address>" C <mtly-slry> <com-rate>

The employee record is created with its fields assigned appropriately.

Alternative 1: An error in the transaction structure

If the transaction structure is inappropriate, it is printed out in an
error message, and no action is taken


Use Case 2: Deleting an Employee

Employees are deleted when a DelEmp transaction is received. The form
of this transaction is as follows:

DelEmp <EmpID>

When this transaction is received, trhe appropriate employee record is deleted.

Alternative 1: Invalid or unknown EmpID

If the <EmpID> field is not structured correctly or does not refer to
a valid employee record, the transaction is pinted with an error
message, and no other action is taken.


Use Case 3: Post a Time Card

On receipt of a TimeCard transaction, the system will create a time
card record an associate it with the appropriate employee record.

TimeCard <EmpID> <date> <hours>

Alternative 1: The selected employee is not hourly

The system will print an appropriate error message and take no further action.

Alternative 2: An error in the transaction structure

The system will print an appropriate error message and take no further action.


Use Case 4: Post a Sales Receipt

On receipt of the SalesReceipt Transaction, the system will create a
new salesreceipt record and associate it with the appropriate
commissioned employee.

SalesReceipt <EmpID> <date> <amount>

Alternative 1: The selected employee not commissioned

The system will print an appropriate error message and take no further action.

Alternative 2: An error in the transaction structure

The system will print an appropriate error message and take no further action.


Use Case 5: Post a Union Service Charge

On receipt of this transaction, the system will create a
service-charge record and associate it with the appropriate union
member.

ServiceCharge <memberID> <amount>

Alternative 1: Poorly formed transaction

If the transaction is not well formed or if the <memberID> does not
refer to an existing union member, the transaction is printed with an
appropriate error message.


Use Case 6: Changing Employee Details

Upon receipt of this transaction, the system will alter one of the
details of the appropriate employee record. There are several possible
variations to this transaction.

ChgEmp <EmpID> Name <name>                      Change employee name
ChgEmp <EmpID> Address <address>                Change employee address
ChgEmp <EmpID> Hourly <hourly-rate>             Change to hourly
ChgEmp <EmpID> Salaried <salary>                Change to salaried
ChgEmp <EmpID> Commissioned <salary> <rate>     Change to commissioned
ChgEmp <EmpID> Hold                             Hold paycheck
ChgEmp <EmpID> Direct <bank> <account>          Direct Deposit
ChgEmp <EmpID> Mail <address>                   Mail paycheck
ChgEmp <EmpID> Member <memberID> Dues <rate>    Put employee in union
ChgEmp <EmpID> NoMember                         Cut employee from union

Alternative 1: Transaction errors

If the structure of the transaction is improper, <EmpID> does not
refer to a real employee, or <memberID> alreday refers to a member,
the system will print a suitable error and take no further action.


Use Case 7: Run the Payroll for today

On receipt of the payday transaction, the system finds all those
employees that should be paid on the specified date. The system then
determines how much they are owed and pays them according to ther
selected payment method. An audit-trail report is printed showing the
action taken for each employee.

Payday <date>

About

An Implementation of a Payroll Application for comparison and show of good design

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • Python 100.0%