1.

Chapter One
1.1 Introduction
E-commerce (electronic commerce) is the buying and selling of goods and services, or the
transmitting of funds or data, over an electronic network, primarily the internet. These business
transactions occur either as business-to-business (B2B), business-to-consumer (B2C), consumer-
to-consumer or consumer-to-business.

E-commerce is powered by the internet. Customers access an online store to browse through
and place orders for products or services via their own devices. As the order is placed, the
customer's web browser will communicate back and forth with the server hosting the e-
commerce website. Data pertaining to the order will be relayed to a central computer known as
the order manager. It will then be forwarded to databases that manage inventory levels; a
merchant system that manages payment information, using applications such as PayPal; and a
bank computer. Finally, it will circle back to the order manager. This is to make sure that store
inventory and customer funds are sufficient for the order to be processed.

Habesha e-commerce allows us to change our product offerings, display, and marketing
materials almost instantly on an e-commerce site. The existing systems lacks data collection
method in which sellers are not bound to know costumers needs. Habesha e commerce will use
features like data, to collect tons of information about how people surf the web, what sorts of
sites they visit, and what kinds of things they purchase and the sellers use that
information to improve the shopping experience and improve the likelihood that their
site’s visitors will turn into customers.

1.2 Background Information

1.21) Background of the project

The main reason we want to implement Habesha e-commerce is to provide a flexible and fast
online marketplace without physically moving things around and also without consuming a lot
of time.

The existing system lacks inventory management in which inventory is monitored and
managed, ensuring re-orders are place as inventory runs low to always be in stock. It also lacks
a delivery system that is available in a wide range of environment. So we want to improve the
existing systems by implementing those services.

1.3 Statement of the problem

The problem is that there are no satisfying services provided by the existing system. As an
example a customer may order a certain product that is already sold but is still on the site since
there is no announcement bar to notify customers sold out products. Also if there is a product
that isn’t quite ready for sale or one that’s been sold old that you want to allow people to be
notified of when it’s back in stock there is no means of achieving those things.

Another problem in the existing system is unavailability of the delivery service . There is only a
delivery service within a bounded km Radius of the seller. In most cases the seller is in charge of
the delivery service not the company. The company only advertises sellers product attaching
their contact or address information after that company won’t get any information regarding
the product whether it is sold or not.

1.4 Purpose of the project

With the evolution of technology and the wave of digitalization more and more businesses are
adapting to technology evolution. Purpose of the projects solving problems stated above. It’s
main goal is to serve a better environment that is advantageous for both sellers and customers
using technologies.

Sellers can do their businesses despite holidays, events, day-night cycles, and geographic
boundaries affecting them. Building an online store with ecommerce platforms can help sellers
streamline their business operations. They can manage sellers inventory, orders, customers,
sales channels, plan & implement marketing strategies to align all the business operations
centrally to attain sellers end goal.

The consumers can also get the right details of the products sellers have at online store. With
online chat, email, telephone sellers can resolve customer queries in real-time to strengthen
their relations with them.

1.5 Objective
1.5.1 General Objective
The general objective of this project is to provide an online area that is convenient both for
sellers and customers in a marketing system. It is a business that implements flexible and
fast services. Sellers can work from anywhere with an Internet connection. They may not
even need to have office space; can work from home.

1.5.2 Specific objectives

 Manage Online Selling Costs in a Strategic Way
 Establish Deeper Business Relationships
  Provide a Unique Customer Experience
 Improve Customer Loyalty
 Provide convenient Shopping Experience
 Provide border less Sales Opportunity
1.6 Feasibility Study
Feasibility study is a study to evaluate feasibility of proposed project or system. Feasibility
study is the feasibility analysis, or it is a measure of the software product in terms of how
much beneficial product development will be for the organization in a practical point of view.

Feasibility Study gives a conclusion of whether to go ahead with proposed project as it is

practically feasible or to stop proposed project here as it is not feasible to develop or to
analyze about proposed project again

Feasibility study helps in identifying risk factors involved in developing and deploying system
and planning for risk analysis also narrows the business alternatives and enhance success rate
analyzing different parameters associated with proposed project development and The
following are major feasibly concerns.

1.6.1 Technical Feasibility

