Tribhuvan University

Institute of Science and Technology (IoST)

Project report on
“STYLISTA”
Clothing and Makeup Ecommerce Website

Submitted To:
National College of Computer Studies
Department of Bachelor of Science in Computer Science and Information Technology
([Link])

In partial fulfillment of the requirement for the degree of Bachelor of Science in Computer
Science and Information Technology ([Link])

Submitted By:
Ayusha Adhikari (28864/078)
Bipasna Dulal (28866/078)
Riya Shrestha (28886/078)
Yunika Shrestha (28899/078)

Submission Date: 2025/08/25

 ACKNOWLEDGEMENT

We would like to extend our heartfelt thanks and gratitude to our supervisor, Mr. Anup Raj
Poudel, for granting us the valuable opportunity to work on “STYLISTA- E-commerce
Website for Clothing and Makeup” project. His insightful guidance and support have greatly
contributed to the success of this project, allowing us to explore new tools and technologies.
Our sincere appreciation goes to NCCS College for their constant supervision, guidance, and
the necessary resources provided, which played a crucial role in the completion of this project.
The support from the library and staff members of NCCS has been invaluable, and we are
grateful for their cooperation and encouragement. Here, we would like to show an attitude of
reverence to all of them who have contributed directly or indirectly to making the study a
reality.
Finally, we shall be grateful to those people who read this project and who shall benefit from
this project at present and in future.

Yours sincerely,
Ayusha Adhikari
Bipasna Dulal
Riya Shrestha
Yunika Shrestha

i
 ABSTRACT

STYLISTA is an e-commerce platform dedicated to fashion and women’s makeup, designed

to offer a stylish and online shopping experience. Built with a clean interface, it ensures
seamless browsing and purchasing across devices. The platform provides essential e-
commerce functionalities such as user registration and authentication, product catalog with
detailed descriptions, “add to favorites” and “add to cart” options. With its focus on usability,
STYLISTA aims to redefine online shopping by delivering a fashionable and convenient
digital destination for modern consumers.

ii
 Table of Contents
ACKNOWLEDGEMENT ..................................................................................................... i

ABSTRACT ........................................................................................................................... ii

CHAPTER 1: INTRODUCTION ........................................................................................ 1

1.1 Introduction .................................................................................................................. 1

1.2 Problem Statement ....................................................................................................... 1

1.3 Objectives ..................................................................................................................... 2

1.4 Scope and Limitation ................................................................................................... 2

CHAPTER 2: BACKGROUND STUDY AND LITERATURE REVIEW ..................... 3

2.1 Background Study ......................................................................................................... 3

2.2 Literature Review .......................................................................................................... 4

CHAPTER 3: PROJECT MANAGEMENT ACTIVITITES ........................................... 5

3.1 Functional requirements ................................................................................................ 5

3.2 Project schedule management ....................................................................................... 6

3.2.1 Project activity planning......................................................................................... 6

3.2.2 Scheduling .............................................................................................................. 9

3.2.3 Resource allocation .............................................................................................. 11

3.3 Cost benefit analysis.................................................................................................... 14

3.3.1 Net Present Value ................................................................................................. 15

3.3.2 ROI and Payback Period ...................................................................................... 15

3.3.3 Internal Rate of Return ......................................................................................... 16

3.4 Earned Value Analysis ................................................................................................ 18

3.5. Risk Analysis.............................................................................................................. 21

3.5.1. Risk Identification ............................................................................................... 21

 3.5.2. Risk Analysis Process ......................................................................................... 22

3.6 QA Activity ................................................................................................................. 25

3.6.1. Test Cases for Unit Testing ................................................................................. 25

3.6.2. Test Cases for Integration Testing ...................................................................... 27

3.6.3. Test Cases for System Testing ........................................................................... 28

CHAPTER 4: CONCLUSION ........................................................................................... 29

REFERENCES .................................................................................................................... 31
 LIST OF ABBREVIATIONS
ACWP – Actual Cost of Work Progress
BCWP – Budget Cost of Work Performance
BCWS - Budget Cost of Work Schedule
CBA – Cost Benefit Analysis
CPI – Cost Performance Index
CPM – Critical Path Method
CSS – Cascading Style Sheet
CV – Cost Variance
EVA - Earned Value Analysis
HTML – Hypertext Markup Language
IRR – Internal Rate of Return
NPV – Net Present Value
PHP – Hypertext Preprocessor
ROI – Return On Investment
SPI – Schedule Performance Index
SV – Schedule Variance

