ECOMMERCE WEBSITE

FOR
CRAFTIFY

BY
Nicky Maharjan
7-2-551-210-2020
Garima Maharjan
7-2-551-201-2020
AND
Jubisha Prajapati
7-2-551-203-2020
National College of Computer Studies

A Software Engineering Project Report Submitted to

Faculty of Management, Tribhuvan University
in partial fulfilment of the requirements for the degree of

Bachelor of Information Management (BIM)

Paknajol, Kathmandu

February, 2024
 ACKNOWLEDGEMENT
The completion of this project would not have been possible without the involvement and
assistance of quite a handful of individuals whose names cannot be all disclosed. Their
contributions are respectfully appreciated and gratefully acknowledged. However, we would
want to convey our heartfelt gratitude and thankfulness to "Mr. Sudil Maharjan" for his
continuous support, kindness, and understanding spirit. This project would not have
happened without every individual's encouragement and guidance. The guidance and
assistance provided by all people who contributed to this initiative was crucial to its success.
We are grateful for his constant support and assistance during this effort.

Garima Maharjan
Nicky Maharjan
Jubisha prajapati

i
 EXECUTIVE SUMMARY
In the Introduction chapter, the background of e-commerce and the establishment of Craftify
are detailed. The organization's current situation, including its limitations and issues, such
as local customer constraints and lack of digital presence, is discussed. Objectives, scope,
and methodology are also outlined, with a focus on the Waterfall model used for the project's
development.

The Tasks and Activities Performed chapter delves into the analysis of customer
demographics, entity relationship diagrams, problem analysis, and analysis of possible
solutions. Functional and non-functional requirements, feasibility study, process modeling,
system implementation methodology, testing, and findings are also covered. Each module
of the Craftify e-commerce platform, including login, dashboard, products, orders, payment,
and cart, is discussed along with corresponding test cases
.
Finally, the Discussion and Conclusion chapter provides an overview of the Craftify e-
commerce platform's role in enhancing craft businesses' operations. The platform's features,
benefits, and recommendations for careful implementation and user training are highlighted.
The report concludes by emphasizing Craftify's ability to streamline operations, enhance
customer satisfaction, and improve overall business performance within the craft industry.
Overall, the Craftify e-commerce platform serves as a comprehensive software solution
designed to optimize the management of handmade goods businesses, ultimately leading to
increased efficiency and customer satisfaction.

ii
 TABLE OF CONTENT
TITLE OF PAGE
ACKNOWLEDGEMENT ........................................................................................................ i
EXECUTIVE SUMMARY ...................................................................................................... ii
TABLE OF CONTENT.......................................................................................................... iii
LIST OF FIGURES ................................................................................................................ v
LIST OF TABLES.................................................................................................................. vi
ABBREVIATIONS ................................................................................................................ vii
CHAPTER 1: INTRODUCTION....................................................................................... 1
1.1 Project Introduction ...................................................................................................... 1
1.2 Objective of Project...................................................................................................... 1
1.2 Limitation of Project .................................................................................................... 1
1.3 Software Development Methodology .......................................................................... 1
1.4 Project Framework ................................................................................................... 3
1.5 Data and Information ................................................................................................ 4
1.6 Tools Used ................................................................................................................ 5
CHAPTER II: TASK AND ACTIVITIES PERFORMED.............................................. 6
2.1 Requirement Specification ........................................................................................... 6
2.1.1 Functional Requirement ........................................................................................ 6
2.1.2 Non-Functional Requirement ................................................................................ 8
2.2 Feasibility Study........................................................................................................... 9
2.2.1 Technical Feasibility: ............................................................................................ 9
2.2.2 Operational Feasibility: ......................................................................................... 9
2.2.3 Economic Feasibility: ............................................................................................ 9
2.2.4 Schedule Feasibility: ............................................................................................. 9
2.3 System Analysis ......................................................................................................... 10
2.3.1 System Modelling ................................................................................................ 10
2.3.1.1 E-R Diagram ..................................................................................................... 10
2.3.2 Process Modelling ............................................................................................... 11
2.4 System Design ............................................................................................................ 18
2.4.1 State Diagram .......................................................................................................... 18
2.5 System Implementation .............................................................................................. 19

iii
 2.6 System Testing ........................................................................................................... 20
2. 7 Findings ..................................................................................................................... 23
CHAPTER III: DISCUSSION AND CONCLUSION .................................................... 24
3.1 Discussion .................................................................................................................. 24
3.2 Conclusion.................................................................................................................. 24
3.3 Recommendations ...................................................................................................... 24
REFERENCES