Technical Feasibility study is about evaluating if the current technology has a potential to
develop or unable to support our proposed system. Implementation of the proposed system
will use windows operating system scripting programming language.

The proposed system can use software and hardware tools and other resources that are
accessible by low cost and available for the development and implementation of proposed
system. Therefore, the system is technically feasible.

The team has the ability to develop this system without any difficulty since the team has
studied the required methodologies and tools. So the system will be technically feasible. The
project members also have knowledge about Java, CSS, MYSQL database and Enterprise
architect to design the system.

Besides, the group members have enough capability to develop the project. So the system is
technically feasible. In general using the different techniques, we can perform the work up to
the desire of the organization, even though fulfilling human being’s needs in all directions may
be difficult.
1.6.2 Operational Feasibility

Operational feasibility test is making sure if the system works with less difficulties when
developed and installed. Operational feasibility is mainly concerned with issues like whether
the system will be used if it is developed and implemented. During the installation of the
system, it is easy, likely that the installer can easily install to the environment of the system.
This project is surely operationally feasible because the proposed online system is a good
solution maker of the existing problem or specific solution will work in the existing system and
create a good environment towards both sellers and customers or users in all.

Users can use the system using their hand phones and laptop computer only by connecting it to
the internet since the system is not complicated (simple) and easy to use. The system will be
available only on mobile and laptop computer system therefor users able to run the system on
their devices. Users won’t need much time to adapt the system because the system is much
user friendly and adaptable. And finally, the project is operationally feasible.

1.6.1 Economic Feasibility

Economic feasibility evaluates the cost of the system development against the ultimate income,
or a benefit gets from the developed system. For any system if the expected benefits equal or
exceed the expected costs, the system can be judged to be economically feasible. In economic
feasibility, cost benefit analysis is done in which expected costs and benefits are evaluated.

This is to determine the benefits and savings that are expected from a proposed system and
compare them with costs. If benefits outweigh costs, then the decision is made to design and
implement the system. The proposed system is economically feasible because the proposed
system uses software and hardware tools that are available by low cost and open source
software except for few major hardware components of the central system like the central data
server on but that’s not a problem because the hosting organization that is going to
implement the system is a big governmental organization that can obtain such hardware
components easily and it is going to get by implementing the system that will eliminate the
time and cost consuming process

So, the project is economically feasible because the proposed system can use software and
hardware tools that are accessible by low cost with a limited time.

1.7 Scope and limitation

1.7.1 Scope
Scope of the system can be enumerated as:-
  Buying and selling of products
 Shipping of products
 Producing financial statements
 Exchange of digitized information

1.7.2 Limitation of the project

There are some limitation of Habesha e commerce faces they includes:-

 Late delivery
 Difficulty to buy some products online
 Lack of privacy. A customer has to provide his personal details before making a purchase
like address, name, and phone number and so on.
 Fear People fear the unknown. E-commerce transactions are mostly faceless and
paperless without any due proof.
 Credit card fraud- what if the site is hacked by cyber criminals.
 Dependency on the website
 An e-commerce site is heavily dependent on its website. If it is not properly projected or
the software is not implemented the site can face technology hiccups . 

1.8 Significant of the project

The biggest advantages of the project are the low costs, the flexibility and speed, and the high
levels of data. The websites we use every day collect tons of data about us to learn how we surf
the web, what sorts of sites we visit, and what kinds of things we purchase. If someone running
an e-commerce site, they’ll be able to collect data on how long their customers stay on their
site, what they look at, and how they go about making purchases.

Sellers can use that information to improve the shopping experience and improve the likelihood
that their site’s visitors will turn into customers. It’s much harder to get that information in a
brick-and-mortar store. There’s no record of what every single customer looked at or how long
they spent with a particular product before buying it.

1.9 Methodology
 1.9.1 Fact finding methodology
Fact finding is process of collection of data and information based on techniques which contain
sampling of existing documents, research, observation, questionnaires, interviews, prototyping
and joint requirements planning.

In our case we do some researches or we collect data by visiting some sites with less paper
work .It can save the time if the problem is already solved. We can know how different
person previously solved the same problems and the detailed information about the current
development system.

1.9.2 Software development methodology

Since the time given to finish the project is limited or since it is time-boxed we use Rapid
Application Model to develop the system.

1.9.3 Development tools

