Full Document

Online Shopping System 2016
Table of Contents
Acknowledgement....................................................................................................................................i
Abstract....................................................................................................................................................ii
Chapter One.................................................................................................................................................1
1. Introduction......................................................................................................................................1
2. Problem statement of the project......................................................................................................2
3. Objectives of the project..................................................................................................................2
3.1. General Objectives..................................................................................................................2
3.2. Specific Objectives...................................................................................................................3
4. Methodology of the project..............................................................................................................3
4.1. Methodology of the project......................................................................................................3
5. Scope of the study............................................................................................................................5
6. Limitation of the project...................................................................................................................5
7. Significance of the project................................................................................................................6
8. Feasibility Assessment.....................................................................................................................6
8.1. Economic Feasibility................................................................................................................6
8.2. Technical Feasibility................................................................................................................9
8.3. Operational Feasibility...........................................................................................................10
8.4. Schedule Feasibility...............................................................................................................10
9. Management issues........................................................................................................................11
9.1. Team configuration and management.....................................................................................11
9.2. Communication plan.............................................................................................................12
Chapter Two..............................................................................................................................................13
System Requirements Specification.......................................................................................................13
1.1. Purpose..................................................................................................................................13
1.2. Overview the Existing System...............................................................................................13
1.3. Overview the Proposed System..............................................................................................13
2. Supplementary specification..........................................................................................................14
2.1. Functional Requirements........................................................................................................14
2.2. Non Functional Requirements................................................................................................14
i|Page
2.3. Business rules.........................................................................................................................16

2.4. Constraints.............................................................................................................................17
3. Class responsibility collaboration (CRC).......................................................................................18
4. Use case Diagram..........................................................................................................................21
4.1. Essential Use Case.................................................................................................................21
4.2. System Use Case....................................................................................................................24
5. User interface prototype.................................................................................................................35
6. Activity diagram............................................................................................................................37
Chapter Three............................................................................................................................................40
System Design Document..........................................................................................................................40
1. Class modeling...............................................................................................................................40
2. Sequence Diagram.........................................................................................................................43
3. Collaboration diagram....................................................................................................................47
4. User Interface Design.....................................................................................................................50
5. State chart diagram........................................................................................................................53
6. Persistent Modeling/ Database Design...........................................................................................56
6.1. Table Structure.......................................................................................................................56
6.2. ER Diagram...........................................................................................................................58
6.3. Normalization........................................................................................................................59
6.4. Database Relationship Diagram.............................................................................................62
7. Component diagram.......................................................................................................................63
8. Deployment diagram......................................................................................................................64
Chapter Four..............................................................................................................................................65
Implementation Document.........................................................................................................................65
1. Introduction....................................................................................................................................65
2. Report on Implementation..............................................................................................................65
3. Sample Code..................................................................................................................................67
4. Testing...........................................................................................................................................74
4.1. Unit Testing...............................................................................................................................74
4.2. Integration and System Testing..................................................................................................74
Error Handling.......................................................................................................................................75
ii | P a g e
4.3. Conclusion.................................................................................................................................76
5. Clients Feedback............................................................................................................................77
6. User Manual...................................................................................................................................78
Appendix...................................................................................................................................................89
Reference...............................................................................................................................................89
ii | P a g e
Acknowledgement
First and foremost, and above all our biggest thanks would be to Almighty God because nothing
could be possible without his free will and the completion of this project is supported by him.
Secondly, our deepest thanks go to our Advisors Mr. ABDURAHMAN REDI and Miss RAMA
AMATI for guiding and for their invaluable advice and useful suggestion. Next I would like to
acknowledge Haramaya University Information System Department in order to developing
computer based system in a good manner. At the last special thanks to our classmates specially to
Tesfaye Bekele for their great help and keeping us to reach today’s day.
i|Page
Abstract
The Online Shopping is a web based application intended to online for customer. The main
objective of this application is to make it interactive and its ease of use. It would make searching,
viewing and selection of a product easier.
This project concern about online shopping system for literature materials like Electronic
product. The customer can view the complete detail of each product. The application also
provides to customer can add a product to the shopping cart and also they may view the
contents of their shopping cart at any time and may they remove items at will finally Our
system provides automatically calculates the total price then display for the customer. The main
emphasis lies in providing customer to order item in easy way by using add to cart or select one
item The system generate receipt for the customer when successfully order item The Admin
have many privilege in the system, such as create and delete employee account, viewing order.
For sales person, search item, view comment and view report. The warehouse employee also has
privilege such as manage product (add, delete, update product) and view order.
ii | P a g e
Chapter One
1. Introduction
Online Shopping center is the system that involves selling and buying transaction process. Such
transaction is concentrate on literature materials like Electronic product like, Computer, Cell
phones, printer, scanner, Photo copier and other kinds of electronic materials. Current Ethiopian
shopping centers are most of them are use a manually system to sale their products.
The Online Shopping Cart website allows to customer online shopping collecting items in a
shopping cart. They may view the contents of their shopping cart at any time and may add or
delete items at will. This system provides automatically calculates the total price of the
product, and provide payment system.
This is website which helps you to do the major part of online shopping by using this site
and can be managed by online. Customer can do the all major transaction in a secured way. Here
the customer will feel shopping by adding the selected product to his/her cart in addition to that
he/she can also does bulk addition into the cart before purchasing. This all options are done by
session management. To ensure the authentication of the customer, he/she must have to register
before purchasing.
Therefore, the online shopping system we planned to analyze in this project we will try the best
way to make the complicated process of the shopping system as simple as possible using
Structured, Modular technique and Menu oriented interface. We are going to design the website
in such a way that customer may not have any difficulty in using this package & further
expansion is possible without much effort. Even though we cannot claim that this work to
be entirely exhaustive, the main purpose of this project is to make each customers and sellers
activity in automated or computerized way rather than manually.
1
HARAMAYA UNIVERSITY DEPARTMENT OF INFORMATION SYSTEMS
2. Problem statement of the project
The overall activities in the Existing System the Customer is completely depending on the
manual process for buying the products. Manual process is a time consuming factor. And when
customer approaches for a manual shopping directly, actually he/she does not have an idea about
things like, price range, items, etc. The time which has been spent by the customer in manual
shopping can equates to multiple number of shopping. As customer can sit at home and browse
in a fraction of seconds. Thus we need to change to a system like “Online Shopping “.
Some of the problems exist in the system: -

 The store opened in a day 10 hours only.
 There is no advertisement of product.
 It takes more time to processes transaction.
 There is no written items description and price.
 Use more labor.
 It is a time consuming process.
 The customer must be waiting until another customer is served.
 It is easy to stole materials
3. Objectives of the project
3.1. General Objectives
The general objective of the project is to automate the existing shopping system.
2
3.2. Specific Objectives
In order to fulfill the above objectives, we need to accomplish the following specific objectives.
 To minimize time consumption

 To save resource
 Transaction will be carried on time
 To satisfy customer with the service
