Defining Classes Labs – Part 1 and Part 2

The system that Victoria is looking for must have the capability of categorizing her data by, at
least, the following category classes:
1. Payment Type
2. Product Type
User Story
Eventually, we would like to retrieve total amounts of income paid for by credit card, debit card,
PayPal and cash. We call this Payment Type.
Acceptance Criteria:
1. Must be able to query Payment Type to be able to select income transactions.

Use Case Name Create a payment type

Triggering Event A new type of payment type available
Brief Allows the Owner to create a payment type
Description
Actors Owner
Related Use
Cases
Preconditions Owner has opened the Main Menu.
Post Conditions payment is added and available to query
Flow of Actor System
activities
1. Requests to add a new payment Displays a list of payment types
type prompting for a payment type
identifier and description.
2. Enters payment type identifier Verifies that payment type
and description identifier and description have been
entered
Prompts for confirmation
3. Confirms entry Saves the payment type and returns
to the main menu
Exception  Owner chooses to cancel adding payment type
Conditions

Use Case Name Change a payment type description

Triggering Request to change a payment description
Event

1|Page
Brief Allows the Owner to change a payment type description
Description
Actors Owner
Related Use
Cases
Preconditions Owner has opened the Main Menu.
Post Conditions Payment type description is updated
Flow of Actor System
activities
1. Requests to change a Displays a list of payment types
payment type and prompts for payment type
selection.
2. Selects a payment type Retrieves the payment type
description and prompts for
updates

3. Updates description and Verifies that description was

requests to save entered.
Saves the data
Exception  Owner chooses to cancel updating the payment type description
Conditions

Use Case Name Delete a payment type

Triggering Request to delete a payment type
Event
Brief Allows the Owner to delete a payment type
Description
Actors Owner
Related Use
Cases
Preconditions Owner has opened the Main Menu.
Post Conditions Payment type is deleted
Flow of Actor System
activities
1. Requests to delete a payment Displays a list of payment types
type Prompts for selection
2. Selects a payment type Retrieves the payment type and
description. Prompts to delete
3. Chooses to delete Deletes the payment type.
Exception  Owner chooses to cancel deleting the payment type
Conditions

Use Case Name Query all payment types and their descriptions

2|Page
 Triggering Request for payment types
Event
Brief Allows the Owner to retrieve all payment types and their descriptions.
Description
Actors Owner
Related Use
Cases
Preconditions Owner has opened the Main Menu.
Post Conditions All payment types and their descriptions are retrieved.
Flow of Actor System
activities
1. Requests to query all payment Displays a list of payment types
types Prompts to cancel
2. Chooses to cancel returns to the main menu
Exception  Owner chooses to cancel retrieving the payment types
Conditions

User Story
With our expansion, our list of locations is growing. We would like to record the address and
notes about each location.
Acceptance Criteria:
1. Must be able to query locations.
2. Must be able to record locations.
Use Case Name Create a location
Triggering Event A new location
Brief Allows the Owner to create a location
Description
Actors Owner
Related Use
Cases
Preconditions Owner has opened the Main Menu.
Post Conditions Location is added and available to query
Flow of Actor System
activities
1. Requests to add a new location Displays a list of locations and
prompts for a location name,
address and notes
2. Enters the location name, Verifies that name and address
address and notes have been enter. Generates a
unique location identifier. Displays
location.
Prompts for confirmation

3|Page
 3. Confirms entry Saves the location and returns to
the main menu
Exception  Owner chooses to cancel adding the location
Conditions

Use Case Name Change a location

Triggering Request to change a location
Event
Brief Allows the Owner to change a location
Description
Actors Owner
Related Use
Cases
Preconditions Owner has opened the Main Menu.
Post Conditions location is updated
Flow of Actor System
activities
1. Requests to change a location Displays a list of locations and
prompts for location selection.
2. Selects a location Retrieves the location’s name,
address and notes

3. Updates the location and Saves the data

requests to save
Exception  Owner chooses to cancel updating the location
Conditions

Use Case Name Delete a location

Triggering Request to delete a location
Event
Brief Allows the Owner to delete a location
Description
Actors Owner
Related Use
Cases
Preconditions Owner has opened the Main Menu.
Post Conditions location is deleted
Flow of Actor System
activities
1. Requests to delete a location Displays a list of locations
Prompts for selection
2. Selects a location Retrieves the location. Prompts to

4|Page
 delete
3. Chooses to delete Deletes the location
Exception  Owner chooses to cancel deleting the location.
Conditions

Use Case Name Query all locations

Triggering Request for a list of locations and their addresses
Event
Brief Allows the Owner to retrieve all locations
Description
Actors Owner
Related Use
Cases
Preconditions Owner has opened the Main Menu.
Post Conditions All locations and addresses are displayed.
Flow of Actor System
activities
1. Requests to query all locations Displays a list of locations.
Prompts to cancel
2. Chooses to cancel returns to the main menu
Exception  Owner chooses to cancel query locations
Conditions

User Story
To allow for easy retrieval of products, we would like to organize our list of products by product
type.
Acceptance Criteria:
1. Must be able to query product types.
2. Must be able to record a new product type.
Use Case Name Create a product type
Triggering Event Business decides to add a new type of products
Brief Allows the Owner to create a product type
Description
Actors Owner
Related Use
Cases
Preconditions Owner has opened the Main Menu.
Post Conditions product type is added and available to query
Flow of Actor System
activities

5|Page
 1. Requests to add a new product Displays a list of product types and
type prompts for product type and
description
2. Enters product type and Verifies that product type and
description description have been entered.
Displays product type.
Prompts for confirmation
3. Confirms entry Saves the product type and returns
to the main menu
Exception  Owner chooses to cancel adding the product type
Conditions

Use Case Name Change a product type

Triggering Request to change a product type
Event
Brief Allows the Owner to change a product type
Description
Actors Owner
Related Use
Cases
Preconditions Owner has opened the Main Menu.
Post Conditions location is updated
Flow of Actor System
activities
1. Requests to change a product Displays a list of product types
type and prompts for product types
selection.
2. Selects a product type Retrieves the product type

3. Updates the product type and Saves the data

requests to save
Exception  Owner chooses to cancel updating the product type
Conditions

Use Case Name Delete a product type

Triggering Request to delete a product type
Event
Brief Allows the Owner to delete a product type
Description
Actors Owner
Related Use
Cases
Preconditions Owner has opened the Main Menu.
Post Conditions Product type is deleted

6|Page
Flow of Actor System
activities
1. Requests to delete a product Displays a list of product types
type Prompts for selection
2. Selects a product type Retrieves the product types.
Prompts to delete
3. Chooses to delete Deletes the product type
Exception  Owner chooses to cancel deleting the product type.
Conditions

Use Case Name Query Product Types

Triggering Request for a list of product types
Event
Brief Allows the Owner to retrieve all product types
Description
Actors Owner
Related Use
Cases
Preconditions Owner has opened the Main Menu.
Post Conditions All product types are displayed.
Flow of Actor System
activities
1. Requests to query all product Displays a list of product types.
types Prompts to cancel
2. Chooses to cancel returns to the main menu
Exception  Owner chooses to cancel query product types
Conditions

7|Page