Final Version Cospact Use Cases Script

Fashion Inc.
Use Case
Table of Contents for Fashion Inc. Use Case
Index 1
Registration 2
Product Categories 3
Place order 4
Check order status 6
Return item 7
Maintain account information 8
Process order 9
Process out of stock order 10
Process return 11
Setup promotion list 13
Maintain product catalogue 14
Generate popular item report 16
1
Send promotional emails 17
Process credit card and refund 18
Redeem coupon or Gift cards 19
Authentication 21
Deliver items 23
Deliver gift items 24
Collect return item 25
Women Category 27
2
Use Case Name: REGISTRATION
Created By: Business Analyst Name Last Updated By:
Actors: New Customer

Description: This use case allows new customer to register with a valid email id, phone
number and shipping address. There will be a section to provide a
username and password. A welcome email is send to the registered email
for the customer after the successful registration on Fashion Inc.
Trigger: User selects the ‘Register User’ link
Authentication of Use Case
Include use cases Authentication
Preconditions: 1. Customer needs to register and then login in, in order to purchase their
items
2. Billing and shipping addresses needs to be accurate with zip code
Postconditions: 1. Customer will be prompted to register as soon as he selects the product
and wants to buy it.
Normal Flow: 1. Customer enters Name, Address, Email Id.
2. The system checks with image to click, I am not a Robot.
3. The system triggers Authentication use case.
4. Welcome email is sent to the user.
5. System displays login button
6. Customer can browse items and add to shopping cart and purchase
them
7. The use case ends
Alternative Flows: 1 The New Customer has added a product to the shopping cart
a. The system displays “Register Page” ; then it starts from the step 1
b. The use case ends
Priority: High
Notes and Issues: None
3
Use Case Name: Product Categories
Actors: New customers, Registered customers
Description: This use case allows New or Registered customer to browse all the different
type of products. Fashion Inc. will have following women categories such as
clothing, western wear, ethnic wear, lingerie and nightwear, accessories,
handbags and clutches, shoes (fashion sandals) and fashion sales and deals
(There will be some more categories for men and kids in future). The
purpose of this use case is to narrow down the customer search and
customize according to their needs.
Trigger: As soon as customer tries to search different products that is on the website
Include use cases None
Extends use cases None
Preconditions: Customer needs to be on the website
Postconditions: Customer will either browse or add the products to the cart
Normal Flow: 1. New or registered customer will go on website and type the categories
in the search bar
2. Customer will be directed to a further page in the category they have
chosen.
3. System will display the products of category that customer has chosen
4. Customer will browse all the display products and choose the products
they like
5. Customer will be prompted to either ‘add to cart’ their selected product
or ‘add to wish list’ (this step option will be shown only for registered
customer)
6. This use case ends
Alternative Flows: 4a. If customer do not want to browse all the listed products
1. Customer can narrow down the search by their preference
2. In order to filter down the category customer has to use the search
bar on the left side
3. Based on the category chosen the filter options will change
4. System will display following filters for the clothing category:
System will display material, type, color, price, style, gender, age, and
vendor
5. System will display following filters for the accessories category:
System will display type, style, color, size, price, and vendor
4
6. System will display following filters for the handbags and clutches
category:
System will display material, color, style (size), price, and vendor
7. System will display following filters for the shoes category:
System will display size, color, material, style, prize, vendor
8. System will display following filters for Fashion markdowns and
clearance:
System will display price cut products of all the 4 categories
9. Repeat steps 4 and 5
Priority: High
Notes and Issues: The extensive list of women category is included on page 27 for more
details
Use Case Name: PLACE ORDER

