The Use cases of book shop

1. Fully DressedStyle
Admin Account
Use case 1:Login
Scope: Android App
Level: User Goal
Primary Actor: Admin
Stake holder and interest: Admin wants to login the account Very efficiently and fast
Pre-condition: Admin wants their login secure and Authenticated
Post-condition: Login is Authenticated and secure
Special Requirements: Performance Should be quick and High response
Attractive or user convenient interface
Technology and data variation list: Admin override entered by swiping an override login
information through password
Main Success Scenario: Admin wants to login their account insufficient and
effectively manner
Admin wants authorized account.Security must be preferable.
Then Enter their login Account
Frequency of concurrence: Must be nearly Continuous
Offstage Actor System
Supporting Actor Admin
Use Case 2:Registration
Scope: Android App
Level: User Goal
Primary Actor: Admin
Stake holder and interest: Admin wants to registered there self in this book shop App
Pre-condition: Admin wants to registered their self
Post-condition: Admin is registered
Special Requirements: Performance Should be quick and High response
Attractive or user convenient interface
Technology and data variation list: Registered account can have secure and authenticated.
Main Success Scenario: Admin wants to registered their account insufficient and
effectively manner
Admin wants authorized account.Security must be preferable.
Then Enter their login Account
Frequency of concurrence: Must be nearly Continuous
Offstage Actor System
Supporting Actor Admin
Use Case 3:Manage Categories
Scope: Android App
Level: User Goal
Primary Actor: Admin
Stake holder and interest: Admin manage all the categories that the customer want
Pre-condition: Admin wants Fulfill customers needs
Post-condition: Admin fulfill customer needs
Special Requirements: Performance Should be quick and High response
Attractive or user convenient interface
Technology and data variation list: When login the account all the categories is managed thorough
database

2. Main Success Scenario: Admin login there account all the categories must be managed
for the customer
Customer easily select the category and used it as they want.
Frequency of concurrence: Must be nearly Continuous
Offstage Actor System
Supporting Actor Admin
Use Case 4:Manage Products
Scope: Android App
Level: User Goal
Primary Actor: Admin
Stake holder and interest: Admin manage all the products that the customer want
Pre-condition: Admin wants Fulfill customers needs
Post-condition: Admin fulfill customer needs
Special Requirements: Performance Should be quick and High response
Attractive or user convenient interface
Technology and data variation list: When login the account all the products is managed thorough
database
Main Success Scenario: Admin login there account all the products must be managed
for the customer
Customer easily select the product and used it as they want.
Frequency of concurrence: Must be nearly Continuous
Offstage Actor System
Supporting Actor Admin
Use Case 5:Manage Orders
Scope: Android App
Level: User Goal
Primary Actor: Admin
Stake holder and interest: Admin manage all the orders that the customer said
Pre-condition: Admin wants Fulfill customers needs
Post-condition: Admin fulfill customer needs
Special Requirements: Performance Should be quick and High response
Attractive or user convenient interface
Technology and data variation list: When login the account all the order is managed thorough
database
Main Success Scenario: Admin login there account all the orders must be managed for
the customer
Admin easily select the order and used it as they want.
Frequency of concurrence: Must be nearly Continuous
Offstage Actor System
Supporting Actor Admin
Use Case 6:Manage Sale
Scope: Android App
Level: User Goal
Primary Actor: Admin

3. Stake holder and interest: Admin manage all the sales
Pre-condition: Admin wants Fulfill customers sale
Post-condition: Admin fulfill customer sale
Special Requirements: Performance Should be quick and High response
Attractive or user convenient interface
Technology and data variation list: When login the account all the sale is managed thorough
database
Main Success Scenario: Admin login there account all the sale must be managed for
the customer
Admin easily select the sale and used it as they want.
Frequency of concurrence: Must be nearly Continuous
Offstage Actor System
Supporting Actor Admin
Use Case 7:Manage Suppliers
Scope: Android App
Level: User Goal
Primary Actor: Admin
Stake holder and interest: Admin manage all the suppliers that they want
Pre-condition: Admin supplies all the suppliers as they want
Post-condition: Admin fulfill the suppliers
Special Requirements: Performance Should be quick and High response
Attractive or user convenient interface
Technology and data variation list: When login the account all the Suppliers is managed thorough
database
Main Success Scenario: Admin login there account all the suppliers must be managed
for the customer
Admin easily select the supplier and used it as they want.
Frequency of concurrence: Must be nearly Continuous
Offstage Actor System
Supporting Actor Admin
Use Case 8:Settings
Scope: Android App
Level: User Goal
Primary Actor: Admin
Stake holder and interest: Admin manage all the Settings
Pre-condition: Admin wants Fulfill their settings
Post-condition: Admin is fulfill their settings
Special Requirements: Performance Should be quick and High response
Attractive or user convenient interface
Technology and data variation list: When login the account all the Settings is managed Through
App
Main Success Scenario: Admin login there account all the Settings must be managed
for their self
Admin easily select the setting and change it as they want.
Frequency of concurrence: Must be nearly Continuous
Offstage Actor System
Supporting Actor Admin
Use Case 9: Logout