iv
 LIST OF FIGURES
Figure 1.1 Incremental model 3
Figure 2. 1 Use case Diagram ................................................................................................ 7
Figure 2. 2 ER Diagram ....................................................................................................... 10
Figure 2. 3 Activity Diagram of user ................................................................................... 12
Figure 2.4 Activity Diagram of admin 13
Figure 2.5 Level Zero DFD Diagram .................................................................................. 14
Figure 2.6 Level One DFD Diagram ................................................................................... 15
Figure 2.7 State Diagram ..................................................................................................... 18

v
 LIST OF TABLES
Table 2. 1 Use case Description............................................................................................. 8
Table 2.2 Sequence Diagram of user of Craftify ................................................................. 16
Table 2.3 Sequence Diagram of Admin of Craftify 17
Table 2.4 Test case for Login .............................................................................................. 20
Table 2.5 Test case for product detail 21
Table 2.6 Test case for add product 22
Table 2.7 Test case for add to cart 22
Table 2.8 Test case for checkout 23

vi
 ABBREVIATIONS

BIM Bachelor of Information Management

CSS Cascading Style Sheet

FOM Faculty of Management

NFR Non-Functional Requirements

SEP Software Engineering Project

TU Tribhuvan University

UI User Interface

UML Unified Modeling Language

vii
 CHAPTER 1: INTRODUCTION
1.1Project Introduction
Craftify's ecommerce website offers customers a seamless and user-friendly shopping
experience, featuring a comprehensive product. The platform's secure checkout process
supports multiple payment methods, while personalized product recommendations and
customer reviews aid shoppers in making informed purchasing decisions. With transparent
order tracking and responsive customer support, Craftify ensures timely delivery and
assistance throughout the shopping journey. Craftify's commitment to excellence extends
beyond just providing high-quality products, fostering a vibrant crafting community where
enthusiasts can connect, learn, and explore their creativity.

1.2 Objective of Project

The objectives of our project are:
• To offer easy access to high-quality crafting supplies.
• To provide a wide range of crafting categories.
• To ensure secure and seamless checkout.

1.2Limitation of Project
The Limitations of the project are:
● Inability to Customize Products
● Dependence on Technology
● Return and Exchange Policies

1.3 Software Development Methodology

In the context of the Craftify ecommerce website development, the incremental model was
utilized, meaning that the project progressed in a series of incremental steps or stages, rather
than being developed all at once in a linear way.
The incremental model is a software development methodology where the project is divided
into small, manageable modules or increments. Each increment passes through the phases of
development, starting from requirements analysis, moving through design and development,
and concluding with testing and implementation. Here's how the various phases of the
incremental model were applied:
1
• Requirement Analysis: In this phase, the requirements for the Craftify website were
gathered and analyzed. This involved understanding the needs and expectations of
owner, identifying the functionalities required. The requirements were broken down
into smaller, more manageable parts or increments.
• Design and Development: Once the requirements were understood, the design and
development phase began. This involved designing the architecture of the website,
creating wireframes and developing the actual features and functionalities
incrementally. Each increment would add new features or refine existing ones based
on the priorities set during the requirement analysis phase.
• Testing: Testing is an integral part of the incremental model and occurs after each
increment or module is developed. This ensures that each increment meets the
specified requirements and functions as intended. Testing may include unit testing,
integration testing, and system testing to identify and fix any defects or issues.
• Implementation: This phase enables the coding phase of the development system.
It involved the final coding that design in the designing and development phase and
tests the functionality in the testing phase. After completion of this phase, the number
of the product is enhanced and upgraded up to the final system product.

2
Below is the diagram of incremental model:

Build 1

Design & Implementati

Testing
Development on

Build 2

Design & Implementati

requirements Testing
Development on

Build 3

Design & Implementati

Testing
Development on

Figure 1.1 Incremental model

The System involves three versions:

• Version 1: It involves front end and backend development without search feature
and only cash on delivery option as payment.
• Version 2: In version 2 of the System, online payment feature was added
• Version 3: In version 3 of the System, search feature was added through which
customers can search the products of their choice.

1.4 Project Framework

The overall project is divided into four segments. They are:
• Initiation:
In the initiation phase, all the activities related to brainstorming, research, feasibility
analysis, and stakeholder interviews were performed. The key focus of this phase
was to identify which key components are required to put the project into action.
• Planning:

3
 In the planning phase, all the plans for the project were determined including a
number of individuals to be interacted with, planning of progress milestones, and
proper management is addressed.
• Execution:
The execution phase was focused on the actual production of a system and all the
action required for the development of the system. This phase helped to make
progress in the project.
• Management and Review:
This phase focused on documentation and monitoring of the project. Progress was
identified and necessary steps were further implemented.
In the review phase, the overall project was analyzed and discussed with relevant
stakeholder, and individuals involved in the development of the project.

1.5 Data and Information

The data and information for this report were collected using two methods. They are:
a) Primary data collection method
Primary data were collected by gathering data through surveys, interviews and
observation. For the data collection, different sets of questionnaires were prepared
and provided to the owner. Some of the questions that were asked to owner of the
organization were:
• How long has Craftify been in operation?
• Can you describe the types of macrame products Craftify offers?
• How many professional macrame artisans does Craftify currently work with?
• How do you currently manage your inventory and product records?

b) Secondary data collection method

The secondary data were collected using internet that helped to know which type of
software will be suitable for the organization.

4
1.6 Tools Used
For the development of the Craftify, different tools were used. They are mentioned below:
● Front-end:
HTML: This programming language helped to create a suitable interface for website
in Craftify project.
CSS: This technology was used to style the website and format the html elements of
the webpage.
• Back-end:
PHP: This language helped to create an independent platform for the project along
with database connectivity. In this project, PHP is used to perform all the backend
programs.
• Database:
MySQL: MySQL is used for the database management for the Craftify.
● Server Implementation:
Xampp: It allowed computer to run server locally and test the system.
• Editor: Visual Studio Code

5
 CHAPTER II: TASK AND ACTIVITIES PERFORMED

2.1 Requirement Specification

Requirements analysis or requirements engineering is a process used to determine the needs

and expectations of a new product. It involves frequent communication with the stakeholders
and end-users of the product to define expectations, resolve conflicts, and document all the
key requirements. (simplilearn, 2023)
The Craftify ecommerce provides functions to both customer and admin. Individuals can
browse, purchase, and manage their orders for macrame products on the Craftify platform.
Whereas admin can add and update products, process orders, and handle customer inquiries.

2.1.1 Functional Requirement

Here are the functional requirements for Craftify, the macrame business:
User Authentication:
• Login: Customers and shop owner can log in to access the system and its
functionalities.
• Logout: Users can log out of their accounts, which redirects them to the login page.

Product Management:
• Manage Products: Shop owners can add, update, or delete macrame products,
including details such as description, price, photos etc.
• Manage Inventory: Shop owners can track and display inventory levels for each
product.

Customer Management:
• Manage Customer Accounts: Customers can create accounts to view orders, and
manage wishlists.
• Checkout Process: The system shall facilitate a secure checkout process, allowing
customers to pay for their orders through various payment methods.

Order Management:
• Manage Orders: The system shall view all orders placed by customers, including
order details, customer information, and payment status.

6
 • Update Order Status: Shop owners can update the status of orders (e.g., pending,
delivered).

2.1.1.1 Use Case Diagram

Use case are the scenario-based technique for requirements. This is used to identify the type
of interaction between the system and its users and the actors involved. The functional
requirements can be represented by a use case diagram. The use case diagram for this system
is

Figure2.1 use case diagram

7
 Actor User, Admin
Description User_id and user_pw allows the user to log in to the system with ease.
The user can browse and buy the available things. In addition, the user
has easy access to the system's dashboard and logout functionality.
Admin can easily login to the system with the help of admin_id and
admin_pw. Admin can manage the products by adding, updating or
deleting as per the requirement. Along with that, Admin can view
dashboard of the system and can logout from the system easily.
Data Name, address, email, payment information
Product information, inventory data.
Stimulus Browse, search, view details, add to cart, checkout, view order
Add/edit/delete products, manage orders, view stock, communicate
with customers
Response Displays products, processes order, sends confirmations, provides
delivery information
Adds/updates products, processes orders, stock analysis, facilitates
communication

Comments Core functionalities - browse, search, purchase

Key tasks - manage products, orders, customers
Table 2.1: Use case Description

2.1.2 Non-Functional Requirement

