เลือกไซต์น ี

Welcome Category Promotion Payment inform Help Contacts Admin Tab About Us

About Business >

Use-Case Narrative

Use-Case Narrative for “Check Stock”

Use case:
Administrator able to Check Stock.

Iteration:
1, last modification: 29 September 2012 by Aekaphon Chaisereelamlert.

Primary Actor:
Administrator.

Goal in context:
To view the product inventory.

Preconditions:
System must be fully configured; appropriate user ID and passwords must be obtained.

Trigger:
The Administrator decides to view their product inventory.

Scenario:
1. The Administrator logs onto the Shopping Online website.
2. The Administrator enters his/her ID.
3. The Administrator enters his/her password.
4. The system displays all major function lists.
5. The Administrator selects the function “Administrator Panel”.
6. The Administrator selects “Check Stock”
7. The system displays the list of product’s stock arrange by product name.
8. The Administrator inserts the name of product in search box.
9. The system displays the searched product stock.

Exceptions:
1. ID or password are incorrect or not recognized – see use case Log in.
2. The Administrator selects “Modify page” – see use case
Administrator able to Manage Product Database
3. The Administrator selects “Money Transfer Check” – see use case
Administrator able to Check money transfer status.
4. The Administrator selects “Selling Record” – see use case
Administrator able to View Selling Record Statistic.

Priority:
To be implemented in basic function.

When available: N/A

Frequency of use: Frequency use

Translate
Channels to actor: Web browser, Administrator’s server.

Open issues: N/A

Use-Case Narrative for “View Selling Record Statistic”

Use case: Administrator able to View Selling Record Statistic.

Iteration: 1, last modification: 29 September 2012 by Aekaphon Chaisereelamlert.

Primary Actor: Administrator.

Goal in context: To view the selling statistic of the products.

Preconditions: System must be fully configured; appropriate user ID and passwords must be obtained.

Trigger: The Administrator decides to view their selling statistic of their products.

Scenario: 1. The Administrator logs onto the Shopping Online website.

2. The Administrator enters his/her ID.
3. The Administrator enters his/her password.
4. The system displays all major function lists.
5. The Administrator selects the function “Administrator Panel”.
6. The Administrator selects “Selling Record”
7. The system displays the list of product’s selling information arrange by product name.
8. The Administrator inserts the name of product in search box.
9. The system displays the searched product’s selling information.

Exceptions: 1. ID or password are incorrect or not recognized – see use case Log in.
2. The Administrator selects “Modify page” – see use case
Administrator able to Manage Product Database.
3. The Administrator selects “Money Transfer Check” – see use case
Administrator able to Check money transfer status.
4. The Administrator selects “Check Stock” – see use case
Administrator able to Check Stock.

Priority: To be implemented in basic function.

When available: N/A

Frequency of use: Moderate Frequency

Channels to actor: Web browser, Administrator’s server.

Open issues: N/A

Use-Case Narrative for “Checks money transfer status”

Use case: Administrator able to Checks money transfer status.

Iteration: 1, last modification: 29 September 2012 by Aekaphon Chaisereelamlert.

Primary Actor: Administrator.

Goal in context: To check the customer money transfer status.

Preconditions: System must be fully configured; appropriate user ID and passwords must be obtained.

Trigger: The Administrator decides to check their customer money transfer status.

Scenario: 1. The Administrator logs onto the Shopping Online website.

2. The Administrator enters his/her ID.
3. The Administrator enters his/her password.
4. The system displays all major function lists.
5. The Administrator selects the function “Administrator Panel”.
6. The Administrator selects “Money Transfer Check”.
7. The system displays the list of product’s reserve information arrange by customer name.
8. The Administrator inserts the name or ID of customer in search box.
9. The system displays the searched customer’s reserve information.
10. The Administrator check on customer’s product reserve list transfer status.

Exceptions: 1. ID or password are incorrect or not recognized – see use case Log in.
2. The Administrator selects “Modify page” – see use case
Administrator able to Manage Product Database.
3. The Administrator selects “Selling Record” – see use case
Administrator able to View Selling Record Statistic.

4. The Administrator selects “Check Stock” – see use case

Administrator able to Check Stock.

Priority: To be implemented in basic function.

When available: N/A

Frequency of use: Frequency use

Channels to actor: Web browser, Administrator’s server.

Open issues: N/A

Use-Case Narrative for “Managing Product Database”

Use case:
Administrator able to Manage Product Database.