Actors: Customer
Description: This use case allows customer to log in, browse the items and add to cart.
They will have 5 attempts to enter their correct ID. If they entered wrong ID
5 times then system will prompt them to contact the system administrator
and set up new password. Once the item is added to the cart, they start
checking out their order. They need to verify the billing and shipping
address and make a payment to finalized and process their order.
Trigger: As soon as the customer will open the Fashion Inc. website and log in to
their account
Preconditions: 1. Customer need to login in, in order to purchase their items
2. Billing and shipping address needs to be accurate with zip code
Postconditions: 1. Customer will prompt to check their order is processed
Normal Flow: 1. Customer enter login information
2. The system triggers authentication use case
3. System display products menu for Men, women and kids
4. Customer browse items and click ‘add to shopping cart’ and the item
5
is added to the shopping cart
5. System display message that the Customer proceed to checkout
6. System asks user to provide shipping and billing information
7. Customer provide shipping and billing information
8. Customer will enter any item related coupons
9. Customer will make payment
10. System confirm the shipping information, process the order and
ship out the items
11. Customer receives items
Alternative Flows: 1a. Missing login ID and/ or password
1. The system prompts for customer ID and password
2. Use case resumes at step flow 1
1b. More than 5 attempts to enter login ID and Password
1. The system display “maximum attempts have been made. Please
contact system administrator/ customer service department for
technical support”
2. The use case ends until customer gets the new link for password set
up
Priority: High
Use Case Name: Check order status

Actors: Customer
Description: This use case allows customer to check their order status in detail. Once the
order is processed they will have a notification email to check the status of
their order. It will also allow user to track their order at any point.
Trigger: As soon as the order is processed from customer side
Preconditions: Customer order need to be purchased and get an order purchase
notification
Postconditions: Customer can either return item or get notification email or feedback of
6
service (optional)
Normal Flow: 1. Customer will login to check the status of their order
3. System send email once the order is processed
4. System will send email once shipping company labeled their orders
5. System will send email once tracking number is available
6. System will generate estimated arrival time and send it to the customer
via email
7. Customer will receive email once the order is delivered by shipping
company
Alternative Flows: 3a. If customer did not get any email in two days after purchase
1. Customer needs to call customer service department for receiving
any email
2. Agent will verify the email address and if email is incorrect then
agent will transfer a phone to technical team
3. Use case resume at step flow 3
5a. If customer can not open the tracking number
1. Customer will contact shipping company. Phone number will be
listed on email
2. Shipping company will resolve the issue
3. Use case resume at step flow 5
Priority: High
Notes and Issues: Customer can check all information by login to their account at any point
until they receive the item
Use Case Name: Return items

Actors: Customer
Description: This use case allows customer to send a request for returning their items. If
customer did not like the item then they have 14 days to return any apparel.
Apparel will be non returnable after 14 days period is over. Customer will
get free shipping label if item is defective. Incase the customer changed
their mind they have to pay the shipping cost. Customer needs to contact
7
Fashion Inc. service department either online or phone
Trigger: Once customer has decided to not keep the item
Preconditions: Customer will receive the item and inspect or try it out
Postconditions: Customer will contact sales staff
Normal Flow: 1. Customer will log in to their account
3. Customer will go to their account home page and go under return menu
4. Customer will write message for returning the massage
5. Customer will be prompted to read the return policy before submitting
the messages
6. Customer will accept submit button and message will be sent to the sales
staff
7. Customer will wait until they get any response from sales staff
Alternative Flows: None

Priority: High
Notes and Issues: Customer needs to wait until they get any response from sales staff. After
getting response further return procedure will start
Use Case Name: Maintain account information

Actors: Customer
Description: This use case allows customer to manage their account information at any
time. They can change their credit card information, updated shipping
address, and personal information. Once they registered their account they
can manage their account at any time. They can also add multiple address
and credit card information as well.
Trigger: Once customer had registered their new account
Preconditions: Customer needs to register and login to their account
8
Postconditions: Customer information will be updated and saved securely in their account.
Normal Flow: 1. Customer will login to manage their account information
3. Customer will go to manage account menu
4. Customer will be prompted to the screen where they can change multiple
information
5. They will either add or update the existing information
6. If customer choose to replace their current password then system
triggers authentication use case
7. Customer will have an option to delete their account
8. Once they choose this option system triggers authentication use case
9. They will choose “Done” button before log out of their account
Alternative Flows: 9a. If customer forget to choose “Done” button
1. System will not save changed information
2. Customer will have to login one more time
3. Customer will repeat steps 3 to 9
Priority: Moderate
Use Case Name: Process order

