0% found this document useful (0 votes)
44 views30 pages

Group 8 Final

Statistic
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
44 views30 pages

Group 8 Final

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

Developing an

Online Sales
Website for a
Clothing Store
By group 8
TABLE OF CONTENT

01 Introduction 06 Resources Management

02 Project Overview 07 Risk Management

03 Methodology 08 Project assessments

04 Project Plan
09 Conclusion

05 Project Management
INTRODUCTION
E-commerce is booming globally, especially in Vietnam's
fashion sector, where consumers are increasingly
choosing the convenience of online shopping. Fashion is
one of the most popular categories purchased online.
This project aims to create a modern, user-friendly e-
commerce website for a clothing store, enhancing its
digital presence and offering a seamless shopping
experience to meet the growing demands of online
shoppers.
WHAT ARE THE PROBLEMS OUR PROJECT SEEKS TO ADDRESS?

Reasons for
implementing the
project Problem Solving
Background
Objectives
As more consumers turn to
Nowadays, e-commerce, online shopping, having a well-
particularly in fashion, is crafted website is essential for Design a High-Performance
thriving globally and in businesses to expand their Sales Platform
Vietnam due to its reach and build long-term Enhance Customer
convenience and appealing customer loyalty. Experience & Optimize
offers. Operations
Small and medium-sized Offer Scalable, User-Friendly
businesses face challenges in Solutions
building and maintaining
effective e-commerce
websites
PROPOSED IT PROJECT

Address problem
The project addresses a fashion store
chain's online presence by creating a
platform for convenient shopping and
brand interaction, boosting sales and
engagement.

Current state The objectives of the project


The project utilizes e-commerce The objective is to create a user-
expertise to help fashion SMEs friendly online sales website with
improve digital transformation essential tools, secure payments,
and expand customer reach. and responsive design to boost
sales and digital presence.
METHEDOLOGY

Method for Overview of How Technical Project


Selecting the The Proposal Will Approach Constraints
System Be Implemented
METHOD FOR SELECTING THE
SYSTEM
We choose Waterfall Method

The project requirements are well-


defined and unlikely to change
significantly.

Waterfall provides a strong It aligns well with our


focus on planning and project's timeline, which has
documentation, ensuring fixed milestones and
clarity and reliability. deliverables.

With Waterfall, we ensure a systematic, phase-by-phase


progression that minimizes risks and sets a clear path for success.
OVERVIEW OF HOW THE PROPOSAL WILL BE
IMPLEMENTED

Phase 1 . Planning Phase 2. Design


We document detailed requirements,
We focus on creating UI/UX mockups,
create the SOW (Statement of Work), and
database schema, and technical designs. All
design the system architecture. This sets a
designs are reviewed and approved before
solid foundation for the project.
moving forward

WATERFALL
MODEL

Phase 4. Testing and


Phase 3. Development
Deployment
The actual coding and system integration
We rigorously test the system for
occur in this phase. Frontend and
functionality, performance, and security
backend components are built based on
before deploying it into the production
the designs, ensuring compatibility.
environment

The implementation process under the Waterfall model is broken into four distinct phases
System Architecture Design
●Customer Use Cases ● Admin Use Cases
ERD and Wiframe
Prototype

Prototype helps test, adjust and optimize the interface, features and user experience
before building a complete clothing sales website, ensuring that the final product
meets the needs of users and customers.
1 Frontend Development
HTML, CSS, and JavaScript (or React.js for interactivity).

2 Backend Development
Node.js for scalable server-side operations.

3 Database
TECHNICAL MySQL for structured and secure data storage.
APPROACH

4 Hosting and Deployment


AWS services like SES for email service and S3 for image
url storage

5 Security
Integration of SSL/TLS encryption, secure authentication
protocols, and vulnerability scanning during the testing phase.
PROJECT CONSTRAINTS
By addressing these constraints from the start, we ensure a realistic and achievable plan for project
success

The architecture must support All resources, including


modularity for easy feature technologies and manpower,
expansion and high-traffic must stay within the allocated
handling. budget.

System Architecture Budget Constraints

Critical Milestones

Phase 1 Completion: December 14, 2024


Phase 2 Completion: December 28, 2024
Phase 3 Completion: January 11, 2025
Phase 4 Completion: February 10, 2025
Objective: Develop an online fashion retail website for a fashion store
1
● Design user interface (UI) and user experience (UX)

2
● Develop backend and frontend

Scope: Develop an online 3


