SCHOOL OF TECHNOLOGY

DIPLOMA IN INFORMATION TECHNOLOGY

UNIT: PROJECT
UNIT CODE: DIT 503
TITLE: ECCOMERCE MANAGEMENT SYSTEM SRS
NAME: JORAM SIREE
REG NO: 21/07233
SUPERVISOR: Ms. GLADYS MANGGE.

THIS PROJECT PROPOSAL ISSUBMITTED IN PARTIAL FULFILMENT OF THE

REQUIREMENTS OF THE AWARD OF DIPLOMA IN INFORMATION
TECHNOLOGY IN KCA UNIVERSITY
DECLARATION
I hereby declare this project is submitted to the full requirements of the diploma in Information
Technology based on my original work and has not been presented in any other university.

STUDENT
Signature………… Date………..

SUPERVISOR
Signature……….. Date………..
 Table of Contents
1. Project Proposal.………………………..1
Acknowledgement…………………………0.0
Introduction…………………………………………1.1
Background…………………………………………1.2
Current problems…………………………………….1.3
Proposed solution....…………………………………1.4
Objectives....…………………………………………1.5
Justification …………………………………………1.6
Scope……..………………………………………….1.7
Literature Review……………………………………1.8
Methodology…………………………………………1.9
Project Schedule……………………………………1.2.1
Gantt chart………………………………………….1.3.1
Budget………………………………………………1.4.1
Risk management…………………………………..1.5.1
Reference……………………………………………1.6.1

2. System Requirements Specification

3. System Design Specification
4. Test Specification
5. Implementation
6. User Manual
ACKNOWLEDGEMENT

This project would not have been prosperous without the support of my supervisor.

Ms. Gladys Maenge who helped me every step of the way. I also acknowledge my

classmates who offered guidance and support throughout the entire project.

Finally, to my friends who endured this long and challenging process with me. Be

blessed. Thankyou.
 PROJECT PROPOSAL

INTRODUCTION
The goal of this project is to develop an ecommerce system that allows users to purchase products online.
The ecommerce system will include features such as a shopping cart, user authentication, payment
processing, and an admin panel for managing products and orders.

BACKGROUND
FEDHA MINIMARKET is a business whereby it involves in the sale of electronics, shoes and toys. It is
located in Kacheliba zone, kishaunet Sub-County, Nyandarua County and 15kms from Makutano town.
FEDHA MINIMARKET in operation for the last four years. It has been using physical system. This is
displaying laptops, phones and clothes on shelves. The current system supports the buying of movies
and music from the sources such as the music and movie producers. The business then distributes the
media to be sold at wholesale and retail price. It also advertises any promotions they are offering.

1.2 PROBLEM STATEMENT

The current system is affected by so many demerits that are making the business to operate at a loss as
gives below;
• The ecommerce industry is continuously growing, with many businesses now selling electronics
and other products online. This has created a need for an effective system to manage and store
ecommerce product data, efficiently process customer orders and automate the delivery
process.
 LITERATURE REVIEW:
• Reviewing literature is the primary activity of any researcher to gather immediate insight on a
theme or area. Reviewing other instances of similar solutions elsewhere in the world.
The relevant literature was reviewed from different books, journals, newsprint, magazines and
on-line materials. The literature review will move from general themes involving research areas
under investigation. Major themes discussed with reference to academic literature include e-
commerce, internet marketing, customer centricity, marketing strategies in the developing
horizons of the global business and the factors affecting the success of these strategies.
The first section of the chapter is aimed to explore the above-described general issues in
internet marketing and effectiveness of internet marketing in the business settings while the
second section is about the validity and application of classical marketing theories in the field of
e-commerce. These researches lead to the fact that use of internet in general business activities
has been there since past decades and organizations are reaping substantial benefits from their
online presence.

1.3 PROPOSED SYSTEM

The goal is to develop a general-purpose e- commerce store where any kind of product can be bought
from the comfort of home through the Internet. However, for implementation purposes, this website
will deal with an online shopping for products. These days, an increasing number of consumers prefer
making most of their purchases online and in such a scenario, having an ecommerce website for
business is the need of the hour.

OBJECTIVES /GOALS
The main objective is:
-To enable customers to easily search for and purchase electronics and other products from an
online store.