4. Scope: Android App
Level: User Goal
Primary Actor: Admin
Stake holder and interest: Admin wants to logout there account very efficiently and fast
Pre-condition: Admin wants their logout in secure and Authenticated form
Post-condition: Logout is Authenticated and secure
Special Requirements: Performance Should be quick and High response
Attractive or user convenient interface
Technology and data variation list: Admin override entered by swiping an override logout
information through password
Main Success Scenario: Admin wants to logout their account insufficient and
effectively manner
Admin wants authorized account.Security must be preferable.
Then Logout their Account
Frequency of concurrence: Must be nearly Continuous
Offstage Actor System
Supporting Actor Admin
CustomerAccount
Use Case 1:Login
Scope: Android App
Level: User Goal
Primary Actor: Customer
Stake holder and interest: Customer wants to login there account very efficiently and
fast
Pre-condition: Customer wants their login secure and Authenticated
Post-condition: Login is Authenticated and secure
Special Requirements: Performance Should be quick and High response
Attractive or user convenient interface
Technology and data variation list: Customer override entered by swiping an override login
information through password
Main Success Scenario: Customer wants to login their account insufficient and
effectively manner
Customer wants authorized account. Security must be
preferable.
Then Enter their login Account
Frequency of concurrence: Must be nearly Continuous
Offstage Actor System
Supporting Actor User
Use Case 2:Browse Products
Scope: Android App
Level: User Goal
Primary Actor: Customer
Stake holder and interest: Customer wants to Browse their products well mannered and
fast
Pre-condition: Customer wants to Browse their product in secure and
Authenticated

5. Post-condition: Browse product is Authenticated and secure
Special Requirements: Performance Should be quick and High response
Attractive or user convenient interface
Technology and data variation list: When login the account all the products is managed thorough
database
Main Success Scenario: Customer wants to Browse the products insufficient and
effectively manner
When customer Browse the products it used feasible options.
Browse product is successfully done.
Frequency of concurrence: Must be nearly Continuous
Offstage Actor System
Supporting Actor User
Use Case 3:SearchProducts
Scope: Android App
Level: User Goal
Primary Actor: Customer
Stake holder and interest: Customer wants to Search their products well mannered and
fast
Pre-condition: Customer wants to Search their product in secure and
Authenticated
Post-condition: Search product is Authenticated and secure
Special Requirements: Performance Should be quick and High response
Attractive or user convenient interface
Technology and data variation list: When login the account all the products is managed thorough
database
Main Success Scenario: Customer wants to Search the products insufficient and
effectively manner
When customer Search the products it used feasible options.
Search product is successfully done.
Frequency of concurrence: Must be nearly Continuous
Offstage Actor System
Supporting Actor User
Use Case 4:SelectProducts
Scope: Android App
Level: User Goal
Primary Actor: Customer
Stake holder and interest: Customer wants to Select their products well mannered and
fast
Pre-condition: Customer wants to Select their product in secure and
Authenticated
Post-condition: Select product is Authenticated and secure
Special Requirements: Performance Should be quick and High response
Attractive or user convenient interface
Technology and data variation list: When login the account all the products is managed thorough
database
Main Success Scenario: Customer wants to Select the products insufficient and
effectively manner
When customer Select the products it used feasible options.

6. Select product is successfully done.
Frequency of concurrence: Must be nearly Continuous
Offstage Actor System
Supporting Actor User
Use Case 5:Add to Cart
Scope: Android App
Level: User Goal
Primary Actor: Customer
Stake holder and interest: Customer wants to Add to cart their products.
Pre-condition: Customer wants to Add to Cart their product in secure and
Authenticated
Post-condition: Add to cart product is Authenticated and secure
Special Requirements: Performance Should be quick and High response
Attractive or user convenient interface
Technology and data variation list: When login the account all the products is managed thorough
database
Main Success Scenario: Customer wants to Add to cart the products insufficient and
effectively manner
When customer Add to cart the products it used feasible
options.
Product is successfully done.
Frequency of concurrence: Must be nearly Continuous
Offstage Actor System
Supporting Actor User
Use Case 6:View Cart
Scope: Android App
Level: User Goal
Primary Actor: Customer
Stake holder and interest: Customer wants to View their cart .
Pre-condition: Customer wants to View their cart in secure and
Authenticated
Post-condition: Customer view cart is Authenticated and secure
Special Requirements: Performance Should be quick and High response
Attractive or user convenient interface
Technology and data variation list: When login the account all the carts that customer sold is
managed through database
Main Success Scenario: Customer wants to View their cart insufficient and
effectively manner
When customer view their it used feasible options.
Customer view cart is successfully done.
Frequency of concurrence: Must be nearly Continuous
Offstage Actor System
Supporting Actor User
Use Case 7:Place Order

