Question

Your supervisor has given you a specification document which details Pet BAG’s software needs and includes a UML Class diagram. Using these documents, you will create both a Java class and a summary report. Your summary report will include pseudocode and a flowchart for one method (pet check in or pet check out), and an explanation of how your work meets object-oriented principles. Pet.java Class File. Before you begin, it is important to understand what your client needs the software to do, and what work has already been done by your team. Review the Pet BAG Specification Document, located in the Supporting Materials section, which includes a UML Class diagram. Pay close attention to the class hierarchy, attributes, and behaviors. To begin, open the Virtual Lab by clicking on the link in the Virtual Lab Access module. Then open your integrated development environment (IDE) and create the Pet class based on the specifications in the UML Class diagram. The Pet class must include the following: All attributes with appropriate data structures. Note that the types are not specified in this UML class diagram. You will need to think about what the most appropriate data type is for each attribute. At least one constructor method. You may use a default constructor. To score "exemplary" on this criterion, your constructor must initialize values for the petType, petName, petAge, and daysStay attributes. Accessors and mutators for all attributes Global Rain Summary Report. When you are done implementing the Pet class, refer back to the Pet BAG Specification Document and select either the pet check in or check out method. These methods are detailed in the Functionality section of the specification document. Open the summary report template, located in the What to Submit section. In the template, write pseudocode that lays out a plan for the method you chose. Ensure that you organize each step in a logical manner and that your method meets the specifications in the document for either the check in or check out process. Your pseudocode must not exceed one page. Based on the pseudocode you wrote, create a flowchart using a tool of your choice for the method you selected. Your flowchart will help your team communicate how you are planning to develop the software for your client. Your flowchart must be confined to one page. In your flowchart, be sure to do the following: Include start and end points. Include appropriate decision branching. Align the flowchart to the check in or check out process. Based on your software design and development experience, your supervisor has asked you to articulate your programming approach. This will help ensure clarity, consistency, and efficiency among all developers working on this app. Specifically, you have been asked to briefly explain how you applied object-oriented programming principles and concepts (such as encapsulation, inheritance, and so on) in your software development work thus far. Your explanation should be one paragraph, or four to six sentences.

Answer 1

To create the Java class for the Pet BAG software, review the Pet BAG Specification Document and UML class diagram. Implement the Pet class with attributes, constructors, and accessors/mutators. Create a summary report with pseudocode and a flowchart. Explain how object-oriented programming principles were applied.

Step-by-step explanation:

To create the Java class for the Pet BAG software, you need to review the Pet BAG Specification Document and the UML class diagram. The Pet class should include all the attributes with appropriate data structures, at least one constructor method, and accessors and mutators for all attributes. Once the class is implemented, you can move on to creating a summary report for either the pet check in or check out method. In the report, you should include pseudocode that outlines the plan for the chosen method and a flowchart that visually represents the steps. Finally, you need to explain how you applied object-oriented programming principles and concepts in your software development work, such as encapsulation and inheritance.