0% found this document useful (0 votes)
30 views

MizeMap UML

The document describes 7 use cases for an application that allows users to manage inventory and product locations. The use cases include activating and terminating accounts, logging in, adding and updating item locations, viewing cart items, and locating products. The use cases define the actors, workflows, success and failure conditions, and alternate flows for each scenario.

Uploaded by

NOEL GALLO
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
30 views

MizeMap UML

The document describes 7 use cases for an application that allows users to manage inventory and product locations. The use cases include activating and terminating accounts, logging in, adding and updating item locations, viewing cart items, and locating products. The use cases define the actors, workflows, success and failure conditions, and alternate flows for each scenario.

Uploaded by

NOEL GALLO
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 7

MizeMap: Assisting Customers in Efficient Market Shopping

Use Case Description:

Use Case: Activate Account

Use Case ID: U-001

Related Requirements: -

Description: Activation of the admin/employees' account

Preconditions: Application is open

Success Condition: Account Created

Failed Condition: Account not created

Actors: Client/Owner

1. The client/owner will click the account creation button

2. Fill up all the information

3. The client/owner registers the account by clicking the


Flow of Activities:
register button

4. The system will show the message that the account has

been successfully activated.

3. The client/owner can’t register the account by clicking

register

i. The client/owner needs to check if all input data is

correct or no missing data that need to fill in

ii. The client/owner should click the register button


Alternate Flow:
4. The system showed that the account failed to create

because some input key data doesn’t match any records

in administration records

i. The client/owner needs to attach his records and

do an activation account again


Terminate
Account

Use Case: Terminate Account

Use Case ID: U-002

Related Requirements: U-001

Description: Users with administration rights can terminate accounts.

Preconditions: There are accounts in the database to be terminate.

Success Condition: Account Terminated

Failed Condition: Account not Terminated

Actors: Client/Owner

1. The actor will open the application if not open already

2. The actor will click the login button

3. The actor will input his/her client/owner ID and

password into the textbox

Flow of Activities: 4. The client/owner then clicks the login button

5. The system will show that the account is successfully

logged in

6. The client/owner should be able to use the admin part of

the system

5. The client/owner failed to log in because of the wrong


inputs
i. The client should check if the input ID and

password are correct.

ii. The client/owner then clicks the login button


Alternate Flow:
5. The client/owner failed to log in again
i. The actor should fill up a form for a password
change
ii. Click the save button
iii. The system will show a message that the
password has been changed
Use Case: Log in Account

Use Case ID: U-003

Related Requirements: U-001

Users with administration rights want to open the admin


Description:
part of the application

Preconditions: The employee should already have an account

Success Condition: Allows access to system admin

Failed Condition: Failed to login into the actor's account

Actors: Employee

1. The actor will open the application if not open already

2. The actor will click the admin button

3. The actor will input his/her client/owner ID and

password into the textbox

Flow of Activities: 4. The employee then clicks the login button

5. The system will show that the account is successfully

logged in

6. The employee should be able to use the admin part of

the system

5. The employee failed to log in because of the wrong


inputs
iii. The employee should check if the input ID and

password are correct.

iv. The employee then clicks the login button


Alternate Flow:
5. The employee failed to log in again
ii. The actor should fill up a form for a password
change
iv. Click the save button
v. The system will show a message that the
password has been changed
Use Case: Adding Location of Item

Use Case ID: U-004

Related Requirements: U-001, U-002

Actors want to add products to designate also a new


Description:
location for that item

Preconditions: Actor should have an account

Success Condition: The results are displayed

Failed Condition: Adding transaction is not completed

Actors: Client/Owner

1. The actor will log in to his/her account

2. Search for the item want to add

3. The actor will click add to proceed to the next step

Flow of Activities: 4. There will be another window that needs to fill in about

the location of an item

5. The actor will save the complete information

6. The results will be displayed

5. The actor failed to save the information


i. System will display an error message that there
Alternate Flow: is missing information need to fill in or incorrect
information
ii. Actors will check if the all needed information is
provided and change it if there's wrong
Use Case: Updating Location of Items

Use Case ID: U-005

Related Requirements: U-002, U-003, U-004

Description: Actors want to update the location of an item

• Actor should have an account


Preconditions:
• Item should already have location

Success Condition: The results are displayed

Failed Condition: Updating transaction is not completed

Actors: Client Owner

1. The actor will log in to his/her account

2. Search the item want to update location

3. Actor will click update to proceed to the next step

4. There will be another window that need to fill in about


Flow of Activities:
the new updated location

5. The actor will save the information the complete

information

6. The results will be displayed

5. The actor failed to save the information


i. System will display an error message that there
Alternate Flow: is missing information need to fill in or incorrect
information
ii. Actors will check if the all needed information is
provided and change it if there's wrong
Use Case: Cart Listing

Use Case ID: U-006

Related Requirements: U-004, U-005

Description: Actors want to confirm the cart items

Preconditions: Actors should have added items to the cart

Success Condition: The list of items will be displayed

Failed Condition: Failed to confirm list of items

Actors: Customer

1. The actor will search the products he /she want to buy

2. The item will then be added to the cart

3. Actor will be given a chance to change/delete the


Flow of Activities:
selected products

4. The actor will checkout/confirm the list of items

5. The list of items will be displayed

1. There will be an error message when the actor decides to


proceed without selecting any items
i. The screen will then go back the selection of
Alternate Flow: products
ii. Actor will be given a chance to select items
iii. The actor will checkout/confirm the list of items
iv. The list of items will be displayed
Use Case: Locating

Use Case ID: U-007

Related Requirements: U-004, U-005, U-006

System will be given a map that contains the items in the


Description:
cart and it will show the location of the items.

Preconditions: Customers should have confirmed the items to the cart

The location of the items will be given on the map with an


Success Condition:
arrow guiding the Actor

Failed Condition: Failed to the displayed path

Actors: System

1. The system will find and locate the items in the map.

Flow of Activities: 2. The system will compute the total price of all items in

the cart.

Alternate Flow: 1. Failed to the displayed path


i. Procced again to cart listing

You might also like