business requirement Document, High school final essays of Business

its ref guide of BRD & Use case

Typology: High school final essays

2021/2022

Uploaded on 07/20/2022

Lokeshu
Lokeshu 🇮🇳

1 document

1 / 74

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Revision History
Orion.com
January 2018
Version 1.00
Functional Requirement
Document
201
8
This Document describes the
Functionality of the Product. It describes
exactly what tasks the software must
preform and defines the scope of the
system, the product boundaries, and its
connections to adjacent systems
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe
pff
pf12
pf13
pf14
pf15
pf16
pf17
pf18
pf19
pf1a
pf1b
pf1c
pf1d
pf1e
pf1f
pf20
pf21
pf22
pf23
pf24
pf25
pf26
pf27
pf28
pf29
pf2a
pf2b
pf2c
pf2d
pf2e
pf2f
pf30
pf31
pf32
pf33
pf34
pf35
pf36
pf37
pf38
pf39
pf3a
pf3b
pf3c
pf3d
pf3e
pf3f
pf40
pf41
pf42
pf43
pf44
pf45
pf46
pf47
pf48
pf49
pf4a

Partial preview of the text

Download business requirement Document and more High school final essays Business in PDF only on Docsity!

Revision History

Orion.com January 2018 Version 1.

Functional Requirement

Document

201 8 This Document describes the Functionality of the Product. It describes exactly what tasks the software must preform and defines the scope of the system, the product boundaries, and its connections to adjacent systems

Orion .com is India’s online store providing massive collection on all the products at best prices. Table of Content

1. Introduction Online shopping is the process of buying goods and services from merchants who sell on the Internet. Since the emergence of the World Wide Web, merchants have sought to sell

Scope The scope of this document is to provide details about the different functionalities of the system. Background The demand for this system has originated from businesses focusing on products and services in which there is daily interaction with customers. A team of Business Analysts has been involved in the production of this document to meet the client expectations from such a product. Assumptions · Images of the products will be provided by the vendors. · Product description will be provided by vendors. · Terms and Conditions will be provided by legal team. · Return Policy will be provided by legal team. · Discount & Offers will be provided by the merchants. · News Letters and Emails will be provided by the marketing team. Constraints · Return Policy is subject to approval by legal team. · Design is subject to approval by UI team. · License is subject to approval by Government. Document Overview This document has been organised as a series of Use cases based on the workflow of an online shopping system.

2. Methodology The methodology used was to identify the user base, make a list of all their actions and put the actions in a flow consistent with the existing business process. 2. Functional Requirements a. Context The context below shows an image of the online shopping process.

Pre-condition • The customer must have a Mobile Number

  • The customer must have an Email ID Business Rules • The customer’s Mobile number & Email ID must not be previously registered.
  • The Password must have minimum 8 characters which must include at least - 1 Upper case, 1 Lower case, 1 Number & 1 Special Character. Trigger NA

Main Scenario Navigation - orion.com Homepage > Sign Up

  1. The customer must be able to register on the site.
  2. The user navigates to Homepage > Register > Registration Page opens.
  3. Once the registration page opens, the user will be displayed with 2 text fields: - Username - The User must choose his Email ID or Mobile number as the username - Password - In order to have a strong password strength following rules must be used: The password must have at minimum 8 characters. One or more of each of the following: 1. Upper Case Letter 2. Lower Case Letter 3. Number 4. Special Character
  4. Once the user enters the Mobile number, the system must send an OTP for verification.
  5. The OTP must be a 6 digit number sent by the system automatically when the OTP is requested.
  6. The customer has to enter the sent OTP and click on the “register” Button.
  7. Once the user clicks the Register Button, he will be navigated to the Login Page.
  8. Similarly, the system will send a verification link to the customer’s Email ID and then the customer must be able to click on the link to register.
  9. Once the User clicks on the link, user will be navigated to the Login page. Post condition The Customer will receive a notification upon successful registration via SMS and Email.

Req. ID Requirement Bus. Req. Prio rity

UR#S

at- isfied Use Case ID UC2- BR1.2.0_1.2.2 - Login System/Application Online shopping system - orion.com Goal Description User must be able to login to the system. Actors Customer Assumption • The system is up and available.

  • The servers are running. Pre-condition The customer must be registered on the website in order to login. Business Rules During the Login process, the User’s credentials must match. Trigger NA Main Scenario Navigation - Homepage > Login
  • User must first go to Login Page.
  • User must then enter the Mobile Number or Email ID and Password.
  • User must click on the Login Button.
  • The system must must validate all the credentials entered by the user: If correct - then the user must be logged in. If Incorrect - then user must see an error message. Post condition The user is either logged in or failed to log in and is appropriately notified.