iii
 LIST OF FIGURES
Figure 1 Use Case Diagram of Stylistaa ................................................................................... 5
Figure 2 WBS of Stylistaa ........................................................................................................ 7
Figure 3 WBS using MS Project ............................................................................................... 7
Figure 4 Calculating Estimated Time ....................................................................................... 8
Figure 5 CPM Network Diagram .............................................................................................. 9
Figure 6 Ball Chart.................................................................................................................. 10
Figure 7 Gantt Chart ............................................................................................................... 11
Figure 8 Resources used for project........................................................................................ 13
Figure 9 Resource Allocation ................................................................................................. 14
Figure 10 Cost Benefit Analysis ............................................................................................. 16
Figure 11 Risk Exposure Analysis for Stylista E-commerce Website in MS Excel .............. 24
Figure 12 Risk Exposure analysis visualization in column chart ........................................... 24

iv
 LIST OF TABLES
Table 1: Unit testing 1............................................................................................................. 26
Table 2: Unit Testing 2 ........................................................................................................... 26
Table 3: Integration Testing 1 ................................................................................................. 28

v
 CHAPTER 1: INTRODUCTION
1.1 Introduction
STYLISTA is an e-commerce platform dedicated to fashion and beauty enthusiasts. Our
website offers a curated selection of clothing and makeup products, ensuring a seamless
shopping experience for users looking to elevate their style. At STYLISTA, customers can
explore a wide variety of trendy apparel as well as makeup products, including lipsticks,
foundations, and skincare essentials.

It allows users to easily browse products, view detailed descriptions, select product varieties
(like sizes and colors), and make secure purchases. STYLISTA also includes features like user
registration, favorites, shopping cart, and smooth checkout options to enhance convenience.

1.2 Problem Statement

In today’s fast-paced digital world, consumers face challenges when shopping for fashion and
beauty products online. Existing platforms often lack personalized experience, product variety,
or clear information about size, color, and quality, making it difficult for users to make
informed choices. Additionally, managing multiple product selections and completing secure
transactions can be cumbersome on traditional e-commerce sites.

STYLISTA aims to solve these problems by providing a platform where customers can easily
browse, compare, and purchase a wide range of clothing and makeup products. By integrating
intuitive navigation, detailed product information, and secure payment. STYLISTA ensures an
efficient, enjoyable, and reliable online shopping experience for fashion and beauty
enthusiasts. By prioritizing variety our platform enhances the online shopping experience,
making fashion and beauty more accessible and enjoyable.

1
1.3 Objectives

The main objective of STYLISTA includes:

• To provide clear product descriptions, pricing, and available variations to assist users
in making informed decisions.

• To improve the shopping experience with a fast, user-friendly design.

• Allow users to save their favorite items, “add to cart” and make online payments for
easy future access and purchases.

1.4 Scope and Limitation

The scope of the STYLISTA site includes:
• STYLISTA makes buying clothes and makeup online simple and easy.
• Provide a diverse collection of clothing and makeup products, ensuring a wide
selection for different styles, preferences, and budgets.
• Focus on enhancing customer management and improving the overall user
experience.
• Implement a secure login and registration system, allowing users to manage their
profiles.
• Focus on making shopping personal and enjoyable.
Some limitations of the STYLISTA site might include:

• Tools for managing orders, including order tracking and shipping information are not
available.
• Ensuring the website is accessible and functional across various devices (desktops,
tablets, and smartphones).
• There may not be implementation of a contact form and FAQ section.
• Users cannot try on clothes or makeup virtually before making a purchase.
• Product information will be simple and may not include all technical details.

2
 CHAPTER 2: BACKGROUND STUDY
AND LITERATURE REVIEW

2.1 Background Study

STYLISTA is an e-commerce platform made to give users a simple and smooth online
shopping experience. It allows people to browse products, add them to a cart, and buy them
easily from their phones or computers. The platform has a clean and user-friendly design
that makes it easy for anyone to use, whether they are shopping online for the first time or
regularly.
With STYLISTA, users can create accounts, view product details, and place orders without
any confusion. The website helps users find what they need quickly and safely. It also includes
features like order history and a simple checkout process. From a technological perspective,
STYLISTA is developed using HTML, CSS, and JavaScript for the frontend, ensuring an
interactive and responsive user interface. The backend is powered by PHP, enabling dynamic
content generation, form handling, and server-side logic. MySQL is used for managing the
database, where user accounts, product information, cart details, and orders are securely stored
and retrieved.

