Reference no: EM133516216
Assignment - Federation Car Rental (FedCR)
Overview
You are required to design and develop a small Java console application. Completion of this assignment requires an understanding of:
• Analysis and design techniques, including development of use cases and UML diagrams - specifically, use case diagrams, class diagrams and sequence diagrams
• Object-oriented programming, focusing on polymorphism and the use of interfaces
Learning Outcome 1: Understand the significance of detailed project planning and control, good communication and documentation and the use of appropriate tools in order to provide a quality product
Learning Outcome 2: Understand the distinction between software engineering and programming, and thus the distinction between a software configuration and a program
Learning Outcome 3: Understand the methods and techniques involved in designing, implementing and maintaining an information system, in particular using an object-oriented approach
Learning Outcome 4: Demonstrate skills in designing and implementing an information system
Assessment Details
FedCR is a car hire company that offers vehicle rentals to its clients. Clients are able to hire vehicles according to availability and preference. FedCR offers 10% loyalty discount on the rental fees to members of its loyalty club. No discount is offered to standard clients who are not members of the loyalty club. A special discount of 20%, is offered to clients who are also employees of the company.
You have been hired to design and develop a Java application for FedCR employees to manage the car rental system. The application should have an interactive menu, allowing the user to select the type of client (standard, loyalty member or staff member) making the booking and determine and track the appropriate discounts.
The menu should also provide different other options, such as displaying clients list, generating a report to display the current payments received, and quitting the execution. In the report, the payments should be broken down into different categories of bookings such as standard, loyalty and staff, and the total discounts given in each category (using the discounted values where appropriate). At this stage, there is no need for data to persist once the program finishes execution.
FedCR wants the system to be flexible so that users can include additional functionality at a later date without having to rewrite the entire program. This means you will need to use an interface for processing payments, and polymorphism for the various payment classes, so that new, different payment types may be added at a later date with minimal updates to the code.
FedCR asked that you provide it with some documentation before you commence coding so that the manager is able to verify that the program you intend to code will address the business requirements. The manager would like to see use cases that summarizes the requirements in written format, as well as use case diagrams, class diagrams and sequence diagrams.
Start-up code (A1_BaseCode.zip) is provided for your convenience. You are free to use, update and build your program on this. A sample expected output of an execution of a complete program is also attached. Notice in the sample output clients 1, 2, and 3 are hard coded in the program; clients 4, 5, and 6 are entered at execution. Similarly, your program should include hard coded clients, at least one client in each category.
• With descriptions of each diagram. The description should include:
o a clear explanation of the diagram in your own words
o any issues and challenges faced in developing the diagram
o how you overcame these challenges
o anything related to the diagram that you feel is important
o A short reflection (approximately 200-300 words) of what you have learned, if anything, on this assignment, particularly relating to requirements design and analysis, UML diagrams and object- oriented programming with interfaces and polymorphism. As an example, if you found that you would change your initial UML diagrams after you had commenced coding, you should explain what these changes would be and explain what you learnt that led to these changes.• Enterprise Architect file(s) containing your UML Diagrams for the Use Case, Class Diagrams and Sequence Diagrams.