● Integrate online payment system
fashion retail website for a
fashion store
4
● Manage products, orders, and customers

5
● Basic SEO and marketing
DETAILED PROJECT PLAN

Phase 1: Planning Phase 2: Phase 3: Phase 4: Testing


and Preparation Design Development and Deployment

Create SOW Design user Perform functional


Develop frontend
document (4 days) interface (UI) (4 testing (7 days)
components (5
Analyze customer days) Conduct
days)
requirements (3 days) Design user performance
Develop backend
Design system experience (UX) (4 testing (7 days)
services (5 days)
architecture (5 days) days) Perform security
Integrate core
Choose technologies Design database testing (7 days)
features (3 days)
(2 days) schema (3 days) Deploy to
Integrate online
Set up development Build mockups (3 production
payment system
environment (3 days) days) environment (9
(3 days)
Plan testing (3 days) Develop prototype days)
(3 days)
DEPENDENCY MAPPING

Phase 1: Planning Phase 2: Phase 3: Phase 4: Testing


and Preparation Design Development and Deployment

Analyze customer Design user interface


Create SOW document Integrate core
requirements -> (UI), Develop
-> Analyze customer features, Integrate
Design user interface prototype -> Develop
requirements online payment system
(UI) frontend components
Analyze customer -> Perform functional
Analyze customer Design system
requirements -> Design testing
requirements -> architecture, Design
system architecture Perform functional
Design user database schema ->
Analyze customer testing -> Conduct
experience (UX) Develop backend
requirements -> Choose performance testing
Design system services
technologies Perform functional
architecture -> Design Develop frontend
Choose technologies -> testing -> Perform
database schema components, Develop
Set up a development security testing
Design user interface backend services ->
environment Conduct performance
(UI) -> Build mockups Integrate core features
Design system testing, Perform
Design user Develop backend
architecture -> Plan security testing ->
experience (UX), Build services, Integrate
testing Deploy to the
mockups -> Develop core features ->
production
prototype Integrate online
environment
payment system
Visualizing

Gantt chart
Visualizing

Kanban Board Assignee over task Status over task Issue type over the task
PROJECT MANAGEMENT

WORK BREAKDOWN
STRUCTURE (WBS)

JIRA
COMMUNICATIONS PLAN
RESOURCES MANAGEMENT
PROJECT TEAM,
ROLES,
RESPONSIBILITIES

RACI STANDS FOR:


R : THE PERSON WHO CARRIES OUT
THE TASK.
A : THE PERSON ULTIMATELY
RESPONSIBLE FOR THE OUTCOME.
C: THE PERSON CONSULTED FOR
INPUT OR SUPPORT.
I: THE PERSON WHO NEEDS TO BE
KEPT INFORMED ABOUT PROGRESS
OR RESULTS.
RISK
MANAGEMENT
1 Limited Customer Reach
Relying solely on traditional stores limits potential customer base.

2 High Operating Costs


Rent, staff salaries, and warehousing reduce profit margins.
Database
ASSESSMENT OF
EXISTING SYSTEM
3 Inventory & Order Management Issues
Leads to errors and poor customer experience.

4
Lack of Customer Insights
Makes strategy development challenging.
ASSESSMENT OF ALTERNATIVE PROPOSALS

USING E-COMMERCE PLATFORMS COMBINING ONLINE & OFFLINE

Advantages: Low costs, large customer Advantages: High competition, platform


base. dependency.
Disadvantages: High competition, platform Disadvantages: Requires investment and
dependency. complex management.
01 02
1 Stable Internet Connection
The website needs a stable internet connection to operate effectively.

2 Secure and Convenient Online Payment System

Database
Ensures information security and transactions for customers.
ASSUMPTIONS USED
IN THE IT PROJECT
PROPOSAL 3 Professional Website Management Team
A team with expertise in online marketing, website administration,
order processing, and customer service is needed

4 Initial Investment and Operating Costs


A budget needs to be allocated for website design,
development, maintenance, marketing, etc.
CONCLUSION
As the development team, we are committed to building a
high-performing online sales platform for the clothing
store. Utilizing the Waterfall method, we have crafted a
structured plan to ensure each phase, from planning to
deployment, is meticulously executed.

Leveraging modern technologies like Node.js, MySQL, and


AWS, the platform is designed for scalability, security, and
exceptional user experience. By optimizing resources and
meeting deadlines, we aim to deliver a user-friendly and
visually engaging website that fulfills business goals and
exceeds customer expectations.
THANKS FOR
LISTENING

You might also like