4. Methodology of the project

4.1. Methodology of the project
4.1.1. Methodology for data collection
We use primary data collection methods have been implemented for the identification of the
problem and understanding the existing system. Some of the methods we use: -
Interview: - The most important method that helps us to get most important and critical
information about the general view of the Shops is by interviewing owner of the Shop material,
seller of the Shop and some customers.
We ask some questions for Example: -
 How do you work currently?

 Have you any computerized system?
 Do you have an items list with their descriptions and price?
 What is the problem of the current system?
 How many employees you have?
3
We get responses from the persons and they also say that, the current system is used manual
system that means all activates performed by agenda. So that the system is complex, more time
consuming and redundant activity.
Observation: - this method is also used to collect data, done by direct seeing the working
environment. We have observed physically by going to some electronic shop in harar. Also we
observed that there is no any computerized system in the Shop and also information about the
Shop and the service that the Shop provides were not available easily. The team also
observes that ordering is only by face to face.
4.1.2. Methodology for system analysis and design
We decided to use object oriented system analysis and design (OOSAD) because of the following
reasons.
 It would facilitate code re use since it implements the concepts of object oriented method
like, inheritance, encapsulation and polymorphism. From development method, we use
prototyping and from testing method we use integration and system testing.
4.2. Software Tools we use

4.2.1. Front-end Technologies
The user interface will be developed using HTML, CSS, JavaScript integrated development
environment since it easily designing the front end and connected in to data base realizing rapid
application development with constraints on the hand.
4.2.2. Back-end Technologies

PHP MYSQL (xamp,server), database system will be used in developing and managing the
database at back end.
4
5. Scope of the study
The scope of the project is defined in terms of the tasks that the system accomplishes. Thus, the
scope of the project is limited to:
 Register new customers

 Customer can add and subtract items from cart
 Customer can view his/her cart with total price of the product
 Online ordering systems.
 The system deducts the total amount of price from the customer account
 Managing products (adding, deleting, and updating).
 Preventing unauthorized access.
 Generating reports and receipt of items.
 Generate advertisement for items which price is discount and when new item is
registered.
 Displaying alert message for insufficient item.
 Display ordered items information
6. Limitation of the project

The new system can’t provide
 Rate of taxes
 Payment salary of the employee’s
 Only provide electronic materials
5
7. Significance of the project

 Fulfill what customer needs.
 Items deliver on time
 Decrease the load and number of employees.
 Be reliable and honest
 To describe details information of the items
 24 hour working time.
 Attract the customer.
 Safety way of data storage and retrieval.
8. Feasibility Assessment
Preliminary investigation examines project feasibility 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
systems are feasible if they are given unlimited resources and infinite time. There are aspects
in the feasibility study portion of the preliminary investigation:
 Economic Feasibility
 Technical Feasibility
 Operation Feasibility
 Schedule Feasibility
8.1. Economic Feasibility
Economic feasibility attempts to weight the costs of developing and implementing a new system,
against the benefits that would occur from having the new system in place. This feasibility study
gives the top management the economic justification for the new system. There could be various
types of tangible and intangible benefits and costs on account of automation.
6
Benefits: the benefits of one system can be expressed in terms of tangible benefit and intangible
benefit.
A. Tangible benefits:
In the project going to be computerized there will be reduction of cost for materials used for
manual operation such as: pen, paper, human power, space needed to keep data record, and
save data storage and time that we are induced or brought in during manual system.
The team calculated the corresponding tangible benefits based on the technique called the time
value of money (TVM).
1. Cost Reduction and Avoidance: - To calculate these following things will be considered.
Total Number of Employee in existing system= 10
Average Salary of each Employee per month = 1000.00Birr
Total money required for payment per year= 10*1000*12= 120,000Birr
Average Number of Employee needed when the new system is deployed= 5
Average salary of each of them per month = 1200.00Birr
Total money required for payment per year= 5*1200*12= 72,000.00Birr
Difference b/n before and after deployment money required for payment
Cost Reduction and Avoidance= 120,000.00Birr-72,000.00Birr= 48,000.00Birr
B. Intangible Benefits
This refers to benefits that cannot easily be measured in terms of money and with certainty. Some
of the intangible benefits of the proposed system are: -
 It minimizes the work load of the worker
 Efficient work flow
 Increase speed of activity
 Save the loss of documents
7
 Increase flexibility
 On time information
 Increase security
Cost: This is the tangible and intangible cost of the proposed system.
A. Intangible cost
Costs consequent from the design of an automated system that cannot be easily considered as cost
are:
 Time requires for adapting new system
 Requiting or train staffs who operates the new system.
 Organizing the office with the new organization.
 Work satisfaction
B. Tangible cost
Hardware cost
Name the material Quantity Price per unit Total price
Pen 6 3.50birr 21birr
Printing 85 1birr 85birr

Paper coverage 6 6birr 36birr
Paper(A4) 200 40cents 80birr
Flash disk(2GB) 1 180birr 180birr
CD disk 3 5birr 15birr
Total
417birr
8
Software cost
Name of Software price
Microsoft Office Word 2007 free download

Notepad++ free download
Xamp free download
Adobe Photoshop free download
Buidu browser free download
Visual Paradigm for UML free download
Total cost ------------------
8.2. Technical Feasibility

The proposed system can be technically feasible because the technical resources needed to develop, install and
to operate is available in the present infrastructure. Evaluating the technical feasibility is the trickiest part of a
feasibility study. A number of issues have to be considered while doing a technical analysis.
Understand the different technologies involved in the proposed system:Before commencing the project,
we have to be very clear about what are the technologies that are to be required for the development of the
new system.
Find out whether the organization currently possesses the required technologies:
Is the required technology available with the organization?
If so is the capacity sufficient?
For instance- “Will the current printer be able to handle the new reports and forms required fort the new
system?”
9
 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?
 Can the system be upgraded if developed?
8.3. Operational Feasibility

The proposed system can be used effectively after it has been developed. Users will not have any
difficulty with the new system to produce the expected benefits. System will be developed based on
the policies of the organization and it doesn’t require much training for users. And the new system will
not place any new demands on users nor requires any operating changes. Since the proposed system
was to help reduce the hardships encountered. In the existing manual system, the new system was
considered to be operational feasible.
 User-friendly
 Reliability
 Security
 Portability
 Maintainability
8.4. Schedule Feasibility
As we know planning is the first phase of any system so we need to start with the schedule
programs and our project is intended to be with in fixed time interval. Unless and otherwise we
may fall in difficulty in cost estimation and as well as we may fall in the financial problem. To
overcome such problems, we fixed the time interval in which we should finish the development
of the whole time among different section of project by using the techniques of schedule like
Gant chart.
10 HARAMAYA UNIVERSITY DEPARTMENT OF INFORMATION SYSTEMS

