Have a Question ?

Home / Answered Questions / Computer Science / develop-a-payroll-system-for-small-manufacturing-company-called-marline-production-ltd-this-company--q-609

(Solved): Develop a Payroll System for small manufacturing company called Marline Production Ltd. This company have 15-20 employees working in different contract types....




Develop a Payroll System for small manufacturing company called Marline Production Ltd. This company have 15-20 employees working in different contract types.

Most of the businesses have three types of employees i.e. Salaried Employees, Commissioned Employees and Hourly Employees. You are required to store basic information for different employees, which include:

  • Employee ID
  • Employee title
  • First name
  • Last name
  • Date of birth
  • National Insurance (NI) Number
  • Job titles (you can fix the job titles e.g. Office worker, Officer, Supervisor, Team leader, Managers, CEO, Director etc. add more if required)
  • Job Department (you can assume departments e.g. Production, Sales, Marketing etc. add more if required)

For salaried employees you need to include additional information related to mode (i.e. Part time or Full time) and their agreed Annual salary. Similarly, for Hourly Employees you will need to store agreed hourly pay rate and finally for Commission Employees their annual gross salary and their Commission rate. Before you could generate payslips, the employee must be registered. For testing purposes the program should auto populate at least three employees (one for each type of employee).

At the end of every month, you will generate and store the monthly payslip for each employee, which will require you to enter employee ID, month followed by relevant parameters, for example for hourly employee you will input number of hours and for commission employees you will input sales amount to calculate their commission. For salaried employees no input is required. You should only record the calculation of their monthly amount for salary based on their annual salary. Finally, your programme should be able to display the pay slip for any selected employee for any selected previous month only.

Your programme should have the following menu and sub menus.

  1. Register Employee
    1. Salaried Employees
    2. Hourly Employees
    3. Commission Employees
  2. View Employee
    1. All Employees
    2. Salaried Employees
    3. Hourly Employees
    4. Commission Employee
  3. Remove Employee
  4. Generate Pay slips
    1. Salaried Employee
    2. Hourly Employee
    3. Commission Employee
  5. Exit


A sample menu is provided below, however you can use your own imagination to present your screens.

The user interface will be menu driven prompting the user to select a choices. The menu items listed by numbers (in the above menu) will appear as your main menu and the items listed by alphabets will be your sub menus.

Depending on the option selected from the main menu, sub menus should branch out offering the user different options e.g. if option 1 from the main menu is selected, a sub menu should appear offering the user the choice to select type of employees to register.


What the system should be able to do:

The system should follow the sequence of evets and notify the use if wrong options is selected, for example, you cannot display employee if the employee is not registered. The first step will be to record employee’s information.

Special Notes:

  • One employees with same name cannot be registered in two different contract type, e.g. salaried and commission.


  • A list of at least 3 employees’ objects (one for each type of employee) can be pre populated for program testing and demonstration screen grabs.


On-screen reporting

Appropriate menus and submenus based on the option selected.




  1. A report on knowledge and understanding of OOP concepts and principles. To begin with, you must explain the ethos of Object Oriented concept.  Further, you need to justify the use of object-oriented concepts such as inheritance, abstraction, and polymorphism. Support your answer with the help of examples.
  2. Design documentation: Produce a class diagram for the above given scenario using Class, abstraction, inheritance, enum diagrams, or description templates. This diagram should include all possible methods and attributes you are planning to use in your program. Your diagram should accompany with brief description of use of type of relationship between classes.
  3. Development: Using your design solution develop only three menu options (i.e. Register Employee, View Employee and Exit option) using the given scenario with the respected submenus.
  4. Include Screen shots of the application performing tasks explain the operations (Hint: like a mini user guide).




Object Oriented Concepts

Explenation of Object Oriented Concepts including examples? Justification the use of object oriented concepts such as inheritance, abstraction, polymorphism etc. What are they?

Design documentation

Have you provided class/interface/enum description template detailing the role the class performs in the project?

The full source code for the chosen solution as an appendix in your report.

Your program executes successfully, produces the correct results and displays them in the correct order. It also meets all of the specifications in the requirements.

  • Register Employee
  • View Employee
  • Remove Employee
  • Generate Pay slips
  • Sub-menus 
  • Use of OOP’s Principles


Have you commented the code properly? Have you used meaningful names for your classes, variables and methods?


Is the code efficient without sacrificing readability and understanding? Is it well refactored without duplication of code?


Have you included error checks? Have you included exceptions? Have you made sure that the programme executes successfully?

Screen shots of the program

Provide a comprehensive set of screen grabs of the application performing different tasks? (Registering all three types of employees, also viewing and deleting them etc.). Note do not include source code screen shoots











  1. Cover sheet completed


  1. Table of contents


  1. Section on Object Oriented Concepts with examples.


  1. Section on Design Document


  1. The full source code attached in appendix.


  1. Appropriate Screen shots of the program provided.


  1. In-text citations correctly written


  1. Reference list on a separate page, completed and in the correct format



  • \Please note file size limitation might apply. You report must be under 100MB.
  • The full source code package should be zipped and attached to your word document report submission in the appendix.





Part 2

For this coursework, you are also required to complete the following (Word Count 1000-1500 words).

  1. Create Test plan to test functionality and ensure it meets requirements. A test table listing any one of the main functional requirements (e.g. register employee), inputs and expected outputs, and if your program produces the desired output when tested. Also, support your testing with an example of screen shots from your code.  
  2. Critically evaluate your program, write a report that assesses your solution, the approach taken, and your thoughts about using Java for object-oriented programming. Give examples, code samples and screen shots to back-up your comments.
  3. Meeting the Design Criteria:  you need to explain on how you meet the design criteria and reflection of your approach used to develop. In addition, you should suggest how you could have made this application better if you design it again.


Marking Criteria for Coursework 2:



Test Evidence

Test Table? Is there evidence that full and comprehensive testing of any one function been completed, with examples of code screen shoots.

Critical Review Report

You need to provide a critically review report, starting with the discussion on which Object Oriented (OO) Concepts and principles you have used in your program? Why did you choose the OO concepts or not, why do you think your approach is better or worse? Looking back at the project do you think you made the right choices regarding the object-orientated concepts you used. Would you use the same ones again in a similar project and if so why, why not? You can support your answer with example of screenshot of your code.

Meeting the design criteria

Did you meet all of the design criteria and did your approach work? With the benefit of your experience, would you have developed the application in any other way?  If so how and why?


Your commentary should show evidence of your reading and research and use the Harvard referencing system. Your report is a chance to assess what you have down and to revisit key design and technical decisions you made.  Based on your experience were these the right decisions or would you do anything differently?



Coursework 1 Checklist



  1. Cover sheet completed


  1. Table of contents


  1. Full and comprehensive Test table.


  1. Critical Review Report


  1. Meeting the design criteria


  1. In-text citations correctly written


  1. Reference list on a separate page, completed and in the correct format



We have an Answer from Expert View Expert Answer

Expert Answer

we are working on this answer and it will be ready in less than 2 days from now... please be patient.

Price for your unique answer is $100 

For any queries please live chat with us

OR contact our support: support@answerswave.com

We have an Answer from Expert
Buy This Answer $15

-- OR --

Subscribe To View Unlimited Answers
Subscribe $20 / Month