IT 145 Global Rain Summary Report Template
Developer: [Insert your name here.]
Date: [Insert the date here.]
IT 145 Global Rain Summary Report Template
Directions
Place your pseudocode, flowchart, and explanation in the following sections. Before you submit your report, remove all
acketed text.
Pseudocode
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.
Write pseudocode that lays out a plan for the method you chose, ensuring that you organize each step in a logical manner. Remember, you will not be creating the actual code for the method. You do not have to write pseudocode for both methods. Your pseudocode must not exceed one page.
[Type or copy your pseudocode here.]
Flowchart
Based on the pseudocode you wrote, create a flowchart using a tool of your choice for the method you selected. In your flowchart, be sure to include start and end points and appropriate decision
anching, and align the flowchart to the check in or check out process. Your flowchart must be confined to one page.
[Insert your flowchart image here. Refer to the Project One Supporting Materials for tool options to create your flowchart and support for copying images into this template.]
OOP Principles Explanation
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.
[Type your explanation here.]
2
IT 145 Pet BAG Specification Document
IT 145 Pet BAG Specification Document
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
eplace 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.
1
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 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.
Type of Pet Daily Boarding Fee Grooming Fee
Dog (greater than or equal to 30 lbs.) $34.00 $29.95
Dog (20–30 lbs.) $29.00 $24.95
Dog (fewer than 20 lbs.) $24.00 $19.95
Cat $18.00 N/A
2
IT 145 Pet BAG Specification Document
Overview
UML Class Diagram
Functionality
Pet Check In
Pet Check Out