9. Management issues
This phase is the responsibility of the manager to do management roles to the project members.
And it has a power to do anything such as to punish the members or to give some reward and so
on. Management issue is about the team members and the way in which we are going to use our
effort on the system and a plan how we go with time based on the schedule to accomplish within
the time we have.
9.1. Team configuration and management

To assign own work to the group member is to reduce the work load and to accomplish the
project on time composed of 4 members. Decision on problem and approach are made by
group agreement, which is much better than individual decision. The team responsible for every
activity of this project work is organized and grouped based on the rules and regulations to
achieve our project.

Project Members ID NO. Responsibilities

Sadat Mehamedseid 2040/05 Analysis/Designer/Programmer
Marta Assefa 1958/05 Analysis/Designer/Programmer
YrgalemNguse 2129/05 Requirement Gathering /Designer/Testing
MalefiaKindie 1957/05 Requirement Gathering/Designer/Testing
9.2. Communication plan

For the achievement of our proposed project all of the group members fully participate on each activities
of the project. To insure this, we try to work corporately by sharing idea with each other and present on
time at the time of meeting. As a team member, we communicate each other by group discussing on the
issues in general, for example we design on paper before writing on the system. And sometimes we divide
and do a separate task to facilitate the project to proceed based on the schedule. And we regularly contact
our advisor (necessarily twice a week) to submit the progression of work and irregularly to ask questions
related to the project development, to get advice, information and resources necessary to our system
development. We use the following method of communication in order to meet one another.
Schedule time table for meeting
Time Techniques
Member with Members 1.Monday 1:00pm - 4:00pm
2.Thursday 1:00pm - 4:00pm SMS and call phone
3.Sutarday 7:00pm - 11:00pm
Member with Advisor Monday 10:30am12:00am Office meeting, E-mail, and

Thursday 8:30am10:00am
call phone.

Chapter Two
System Requirements Specification
1.1. Purpose
Considering the main problem of the online shopping system, the major purpose of this proposed
system is to organize and manage the items which is purchase and sold as well as the systems
also aim generating the daily, monthly, semi and yearly transaction reports and receipts for each
sold items. In addition to this some of the main purpose of this project is:
 Advertising products
 Decrease time and resource of customers etc.
 Provide sale and buy service to customer
 Provide good and fast service to customer
1.2. Overview the Existing System

The current system of Online Shopping System in Ethiopia are not provide goods and services
online and has not provide online banking system to make payment, to their purchased items.
And also no anyway of method and awareness on preparing report and receipt. They simply
selling and purchasing items to their customers and only generate the day to day income of
the shop. The activity of the retailer is selling the items dealing within a customer.
1.3. Overview the Proposed System

The proposed system is concern about the Online Shopping System transaction in order to
provide an alternative solution for the online shopping. For doing activities of the Online
Shopping System such as recording purchased and sold items and generating transaction of it.
And also these new systems protect and secure the Online Shopping System data files in secured
way.
13
2. Supplementary specification
2.1. Functional Requirements
The Functional Requirements Specification documents the operations and activities that a system
must be able to perform. Functional requirements should include functions performed by specific
screens, outlines of work flows performed by the system, and other business requirements the
system must meet
 Administrator
 Manages Employees
 Accept feedbacks.
 Update profile.
 View order
 View report
 Customer
 Register and login to site.
 View item, add to cart and Remove items from cart.
 Send feed back
 Order product
 Warehouse employee
 Add, update and delete products
 View customer order
 Update profile.
2.2. Non Functional Requirements

Non-functional requirement is a requirement that specifies criteria that can be used to judge the
operation of a system, rather than specific behaviors this requirement dose not directly affect the
performance of the proposed system but, they concerned with security, performance, usability,
maintainability, reliability, efficiency, portability (across operating systems) testability,
understandability etc.
14
The non-functional requirements of the system are presented below: -
 User Interface: - user friendly interface with easy navigational scheme.

 Error handling Mechanism: - handles invalid inputs and display user error in meaningful
messages.
 Security issue: - provides security tasks such as for registering, for modifying user’s information
and viewing needs authentication and authority.
 Maintainability: -When the website fails, it can be maintained easily. What does it mean to say
the web has failed? Over time the number of people using the system will dramatically grow and
customer demands will grow and change. So this website can easily be rebuilt to fit the evolving
customer demands and the newly arriving changes. So it can be easily maintained and can grow to
a better version.
 Performance: -the performance of our website is measured in terms of load time and number of
requests handled. So it is fast in accepting inputs and displays the result as well as requires small
space.
 Modifiability: -The system is can easily modify or change the given information.
 Availability: -The system will be available for 24 hours to users with internet connection.
 System requirement:-Our website requires software and hardware requirements. These are: -
A) Hardware requirement
 Flash 16 GB
 Laptop
 RAM size 4 GB or more
 Processor speed 2.5 GHZ or more
B) Software requirement
 Notepad ++
 XAMP Server
 Edraw MaxUML
 Mozilla Firefox, Baidu browser
 Microsoft office word 2016
15
Others
 Internet connection
 Dedicated lab room
2.3. Business rules

A business rule is a rule that defines or constrains some aspect of business and always resolves to
either true or false. Business rules are intended to assert business structure or to control or
influence the behavior of the business system. Business rules describe the operations,
definitions and constraints that apply to an organization. Business rules can apply to people,
processes, corporate behavior and computing systems in an organization, and are put in place to
help the organization achieve its goals.
Name: determine need of login
Identifier: BR1
Description: The user has to login to do his/her business operation on the system
Name: customer need to change or cancel ordered products
Identifier: -BR2
Description: for the changing or cancel customer must be change or canceled on 10 minute only.
Name: determine need to reports
Identifier: -BR 3
Description: -it is not allowed to see all reports unless he/she is the Administrator
Name: determine need to Add items, Update items, and Delete items
Identifier: -BR 4
16
Description: - it is not allowed to add, update, and delete items unless he/she is the Warehouse
Employee.
Name: determine need to Add users and Delete users
Identifier: -BR 5
Description: - it is not allowed to add and delete users unless he/she is the Administrator.
Name: determine need to order
Identifier: -BR 6
Description: - the customer must have logged in before order
items Name: admin or ware house employee’s needs to view order
Identifier: -BR7
Description: -admin or ware house employee’s must have logged in to view order
2.4. Constraints
The following requirements are general constraints of the system:
 Lack of fast internet connection

 Lack of resource like computer
 The system operates only in English language
 The system only work when electric power is available
 It’s not suitable for disable person, like blind people.
 It needs some computer skill to operate on the system.
17
3. Class responsibility collaboration (CRC)
Class Responsibility Collaborator (CRC) Modelling is a method to gather and define the user
requirements for an object-oriented application. The output of CRC Modelling is a CRC Model
which is a collection of CRC cards that represent the whole or part of an application or problem
domain. Each CRC Card in the model represents a class in the solution. A class represents a
person, place, thing, event, concept, screen, or report that is relevant to the system at hand. The
name of the class appears across the top of the card. A responsibility is anything that a class
knows or does.
customer <<Actor>>
Fname Lname Username password Sex