This e-commerce website is able to operate in the following NFR (non-functional)
characteristics:
• Usability: The system has user-friendly interface so that anyone familiar with
Windows operations may use it.
• Reliability: This website is available and can function correctly dependent on the
needs of the user. The information can only be saved after it has been confirmed by
the system. Any attempt to store invalid data will be prohibited.
• Performance: The Craftify website operates its functions in small amount of time.
• Security: Only the authorized user may access the Craftify website to ensure safety
while working. Nobody can access the system without their login credentials.
8
2.2 Feasibility Study

Feasibility study is a study to evaluate the feasibility of a proposed project or system. It is

the feasibility analysis or a measure of the software product in terms of how beneficial
product development is from a practical point of view. The purpose of the study is to
determine if the system's request should proceed further.

2.2.1 Technical Feasibility:

The use of modern web development technologies like HTML, CSS, JavaScript, and server-
side programming languages like PHP ensures Craftify's technical sustainability. These
technologies ensure compatibility across diverse devices and operating systems by offering
platform independence and running on many web servers. Scalability and dependability can
be further improved using online service options.

2.2.2 Operational Feasibility:

From an operational point of view, Craftify offers a user-friendly interface that makes it
simple for customers and shop owners to navigate and manage products and orders. The
system is built to provide maximum reliability and performance, guaranteeing smooth
operation even during moments of high traffic. Additionally, easy maintenance and upgrades
may be performed on a regular basis to improve user experience and adapt to changing
company needs.

2.2.3 Economic Feasibility:

Craftify's development is financially possible since it makes use of affordable tools and
technology. Using open-source frameworks and platforms can help reduce development
costs. The initiative is financially feasible since it does not require physical inventory or real
shops, which also lowers overhead costs.

2.2.4 Schedule Feasibility:

In Schedule Feasibility Study mainly timelines/deadlines are analyzed for proposed projects
which includes how many times teams will take to complete the final project. The purpose
of the project may fail if it can’t be completed on time. In many cases a project will be

9
unsuccessful if it takes longer than it was estimated: some external environment conditions
may change, hence a project can lose its benefits, expediency and profitability.

2.3 System Analysis

System analysis is the process by which an individual’s studies a system such that an
information system can be analyzed, modeled, and a logical alternative can be chosen.
System analysis projects are initiated for the three reasons: problems, opportunities, and
directives.

2.3.1 System Modelling

2.3.1.1 E-R Diagram

Figure 2.2: ER Diagram

In the above ERD, there are several entities such as User, Product, Order, payment, Cart,
stock and Admin, each defined by specific attributes. Users, representing customers, can
place multiple orders, establishing a one-to-many relationship. Orders, in turn, can consist
of multiple order items, forming another one-to-many relationship. Each order item
corresponds to a specific product, creating a one-to-one relationship. Users also have a one-
to-one relationship with their carts, which can contain multiple order items, following a one-

10
to-many association. Additionally, Admins manage the stock of products, resulting in a one-
to-many relationship, where an admin can oversee the stock for numerous products. This
database structure aims to efficiently capture user interactions, purchase details, and
administrative functions within the shopping platform.

2.3.2 Process Modelling

Process modeling is the graphical representation of business processes or workflows. A

process model allows visualization of business processes so organizations can better
understand their internal business procedures so that they can be managed and made more
efficient. (bizagi, 2022). The suggested models often use a variety of attributes to describe
the solution. The Craftify process model is shown with the assistance of a system
architecture, activity diagram, use case diagram, sequence diagram, and ER diagram.

11
2.3.2.1 Activity Diagram

Below is the activity diagram of the user:

Figure 2.3: Activity Diagram of user of Craftify

In the above activity diagram, it shows an e-commerce ordering process, starting with
logged-in customers browsing products and adding them to cart. Check out involves
choosing a payment method, confirming details, and placing the order. The system sends a
confirmation, and the customer can optionally view their profile or an order report before
closing the process. Alternative paths handle invalid logins, cart item removal, and optional
12
profile viewing before checkout. Overall, the diagram depicts a streamlined path for placing
orders with options for account-related actions.
Below is the activity diagram of the admin:

Figure 2.4: Activity Diagram of admin of Craftify

The activity diagram above demonstrates a secure procedure for managing products and
orders: login and authentication are necessary, and invalid attempts result in retries. After
login in, the administrator can add new goods with information, change or delete existing
13
ones, and see orders with their status (pending or delivered), allowing for additional
modification and deletion. Valid and invalid activities are handled separately to protect data
integrity, and the process concludes with a logout.

2.3.2.2 Data Flow Diagram

Figure 2.5: Level Zero DFD Diagram