Actors: Sales staff

Description: This use case allows sales staff to inspect the customer order and process
the order in a timely manner. That way customer can receive their order on
time. Sales staff will verify all the order related information. They will make
sure that the item that has been ordered is in stock and in good condition. If
the inventory count is wrong then they need to either get the item as early
as possible or notify the guest incase delaying delivery date. After verifying
all the order they will notify the shipping company to pick up from
warehouse and deliver it to the guest at designated location.
Trigger: Once the order has been purchased, online sales staff will get notification
9
Extends use cases Process out of stock order
Preconditions: Order need to be purchased by the customer
Postconditions: Sales staff will notify shipping company to pick up the order from guest
warehouse
Normal Flow: 1. System will generate order for guest on sales staff computer
2. System will print green label and notify sales staff team member to take
care of this order
3. Order status needs to be changed by sales staff with in an 3 hour window
4. Sales staff team member will pick the green ticket and go to their
warehouse to verify the quantity
5. If the order item quantity is in stock then he will put the item in the cart
6. Put the green label sticker on the apparel and put it in the ready to pick
up bag
7. He will change the status of order in the computer
8. System will generate email automatically to notify guest and shipping
company that order is ready for pick up
Alternative Flows: 3a. If order is not pulled within 3 hour window
1. System will change the status as “back ordered”
2. System will generate an email to supervisor for verification
3. Supervisor will verify the order
4. Either contact guest or pull the order
5. System will follow steps 4 to 9
5a. If the order item inventory count is wrong
1. System will trigger Process out of stock use case
Priority: High
Notes and Issues: Warehouse facility and sales staff will be working in the same building
Use Case Name: Process out of stock order

Actors: Sales staff

Description: This use case allows sales staff to process out of stock order. In case of
10
wrong inventory count or defective apparel how can the sales staff can take
care of customer order? There are multiple ways, Fashion Inc. sales staff
will call the guest or notifying the guest via email, the idea is to sale
alternate or substitute the item. Last option should be to cancel customer
order and return their money back.
Trigger: When sales staff cannot locate the customer order item, if the product is
missing color, size, or if the product is defective in the warehouse
Extends use cases Process order
Preconditions: Customer order item must not to found anywhere, missing color, missing
size or if it is defective in the warehouse
Postconditions: Offer either substitute/alternate item or cancel guest order
Normal Flow: 1. Sales staff team member cannot locate the order or the found order item
in warehouse is defective
2. Sales team member will notify the supervisor
3. Once supervisor verify he will collect the customer information from
their order
4. Supervisor will call the customer and if they are not able to pick up the
phone then he will left a voicemail
5. At last if customer cannot reply over the phone then supervisor will
notify the customer via email address listed on their order
6. Supervisor will politely explain to the customer that they do not have
their item in stock
7. Supervisor will offer substitute or alternate item
8. After getting customer reply supervisor will either change the order item
and generate new order or cancel the order manually in the system
Alternative Flows: 7a. Customer do not need substitute or alternate item
1. Supervisor will offer the guest to wait until the receive their item
2. If customer is ok with that then follow step 8
7b. If customer cannot wait long to get their order item
1. Supervisor will apologize for their inconvenience
2. Supervisor will offer them to cancel their order and return money
back
3. If customer is ok with that then follow step 8
11
Priority: High
Use Case Name: Process return

Actors: Sales staff

