Overview

Pet Boarding and Grooming (Pet BAG) is a company that provides boarding and grooming services for dogs and cats. They want to modernize their operations by introducing custom software that will help replace inefficient paper-based processes.

UML Class Diagram Work on the Pet BAG application has already begun.

Use this UML Class diagram, prepared by your supervisor, to understand the relationships between the Pet, Dog, and Cat classes.

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

• Ability to check-in pets 

• Ability to check out pets

 

Pet Check 

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

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

• There are 30 spaces for dogs and 12 for cats. Pet BAG will need to 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 space.

 

Pet Check Out 

The method for the pet check out process should meet the following criteria: 

• Identify the pet and its boarding space. 

• Determine if the pet had a grooming fee. Only dogs can be groomed and only if they stay two or more days. 

• Use the following table to calculate the total fees. 

• Mark the boarding space as vacant.

 

 Write pseudocode that outlines a plan for the method you chose (Check-In / Check out) and aligns to the specifications. Start by breaking down the description of your chosen method into a series of ordered steps. As you write and review each step, consider the following:
What input does the computer need to complete the task? Be sure to prompt the user for the appropriate input.
What output should the computer display to the user?
When might you need to use decision branching and use a different set of steps depending on the user input? If you used decision branching, did you account for all possible input values?
Reminder: You do not need to write pseudocode for both methods.
 

Based on the pseudocode you wrote, create a flowchart for the method you selected. Remember, you do not need to create a flowchart for both methods. Your flowchart will help your team communicate to your client how you are planning to develop the software. 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 you selected.
Note: You can find the correct shapes to create your flowchart on the Insert menu in Microsoft Word. You may also draw your flowchart by hand, take a clear picture, and insert the picture into your Word document. Use the add shapes or insert pictures tutorials to help you. You could also use a flowcharting tool that you are familiar with, such as Lucidchart if you prefer.

-dogSpaceNumber -dogWeight -grooming +Dogo + getGrooming() + setGrooming Dog + getDogWeight() + setDogWeight() + getDogSpaceNumber() + setDogSpaceNumber -petType -petName Pet -petAge -dogSpaces -catSpaces -daysStay - amountDue + Pet() + getPetType() + setPetType() + getPetName() + setPetName() + getPetAge)) + setPetAge() + getDogSpaces() + setDogSpaces() + getCatSpaces() + setCatSpaces() + getDaysStay() + setDaysStay() + getAmountDue() + setAmount Due() Cat -catSpaceNumber + Cat + getCatSpaceNumber() + setCatSpaceNumber()