2. Chapter Two
2.1 Major functionality of the current system

Currently e commerce’s available in Ethiopia are used only as an advertising site. As said earlier
the company only advertises sellers product attaching their contact or address information
after that company won’t get any information regarding the product whether it is sold or not.

It gives unsatisfying delivery service and in some cases the sellers himself is in charge of the
delivering service.

2.2 User of the current system

Actors involved in the current system are:-

Businesses:

Sell products

Consumers:

Trade products

Administrators:
Organize and run businesses

2.3 Problem of the current system

The current system has many drawbacks which includes availability problems in which the
system is not available 24/7 and it is not also widely available. The system also lacks
recommendations of personalized product since the sites can’t track visitor’s browse; so they
have no idea which item the visitor viewed. It lacks data governance.

There is no updated information for products which are already sold out so consumers still
think the product is available which is not. This leads to loosing of customers. The current
system lacks inventory management in which inventory is monitored and managed, ensuring
re-orders are place as inventory runs low to always be in stock. It also lacks a delivery system
that is available in a wide range of environment.

2.4 Business rule of the current system

The following are business rule of the system:

1. The admin is the one that updates and posts product related information for the consumer to
view
2. The admin is the only user allowed to manage users and any activity related with the system
3. The user should have an internet connection and a computer or smart phone
4. The consumers and the sellers should be registered to access the system
5. Consumers need valid trade warrant to register
6. The seller and buyer could perform the transaction, without shipping service

3 Chapter Three
PROPOSED SYSTEM

3.1 Overview
To overcome the limitations of the existing system Habesha e commerce provides many
services. On Habesha e-commerce site, you can change your product offerings, display, and
marketing materials almost instantly. In a brick-and-mortar store, you’ll have to physically move
things around and it just takes longer. Habesha e-commerce site is extremely flexible and lets
you adapt to the changes needs of your customers and the changing demands of the business
environment.
Finally, Habesha e-commerce business is flexible. As the owner, you can work from anywhere
with an Internet connection. You may not even need to have office space; you can work from
home.

3.2 Functional Requirement

Requirements for e commerce sites can be very different depending on the region a particular
site targets. Functional requirement of our proposed system includes:-

1, seller procures products

2, sellers ships products to the e commerce site

3, customer opens the ecommerce site and order

4, the site receives order

5, customer receives an order confirmation

6, the site ships the order and handle payment details

7, customer receives their packages

3.2 Non Functional Requirement:- are requirements that specify criteria that can be
used to judge the operation of a system, rather than specific behavior. They define how a
system is supposed to be.

1, usability:-includes

 how easily a user can achieve their goal in a single page visit;
 how quickly they perform the tasks in the store;
 how memorable and intuitive the design is; number and time of errors users make.

2, security:-is about different admin roles allowing you to control who can create, see, copy,
change, or delete information. Depending on your business location, security also means
complying with the customer data protection rules. The website must be resilient to any kind of
attacks

3, performance:-Performance should be fast.

4, maintainability:- the system has to be easy-to-maintain right from its launch.

5, scalability:- This requirement defines how the website can grow and expand its functionality
without affecting its performance.

3.4) System model

3.4.1 Scenario
Scenario is a real-life example of how the system can be used. It should include scenario name,
flow of event, what can go wrong and how it is handled. Based on this the following scenarios
for our project are listed below.

1, name of scenario: administration of the system

Participating actors: admin

Flow event:

a. admin open and login to the system

b. he/she enters full name with their password

c. click sign in button or cancel button

d. login to main page

e. admin select manage account tab

f. he/she can edit from the previous data.

g. changes the detail he/she want to update

h. clicks the update button

i. The system displays update successful message

j. selects the delete tab if he/she want to delete the price of the current system or if the available
product is no longer available

k. the system displays deleted message

 names of scenario: registration of sellers

a. registration tab is displayed
b. create account by registration including name, gender, address (like Kebele, woreda),
write available product that he/she has to the market, phone number, password
c. then click the register button
d. the system displays successful message
 e. If the seller already has an account, he/she can sign in by using their username and
password
f. And can see how much the consumer wants to buy the items
3 names of scenario: registration of consumer

A. Registration tab is displayed