Description: This use case allows sales staff to process the customer return. After getting
notification from customer account they need to inspect and analyze the
reason for return. Sales staff goal is to resolve the customer order issue and
try to understand the reason of return. Often it is possible to resolve
customer issue and clear misunderstandings. This way they do not need to
return the items and loose potential future customer. If there are too many
complaints then they need to inform supervisor to call vendor for quality
issue.
Trigger: As guest send a request to return their order
Preconditions: Customer needs to send return request through their account
Postconditions: Customer money will be credited through Payment Services or customer
will not return the item at all
Normal Flow: 1. System will notify sales staff that customer has requested return request
3. Sales staff will inspect the customer return request
4. Sales staff will identify the return request
5. Sales staff will determine whether return request is meeting return policy
or not
6. Sales staff will call the customer and try to understand customer point of
view over the phone
7. After listening customer point of view sales staff will try to resolve the
customer order issue
8. If customer issue is resolved then order do not require to process return
Alternative Flows: 5a. Return request does not meet return policy requirement
12
1. Sales staff will notify customer that return request does not meet
return policy standard
2. Sales staff will notify customer that their return request is “Declined”
due to return policy requirements
8a. If customer issue not resolved
1. Sales staff will approve the customer return request
2. Sales staff will email free shipping label to the guest if it requires
3. In case of no free shipping label sales staff will email customer their
warehouse address
4. Sales staff will process the return item in their warehouse
5. Sales staff will notify system to generate email to customer that their
return request is accepted and their return amount will be credited
back to their card in next 4 to 5 business days
6. Sales staff will sent an email thanking them for doing business with
them and will welcome their business in near future
Priority: High
Notes and Issues: Idea is always to resolve customer issue and do not lose customer sales.
Return needs to be the last option after going through all other options
Use Case Name: Setup promotion list

Actors: Marketing staff

Description: This use case allows marketing staff to setup the promotion list. Clothing
market especially online clothing market is very competitive. In order to
stand out unique and generate more sale marketing staff needs to be
competitive and analyze their competitors approach as many times as
possible. Setting up promotion list might help Fashion Inc. to generate more
sales and capture more market in fashion wear industry. Therefore this use
case will shows marketing staff on how to set up promotion list
Trigger: When promotion is required to capture more sales
13
Preconditions: Marketing staff needs to set up promotion list/flyer
Postconditions: Marketing staff needs marketing manager approval
Normal Flow: 1. Marketing staff will collect all the response from customer feedback
review
3. Marketing staff will attend meeting every Monday (or at least once a
week)
4. Marketing staff will discuss which category of items are selling more and
which category of items are selling less
5. Marketing staff will take current season and current trend under
consideration
6. Marketing staff will put current season and current trend items on sale
on front page
7. Before deciding the sale price they will inform the whole team on the cost
of the product
8. Marketing staff will try to set the price of out of season and out of trend
items very aggressively
9. Marketing staff will put out of season and out of trend items on clearance
item category
Marketing staff will send the promotion list details with price to marketing
manager
10. Once marketing manager approve the price and list marketing staff
will send this information to technical team
Alternative Flows: 9a. Marketing supervisor not approve the list
1. Marketing manager will conduct a meeting to decide which prices
needs to go up and which needs to be slashed down.
2. Marketing staff will work on highlighted issue
3. Marketing staff will send revised promotion list detailed with prices
to marketing manager
4. Marketing manager will look at the changes closely and approve or
deny the promotion list
5. If marketing manager denied then follow step 1 to 3 one more time
6. Once marketing manager approved the promotion lists follow step 9
Priority: High
14
Notes and Issues: At the end of every meeting every marketing staff team member should
agree to the decision that has been made and send public codes (anyone can
use), private codes (only to loyal customer who has accounts) and restricted
codes (complementary to apologize for inconvenience) to PayPal system.
Use Case Name: Maintain product catalogue