Iteration:
1, last modification: 29 September 2012 by Aekaphon Chaisereelamlert.

Primary Actor: Administrator.

Goal in context: To update the product database.

Preconditions: System must be fully configured; appropriate user ID and passwords must be obtained.

Trigger: The Administrator decides to update their products information.

Scenario: 1. The Administrator logs onto the Shopping Online website.

2. The Administrator enters his/her ID.
3. The Administrator enters his/her password.
4. The system displays all major function lists.
5. The Administrator selects the function “Administrator Panel”.
6. The Administrator selects “Modify page”.
7. The system displays the list of product’s information arrange by product name.
8. The Administrator inserts the name of product in search box.
9. The system displays the searched product’s information.
10. The Administrator selects “edit” after product’s information.
11. The Administrator change status in “inventory”.
12. The system displays the edited product’s information.
13. The Administrator selects “remove” after product’s information.
14. The system removes that product’s information.

Exceptions: 1. ID or password are incorrect or not recognized – see use case Log in.
2. The Administrator selects “Money Transfer Check” – see use case Administrator able to Check money transfer sta
3. The Administrator selects “Selling Record” – see use case
Administrator able to View Selling Record Statistic.
4. The Administrator selects “Check Stock” – see use case Administrator able to Check Stock.

Priority: To be implemented in basic function.

When available: N/A

Frequency of use: Frequency use

Channels to actor: Web browser, Administrator’s server.

Open issues:
1. Server down while the Administrator editing their database.
2. Edited data will duplicate when more than one Administrator editing in same time example both Administrator sele
shortcut function to increase inventory of product then the server will increase it by twice.

Use-Case Narrative for “Buy Products”

Use case: Members able to Buy Products.

Iteration: 1, last modification: 29 September 2012 by Aekaphon Chaisereelamlert.

Primary Actor: Members.

Goal in context: To buy products or reserve.

Preconditions: System must be fully configured; appropriate user ID and passwords must be obtained.

Trigger: The Members decides to buy products.

Scenario: 1. The Members logs onto the Shopping Online website.

2. The Members enter his/her ID.
3. The Members enter his/her password.
4. The system displays member function lists.
5. The Members select the function “Buy Products”.
6. The system displays the list of product’s name arrange by product name. Except “Out of stock” product.
7. The Members insert the name of product in search box or select product name from the list.
8. The system displays the product’s purchase information.
9. The Members select “Add to cart” after product’s information.
10. The Members select “Purchase” after he/she gets all products they want.
11. The system displays the Purchase page.
12. The Members select “Purchase”.
13. The system displays purchased information.

Exceptions: 1. ID or password are incorrect or not recognized – see use case Log in.
2. The Members selects “View Promotion” – see use case Members able to View Promotions.
3. The Members selects “Check Track Number of EMS” – see use case
Members able to Check Track Number of EMS.
4. The Members selects “View Product” – see use case Members able to View Product.
5. The Members selects “Check Shipping Product Status” – see use case Members able to Check Shipping Product

Priority: To be implemented in basic function.

When available: N/A

Frequency of use: Frequency use

Channels to actor: Web browser

Open issues: 1. Server down while the Members purchasing our product.

Use-Case Narrative for “View Promotion”

Use case: Members able to View Promotion.

Iteration: 1, last modification: 29 September 2012 by Aekaphon Chaisereelamlert.

Primary Actor: Members.

Goal in context: To view the promotion information.

Preconditions: System must be fully configured; appropriate user ID and passwords must be obtained.

Trigger: The Members decides to view promotions information.

Scenario: 1. The Members logs onto the Shopping Online website.

2. The Members enter his/her ID.
3. The Members enter his/her password.
4. The system displays member function lists.
5. The Members select the function “View Promotion”.
6. The system displays the list of product’s promotion information arrange by promotion’s date.

Exceptions: 1. ID or password are incorrect or not recognized – see use case Log in.
2. The Members selects “Buy Products” – see use case Members able to Buy Products.
3. The Members selects “Check Track Number of EMS” – see use case
Members able to Check Track Number of EMS.
4. The Members selects “View Product” – see use case Members able to View Product.
5. The Members selects “Check Shipping Product Status” – see use case Members able to Check Shipping Product

Priority: To be implemented in basic function.

When available: N/A

Frequency of use: Frequency use

Channels to actor: Web browser

Open issues: N/A

Use-Case Narrative for “View Product”

Use case: Members able to View Product.

Iteration: 1, last modification: 29 September 2012 by Aekaphon Chaisereelamlert.