Age Phone
Order Register
Order product<<UI>> Register<<UI>> login<<UI>>
Warehouse Employee<<Actor>>

Age Phone
View ordr register

Manage product<<UI>> Login<<UI>> View Order<<UI>>
add new product delet product updet product
18
Administerator<<Actor>>

Age
Phone
View order
register Creat Employee Login<<UI>> View Order<<UI>> View Report<<UI>>
Account Delete Account
Order Product<<UI>>
User name Order

FnameCustomer
Lname password
Product Account
Account Number Order Date Product Name Product model Total price
Cus coupon
Figure 3.1 class responsibility collaboration diagrams
19
Manage Employee<<UI>>
User name Password

Account<<UI>> Employee
Creat Account Delet account
Manage Product<<UI>>
User name Password
Account Product
Add new product Delet Product Update product
20
Registeration<<UI>>

Age Username Password
Customer Account
Login<<UI>>
Username PasswordAccount
21
Account
Account-ID Account-Type User Name Password
Customer Employee
Customer
Cus-ID Cus-Fname Cus-Lname

Password Phone Sex
Age Adress
Account Num Account-ID
Order Account
Employee
Fname Lname Customer ID User Name Password Sex

Age Phone
Account

Report
Product-ID Cus-ID Cus-Fname

Cus-Lname Pro-Name Pro-Code Pro-quantity Order Date
Customer Product Order
Order
Order-ID Cus-ID Cus-Fname

Cus-Lname Pro-ID
Pro-name Pro-Code Pro-Quantity Order Date Order time
Customer Product

4. Use case Diagram
A use case is a sequence of transactions performed by a system that yields an outwardly visible,
measurable result of value for a particular actor. A use case typically represents a major piece of
functionality that is complete from beginning to end. An actor represents whoever or whatever
(person, machine, or other) interacts with the system. The actor is not part of the system itself and
represents anyone or anything that must interact with the system.
4.1. Essential Use Case

The current use case of manual system
Figure 4.1 Essential use case of the manual system
21
4.1.1. Essential Use Case Description

Use case name Add to cart
Participating Actor Customer
Description The Customer adds the products what he wants to buy to the cart
Precondition The customer must view the products.
Flow of events Basic Action:
1. The customer wants to buy product
2. The customer search product that he wants
3. The customer adds products to his/her cart
4. The use case end

Post condition The item or product is added to the cart.
Use case name Make payment
Description Here using the use case, the Customer will pay the bill.
Precondition The customer must select items with in a cart
Flow of events 1. The customer wants to pay bill

2. The customer goes to the sales person
3. The sales person calculates and put total price of the items
4. The customer pays the total price of the items.
5. The use case end
Post condition Receive items from sales person.
22
Use case name Add new Product
Participating Actor Sales Person
Description The Sales Person Add the product category to the shelf
Precondition The product must available on the shop
1. The Sales Person wants to add new product

2. The Sales Person add the product to the shelf
3. The use case end
Post condition The item is available to sale.
23
4.2. System Use Case
Figure 4.2 System use case of the new system
24
4.2.1. System Use Case Description
Use case name Register
Description New Customer of the site is registered here.
Precondition The Customer must be new user
1. The customer wants to register
2. The customer click on registration button
3. The system displays a registration form
4. The customer enters all required inputs
5. The system validates the data entered
6. The customer clicks on Register button.
7. The system send data to validate
8. The system establish connection
9. The system return msg
10. The system perform the query
12. The system displays successfully registered message and login page.
13. The use case end
25
Alternate Course A: Invalid data entered.
A.5. The system displays error massage
A.6. The system asks to re-enter valid data
A.7. The use case end
Alternate Course B: If the customer already registered
B.12. The system displays already registered message
B.13. The system displays login page
B.14. The use case end
Post condition The customer is registered.
Use case name Login
Participating Actor Customer, Administrator, Ware house employee
Description Only the registered users will login, it may be the customer, Administrator or
Ware house employee.
Precondition The user have to be already register
1. The user wants to login
2. The user clicks on login button
3. The system displays a login form
4. The user enters user name and password
26
The system validates the data entered
The user clicks on Login button.
The system send data to validate based on Bissness Rule 1
The system establish connection
The system return msg
The system perform the query
The system displays successfully logged in message.
The use case end
The system displays error massage
The system asks to re-enter valid data
The use case resume to step 4
Alternate Course B: If the user is not having an account
The system display your user name and password is incorrect
Alternate Course C: If the user forgot password
The system display your user name and password is incorrect
The user must have to click on forgot password button
The system asks to fill username and email address
27
C.15. The customer clicks on Change button
C.16. The system sends the password to his/her email account
C.17. The use case end
Post condition A user is logged into the system
Use case name Order product
Description The Customer Orders the products what he wants to buy and it includes login before
order
Precondition The customer must add an items before ordering
1. The customer wants to order products
2. The customer clicks on products button
3. The system displays product list form
4. The customer add an items to cart
5. The customer click on Order button based on Bissness Rule 6
6. The system displays a login form
7. The customer enters user name and password
9. The customer clicks on Login button.
11. The system establish connection
28
The system perform the query
The system return msg and display on cart page
The customer click on Order button
The system send data to the controler
The system check the customer Coupon account
The system Return msg
The system deduct from customer Coupon account
The system execute save to order table
The system display successfully ordered products.
Alternate Course A: If the customer not added products.
The system display your cart is empty massage
The system ask to add items
The customer click on product button
The system display product list page
The customer added an item to his/her cart
Alternate Course B: If the customer not has enough money in coupon account.
The system display account not have enough money massage
The use case end
29
Alternate Course c: If the customer wants to cancel order.
c.24. The customer clicks on cancel order button based on Bissness Rule 2
c.25. The system cancel the customer ordered product and add balance to customer
coupon account
D.27. The use case end
Post condition The customer get the product
Use case name Remove items from cart
Description The customer removes the product from the cart
Precondition The customer added a product to the cart.
1. The customer wants to remove an items from his/her cart
2. The customer clicks on cart button
3. The system display customer cart with items information.
4. The customer selects item to remove from the cart.
5. The customer clicks on the Remove item link.
6. The system asks the user for the confirmation.
7. The customer confirms the removal
8. The system removes the item from the customer cart.
9. The system displays the products is removed successfully
10. The use case end.

