Reference no: EM132435148

COMP1690 Component Programming Assignment - Holiday Booking System, University of Greenwich, UK

This assignment consists of two parts: Part A will be completed in a group and  Part B must be completed individually.

Part A -

With the help of the tutor, organise yourselves into groups consisting of 2 students to engage in pair programming.

Implementation - As a team you are required to:

Design/implement a database which meets the requirements of the case-study described above.

You can use any relational database management system you wish (e.g. JavaDB, SQLServer, MySQL, Oracle, Access, etc.). The database should be normalised and use primary key and foreign key constraints.

Create a set of entity/model classes which reflect entities from the database. Feel free to use LINQ or Entity Framework, if you wish.

Implement a desktop application using C#, which offers the following functionality to admin users:

- User log in

- User management enabling an admin user to create/edit/delete employees. It must be possible to allocate an employee to a department and assign him/her a role.

Group report section - The group report section should contain the design documentation that you created as a group, which should contain an Entity Relationship Diagram outlining the database structure and an architecture diagram which shows the overall setup of the system. This should be prepared by the group and each member then includes the same diagrams in their final report (unless you make further modifications during the individual phase of the assessment).

Individual report section - Please include a reflection of your role within the team and discuss lessons learnt. What you think went well and what you think could have been improved and how. This section should be included in the final report.

Part B -

For Part B the teams will be disbanded, and you are expected to work individually.

You can take a copy of the work completed as a group and build on it to complete the remaining implementation. This may involve exporting the database you developed as a team and importing it to your individual database account.

It is envisaged that the system will be developed in three stages, to include basic, intermediate and advanced functionality.

Implementation -

Functionality A -

Extend the functionality implemented as a group to add the following functionality for an admin user:

View a list of outstanding holiday requests.

Accept/reject a request.

View a list of all holiday bookings and filter them by employee.

Select a date and show all employees working that day and those on leave that day.

When a holiday request is accepted or rejected it should be removed from the list of outstanding requests.

Functionality B -

To facilitate the data entry of phone numbers, you should implement a Phone Textbox. Implement a component which inherits from the Textbox control. It should only allow numbers to be entered. Further, it should display the numbers that are entered into it in red if there are more than 11. The Phone Textbox component should be integrated into the application so it is used instead of a normal textbox when entering a phone number for a driver.

It must be possible for an admin user to view a list of drivers and for a particular driver show his/her qualifications and training.

Create a web application using ASP.NET which allows employees to:

- Log in.

- Submit a holiday request.

- View a list of existing holiday requests, which also shows whether they were approved/rejected.

Functionality C -

You should extend the system by including a component which applies constraint checking.

When an employee submits a holiday request, the system should use the component to automatically check whether all constraints are satisfied. The list of outstanding requests shown to the admin user should be split into two, those which don't break any of the constraints and those which do and can't be accepted.

For requests which break constraints, the system should specify which constraint is being broken. There could be more than one, in which case they should all be listed.

Functionality D -

Create a Web Service (SOAP or REST) which exposes functionality for employee log in and make holiday request submissions. This web service will be called from the employee app.

The prototype of the employee app should also be created, as a desktop application (or mobile app) and it must be possible for an employee to log in and to submit a holiday booking request.

The employee app should not connect directly to the database, but all communication must be via the Web Service (remember that the company is planning to replace the desktop application with a mobile app at a later stage).

Functionality E -

Add more functionality to the web application.

Create a prioritisation component which prioritises requests based on the number of days already approved and the number of days requested during the peak times. The prioritisation should determine the order in which outstanding requests are listed.

Implement a component which suggests alternative dates (where possible) for requests which break constraints.

Functionality F -

Create a visualisation component which makes it possible to visually depict a calendar which highlights the days on which an employee has booked leave.

Technical and User Documentation -

Prepare a final report which should contain the design documentation and reflection from Part A as well as the following sections:

Screen shots: Screen shots demonstrating each of the features that you have implemented. Give captions or annotations to explain which features are being demonstrated.

Evaluation (approx. 600 words): An evaluation of the evolution of your application. You should discuss any problems you had during implementation. You should be critical (both positive and negative) of your implementation. Be prepared to suggest alternatives. Discuss how your final implementation could be improved.

Algorithm (approx. 600 words): A complete implementation of the advanced functionality requires you to devise algorithms for predicting the likelihood of an incident. Outline how you implemented this algorithm and wherever possible support your discussion with pseudo code, equations and/or diagrams. If you didn't implement the component or you think your implemented algorithm could be improved, then you can critically discuss how you would have implemented/improved the algorithm.

Acceptance Test -

You must demonstrate your implementation to the company which is represented by your tutor who will sign off the system. Failure to demonstrate will result in a failed assessment. You will be allocated a time slot closer to the submission deadline.

Attachment:- Component Programming Assignment File.rar