OTHER OBJECTIVES
 To provide customers with an easy payment system for their purchases.
 To provide a secure platform for customers to store and manage their purchases.
 To automate the process of tracking orders and ensuring timely delivery.
 To enable customers to access updated information on products and services.
  To enable businesses to easily manage customer orders and monitor online sales.
 To enable businesses to generate accurate reports on customer trends and sales performance.

METHODOLOGY
Incremental approach will be most preferable in the development of the software this is because it will
combine both the linear and iterative development methodology approaches. The user will identify the
services that the system will provide and identify which of the services have more priority than the other
services. It will also enable the fact that users will not have to wait for the entire system to be complete
in order for them to use it, user can use the earlier increments as prototypes and hence gain experience
which informs their requirements for further increment and also the highest priorities are offered first,
then later increments will be integrated with them.
The methodology used will be:
The Waterfall Model was first Process Model to be introduced. It is also referred to as a linear-
sequential life cycle model. It is very simple to understand and use. In a waterfall model, each phase
must be completed fully before the next phase can begin. This type of software development model is
basically used for the for the system which is small and there are no uncertain requirements. At the end
of each phase, a review takes place to determine if the project is on the right path and whether or not to
continue or discard the view. In this model software testing starts only after the development is
complete. In waterfall model phases do not overlap.

RESOURCES
The new proposed system will require the following resources:

RESOURCES REQUIRED TO DEVELOP THE SYTEM AND RUN IT.

NOTEPAD++ text editor for coding the HTML, CSS and java script.

Xampp or Wamp 5.6 as the local server

Web browser: Chrome ,Firefox , safari and edge (any web browser will really do)

CONSTRAINS:
As much as the system will be helpful to customers that live far away it also have it’s constrain.
The constrains of this system is that it will require internet in order to place and purchase the
goods.

PROJECT SCHEDULE.
Tas Description Planned Start Date Planned Deliverables
k Completion Date

1 Project proposal design 12/01/2023 18/01/2023 Project

Proposal
2 Requirements specification 15/01/2023 System
design requirement
specification
document

20/01/2023

3 System design specification 21/01/2023 23/01/2010 Design

document specification
document
4 Preparation of progress report 28/01/2010 Presentation
done

24/01/2023

5 Test plan document design 31/01/2023 3/02/2023 Test Plan

document
6 System Coding and compiling 5/02/2023 20/02/2023 Progress
presentation
7 System testing 23/02/2023 28/02/2023 Test results

8 Implementation strategy 30/02/2023 3/03/2023 Implementation

document design strategy
document
9 User manual design 8/03/2023 12/03/2023 User manual

10 Compilation of complete system 13/03/2023 20/03/2023 Final

 And final documentation documentation
and compiled
system
11 Project presentation 31/03/2023 31/03/2023 Present project

GANTT CHART
The Gantt chart below shows the tasks to be undertaken throughout this project and the duration that
will be taken to complete each task.

Duration(dd/mm) 2/1/23 3/02/23 5/2/23 15/2/23 21/2/23 23/2/23 30/2/23 13/3/23

Year 2023

Project idea
Project proposal

Feasibility study

Requirements
Definition
System Design

Testing and
debugging

Implementation

Final
documentation

BUDGET
The following are the costs of the resources that will be required in the successful completion of this
project. The resources are hardware and also the software resources. The other resources will be
stationary that I will use in the day to day

ITEM COST

INTERNET KSH 70,000

COMPUTER SYSTEM KSH 150,000

TOTAL KSH 220,000

CONCLUSION
This project will deliver a full-featured ecommerce system that provides a convenient and
secure shopping experience for users. The system will be developed using modern web
technologies and will be scalable and maintainable. The implementation of a payment gateway
and order management system will ensure a smooth and efficient checkout experience

REFERENCES
1. Ackerman, J. (1993) Robust control: systems with uncertain physical parameters Springer, Berlin

2. Amram, M. and Kulatilaka, N. (1999) Real options: managing strategic investments in an uncertain
world Harvard Business School Press, Boston, MA

3. Barad, M. and Sipper, D. (1988) Flexibility in manufacturing systems: definitions and Petri Net
modelling. International Journal of Production Research 26:2, pp. 237-248. [Inform world] .

4. Chaffey, D. (2012), ’Internet marketing’: Financial Times, Prentice Hall,

Pearson education, London
 SRS

Declaration
I declare that this project is my original work and has not been presented in any other college
or University for the award of a Diploma or Degree.

Student name…………………………………... Date…………………………….

Signature…………………………………………...

This proposal has been submitted for examination purpose to my project supervisor for approval.