Alternate Course A: If The user not confirms to remove the item
A7. The use case go to step 3
Post condition The products is successfully removed
Use case name Add new product
Participating Actor Warehouse employee
Description The Warehouse employee creates the product category list
Precondition The Warehouse employee must be logged in
1. The warehouse employee wants to add new product based on Bissness Rule 4
2. The warehouse employee clicks on add new product button.
3. The system displays add new product form
4. The warehouse employee fills all required inputs
6. The warehouse employee clicks on add button.
8. The system established connection
10. The system excute the query
12. The system displays successfully added message.
31
A.9. The use case resume to step 6
Alternate Course B: If the product already available.
B.14. The system displays the product already available message
B.15. The system displays add new product page
B.8. The use case end
Post condition The category list of the product is created.
Use case name Update product
Participating Actor Warehouse employee
Description The Warehouse employee updates the product category list
Precondition The Warehouse employee must be logged in
1. The warehouse employee wants to update product based on Bissness Rule 4
2.The warehouse employee enter product code in the search form
3. The warehouse employee clicks on search button.
4. The system send data
32
7. The system execute the query
9. The system displays searched product .
10. The warehouse employee click on Edit button
11. The system display product information
12. The warehouse employee update the product information
13.The system validate the data entry
14. The warehouse employee clicks on update link button
15. The system send data
18. The system execute the query
20. The system display successfully updated msg
Post condition The category of the product is updated.
33
Use case name Delete Employee
Participating Actor Administrator
Description The Administrator wants to delete user
Precondition The Administrator is logged in
Flow of events Basic Course of Action:
1. The Administrator wants to delete employee account based on Bissness Rule 5
2. The Administrator clicks on Delete Employee button.
3. The system displays Employee page
4. The Administrator enter employee name in the search form
5. The Administrator clicks on search button.
6. The system send data to fetch employee
7. The system displays searched employee.
8. The Administrator clicks on delete link button
9. The system asks for confirmation

10. The administrator confirms the deletion.
11. The system display successfully deleted account.
12. The use case end.
Alternate Course A: If the administrator enters in correct Employee Name

A.7. The system displays there is no employee with this name message
A.8. The system asks to re input the employee information.
Alternate Course B: If the user is does not exist
B.7. The system display the employee is doesn’t exist
B.8. The system resume at step 3
Alternate Course C: If the administrator confirms not to delete
Post condition B.10.employee
The The system resume at step 7
is deleted
34
5. User interface prototype
User interface prototype is to indicate the surface that can be used by user and the system to
communicate to each other, but, not actual work area. Here the prototype of applicant registration
form and employee search detail is listed.
Administrator Page
View Order Manage Employees
User Information
Information
Warehouse Employee
Page
View Order Manage Product
Order Information Product Information
Figure 5.1 User interface prototype for administrator and warehouse employee
35
Warehouse Employee Information
Username
Manage Product
Password View Order
Administrator Information
Username
Manage Employees
Password View Order
Customer Information
Username
Manage Cart
Password Order Item
Figure 5.2 User interface prototype for all users
36
6. Activity diagram
Introduction
 An Activity diagram is a type of flow chart with additional support for parallel behavior.
 This diagram explains overall flow of control.
 Activity diagram is another important diagram in UML to describe dynamic aspects of
the system.
 Activity diagram is basically a flow chart to represent the flow from one activity to
another activity
 The activity can be described as an operation of the system.
 The control flow is drawn from one operation to another. This flow can be sequential,
branched or concurrent. This distinction is important for a distributed system.
37
Figure 6.1 Activity diagram for customer registration
Figure 6.2 Activity diagram for Create User Account
Figure 6.3 Activity diagram for users login
38
Figure 6.4 Activity diagram for Manage Product
Figure 6.5 Activity diagram for Order Products
39
Chapter Three
System Design Document

1. Class modeling
Diagrams are used to represent the structure of the system in terms of objects, their notes and
nature of relationship between classes. It shows the static features of the actors and do not
represent any particular processing. It is an abstraction of the real environment class of seller,
patron (user) and Administrator. The purpose of a class diagram is to depict the classes within a
model. In an object oriented application, classes have attributes (member variables),
operations (member functions) and relationships with other classes. The UML class diagram
can depict all these things quite easily. The fundamental element of the class diagram is an icon
the represents a class.
Classes-type layered approach

User Interface Classes
order product
Manage Employee
Manage Product* Login
Registration
View order
View report
Control / Process classes
System
Business / Domain Classes
Class
order product
report
feed back
Persistence Classes
Account
Customer
Employee
Order
Product
Data storage
Figure 1.1. Class layered approach
41
Person
Account
fname
Account_ID lname
Account_type 1Have1 password
user_name phone
password sex
+ login() age
+ logout() - Account_ID
Customer Employee
cus_ID emp_ID
state Account_type
city
kebele
house num
Account num
+ addtocart()
+ remove() Report
+ viewcart()
+ order() Administrator rep_ID
+ register() cus_ID
M Warehouse Emp
M M cus_fname
M M cus_lname
Order + report() pro_name
1 + vieworder()
Manage + vieworder() View pro_code
+ create() pro_quantity
+ delete() order_date
M
Manage + report()
Register
1
M
Product
1 pro_ID
pro_name
Registration pro_code
M pro_desc
user_ID pro_image
user_fname pro_price
user_lname pro_quantity
user_name
password + add()
phone + update()
sex + delete()
age 1 Register
Account_type
+ register()
Figure 1.1 Class Modeling Diagram
42
2. Sequence Diagram
Diagrams model the dynamic aspects of a software system. The emphasis is on the “sequence” of
messages rather than relationship between objects. A sequence diagram maps the flow of logic or
flow of control within a usage scenario into a visual diagram enabling the software architect to
both document and validate the logic during the analysis and design stages. Sequence diagrams
provide more detail and show the message exchanged among a set of objects over time. Sequence
diagrams are good for showing the behavior sequences seen by users of a diagram shows only
the sequence of messages not their exact timing. Sequence diagrams can show concurrent
signals.
43
Figure 2.1 Sequence Diagram for login
44
Figure 2.2 Sequence Diagram for registration
45
Figure 2.3 Sequence Diagram for add new product
46
Figure 2.4 Sequence Diagram for update product

3. Collaboration diagram
A collaboration diagram, also called a communication diagram or interaction diagram, is an
illustration of the relationships and interactions among software objects in the Unified Modeling
Language (UML).
Use case: Register
Figure 3.1 Collaboration Diagram for registration

Use case: Login
Figure 3.2 Collaboration Diagram for login
Use case: Add new product
Figure 3.3 Collaboration Diagram for add new product
48
Use case: Update product
Figure 3.4 Collaboration Diagram for update
49
4. User Interface Design
User Interface Design is contain home page, products page, login form, registration form,and
shopping cart page. Home Page is a page that users interact with the system primarly. It contains
Home, Products,Register, Login, About us and Contact us.
Figure 4.1 User Interface Design for home page

Product page is used to select or add items the user wants to his cart. In this page there is much
kind of Electronics products like laptop, desktop, mobile, and other devices.
Figure 4.2 User Interface Design for product page
Shopping cart page is used to show what the user added to his cart with their total price and
quantity.in this page user can remove items from his cart and also can add another items.
Figure 4.3 User Interface Design for shopping cart page
51
Also this page is used to register new Customer and can login in this page. The customers of the
system have to fill all those data to register if does not fill all the box alert massage to customer
and cannot register.
Registration Form
Figure 4.4 User Interface Design for registration page
Login Form
Figure 4.5 User Interface Design for login page
52
5. State chart diagram

