Simple holiday tracking system

Employees in a company have a given number of days holiday allowance, which is specified in the employment contract. To book some days off, an employee makes a request, which the manager responsible will either grant or decline. If the request is granted then the details are recorded. In a small company with a few employees, the holidays may be tracked using a planner. However, as the number of employees grows keeping track becomes more difficult. Sometimes there are further considerations to take into account such as having sufficient cover in critical departments. This project is to develop a computerized booking system. Initially, the user of the system will be the manager in charge of holidays. Later versions may provide a web interface for employees to view their holiday status and to submit their requests. The functional requirements of the system are as follows: · To store employees' annual holiday allowances · Provide a suitable user-interface to allow a manager ger to enter a holiday request for an employee · To carry out validation checks (e.g. sufficient days days allowance remain to meet the request) · Cancel a holiday request · Report the holiday status of an employee · Generate a report of employees on holiday for a specified period · Reset the system at the start of the year. ## Deliverables Prototype 1 - Basic model classes. [login to view URL] and implement a Employee Holiday Record class. Each record should have an employee ID, maximum number of days holiday allowance, and a field to record the number of days holiday taken (or remaining). In addition to set and get methods, there should be methods to deal with the holiday count. In this prototype ignore actual dates,, just deal with the number of days of holiday. Create some instances of the Employee Holiday Record class, and test all the methods thoroughly. Create a test plan and record the outcomes. Print copies of the holiday class, test programs and results. Create a HolidayPlanner class to hold a collection holiday records for a company. The class should include methods to add, remove, and find an employee's holiday record. Populate this class with a set of holiday records, and test all its methods. Print copies of the HolidayPlanner class, test programs and results. Write a short summary (800 words) about this prototype: what it has achieved and its limitations. Prototype 2 - GUI to collect holiday request data Design and implement user interface to display a employee's record and to enter the data for a holiday request. The GUI should be a 'Form' with fields to enter an employee ID and the number of days holiday requested. A buttons panel may hold buttons to action events such as 'Find', 'Submit', 'Clear'. You may also consider creating a menu bar with some potential menu items, e.g. open, save, print data files. Correctness and validation of the data is not a primary concern in this prototype. The requirement is that a form can be displayed, data can be entered, and eventually used to update an employees holiday record. Obtain print out(s) of your GUI and label the containers and components used to construct it. Prototype 3 - Integration of GUI and Model classes This stage links the classes in prototype 1 and the Form in prototype 2. Implement the actions corresponding to the events generated by the user. For example, when a holiday request is submitted, the data from the Form should be used to update the holiday record for the employee. A message should be displayed to confirm that the holiday request has been granted or not. The purpose of the prototype is to ensure that actions will take place corresponding to the user's inputs. Validation of the data should take place. e.g. that the data has been entered correctly, and that the employee has sufficient days allowance to satisfy the holiday request. Below is the dialogue for a successful request. Use Case: Successful Holiday Request User: 1. Enter Employee Id System Response: 2. Look up employee and display details User: 3. Submit holiday request details System response: 4. Validate request 5. Update Employee record 6. Display confirmation message Produce other use case dialogues showing the cases when the request fails. Draw up a test plan and test your system thoroughly, including all validation possibilities and error paths. Show a printout of the employee records before and after to show that updates have occurred as expected (or not as the case may be). ## Platform The use case model ( class diagrams ) are to be drawn using Rational rose software. All coding should be in java [login to view URL] project should use a spiral development ( prototype) [login to view URL] OS used will be windows XP.