Hulu Online Project

Adama science and Technology University
School of Electrical Engineering and Computing
Computer Science and Engineering Program
A senior project Documentation for computer science and engineering:
HULU web and android based online shopping
Group Name ID
Mikiyas Tilahun R/00716/07
Misikir Damenu R/02819/07
Nardos T/Mariam R/00771/07
Abel Tesfaye R/00030/07
Eshita Addisu R/00354/07
Amanuel Mesfin R/00107/07
Submission Date 22/11/18

I
Submitted by
Mikiyas Tilahun __________________________ April 19, 2019
Student Signature Date
Misikir Damenu __________________________ April 19, 2019
Nardos T/Mariam __________________________ April 19, 2019
Abel Tesfaye __________________________ April 19, 2019
Eshita Addisu __________________________ April 19, 2019

______________________
Amanuel Mesfin ____ April 19, 2019
1. Mr.Daniel Tsegaye ___________________________ April 19, 2019
Advisor Signature Date
2. ______________________ ______________________ ____________________

Chairman, Dept.’s Signature Date
Senior project Committee
---------------------------- --------------------------------- ---------------------------------------

Head od dept Signature Date
II
Acknowledgment
We have taken efforts in this project. However, it would not have been possible without the kind
support and help of many individuals and organizations. We would like to extend our sincere
thanks to all of them. We are highly indebted to Adama Science and Technology University for
the opportunity it provided us to work on this project and explore further knowledge. We would
like to express our deepest gratitude towards our advisor Mr. Daniel for his guidance and
constant supervision as well as his kind co-operation and encouragement, which helped us in
completion of this project, which is a Software Requirement Specification (SRS) document. Our
thanks and an appreciation goes to all of those who have willingly supported and helped us out
with their abilities.
Abstract
We study how online competition, with its algorithmic pricing technologies and the
transparency of the Internet, can change the pricing behavior of large retailers and affect
aggregate inflation dynamics. In particular, we show that online competition has raised both the
frequency of price changes and the degree of uniform pricing across locations in the world over
the past 10 years. These changes make retail prices more sensitive to aggregate “nationwide”
shocks, increasing the pass-through of both gas prices and nominal exchange rate fluctuations.
III
Contents
Adama science and Technology University....................................................................................I
Chapter one.....................................................................................................................................4
Introduction of the project process................................................................................................4
1.1 Introduction..............................................................................................................................4
1.2 Background Information..........................................................................................................5
1.3 Statement of the problems........................................................................................................6
1.3.1Mission................................................................................................................................7
1.4 Objectives..................................................................................................................................8
1.4.1 General objective...............................................................................................................8
1.4.2 Specific objective...............................................................................................................8
1.5 Feasibility study........................................................................................................................8
1.5.1 Technical feasibility..........................................................................................................8
1.5.2 Operational Feasibility.....................................................................................................9
1.5.3 Economic Feasibility.........................................................................................................9
1.6 Scope and Limitation..............................................................................................................10
1.6.1 Scopes of the system........................................................................................................10
1.6.2 Limitation........................................................................................................................10
1.6.3 Beneficial of the system...................................................................................................11
1.7 Significance of the project......................................................................................................11
1.8 Methodology............................................................................................................................12
1.8.1 Fact Finding of Methodology.........................................................................................12
1.8.2 System Development Methodologies.............................................................................12
1.9 Testing procedure...................................................................................................................12
1.9.1 Unit testing.....................................................................................................................12
1.9.2 Integration testing.........................................................................................................13
1.10 project plan............................................................................................................................13
1.10.1. Schedule........................................................................................................................13
1.11. Team Composition...............................................................................................................13
1
Chapter Two..................................................................................................................................14
Description of the Existing System..............................................................................................14
2.1 Major Function of the Current System..................................................................................14
2.3 Problems of the current system..............................................................................................16
2.5 Business rule of the current system.......................................................................................17
Chapter 3.......................................................................................................................................18
3.2 Functional Requirements.......................................................................................................19
3.3 .Non-functional Requirements...............................................................................................19
3.4 System Model.........................................................................................................................21
3.4.1. Scenarios.........................................................................................................................21
3.5 Use case diagram and description..........................................................................................39
3.5.1 Description of use case model........................................................................................40
3.6. Object Model..........................................................................................................................50
3.6.1. Data dictionary...............................................................................................................50
3.7. Class diagram.........................................................................................................................52
3.8. Dynamic model......................................................................................................................55
3.9. Activity diagram.....................................................................................................................61
3.10. State chart diagram..............................................................................................................74
Chapter Four.................................................................................................................................86
System design................................................................................................................................86
4.1 overview...................................................................................................................................86
4.2 purpose of the system..............................................................................................................86
4.3 design goal...............................................................................................................................86
4.3.1 Performance....................................................................................................................86
4.3.2 Dependability...................................................................................................................87
4.3.3 Maintenance....................................................................................................................87
4.3.4 End user...........................................................................................................................87
4.3.5 Priorities of the system...................................................................................................88
4.4.1 Overview...............................................................................................................................88
2
System Architecture......................................................................................................................89
Subsystem Description..................................................................................................................93
Chapter one
Introduction of the project process
1.1 Introduction
E-commerce is fast gaining ground as an accepted and used business paradigm. More and more
business houses are implementing web sites providing functionality for performing commercial
transactions over the web. It is reasonable to say that the process of shopping on the web is
becoming common place. The objective of this project is to develop a general purpose e-
commerce store where any products can be bought from the comfort of home through the
Internet. However, for implementation purposes, this paper will deal with an online Shopping
Cart .The Shopping Cart is a virtual store on the Internet where customers can browse the catalog
and select products of interest. The selected items may be collected in a shopping cart. At
checkout time, the items in the shopping cart will be presented as an order. At that time, more
information will be needed to complete the transaction. Usually, the customer will be asked to
fill or select a billing address, a shipping address, a shipping option, and payment information
such as visa card number. An e- mail notification is sent to the customer as soon as the order is
placed.
Private customer and business customers can order the selected products of the Shopping Cart
service online quickly and comfortably. Target groups of customer of the Shopping Cart are. The
customers can have a payment option through visa card only. In order to use the load writing
procedure, the customer registers itself and receives a login for its purchases name. It is an
3
Internet application. Electronic Commerce (e-commerce) applications support the interaction
between different parties participating in a commerce transaction via the network, as well as the
management of the data involved in the process.
1.2 Background Information