Primary Actor: Members.

Goal in context: To view the product information.

Preconditions: System must be fully configured; appropriate user ID and passwords must be obtained.

Trigger: The Members decides to view products information.

Scenario: 1. The Members logs onto the Shopping Online website.

2. The Members enter his/her ID.
3. The Members enter his/her password.
4. The system displays member function lists.
5. The Members select the function “View Products”.
6. The system displays the list of product arrange by product’s name.
7. The Members insert the name of product in search box or select product name from the list.
8. The system displays product’s information.

Exceptions: 1. ID or password are incorrect or not recognized – see use case Log in.
2. The Members selects “Buy Products” – see use case Members able to Buy Products.
3. The Members selects “Check Track Number of EMS” – see use case
Members able to Check Track Number of EMS.
4. The Members selects “View Promotion” – see use case Members able to View Promotion.
5. The Members selects “Check Shipping Product Status” – see use case Members able to Check Shipping Product

Priority: To be implemented in basic function.

When available: N/A

Frequency of use: Frequency use

Channels to actor: Web browser

Open issues: N/A

Use-Case Narrative for “Check Shipping Product Status”

Use case: Members able to Check Shipping Product Status.

Iteration: 1, last modification: 29 September 2012 by Aekaphon Chaisereelamlert.

Primary Actor: Members.

Goal in context: To view the product shipping status.

Preconditions: System must be fully configured; appropriate user ID and passwords must be obtained.

Trigger: The Members decides to check their product shipping status.

Scenario: 1. The Members logs onto the Shopping Online website.

2. The Members enter his/her ID.
3. The Members enter his/her password.
4. The system displays member function lists.
5. The Members select the function “Check Shipping Product Status”.
6. The system displays the list of their product shipping status.

Exceptions: 1. ID or password are incorrect or not recognized – see use case Log in.
2. The Members selects “Buy Products” – see use case Members able to Buy Products.
3. The Members selects “Check Track Number of EMS” – see use case
Members able to Check Track Number of EMS.
4. The Members selects “View Promotion” – see use case Members able to View Promotion.
5. The Members selects “View Product” – see use case Members able to View Product.

Priority: To be implemented in basic function.

When available: N/A

Frequency of use: Frequency use

Channels to actor: Web browser

Open issues: N/A

Use-Case Narrative for “Check Track Number of EMS”

Use case: Members able to Check Track Number of EMS.

Iteration: 1, last modification: 29 September 2012 by Aekaphon Chaisereelamlert.

Primary Actor: Members.

Goal in context: To view the product EMS status.

Preconditions: System must be fully configured; appropriate user ID and passwords must be obtained.

Trigger: The Members decides to check their product shipping status.

Scenario: 1. The Members logs onto the Shopping Online website.

2. The Members enter his/her ID.
3. The Members enter his/her password.
4. The system displays member function lists.
5. The Members select the function “Check Track Number of EMS”.
6. The system displays the list of their product EMS status.

Exceptions: 1. ID or password are incorrect or not recognized – see use case Log in.
2. The Members selects “Buy Products” – see use case Members able to Buy Products.
3. The Members selects “Check Shipping Product Status.” – see use case
Members able to Check Shipping Product Status.
4. The Members selects “View Promotion” – see use case Members able to View Promotion.
5. The Members selects “View Product” – see use case Members able to View Product.

Priority: To be implemented in basic function.

When available: N/A

Frequency of use: Frequency use

Channels to actor: Web browser

Open issues: N/A

Use-Case Narrative for “Reservation Product”

Use case: Members able to Reservation When “Out Of Stock”.

Iteration: 1, last modification: 29 September 2012 by Aekaphon Chaisereelamlert.

Primary Actor: Members.

Goal in context: To reserve when product out of stock.

Preconditions: When the Members select “Add to cart” and product “Out Of Stock”.

Scenario: 1. The system display that product is out of stock.

2. The system display reservation page.
3. The Members insert number for reserved.
4. The system record reserved number to the database.

Exceptions: 1. ID or password are incorrect or not recognized – see use case Log in.
2. The Members select “close” – see use case
Members able to Buy Products.

Priority: To be implemented in basic function.

When available: N/A

Frequency of use: Moderate frequency

Channels to actor: Web browser

Open issues: N/A

Use-Case Narrative for “Log in”

Use case: User able to Log in.

Iteration: 1, last modification: 29 September 2012 by Aekaphon Chaisereelamlert.