A State chart diagram describes a state machine. Now to clarify it state machine can be defined
as a machine which defines different states of an object and these states are controlled by
external or internal events. Activity diagram explained in next chapter is a special kind of a
State chart diagram. As State chart diagram defines states it is used to model lifetime of an
object.
Figure 5.1 State Chart Diagram for login
53
Figure 5.2 State Chart Diagram for order product
Figure 5.3 State Chart Diagram for add new product
54
Figure 5.4 State Chart Diagram for remove from cart
55
6. Persistent Modeling/ Database Design
Persistent data management deals with how the persistent data i.e. file, database, etc. are stored
and managed and to outlives a single execution of the system. Database design is the process of
producing a detailed data model of a database. This data model contains all the needed logical and physical
design choices and physical storage parameters needed to generate a design in a data definition language,
which can then be used to create a database. A fully attributed data model contains detailed attributes for
each entity.
6.1. Table Structure

NO ENTITY NAME ATTRIBUTES DATA TYPE PRIMARY KEY FOREIGN KEY
1 ACCOUNT account_ID varchar(50) Account_ID User_name
account_type text(50)
user_name varchar(50)
password varchar(50)

2 CUSTOMER cus_ID number(20) cus_ID user_name
fname text(50)
lname text(50)
user_image varchar(50)
phone number(20)
sex text(50)
age number(20)
state text(50)
city text(50)
kebele number(20)
house num number(20)
email varchar(50)
Table 6.1.1 Database tables
56

3 PRODUCTS ID number(20) ID product_code
product_type text(50)
product_code varchar(50)
product_name varchar(50)
product_desc varchar(50)
product_image varchar(50)
price number(20)
quantity number(20)

4 Order order_id number(20) order_id product_code
cus_fname text(50) user_name
cus_lname text(50)
pro_code varchar(50)
order_date date(20)
quantity number(20)

5 Employee emp_id number(20) emp_id user_name
fname text(50)
lname text(50)
user_image varchar(50)
account_type text(50)
phone number(20)
sex text(50)
age number(20)
Figure 6.1.2 Database tables
57
6.2. ER Diagram
An entity-relationship diagram is a data modeling technique that creates a graphical

representation of the entities, and the relationships between entities, within an information
system. The Entity Relationship Diagram is shown in the figure 4.4 below.
Figure 6.2.1 ER Diagram
58
6.3. Normalization
6.3.1. First Normal Form
Account Table
Account_ID Account_type user_name password
Customer Table
Cus_ID fname lname phone sex age state city kebele Hou Account Account_ID
num num
Product Table
Pro_ID Pro_name Pro_code Pro_desc Pro_image Pro_price Pro_quantity
Order Table
Order_ID Cus_ID fname lname Pro_ID Pro_name Pro_code Order_date Order_time
Employee Table
Emp_ID fname lname phone Sex age Account_type Account_ID
59
6.3.2. Second Normal Form
Customer Table
Cus_ID fname lname phone sex age state city kebele Hou Account
num num
New Table
Cus_ID Account_ID
Order Table
Order_ID Order_date Order_time
New Table
Order_ID Cus_ID fname Lname
New Table
Order_ID Pro_ID Pro_name Pro_code
Employee Table
Emp_ID fname lname Phone Sex age Account_type
New Table
Emp_ID Account_ID

6.3.3. Third Normal Form
Customer Table
Cus_ID fname lname Account num
Address Table
Cus_ID state city kebele Hou num
Contact Table
Cus_ID phone sex age
Employee Table
Emp_ID fname lname Account_type
Contact Table
Emp_ID phone sex age
61
6.4. Database Relationship Diagram
Figure 6.4.1 Database relationship Diagram
62
7. Component diagram
The component diagram helps to model the physical aspect of an object-oriented software
system. It illustrates the architectures of the software components and the dependences between
them.In the Unified Modeling Language, a component diagram depicts how components are
wired together to form larger components and or software systems. They are used to
illustrate the structure of arbitrarily complex systems. A component is something required
to execute a stereotype function. Examples of stereotypes in components include executable,
documents, database tables, files, and library files.
Components are wired together by using an assembly connector to connect the

required interface of one component with the provided interface of another component. This
illustrates the service consumer - service provider relationship between the two components.
Figure 7.1 Component Diagram
63
8. Deployment diagram
Deployment diagram in the Unified Modeling Language models the physical deployment
of artifacts on nodes. To describe a web site, for example, a deployment diagram would show
what hardware components exist what software components run on each node and how the
different pieces are connected.
Deployment modeling is used to show the hardware of the system, the software that is installed in
the hardware and also the middleware that is used to connect the disparate machines to one and
other. It also shows how the software and the hardware components work together.
The deployment diagram helps to model the physical aspect of an object-oriented software
system. It models the run-time configuration in a static view and visualizes the distribution of
components in an application. In most cases, it involves modeling the hardware configurations
together with the software components that lived on.
Application Server
Client Server Apache Server

Http request Database Server
Search item
My sql server
View Orders
Customer
Warehouse Employee Ordered item
DB
Manage Employees
Administrator
Figure 8.1 Deployment Diagram
64
Chapter Four
Implementation Document
1. Introduction
The implementation document helps to the users on how to work with the system. This
implementation document acts as a user manual and it helps to the users not to be confused with
the system. It includes sample pages and sample code of our system. It gives the users a brief
over view of the system.
Our project implementation contains the code and its data base connection. The implementation
is carried out with the results that have been obtained from the feasibility study and analysis.
The system is implemented by finishing the project with the help of appropriate tools that
been suggested and are loaded in to the server. Then the system is tested with appropriate data
inputs to check the successfulness of the system. This being carried out by inputting data that are
of rare to be inputted. Then the system administrator will be trained of the operational
functionalities to control and maintain system at a later stage.
2. Report on Implementation
The first phase in the implementation of a system is the plan to make it implement. For proper
implementation the plan is a pre-requisite and is known as pre-implementation activity. It is in
these steps that various activities which are required for implementing a system are identified and
their sequence and relation to each other is desired. In this step various other estimates like time
required for each activity and cost estimates are also obtained. For the better description of the
plan and implementation various tools like Gantt charts have been used.
65
The implementation is to change what we did in the design phase by writing code using php to all
forms. The system contains many forms that are connected to the data base in each individual
form also combined in one module in order to work the system as whole. Implementation is all
about the description of the overall developed system how users interact and use the system.
According to proposed we like to describe the implementation or how user can simply
interact with the website. Coupon card system of online shoping system is developed to easy
buying and selling using the automated system.
The users of the system are:
 Administrator
 Warehouse employee and
 Customers
