Listed below are various aspects of the assignment. When you turn in your work, please indicate the status of each item
- YES : indicates that the item is fully complete
- NO : indicates that the item is not attempted
- PART : indicates that the item is attempted but not fully complete
YES 1 pt: All classes, methods, and attributes are named as requested in the assignment specifications
YES 1 pt: The Engine class contains appropriately-encapsulated attributes to store information about its fuel type, capacity, and current level
YES 1 pt: The Engine class has a functional constructor
YES 1 pt: The Engine class has refuel() and go() methods that correctly modify the fuel level
YES 1 pt: The Car class contains appropriately-encapsulated attributes to store information about its capacity and current Passengers
YES 1 pt: The Car class has functional addPassenger(...) and removePassenger(...) methods
YES 1 pt: The Car class has a printManifest() method that prints a nicely-formatted roster of all Passengers currently aboard the car
YES 1 pt: The Passenger class uses appropriate methods from the Car class to implement its boardCar(...) and getOffCar(...) methods
YES 1 pt: The Train class has all expected attributes / relationships with the other classes
YES 1 pt: The Train class has all expected methods, making use of methods from other classes as appropriate
YES 4 pts: Programs compile without errors or warnings
YES 2 pts: Executes fully & consistently without crashing (exception/freeze)
YES 2 pt: Complies with style guidelines (missing items 1 pt each):
_____ Classes & class members all have Javadoc header comments
_____ Clear and consistent indentation of bracketed sections
_____ Adheres to Java conventions on naming & capitalization
_____ Methods & variables all have clear and accurate names
_____ Methods avoid confusing side effects
YES 1 pt: All required files included with submission (including completed rubric.md file)
YES 1 pt: reflection.md contains your reflection on the assignment