Help with Java Programming  Create a program that simulates a meeting reservation system. This project is broken up into 4 parts. Part 1: Basic requirements: 1. The program shall allow the user to select from the following options: a. Create a new meeting b. Show meetings on the calendar c. Clear all meetings 2. Each meeting has a subject, start day/time and end day/time a. Subject is a short text description of the meeting b. Day is a date that contains month, day, and year c. Meeting times need only deal with hour and minute 3. When the user wants to create a new meeting, the program asks for the subject, start and end day/times for it and adds it to the calendar a. For the basic requirements, meetings are not allowed to overlap. If a meeting the user wants to schedule overlaps with an existing meeting, the program presents an error message showing which meeting the one the user wants to schedule overlaps with 4. When the user wants to show all meetings for the week, the report displays all meetings each day as follows a. Show all meetings in chronological order b. At the end of the report, show a tally of all meetings scheduled in each day and a count of all the meetings that have been scheduled c. When the user wants to clear meetings for the week, all meetings scheduled are deleted Technical requirements: A. You must have at least one array of objects B. Assume the user will enter data correctly with valid start and end day/times Part 2: Additional requirements: 6. The program must support 2 types of meetings a. Standard meetings have attributes already described in part one of these requirements (title, start date/time, and end date/time) b. Urgent meetings are meetings that also have a priority level of either 0 or 1 and have the following rules when scheduling them: i. If the user schedules an urgent meeting level 1 and it overlaps with a standard meeting(s), the program asks the user if they want to remove the standard meeting(s) and if so, the urgent meeting is scheduled and the standard is/are removed ii. If the user schedules an urgent meeting level 0, the same rule applies as well as may take over urgent meetings that are level 1 iii. If the user schedules an urgent meeting that overlaps with another urgent meeting of the same priority level, an error message is displayed following the same rule as described in requirement 3a) 7. Update your meeting report function to also show counts of standard and urgent meetings in a day and in total Part 3: Enhanced requirements 8. Each meeting now also has a numeric ID automatically assigned with each new meeting scheduled. Each meeting instance must be a different ID number 9. Allow the user to delete individual meetings from the calendar. When the user wants to do this, the program asks the user for the ID of the meeting. If the meeting is found from the ID, the program shows the meeting to the user and first asks, “Are you sure you want to remove this?” The meeting is removed if the user confirms deleting it 10. Allow the user to update individual meetings from the calendar. When the user wants to do this, the program asks the user for the ID of the meeting. If the meeting is found from the ID, the program shows the meeting to the user and allows the user to enter new information about the meeting. If the start or end times change, the rules for meetings not overlapping still apply Part 4: Advanced requirements 11. Incorporate usage of days of the week to identify meetings on Mondays, Tuesdays, etc. 12. Generate your own set of reporting capabilities such as (and not limited to): a. Showing meetings for the week b. Meeting metrics such as longest meeting in a day, week, month, or year c. Calculate percentage of time spent in meetings d. Other ideas… 13. Allow for meeting adjustments such that if a new meeting to be scheduled is overlaps with another, then instead of removing the lower priority or standard meeting, ask the user if they want to change the lesser meeting to start or stop such that it no longer overlaps

Help with Java Programming 

Create a program that simulates a meeting reservation system. This project is broken up into 4 parts.

Part 1: Basic requirements:

1. The program shall allow the user to select from the following options:

a. Create a new meeting

b. Show meetings on the calendar

c. Clear all meetings

2. Each meeting has a subject, start day/time and end day/time

a. Subject is a short text description of the meeting

b. Day is a date that contains month, day, and year

c. Meeting times need only deal with hour and minute

3. When the user wants to create a new meeting, the program asks for the subject, start and end day/times for it and adds it to the calendar

a. For the basic requirements, meetings are not allowed to overlap. If a meeting the user wants to schedule overlaps with an existing meeting, the program presents an error message showing which meeting the one the user wants to schedule overlaps with

4. When the user wants to show all meetings for the week, the report displays all meetings each day as follows

a. Show all meetings in chronological order

b. At the end of the report, show a tally of all meetings scheduled in each day and a count of all the meetings that have been scheduled

c. When the user wants to clear meetings for the week, all meetings scheduled are deleted

Technical requirements:

A. You must have at least one array of objects

B. Assume the user will enter data correctly with valid start and end day/times

Part 2: Additional requirements:

6. The program must support 2 types of meetings

a. Standard meetings have attributes already described in part one of these requirements (title, start date/time, and end date/time)

b. Urgent meetings are meetings that also have a priority level of either 0 or 1 and have the following rules when scheduling them:

i. If the user schedules an urgent meeting level 1 and it overlaps with a standard meeting(s), the program asks the user if they want to remove the standard meeting(s) and if so, the urgent meeting is scheduled and the standard is/are removed

ii. If the user schedules an urgent meeting level 0, the same rule applies as well as may take over urgent meetings that are level 1

iii. If the user schedules an urgent meeting that overlaps with another urgent meeting of the same priority level, an error message is displayed following the same rule as described in requirement 3a)

7. Update your meeting report function to also show counts of standard and urgent meetings in a day and in total

Part 3: Enhanced requirements

8. Each meeting now also has a numeric ID automatically assigned with each new meeting scheduled. Each meeting instance must be a different ID number

9. Allow the user to delete individual meetings from the calendar. When the user wants to do this, the program asks the user for the ID of the meeting. If the meeting is found from the ID, the program shows the meeting to the user and first asks, “Are you sure you want to remove this?” The meeting is removed if the user confirms deleting it

10. Allow the user to update individual meetings from the calendar. When the user wants to do this, the program asks the user for the ID of the meeting. If the meeting is found from the ID, the program shows the meeting to the user and allows the user to enter new information about the meeting. If the start or end times change, the rules for meetings not overlapping still apply

Part 4: Advanced requirements

11. Incorporate usage of days of the week to identify meetings on Mondays, Tuesdays, etc.

12. Generate your own set of reporting capabilities such as (and not limited to):

a. Showing meetings for the week

b. Meeting metrics such as longest meeting in a day, week, month, or year

c. Calculate percentage of time spent in meetings

d. Other ideas…

13. Allow for meeting adjustments such that if a new meeting to be scheduled is overlaps with another, then instead of removing the lower priority or standard meeting, ask the user if they want to change the lesser meeting to start or stop such that it no longer overlaps