‘E-Commerce Project

(SRS)
Introduction

 Tata CLiQ (stylised as Tata CLiQ) is an Indian e-commerce company based in Mumbai, India.[2] It is
owned by Tata Unistore Limited of Tata Group.[3] Tata CLiQ operates in categories such
as Fashion, Footwear, and Accessories. Tata Group's E-commerce platform, Tata CLiQ, also
launched a premium and luxury fashion and lifestyle destination, Tata CLiQ Luxury, and it houses
a wide range of apparel and accessories for men and women by luxury and bridge-to-luxury brands.
 Also known as electronic commerce or internet commerce, is an activity of buying and selling goods
or services over the internet or open networks.
 The purpose of an e-commerce website is to facilitate online transactions between buyers and sellers.
 E-commerce brings convenience for customers as they do not have to leave home and only need to
browse websites online, especially for buying products which are not findable otherwise in the retail
world.
 E-commerce allows customers to overcome geographical barriers and allows them to purchase
products anytime and from anywhere.
 E-commerce has become one of the most popular methods of making money online and an attractive
opportunity for investors.
 Overall, an e-commerce website is a platform that enables businesses to sell products or services
online and allows customers to purchase them electronically using the internet, providing
convenience and accessibility to both buyers and sellers.

Purpose
 The purpose of an e-commerce website is to facilitate online transactions between buyers and sellers.
 Tata CLiQ—a platform from a Tata Group business venture, Tata Unistore—was launched in 2016
as an online marketplace for brand-loving consumers.
  The marketplace connects customers with over 1,200 local and international brands across categories
including fashion, electronics, and footwear.
 An e-commerce website supplants the need for a home office and allows a business to function almost
entirely online.
 The purpose of an e-commerce website is to facilitate the buying and selling process for both the
business and the customer.
 Overall, the purpose of an e-commerce website is to provide a convenient and efficient way for
businesses to sell products or services and for customers to purchase them online.
Scope
 The scope of work for an e-commerce website defines the project purpose, deliverables, and major
known risks and constraints.
 The potential for e-commerce development is enormous. Now a days one can buy products online
through some sites like Flipkart and Amazon. In the age of e-commerce everything from gym
equipment to laptops are available online. E-Commerce is a super set of business cases. It includes
E-trading, E-Franchising, E-Mailing, E-Engineering etc. Scope of e-commerce can be enumerated as
follows:

Exchange of digitized information

 Technology-enabled
 Customers retention
 Accounting
 Supplier integration
 Support the exchange

Finally, the future scope of an e-commerce website is vast, as it allows online businesses to widen the circle
of their customers both nationally and internationally.

Contribute to the design of software products and web applications

PC 1 . check your understanding of the Business Requirement Specification / User Requirement
Specification with appropriate people.

Module of e-commerce website

 Modern e-commerce stores require a feature-rich set of components to provide customers with the
best possible shopping experience. The traditional e-commerce architecture tightly couples all these
services into a single system. Combining all parts of the e-commerce system into a single platform
like this limits what you are able to get out of each service. It is also difficult to scale.
 Modular commerce divides the backend components into individual modules. Each is responsible for
a single service. Breaking each area of functionality out into its own module provides more
flexibility. It cleans up the codebase and makes it easier to deploy new features.

Some of the most common e-commerce modules include:

 Cart and checkout

 Product information management
 Order management
 Pricing and promotions engines
 Personalization engines
 Content management
 Analytics
 SEO tools

 Introduction
  General description
 Functional Requirements
 Interface Requirements
 Performance Requirements
 Design Constraints
 Non-Functional Attributes
 Preliminary Schedule and Budget
 Appendices
 Uses of SRS document
 FAQs on SRS Format
 Conclusion

Introduction

Purpose of this Document – At first, main aim of why this document is necessary and what’s purpose of
document is explained and described.
Scope of this document – In this, overall working and main objective of document and what value it will
provide to customer is described and explained. It also includes a description of development cost and
time required.
Overview – In this, description of product is explained. It’s simply summary or overall review of product.

General description

 In this, general functions of product which includes objective of user, a user characteristic, features,
benefits, about why its importance is mentioned.
 It also describes features of user community.

Functional Requirements

 In this, possible outcome of software system which includes effects due to operation of program is
fully explained.
  All functional requirements which may include calculations, data processing, etc. are placed in a
ranked order.
 Functional requirements specify the expected behavior of the system-which outputs should be
produced from the given inputs.
 They describe the relationship between the input and output of the system. For each functional
requirement, detailed description all the data inputs and their source, the units of measure, and the
range of valid inputs must be specified.

Interface Requirements

 In this, software interfaces which mean how software program communicates with each other or
users either in form of any language, code, or message are fully described and explained.
 Examples can be shared memory, data streams, etc.

Performance Requirements
 In this, how a software system performs desired functions under specific condition is explained. It
also explains required time, required memory, maximum error rate, etc.
 The performance requirements part of an SRS specifies the performance constraints on the software
system. All the requirements relating to the performance characteristics of the system must be
clearly specified.
 There are two types of performance requirements: static and dynamic. Static requirements are those
that do not impose constraint on the execution characteristics of the system. Dynamic requirements
specify constraints on the execution behaviour of the system.

Design Constraints

 In this, constraints which simply means limitation or restriction are specified and explained for
