i have an assignment that it is almost done but i need you guys to complete it and you will se the requirement in the Project Specification in the document that i will upload. And
i need you guys to focus on oop and do not repeat things in the project. i will upload the project so you can continue working on it. And here is my teacher comment on this that I have done”
Your submission is incomplete as it is missing a class diagram and it was instructed that a class diagram must be included. Therefore, you will have to resubmit your project be the project re-exam deadline. Also, there were too many attributes in many of your classes, and some of the mechanisms (Composition and Inheritance in Employee) were not implemented correctly.“. plus that i need you guys to let me know about the mistakes that i have done in the project.
Epic Feature 6 - Preventing Errors
This epic feature should cover Exception handling in your project. You are expected to use
and handle Exceptions in your code. The Exceptions should be added as part of the special
cases for Epic Feature 5 (Employees). You do not need to change your Epic Features (2--4)
to introduce Exception Handling.
There is a minor handling that you will introduce in Epic Feature 1, because of the menu
connections between Epic Feature 1 and 5 (otherwise, no need to change all your menus to
add Exception Handling).
User Story 6.1 - No employee has been registered.
Throughout Epic Feature 5, there are multiple cases in which we try to print or sort all
registered employees. However, there may be situations in which not a single employee
was registered to the system before trying to access those functionalities.
To handle those cases, you should create and handle an Exception with the following
message: "No employees registered yet."
User Story 6.2 - Specific employee not found or not registered yet.
Throughout Epic Feature 5, there are multiple cases in which an employee may not be found
during the operation (e.g., during removal, printing, etc.). To handle those cases in which a
desired employee ID is not found in our system, you should create and handle an
Exception with the following message: "Employee <ID> was not registered
yet."
User Story 6.3 - Presenting the creation or assignment with invalid Employee data.
Your program should prevent the creation or assignment of Employees with the information
below. You should create Exceptions with the corresponding messages for each case.
● Empty IDs: “ID cannot be blank.”
● Empty employee names: “Name cannot be blank.”
● Gross salaries less than or equal to zero: “Salary must be greater than
zero.”
These cases above should also work for the creation of all types of Employees.
User Story 6.4 - Presenting the creation or assignment with invalid Manager data.
Your program should prevent the creation or assignment of Managers with the information
below. You should create Exceptions with the corresponding messages for each case.
● Invalid degree: “Degree must be one of the options: PhD, MSc or
PhD.”
The case above should also work for the creation of Directors that also require a degree.
User Story 6.5 - Presenting the creation or assignment with invalid Directors data.
Your program should prevent the creation or assignment of Directors with the information
below. You should create Exceptions with the corresponding messages for each case.
● Invalid Department: “Department must be one of the options:
Business, Human Resources or Technical.”
User Story 6.6 - Presenting the creation or assignment with invalid Interns data.
Your program should prevent the creation or assignment of Interns with the information
below. You should create Exceptions with the corresponding messages for each case.
● GPA outside the valid range: “<GPA> outside range. Must be between
0-10."
DescriptionIn this final assignment, the students will demonstrate their ability to apply two ma
Path finding involves finding a path from A to B. Typically we want the path to have certain properties,such as being the shortest or to avoid going t
Develop a program to emulate a purchase transaction at a retail store. Thisprogram will have two classes, a LineItem class and a Transaction class. Th
1 Project 1 Introduction - the SeaPort Project series For this set of projects for the course, we wish to simulate some of the aspects of a number of
1 Project 2 Introduction - the SeaPort Project series For this set of projects for the course, we wish to simulate some of the aspects of a number of