7. Scope: Android App
Level: User Goal
Primary Actor: Customer
Stake holder and interest: Customer wants to Place their order in well mannered and
fast
Pre-condition: Customer wants to Place their order in secure and
Authenticated
Post-condition: Place order is Authenticated and secure
Special Requirements: Performance Should be quick and High response
Attractive or user convenient interface
Technology and data variation list: When login the account all the Order is managed thorough
database
Main Success Scenario: Customer wants to Place their order insufficient and
effectively manner
When customer place their order it also see it
Place order is successfully done.
Frequency of concurrence: Must be nearly Continuous
Offstage Actor System
Supporting Actor User
Use Case 8:CashPay
Scope: Android App
Level: User Goal
Primary Actor: Customer
Stake holder and interest: Customer wants to Cash their payment on delivery well
mannered and
fast
Pre-condition: Customer wants to Cash their payment on delivery in secure
and Authenticated
Post-condition: Cash payment on delivery is Authenticated and secure
Special Requirements: Performance Should be quick and High response
Attractive or user convenient interface
Technology and data variation list: When login the account all the Payment is managed thorough
database
Main Success Scenario: Customer wants to Cash their payment on delivery
insufficient and effectively manner
When customer Cash their payment on delivery it used
feasible options.
Cash their payment on delivery is successfully done.
Frequency of concurrence: Must be nearly Continuous
Offstage Actor System
Supporting Actor User
Use Case 9:Confirm Order
Scope: Android App
Level: User Goal
Primary Actor: Customer
Stake holder and interest: Customer wants to Confirm their order well mannered and
fast
Pre-condition: Customer wants to Confirm their order in secure and
Authenticated
Post-condition: Confirm order is Authenticated and secure
Special Requirements: Performance Should be quick and High response

8. Attractive or user convenient interface
Technology and data variation list: When login the account all the order is managed thorough
database
Main Success Scenario: Customer wants to Confirm their order insufficient and
effectively manner
When customer Confirm their order it also see it
Confirm Order is successfully done.
Frequency of concurrence: Must be nearly Continuous
Offstage Actor System
Supporting Actor
Use Case 10:Order Details
Scope: Android App
Level: User Goal
Primary Actor: Customer
Stake holder and interest: Customer wants to see order details well mannered and
fast
Pre-condition: Customer wants to see order details in secure and
Authenticated
Post-condition: Order detail is Authenticated and secure
Special Requirements: Performance Should be quick and High response
Attractive or user convenient interface
Technology and data variation list: When login the account all the order detail is managed
thorough database
Main Success Scenario: Customer wants to see their order details insufficient and
effectively manner
When customer Select the products it used feasible options.
Select product is successfully done.
Frequency of concurrence: Must be nearly Continuous
Offstage Actor System
Supporting Actor User
Use Case 11:Profile Setup
Scope: Android App
Level: User Goal
Primary Actor: Customer
Stake holder and interest: Customer manage all the Settings
Pre-condition: Customer wants Fulfill their settings
Post-condition: Customer is fulfill their settings
Special Requirements: Performance Should be quick and High response
Attractive or user convenient interface
Technology and data variation list: When login the account all the Settings is managed Through
App
Main Success Scenario: Customer login there account all the Settings must be
managed for their self
When customer Confirm their order it also see it.
Frequency of concurrence: Must be nearly Continuous
Offstage Actor System
Supporting Actor User

9. Use Case 12: Logout
Scope: Android App
Level: User Goal
Primary Actor: Customer
Stake holder and interest: Customer wants to logout there account very efficiently and
fast.
Pre-condition: Customer wants their logout in secure and Authenticated form.
Post-condition: Logout is Authenticated and secure.
Special Requirements: Performance Should be quick and High response.
Attractive or user convenient interface.
Technology and data variation list: Customer override entered by swiping an override logout
information through password.
Main Success Scenario: Customer wants to logout their account insufficient and
effectively manner.
Customer wants authorized account. Security must be
preferable.
Then Logout their Account.
Frequency of concurrence: Must be nearly Continuous.
Offstage Actor System
Supporting Actor User