Supervisor:………………………………... Date…………………………….
Signature…………………………………………...

1. INTRODUCTION
1 .1 P u r p o se:
This document is meant to delineate the features of E-commerce OSS, so as
to serve as a guide to the developers on one hand and a software validation
document for the prospective client on the other. The Online Shopping
System (OSS) for electronics item shop web application is intended to
provide complete solutions for vendors as well as customers through a single
get way using the internet. It will enable vendors to setup online shops,
customer to browse through the shop and purchase them online without
having to visit the shop physically. The administration module will enable a
system administrator to approve and reject requests for new shops and
maintain various lists of shop category.

1.2 Scope:
The eCommerce system is a web-based application that allows customers to
purchase products and services online. It will include features such as user
accounts, product catalogues, a shopping cart, payment processing, and
 order tracking. The system will also be able to integrate with third-party
services such as shipping providers, payment gateways, and analytics
services.

1.3Definitions:
OSS- Online shopping System (for electronics item shop)
SRS- Software Requirement Specification
GUI- Graphical User Interface
Stackholder- The person who will participate in system
Ex. Customer, Administrator, Visitor etc.

1.4 Overview:
This system provides an easy solution for customers to buy the
product without going to the shop and also to shop owner to sale the
product.
This proposed system can be used by any naïve users and it does
not require any educational level, experience or technical expertise
in computer field but it will be of good use if user has the good
knowledge of how to operate a computer.

2.OVERALL DESCRIPTION:

The Online Shopping system (OSS) application enables vendors to set up

online shops, customers to browse through the shops, and a system
administrator to approve and reject requests for new shops and maintain lists
of shop categories. Also the developer is designing an online shopping site
to manage the items in the shop and also help customers to purchase them online
without visiting the shop physically. The online shopping system will use the
internet as the sole method for selling goods to its consumers.
2.1 Product Perspective:
This product aimed toward a person who don’t want
to visit the shop as he might don’t get time for that or
might not interested in visiting there and dealing with
lot of formalities.

2.2 Product Functions:

OSS should support this use case:
 2.3 User Characteristics:
User should be familiar with the terms like login, register,order system
etc.

2.4Principle Actors:
Principle Actors are Customer and Administrator.

2.5 General Constraints:

A full internet connection is required for OSS.

2.6 Assumptions and Dependencies :

Working of OSS need Internet Connection.

3. Specific Requirements

Functional Requirements:

This section provides requirement overview of the system Various functional

modules that can be implemented by the system will be -

3.1 Description:
Registration

If customer wants to buy the product then he/she must beregistered, unregistered
user can’t go to the shopping cart.

Login

Customer logins to the system by entering valid user id and password for the
shopping.

Changes to Cart

Changes to cart means the customer after login or registration can make order or
cancel order of the product from the shopping cart.

Payment

In this system we are dealing the mode of payment by paypall.We will extend
this to credit card,debit card etc in the future.

3.1.1 Logout

After ordering or surfing for the product customer has to logout.

3.1.2 Report Generation

After ordering for the product,the system will sent one copy of the bill to the
customer’s Email-address and another one for the system data base.

USER REQUIREMENTS
 Users should be able to create accounts using their email
addresses and a password. - Users should be able to log in and out
of their accounts. - Users should be able to view and edit their
account information. - Users should be able to view product
catalogues and add items to their shopping carts. - Users should
be able to view their shopping cart and checkout with their
payment information. - Users should be able to view the status of
their orders.

Technical Requirements:
The system should be developed using the PHP programming language. -
The system should be designed to be used on modern web browsers. - The
system should be secure and protect customer data. - The system should
be integrated with third-party services such as shipping providers, payment
gateways, and analytics services. - The system should be able to scale up
or down to accommodate traffic spikes.
Testing Requirements:
The system should be tested on multiple web browsers and devices. - The
system should be tested against security threats such as SQL injection and
Cross-Site Scripting (XSS). - The system should be tested for performance
and scalability. - The system should be tested for usability and
accessibility.

3.2 Non-Functional Requirements:

Following Non-Functional Requirements will be there in the insurance to the
internet:
(i) Secure access to consumer’s confidential data.
(ii) 24X7 availability.
(iii) Better component design to get better performance at peak time.
(iv) Flexible service based architecture will be highly desirable for future
extension. On non-Functional Requirements define system properties
and constraints.
Various other Non-Functional Requirements are:
  Security
 Reliability
 Maintainability
 Portability
 Extensibility
 Reusability
 Compatibility

 Resource Utilization

