EW0-0002 E-commerce

  

         

User Requirement Document

(Version 1.0.0)

Revision History

Date	Version	Description	Author	Reviewer
Nov 27, 2023	1.0	Initial Version.	Krishnaa

Introduction

Objective

Create a e-commerce website which can handle multiple stores sales and its product.

Scope of work

1. Rules:My Profile - My Transaction

2. Products - Keyword Search
3. Products - Sorting / Pagination, Based on Brand
4. Checkout - Promo code ( For Admin to maintain)
5.  Checkout - Billing Details   ( Need more clarification)
6. Checkout - Delivery Details, Lala Move Integration.
   
7. Checkout – Payment Methods ( Need to test only)
8. Checkout – Payment Methods ( Need to test only)
9.  Email & SMS Notification ( Need to test only)
10. Blog
11. Postcode - Based on the postcode shoe the available Store.
12.  Contact Us - Must able to upload images for refund.
13. Admin End 
    1.  User Module - Manage User Roles 
    2.  User Module - Manage User Registration
    3.  User Module - Change password
    4.  User Module - Forget password
    5.  Manage Products – Categories
    6. Manage Products – Brand (A, B, C etc)
    7.  Manage Products – Products [Product Bulk Upload]
    8.  Manage Products – Product Options 
    9. Manage Products – Frequently Bought Together (Products)
    10.  Manage Products – Rating & Reviews
    11.  Manage Products – Contact us
    12. Video for product
    13.  Manage Customers – Customers
    14.  Manage Customers – Customers Groups
    15. System Setup - Zones (Pincode Based Availability)
    16. System Setup - Countries
    17.  System Setup – States
    18. System Setup – Store Setup
14. Store Management
    1. Multiple store Features -Manage Products
    2. Multiple store Features -Manage Stock
    3. Multiple store Features -Manage Orders
    4. Multiple store Features - Frequently Bought Together(Products)

Out Of Scope

1. Library asProducts a- separateQuick module,View
accessible
2. Product byView all- usersProduct (exceptZoom parents, we may look into having "assigned document" sectionOption for parentsProduct andImage learnerson in future)
3. There will only be one Library. Within the Library, there are sub-libraries (My Library, Account Library, Assigned Documents)
4. Materials can be duplicated from My Library to Account Library, but not the other way around. 
5. Only materials from Account Library can be imported into Active Curriculum
6. Changes made in materials in My Library will not be reflected after materials are duplicated into Account Library, likewise, changes made in Active Curriculum will not be reflected after materials are duplicated into Active Curriculum (this may change in future where we provide option to allow overwrite of the material)
7. In the case when learners have attempted the experios in Active Curriculum, no changes should be allowed in Active Curriculum. When cases such as this happens, educators need to be informed when attempting to edit Active Curriculum. (in future, we may look into allowing educators to have the option to set it as private, and learners to be able to attempt after it is made public. this is to allow educators to edit in active curriculum first, if they need to after duplicating it from Account Library)Hover
8.  

   PermissionDesigns needs- to be given by institution to directly buy to My LIbrary (unless user is registered under BeEDpublic organisation aka independent users, then permission to automatically allow purchase into My Library, while disabling Account Library access)

   Pages
9. Designs

   Note:- (ForBanners

now)
10. Designs Experio- builderEmail usesTemplates
LMS
11. System experioSetup builder– (leavePayment fieldSetup
empty,
12. Multiple removestore dataFeatures from- field)
    Related Products
13. Frond End Manager

Reference

Document Title	Version No	Location
TOGAF	10.0

Assumptions

• BeEDSMS or watsapp/Email cost is excluded
• Payment Gateway cost is excluded Max 2 Payment Gateway. Anything more will be considerd as theextra only contributorwork.
• EducatorsThe whoreports creatingor experio.requirements that was not mentioned in this document will be consider as Extra work.
  
• LeanerIndividual whoRequirment usesdesign will be developed once the experio.
project
• BeEDis Publicsigned user who uses the experio.off.
  

Software Design Specification

Flow Chart

Data Architecture

Application Architect

1. Create two table in Beed_Nexus Database in MYSQL
   1. tbl_ampiteater_teacher_todelete
   2. tbl_ampiteater_request

tbl_ampiteater_teacher_todelete
SNO	Field	Data Type	Example
1	SNO	INT	PRIMARY
2	TeacherID	INT	Generated from GENERIC TABLE
3	TeacherName	VARCHAR(75)
4	TeacherEmailD	VARCHAR(100)
5	TeacherURL	TEXT	Image URL from S3
6	TeacherDesc	TEXT
7	CreatedID	VARCHAR(45)
8	CreatedTM	TIMESTAMP

Definitions & Acronyms

• SDD – Software Design Document
• S3 – Object Storage
• HA – High availability

Application Architect & Acceptance Criteria

Approval For Gate

Date	Version	Name	Title	Sign-Off
Nov 23, 2023	1.0	Initial Version.	Krishnaa

Appendix A