The history of ecommerce started 40 years ago and, to this day, continues to grow with new
technologies, innovations, and thousands of businesses entering the online market each year.
Electronic Data Interchanges and teleshopping in the 1970s paved the way for the modern day
ecommerce store. The history of ecommerce is closely intertwined with the history of the
internet. Online shopping only became possible when the internet was opened to the public in
1991. Amazon.com was one of the first ecommerce sites in the US to start selling products
online and thousands of businesses have followed since. The convenience, safety, and user
experience of ecommerce have improved exponentially since its inception. Absence of E-
payment Hampers the Development of Online Business in Ethiopia. It’s no secret that the
Internet has changed the way companies do business. E-payment in particular has helped
multinational companies like Amazon and e-Bay expand their enterprises and become household
names, while on-line marketing has increased in Ethiopia, it still has a long way to go.
Technology has changed the way people live and the activities they pursue in their day-to-day
lives. The application of information communication technologies (ICT) has made it easy and
convenient for people to do businesses that would have once cost a lot of time and money.
Online shopping now has enabled people in many parts of the world to buy and sell things
quickly, expanding opportunities for companies to do business worldwide.
An increasing number of companies consider online marketing one of the main strategies to
promote and sell their products. Multibillion international companies like Amazon and eBay, for
example, are engaged in online marketing all over the world.
Electronic commerce is in its infancy in Ethiopia and is rarely used. The Government of Ethiopia
(GOE) is preparing a draft national law to govern e-Commerce. Ethiopian banks use debit cards
and automated teller machines (ATM) but have not begun to issue credit cards. Most Ethiopians
do not have credit cards and internet connections are slow, expensive and unreliable. However,
internet service has recently improved as a result of Ethiopia's connection to Seacom's
4
underground/sea fiberoptic cable through Djibouti. ATMs are interconnected with international
banking networks. International ATM cardholders are able to withdraw funds from any ATM
machine of the 18 commercial banks operating in Ethiopia. ET Switch S.C., a shared ownership
company with the commercial banks, was created to improve bank-to-bank integration. Even in
Ethiopia, despite numerous barriers to technology use, many are using online marketing as a
means of reaching potential buyers. Used car importers and dealers as well as real estate brokers
are exploiting the new way of marketing. They employ internet marketing to advertise and
promote goods and services and also to communicate with potential buyers.
Business developers usually give the services for free then start charging fees when a substantial
amount of viewers start viewing the site.
1.3 Statement of the problems

Online shopping — that glorious invention which allows people to buy things from the comfort
of their homes. No more travelling to multiple stores to find the right product; no more having to
deal with over-enthusiastic sales persons; no more standing in long lines at the checkout counter.
The ecommerce boom has certainly changed the way we shop for the better. But, like everything
else, the world of online shopping is not all roses. Despite all the efforts of e-commerce
companies to alleviate them, there are a few problems that customers still have to face while
shopping online. Six of these problems are listed below.
Quality issues
The biggest problem while buying things online is that you have no guarantee of a product's
quality. Reviews are not always reliable and all the research can't assure you of a product's
quality; fraudulent sellers who intentionally mislead customers to increase sales are the prime
reason for faulty/sub-par products being sold online. With the volume of goods e-commerce
companies handle these days, it can be quite difficult for them to conduct quality checks on each
and every one of the products they're selling.
Delivery and logistics
5
One predicament that constantly turns up while shopping online is when the order will be
delivered. While all e-commerce sites have order tracking systems for their customers, they
aren’t always accurate.
Digital payment failures
The failure of digital payments always looms overhead while making online transactions. A
faltering internet connection or a technical glitch often results in the payable amount being
debited from a customer's account without being credited to the selling party
Unclear return and guarantee policies
Since you have no idea of product's quality until you hold it in your hands, returning things
bought online is quite common. Unless you're buying from one of the established e-commerce
companies it's important to go through the return policy while making a purchase.
Problem of Plenty
The online world provides too many options and it can be overwhelming for the customer to
make a choice. The absence of support that most customers are used to in the in-store experience
is missing and this can chicken out them of a purchase decision.
Complicated Navigation
Many online shopping organization may have a complicated navigation system.
1.3.1Mission
Our mission statement is “We strive to offer our customers the lowest possible prices, the best
available selection, and the utmost convenience.” This corporate mission promises attractive e-
commerce services to satisfy target customers’ needs. The company focuses on the variables of
price, selection, and convenience. In this regard, the following characteristics are identifiable in
Hulu’s corporate mission statement:
6
1. Lowest prices
2. Best selection
3. Utmost convenience
1.4 Objectives
1.4.1 General objective
The general objective of this project is to develop web and android based online shopping system
1.4.2 Specific objective

In order to fulfill the above General objectives, we need to accomplish the following specific
objectives.
 Design and implement online shopping web and android based system.
 Manage Transaction will be carried on time.
 To develop a system that enable customers to purchase and merchants to sell online.
 Develop the detail description of the items and product.
 Manage and Recording the data for sold customer.
 Making the advertisement of the product.
 Manage customer order.
1.5 Feasibility study

Preliminary investigation examines project feasibility; the likelihood the system will be useful
to the organization. The main objective of the feasibility study is to test the Technical,
Operational and Economical feasibility for adding new modules and debugging old running
system. All system is feasible if they are unlimited resources and infinite time. There are aspect
in the feasibility study portion of the preliminary investigation.
1.5.1 Technical feasibility

The Technical issue usually raised during the feasibility stage of the investigation includes the
following:
 Does the necessary technology exist to do what is suggested?

 Do the proposed equipment’s have the technical capacity to hold the data required to use
the new system?
 Will the proposed system provide adequate response to inquiries, regardless of the
number or location of users?
7
Are there technical guarantees of accuracy, reliability, ease of access and data security?
Earlier no system existed to cater to the needs of ‘Secure Infrastructure Implementation System’.
The current system developed is technically feasible. Thus, it provides an easy access to the
users. The database’s purpose is to create, establish and maintain a work flow among various
entitie. Permission to the users would be granted based on the roles specified. Therefore, it
provides the technical guarantee of accuracy, reliability and security. The software and hard
requirements for the development of this project are not many and are already available in-house
at NIC or are available as free as open source. The work for the project i s d o n e w i t h the
current equipment and existing software technology. Necessary bandwidth exists for providing a
fast feedback to the users irrespective of the number of users using the system.
1.5.2 Operational Feasibility