Alternative Scenario The customer must be able to login with Facebook Account or Google Account Facebook:

  1. The user must enter its username
  2. The user must enter its password
  3. The user can now click on ‘Login’ button
  4. Once the user clicks ‘Login’ button, he can access his account Google+
  5. The user must enter its username
  6. The user must enter its password
  7. The user can now click on ‘Login’ button
  8. Once the user clicks ‘Login’ button, he is registered with ‘orion.com’ and can access his account Validations • The Customer must have valid credentials of the Email ID and password.
  • The Must have valid Facebook and Google Account Error Messaging If the User will not provide valid Mobile Number, the system will display “Please provide valid registered mobile number in order to login”

Alternative Scenario The user can set a New Password by clicking on “Forgot Password” Button.

  • The user must enter the registered Email ID
  • Once the user enters on Submit button, the system will send an link to the registered Email ID.
  • The user must click on the link and system redirects to “Set New Password”.
  • After setting the New Password, the user is taken to the Logon Page. Validations The user must provide valid Mobile Number or Email ID in order to set a new password in case the user forgets the password. Error Messaging • If the user will not provide valid Mobile Number the system will display “Please provide valid registered mobile number.
  • If the user will not provide valid Email ID the system will display “Please provide valid registered Email ID.

Req. ID Requirement Bus. Req. Prio rity

UR#S

at- isfied Use Case ID UC - 4 - BR1.5.0_1.5.4 - Search H 1.0,

System/Application Online shopping system - orion.com Goal Description To be able to search the products Actors Customer Assumption • The system is up available

  • The servers are running Pre-condition NA Business Rules Relevant products must be available whenever the user searches or browses for a product. Trigger NA Main Scenario Navigation - orion.com Homepage > Search
  • User searches product by products available on the Homepage or by entering ‘KEYWORD” on the search field.
  • System displays products list with all of the items with their prices and offer.
  • User clicks on any item link.
  • System displays “Item with its images and Product description”.
  • User must be able to see an “Add to Cart” link.
  • User must be able to enter Delivery Pincode to see expected time of delivery. Post condition • Product Screen will display items and corresponding list prices for a chosen product.
  • Item Screen displays detailed information about an individual item for sale, including a photo, if one is available.

Req. ID Requirement Bus. Req. Prio rity

UR#S

at- isfied Use Case ID UC - 5 - BR1.6.0_1.6. System/Application Online shopping system - orion.com Goal Description To display the product details. Actors Customer Assumption • The system is up and running.

  • The servers are running. Pre-condition The user must enter the product name accurately. Business Rules The system must display the following details of the product:
  • Price
  • Features
  • Merchant Name
  • Reviews Trigger NA

Main Scenario 1.The user enters the product he wants to buy or check out into the ‘Search’ box 2.The system displays the Thumbnail images of the product along with their price details 3.The user can now choose the relevant product and click on the image of the product 4.The system will display all the product details such as –

  • Delivery pin code – Once the user enters the delivery pin code, the system automatically checks whether the item is deliverable to that particular location or not. If ‘YES’ then the system accepts it and shows a ‘Green Tick’. If ‘NO’ then the system notifies the user that the product is not deliverable to that particular location.
  • Colour – The user can choose a colour if it is applicable for that particular product
  • Size – The user can choose size if it is applicable for that particular product.
  • Features – It will include: Colour of the item (if applicable) Wear: Casual / Formal (if applicable) Material: If applicable Images: From all the angles and which can be zoomed.
  • Seller - Merchant Post condition The system will display the product details and will navigate the user to:
  • To buy the Product or
  • Add to Cart or
  • Add to WishList Alternative Scenario None Validations The system must display relevant products with accurate details. Error Messaging If the Product is not available currently, then the system must display “Currently out of Stock” message.

Trigger NA

Main Scenario Navigation: Navigate to orion.com Homepage > Click on Cart Tab > Login with user credentials > Manage Cart Navigate to orion.com Homepage > Login with user credentials > Click on Cart Tab > Manage Cart Navigate to orion.com Homepage > Login with user credentials > Click on My Account Tab > WishList > Select a product > Add to cart > Manage Cart Process: Once the user has navigated to Homepage and Logged in and searched and selected his/her desired product he/she wants to buy he must be able to Add that product to CART. He must be be able to add as many quantity of that product unless specified by Vendor. User is allowed to edit his cart by clicking on Cart button & edit number of quantity. User must be able to delete the item(s) in cart by selecting a particular product & clicking on Delete button below the product in the cart. User must also be able to Move item(s) to wish-list by selecting a particular product and clicking on “ Save for later” link below the product in Cart. User must be able to go to Shop more Link which must be next to Proceed to Checkout button to go back to shipping online.