Overview Pseudocode is language agnostic. This means that you can create pseudocode with little to no experience in a specific programming language. Pseudocode helps you plan out your code in a logical manner. Flowcharts are a powerful way to graphically represent logic, decisions, and branching. This activity will help you develop the skills necessary to plan and organize your code, which is an important skill for programmers of all experience levels. In this milestone, you will be working with the same scenario as in Project One. You are part of a development team that has been asked to design and develop custom software for a local pet boarding and grooming business, Pet Boarding and Grooming (Pet BAG). In this milestone, you will work on creating pseudocode and a flowchart for either the pet check in or pet check out method to meet the Pet BAG company’s specifications. Your work in this milestone is one portion of the work you will need to complete for Project One. After you have completed this milestone, make sure to review any instructor feedback you receive so that you can make improvements before your final submission in Project One. Prompt Your supervisor has provided you with the Pet BAG Specification Document. This document reviews Pet BAG’s software needs. Review the pet check in and pet check out methods, which are described in the Functionality section. Then choose one of these methods (check in or check out) to implement. As you read through the descriptions for each method, ask yourself the following: How would I break down these steps in a way that a computer can understand? What information would I need from the user at each point? When would it be a good idea to use decision branching, such as “IF” and “IF ELSE” statements? Next, write pseudocode that outlines a plan for the method you chose 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.

Overview Pseudocode is language agnostic. This means that you can create pseudocode with little to no experience in a specific programming language. Pseudocode helps you plan out your code in a logical manner. Flowcharts are a powerful way to graphically represent logic, decisions, and branching. This activity will help you develop the skills necessary to plan and organize your code, which is an important skill for programmers of all experience levels. In this milestone, you will be working with the same scenario as in Project One. You are part of a development team that has been asked to design and develop custom software for a local pet boarding and grooming business, Pet Boarding and Grooming (Pet BAG). In this milestone, you will work on creating pseudocode and a flowchart for either the pet check in or pet check out method to meet the Pet BAG company’s specifications. Your work in this milestone is one portion of the work you will need to complete for Project One. After you have completed this milestone, make sure to review any instructor feedback you receive so that you can make improvements before your final submission in Project One. Prompt Your supervisor has provided you with the Pet BAG Specification Document. This document reviews Pet BAG’s software needs. Review the pet check in and pet check out methods, which are described in the Functionality section. Then choose one of these methods (check in or check out) to implement. As you read through the descriptions for each method, ask yourself the following: How would I break down these steps in a way that a computer can understand? What information would I need from the user at each point? When would it be a good idea to use decision branching, such as “IF” and “IF ELSE” statements? Next, write pseudocode that outlines a plan for the method you chose 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.

Computer Networking: A Top-Down Approach (7th Edition)

7th Edition

ISBN:9780133594140

Author:James Kurose, Keith Ross

Publisher:James Kurose, Keith Ross

Chapter1: Computer Networks And The Internet

Section: Chapter Questions

Problem R1RQ: What is the difference between a host and an end system? List several different types of end...

See similar textbooks

Overview

Pseudocode is language agnostic. This means that you can create pseudocode with little to no experience in a specific programming language. Pseudocode helps you plan out your code in a logical manner. Flowcharts are a powerful way to graphically represent logic, decisions, and branching. This activity will help you develop the skills necessary to plan and organize your code, which is an important skill for programmers of all experience levels.

In this milestone, you will be working with the same scenario as in Project One. You are part of a development team that has been asked to design and develop custom software for a local pet boarding and grooming business, Pet Boarding and Grooming (Pet BAG). In this milestone, you will work on creating pseudocode and a flowchart for either the pet check in or pet check out method to meet the Pet BAG company’s specifications. Your work in this milestone is one portion of the work you will need to complete for Project One. After you have completed this milestone, make sure to review any instructor feedback you receive so that you can make improvements before your final submission in Project One.

Prompt

Your supervisor has provided you with the Pet BAG Specification Document. This document reviews Pet BAG’s software needs. Review the pet check in and pet check out methods, which are described in the Functionality section. Then choose one of these methods (check in or check out) to implement. As you read through the descriptions for each method, ask yourself the following:
- How would I break down these steps in a way that a computer can understand?
- What information would I need from the user at each point?
- When would it be a good idea to use decision branching, such as “IF” and “IF ELSE” statements?

Next, write pseudocode that outlines a plan for the method you chose 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.

# 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 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.

### Diagram Details

**Pet Class**
- Attributes:
- `- petType`
- `- petName`
- `- petAge`
- `- dogSpaces`
- `- catSpaces`
- `- daysStay`
- `- amountDue`
- Methods:
- `+ Pet()`
- `+ getPetType()`
- `+ setPetType()`
- `+ getPetName()`
- `+ setPetName()`
- `+ getPetAge()`
- `+ setPetAge()`
- `+ getDogSpaces()`
- `+ setDogSpaces()`
- `+ getCatSpaces()`
- `+ setCatSpaces()`
- `+ getDaysStay()`
- `+ setDaysStay()`
- `+ getAmountDue()`
- `+ setAmountDue()`

**Dog Class**
- Attributes:
- `- dogSpaceNumber`
- `- dogWeight`
- `- grooming`
- Methods:
- `+ Dog()`
- `+ getGrooming()`
- `+ setGrooming()`
- `+ getDogWeight()`
- `+ setDogWeight()`
- `+ getDogSpaceNumber()`
- `+ setDogSpaceNumber()`

**Cat Class**
- Attributes:
- `- catSpaceNumber`
- Methods:
- `+ Cat()`
- `+ getCatSpaceNumber()`
- `+ setCatSpaceNumber()`

### Diagram Explanation
The UML Class Diagram illustrates the primary classes involved in the Pet BAG application: `Pet`, `Dog`, and `Cat`. The `Pet` class serves as a general class with attributes and methods that pertain to all pets, while the `Dog` and `Cat` classes inherit from the `Pet` class and

**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.

<table>
<tr>
<th>Type of Pet</th>
<th>Daily Boarding Fee</th>
<th>Grooming Fee</th>
</tr>
<tr>
<td>Dog (greater than or equal to 30 lbs.)</td>
<td>$34.00</td>
<td>$29.95</td>
</tr>
<tr>
<td>Dog (20–30 lbs.)</td>
<td>$29.00</td>
<td>$24.95</td>
</tr>
<tr>
<td>Dog (fewer than 20 lbs.)</td>
<td>$24.00</td>
<td>$19.95</td>
</tr>
<tr>
<td>Cat</td>
<td>$18.00</td>
<td>N/A</td>
</tr>
</table>

Expert Solution

Trending now

This is a popular solution!

Step by step

Solved in 2 steps with 1 images

SEE SOLUTION Check out a sample Q&A here