14
 Figure 2.6: Level One DFD Diagram

The above data flow diagram represents the flow of data through the application. It provides
an overview of the system. Level 0 DFD provides a basic overview of the entire application.
It provides a quick summary of the system. The user makes login, view products, search
product, add to cart, order, and checkout requests to the application. The application
responds to the user's queries. Similarly, the admin makes login, manage products, manage
order and manage stock request to the application and the application responds to admin’s
request. The application stores information related to user, order, products, cart and payment
in the database. Level one DFD depicts basic modules in the system and flow of data among
the modules. It provides a more detailed view of the website.

15
2.3.2.3 Sequence Diagram

Below is the sequence diagram of user:

Table 2.2: Sequence Diagram of user of Craftify

The above sequence diagram shows all of the steps a user takes, from exploring products to
completing an order, with the system seamlessly processing requests and authenticating user
input throughout. As the user browses the website and picks products, the system replies by
allowing the user to add chosen items to the shopping cart, where they can optionally
evaluate their selections before proceeding to checkout. During the checkout process, the
16
user enters relevant details such as payment information, which the system validates to
ensure product availability and payment viability. Following successful validation and order
placement, the system validates the orders.

Below is the sequence diagram of admin:

Table 2.3: Sequence Diagram of user of Craftify

The above sequence diagram outlines the several features that an administrator can access.
The administrator logs in first, and after their credentials are verified, they are able to access

17
the dashboard. The admin can easily navigate activities like viewing orders, adding products,
and updating stock levels within the dashboard. In particular, adding products comprises
entering product details and storing them to the database upon submission, whereas viewing
orders comprises retrieving and displaying every order from the database. The administrator
can modify product stock levels by editing stock. The administrator logs out at the end of
the process to end the session and return to the login page.

2.4 System Design

2.4.1 State Diagram

Figure 2. 7: State Diagram

The flow of the system begins from the login window. The user can view or search the item
and select the item. After selecting the item, the user can add their product into the cart. The
user needs to be logged in in order to add the items into their cart. If the user doesn't have
any account, then he/she should register for the further process. The item will be placed as
ordered and goes through the payment section where users need to fill the form and select
payment mode i.e. cash and khalti. After that the user can view the order statement.

18
2.5 System Implementation
In this part, it is actually constructing a new system from scratch with the help of the system
design. This part will look at the implementation of the system including the database and
the main application. It includes coding, testing and integrating the system to meet its
requirements. System implementation is the most important step in case of finalizing the
approved web system. We need to justify some basic requirements (software & hardware)
so that the system will work or be implemented without having obligations and customer
dissatisfaction.
System requirements:

● Operating system: Windows or Mac

● Web Development System: Visual Studio
● Database Management System: MySQL, SQL Server
order Module:

19
Product detail module

2.6 System Testing

Project Name: Craftify

Module Name: login
Testcase Id Test Scenario Test Case Precondition
TC_login_1 To test if an Enter valid email Need a valid email
appropriate message and password and password from
is displayed when the login
user login without
appropriate email
and password
Test Steps Test Data Expected Status Actual Result

20
 1. Enter Email <valid Email> Successful Login User inside the
2. Enter <valid Password> System
Password

Table 2.4: Test Case for Login

Module Name: Products detail

Testcase Id Test Scenario Test Case Precondition
TC_product_details_1 Verify the display Ensure that product The product details
of product details details are page is accessible.
displayed correctly
on the product
details page.

Test Steps Test Data Expected Status Actual Result

1) Navigate to the Product ID: [valid Product details Product details are
product details page. product ID] should be displayed displayed
accurately. accurately.

Table 2.5: Test Case for product detail

Module Name: Add products

Testcase Id Test Scenario Test Case Precondition

TC_product_add_1 Add a new product Ensure that a new The admin is logged
to the system product can be in and has access to
successfully added the dashboard

Test Steps Test Data Expected Status Actual Result

1)Navigate to the Product name: Product should be Product is
product addition Macrame mirror successfully added successfully added
form available in Product description:
the admin Macrame mirror
dashboard. Product price: 2500

21
 Product quantity: 10
Product image:
pp2.jpg

Table 2.6: Test Case for add products

Module Name: Add to cart

Testcase Id Test Scenario Test Case Precondition

TC_add_to_cart_1 Add product to cart Ensure that a Product ID and user
successfully product can be ID are valid
added to the cart

Test Steps Test Data Expected Status Actual Result

