https://github.com/joshidivanshu/travelitineray
Design, implement and test a software system that allows travel agencies to maintain their travel packages' itinerary and passengers.
https://github.com/joshidivanshu/travelitineray
java-8 junit5 mockito
Last synced: 4 months ago
JSON representation
Design, implement and test a software system that allows travel agencies to maintain their travel packages' itinerary and passengers.
- Host: GitHub
- URL: https://github.com/joshidivanshu/travelitineray
- Owner: joshidivanshu
- Created: 2023-10-02T07:07:10.000Z (over 1 year ago)
- Default Branch: main
- Last Pushed: 2023-10-02T07:17:33.000Z (over 1 year ago)
- Last Synced: 2024-12-27T04:43:09.719Z (5 months ago)
- Topics: java-8, junit5, mockito
- Language: Java
- Homepage:
- Size: 16.6 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Travel Itinerary
Design, implement and test a software system that allows travel agencies to maintain their travel packages' itinerary and passengers.
---
# Specification
1. Each travel package has a name, a passenger capacity, an itinerary (list of destinations) and a list of it's passenger.
2. Each destination has a name, and a list of the activities available at that destination.
3. Each activity has a name, a description, a cost and a capacity. Each activity is available at one destination only.
4. Each passenger can sign up for zero or more activity at each destination of the travel package.
5. Once an activity has reached it's capacity no more passengers can sign up for it.
6. Each passenger has a name and a passenger number.
7. A passenger can be a standard, gold or premium passenger.
1. A standard passenger has a balance. And each time a standard passenger signs up for an activity the cost is deducted from their balance. They cannot sign up for an activity if they do not have sufficient balance.
2. A gold passenger has a balance. Each time a gold passenger signs up for an activity, a 10% discount is applied on the cost of the activity and the discounted amount is deducted from their balance. They cannot sign up for an activity if they do not have sufficient balance.
3. A premium passenger can sign up for activities for free.
In addition to the above specifications, the classes should provide the following functions:
1. Print itinerary of the travel package including:
1. travel package name,
2. destinations and details of the activities available at each destination, like name, cost, capacity and description.
2. Print the passenger list of the travel package including:
1. package name,
2. passenger capacity,
3. number of passengers currently enrolled and
4. name and number of each passenger
3. Print the details of an individual passenger including their
1. name,
2. passenger number,
3. balance (if applicable),
4. list of each activity they have signed up for, including the destination the at which the activity is taking place and the price the passenger paid for the activity.
4. Print the details of all the activities that still have spaces available, including how many spaces are available.
# Sub-Tasks
The following are the sub-tasks that needs to be done. The code needs to be written using the Java programming language and needs to adhere to the guidelines detailed out in the next section.
1. Higher Level Diagram : A block diagram indicating interaction between different sub-blocks.
2. Lower Level Diagram : A UML class diagram of all the classes that needs to implemented. The classes must be designed with suitable attributes and methods to represent the requirement mentioned above.
3. Implementation : Java programming language should be used for implementation.
4. For every class, unit test cases should be written. Junit framework can be used for unit testing the classes.
💡 ***Note:** You may use https://app.diagrams.net/ for designing the Higher Level Diagram(HLD) and Lower Level Diagram(LLD).*
# Guidelines
The code should adhere to the following guidelines.
1. Each class should follow the [SOLID Design Principles](https://itnext.io/solid-principles-explanation-and-examples-715b975dcad4).
2. [Clean Code Guidelines](https://gist.github.com/wojteklu/73c6914cc446146b8b533c0988cf8d29) should be kept in mind while writing the code (Dependency Injection can be skipped)
3. [Unit Test guidelines](http://www.kyleblaney.com/junit-best-practices) should be followed.
4. [Java code documentation](https://www.tutorialspoint.com/java/java_documentation.htm) needs to be done properly.