B. Create an account by registration of name, gender, address (kebele,woreda…. etc.),
C. If the consumer already has an account, he/she can sign into the system
D. write how much he/she wants to buy the product by viewing the current market by the
admin (by authority bureaus)

3.5 Use case model

3.5.1 Actor identification
1 Admin

 open and login to the system

 control sold out and procured products
 Manage the product catalogue on e-Shop & Company Website
 Build, test and deploy new devices as per the Consumer Devices road map
 Work with Manufacturers to source launch assets
 Liaise with Web Content & Design team on product content & images

2 seller/businesses

 Register
 Post the available product they have
 View the current price
 Make connection to the consumers

3 Consumer
 Sign in if they have account
 Register for new account
 Order what they want to buy and with their price
 Give comment for the admins
4 employee
 in charge of delivery service
 manage the warehouse
 track where items are located
 keep record of products when they arrived
  how long products have been in stock
 the quantity on hand at any given time

use case identification

Our system includes the following use cases:
 Login
 Registration of sellers
 Registration of consumer
 Update the price
 Generate the overall reports
 Giving comments
 Change password
 View detail: used to view all information included under the system, such as:
 View the current balance
 View comments
 View the sellers info
 View consumers info
 Update details: used to update the required information in the system such as:
 Update the price
 Update account and password
 Delete details: use to delete all irrelevant information in the system, such as:
 Delete account
 Delete unavailable products

Use case diagram

Use case id 1

Use case name Login

Actor consumer

Description User must login with a valid id and password in order to buy
products online

Precondition The user is a valid user and has entered his login credentials in
the fields provided

Post condition The user is successfully logged in to the system

Table 3.1 login use case description

Use case id 2

Use case name Authentication/testify

Actor Administration

Description this feature will authenticate weather the user is a valid user or
not by validating if he has already registered or not.

Precondition The user is directed to the login page

Post condition The system are either accept or reject the user’s credentials if
user input is wrong the system give a message “your information
is not available”

Table 3.2 description of use case authentication

Use case id 3

Use case name Add product

Actor seller

Description This feature allows user to add products to the website

Precondition User click on the add question button

Post condition The user add question details in the database

Table 3.3 description of use case add product

Use case id 4

Use case name View price

Actor consumers

Description The feature user to view prices of products

Precondition User click on the price button to see the price of the product they
chooser

Post condition The system summit all the result details in the database

Table 3.4 description of use case view price

3.6 Object Model

3.6.1 Data dictionary
Object model is a description of an object-oriented architecture, including the details of the
object structure, interfaces between objects and other object-oriented features and related
functions.

3.7 Class Diagram

3.8 Dynamic Model

3.8.1. Sequence diagrams

Sequence diagrams in the UML are primarily used to model the interactions between the actors
and the objects in a system and the interactions between the objects themselves. As the name
implies, a sequence diagram shows the sequence of interactions that take place during a
particular use case or use case instance.

The objects and actors involved are listed along the top of the diagram, with a dotted line
drawn vertically from these. Interactions between objects are indicated by annotated arrows.
The rectangle on the dotted lines indicates the lifeline of the object concerned. The annotations
on the arrows indicate the calls to the objects, their parameters, and the return values.
3.9 Activity Diagram

An activity diagram is used to understand the flow of work that an object or component
performs. It can also be used to visualize the interaction between different use cases. One of the
strengths of activity diagrams is the representation of concurrent activities.They are graphical
representations of workflows of stepwise activities and actions with support for choice,
iteration and concurrency. And show the overall flow of control.

Activity diagrams are constructed from a limited number of shapes, connected with arrows. The
most important shape types:

 rounded rectangles represent actions;

 diamonds represent decisions;
 a black circle represents the start (initial node) of the workflow;
 An encircled black circle represents the end (final node).
 Arrows run from the start towards the end and represent the order in which activities
happen.
3.10 State Diagram
State chart diagram is one of the five UML diagrams used to model the dynamic nature of a
system. They define different states of an object during its lifetime and these states are changed
by events. State chart diagrams are useful to model the reactive systems. Reactive systems can be
defined as a system that responds to external or internal events.

State chart Diagrams Basics

 States and Events

 Transitions
 Actions
 Synchronization Bars
 Decision Points
 Complex States
• Composite States
• Concurrent Sub states
• History States
 Transitions to and from Composite States.