Description: This use case allows marketing staff how to maintain product catalogue.
The company must be always doing a R&D on the latest trends available in
the Fashion Industry as well as the different types of Ethnic wears.
Fashion wear industry is very competitive. In order to maintain sales
number they need to maintain a catalogue. If it’s not interesting it will result
in losing sales or potential customers. Maintaining te product catalogue
requires updating products constantly, dealing with supplier data,
expanding your product catalogue, keeping data quality consistent and
merchandising
Trigger: As soon as marketing staff need to add or delete any product
Extends use cases Generate popular items report
Product of the Week
Newly added items to be displayed on the main page.
Preconditions: Product catalogue management application needs to exist
Postconditions: Product catalogue will convert more visitors into sales
Normal Flow: 1. Marketing staff will collect all the requirement from customer feedback,
review and from suppliers
3. Marketing staff will conduct a meeting on 1st of every month (or at least
once a month)
4. Marketing staff will open the product catalogue management system
application
5. Marketing staff will determine how many products will be sold. That
number will be approved by marketing supervisor and upper
management
15
6. Marketing staff discuss how many variants we have for our product and
do we need to add more variants or not
7. Marketing staff will discuss how many categories do we have and is there
any need for adding category (application should tell how many
categories does Fashion Inc. have)
8. Marketing staff will discuss and track major changes in any inventory
levels in last month. They will increase or decrease inventory level
according to that
9. Marketing staff will discuss whether any change is needed on any
product category page. Current season and current trend will be taken
into consideration
10. Marketing staff will discuss is there any category need upsell via
related products or not
11. Meeting agenda and discussed details will be recorded for future
meetings
12. Necessary changes will be made and sent to the marketing manager
for approval
13. Marketing manager will approve the changes and send it to technical
team for implementation
14. (Extension point: Generate popular item report)
Alternative Flows: 13a. Marketing manager not approved the changes
1. Marketing manager will discuss his concerns with marketing staff
2. Marketing manager will understand the marketing staff point of view
3. Marketing manager will consider changes one more time
4. Marketing manager will request marketing staff to add or delete
changes accordingly
Priority: High
Notes and Issues: Marketing manager will be conducting the meeting and make sure all the
meeting agendas are discuss and recorded
Use Case Name: Generate popular item report

16
Description: This use case allows marketing staff to generate popular item report. After
discussing the meeting agenda on Maintaining a product catalogue use case
all information that marketing staff has will make it easy to generate
popular item report. This use case determines which product needs more
focus and which not. This report will help marketing staff to make accurate
decisions in their next meeting.
Trigger: As soon as all the agendas are discussed in maintain product catalogue
meeting
Extends use cases Maintain product catalogue
Preconditions: All meeting agenda needs to be discussed in Maintain product catalogue use
case
Postconditions: Report copy will be sent to the marketing staff before next meeting
Normal Flow: 1. Marketing staff will collect all the details that are discussed in Maintain
product catalogue use case
2. Marketing staff will filter all the information
3. Marketing staff will generate report that states which items were more
popular compare to others in terms of sales
4. Marketing staff will require to sent copy of this report a week before next
meeting
Alternative Flows: None
Priority: High
Notes and Issues: Marketing staff needs to send the copy of report to every member 1 week
before the next meeting
Use Case Name: Send promotional email


Description: This use case allows marketing staff to send promotional email to customer.
Since the market is very competitive and e-commerce is still a new
platform, marketing staff need to send promotional emails to their
17
customer for awareness purpose. Marketing staff will generate all the
accounts information and send them email once the promotion is on. This
email will increase more guest traffic that turns into sales
Trigger: As soon as promotional list is created
Preconditions: Promotion list needs to be created
Postconditions: More customers will visit the site
Normal Flow: 1. Once the promotion list is created, technical team will send the PDF
version of that file
2. Marketing staff will create a template for promotional email
3. Marketing staff will send copy to marketing manager for approval
4. Marketing manager will verify all the details
6. Marketing staff will gathered all customer account email information
from authentication use case (include use case)
7. Marketing staff will send promotional email to all the customers using the
approved template
Alternative Flows: 6a. If customer email was not valid
1. Marketing staff will delete that email address from their account
2. Customer will prompt to page “add email address” as soon as they
open account
Priority: High
Use Case Name: Process credit card or refund