Study of existing system

In our research of current online fashion and beauty shopping platforms, we looked at
Sephora and Shopify as references while planning the development of Stylista. These
platforms are popular and widely used for their extensive product selections, user-friendly
designs, and smooth shopping experiences. Sephora and Shopify are successful because
they make it easy for users to browse products, compare options, add items to the cart, and
place orders efficiently. They also offer features such as product reviews, ratings, order
tracking, personalized recommendations, and secure payment options. Their clean design,
smart search functionality, and responsive performance help users shop with ease. Both
platforms also support mobile applications, allowing users to shop conveniently on
smartphones or tablets. The simplicity and effectiveness of Sephora and Zalora guided the

3
design and development of Stylista. Our aim is to provide a similarly smooth and engaging
shopping experience, with intuitive navigation, secure checkout, and helpful features—so
that anyone, regardless of technical skills, can explore fashion and beauty products online
comfortably.

2.2 Literature Review

E-commerce has transformed how consumers purchase fashion and beauty products,
providing opportunities for personalized shopping experiences. Laudon and Traver (2020)
describe e-commerce as the use of the internet and web technologies to conduct business
transactions. They explain that e-commerce platforms allow users to browse products, make
payments, and access services through digital interfaces. The study highlights that growth
in mobile device usage and improved internet connectivity have driven the expansion of e-
commerce globally. The authors also emphasize that customer trust, secure payment
systems, and easy-to-use website interfaces are crucial for successful online businesses. [1]

Chong et al. (2016) investigated factors influencing customer satisfaction and loyalty in
online shopping environments. Their research shows that website quality, fast delivery, and
reliable customer service significantly affect repeat purchases. They also stress the
importance of personalization in enhancing user experience, such as suggesting products
based on past behavior or preferences. Additionally, customer reviews and ratings play a
critical role in purchasing decisions, highlighting the need for transparency and trust on e-
commerce platforms. [2]

Gefen, Karahanna, and Straub (2003) explored the role of trust in e-commerce adoption.
Their study indicates that trust is essential because online transactions involve inherent
uncertainty and risk, unlike traditional in-person shopping. Key factors such as website
design, clear communication, privacy policies, and secure payment gateways contribute to
building consumer trust. Without trust, even well-designed platforms may fail to retain
users. [3]

4
 CHAPTER 3: PROJECT MANAGEMENT ACTIVITITES

3.1 Functional requirements

The "STYLISTA" system must fulfill the following functional requirements to provide
comprehensive and effective e-commerce experience:
• User registration and login: Users should be able to create an account and log in using
their email and password to access their profile, order history, and make purchases.
• Product Browsing: Users should be able to browse all available products.
• Product Details Page: Users should be able to click on a product to view detailed
information, including name, price, description, and images.
• Shopping Cart System: Users should be able to add products to their cart, update
quantities, and remove items.
• Checkout and Payment Process: Users should be able to place an order by
providing delivery information and choosing a payment method.

Figure 1 Use Case Diagram of Stylista

5
ID: 101
Actors: User
Description:
The use case diagram of STYLISTA represents the primary interactions between users and
the e-commerce system. It outlines the core functionalities such as user registration, login,
product browsing, cart management, order placement, and logout. By visually representing
these use cases, the diagram ensures clarity in understanding user-system interactions and helps
guide the system’s development. It provides a solid foundation for identifying system
requirements, improving user experience, and ensuring that all essential features are
implemented accurately and efficiently.

3.2 Project schedule management

Project schedule management is the process of developing a project schedule, defining
activities, sequencing them, estimating durations, and allocating resources to create a timeline
for completing the project. It also involves monitoring and controlling the schedule to track
progress, manage changes, and ensure the project is delivered on time.

3.2.1 Project activity planning

A project plan is a list of activities showing when each task starts and ends. Planning and
scheduling a project means carefully organizing tasks and deciding the right order to complete
them.
[Link] Work Breakdown Structure

Work Breakdown Structure is the process of breaking engineering project into sub-project,
task, subtasks, work-packages and so on. When the software project management is able to
break a given set of tasks recursively into small activities it is WBS in project management.

6
 Figure 2 WBS of Stylistaa

Figure 3 WBS using MS Project

7
[Link] PERT

