For your development project, you will imagine you are in charge of managing a zoo’s computer infrastructure. There are many aspects of a zoo that need to be in place to keep it running. One of those aspects are monitoring animal activities in exhibits. This option requires at least two classes and for the design to be broken into multiple methods.
This project represents an authentic demonstration of competency because it involves application of real-world Java programming.
In this assignment, you will demonstrate your mastery of the following course outcomes:
Implement appropriate variables, operators, methods, and classes as they are used in object-oriented programming for developing successful programs
Utilize appropriate syntax and conventions in terms of their best practice and use in programming
Debug coding errors by testing existing code, identifying errors, and correcting errors for improved functionality
Assemble basic, working programs that effectively integrate essential elements of object-oriented programming
As a zookeeper, it is important to know the activities of the animals in your care and to monitor their living habitats. Create a monitoring system that does all of the following:
Asks a user if they want to monitor an animal, monitor a habitat, or exit
Displays a list of animal/habitat options (based on the previous selection) as read from either the animals or habitats file
o Asks the user to enter one of the options
Displays the monitoring information by finding the appropriate section in the file
Separates sections by the category and selection (such as “Animal – Lion” or “Habitat – Penguin”)
Uses a dialog box to alert the zookeeper if the monitor detects something out of the normal range (These will be denoted in the files by a new line starting with *****. Do not display the asterisks in the dialog.)
Allows a user to return to the original options
Specifically, the following critical elements must be addressed:
I. Process Documentation: Create process documentation to accompany your program that addresses all of the following elements:
A. Problem Statement/Scenario: Identify the program you plan to develop and analyze the scenario to determine necessary consideration for building your program.
B. Overall Process: Provide a short narrative that shows your progression from problem statement to breakdown to implementation strategies. In other words, describe the process you took to work from problem statement (your starting point) to the final product. Your process description should align to your end resulting program and include sufficient detail to show the step-by-step progress from your problem statement analysis.
C. Pseudocode: Break down the problem statement into programming terms through creation of pseudocode. The pseudocode should demonstrate your breakdown of the program from the problem statement into programming terms. Explain whether the pseudocode differs from the submitted program and document any differences and the reason for changes.
D. Methods and Classes: Your pseudocode reflects distinct methods and classes that will be called within the final program. If the pseudocode differs from the submitted program, document the differences and reason for changes.
E. Error Documentation: Accurately document major errors that you encountered while developing your program.
F. Solution Documentation: Document how you solved the errors and what you learned from them.
II. Program: Your working program should include all of the specified requirements. The comments within your program will count toward the assessment of the documentation aspects of your submission.
1. Input/Output: Your program reads input from the user and uses system output.
2. Control Structures: Your program utilizes appropriate control structures for program logic.
3. Libraries: Your program utilizes standard libraries to pull in predefined functionality.
4. Classes Breakdown: Your program is broken down into at least two appropriate classes.
5. Methods: Your program utilizes all included methods correctly within the classes.
6. Error Free: Your program has been debugged to minimize errors in the final product. (Your program will be run to determine functionality.)
B. Best Practices: These best practices should be evident within your working program and process documentation.
1. Formatting Best Practices: Provide program code that is easy to read and follows formatting best practices as defined by the industry, such as with indentation.
2. Documentation Best Practices: Include comments where needed within the program in appropriate detail for communicating purpose, function, and necessary information to other information technology (IT) professionals.
3. Coding Best Practices: Ensure your program supports clean code through descriptive variable names.
Guidelines for Submission: Your process documentation should be approximately 2 to 4 pages double-spaced and in 12-point Times New Roman font. Any resource citations should adhere to the most current guidelines for APA formatting. You will submit the code for your working program in a separate file from your process documentation, though the two will be graded together by your instructor. Submit all files as a ZIP file to Blackboard for grading.