Software Requirements & Specification Assignment 2, Summaries of Software Project Management

Several use cases related to a website for shipping orders, including canceling orders, viewing products, booking products, logging out, and managing customers. Each use case includes a description, actors involved, preconditions, post conditions, normal flow, alternative flows, and exceptions. likely part of a software engineering or computer science course related to requirements gathering and specification.

Typology: Summaries

2020/2021

Available from 01/28/2022

MuazAshraf
MuazAshraf 🇵🇰

5 documents

1 / 15

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Software requirements& Specification
Assignment 2
Group Members
Muhammad Muaz Ashraf (70067005)
Mian Hamza Ali (70067004)
Ghulam Mustafa Hafeez (7006999)
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe
pff

Partial preview of the text

Download Software Requirements & Specification Assignment 2 and more Summaries Software Project Management in PDF only on Docsity!

Software requirements& Specification

Assignment 2

Group Members

Muhammad Muaz Ashraf (70067005)

Mian Hamza Ali (70067004)

Ghulam Mustafa Hafeez (7006999)

Exceptions: CNIC Number already registered Ask the user to login or recover password re-enter password do not match Ask the user to retype passwords Use Case ID: 2 Use Case Name: Login Date Created: March 25, 2021 Actors: Customer, Admin Description: A user login to system to access the functionality of the system User will login using username, password Preconditions: 1. system must be connected to network

  1. the user is given their account detail to access the system Post conditions: 1. after a successful login a notification mail is sent to user mail id
  2. user can access the site Normal Flow: Customer System
  3. customer will enter user name and password 2.System will verify it is password and user name registered and is information is right if information wrong it asked user to check and re-enter
  4. if info wrong user re-write it and enter
  5. system verify it and allow user to access site Exceptions: User account is not created by system Administrator

Use Case ID: 3 Use Case Name: Cancel order Date Created: March 25, 2021 Actors: Customer, Admin Description: In this use case user can cancel his order if it is unopened. And he return it within 30 days or applicable according to policy Preconditions: 1. Order is must place before cancellation Post conditions: 1. it will show order cancellation confirmation message and remove order from cart. Normal Flow: Customer System

  1. customer select cancel order option
  2. System check that order which user want to cancel and show display cancel order screen to user
  3. customer will select cancel order
    1. if order has not shipped system cancel it and update user cart if it placed it check is it unopen and cancel it

Exceptions: Some unauthorized want to access. Use Case ID: 5 Use Case Name: Book Product Date Created: March 25, Actors: Customer Description: Customer will select one of the product from the products available and then add this product to cart. Preconditions: 3.Customer should have login into the website. Post conditions: 1. System must have added the product to the cart so it will be delivered. Normal Flow: Customer System

  1. System will show the available products
  2. Customer will select one of the product and fill the required conditions to deliver.
  3. System will verify the details entered and then add to

the delivery/shipping log. Alternative Flows: Exceptions: The product might not be available. The details might not match like payment method invalid The credit card details failed. Use Case ID: 6 Use Case Name: Feedback Date Created: March 25, Actors: Customer Description: Customer will give feedback after receiving the ordered product through their account so that we will able to improve the flaws of our system or product. When he login the feedback form will be shown and they will have option to fill or skip. Preconditions: 1. Customer should have login into the website.

  1. Customer should have received the Ordered product. Post conditions: 1. The given feedback should be saved to the database and the reviews and rating should be shown to other customer for the product. Normal Flow: Customer System
  2. Customer will enter the feedback form and submit.
  3. The system then save the provided feedback and show it to the admin of the system.
  1. System will verify the details entered and then the transaction will be done. 4.The system should save the information of transaction for the future process if needed. Alternative Flows: Exceptions: The details might be wrong entered so the transaction will be denied. The amount might be insufficient and the transaction will be denied. Use Case ID: 8 Use Case Name: Log Out Date Created: March 25, Actors: Customer, Admin Description: The users will select the logout icon on the screen and the system prompt a message for confirmation and the user press the ok message and gets logout of the system. Preconditions: 1. The users should be login first. Post conditions: 1. System must logout and users will not be able to see the home screen and no process can be done afterwards Normal Flow: Customer, Admin System
  2. They select the logout icon on the screen.
  3. The system should stop process if any and gets logout the user.
  1. System will not allow user to do processing until gets login first. Alternative Flows: Exceptions: Use Case ID: 9 Use Case Name: Add and update items Date Created: March 25, 2021 Actors: Admin Description: Admin will be responsible to add and update items to the cart list. He can add new product or change the details of the current products. Preconditions: 1. The admin must login the account.
  2. Also he should have rights to do so. Post conditions: 1. System must have add and update items after the admin accessed to perform and then the customer must be able to see that. Normal Flow: Admin System
  3. The admin select the add/ update tab.
  4. System will ask add or update the items.
  5. Admin will then enter the details of the items add or
  1. Admin will check the history of customer
  2. System will verify whether customer cancelled an order or not.
  3. System will add customers Exceptions: You are now the customer. waiting for your response for an order. Use Case ID: 11 Use Case Name: Shipping order Date Created: March 25, 2021 Actors: Admin Description: In this the admin can manage the shipping orders placed by the customer he can track the shipping details and maintain the process of shipping. Preconditions: 3. Customer must have placed order.
  4. Admin should login before this. Post conditions: 1. Admin will able to see the order details of the shipping orders. Normal Flow: Admin System
  1. System will show the shipping orders.
  2. Admin will maintain the orders of the customer.
  3. Admin will select customer order and check the status of the orders.
  4. Orders will be add to the system and wait for the delivery date. Exceptions: Dear customer your Order is placed thank you! You can cancel your order. You can replace your order until 7 days of dispatch. . Use Case ID: 12 Use Case Name: Add/ cancel shelf for suppliers Date Created: March 25, 2021 Actors: Admin Description: Here Admin will decide to add shelfs for the suppliers or not. Here suppliers can sale item using website. Preconditions: 3. He must have his account on site
  5. He’s login into his account Post conditions: 2. He can open the product and check the history of suppliers and