Scribd
Upload
20 views3 pages

E Commerce

Uploaded by

avneetvalotra
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
20 views3 pages

E Commerce

Uploaded by

avneetvalotra
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

1.

Feasibility Study:
- Assessing the technical, operational, economic, and schedule feasibility of the
ecommerce project.
- Analyzing the market demand and potential for the proposed ecommerce platform.
- Evaluating the available resources, including technology, finances, and human capital.
- Identifying potential risks and challenges that may impact the success of the project.
- Considering regulatory and legal requirements, such as data privacy and consumer
protection laws.
- Generating a feasibility report outlining the findings and recommendations

Requirement Gathering & Analysis:*


- Conducting stakeholder interviews to understand the needs and expectations of various
parties involved, including customers, vendors, and internal teams.
- Documenting functional requirements, such as user roles, product catalog management,
shopping cart functionality, checkout process, payment gateway integration, and order
management.
- Identifying non-functional requirements, including performance, scalability, security, and
usability criteria.
- Prioritizing requirements based on their importance and impact on the project's success.
- Creating requirement specifications documents detailing the agreed-upon features and
functionalities of the ecommerce platform.

Advantages:*
1. Established User Base: An existing system likely already has a customer base, which can
provide immediate revenue and feedback.
2. Tested Features: The features and functionalities of the existing system have been tested
and refined over time.
3. Brand Recognition: The existing system may have established brand recognition, which
can lead to increased trust and credibility among users.
4. Existing Infrastructure: The infrastructure, including servers, databases, and security
measures, is already in place and operational.

• *Disadvantages:*
1. Legacy Technology: The existing system may be built on outdated technology, making it
difficult to implement new features and adapt to changing market trends.
2. Limited Customization: It may be challenging to customize or extend the functionality of
the existing system to meet specific business requirements.
3. Technical Debt: Accumulated technical debt, such as poorly written code or outdated
dependencies, may hinder system performance and scalability.

5. Security Vulnerabilities: Over time, security vulnerabilities may arise in the existing
system, posing risks to user data and system integrity.
1. System Requirement Specification:*

The System Requirement Specification (SRS) document outlines the detailed requirements of
the proposed ecommerce system. Here's an overview of what it typically includes:

• *Introduction:* An overview of the project, its objectives, and scope.


• *Functional Requirements:* Detailed descriptions of the system's functionalities, including
user roles, product management, shopping cart, checkout process, payment integration,
order management, etc.
• *Non-Functional Requirements:* Specifications for performance, scalability, security,
usability, and other quality attributes.
• *External Interfaces:* Descriptions of interfaces with other systems, such as payment
gateways, shipping providers, and third-party APIs.
• *Constraints:* Any constraints or limitations that need to be considered during
development.
• *Assumptions:* Assumptions made during the requirements gathering process.

Flow chart Diagram.

You might also like