Program Evaluation and Review Technique (PERT) is a graphical technique used to show
project activities and key milestones on a timeline. PERT uses a network diagram to represent
the tasks and their dependencies, and estimates the time required to complete each task. PERT
uses three-time estimates for each task: the optimistic time, the most likely time, and the
pessimistic time. The optimistic time is the best-case scenario for completing the task, the
pessimistic time is the worst-case scenario, and the most likely time is the most realistic
estimate. Using these time estimates, PERT calculates the expected time for each task using
the formula:

Expected Time = (Optimistic Time + 4 * Most Likely Time + Pessimistic Time) / 6

Figure 4 Calculating Estimated Time

[Link] Critical Path Method

CPM (Critical Path Method) is a project management technique used to determine the critical
path of a project, which is the sequence of tasks that must be completed on time in order for
the project to finish as scheduled. The critical path is the longest chain of activities that directly
affects the project duration. Any delay in these activities will cause a delay in the entire project.
CPM focuses on identifying the most important tasks in the timeline, understanding task
dependencies, and calculating their duration. In the Stylista project, the critical path is Planning
followed by Design, Implementation, Testing, and Documentation.

8
The critical path of the project is:

Planning → Design → Implementation → Testing → Documentation

Planning takes 8 days → Design takes 11 days → Implementation takes 20 days → Testing
takes 8 days → Documentation takes 5 days → giving a total project duration of 52 days.

Figure 5 CPM Network Diagram

3.2.2 Scheduling

Project scheduling is the process of defining, organizing, and assigning timeframes to project
activities so that the entire project can be completed within the planned deadline. It is the
process of planning when project tasks will start and finish. It organizes activities in the right
sequence to meet deadlines. Resource such as people, time, and budget are allocated to each
task. Overall, it creates a clear timeline to guide project execution.

[Link] Ball Chart

Ball Chart are used to show whether the targets have been met or not. It provides even more
striking way of showing whether or not the targets have been met. Circles indicate the start
date and completion date. Whenever revision are made, the revised date is put to the circle.
The color of circle is changed to green when the event actually takes place and changed to red
if it has missed the target.

9
Figure 6 Ball Chart

10
[Link] Gantt Chart

A Gantt Chart is graphical representation of project activities in time-scaled bar line with no
link in between. It is the simple and the oldest form of representing the progress of the project.
Gantt chart can be defined as the horizontal bar chart which is used in project management to
visually represent the project plan over time. It is the graphical representation of the project
activities that aids in monitoring the progress of the project.

Figure 7 Gantt Chart

3.2.3 Resource allocation

Resources are anything you need to complete a project, including teams, equipment, raw
materials and so on. These are called the resource requirements.
Resource allocation is the process of scheduling resources such as labor, materials or
equipment to complete tasks. Organizations need resources to carry out the processes they
operate normally and to execute operational and strategic projects to achieve specific goals.
Good resource allocation isn’t just a one-time activity. It requires constant monitoring and
adjustments throughout the entire project. Priorities may change, new risks may appear, and
unexpected challenges may occur, so resources need to be shifted accordingly. The main goal
is to balance competing needs and make the most out of limited resources, ensuring the best
possible return on investment.
In the case of Stylista’s e-commerce project, the resources required can be grouped into four
main categories:
1. People

Team members are the most important resource of any project. They’re the ones responsible
for executing tasks, solving problems, and ensuring progress. Even with the best tools and
biggest budget, a project cannot succeed without the right people in place.
For Stylista, this includes developers, designers, testers, content creators, and project managers
11
who will bring the platform to life.

2. Information

Information is the knowledge and data the team needs to complete the project. Without
proper information, the team would be working blindly. Some of this knowledge comes from
experience (such as knowing how to use tools or follow company processes), while some of
it is project-specific and can change quickly.
For Stylista, important information includes customer data (like names, addresses, and
contact details), product details (sizes, colors, and attributes), wishlists, and order history.
This ensures that the shopping platform delivers a personalized and seamless experience for
users.

3. Materials

Material resources are the physical and digital assets required to carry out the project. These
can be tools, hardware, software, or even office supplies. Some may already be available within
the organization, while others might need to be purchased or leased.
For Stylista, this includes laptops, servers, software licenses, testing tools, and workspace
essentials.

4. Financial Resources