design team.
 Examples may include use of a particular algorithm, hardware and software limitations, etc.
  There are a number of factors in the client’s environment that may restrict the choices of a designer
leading to design constraints such factors include standards that must be followed resource limits,
operating environment, reliability and security requirements and policies that may

 an impact on the design of the system. An SRS should identify and specify all such constraints.

Non-Functional Attributes
 In this, non-functional attributes are explained that are required by software system for better
performance.
 An example may include Security, Portability, Reliability, Reusability, Application compatibility,
Data integrity, Scalability capacity, etc.

Preliminary Schedule and Budget

 In this, initial version and budget of project plan are explained which include overall time duration
required and overall cost required for development of project.
Appendices
 In this, additional information like references from where information is gathered, definitions of
some specific terms, acronyms, abbreviations, etc. are given and explained.
Uses of SRS document
 Development team require it for developing product according to the need.
 Test plans are generated by testing group based on the describe external behviour.
 Maintenance&support staff need it to understand what the software product is supposed to do.
 Project manager base their plans and estimates of schedule, effort and resources on it.
 customer rely on it to know that product they can expect.
 As a contract between developer and customer.

PC 3. Check Your Understanding of High Level Design (HLD) with appropriate people.

HLD (High Level Design )

  What is High-Level Design Document?
 Components of High-Level Design
 Purpose of High-Level Design
 Characteristics of High-Level Design
 How HLD is different from LLD
 How To Design Scalable High-level Design (HLD) Systems

Module

What is High-Level Design Document?

 HLD document consists of data flows, flowcharts, and data structures to help developers in
understanding and implement how the current system is being designed intentionally to function.

Components of High-Level Design

 For providing a bird’s eye view of the entire solution, HLD should be possessing 2 elements as
follows:
 Attributes and features of software entities.
 Relationships between different software entities (components, modules, classes, etc)

Purpose of High-Level Design

 The purpose of this High-Level Design (HLD) is to add the necessary detailed description to
represent a suitable model.
 This is designed to help with operational requirements and can be used as a reference manual for
how the modules interact.

 Basically, HLD is a technical representation of functional requirements and the flow of information
across assets or components.
Characteristics of High-Level Design
 A diagram representing each design aspect is included in the All Design HLD (which is based on
business requirements and anticipated results).

 Description of hardware, software interfaces, and also user interfaces.

 The workflow of the user’s typical process is detailed, along with performance specifications.
 The project’s architecture and design are contained in Users HLD.

Functionalities

functionality of cart and checkout model

 The cart module can also use other modules to show the order summary and any promotional codes
that have been applied to the customer order
 The checkout page of an e-Commerce website presents a step-by-step flow that customers follow to
enter all the information that is required to place an order.

functionality of product information management

 Product Information Management tools provide a centralized hub that allows you to control all your
product information.
 In other words, it simplifies the process of creating, using, and updating product specifications and
feature descriptions that bind to product catalogues online as well as offline.
functionality of order management
 This process is called order management, which is basically keeping track of customers' orders and
handling the steps involved with fulfilling them.
 The process generally consists of accepting the order; picking, packing, and shipping the items
mentioned in the order; and finally tracking them until they get delivered.
functionality of pricing &promotion engines
 Retailers need to streamline and simplify every aspect of their promotions. But the rules governing the
promotions are often complex, limiting marketing efforts and risking customer loyalty in the
process.
  the Price & Promotion Engine solutions on AWS help retailers apply the correct pricing and
promotions to the items in the customers' cart, all within seconds. These solutions consider the
context of the transactions and determine how to best apply promotions to a cart of products.

Functionality of personalization engines.

 A personalization engine is a tool used by businesses to collect and analyze customer behavior and
data to create a customized user experience -- including special offers, product recommendations and
automated marketing efforts -- in an e-commerce setting
 . Digital marketing teams use personalization engines because they increase lead conversion rates,
improve marketing campaigns and optimize customer satisfaction, thereby improving business
results.

functionality of content management.

 A content management system (CMS) is a software application that enables users to create, edit,
collaborate on, publish and store digital content.

7.functionality of SEO tools

 I define an SEO tool as any software you can use to improve some aspect of a search engine
optimization campaign.
 These tools can serve many different functions, including search query analytics, reporting
automation, AI-driven content optimization recommendations, and website performance analysis.

Components of Functionality

1.cart and checkout components

 Header
 My Cart
 Saved for Later.
2.product information components.
 Quality Content. While having lots of content in a PIM software is important, more often it's the
quality of the content that makes a real difference. ...
 Content Targeting. ...
 Content Accessibility. ...
 Content Governance.

3.order management components

 The first step involves the correct order entry.

 Next, the data is processed and sent to relevant stations.
 Before the order gets placed, customer data needs to be verified.
 Once the customer information is qualified, the billing and invoice are issued.

4 pricing and promotion components

 Cost base pricing
 Value based pricing
 Competitive pricing
 Sales promotion
 Social media marketing

5 SEO tools components

 Rank tracking
 Backlink analysis
 Competitor analysis
 Technical SEO tools

Use Case Diagram

 1 Cart and checkout use case

2 PRODUCT INFORMATION USE CASE.

3 ORDER MANAGEMENT USE CASE.
4 PRINCIPAL AND PROMOTIONUSE CASE .
5 CUSTOMER ACCOUNT MANAGEMENT USE CASE.
6. SEO TOOL MANAGEMENT USE CASE
Class diagram of modules