QAC020C152A Object Oriented Programming Assignment - University of Roehampton London, UK

Learning outcomes assessed within this piece of work as agreed at the programme level meeting On successful completion of this module students will be able to:

1. Gain knowledge and understanding of OOP concepts and principles and be able to evaluate and interpret within the context.

2. Demonstrate comprehensive analytical knowledge of design and implementation of object oriented programmes, taking quality and reusability into account using API's or object repositories.

3. Employ a structural approach to test OOP based systems, using a test plan, monitoring expected and actual results.

4. Evaluate and collect information from a variety of authoritative sources to inform a choice of solutions to standard problems; advance the knowledge of OOP; and become familiar with a variety of research methods such as qualitative and quantitative.

Assignment Scenario -

Your assessment consists of two pieces of coursework: Coursework 1 consists of report on your knowledge and understanding with software project, which assesses learning outcomes 1 and 2 and weight an overall 60%. Coursework 2 is an individual report, which assesses learning outcome 3 and 4 and weight overall 40%.

Requirements - You have recently begun a position in Dexter Software Ltd as a Junior Programmer, and have joined a small development team to 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

a. Salaried Employees

b. Hourly Employees

c. Commission Employees

2. View Employee

a. All Employees

b. Salaried Employees

c. Hourly Employees

d. Commission Employee

3. Remove Employee

4. Generate Pay slips

a. Salaried Employee

b. Hourly Employee

c. Commission Employee

5. Exit

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.

Coursework 1 Tasks - (Word Count 1000-1500 words)

Deliverables -

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).

Coursework 2 Tasks -

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.

Attachment:- Object Oriented Programming Assignment Files.rar