Every project runs on a budget, and financial resources ensure that the required people and
materials can be managed properly. This covers salaries, equipment costs, software
subscriptions, office expenses, and even marketing or product distribution costs. For Stylista,
careful budget planning will be needed to balance development expenses with business growth
goals.

12
Figure 8 Resources used for project

13
 Figure 9 Resource Allocation

3.3 Cost benefit analysis

Cost Benefit Analysis (CBA) is a method used to assess the costs and benefits of a proposed
project, helping to identify the most cost-effective option. It allows comparison between
different alternatives by evaluating their expected costs and returns, and then making decisions
accordingly. Techniques such as Net Present Value (NPV), Internal Rate of Return (IRR), and
Benefit-Cost Ratio (BCR) are commonly applied in this analysis. For our project, we will be
using the Net Present Value (NPV) method. To perform the CBA, we must first estimate the
development costs and the potential benefits of the project. These costs may include:
• Direct Cost
• Indirect Cost
• Intangible Cost
• Potential Risk
14
The advantages of using Cost Benefit Analysis are given below:
• Supports better decision making
• Provides clearer understanding of project objectives
• Strengthens project planning and management

3.3.1 Net Present Value

Net Present Value (NPV) is a financial metric used to determine the difference between the
value of cash flow and value of cash at future date. It is the difference between the present
value of cash inflows and the present value of cash outflows. To calculate NPV, we need to
estimate the timing and amount of future cash flows and pick a discount rate equal to the
minimum acceptable rate of return.

The formula for the calculation of the Net Present Value (NPV) is:
𝑛
𝐶𝑎𝑠ℎ 𝐹𝑙𝑜𝑤𝑖
𝑁𝑃𝑉 = ∑ − 𝐼𝑛𝑖𝑡𝑖𝑎𝑙 𝐼𝑛𝑣𝑒𝑠𝑡𝑚𝑒𝑛𝑡
(1 + 𝑟)𝑡
𝑖=0

Where, r = discount rate of interest

t = Number of time periods

3.3.2 ROI and Payback Period

Return on Investment (ROI) is a financial ratio used to measure the profitability of an

investment. It is typically calculated as a percentage by dividing the net profit of an investment
by the cost of the investment. The higher the ROI, the more profitable the investment. The
formula for ROI is:
𝑁𝑒𝑡 𝑝𝑟𝑜𝑓𝑖𝑡
𝑅𝑂𝐼 = ∗ 100%
𝐼𝑛𝑖𝑡𝑖𝑎𝑙 𝐼𝑛𝑣𝑒𝑠𝑡𝑚𝑒𝑛𝑡
Payback period can be defined as the amount of time required to recover the cost of an
investment through its cash flow. It can be calculated by dividing the initial investment cost by
the average annual cashflows generated by the investment. The payback period can be
calculated as:
15
 𝐶𝑢𝑚𝑢𝑙𝑎𝑡𝑖𝑣𝑒 𝐶𝑎𝑠ℎ 𝐹𝑙𝑜𝑤 𝑂𝑓 𝑝𝑟𝑒𝑣𝑖𝑜𝑢𝑠 𝑌𝑒𝑎𝑟
𝑃𝑎𝑦𝑏𝑎𝑐𝑘 𝑃𝑒𝑟𝑖𝑜𝑑 = 𝑝𝑟𝑒𝑣𝑖𝑜𝑢𝑠 𝑦𝑒𝑎𝑟 +
𝐶𝑎𝑠ℎ 𝐹𝑙𝑜𝑤 𝑜𝑓 𝐶𝑢𝑟𝑟𝑒𝑛𝑡 𝑌𝑒𝑎𝑟

3.3.3 Internal Rate of Return

Internal Rate of Return (IRR) is the rate at which the NPV of the investment cashflows equals
zero. The higher the IRR the more profitable the investment or project. The formula for IRR is
given as:
𝑛
𝐶𝑡
𝑁𝑃𝑉 = ∑ =0
(1 + 𝐼𝑅𝑅)𝑡
𝑡=0

For the cost benefit analysis of our project, the initial investment be Rs 70,000 at the discount
rate of 10%, expecting to generate the net cash flow of Rs. 28899, Rs. 28886, Rs. 28866, and
Rs. 28864 in the next 4 years.

Figure 10 Cost Benefit Analysis