Proposed project is beneficial only if they can be turned out in to information system. That will
meet the organization’s operation requirements. Operational feasibility aspect of the project are
to be taken an important part of the project implementation. Some of the important issues raised
are to test the operational feasibility of a project includes the following
•Is there sufficient support for the management from the users?
•Will the system be used and work properly if it is being developed andimplemented?
Beforehand, the management issues and user requirements have been taken intoconsideration. So
there is no question of resistance from the users that can undermine the possible application
benefits. The well-planned design would ensure the optimal utilization of the computer resources
and would help in the improvement of performance status
1.5.3 Economic Feasibility

A system can be developed technically and that will be used if installed must still be a good
investment for the organization. In the economic feasibility, the development cost
In creating the system is evaluated against the ultimate benefit derived from the new systems.
Financial benefits must equal or exceed the cost.
8
The system is economically feasible. It does not require any addition hardware or software.
1.6 Scope and Limitation

1.6.1 Scopes of the system.
The proposed system includes the following systems
 Delivery system_ means we deliver the product for the one how purchase it
from our site.
 Taxation system_ our system will also provide tax for all commodities based
on countries taxation rule.
 Payment system_ our system will have different types of making payement.
 Ordering system_ the system make order for the purchased item.
 Complain management system_ the system will recive comment from the
customer.
 Professional sellers can give priority to Employee authorization
 Ease of use_ our system more flexible to use.
 Content management capabilities
 Reporting_ all employees make report for their task.
 Advertisement and promotion we will advertise the seller item promotion .
 Wish list_ in our system the customer have a chance to wish the item they
want.
 Search engine optimization_ there will be search button to search an item to
find their feelings.
 Real time inventory_ make inventory on the purchased item and the left item
on the store.
 Special offers_ seller may give special offer for there item in our system.
 Checkout_ the system will check the item is deliver for the purchased person.
 Mobile friendly.
9
1.6.2 Limitation
 Since we can’t receive a recite we don’t have knowledge for seller to verify the item
is his.
In order to use this system, user needs to have basic computer knowledge
1.6.3 Beneficial of the system
 It saves time! Time that can be used in other activities.
 You get a larger variety to shop from and you know all your options (well most of).
 You can shop from literally anywhere in the world.
 This allows you to buy stuff that’s not available in your city.
 You can compare prices instantly and get the best value.
 You can make a better decision using reviews.
 You can instantly avail promotions and discounts.
 It saves energy and cost that would be needed to go to a retail shop.
 You get delivery wherever you want.
 Easier refund process.
1.7 Significance of the project

The significance of the study is to create an online shop system that will provide secure services
to customers, easy to use and provide different features of Hulu online shopping system. If this
project is implemented, it has a potential to make a difference in online shopping system process
trend by the following ways.
 To provide a well-structured online shopping system to fulfill what customer
needs.
 Delivery system or make a pay of delivery.
 Generate a tracking number which will be used to uniquely identify the product.
 Provide a well-structured data-handling system.
 Provide Fulfilled by Hulu, Fulfilled by merchant, easy shipping, and pickup
system, Hulu vendor.
10
 Provide different types of payment system.
1.8 Methodology
The first and the most valuable data source of our system is the current system of online
shopping system which is used to provide different features to the customers.
1.8.1 Fact Finding of Methodology
Document analysis: It describes the act of reviewing the existing documentation of comparable
business processes or systems in order to extract pieces of information that are relevant to the
current project, and therefore should be consider projects requirements.
1.8.2 System Development Methodologies
In the system development methodology of a project we have used the component based
approach in which all system processes are placed into separate components so that all of the
data and functions inside each component are semantically related. Because of this principle, it is
often said that components are modular and cohesive.
Constraints
Shortage of resource: the system does not handle all the complex activities and histories of
individuals. The users of the system will have limited access to the system.
1.9 Testing procedure

1.9.1 Unit testing
In this phase of testing we will try to eliminate faults in procedure and functions point of view
by using black box and white box testing. Tasks that we will perform under this phase
 Prepare unit test plans.
11
 Identify the unit test objectives.
 Prepare test cases that includes information such as set of test inputs, execution condition
and expected output
 Perform the tests according to our plan
 Analyze the test results
 Document the test results.
1.9.2 Integration testing
In this phase we have focused on how individual software modules are combined and tested as a
group. It occurs after unit testing. Tasks that we have performed under this phase
 Prepare integration test plans

 Identify integration test objectives.
 Identify integration test acceptance criteria.
 Perform the tests according to our plan
 Document the test results.
1.10 project plan

1.10.1. Schedule
months
Phases February1 May June July July

–April 18 1_june 2_june 1_july 16-
1 30 15 july 29
Requirement 
gathering and
Analysis
Design 
Implementatio 
n
Testing 
12
Maintenance 
1.11. Team Composition
HULU ONLINE SHOPPING
No Name Id Responsibility
1 Nardos Teklemariam r/00771/07 Requirement
Gathering,
analysis, design,
implementation
and Testing
2 Mikiyas Tilahun r/00716/07 Coordinating,
Designing ,analy
sis,
implementation
and
Programming
3 Abel Tesfaye r/0030/07 Requirement
Gathering,
analysis, design,
implementation
and Testing
4 Misikir Damenu r/002819/07 Programming, ,a
nalysis, design,
implementation
and Testing
5 Eshita Addisu r/00354/07 Requirement
Gathering,
Designing, ,analy
sis,
implementation
and Testing
6 Amanuel Tesfaye r/00106/07 Requirement
Gathering
13
Chapter Two
Description of the Existing System
2.1 Major Function of the Current System
The major function of the existing system is to sell and buy products using the online shopping
system including limited payment and delivery options.
Function of the Current systems are
- Providing platform to sell and buy products

- Seller register to the system
 Fill seller form with item description

- Buyer register to the system
 Fill a buyer form with account number
- Provide limited payment options

- Provide limited delivery options
2.1 User of the current system