3.3 Performance Requirements:

In order to maintain an acceptable speed at maximum number of uploads
allowed from a particular customer as any number of users can access to the
system at any time.
Also the connections to the servers will be based on the attributes of the user like
his location and server will be working 24X7 times.

3.4 T e c h n i c a l I s s u es:
This system will work on client-server
architecture. It will require an internet
server and which will be able to run PHP
application. The system should support
some commonly used browser such as IE,
mozzila firefox,chrome etc.

4.Inter f ace Requirement:

Various interfaces for the product could be-
1). Login Page
2). Registration Form
3). There will be a screen displaying information
about product that the shop having.
 4). If the customers select the buy button then
another screen of shopping cart will be opened.
5). After ordering for the product,the system will sent
one copyof the bill to the customer’s Emailaddress

Software Interface:
1.Operating System: Windows7 Ultimate which supports
networking.
2.XAMPP 5.6.
3.Web browsers.
4.Notepad++

Hardware Interface:
Hardware requirements for insurance on internet will
be same for both parties which are as follows:
Processor:Dual Core
RAM:2 GB
Hard Disk:320 GB
NIC:For each party

Communication Interfaces:
The two parties should be connected by LAN or WAN
for the communication purpose.
SENDER
Communication channel RECIVER
 SDS

Declaration
I declare that this project is my original work and has not been presented in any other college
or University for the award of a Diploma or Degree.

Student name…………………………………... Date…………………………….

Signature…………………………………………...

This proposal has been submitted for examination purpose to my project supervisor for approval.
Supervisor: ………………………………... Date…………………………….

Signature…………………………………………...

DEFINITION OF TERMS (ACRONYMS) AND KEYWORDS

SDS : System Design Specification
DFD : Data Flow Diagram
ERD: Entity Relationship Diagram
Checkout-Checkout is the process of gathering the payment and shipping
information to complete the purchase of items in the shopping cart. It is the final
step of purchase on an e-commerce shop that the customer reviews and places the
order online.

PayPal-PayPal is a global leader in online payments and a fast and secure way for
customers to pay online.
Shopping cart-Shopping cart is an online shopping software commonly used in
online shops or e-commerce platforms which allows people, during online-shopping,
to collect all preferred goods in a shopping cart first and then buy and pay them all
together after having made all choices.

Actors

Customer: Interactive actor who uses the portal to search for items and register himself.

Registered Customer: Interactive user who uses the portal to buy items and provide
feedback.

Objective

The purpose of this document is to define the requirements of the Online shopping
system. This document lists the requirements that are not readily captured in the use-
cases of the use-case model. The supplementary specification and use-case model
together capture a complete set of requirements of the system.

Scope

This supplementary specification defines the non-functional requirements of the system

such as reliability, performance, supportability, and security as well as functional
requirements that are common across a number of use-cases.

Common Functionalities

 Multiple users must be able to log on to the website and perform their
work concurrently.
 If the selected item is out of stock or has been restocked, the customer must
 be notified.

Usability

The desktop user interface shall be Widows 08 or Windows 10 compliant.

Reliability

The system shall be 24 hours a day, 7 days a week and not more than 10% down time.

Performance

 The system shall support up to 5000 simultaneous users against the central
database of any given data
 The system must be able to complete 80% of all transactions within 5 minutes

Security

 The system must prevent customers from changing product information, seller
 Information and pricing information.
Only admin can modify product information, seller information, and pricing
Information

CONTEXT DIAGRAM
The diagram describes the interaction between different users and other
systems and its environment. It dwells on Inputs, Processes and Outputs of
the System.

user Online
products
shop
ARCHITECTURE
The software will consist of a database, an Operating System, a web server, VB Code,
and several APIs to third parties:
Operating System: WINDOWS
Database: XAMPP MYSQL server
Web Server: MS Internet Information Services 6.0
Code: PHP, html, jQuery, JavaScript and CSS
API: Google Checkout
API: PayPal

Use – Case Model

Actors

Actor is something external to the system and interacts with the system. Actor may be a
human being, device or some other software system.

For Online shopping system, actors might be;

 Customer
 Registered Customer
 Shop Owner

Use – Case

A use-case represents sequence of actions performed by the system that yields an

observable result of value for a particular actor. Use-case represents a functional
requirement of a system.