16
So, if discount rate is 10%, the project is worth the investment. Hence, our project group can
undertake the project because NPV>0. Along with NPV, the net profit is found to be Rs. 45515,
Average Annual Profit is found to be Rs. 11378.75, ROI is found to be 65.02%, and Discounted
ROI is found to be 30.78%. Similarly, the payback period is 2.22 years and total benefit with
10% discount is Rs. 91546.49. Finally, the Benefit Cost Ratio (BCR) is 1.307. Hence, BCR>1,
so our project is feasible.

17
 3.4 Earned Value Analysis

Earned Value Analysis (EVA) is a project management technique used to measure project
performance and progress in terms of scope, schedule, and cost. It compares the planned
progress with the actual progress to determine if the project is on track.
Key metrics:
• BCWS / PV (Planned Value): Budgeted cost for scheduled work.
• BCWP / EV (Earned Value): Budgeted cost for actual work completed.
• ACWP / AC (Actual Cost): Actual cost incurred for completed work.
• CPI = EV / AC: Cost performance index.
• SPI = EV / PV: Schedule performance index.
• CV = EV − AC: Cost variance.
• SV = EV − PV: Schedule variance.

Figure 11 WBS of cost of resources

18
 Figure 12 Earned Value Analysis

Observations
Schedule Variance (SV)
• Tasks 1–3: SV = 0 → Project was on schedule.
• Task 4: SV = –1242.5 → Project started falling behind schedule.
• Task 5: SV = 0 → Project caught up briefly.
• Task 6: SV = –245.60 → Minor delay.
• Task 7: SV = –139.06 → Small delay.
• Task 8: SV ≈ –370.28 → Moderate delay.
• Task 9: SV = –141.84 → Slight delay.
Result: The project initially stayed on track, but experienced increasing schedule delays
starting from Task 4, particularly during development and testing phases. Later tasks showed
smaller but consistent delays.
Schedule Performance Index (SPI)
• Tasks 1–3: SPI = 1.0 → Work was completed as planned.
• Task 4: SPI = 0.5 → Only 50% of planned work completed → moderate delay.
• Task 5: SPI = 1.0 → Work completed on schedule.
• Task 6: SPI = 0.25 → Significant slowdown in progress.

19
• Task 7: SPI = 0.5 → Partial recovery.
• Task 8: SPI ≈ 0.64 → Improvement in schedule efficiency.
• Task 9: SPI = 0.15 → Severe slowdown at the final stage.
Result: Schedule efficiency fluctuated, with notable drops in Tasks 4, 6, and 9, reflecting
intermittent delays and partial recoveries.
Cost Variance (CV)
• Tasks 1–9: CV = 0 → Actual Cost of Work Performed (ACWP) = Earned Value (EV).
Result: No cost overrun or underrun was recorded. Cost tracking appears consistent but may
not reflect real variations due to missing or unrecorded cost data.
Cost Performance Index (CPI)
• Tasks 1–9: CPI = 1.0 → Cost efficiency was on budget throughout.
Result: Costs were well controlled during the project. There were no inefficiencies, but SV
and SPI indicate that schedule issues were not caused by cost overruns.

20
 3.5. Risk Analysis
Risk is an expectation of loss, a potential problem that may or may not occur in the future. It
is generally caused due to lack of information, control or time. A possibility of suffering from
loss in software development process is called a software risk.
Loss can be anything, increase in production cost, development of poor quality software, not
being able to complete the project on time etc.
Software risk exists because the future is uncertain and there are many known and unknown
things that cannot be incorporated in the project plan.
So, Risk Management is required in the project. Risk management is the process of doing risk
analysis, it involves identifying and grading risks or threats and opportunities. It is also the
process of deciding how to respond (if at all).
3.5.1. Risk Identification
The Risk Identification part of the Risk Management process deals with finding out what are
the potential threats to a project. These risks could be towards the organization, software
developers or the project itself. Some of the risks that are found as part of the identification
process include employees falling sick, bugs in the software, data breaches and not adhering
to development schedules.

Techniques for Risk Identification

• Brainstorming

A group of stakeholders from different departments or disciplines identifies potential risks. It

can be an effective tool for generating creative and innovative ideas, and it can help to foster
collaboration and teamwork among project team members.
• Root Cause Analysis

A systematic approach to identifying the underlying causes of risks. It involves investigating

the factors contributing to a particular risk event to identify the root cause and develop effective
risk mitigation strategies.
• SWOT Analysis

SWOT Analysis represents the organization's strengths, weaknesses, opportunities, and

21
threats. It is a structured approach that can help to identify internal and external factors that
can affect the success of an initiative.
• Expert Judgment

