Pet.java Class File

$1.$ Before you begin, you must understand what your client needs the software to do and what work your team has already done. Review the Pet BAG Specification Documentation in the Supporting Materials section, which includes a UML class diagram. Think about the realworld objects that you must represent in your code. These objects are your first$-$level blueprints. Pay close attention to the class hierarchy, attributes, and behaviors. Consider how these classes will interact with one another and what information must be passed between them.

$2.$ To begin, open the Virtual Lab by clicking 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 criteria:

A$.$ All attributes with appropriate data structures

i$.$ Note that the types are not specified in this UML class diagram. You must consider the most appropriate data type for each attribute.

B$.$ At least one constructor method

i$.$ 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.

C$.$ Accessors and mutators for all attributes

Note: You are only being asked to create one class. Though the UML diagram shows the Pet class as part of a larger application, you are not required to connect it to other classes or to try and run it as a program for this project. Instead, you are practicing creating a class from a UML class diagram.

Global Rain Summary Report

When you are done implementing the Pet class, refer 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.

A$.$ Make certain you properly comment your code. Commenting code provides human$-$readable explanations of the code's functionality.

The comments make it easier for other developers or even the original coder to understand and maintain the code after some time.

Clear and concise comments provide documentation. Comments offer insights into the logic, purpose, and usage of different sections

of the code. Comments become especially valuable in collaborative projects or when handing over code to other developers.

Comments can also help identify potential issues, edge cases, or important considerations that help communication between

developers. Well$-$documented code accelerates the development process and contributes to overall maintainability, which reduces

the likelihood of errors and makes code more adaptable to changes and improvements.

Open the summary report template in the What to Submit section. In the template, write pseudocode that lays out a plan for your

chosen method. Make certain that you logically organize each step 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. Maintain high$-$level pseudocode. You do not need

to write pseudocode for every line of potential Java code.

A$.$ Remember, you will not create the actual code for the method. You only must write pseudocode for one method.

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 plan to develop the software for your client. Your flowchart must be confined to one page. Make

certain you include the following items in your flowchart:

A$.$ Start and end points

B$.$ Appropriate decision branching

C$.$ Flowchart aligned 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 explanation 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 $($OOP$)$ principles and concepts such as encapsulation and inheritance in your software development work thus far. Your explanation should be one paragraph or four to six sentences.

Functionality

Pet BAG is seeking an application that has the following initial functionality:

$-$ Ability to check in pets

$-$ Ability to check out pets

Each of these functional areas is described in more detail below.

Pet Check$-$In

The method for the pet check$-$in process should meet the following criteria:

$-$ Determine if the pet is a dog or cat and check for boarding space.

$-$ There are $30$ spaces for dogs and $12$ for cats. Pet BAG must be able to adjust these counts as the shop grows.

$-$ If there is space for a new pet, collect the appropriate information. For returning pets, update the information as needed.

$-$ Gather information on the length of the stay.

$-$ Determine if the pet owner would like the pet to be groomed. Only dogs can be groomed and only if they stay two or more days.

$-$ Assign the pet to a s