14
1. Consumer - to - Consumer (C2C)
2. Business - to - Business (B2B)
3. Consumer - to - Business (C2B)
4. Business - to - Consumer (B2C)
1. Consumer - to - Consumer (C2C)
The C2C business model helps consumers to sell their assets like residential property, cars,
motorcycles, etc., or rent a room by publishing their information on the website. Website may
or may not charge the consumer for its services. Another consumer may opt to buy the product
of the first customer by viewing the post/advertisement on the website.
2. Business - to - Business (B2B)
The B2B business model sells its products to an intermediate buyer who then sells the product
to the final customer. As an example, a wholesaler places an order from a company's website
and after receiving the consignment, sells the end product to the final customer who comes to
buy the product at one of its retail outlets.
3.Consumer - to - Business (C2B)
C2B is another model most people don’t immediately think of, but that is growing in prevalence.
This type of online commerce business is when the consumer sells goods or services to
businesses, and is roughly equivalent to a sole proprietorship serving a larger business.
4.Business - to - Consumer (B2C)
The B2C business model sells its products directly to a customer. A customer can view the
products shown on the website. The customer can choose a product and order the same. The
15
website will then send a notification to the business organization via email and the organization
will dispatch the product/goods to the customer.
2.3 Problems of the current system
1. An absence of Online Identity Verification
When a visitor visits an e-commerce website and signs up, the portal is unaware of the customer
except for the information he/she entered. The customer is genuine or not is questionable. This
creates huge revenue losses for a company when a customer makes a Cash-On-Delivery (COD)
purchase and the information entered like phone number, the address is invalid or fake.
2. Competitor Analysis
In this competitive world, there will be too many competitors who will be offering same products
and service as you. Unless you have the best strategy that differentiates yourself from other
competitors; it will become difficult to survive.
3. Maintaining customer’s loyalty
No matter how attractive or fancy your website looks, if you would not be able to build the
customer trust and loyalty, the business has to struggle another day!
It’s the work of lots of efforts for companies to make a new a customer and maintain the same
customer for a long time. One of the reasons why ecommerce companies face the struggle while
building trust and loyalty with the customer is because a seller and a buyer don’t know each
other nor they can see each other while making a transaction, unlike street-shopping. It takes few
transactions, time and plenty of efforts by the company to build the customer trust and loyalty.
4. Lack of Customer Support