Consulting with experts who have experience with similar projects or in relevant fields. The
experts can provide insights and recommendations on the technical feasibility, cost-
effectiveness, and other factors related to the project.
Types of Risk
1. Project Risk: Risks related to delays or issues in project completion, such as failure to meet
development timelines, incomplete features, or resource shortages during website
development.
2. Budget Risk: Risks of exceeding the allocated budget due to unexpected costs like
additional development tools, server costs, or marketing expenses.
3. Technical Risk: Risks arising from technology challenges, including website crashes,
payment gateway failures, security vulnerabilities, or integration issues with third-party
services.
4. Business Risk: Risks affecting the overall business success, such as low user engagement,
high competition, poor customer retention, or market demand fluctuations for fashion.

3.5.2. Risk Analysis Process

1. Identifying the Problems Causing Risk
For Stylista, risks can come from technical, financial, operational, and business challenges.
Some possible problems include:
• Cyberattack or data breach compromising customer data.

• Payment gateway failure during transactions.

• Server downtime/crash during high traffic.

• Delay in developing or delivering new features.

• Low user engagement due to lack of interest or poor experience.

At this stage, the focus is only on listing risks, not solving them. Techniques such as

22
brainstorming, SWOT analysis, and expert judgment can help identify risks.
2. Identifying the Probability of Occurrence of the Problem
The likelihood of each risk is estimated based on prior experience, expert opinion, and industry
benchmarks. Probability is expressed as decimals (0–1).
Example from Stylista’s risks:
• Cyberattack / Data Breach → High probability (0.8).

• Server Downtime / Crash → Medium probability (0.5).

• Low User Engagement → Low probability (0.15).

3. Identifying the Impact of the Problem

Impact shows the possible damage if the risk happens. It can be financial (lost revenue,
penalties, recovery cost) or operational (loss of customer trust, disruption of service).
Examples:
• Cyberattack could cause data loss, financial loss, and brand damage (Impact = 9).

• Payment Gateway Failure may lead to loss of sales and unhappy customers (Impact =
8).

• Delay in Feature Development may slow growth and competitiveness (Impact = 6).

4. Assign Values to Probability and Impact

Both Probability (P) and Impact (I) are assigned numeric values to make the risks measurable.
In this project:
• Probability values are decimals between 0–1.

• Impact values are rated on a 1–10 scale.

Example from Stylista:

• Cyberattack → P = 0.8, I = 9

• Server Downtime → P = 0.5, I = 7

5. Calculate Risk Exposure (RE)

Risk Exposure (RE) is calculated as:
RE=Probability × Impact
23
This shows the seriousness of each risk.
Examples from Stylista:
Cyberattack → RE = 0.8 × 9 = 7.2
Payment Gateway Failure → RE = 0.6 × 8 = 4.8
Server Downtime → RE = 0.5 × 7 = 3.5
6. Prepare a Table and Order Risks by Risk Exposure
Organize all identified risks into a table with probability, impact, and RE, then sort in
descending order of RE. High RE risks should be addressed first with mitigation strategies.

Figure 13 Risk Exposure Analysis for Stylista E-commerce Website in MS Excel

Risk Exposure Analysis – Stylista E-commerce

Project
8 7.2
7 Cyberattack

6
4.8 Payment Gateway Failure
5
4 3.5 Server Downtime
3
Delay in feature
2 1.5
development
0.75
1 Low user engagement
0
Risk Exposure(RE) = P * I

Figure 14 Risk Exposure analysis visualization in column chart

7. Risk Mitigation Plans

After identifying, quantifying, and prioritizing risks, the next step is to plan strategies to reduce
or manage them. Risk mitigation involves taking proactive steps to minimize the probability
24
of occurrence, reduce the impact, or both. Strategies can include technical, operational,
financial, and organizational measures.
Risk Mitigation Plan for Cyberattack / Data Breach
Risk: Unauthorized access to Stylista’s e-commerce website leading to data theft, financial
fraud, or service disruption.
Risk Exposure (RE): 7.2 (Highest)
Priority: 1
Mitigation Strategies that can be undertaken to solve or mitigate the risk are
Use website security: Add SSL certificate (HTTPS) and firewalls to protect the site.
Protect user data: Store passwords safely (encrypted) and take regular backups.
Limit access: Only trusted staff can access important data and use two-step login factor
authentication.
Keep system updated: Always update the website, plugins, and payment system.
Monitor activity: Watch the website for suspicious activity and get alerts quickly.
Be ready for attacks: Make a response plan so the team knows what to do if an attack happens.