Actors: Payment Services
Description: This use case allows Payment Services to process the credit or refund their
money back. They will always need approval from sales staff. They will do
either charged or refund money to customer card per sales staff order.
Trigger: Customer needs to choose make a payment option
18
Preconditions: Customer needs to choose make a payment option
Postconditions: Customer credit card will charge the amount or credit the money back
Normal Flow: 1. Customer will choose make a payment option while checking out
2. Customer will prompt to page collect credit card information
3. Customer will enter credit card number, CCV number and expiration
date
4. Payment Services will verify all the information
5. Payment Services will process the payment and notified the sales staff
and customer that transaction was processed
6. Incase of refunding money, sales staff will notify Payment Services how
much money needs to credit back on guest credit card
7. Payment Services will process the refund
8. Payment Services will notify sales staff and customer that refund
transaction is processed
Alternative Flows: 3a. Customer credit card number, details and CCV number do not matched
1. Payment Services will prompt on screen as “Credit card errors”
2. Repeat steps 3 to 5
3b. Customer attempt 5 times wrong credit card information
1. Payment Services prompt to page, as transaction cannot process.
Please call customer service department
2. Payment Services will notify sales staff that transection got cancelled
because maximum attempt exceeded
7a. If money cannot process on customer credit card
1. Payment Services will notify sales staff only that money credit back
to customer credit card
2. Sales staff will notify the customer
3. Customer will either call credit card company or give a different card
to process return transection
Priority: High
Notes and Issues: Payment Services is payment is a third party software act as actor
19
Use Case Name: Redeem coupon or Gift cards
Created By: Krunal, Tripti, Hemangm Last Updated By:
Actors: Payment Services

Description: This use case allows Payment Services on how to identify and redeem code
or gift cards. As soon as sales staff creates a promotion list they will send all
the coupon codes and gift card numbers to Payment Services with the date
information. Payment Services will make sure to enter those codes and gift
card numbers in the system and make it active during only those dates.
Incase if promo codes or gift card numbers is not working then Payment
Services will prompt guest to called website customer service
Trigger: As soon as sales staff send all the promo codes to the PayPal system
Preconditions: Promo codes and gift card numbers must be received by the Payment
Services
Postconditions: Promo codes and gift card numbers will be entered in Payment Services
system and activate automatically on assigned date. Also Payment Services
will calculate payment amount after deducting the coupon amount
Normal Flow: 1. Payment Services will receive public codes, private codes, and
restricted codes from sales staff
2. Payment Services will verify the promo codes date and make sure all
the codes are separated
3. Payment Services will enter all the codes and put trigger to active on
designated date
4. Payment Services will make sure that all codes needs to be active
before promotion starts
5. After enter all codes Payment Services will sent a notification to sales
staff that all the codes are entered (this email needs to be sent to
sales staff before that promotion starts)
6. When customer will enter that promo codes Payment Services
system will verify all the promo codes or gift card related
information
7. Payment Services system will verify promo code number, promo
code dates, compare with today dates, only one promo code use per
20
transaction and gift card numbers
8. In case of gift card, Payment Services will verify with number
9. Payment Services will calculate the amount after promo code
discount or gift card amount
10. Payment Services will prompt on screen total purchase amount after
promo code deduction
Alternative Flows: 7a. If promo code or gift card information cannot identify
1. Payment Services will prompt a message to customer that “Coupon
code errors. Please contact customer service”
2. Repeat step 7 to 10
Priority: High
Notes and Issues: Payment Services will be responsible only for identifying promo codes and
gift cards detail and whether it will apply or not. If promo codes or gift card
numbers were given wrong by sales staff then Payment Services will not be
responsible
Use Case Name: Authentication