Administrator and Warehouse employee of the shopping have their own account to manage the
system control all over all thier tasks in the website. The external user or customer of the system
have to create account to interact or to buying and selling using the the system.
The administrator is the person who is responsible for controlling the user add and delete the user
account, view orders and view the feedback from customer. The warehouse employee is the
person who is responsible for controlling the products add, update and delete the product
categories and view orders of customer. The customer is person who can do the activities
like ordering the product, give the feedback for the administrator.
66
3. Sample Code
3.1. Sample code for Login
if (isset($_POST['signin'])){
$en = $_POST['user_name'];
$user_name=base64_encode($en);
$enp = $_POST['password'];
$password=base64_encode($enp);
$query = "SELECT * FROM account WHERE user_name='$user_name' AND password='$password' ";
$result = mysql_query($query)or die(mysql_error());
$num_row = mysql_num_rows($result);
$row=mysql_fetch_array($result);
$row_id=$row['user_name'];
$account_type =$row["account_type"];
$row=mysql_fetch_array($result);
if( $num_row > 0 ) {
if($account_type=="Customer"){
67
result1 = mysql_query("Select fname,lname from customer where user_name='$row_id'") or die("Un able

to select from employee".mysql_error());
$rr =mysql_fetch_array($result1);
$_SESSION['fname']=$rr['fname'];
$_SESSION['lname']=$rr['lname'];
echo "<script>windows: location='customerindex.php'</script>";
$_SESSION['id']=$row_id; }
else if($account_type=="Admin"){
result1 = mysql_query("Select fname,lname from employee where user_name='$row_id'") or
die("Un able to select from employee".mysql_error());
echo "<script>windows: location='delete_account.php'</script>";
$_SESSION['id']=$row_id; }
else if($account_type=="WHEmployee")
{
$result1 = mysql_query("Select fname,lname from employee where user_name='$row_id'") or
die("Un able to select from employee".mysql_error());
echo "<script>windows: location='update_product.php'</script>";
$_SESSION['id']=$row_id;
}
}
else {
echo '<div class="alert alert-dismissable alert-danger error" >';
echo '<strong>'.'<center>'."This User Name AND Password Are Not
Correct!".'</center>'.'<strong>';
echo '</div>';
}
}
?>
68
3.2. Sample code for product form
<form method="post" action="cart_update.php" onclick="return confirmdelete();" >
<div class="product-content" style="width:200px;"><h3>{$obj->product_name}</h3>
<div class="product-thumb"><img src="{$obj->product_img_name}" height="17%"

width="160px"></div><br>
<div class="product-desc">{$obj->product_desc}</div>
<div class="product-info">
<div class="product-info1">Price {$currency}{$obj->price} </div>
<fieldset>
<label>
<span>Quantity</span>
<input type="text" size="2" maxlength="2" name="product_qty" value="1" />
</label>
</fieldset>
<input type="hidden" name="product_code" value="{$obj->product_code}" />
<input type="hidden" name="type" value="add" />
<input type="hidden" name="return_url" value="{$current_url}" />
69
<div align="center">
<button type="submit" name="add" class="add_to_cart">Add To Cart</button>
</div>
</div></div>
</form>
3.3. Sample code for shopping cart
if(isset($_SESSION["cart_products"])) //check session var
$total = 0;
foreach ($_SESSION["cart_products"] as $cart_itm)
$product_name = $cart_itm["product_name"];
$product_qty = $cart_itm["product_qty"];
$product_price = $cart_itm["product_price"];
$product_code = $cart_itm["product_code"];
$subtotal = ($product_price * $product_qty);
echo '<td><input type="text" size="2" maxlength="2" name="product_qty['.

$product_code.']" value="'.$product_qty.'" /></td>';
echo '<td>'.$product_name.'</td>';

echo '<td>'.$currency.$product_price.'</td>';
echo '<td>'.$currency.$subtotal.'</td>';
echo '<td><input type="checkbox" name="remove_code[]" value="'.

$product_code.'" /></td>';
echo '</tr>';
$total = ($total + $subtotal);
$grand_total = $total + $shipping_cost;
foreach($taxes as $key => $value){ //list and calculate all taxes in array
$tax_amount = round($total * ($value / 100));
$tax_item[$key] = $tax_amount;
$grand_total = $grand_total + $tax_amount;
$_SESSION['total'] = $grand_total;
$list_tax = '';
foreach($tax_item as $key => $value){ //List all taxes
$list_tax .= $key. ' : '. $currency. sprintf("%01.2f", $value).'<br />';
$shipping_cost = ($shipping_cost)?'Shipping Cost : '.$currency.
sprintf("%01.2f", $shipping_cost).'<br />':'';
else{
echo " <h1>You Cart Is Empty</h1> ";
71
3.4. Sample code for coupon printing
<?php
$query=mysql_query("select * from admin_coupon where cop_status = 'Unused'")or die(mysql_error());
$count = mysql_num_rows($query);
$i=0; while($row=mysql_fetch_array($query))
$i++;
$card_id=$row['cop_id'];
$card_status=$row['cop_status'];
?>
<tr style="background:FloralWhite ;border:8px solid white ;" border="3">
<td> <h4 style="font-family:times new roman;"> <?php
echo ' <img class="framed" SRC="images/cop.jpg" width="100%" height="40%" /><br><br>';
echo " Card Serial Number. “.” ".$row['cop_number'].'<br>';
echo " Amount Balance. “.” ".$row['cop_balance'].'<br>';
72
echo" Date Of Production: “.”".$row['pro_date'].'<br>'.'<br>'.'<br>';
echo " Instruction: “.” "."To Recharge Your Account Fill Card Serial No. In Provided Space!";
?> </h4><br>
</td>
</tr>
<?php
?>
3.5. Sample code for database connectivity

<?php
$currency = '$'; //Currency Character or code
$db_username = 'root';
$db_password = '';
$db_name = 'final pro';
$db_host = 'localhost';
$shipping_cost = 0; //shipping cost
$taxes = array('VAT' => 15,);
//connect to MySql
$mysqli = new mysqli($db_host, $db_username, $db_password,$db_name);if ($mysqli-

>connect_error) {die('Error : ('. $mysqli->connect_errno .') '. $mysqli->connect_error);
?>
73
4. Testing
The approach of web application testing adopts the basic principle for all software testing and
applies a strategy and tactics that have been recommended for object oriented system. the
following steps summarizes the approach.
4.1. Unit Testing
When web apps are considered, the concepts of the unit changes, each web page encapsulated in
itself content navigation link as well as script, form and applet (processing element). It is not
always possible or practical to test each of these characteristics individually. Every module of the
System is separately tested. I.e. the team tests every module by applying some selection
mechanism. Through this mechanism every modules gets tested. If an error occurs correction will
be taken without affecting another module. We have tried to test UI screens of our system that
needs to verify screen elements that appears on the screen.
4.2. Integration and System Testing
The strategy for integration testing depends upon the architecture that has been chosen for the
web application. In this testing part, all the modules will be combined together and tested it
for its fitness with each other and with the systems functionality. If error occurs in combining
them, the module with problem will be identified and recombined. Both units testing and
integrated testing are performed by all team members.
Finally, with the modular concept inside the application it is being also tested for its system
reliability. The system reliability will be insured through data integrity rules built into the
database at the backend and the system rules built into the front-end application. The system
will take assurance from the user before making any changes permanent.
74
Error Handling
The integration testing and system testing are used to test whether the entered values are valid or
not. We have done this by providing error message when invalid input is entered. For example, if
the user enters wrong user name and password the system displays an error message.
Maintainability
The system has been designed taking care of modularity. Faults in the system can be traced to
modules.
Validation Checks
This will be as such to maintain consistent and persistent information on the web when most of
the time the project has to deal with uploads so a minor error will down the impression of the
system.
Therefore, validation checks by software itself using the flavors of JavaScript and php codes
manual checks are also necessary as: -
1. Correct entry of data in the form.

2. Correct updating of question and with the most suitable answer etc.
75
4.3. Conclusion
The project concept “shopping cart” is something like the original grocery shop shopping cart
that is used by the customer in selecting certain products. Finally, after selection the customer
confirms orders for all the purchasing items and submits his/her information details with tax
information at the checkout counter. Shopping cart is used around the world in e-commerce to
manage business through online. There are different kinds of software available that are useful
for all in making purchase online. Through this software, one can choose the purchasing item
and the software calculates the net amount for the order including taxes. The software collects
the coupon card information of the customer and it provides a secure gateway for all kinds of
transaction online. The shopping cart software provides a reliable platform for keeping all
sensitive information. Shopping cart software is its security as better security can attract
customer by protecting their personal information. Security features include encrypting
information and using a reputable processing service for credit cards.
76
5. Clients Feedback
During implimentation time client feedback is very important input to the system many users
give us by testing the system we get good feedback. Some of the feedbacks are:
 Work to satisfay many customers of the system.

 Give enough guide to the user in order to know how to use the system.
 Provide many kind of products not only electronic materials
 Provide many kind of language like amharic
 Make suaitable for blind or disable peoples.
From the positive feedback on user we try to develop the system to become more effective and
efficient all direction.
77
6. User Manual
user manual, is a technical communication document intended to give assistance to people using a
particular system. Since the system is web based ecommerce site everything important for the
user will be explained and implemented while giving short training with the document. Our
website is depending on buying and selling products so many users must have an account to
access the functionality of the system by using this manual.
A. User manual for Registration new customer

1. Click on Register button
1. Enter your all information requirement into the box fields and Clicks on Register button.
78
B. User manual for login

1. Click on login button and enter your user name and password into the box fields then
click login button.
C. User manual for Forgot password

1. Click on forgot password button
2. Enter your user name and email address into the box fields and click recover
3. Then the system send your password to your email account
79
D. User manual for feedback

1. Click on feedback button
2. Enter your name ,email address and your comment into the box fields and clicks on send
button.
E. User manual for help

1. Click on help button and open your download page and search help file

F. User manual for Product category list

1. Click on product button
2. Clicks Add To Cart button to add an item to your cart
81
G. User manual for cart management

1. Click on Shopping Cart button
2. Click on Add more items button to add an item
82
3. After adding an items select an item to remove from cart and Clicks OK button
4. The system displays Conformations the click on OK
83
H. User manual to order product

1. Click on Order button
I.User manual to order cancel

1. Click on Cancel order button
84
J. User manual to Edit Profile

1. Click on Update profile button
2. Then edit your information in the box fields and click on submit button
85
K. User manual for change password and user name

1. Click on change password or change user name button
2. Fill your user name and password on the box field and click on update button
86
L. User manual for change profile image

1. Click on update profile button
2. Select you want to upload and click on update button
87
M. User manual for recharging coupon account

1. Click on charge balance button
2. Fill the serial number to box field and click on charge button
88
Appendix
PHP………………..Hypertext Preprocessor
TVM………………….Time Value of Money
CSS…………………….Cascading Style Sheet
MYSQL ………………….MY Structural Query Language
HTML…………………..Hypertext Markup Language
UML. …………………..unify Modeling language
OOSAD………………….object oriented system analysis and design
ER …………………..entity-relationship
Reference
1. Ambler, Scott (2001) The Object primer: The application Developers Guide to Object
Oriented and the UML.2nd rev. Ed England: The Cambridge University Press.
2. Another book Fundamentals of Database Systems, 4th Edition
89

Full Document

Uploaded by

Copyright:

Available Formats

You might also like

Full Document

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

Full Document

Uploaded by

Copyright:

Available Formats

Online Shopping System 2016

2.3. Business rules.........................................................................................................................16

2. Problem statement of the project

Some of the problems exist in the system: -

3. Objectives of the project

3.1. General Objectives

3.2. Specific Objectives

 To minimize time consumption

4. Methodology of the project

We ask some questions for Example: -

 How do you work currently?

4.1.2. Methodology for system analysis and design

4.2. Software Tools we use

4.2.2. Back-end Technologies

5. Scope of the study

 Register new customers

6. Limitation of the project

7. Significance of the project

8.1. Economic Feasibility

Average Salary of each Employee per month = 1000.00Birr

Total money required for payment per year= 10*1000*12= 120,000Birr

Average Number of Employee needed when the new system is deployed= 5

Average salary of each of them per month = 1200.00Birr

Total money required for payment per year= 5*1200*12= 72,000.00Birr

Cost Reduction and Avoidance= 120,000.00Birr-72,000.00Birr= 48,000.00Birr

Name the material Quantity Price per unit Total price

Pen 6 3.50birr 21birr

Printing 85 1birr 85birr

Name of Software price

Microsoft Office Word 2007 free download

Total cost ------------------

8.2. Technical Feasibility

Is the required technology available with the organization?

If so is the capacity sufficient?

8.3. Operational Feasibility

8.4. Schedule Feasibility

10 HARAMAYA UNIVERSITY DEPARTMENT OF INFORMATION SYSTEMS

9.1. Team configuration and management

11 HARAMAYA UNIVERSITY DEPARTMENT OF INFORMATION SYSTEMS

Project Members ID NO. Responsibilities

9.2. Communication plan

Schedule time table for meeting

Member with Members 1.Monday 1:00pm - 4:00pm

2.Thursday 1:00pm - 4:00pm SMS and call phone

3.Sutarday 7:00pm - 11:00pm

Member with Advisor Monday 10:30am12:00am Office meeting, E-mail, and

12 HARAMAYA UNIVERSITY DEPARTMENT OF INFORMATION SYSTEMS

 Decrease time and resource of customers etc.

 Provide sale and buy service to customer

 Provide good and fast service to customer

1.2. Overview the Existing System

1.3. Overview the Proposed System

2.2. Non Functional Requirements

The non-functional requirements of the system are presented below: -

 User Interface: - user friendly interface with easy navigational scheme.

2.3. Business rules

Name: determine need of login

Total money required for payment per year= 10100012= 120,000Birr

Total money required for payment per year= 5120012= 72,000.00Birr