For Online shopping system, we can find the following use-cases;

1. Login
2. Register customer
3. Search items
4. Buy items
5. Validate customer
6. Prepare bill
7. Pay bill
8. Feedback

USE - CASE DIAGRAM

DATA FLOW DIAGRAM
A data flow diagram (DFD) is a graphical representation of the "flow" of data
through an information system. On a DFD, data items flow from an external data
source or an internal data store to an internal data store or an external data sink, via
an internal process. This is a Level 1 data flow diagram that is an exploration of the
System Context Diagram. The main purpose of this diagram is to show various
subsystems of the online shop and where they get the data and which internal
process is invoking it.
Class Diagram
The class diagram seeks to identify the various objects to be inherent in the system.
Objects are real life entities that have an identity, a state and exhibits some certain
form of behaviour the case of ECCOMERCE, class diagram will show the class
modeling the various objects that are
interacting with each other and the association thereby

ACTIVITY DIAGRAM
This shows the coordination and flow of various activities within the use case
diagram as shown
below:
DATABASE DESIGN
This is a design technique by which relational database tables are structured in
such a way to make them invulnerable to certain types of logical inconsistencies
and anomalies. This is an activity that involves eliminating data redundancies in a
relational database system.
This is done with the aim of sorting the various attributes into tables in such a way
that:
➢ There are no repetitions within tables
➢ There are no partial dependencies on the primary key
➢ There are no transitive dependencies among attributes of a table.
This is illustrated below:

Database Class Diagram:

Database web class diagram:
ENTITY RELANTIOSHIP DIAGRAM (ERD)

USER INTERFACE DESIGN

Application
The application design concept exists of a basic e-Commerce store front, which allows visitors to browse
and create accounts, as well as place orders. Below is a basic concept of the store front, as it would
appear to a user on first arrival:

Browse
Browsing interface concept:
References

• All about Microsoft controls in C# http://www.msdn.microsoft.com/

• Wikipedia for various diagrams & testing methods http://www.wikipedia.org/

• Cool text for Images and Buttons http://cooltext.com/

• K-State Research Exchange for samples in report writing

http://krex.k-state.edu/dspace/handle/2097/959

• Smart Draw for drawing all the Diagrams used in this report. http://www.smartdraw.com/

• Sample Ecommerce Application http://www.NewEgg.com

 USER MANUAL
The aim of this document is to provide guidelines on how to run the system. The
document will specify how users will use the system and how it operates. It is
geared towards the user’s interaction with the system to be as smooth as possible
so that if the user is not sure of how some parts of the system work, they can
simply refer to this document to get information or instructions.
HOME PAGE

The first page as the system run takes you to the homepage.
Then start adding to cart.S
 REGISTRATION AND USER LOGIN
This page allows the user cutomer to log in and shop .

CHECK OUT
This page shows the available product that was added to the cart, click on
checkout which will redirect you to the last page where you’ll pay.
PAYMENT
Payment is done through paypal click on the paypal icon for transactions.;
In this application we only accept a status of "Completed" and treat all others as
failure. You may want to handle the other possibilities differently
payment status can be one of the following:
 CanceledReversal: A reversal has been canceled. For example,
you won a dispute with the customer, and the fund for the
Completed the transaction that was reversed have been returned
to you.
o Completed:The payment has been completed, and the funds have been
added successfully to your account balance.
Denied:You denied the payment. This happens only if the payment was
previously pending because of possible reasons described for the PendingReason
element:
 Expired: This authorization has expired and cannot be captured.
  Failed: The payment has failed. This happens only if the payment was made
from your customer’s bank account.
 Pending: The payment is pending. See pendingreason for more information.
 Refunded:You refunded the payment.
 Reversed: A payment was reversed due to a chargeback or other type of
reversal. The funds have been removed from your account balance and
returned to the buyer.
 Processed: A payment has been accepted.
 Voided: This authorization has been voided.

USER ADMIN

ADMIN LOGIN
Admin login then is directed to the admin dashbaord
Admin user name: joramsiree73@gmail.com
Password:1234567890
You can always change the password on the admin dashboard.

NB:As the admin you should not share the password

ADMIN DASHBOARD
The admin page where the admin can keep track of cutomers and what they bought
or requests in the comments also he can view product he she wants to add or
delete,check orders.
PRODUCTS
Shows the list of the products admin can delete and add products.

Categories
Admin can manage categories by editing and see the categories of the
products.
BRANDS