Primary Actor: Members, Administrator.

Goal in context: To identify user status.

Preconditions: N/A

Trigger: User want use the Member or Administrator function.

Scenario: 1. The system display log in page.

2. The Members/Administrator enter his/her ID.
3. The Members/Administrator enter his/her password.
4. The Members/Administrator select “Log in”.
5. The system displays log in result.
6. If password or ID doesn’t match return to scenario 1.

Exceptions: 1. User doesn’t have ID – see use case User able to Registeration

Priority: To be implemented in basic function.

When available: N/A

Frequency of use: Frequency use

Channels to actor: Web browser

Open issues: N/A

Use-Case Narrative for " Registeration "

Use-Case Customers are able to register on website.
Iteration 1, last modification : October 1 by Tharamak S.
Primary actor Customer
Goal in context Customers register to be a member of website.
Precondition -
Trigger Customers want to buy products but don't have an account.

Scenario 1. Customer open etc online shopping website.

2. Customer select " Registeration " menu.
3. Customer fills information in register form.
4. Customer selects the " Accept " box in a etc online shopping policy.
5. Customer selects the " Confirm " button.
6. The system displays your curtomer number and shows confirm content you to be a member.

Exceptions 1. Customers use a used citizen ID.

2. Customes don't accept the etc online shopping policy.
3. Customer use a used

Priority To be implemented in basic function.

When available N/A
Frequency of use frequently use
Channel to actor via PC or Mobile base browser and Internet connection.
Secondary actors N/A
Channels to secondary actors N/A
Open issues N/A

Use-Case Narrative for " Notify problems to administrator "

Use-Case Customers and members can notify problems and contact to administrator.
Iteration 1, last modification : October 1 by Tharamak S.
Primary actor Customer, Member
Goal in context To receive respond 's message from administrator.
Precondition N/A
Trigger Customers or users have problems or doubts and want to inform administrator.
Scenario
1. Customer open etc online shopping website.
2. Customer select " Notify problem " menu.
3. Customer fills problems or doubts in a box.
4. Customers select " OK " button.
5. The system displays "Thank You for your message. We will answer your
questions as soon as possible."
Exceptions –
Priority To be implemented in basic functions.
When available N/A
Frequency of use frequently use
Channel to actor via PC or Mobile base browser and Internet connection.
Secondary actors N/A
Channels to secondary actors N/A
Open issues N/A

Use-Case Narrative for " Search product "

Use-Case Members are able to search products.
Iteration 1, last modification : October 1 by Tharamak S.
Primary actor Member
Goal in context To search products on website.
Precondition
1. Member must log in on website.
2. Appropriate user ID and password must be obtained.
Trigger Member would like to find products on website
Scenario
1. Member logs onto on the etc online shopping website.
2. Member enters his or her user ID.
3. Member enters his or her password.
4. Member select "OK" button to log in.
5. Member enters names of product in a box.
6. Member selects "Search" button to search product.
7. The system displays the products or "Not find products" content if
the system can't find products.
Exceptions
1. ID or passwords are incorrect or not recognized - see use case Log
in
Priority To be implemented in basic function.
When available N/A
Frequency of use frequently use
Channel to actor via PC or Mobile base browser and Internet connection.
Secondary actors Administrator
Channels to secondary actors via PC or Mobile base browser and Internet connection.
Open issues N/A

Use-Case Narrative for " Inform a money transfer "

Use-Case Members are able to inform a money transfer on website.
Iteration 1, last modification : October 1 by Tharamak S.
Primary actor Member
Goal in context To inform a money transfer status via website.
Precondition
1. Member must log in on website.
2. Appropriate user ID and password must be obtained.
3. Member must have order products record.
Trigger
Member would like confirm a money transfer status in
payment
Scenario
1. Member logs onto on the etc online shopping website.
2. Member enters his or her user ID.
3. Member enters his or her password.
4. Member select "OK" button to log in.
5. Member select "Inform the money transfer".
6. Member enter an information of transfer in transfer form.
7. Member select "OK" button to send a form.
8. The system displays " Thank you for your payment. "
Exceptions
1. ID or passwords are incorrect or not recognized - see
use case Log in
2. Member enter incomplete transfer form.
Priority To be implemented in basic functions.
When available N/A
Frequency of use frequently use
Channel to actor via PC or Mobile base browser and Internet connection.
Secondary actors N/A
Channels to secondary actors N/A
Open issues N/A

Report Abuse | Powered By Google Sites