1. Submit a POST Valid product ID, Product should be Product is added to

request with valid user ID, amount, added to cart cart
product ID, user ID, and quantity
amount, and
quantity

Table 2.7: Test Case for add to cart

Module Name: Checkout

Testcase Id Test Scenario Test Case Precondition
TC_checkout_1 Place an order Ensure that an order User is logged in
successfully can be successfully
placed

Test Steps Test Data Expected Status Actual Result

1. Submit a POST Valid user session, Order should be Order is

request to the script valid checkout mode successfully placed successfully placed
with valid user

22
 session and
checkout mode.

Table 2.8: Test Case for checkout

2. 7 Findings

In this project, the organization's problems were analyzed, and various solutions to address
these problems were put into practice. The main goal of the development was to create a web
application that would specifically address the issues that the business was having lately.
The project's goal was to modernize operations and increase organizational efficiency by
utilizing current systems. All required resources were acquired and deployed during the
development process, which helped the system's advancement. In order to ensure alignment
with business needs and objectives, the organization's owner and staff participated in a while
addresses and cooperation to gather initial information that was crucial to system creation.

23
 CHAPTER III: DISCUSSION AND CONCLUSION

3.1 Discussion
The Craftify ecommerce platform serves as a project aimed at enhancing the operations of
craft businesses by automating various tasks and improving overall productivity. This
platform enables craft businesses to organize, manage, and secure information related to
macrame products efficiently. Its features are designed to address challenges associated with
manual management of craft businesses. Craftify facilitates inventory tracking, ensuring
optimal stock levels and preventing product shortages. Additionally, the platform enhances
product quality and customer satisfaction by providing detailed product information and
customization options, thus minimizing the risk of dissatisfaction. By centralizing
information and streamlining processes, Craftify intends to increase accuracy, safety, and
efficiency within the craft industry. As a computer-based system, Craftify stores crucial data
and optimizes the operation of craft businesses, ultimately leading to improved business
performance and customer experiences.

3.2 Conclusion
In summary, the Craftify e-commerce platform functions as a comprehensive software
solution that is intended to efficiently handle and arrange critical information related to
macrame items. This program provides functions that meet the individual needs of users,
simplifying many elements of the handmade goods sector. Craftify gives admins the ability
to effectively manage their inventory by giving them information on product stocks along
with the ability to edit and remove data as needed. Finally, the fundamental goal of Craftify
is to simplify and improve the management of craft-related data, allowing users to run their
enterprises with ease and efficiency.

3.3 Recommendations
It is essential to take a careful approach at every stage, from gathering requirements to final
implementation, because of the complex structure of the Craftify e-commerce platform
design. Given the significant benefits this system provides and its ability to enhance client
satisfaction, a number of recommendations are suggested. The new system should be
implemented carefully, paying special attention to detail, and following the specified system

24
requirements. This is the initial piece of advice. To reduce the possibility of disruptions in
power affecting with business operations, a source of uninterrupted power supply should
also be made reachable during the business's hours of operation. In order to guarantee the
best possible use of the program, it is also advised that end users receive training in
fundamental computer skills.

25
 REFERENCES

(n.d.). Retrieved from bigcommerce: https://www.bigcommerce.com/articles/ecommerce/

(n.d.). Retrieved from capitalnumbers: https://www.capitalnumbers.com/blog/the-importance-

of-e-commerce-in-modern-business/

(n.d.). Retrieved from geeksforgeeks: https://www.geeksforgeeks.org/architecture-of-a-

system/

bizagi. (2022). Retrieved from https://www.bizagi.com/en/blog/process-modeling-and-

mapping/what-is-process-modeling-6-essential-questions-
answered#:~:text=What%20is%20the%20definition%20of,context%20of%20the%20
business%20environment.

broserstack. (2023). Retrieved from https://www.browserstack.com/guide/how-to-write-test-

cases#:~:text=A%20test%20case%20refers%20to,necessary%20to%20verify%20a%2
0feature.

Forrester. (2017, July 2017). Retrieved March 25, 2022, from Forrester:
https://www.forrester.com/blogs/fiveeasystepstoanalyzeanyproblem/

simplilearn. (2023). Retrieved from https://www.simplilearn.com/what-is-requirement-

analysis-
article#:~:text=Requirements%20analysis%20or%20requirements%20engineering,do
cument%20all%20the%20key%20requirements.
Screen shots
Some Screenshots of the Craftify E-commerce Website