Still many websites don’t provide proper customer support after the purchase or while doing
online shopping. While shopping customer may get stuck in between or may get confused about
16
the size of the product and may want to discuss but there is not quick support provided by the
websites. They should provide a telephone number where the customer can contact immediately
or online chat should be available. Online stores provide email address but it’s not sufficient as
you may not get the reply immediately or may not get the reply at all.
5.Additional charges
How many times has it happened that you've spotted a great deal on a product and when you're
one click away from purchasing it you noticed an additional shipping charge. This is
commonplace on all e-commerce sites when your order amount isn't high enough to qualify for
free shipping. And even when it is, sometimes these shipping charges are added on each
individual product (if you're buying multiple products of course) and not the collective order.
6.Unclear return and guarantee policies
Since you have no idea of product's quality until you hold it in your hands, returning things
bought online is quite common. Unless you're buying from one of the established e-commerce
companies, it's important to go through the return policy while making a purchase. But most sites
have vague return policies that can leave you with a low-quality product and no way to return it.
The same applies for guarantees, as most sites don't clearly mention what the policy is for a
product and then refuse to carry out replacements if you receive a damaged product.
2.5 Business rule of the current system
The business rule of the current system is mostly
C2C Ecommerce
Created by the rise of the ecommerce sector and growing consumer confidence in online sales,
these sites allow customers to trade, buy, and sell items in exchange for a small commission paid
to the site. Opening a C2C site takes careful planning.
Despite the obvious success of platforms like eBay and Craigslist, numerous other auction and
classified sites (the main arenas for C2C) have opened and quickly closed due to unsustainable
models.
17
B2B Ecommerce
A B2B model focuses on providing products from one business to another. While many
ecommerce businesses in this niche are service providers, you’ll find software companies, office
furniture and supply companies, document hosting companies, and numerous other ecommerce
business models under this heading.
B2C Ecommerce
The B2C sector is what most people think of when they imagine an ecommerce business. This is
the deepest ecommerce market, and many of the names you’ll see here are known quantities
offline, too. B2C sales are the traditional retail model, where a business sells to individuals, but
business is conducted online as opposed to in a physical store.
C2B Ecommerce
C2B is another model most people don’t immediately think of, but that is growing in prevalence.
This type of online commerce business is when the consumer sells goods or services to
businesses, and is roughly equivalent to a sole proprietorship serving a larger business.
Chapter 3
3.1. Proposed System.
Due to rapid changing society people are leading busy lives having no time to go to shops and
buy necessary things. So, purchasing products through internet is preferred. The online shopping
is an easy to maintain, ready to run, scalable, affordable and reliable cost saving tool from
software associates suited for small, medium and large market and daily markets.
The proposed system can be used by everyone and it does not require
Any educational level, experience, and technical expertise in computer filed but it will be of
good use if the user has the good knowledge of how to operate a computer.
18
With this project is to make buying easier without wasting time. we are engaged in various
of online shopping to all classes of people with the great deals. online shopping tries to enhance
access to care and improve the continuity and efficiency of services.
3.2 Functional Requirements
 Login
 Sign up
 Taxation
 Reporting
 Post product
 Verify
 Make a request
 Category a product
 Identify illegal action
 Order
 Give feedback
 Register
 Manage branch manager
 Manage inventory reporting
 Organizing order
 View product
 Tracking product
 Manage employee
 Help customer
 Deliver a product
3.3 .Non-functional Requirements
User interface and human factors

 Our site provides a good graphical user interface
Performance Requirements
 The system shall accommodate high number of items and users without any fault.
 Responses to view information shall take no longer than 5 seconds to appear on the
screen.
19
Safety Requirements
 System use shall not cause any harm to human users.
 The product which is posted on our site have guaranty or specification.
Security Requirements
 System will use secured database.
 Normal users can just read information but they cannot edit or modify anything except
their personal and some other information.
 System will have different types of users and every user has access constraints.
 Our System will have different types of making payment ways that helps the
customer
Performance characteristics
Scalability; any number of users can be able to access at a time
All the details of the user should be stored securely
Its response to the user should be very fast and accurate.
Error handling
 OFS shall handle expected and non-expected errors in ways that prevent loss in
information and long downtime period.
 System handles exception by notifying them to the users.
 Administrator should continually check flaws and maintains it
IMPLEMENTATION REQUIREMENT
 Implementation of the system using CSS and html in front end with jsp as back
end and it will be used for database connectivity. And the database part is
developed by MySQL. Responsive web designing is used for making the website
compatible for any type of screen.
System modification
This system flexible but the only thing is that the modification is done by
administrator only.
Physical environment
20
It can be developed anywhere. It works at room temperature .it can be acceded by
anyone anytime
Resource issues
Resource of the computer should meet the hardware consideration. anything less than
this is not sufficient for proper functioning of the system.
Performance Requirement
Performance requirements define acceptable response times for system functionality.
 The load time for user interface screens shall take no longer than thirty seconds.
 The log in information shall be verified within five seconds.
 Queries shall return results within five seconds.
3.4 System Model
Used to construct an abstraction of a system that focuses on interesting aspects and ignores
irrelevant details. Our system includes three types of system model. Those are
1. Functional model (scenario, use case model)

2. Object model (class diagram)
3. Dynamic model (sequence, activity and state chart diagrams).
3.4.1. Scenarios.
Scenario: 1
Name of use case: log in
Participating instance actor: user.
21
Entry condition:
 Internet connection have to be available.

 They have to navigate to www.huluonlineshopping.cpm.
 The user has a valid username/password and must login with its own user name and
password which recognize by the system.
Flow of events 1:
Participating actor: - all users Flow event:-
a. The user opens the system.
b. The user enters a valid username and password.
c. The login form is displayed to the user.
d. The user clicks the login button. e. The user display user page
Exceptional flow:- a. If the user does not fill the correct username and password, the system
notifies to enter correct username and password.
b. The system does not work when the connection is not available/
Scenario: 2
Name of use case: sign up
Participating instance actor: admin
Entry condition:

 They have to navigate to www.huluonlineshopping.com.
22
Flow of events:
1. The Admin open and login to the system
2. Users page displayed to the user
3. Admin select register employee tab.
4. Registration form is displayed.
5. He/she fills the correct value to the form
6. Click register button.
7. The system display successful message
Alternate conditions:
 If he/she fills the form incorrectly then the system will generate an error message.
Exit condition: The system saves the entered data into database.
Special requirement: any web browser have to be installed.
Scenario: 3
Name of use case: advertisement and promotion
Participating instance actor: admin
Entry condition:

 They have to navigate to www.huluonlineshopping.com.
23
Flow of events:
1. The Admin open and login to the system
2. Users page displayed to the user.
3. Admin receives advertisement and promotion issues from seller.
4. Admin post the advert.
Name of use case: Track the product.
Participating instance actor: Admin.
Entry condition:



Flow of events:
1. The Admin open and login to the system.
2. The Admin check the track .
24
Scenario: 4
Name of use case: check illegal action.
Participating instance actor: Admin.
Entry condition:
Flow of events:

2. The Admin check the the illegal action .
25
 The applied user has been already registered or fulfil entire information
Scenario: 6
Name of use case: sales
Participating instance actor: Admin

2. The Admin receives the product.
3. The Admin post the product.
Entry condition:
26
Scenario: 7
Name of use case: Verification.
Participating instance actor:Admin.
Entry condition:
Flow of events:
1. Admin inserts username and password.
2.Clerk Login in to the system.

3.Admin verify professional seller.

27
Scenario: 8
Name of use case:order
Participating instance actor: buyer
Entry condition:



Flow of events:
1. Buyer inserts username and password.
2. Click login button to log into system.
4. Choose shipping option.
3. View the product catalogue.
4. Order the product.
5. Make payment.
6. Check out.
28
Scenario: 9
Name of use case: categorise a product
Participating instance actor: store clerk.
Entry condition:



Flow of events:
1. Clerk inserts username and password.

3. Add, update and delete category.
4. Logout from the site.

.
Scenario: 9
29
Name of use case: managing order
Participating instance actor: store clerk.
Entry condition:



Flow of events:

3. Receive order from buyer and packed it.
4. Give to delivery guy.
Scenario: 11
Name of use case: manage inventory
30
Participating instance actor: Store clerk
Entry condition:



Flow of events:
1.Clerk inserts username and password.

2.Click login button to log into system.
3.Calculate the product which is in store and which is sealed from the store.
4.Logout from the site.

Scenario: 11
Name of use case: manage inventory

Participating instance actor: Store clerk
Entry condition:
31



Flow of events:
1.Clerk inserts username and password.

3.Calculate the product which is in store and which is sealed from the store.
Scenario: 12
Name of use case: Deliver the product.

Participating instance actor: Delivery clerk.
Entry condition:



32
Flow of events:

3. Receive order from the store clerk.
4. Deliver the product to the buyer.
Scenario: 13
Name of use case: Chat with customer.

Participating instance actor: Help desk
Entry condition:



33
Flow of events:

3. Receive questions (what to help?) from the customer.
4. Answer the quistions.
Scenario: 14
Name of use case: Manage tax.

Participating instance actor: Finance clerk.
Entry condition:



34
Flow of events:

3. Receive questions (what to help?) from the customer.
4. Answer the questions.
Scenario: 15
Name of use case: Manage reports.
Participating instance actor: Finance clerk.
Entry condition:



35
Flow of events:

3. Receive reports from the user.
4. Organize reports.
Scenario: 13
Name of use case: registration
Participating instance actor: registration admin.
Entry condition:



36
Flow of events:
1. Admin inserts username and password.

3.control all registration.

Scenario: 14
Name of use case: Manage employee.
Participating instance actor : Branch manager:
Entry condition:



Flow of events:
1. Manager inserts username and password.

37
3. Manage delivery clerk.
4. Manage Finance clerk.
5. Manage Warehouse clerk.
6. Manage Store clerk
8. Logout: manager must logout of the site after visit site.

Scenario: 17
Name of use case: view product
Participating instance actor: Customer
Entry condition:



Flow of events:
1. User inserts username and password.

38
3. User view the product.
3.5 Use case diagram and description
A use case diagram illustrates a set of use cases for a system, the actors of these use cases,
the relations between the actors and these use cases, and the relations among the use cases.
The UML notation for a use case diagram is shown on the figure, in which
 An oval represents a use case,
 A stick figure represents an actor,
 A line between an actor and a use case represents that the actor initiates and/or
participates in the process.
39
3.5.1 Description of use case model
Use description for login
Use case name Login
Use case number 1
Description This use case describes how users gain access to the e-Store system through
the login/registration process.
Participating actor All user registered
Pre-condition Internet connection have to available.

They have to navigate to www.huluonlineshoppping.com
40
Flow of event 1. The user browses to the "Sign In" page.
2. The user enters his/her username and password in the returning user
section of the "Sign In" screen.
3. The system validates the username and password (successfully) and
displays the user's account information page.
Alternative flow of  If he/she fills the form incorrectly then the system will generate
event an error message
 The applied user has been already registered or fulfill entire
information.
Post condition The system saved the entered data in to database.
Use case description for Sign up

Use case name Sign up
Use case number 2
Description
Register seller and buyer of the system.
Participating actor Seller, buyer
Pre-condition Internet connection have to be available.

They have to navigate to www.huluonlineshopping.com
Flow of events 1. User insert user name and password

2. User login to system.
3. Click “add seller and buyer” button to register new seller and
buyer.
4. The system displays the registration in form.
5. Fill the form and click OK button.
6. Seller or buyer register in to the system.
7. Choose seller option between individual and professional seller
8. Post their product or goods.
41
Alternative flow of event If he /she fills the form incorrectly then the system will
generate an error message
Post condition The system saved the entered data in to database.

Use case for taxation
Use case name Taxation

Use case number 3
description Control tax
Participating actor Finance clerk

Pre-condition Internet connection have to be available.
Flow of events 1. Finance clerk inserts username and password.
3. Control taxation issues.
Alternative flow of events If he/she fills the form incorrectly then the system will generate an error
message.
Post condition The system saved the entered data into database
Use case description for report

Use case name Report
Use case number 4
descriptions Announce their task.
Participating actor seller, system admin
42
Pre-condition Internet connection has to be available
They have to navigate www.huluonlineshopping.com
ss 1.User inserts username and password.
2. User login into the system.
3User report their task.
4Log out
Alternative flow of event If he/she fills the form incorrectly then the system will generate an error
message.
The applied user has been already registered or fulfill entire information.
Post condition The system saves the entered data into database.
Use case description for post

Use case name Post
Use case number 5
description Advert or promote product.

Participating actor Seller, system admin
Pre-condition Internet connection has to be available

They have to navigate www.huluonlineshopping.com
Flow of events 1. user inserts username and password
2 User Login in to the system.

3.post product.
4. Log out
43
Use case description for verification
name of use case Verification
Use case number 6
description Verifying professional seller.
Participating actor System admin
Pre-condition Internet connection has to be available.

Flow of events 1.clerk inserts username and password.
2.clerk Login in to the system.

3.verify professional seller.
4Log out.
Alternative flow of event If he/she fills the form incorrectly then the system will generate an error
message.
The applied user has been already registered or fulfill entire information.
Post condition The system saves the entered data into database
Use case description for Make request
name of use case Make request

Use case number 7
description
Participating actor Buyer seller
Pre-condition 1. Internet connection have to be available
44
2. They have to navigate to www.huluonlineshopping.cpm.
Flow of events 1 buyer, seller inserts username and password.

2. Click login button to log into system
3. make request.
4. Logout from the site
Alternative flow of event  If he/she fills the form incorrectly then the system will
generate an error message.
 The applied user has been already registered or fulfil
entire information
Use case description for Categories a product
name of use case Categories a product

Use case number 8
description
Participating actor Store clerk
Pre-condition  Internet connection have to be available.

Flow of events . 1Clerk inserts username and password.
3.add, update and delete category.
Alternative flow of event  If he/she fills the form incorrectly then the system will
generate an error message.
Use case description of Identify illegal action

name of use case Identify illegal action
Use case number 9
description Control unnecessary action
45
Flow of events 1.Clerk inserts username and password.
3.Manage user who take un necessary action.
Alternative flow of event If he/she fills the form incorrectly then the system will generate
an error message.
Use case description of order

name of use case Order
Use case number 10
description
Participating actor Buyer
Flow of events 1.Buyer inserts username and password.
3.Order the product.
Alternative flow of event If he/she fills the form incorrectly then the system will generate an
error message.
Use case description of Give feedback

name of use case Give feedback
Use case number 11
description
Participating actor seller, buyer
Flow of events 


 The user has a valid username/password and must login
with its own user name and password which recognize by
the system.
46
Flow of events:
1Seller, buyer inserts username and password

3.Give feedback.
4Logout from the site.
Alternative flow of event If he/she fills the form incorrectly then the system will generate an
error message.
Use case description of registration

name of use case Registration
Use case number 12
description
Flow of events 1. Admin inserts username and password.
3.control all registration.
Alternative flow of If he/she fills the form incorrectly then the system will generate an
event error message.
Use case description of Manage branch employee
name of use case Manage branch employee
Use case number 13
description Control employee
Participating actor Branch manager
Flow of events 1Manager inserts username and password.
3. Manage delivery clerk.
4. Manage Finance clerk.
5. Manage Warehouse clerk.
6. Manage Store clerk
7. Manage Sales clerk
8. Logout: manager must logout of the site after visit site
47
Use case description of Manage inventory

name of use case Manage inventory
Use case number 14
description
3. make an inventory.
Use case description of Organize order

name of use case Organize order
Use case number 15
description
Participating actor System ad
Use case description of View product

name of use case View product
Use case number 16
description
48
Participating actor Seller, buyer, visitor
Pre-condition  Internet connection have to be available
Flow of events 1.User inserts username and password.
3. User view the product.
Use case description of Tracking product

name of use case Tracking product
Use case number 17
description
Flow of events 1. Clerk inserts username and password.
3. Receive request from buyer.
4.. Track the product.
Use case description of Manage employee

name of use case Manage employee
Use case number 18
description Control employee
Participating actor Branch manager
Flow of events 1.Manager inserts username and password.
3. Manage all employees.
4. Logout from the site
49
Use case description of Help customer

name of use case Help customer
Use case number 19
description
Participating actor Help desk clerk
3. Help customer.
Use case description of Advertise and promote clerk

name of use case Advertise and promote clerk
Use case number 20
description
Participating actor System clerk
Flow of events 1. clerk inserts username and password
2. Click login button to log into system
3. Advertise and promote clerk for seller
Use case description of delivery product

name of use case Deliver product
Use case number 21
description
50
Participating actor Delivery clerk
Flow of events 1.Manager inserts username and password.
3. Employee delivers the product which is ordered by dispatch
clerk.
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 functions.
38
Table: object class
Classes Attributes Operations Description
Authenticate Id Authenticate() Authenticate the

Log users of the system
51
Login Username Login() Logs the user into
Password the system.
Reset Username , Email , Send Password Reset Link() Allows the users to
password Security question verify Security Question() reset they password
Validate Email() in case they forget
they password.
Access level Id Allow Access() Allow Access()
Deny Access() deny Access()
Set Access Level() set Access Level()
get Access Level() get Access Level()
Sign up User name Login() Allow Users to
Pass word Get Access() access , sign up,
Current location Logout() register and to
Register() request new
Forgot Password() password in order to
use the system
Seller User name Login() Allow Users to
Pass word Get Access() access , login ,
Current location Logout() register and to
Register() request new
Forgot Password() password in order to
use the system
Taxation User name Login() Allows the finance
Pass word Get Access() clerk to control the
Logout() taxiation.
.
Reporting User name Login() Allows to create the
Pass word Get Access() report.
Make report()
Logout()
Advertisement and User name Login() Allows the Admin,

promotion Pass word Get Accsess() advertisement clerk,
Make post() to post.
Logout()
verify User name Login() Allows the Admin

Pass word Get Access() to verify the
Check the account() account.
Logout()
Identify illegal action User name Login() Allows the Admin

Pass word Get Access() to control illegal
52
Identify illegal action action.
Logout()
Manage order User name Login() Allows the store

Pass word Get Access() clerk to order.
Make order()
Logout()
Give feedback User name Login() Allows the r and

Pass word Get Access() buyer to give
Make a feedback(). feedback.
Logout()
Admin User name Register () Allows the admin to

Pass word View project status() Give register new user..
Comment() manage
Account()
Branch manager User name Login() Allows the manager
Pass word Get Access() to control
Manage branch employees employees.
().
Logout()
View item User name Login() Allows the user to

Pass word Get access to view view item.
products().
Logout()
Help customer User name Login() Allows the help
Pass word Get Access to help user() desk clerk to help
Logout user.
Deliver the product User name Login() Allows the delivery
Pass word Get Access() clerk to deliver the
Logout product.
3.7. Class diagram

We use class diagram to describe the structure of a system by showing the system's classes, their
attributes, operations (or methods), and the relationships among objects. For designing of Class
diagram, we have used Unified Modelling Language (UML). This diagram is the main building
block of our object-oriented modelling. The team applies it for both general conceptual
modelling of the systematic of the application, and for detailed modelling translating the models
into programming code. The classes in a class diagram represent both the main objects,
interactions in the application and the classes to be programmed. In the system, Classes are
53
abstractions that specify the attributes and behaviour of a set of objects and Objects are entities
that encapsulate state and behaviour. Each object has an identity: It can be referred individually
and is distinguishable from other objects. In mapping the diagram, we have used the following
criteria:
54
55
3.8. Dynamic model
3.8.1. Sequence diagram
A sequence diagram shows object interactions arranged in time sequence. It depicts the objects
and classes involved in the scenario and the sequence of messages exchanged between the
objects needed to carry out the functionality of the scenario. Sequence diagrams are typically
associated with use case realizations in the Logical View of the system under development.
Sequence diagrams are sometimes called event diagrams or event scenarios.
A sequence diagram shows, as parallel vertical lines (lifelines), different processes or objects that
live simultaneously, and, as horizontal arrows, the messages exchanged between them, in the
order in which they occur. This allows the specification of simple runtime scenarios in a
graphical manner.
1. Registration
56
Figure 3 sequence diagram for registration.
2.Delivery
Figure 4.sequence diagram for delivery of order.

3. creat report
57
Figure 5.sequence diagram to create report.
4. Taxiation
58
Figure 6.sequence diagram to check tax.
5. Post
59
Figure 7.sequence diagram to post item.
6. Manage employee
60
Figure 7.sequence diagram to control branch employee.
6. Manage order.
61
Figure 8.sequence diagram to manage order..
3.9. Activity diagram

1. Login
62
63
Figure 6 Activity diagram for login
2. sign up
64
Figure 7 Activity diagram for sign up.
3. Post
Figure 7 Activity diagram for post.

65
4. Order
Figure 8 Activity diagram to order.
5. Catagory
66
67
Figure 8 Activity diagram to category.

6. Delivery
Figure 9 Activity diagram for delivery
7. Incorrect action
68
Figure 9 Activity diagram for incorrect action.
8. Taxiation
69
Figure 10 Activity diagram for managing report.
9.Tracking
70
Figure 11 Activity diagram for order Tracking.
10. Verification
71
Figure 12 Activity diagram for verification.
11. Report
72
Figure 13 Activity diagram for report.
12. View product
73
74
Figure 14 Activity diagram to view product.

3.10. State chart diagram
State diagrams are the ideal way to model object life cycles. State diagrams enable you to
describe the behaviour of objects during their entire life span. In addition, the different states and
state changes as well as events causing transitions can be described.
1. Login
Figure 15 State Chart diagram to log in.
2. Sign up
75
Figure 16 State Chart diagram to sign up.
3. Post
76
Figure 17 State Chart diagram to post
4. Order
77
78
Figure 18 State Chart diagram to order.
5. Category
Figure 19 State Chart diagram to catagory.
6. Delivery
79
Figure 20 State Chart diagram for delivery.
7. Delivery
80
Figure 21 State Chart diagram to incorrect action.
8. Inventory
81
Figure 22 State Chart diagram for inventory.
9. Tracking
82
Figure 23 State Chart diagram for tracking.
10.Verfication
83
Figure 24 State Chart diagram for tracking.
11.Report
84
Figure 25 State Chart diagram for Reporting.
12.View item
85
Figure 26. State Chart diagram to view item.
86
Chapter Four
System design
4.1 overview
This is the system design document to the online shopping system for all over country. The
document includes the design goal, the proposed system design and object design.
4.2 purpose of the system

This document describes the design issues of the overall system. It provides the complete
architectural overview of the proposed system. It is intended to capture and express the
significant architectural decisions which have been made on the system.
4.3 design goal

The design goals describe the qualities of the system that are derived from the non-functional
requirements which can lead to decisions of developers.
The designing part is very important so as to make the implementation or the coding part very
easy. The different types of the system modeling techniques that are used for the implementation
of the system such as deployment and component modeling are show in detail.
Not only the system modeling techniques but also some system design techniques such as system
decomposition design are cover in detail in this phase. These goals can be inferred from the
nonfunctional requirements. These are:
Performance
Dependability
Maintenance
End user
4.3.1 Performance
.
87
Response time: - Depending on the network connection that the user machine has the system
is going to interact and respond to user’s request in a maximum of a second, if the user is just
viewing the pages, but if the user’s request requires the processing of the data base, like
searching for schedule, is going to take an average of 1-5 seconds of communication latency with
the server system. And streaming of trailers is going to have a response time up to 2-4 seconds.
88
Memory:-The client system requires an average of 512 megabits of RAM memory to be
loaded on a user’s web browser and streaming of trailers require additional memory megabits.
The server system is going to require more GB of memory to store all the data and other
components of the system.
4.3.2 Dependability
The online shopping system should achieve the following dependability characteristics in order
to resist crash and be available and reliable.
Robustness: - since the system is a web based system, that mainly use a menu driven entry
there wouldn’t be an input problem by the user side. But for the server side there might be an
error during the process of entering a data. In this time the system will provide an error page and
the system will continue without failure or crush.
Availability: - as long as there is an internet connection the system will be available 7 days a
week and 24 hours a day.
Security: - by the user side security issue to be considered, the only thing that must be
controlled is in the action of rating a movie that, they can rate or click the like or dislike button
only one at a time. But by the official user side the system will provide a user name and
password that will manage their own page according to their level of access.
Reliability: the information provided by the system is as reliable as it is presented on the
web page interface, and this is maintained by the persistent database.
4.3.3 Maintenance
In time of failure or need modification the system need to be maintained. To be maintainable the
system should meet the following maintenance criteria
Extensibility: - if it is needed to add new functionality to the system, this must be achieved
by only making a separate page and integrate this page with the existing system.
Modifiability: - if in the system, some functionality requires to be modified, this
modification must be done specifically to that function or page without affecting the overall
system organization.
Portability: - the system is developed to be viewed and retrieved from any web browser and
android application regardless of their version and platform it resides in it.
Readability: - the system code can be viewed by clicking on the current web page and
choose “view the source code” option.
4.3.4 End user

From the user point of view the system should provide the following end user criteria’s so that
the system can achieve At least a 90% usability by the user
Utility: - in order to help the user, to easily understand and interact with the system, the
system must provide the following utilities
Mouse over tips
89
Keyboard alternative
Usability: to enhance the usability of the system, the system should be designed
incorporating the following usability concepts
Site mapping
Consistent page pattern
Less overcrowded interface.
4.3.5 Priorities of the system

The design goals of the citizenship identification system (cis) system are prioritized as follows
Priorit Design goal

y
1 End user
2 Performance
3 Dependability
4 Maintenance
Proposed system
4.4.1 Overview
The proposed system is mainly based on the SRS document that’s already developed and
submitted. It mainly deals with subsystem decomposition – dividing the system in to manageable
components. Another major task in system design deals with hardware/software mapping which
deals with which components would be part in which hardware. Yet another aspect of system
design deals with persistent data management, which illustrate as to how persistent data (file,
database, etc.) are stored and managed and at last Access control will be presented.
Our system is a three tires architectural it has client side, server and database.
Client side: here in the client side Employee, Administrator, and user interface will be existing.
Server side: here the web and/or servers to connect the data base application are found; mean
that the application logic to perform the application by the client is found.
Data base: here the data bases that store the information are found.
90
91
System Architecture
Internet service portal

An internet service portal is an initial entry to hulu online shopping services.
92
Store Clerk
This section explores in detail store clerk system architecture design. In a below section
overview of the system.
Finance clerk
This section explores in detail finance clerk system architecture design. In a below section
overview of the system.
93
Delivery Clerk
This section explores in detail delivery clerk system architecture design. In a below section
overview of the system
Customer
This section explores in detail customer system architecture design. In a below section overview
of the system
94
Hulu online shopping Admin
This section explores in detail Hulu online shopping Admin system architecture design. In a
below section overview of the system.
Development View
95
96
Subsystem Description
Subsystem Function
Customer Make request,view product,order,give

feedback,report,post product
Finance clerk Manage report of tax
System admin Verify,register,identify illegal action
Branch manager Manage employee on branch
Store clerk Organize order,category a product,tracking a

product,manage inventory
97
Delivery clerk Deliver a product
Help desk clerk Help customer
Reference
https://www.export.gov/article?id=Ethiopia-ECommerce
98

Hulu Online Project

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Hulu Online Project

Uploaded by

Copyright:

Available Formats

Adama science and Technology University

School of Electrical Engineering and Computing

Computer Science and Engineering Program

A senior project Documentation for computer science and engineering:

HULU web and android based online shopping

Submission Date 22/11/18

Mikiyas Tilahun __________________________ April 19, 2019

Student Signature Date

Misikir Damenu __________________________ April 19, 2019

Student Signature Date

Nardos T/Mariam __________________________ April 19, 2019

Student Signature Date

Abel Tesfaye __________________________ April 19, 2019

Student Signature Date

Eshita Addisu __________________________ April 19, 2019

Student Signature Date

Student Signature Date

1. Mr.Daniel Tsegaye ___________________________ April 19, 2019

Advisor Signature Date

2. ______________________ ______________________ ____________________

Senior project Committee

---------------------------- --------------------------------- ---------------------------------------

1.2 Background Information

1.3 Statement of the problems

Delivery and logistics

Digital payment failures

Unclear return and guarantee policies

Many online shopping organization may have a complicated navigation system.

1.4.2 Specific objective

1.5 Feasibility study

1.5.1 Technical feasibility

 Does the necessary technology exist to do what is suggested?

1.5.2 Operational Feasibility

1.5.3 Economic Feasibility

1.6 Scope and Limitation

1.7 Significance of the project

1.8.1 Fact Finding of Methodology

1.8.2 System Development Methodologies

1.9 Testing procedure

1.9.2 Integration testing

 Prepare integration test plans

1.10 project plan

Phases February1 May June July July

1.11. Team Composition

HULU ONLINE SHOPPING

2.1 Major Function of the Current System

Function of the Current systems are

- Providing platform to sell and buy products

 Fill seller form with item description

 Fill a buyer form with account number

- Provide limited payment options

2.1 User of the current system

1. Consumer - to - Consumer (C2C)

2. Business - to - Business (B2B)

3.Consumer - to - Business (C2B)

4.Business - to - Consumer (B2C)

2.3 Problems of the current system

1. An absence of Online Identity Verification

3. Maintaining customer’s loyalty

4. Lack of Customer Support

6.Unclear return and guarantee policies

2.5 Business rule of the current system

2.