Actors: None
Description: This use cases allows system to validate all information when sales staff,
marketing staff and customer is trying to interact with the system.
authentication use case work as a database that can validate all the
information on the back end when someone is trying to interact with the
system. System should validate everything on server side. The back end is
the right place to make validation. That way when hackers try to hack the
system database cannot validate rather then let him interact with the
system until the end. If there no validation stage then hackers can hack
customer personal information, system and website important information.
Validate user will check whether received information is valid and present
on valid recordset. If not then show an error and stop the further process
Trigger: As soon as anyone try to interact with the system
Include use cases Registration, Place order, check order status, return item, maintain account
21
information, set up promotion list, maintain product catalogue, send
promotional email, and process return
Preconditions: Information needs to be entered In order to validate
Postconditions: It will validate and either give access to interact with the system or stop the
process
Normal Flow: 1. Registration use case: When customer try to register first time
system will verify their entered information and make sure it is valid
or not
2. Place order use case: When customer try to place an order they
either registered or login to their account (place order use case)
3. System (Authentication database) will verify whether registering
account information is real or not
4. System will validate whether user is in valid recordset or not, every
timer when customer is login to their account
5. Check order use case: When customer try to check their order status
they need to login to their account
6. System will validate user once the password and ID match
7. System will also validate that no one had that same account open at
the same time
8. Return item use case: when customer wants to send request to
return their order they need to login
9. System will validate their account information
10. System will validate whether the return item has been delivered to
the guest or not
11. Maintain account information: in order to update or add account
information customer requires to login
12. System will validate account information
13. Every changed information will be recorded in database and validate
at the same time for security purpose, once customer choose option
“Done”
14. Setup promotion list use case: when marketing staff is trying to
interact with the system
15. Every final version of promotion list that has been approved by
marketing manager will be recorded and validate by having that date
16. Maintain product catalogue use case: when marketing staff will be
22
adding or deleting products or category
17. System will record all the updates of final version that has been
approved by marketing manager
18. System will store the updated version so technical team can access
when they need it
19. Send promotional email use case: when marketing staff send emails
to their customers
20. System will validate all the address that has been corrupt or expired
21. Process return use case: when sales staff is processing customer
return
22. System will validate customer account who had sent the return
request
Alternative Flows: Every time when system found suspicious activity or not able to validate the
information, system will display messages`indicate error message “ For
security reason we cannot process. Please contact customer service (This
will be standard for every use case. Technical team will resolve the problem
after discussing with sales staff and marketing staff)
Priority: High
Notes and Issues: This use case purpose is to secure customer and system precious
information
Use Case Name: Deliver items

Actors: Shipping company

Description: This use case allows shipping company how to ship item to the customer at
their designated location
Trigger: As soon as sales staff notify shipping company to pick up order from the
warehouse
Extends use cases Deliver gift items
Preconditions: Sales staff must notify shipping company that order is ready to pick up from
warehouse
Postconditions: Customer order will be delivered at designated location
23
Normal Flow: 1. Sales staff will send deliver request to shipping company
2. Shipping company will collect item from warehouse
3. (extension point: deliver gift items use case)
4. Shipping company assign the tracking number to the order and notify the
customer via account email address
5. Shipping company pack it the item and ship it out
6. Shipping company mark delivery complete
7. Shipping company notify customer and sales staff
8. Shipping company close the order
Alternative Flows: 5a. Fail to deliver items
1. Shipping company mark delivery fail since no one was there to pick
up package
2. Shipping company left a note at customer address
3. Shipping company make three attempts
4. If customer is not there to pick up then shipping company leaves a
note to pick it from shipping office
5. If some is there to take the delivery then follow steps 5 to 7
Priority: High
Notes and Issues: Shipping company will be responsible for any damage that happen during
shipping process
Use Case Name: Deliver gift items


Description: This use case allows shipping company how to process the gift items.
The shipping company will be responsible to deliver the messages from
sender. They may choose to pack it as a gift or wrap it per holiday season.
If customer had paid extra money for shipping then it needs to be done as
requested. It needs to delivered on time will be high priority
Trigger: When shipping company pick up the order from warehouse
Extends use cases Deliver items
24
Preconditions: Sales staff needs to attach details for delivering gift order
Postconditions: Gift item will delivered at designated address
Normal Flow: 1. Shipping company will pick up order from the warehouse
2. Shipping company will read the attached detail for delivering order as a
gift item
3. Shipping company will read the note attached to the order of customer
4. Shipping company will attached the note on coloring paper
5. Shipping company assigned tracking number and notify customer via
email. Shipping company will put high priority label
6. Shipping company will pack the order ship it out
7. Shipping company mark order as complete
8. Shipping company will notify customer and sales staff
9. Shipping company close the order
Alternative Flows: 4a. Customer request gift wrap
1. Shipping company will pack the gift and put nice wrapper paper on
top
2. Repeat step 5 to 9
5a. Fail to deliver items
1. Shipping company mark delivery fail since no one was there to pick
up package
2. Shipping company left a note at customer address
3. Shipping company make three attempts
4. If customer is not there to pick up then shipping company leaves a
note to pick it from shipping office
5. If some is there to take the delivery then follow steps 6 to 9
Priority: High
Notes and Issues: Shipping company will choose high priority to deliver gift items on time
Use Case Name: Collect return items


25
Description: This use case allows shipping company the process of collecting return
items. Many time sales staff generate free shipping label as complimentary
service. Customer will drop the item at shipping company office. Shipping
company will send the item to Fashion Inc. warehouse.
Trigger: When sales staff generate free shipping label
Preconditions: When sales staff generate free shipping label
Postconditions: Shipping company will deliver return item to Fashion Inc. warehouse
Normal Flow: 1. Shipping company will collect return item from customer at shipping
office location
2. Shipping company will inspect the label on box
3. Shipping company will assign tracking number and notify shipping
company and customer who is returning it
4. Shipping company will pack it and ship it out
5. Shipping company will deliver item to Fashion Inc. warehouse
6. Shipping will company will mark order complete
7. Shipping company will notify customer and Fashion Inc. sales staff
8. Shipping company will close the order
Alternative Flows: 2a. No packaging for return items
1. Incase of no packaging shipping company will offer customer to pack
the item or buy it from their store
2b. No label on return items
1. Shipping company will offer customer to buy shipping label or
request Fashion Inc. for free shipping label
Priority: High
Notes and Issues: Customer will be responsible to pay shipping cost if there was no free
shipping label give by sales staff
26
Women category list Lingerie Accessories
Clothing Top Brands
Sarees >
Kurta/Kurti
Handloom / Silk Sarees
Salwar Suits
Accessories
Lehengas
Ethnic Dress Watches
Dupatta Sunglasses
Ethnic Bottom Hair Accessories
Saree Blouse Scarves, Mufflers & Socks
Mobile Covers
Western Wear Belts
Dresses Caps
Tops & Tunics Umbrella
Jeans Towels
Trousers & Palazzos
Jeggings Handbags & Clutches
Leggings Sling
Sweaters & Sweatshirts Handbags
Jackets Utility Bags
Shirts Wallet & Clutches
T-Shirts Laptop Bags and Backpacks
Skirts
Ethnic Wear Shoes

Already given Boots
Lingerie & Nightwear Bellies
Bras Loafers
Panties Wedges
Bra & Panties set Peep Toes
Nightwear Sandals & Flats
Shapewear Stilettos & Heels
Bathrobes Flip Flops & Slippers
Camisoles Sports Shoes & Sneakers
Swimwear
Thermal wear Fashion Sandals
Erotic Lingerie Amazon Fashion
27
Fashion Sales & Deals
28

Final Version Cospact Use Cases Script

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Final Version Cospact Use Cases Script

Uploaded by

Copyright:

Available Formats

Fashion Inc.

Table of Contents for Fashion Inc. Use Case

Check order status 6

Maintain account information 8

Process out of stock order 10

Setup promotion list 13

Maintain product catalogue 14

Generate popular item report 16

Process credit card and refund 18

Redeem coupon or Gift cards 19

Deliver gift items 24

Collect return item 25

Actors: New Customer

Use Case Name: PLACE ORDER

Use Case Name: Check order status

Use Case Name: Return items

Alternative Flows: None

Use Case Name: Maintain account information

Use Case Name: Process order

Actors: Sales staff

Use Case Name: Process out of stock order

Actors: Sales staff

Use Case Name: Process return

Actors: Sales staff

Use Case Name: Setup promotion list

Actors: Marketing staff

Use Case Name: Maintain product catalogue

Actors: Marketing staff

Use Case Name: Generate popular item report

Use Case Name: Send promotional email

Actors: Marketing staff

Use Case Name: Process credit card or refund

Actors: Payment Services

Use Case Name: Authentication

Use Case Name: Deliver items

Actors: Shipping company

Use Case Name: Deliver gift items

Actors: Shipping company

Use Case Name: Collect return items

Actors: Shipping company

Ethnic Wear Shoes

You might also like