3.6 QA Activity
3.6.1. Test Cases for Unit Testing
Unit testing is a software testing method where individual components or units of code (like
functions or methods) are tested in isolation to verify their correctness and ensure they function
as expected.

Test Case ID: 1

Test Title: Verify login with valid username and password.
Test Designed Date: 20 July 2025
Pre-conditions: User has valid username and password.
Dependencies:

25
 Table 1: Unit testing 1

Test Description Test Data Expected Actual Result Status (Pass/Fail)

Result
Navigate to login Username: User should be User is navigated Pass
page. unika able to login. to the landing
Provide valid page with
username. Password: successful login.
Provide valid aa112
password.
Click login button.
Provide invalid Username: abc User login User login Pass
username and Password: 123 invalid. invalid.
password.

Post-condition:

User is validated and the page is redirected to the landing page with login status.

Test Case ID: 2

Test Title: Add items to cart.
Test Designed Date: 27 July 2025
Pre-conditions: The user must be logged in.
Dependencies:

Table 2: Unit Testing 2

Test Description Test Data Expected Actual Result Status (Pass/Fail)

Result

26
 Select an item to Item: Lipstick The item The item is added Pass
purchase. should be to cart along with
Select the quantity of added to cart the quantity.
items to purchase. along with the
Click on “Add to quantity.
Cart” button.

Select an item to Item: The item The item is added Pass

purchase. Foundation should be to cart along with
Select the quantity of added to cart the quantity.
items to purchase. along with the
Click on “Add to quantity.
Cart” button.

Post-condition:
The items are added to cart along with the selected quantity and size/shades of the product.

3.6.2. Test Cases for Integration Testing

Test Case ID: 3

Test Title: Display items based on the selected field.
Test Designed Date: 29 July 2025

Pre-conditions: Items of different categories are stored in the database.

Dependencies:

27
 Table 3: Integration Testing 1

Test Description Test Data Expected Actual Result Status (Pass/Fail)

Result
Select a category. Category: Men Items Items belonging Pass
View items in that belonging to to “Men”
category. “Men” category is
category displayed.
should be
displayed.

Post-condition:
The item is displayed based on different categories.
3.6.3. Test Cases for System Testing
System testing is a level of testing that validates the complete and fully integrated software
product. The purpose of a system test is to evaluate the end-to-end system specifications.
Usually, the software is only one element of a larger computer-based system.

Pre-conditions:
Test Case ID: 4
The system should function as intended.
Test Title: Functionality testing.
Test Designed Date: 1 August 2025

Table 4: System testing 1

Test Description Test Data Expected Actual Result Status (Pass/Fail)

Result

Post-condition:
The functional components are working as intended.
28
 UI Workflow. Landing page. All the buttons All the buttons Pass
and navigation and navigation
bar contents bar contents
should navigate to the
navigate to the correct location.
correct
location.
User login and Correct user The user The user can Pass
registration. registration and should be able register and then
login data. to register and login to the
then login to website. The user
the website. can access the
The user login features.
should also be
able to access
the login
features.

CHAPTER 4: CONCLUSION

In conclusion, the STYLISTA project set out to create an accessible, attractive, and feature-
rich platform for users to explore and purchase beauty and fashion products online. Through a
thorough system design and analysis process, clear functional and non-functional requirements
were established to ensure a secure, user-friendly, and responsive experience. Use of modern
web technologies like HTML, CSS, PHP, and MySQL enabled the development of a dynamic
platform with key modules such as user registration, login, product display, cart management.
While object-oriented practices and structured analysis techniques were employed to plan the

29
system, careful attention was also given to user interface design, making the site visually
appealing and easy to navigate.

30
 REFERENCES

[1] K. &. T. C. Laudon, "E-commerce 2020: Business, Technology, Society," 2020.

[2] A. Y. L. L. Y. N. M. &. C. F. Chong, "Predicting online product sales via online reviews,
sentiments, and promotion strategies," International Journal of Operations & Production
Management, vol. 36, no. 4, pp. 358-383, 2016.
[3] D. K. E. &. S. D. W. Gefen, "Trust and TAM in online shopping: An integrated model,"
MIS Quarterly, vol. 27, no. 1, pp. 51-90, 2003.

31
32