Online Butics Shopping System

SAMARA UNIVERSITY
COLLEGE OF ENGINEERING AND TECHNOLOGY
DEPARTEMENT OF COMPUTER SCIENCE
PROJECT ON
ONLINE BUTICS SHOPPING SYSTEM FOR DUBTI EDERES IN

DUBTI TOWN
SUBMMITED TO
IN PARTIAL FULFILLMENT FOR THE REQUIRMENTS FOR THE

DEGREE OF BACHELOR SCIENCE IN COMPUTER SCINCE
GROUP (2) MEMBERS IDNO
1. GIZACHEW MINALE……………………...CET0040/07
2. YOSEPH WAKGARI………………………CET0096/07
3. BINIYAM ADMASS………………………. CET0055/07
4. HEVEN BELEW……………………………CET0046/07
5. MUZAMILE MUSA………………………...CET0064/07
6. GASHAW YISMAW………………………..CET0038/07
7. NABIYOU ABARA…………………………CET0065/07
ADVISOR NAME: YEHENEW .ADDIS June 2018, SAMARA

SAMARA UNIVERSITY
COLLEGE OF ENGINEERING AND TECHNOLOGY
DEPARTMENT OF COMPUTER SCIENCE
EXAMINERS’ APPROVAL SHEET

As Members of the Board of Examiners of the final BSC degree open defense. We certify
that we have lead evaluated the project prepared by group two under the title “Online
Butics Shopping System for DUBTI EDERES Butics In Dubti Town” and
recommend that it be accepted as fulfilling the project requirement for the degree of
BSC computer science.
-------------------------------- --------------------- --------------

Name of the Chair Person Signature Date
------------------------------- ------------------------ --------------

Name of Examiner1 Signature Date
------------------------------- ------------------------- --------------

Name of Examiner2 Signature Date
------------------------------- ------------------------- ---------------

Name of Advisor Signature Date
Final approval and acceptance of the contingent upon the submission of the final copy of
the project to the department of computer science
Project Approved by:
------------------------- ----------------------------
----------------
Head, Computer Science Signature Date

DECLARATION
We hereby declare that this BSc project is our original work and has not been presented
for a degree in any other university, and all source of materials used for the Project have
been duly acknowledged.
ONLINE BUTICS SHOPPING SYSTEM FOR DUBTI EDERES BUTICS
S.No Name ID Signature Date
1. GIZACHEW MINALE CET0040/07 _______ _________
2. YOSEPH WAKGARI CET0096/07 ________ ___________
3. BINIYAM ADMASS CET0055/07 _________ __________
4. HEVEN BELEW CET0046/07 __________ __________
5. MUZAMILE MUSA CET0064/07 _________ __________
6. GASHAW YISMAW CET0038/07 _________ __________
7. NABIYOU ABARA CET0065/07 ________ __________
Advisor’s Name: Mr.YHENEW ADDIS(MSc)
Signature: _______________________
Date: _______________
ACKNOWLEDGMENT
We would like to express our deepest appreciation and special thanks to our advisor Mr.
YHENEW ADDIS. who give us immeasurable help to done our project. Without his
guidance and persistent help this project would not have been possible with this time. We
have also special thanks to the workers of DUBTI EDERES butics shop who helped us in
providing the necessary information and material such as working manuals for preparing
this document. Finally, we would like to forward our special thanks to college of
engineering and technology of computer science department, who gave us by preparing
laboratory class and internet to done our project.
SU CS 4th YEAR FINAL PROJECT I

Page
ABSTRACT
The general objective of the project is to change the existing paper based system in the
computerized system. We use primary data collection mechanism such as interview,
observation, questionnaire, document analysis and also for designing purpose we use
object oriented methodology. Butics shopping, also known as e-commerce is a type of
industry where buying and selling of a product is conducted over butics shopping
systems such as the internet. This web based shopping system is mainly designed for the
DUBTI EDERES organization and it will be easy, fast, suitable and efficient system.
And it can be performed simple with a little knowledge of computer. This project is the
output of our planning, schedule, programming skill and the hard work, and this report
reflects our steps taken at various levels of programming skill, planning and schedule.
The purpose of this application is to bring knowledge to students about e-commerce and
how an interactive e-commerce application can be designed from scratch using client-
side languages, such as JavaScript and HTML, combined with the server-side Php
language through wamp Server Faces. The server side, mostly Php, contains all the
implementation related to setting up the database, creating session models for joining
different userinterface pages(UI), calculating the shipping costs and sales tax, etc.
SU CS 4th YEAR FINAL PROJECT II

Page
Table of Contents
ACKNOWLEDGMENT............................................................................................................I
ABSTRACT............................................................................................................................II
LIST OF TABLE....................................................................................................................VII
ABBREVIATION.....................................................................................................................X
CHAPTER ONE ............................................................................................................................

1
1. System requirement specification ...............................................................................
1
1.1. Introduction ..............................................................................................................
1
1.2. Background of the organization ...............................................................................
1
1.3. Background of the study ..........................................................................................
1
1.2 Literature Review ....................................................................................................
2
1.3 Statement of the problem.........................................................................................
2
1.4 Objectives................................................................................................................ 3
1.4.1 .General objective.............................................................................................. 3
1.4.2 Specific objectives .............................................................................................
3
1.5 Significance of the system........................................................................................
3
1.6 Scope and limitation .................................................................................................
4
1.6.1 Scope................................................................................................................. 4
SU CS 4th YEAR FINAL PROJECT Page III

1.6.2 Limitation ..........................................................................................................

4
1.7 Methodology ............................................................................................................
4
1.7.1 Data gathering ................................................................................................... 4
1.7.2 Design methodology ..........................................................................................
5
1.7.3 Analysis methodology .......................................................................................
5
1.8 Hardware and software used for implementation ....................................................
6 1.9. Testing methodology .......................................................................................
7
CHAPTER TWO ......................................................................................................................... 8

2. requirement elicitation................................................................................................. 8
2.1. Overview of the Existing System............................................................................. 8
2.2. Problem of the existing system................................................................................ 8
SU CS 4th YEAR FINAL PROJECT IV

2.2 Weakness and strength of the existing system........................................................ 9

2.2.1 Weakness of the existing system....................................................................... 9
2.2.2 Strength of the existing system.......................................................................... 9
2.3 Business rules of the system. ..................................................................................
9
2.4 Overview of the proposed system ...........................................................................
9
2.4.1 Functional requirements ..................................................................................
10
2.4.2 Nonfunctional requirements ............................................................................
11
2.6. Constraints and assumptions ..................................................................................
11
2.6.1 Constraints........................................................................................................ 11
2.6.2 Assumptions..................................................................................................... 12
CHAPTER THREEE ............................................................................................................... 13

3. system modeling ....................................................................................................... 13
3.1. Introduction........................................................................................................... 13
3.2. Use case identification ...........................................................................................
13
3.3. Use case diagram ...................................................................................................
14
3.3.1. Actor specification .......................................................................................... 14
3.3.2. Use case description ........................................................................................
16
3.4. Sequence diagram.................................................................................................. 30
3.5. Class diagram .........................................................................................................
42
CHAPTER FOUR...................................................................................................................... 44
4. System design ................................................................................................................... 44
SU CS 4th YEAR FINAL PROJECT Page V

4.1 Design Goal ............................................................................................................ 44

4.2 System Decomposition and interrelation between them......................................... 44
4.3 System Architecture ................................................................................................
46
4.4 Deployment Diagram ..............................................................................................
47
4.5 Persistence Data management .................................................................................
48
4.6 Access Control and Security................................................................................... 49
4.7 User interface design............................................................................................... 50
CHAPTER FIVE ..................................................................................................................... 59

5. Implementation and Testing ...................... ...................................................................... 59
5.1. Objective of the Implementation ............................................................................
59
5.2. Constraint of Implementation.................................................................................
59
5.3. Sample code and description ..................................................................................
59
5.4. Testing Overview ................................................................................................. 65
5.4.1 Test by scope ........................................................................................... 65
5.4.2 Unit testing............................................................................................ 66
5.4.3. Integration testing .......................................................................................... 67
5.4.4. Testing by requirements ..................................................................................
67 5.4.5. Test implementation (Validation testing)........................................................
68
CHAPTER SIX......................................................................................................................... 69
6. Conclusion and Recommendation .................................................................................... 69
SU CS 4th YEAR FINAL PROJECT Page VI

6.1 Conclusion.............................................................................................................. 69
6.2 Recommendation ....................................................................................................
70
Reference .................................................................................................................................... 71
LIST OF TABLE
Table 1: Use-case description for Create Account........................................................... 17
Table 2: Use-case description for Login ...........................................................................
18
Table 3: Use-case description for Change Password........................................................ 19
Table 4: Use-case description for Search Item................................................................. 21
Table 5: Use-case description for View Item ...................................................................
21
Table 6: Use-case description for Order Item ...................................................................
23
Table 7: Use-case description for View Order................................................................. 24
SU CS 4th YEAR FINAL PROJECT Page VII

Table 8: Use-case description for Update Item.................................................................

26
Table 9: Use-case description for Registration Item........................................................
28
Table 10: Use-case description for Generate Report........................................................ 29
Table 11: Use-case description for Logout....................................................................... 30
Table 13: Test case to Admin Login ................................................................................
66
LIST OF FIGURE
Figure 1:Use case Diagram ...............................................................................................
15
Figure 2 : login sequence diagram ....................................................................................
31
Figure 3: create account sequence diagram ......................................................................
32
Figure 4:change password sequence diagram ...................................................................
33
Figure 5: search item sequence diagram ...........................................................................
34
Figure 6: view item sequence diagram............................................................................. 35
Figure 7: order item sequence diagram.............................................................................
36
Figure 8: view order sequence diagram ............................................................................
37
SU CS 4th YEAR FINAL PROJECT Page VIII

Figure 9: update item sequence diagram.......................................................................... 38

Figure 10: register item sequence diagram....................................................................... 39
Figure 11: generator report sequence diagram ..................................................................
40
Figure 12: logout sequence diagram .................................................................................
41
Figure 13: Class diagram .................................................................................................
43
Figure 14: system Decomposition diagram ......................................................................
45
Figure 15: System Architecture ........................................................................................
46
Figure 16: Deployment diagram .......................................................................................
47
Figure 17: persistence data management diagram........................................................... 48
Figure 18: home page user interface .................................................................................
50
Figure 19: customer login page user interface ..................................................................
51
Figure 20:customer registration user interface .................................................................
52
Figure 21:Admin login page user interface ......................................................................
53
Figure 22:Admin page user interface ................................................................................
54
Figure 23:product register page user interface ..................................................................
55
Figure 24:shopping cart user interface ..............................................................................
56
Figure 25:customer transfer money user interface............................................................
57
SU CS 4th YEAR FINAL PROJECT Page IX

Figure 26:Customer buy page ...........................................................................................

58
SU CS 4th YEAR FINAL PROJECT Page X

ABBREVIATION
CD-RW Compact Disk rewritable
CSS Cascading Style Sheet
HTML Hypertext Markup Language
JS Java Script
MYSQLMY Structured query language
OBSS Online Butics Shopping System
PHP Hypertext pre processor
RAM Random Access Memory
SU Samara University
UC Use case
UI User- Interface
UML Unified Modeling Language

WAMP WindowApachMySQLPHP
SU CS 4th YEAR FINAL PROJECT XI

Page
CHAPTER ONE
1. System requirement specification
1.1. Introduction
This chapter deals about the system requirement specification that follows to analysis and
design methodology. Statement of problem, proposed objective, scope, limitation,
literature review, hardware and software implementation and test methodology.
1.2. Background of the organization

The Afar Regional State is one of the nine region states of Ethiopia, and is the home land
of the Afar people. Formerly known as Region 2, its new capital as of 2007 G.C capital is
the recently constructed city of Samara. Currently, samara and Dubti lead by one
Administrative town. Dubti is town that is located in afar region, 588km North-East of
Addis Ababa. In the town there are different butics shopping systems some of them are: -
DUBTI EDERES, HJERA, PISSYA, AFRICAN, etc. the developer selected one of them
this is DUBTI EDERES butics. It is located in Dubti town in front of awash middle
clinic. The manager name of the shop is EDERES.The butics shopping system in Dubti
town was started its work in 2002 E.C in the form of small shopping system with a few
amounts of items. Then, After 2004 E.C the shop becomes a large by adding many
butics materials such as dress, trouser, shirt jacket, max dress and sharing jacket, shoes
etc.
1.3. Background of the study

The butics shopping system in Dubti Town refers to a place that store and sells butics
which enable customers to buy products over the internet. Customer can visit web stores
from the comfort of their homes and shop as they sit in front of the computer. hence, the
project will be designed to intend to bring about the changes, the development and better
improvement of the customer services through enhancing butics shopping system and the
SU CS 4th YEAR FINAL PROJECT Page XII

effective use of computer technology to enhance the customer can view, buy their
favorite’s product item.
1.2 Literature Review

E-commerce has become a standard method of distributed information to many different
platforms. It is being implemented by a growing number of companies to be more
completive in corporate world. All companies need to make a step forward and towards a
new technology. To be able to complete with the global market, e-commerce was a good
answer (Lanvin and Maggarqul, 2006).The organization websites seem to have
significant influence on sales and corporate image are expected to contribute to overall
customer satisfaction(Hossain,2007). In DubtiTown there are different butics shopping
that works related with our project. But the shop in Dubti Ederes is concerned with
different products items likeshoes, dress, jacket …etc. Base on the outcome of the
literature review performed a conceptual framework that guided the design and
performance of the empirical studies. Aiming at providing answers to the proposed
search question is also presented. Butics 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[3].
1.3. Statement of the problem

It is clear that an organization to be well organized and operative, there must be high file
management and fast retrieval and handling method. Thus are the difficulties that
avoided in new scheme are:-
 Customer has shortages of information about butics product item in order to buy
easily.
 Searching of items is time taking and it also increasing the work load of the
workers.
 There is information gap between the customer and administrator.
SU CS 4th YEAR FINAL PROJECT Page XIII

 When generating report, it takes time and it may not be easy to manage and
analysis the monthly work due to massive collection of data.
1.4. Objectives
1.4.1 .General objective

The general objective of our project is to develop online butics shopping system for
Dubti Ederes organization in Dubti town.
1.4.2. Specific objectives

 Perform a requirement analysis to find out the system functional and
nonfunctional requirement.
 Design the system using object-oriented models for understanding the system and
to make the implementation easy.
 To evaluate its performance and acceptability in terms of security,

userfriendliness, accuracy and reliability.
 To develop a system that will surely satisfied the customer service.

 Test the performance and reliability of web application.
 To develop system that used to check the customers product need.
 To develop a database for butics shopping and store products.
1.5. Significance of the system

The significance of this project is to solve partial problems within the shopping
system . This project is much more important to:
 Customers are very relevant because it can give clear product in the shop.
 Easily add, delete, and update product item.
 To minimize time and efforts needed to perform tasks.
 The system will provide secure services to customers and easy to use.
SU CS 4th YEAR FINAL PROJECT Page XIV

1.6. Scope and limitation
1.6.1. Scope our project should be overcome the drawbacks of their manual system by
replacing computerized system and it provide simple, efficient environment and reduce
time consuming and this project only limited for Dubti town. Generally, part of our
project address: -
 View register customer, view item, and order item, Update item, register item and
View order and generate report.
 Delete product items from database by Administrator.

 Sending and receiving message between Administrator and customer.
 The system generates delivered report.
 Search products using dropdown menu.
 The system announces the total price of the purchase product.
1.6.2.Limitation
 It does not search the item by color, discount ,number
 The system not consider for backward item from customer.
 The system is also does not consider ATM.
1.7. Methodology
1.7.1. Data gathering

The team will use the following requirement determination methodology for the
development of our project:
 Interview: -The teamwas use open interview method asked to EDERES to get
the basic information and background information for thebutics shopping system.
 Observations: -We observed physically the current existing system which is

done manually and observe how they perform each activity.
SU CS 4th YEAR FINAL PROJECT Page XV

 Document analysis: -To understand the existing system, we can collect more
information by referring books, documents and other reading materials about
shopping system with through internet.
1.7.2. Design methodology
During this phase our team will use E-draw max software to refine the use case model,
and to reflect the establishment environment, model object interactions and behavior
that support the use case scenario, and finally update object model to reflect the physical
environment, the users and other people, their work process, and so on. It is critical for
analysts and developers to understand the application domain for a system to accomplish
its intended task effectively [5].
1.7.3. Analysis methodology
The object-oriented approach to software development is decidedly a part of the

mainstream simply because it has proven to be of value in building systems in all sorts
of problem domains and encompassing all degrees of size and complexity. Furthermore,
most contemporary languages, operating systems, and tools are objectoriented in some
fashion, giving greater cause to view the world in terms of objects[4].
The data analysis model applied in this project is an object oriented approach. That is
Object oriented method is select because of the process of analyzing a task (also known
as a problem domain) to develop a conceptual model that can then be used to complete
the task. A typical object oriented approach model would describe computer software
that could be used to satisfy a set of customer-defined requirements[1].
The system analysis model must achieve two primary objectives:-  To
establish the basis for the enhancement of a software design.
 To define a set of requirement that can be validated once the software is

completed enhanced.
SU CS 4th YEAR FINAL PROJECT Page XVI

When it comes to objective it is required to generate rapid and continuous value,

because the template is going to be used in organization and different events before the
official release. Besides any developer interested in the platform should be able to use
the current capability of the system. Consequently, regular small releases of the template
with new added functionality are highly desirable. [2]
1.8. Hardware and software used for implementation

For the project implementation; the following Software and hardware tools are used.
Hardware Tools: -
 Server: for connection to the client computer (to host the system.
 Desktop computer with 2 GB RAM and 150 GB hard disk.
 CD/DVD and flash disk to take back up.
 The laptop with 4 GB RAM and 80-300GB HDD. Software Tools
For the System implementation the following software’s are used.
 Microsoft Office word 2007: - for writing documentation.

 Microsoft edraw Max 8.4 version: - for drawing different UML diagrams.
 Php:-scripting language.
 Html:-Client side coding.
 Css:-for the formatting of the web site.
 Java script:-Client side scripting.
 MySql:-for database.
 Notpad++:-It is used as reserve code to write this project.
 Window-7 operating system: - for used to code running the application.
 Microsoft Office power point 2007: - for used to presentation.
 WAMP SERVER: -This software assists to create database or back end of the
system ,to run and test system application.
SU CS 4th YEAR FINAL PROJECT Page XVII

 Anti-Virus software:- used to keep secure ,scan,fix Flash Disk and to prevent
data destruction and corruption.
1.9. Testing methodology

The Butics shopping system was be tested using the following system testing
methodology.
Unit testing: - Each module was be test separately and often performed by the coder
himself simultaneously along with the coding of the module. The purpose is to exercise
the different parts of the module’s code to detect coding errors.
Integration Testing: -The modules was be gradually integrated into subsystems, which
are then integrated to eventually to the entire system. Integration testing will be done to
detect design errors by focusing on testing the interconnection between modules.
System Testing: - After the system is put together, it was be performed. The system will
be tested against the system requirement to see whether the entire requirements meet and
whether the system performs as specified by the requirement.
SU CS 4th YEAR FINAL PROJECT Page XVIII

CHAPTER TWO
2. Requirement elicitation
2.1. Overview of the Existing System

The existing system of DUBTI EDERES BUTICS is a manual system.
In the existing system shopping are takes place in traditional way or a person must be
there physically to participate on the open shopping system. A traditional open shopping
system is an aggregation of supply and demand in the marketplace to effectively establish
a price for a product or service.
The detail existing system function are listed below: -

 The administrator asks the customer about their desire to purchase.
 The customer tells what type of goods needs to buy.
 The administrator shows the goods to the customer and tells the price.
 If the customer agrees with the price of the goods, then he/she pays the price.
 The administrator receives the money and gives receipt
2.2. Problem of the existing system

The existing system has many problems in the working procedure for the organization
and customer. These are: -
 Risk of management data due to massive data collection.

 Accuracy not guaranteed.
 Lack of awareness.
 Not in reach of distance users.
 Not provide online purchasing.
 The customers may be resulted to unnecessary extra expense and waste their
time.
 The customer might not get service of the organization twenty-four hours a
day and seven days a week.
SU CS 4th YEAR FINAL PROJECT Page XIX

2.2. Weakness and strength of the existing system
2.2.1. Weakness of the existing system

There are many problems for businessmen but the great one is excessive charge backs.
The weaknesses of the system are: -
 Consuming large volume of paper work.

 Lack of immediate retrieval of the required information.
 Lack of prompt updating.
 Time for shopping can make the customer’s options to purchase products from
other places.
2.2.2. Strength of the existing system

The strength of the existing system gives additional service for the customer during
purchasing items. i.e. it purchases the item in credit, satisfy the customer, it prepare
receipt for purchasing item because it uses manual system.
 A distribution of work for the Administrator.

 The Administrator have their own privilege (freedom).
 The customers can buy items in a good price.
2.3. Business rules of the system.

The business rules also implement its own business rule and regulation which are
followed to perform work in easier and best manner.
BR1: -almost all items have some time guaranties given by the business rule.
BR2: -The customer or the owner would purchase with an appropriate.
BR3: -The copy of the original receipt is left for the business rules.
SU CS 4th YEAR FINAL PROJECT Page XX

2.4. Overview of the proposed system

In day to day life, we will need to buy lots of goods or products from a shop. Now days,
it is really hard to get some time to go out and get product item by ourselves due to busy
SU CS 4th YEAR FINAL PROJECT Page XXI

life style or lots of works. In order to solve this, E-Commerce websites have been started.
Using these websites, the customer can buy goods or products by using Account number
preparing a bank database just by visiting the website and ordering the item online. . It
requires lots of time to travel to the particular shop to buy the goods. Since everyone is
leading busy life now days, time means like money to everyone. Also there are expenses
for travelling from house to shop.
In order to overcome these, we have e-commerce solution, i.e. one place where we can get
all required goods/products online. User can choose different products based on
categories, delivery services.
2.4.1. Functional requirements

Functional requirements describe the interaction between the system and its environment
independent of its implementation. The environment includes the user and any other
external system with which the system interacts.
Hence our system has different requirements: -

 The system will allow customer and Administrator to login to the system.
 The system will allow customer to create account.
 The system will allow customer and Administrator to change their password
 The system will allow customer to view items with full information (type, image, and price).
 The system will allow customer to order the item.

 The system will allow Administrator to register item.
 The system will allow Administrator to update item.
 The system will allow Administrator to generate report.
 The system will allow customer and Administrator to logout.
 The system will allow Administrator to delete and edit an item.
 The system will allow Administrator to view customer.
 The system will allow customer to transfer money.
 The system will allow customer and Administrator to search item from the system.
SU CS 4th YEAR FINAL PROJECT Page 10

2.4.2. Nonfunctional requirements

As the name suggests, non-functional requirements are requirements that are not directly
services concerned with the specific functions delivered by the system. These are
constraints on the functions offered by the system.
 Security: -should allow login to only authorized users.

 Performance: -this system gives service 24 hours per day with minimum response time so, it is
easy to participate on the shopping system.
 Reliability: - the proposed system will be better due to proper storage of information when users
access the system.
 Availability: - All data in the system will be available all the time.
 No Redundancy: - In the proposed system can be avoided reputation of data anywhere in the
database.
 Accuracy: - The proposed system will be better due to reduction of error. All operation can be
done correctly and it ensures that whatever information is coming from the data base is accurate.
 Efficiency: - The system must ensure allocation and use of services being requested for the users
by using minimum memory storage, cost, time and human power.
2.6. Constraints and assumptions
2.6.1 Constraints
Constraints are something limit or impose our project. A constraint can be two types which are:-
1. Business constraint: - It depends on the state of the organization. Some of them in

our proposed system are:-
 During gathering information the manager not always present on their office.
 The time schedule limits our project function of working in order to submit before the
given time deadline.

2. Technical Constraints:-It depends on security and safety. Some of them in our proposed
system are:-
 Network connection problem.

 We does not get lab when we want.
2.6.2 Assumptions
It is a belief of what we assume that are expected to happen during the project's life cycle.
Thus are:-
To access the system the customer should be in network coverage area.
 Customer must be good in computer usage.

 The administrator must check if order is existing or not from the customer.
 Customer must know English language.
 Customer must know the address of web.
 All software and hardware requirements are fulfilling.

CHAPTER THREEE
3. System modeling
3.1. Introduction
This chapter deals about the modeling technique that follows to design the system. Object
oriented analysis design technique will be used. It includes system use case model,
sequence diagrams, class diagram Actor specification, use case identification &use case
description.
3.2. Use case identification

A use case is an interaction between users and a system. It captures the goal of the users
and the responsibility the system to its users. It is the functionality of the system or the
service provided by the system. A use case describes a sequence of action that provides a
measurable value to an actor and draw as a horizontal ellipse.
1. UC-01: Create Account

2. UC-02: Login
3. UC-03: Change password
4. UC-04: Search Item
5. UC-05: View Item
6. UC-06: Order Item
7. UC-07: transfer money
8. UC-08: View Order
9. UC-09: View customer
10. UC-10: Update Item
11. UC-11: Item Registration
12. UC-12: Generate Report
13. UC-13: Logout

14. UC-14: Delete Item

15. UC-15: Edit Item
3.3. Use case diagram
3.3.1. Actor specification

Actor:-It can be a person, service, organization or other system that play a role in one or
more interaction with our system. Actor has a goal and this goal is what the actor wants to
achieve by interacting with the system.
The following are actors in our project:-

1. Customer: -The customers can get online shop service from the system, which are
capable of order, search, and view item.
2. Administrator: -The person who manage, controlling and coordinating the activity and
responsible for register item, update item, view order, generate report.

Figure 1:Use case Diagram

3.3.2. Use case description
Use case UC-01

number
Use-case Create Account

Name
Actor Customer
Description These use case allow customer to create account to the system.
Precondition The customer wants to create account on our system.
Basic course User Action System Response

of Action
1. The customer home page to 2. The system creates register account

create account and click on user interface and form.
create account link.
4. The system controller verifies a
3. The customer fill form on form and check the form is verified.(If it
create account form and create does not verify back to step 3 or re enter
account. their information)
5. The system send request to

database to save account and reply
account created is saved to the
controller.

6. The system reply account is

successfully created on create account
user interface. 7. Use case Ends.
Table 1: Use-case description for Create Account
Use-case UC-02
Number
Use-case Login
Name
Actor Administratorand Customer

Description This use case describes how Administrator and customer , to login to the
buying system
Pre-condition Actor must have Account

Postcondition If the use case was successful, the Actor is now logged in to online shopping
system. If not, the system state is unchanged.
Basic course User action System Response

of Action
1. The Administrator and
customer are open

home page to login to 2. The system prompts the Administrator

the system. and customer to enter user name and
password.
3. The Administrator and
customer submit username 5. If they have an account the system
and password. 4. If they verifies that all the filled have been filled out
have no username and and the login controller check username and
password create new password are valid.
account and apply 2&3. 6. The controller request to login the
database and it retrieve the information and
send to the controller.
7. If the authentication false it back to the

login form and if true back to main menu.
8. The system successfully logged in the

system. 9. Use case Ends.

Alternate 3.1 If all fields are not filled out and not matched to the username and
course of password the system notifies the actor message username and password is
Action incorrect and then goes back or returns to step 2 of basic course of Action to
enter again
Table 2: Use-case description for Login
Use-case UC-03
Number
Use-case Name Change password
Actor Customer and Administrator
Description These use case allow and Administrator to change password from the
system.
Per-condition Customer and Administrator want to change password.

Basic course of User Action System Response
Action

1. The user wants to change password on 2. The system creates change

main menu and click change password password user interface and
link. form.
3. The user fills a form and change 4. The system controller

password on the form. verifies the form and check
the form is verified.
5. The controller send

request to database to change
password and it send the
changed password to
controller.
6. The system
replay password
successfully changed
on change password user
interface. 7. Use case Ends.
Table 3: Use-case description for Change Password
Use-case UC-04
Number
Use-case Search Item

Name

Actor Customer and

Administrator
This use case permits Customer to search item from item list in order to
Description
display.
Precondition UC-02

of Action
1. The Administrator and 4. The search controller verify

customers enter to home page item name and check item is
to search the item. verified.
2. The Administrator and 5. The system controller sends

Customer enter the item name the request item to database and it
on search form. retrieve the information and back to
controller.
3. Clicks on search button.
6. If the item is found it display
on the home page user interface, if
not display item is not matched
message.
7. Then the system display all

information about the item based
selected list.
8. Use case End.

Alternative 5.1 If any lists are not selected from the search system goes back or
course
returns to step 2 of basic course of Action to search the item.
of
action
Table 4: Use-case description for Search Item
Use-case UC-05
Number
Use-case View Item

Name
Actor Customer
Description This use case allows Customer to view or display all items with
their detail description about the item.
Preconditio Item select

n
Basic User Action System Response

courseof
Action 1. The Customer opens the system to 2. The system send
enter home page. request item to database.
3. The system display
item on home page user
interface.
4. Use case Ends.
Table 5: Use-case description for View Item
Use-case UC-06
Number
Use-case Order Item

Name
Actor Customer
Description These use case allow customer to order the item from the system.
Pre-condition UC-02

of Action
1. The customer is in home 2. The system creates search form.
page.
4. The system controller
3. The customer writes and verifies the input and check input
search item on search form. 6. is verified.
If the item found the customer
5. The system retrieves the
select it on main menu.
item and the retrieved search
7. The customer click add to result and also the result not found
cart link and click the cart and put on home page.
display cart user interface.
8. The system create order button.
9. The customer click order
10. The system creates
button.
confirmation and clicks and sends
11. The customer writes the text to customer and saves to the
message and confirm on email database.
form.
12. The system verify message on
database and send message
ordered is successful on cart user
Interface.
12. Use case Ends.
Alternate 6.1 If the item is not found the system state is unchanged.
course of action
Table 6: Use-case description for Order Item

Use-case Number UC-07
Use-case Name View Order
Actor Administrator
Description
These use case allow Administrator to view order form the
system.
Pre-condition UC-02
Post-condition The Administrator views the customer order.

of
Action
1. The Administrator 2. The system create order

initiates to view orders on link.
main menu.
4. The system sends the
3. The requested order to DB and

Administrator clicks display orders on order

the order link.
UI.
5. Use case Ends.
Table 7: Use-case description for View Order
Use-case Number UC-08
Use-case Name Update Item
Actor Administrator
Description This use case permits staff to update or modify item information
Pre-condition UC-1 & UC-2
Post-condition Updated item information
User Action System Response

Basic course of Action
1. The administrator enter

main menu to update item.
3. The administrator writes

the item and search on
search form. 6. The
administrator enters update
item information and click
update.
2. The system creates update item user

interface and form.
4. The system controller verifies a

form and check form is verified.
5.The system controller send
request item to database and it
retrieve the item and back to
controller and it display item
information on update item user
interface.
7. The controller verifies the form

and send request to update item on
database.
8. The successfully updates

information into database.
9. Use case Ends.

Alternate course of Action 6.1 If item is not found back to basic course of action 6
to update item.
Table 8: Use-case description for Update Item
Use-case ID UC-09
Use-case Registration Item

Name
Actor Administration
Description This use case permits to register item information of the customers
Pre-condition UC-2
Basic course of User Action System Response

Action

1. The administrator enters the 5. The item controller

main menu to register item. verifies a form and check if it
is valid form.
2. The administrator clicks the
item register link and creates its user 6. The controller register
interface and form. the item in database and it
send the registered item to
3. The administrator fills
controller.
information about the item and
registers the item in item registration 7. If the item correctly
form. registered it display on the
item register user interface.
4. If the item registration form
not found the employee create the 8. The system displays
form. successful item summary.
9. Use case Ends.
Alternate 2.1. If all fields are not filled out and matched to the registration form the
course of system notifies the actor message the item information is incorrect and then
Action goes back or returns to step 2 of basic course of action to register again.
Table 9: Use-case description for Registration Item
Use-case UC-11
Number

Use-case Generate Report

Name
Actor Administrator
Description These use case allow administrator of the organization to generate a report about
the item information of a month.
Precondition Administrator wants to see report , UC-02
Postcondition Generate monthly report information.
Basic course User action System Response

of
Action 1. The administrator wants to

generate report and enter to the
main menu.
2. The administrator cli cks
report pages. 3. The system request to retrieve the report

into database.
4. The system retrieved and generates report

on report UI.
5. Use case Ends.

Alternate 4.1 If the selection information is empty or not found go to 5.

course
of
Action
Table 10: Use-case description for Generate Report
Use-case UC-13
Number
Use-case Logout
Name
Actor Customer and Administrator
Description These use case allow customer and manager to logout from the
system at a time of accomplishing their work.
Precondition UC-02
Postcondition System logout

of Action
1. The customer or 3. The system responds to

Administrator wants to logout and the requested action.
enter to main menu.
4. The system successfully
2. The customer or logout back to home page.
administrator clicks the logout
5. Use case Ends.
button.
Table 11: Use-case description for Logout
3.4. Sequence diagram

Sequence diagrams are dynamic model of use cases, showing the interaction among
classes during a specified time period. Sequence diagrams graphically document the use
case by showing the classes, the messages, & the timing of the messages. The interaction
between objects in the system is shown in the following sequence diagrams. [7]

Figure 2 : login sequence diagram

Figure 3: create account sequence diagram

Figure 4:change password sequence diagram

Figure 5: search item sequence diagram

Figure 6: view item sequence diagram

Figure 7: order item sequence diagram

Figure 8: view order sequence diagram

Figure 9: update item sequence diagram

Figure 10: register item sequence diagram

Figure 11: generator report sequence diagram

Figure 12: logout sequence diagram

3.5. Class diagram

“Class diagrams are used to describe the structure of the system. Classes are abstractions
that specify the common structure and behavior of asset of objects. Objects are instances
of classes that are created, modified, and destroyed during the execution of the system.
Class diagram describes the system in terms of objects, attributes, operations, and their
associations”[8].
In the diagram, classes are represented with boxes which contain three parts:
 The top part contains the name of the class. It is printed in bold and centered, and the
first letter is capitalized.
 The middle part contains the attributes of the class. They are left-aligned and the first
letter is lowercase.
 The bottom part contains the methods or operation the class can execute. They are also
left-aligned and the first letter is lowercase.

Custaccount
bankname:Type = varchar(50)
location: Type = varchar(20)
1 username: Type = varchar(30)
pwd:Type=string
1 balance: Type=int())
Customer
Feedback
cust_id:Type = varchar(15) mailid:Type = (10)
FirstName:Type = Varchar(30) sub:Type = varchar(20)
FatherName:Type = Varchar() message:Type = varchar(30)
gender:Type = Varchar(6) mesdate:Type=date()
1 * sender:Type=varchar(20)
email:Type = Varchar(20)
username:Type = Varchar(20) reciver:Type=varchar(20)
1
password:Type = string
address:Type = Varchar(30) * *
phone:Type = varchar(13) Order
regdate:Type = date() ord_id:Type = varchar(20)
prd_id:Type = varchar(20)
username:Type = varchar(20)
+search products() ord_pname:Type = varchar(20)
+order product() ord_qty_:Type = varchar(20)
+view report() price:Type = int(10)
ord_fname:Type = varchar(20) 1
ord_fathername:Type = varchar(20)
ord_date:Type = date(10)
1 drd_date:Type = date(10)
Category billing_address:Type = varchar(20) Admin
address:Type = varchar(20) username:Type = varchar(20)
* password:Type = string
cat_id:Type =varchar(20) admaccno:Type = int(20) email:Type = varchar(20)
sub_cat:Type=varchar(20) price:Type = Decimal(10)
+add category()
description:Type = varchar(20) admaccno:Type = int(20)
delivery_status:Type=Varchar(20) +record product()
+view report()
+deliver product()
1 +view feedback()
+view balance()
1
* 1
Product
username:Type = varchar(20) 1
prd_id:Type=varchar(20)
prd_name:Type = varchar(20) Admin account
photo:Type =varchar(30)
prd_qty:Type = int(10) bankname:Type = varchar(50)
prd_id:Type=varchar(20) * location:Type = varchar(20)
price:Type= Decimal(10,0)
username:Type =varchar(30)
prd_cat:Type =varchar(30)
prd_sub_cat:Type =varchar(30) pwd:Type=string
prd_descrip:Type=varchar() balance:Type=int()
prd_qty_avila:Type=int(10)
prd_delivery_mode:type=varchar
(30)
prd_delivery_time:Type=int(10)
Figure 13: Class diagram

CHAPTER FOUR
4.System design
Systems design is the process of defining the architecture, components, modules,
interfaces, and data for a system to satisfy specified requirements. Design of software
involves conceiving, planning out and specifying the externally observable characteristics
of the software product. We have data design, architectural design and user interface
design in the design process. These are explained in the following section. The goal of
design process is to provide a blue print for implementation, testing and maintenance
activities.
System design is one of the activities that are required to build and verify software. The
designer’s goal is to produce a model or representation of an entity that will later be built.
Design provides us with representations of software that can assess for quality. Design is
the only way that we can accurately translate customer’s view into finished software
product or system.
4.1 Design Goal

Design goals describe the qualities of the system that developers should optimize. The
design goals are derived from the nonfunctional requirements. Design goals guide the
decisions to be made by us especially when trade-offs are needed.
4.2 System Decomposition and interrelation between them

The rationale behind subsystem decomposition spans many different issues, such as
hardware allocation, persistent storage, access control, global control flow, and boundary
conditions. The comprises three subsystems, which namely and functionally decomposed
as account management, item management, and order management, The Details of each
sub system and their corresponding services are presented as follow:

Figure 14: system Decomposition diagram

4.3 System Architecture

The term system architecture is used to describe the overall design and structure of a
computer network or system. It includes a wide range of physical devices, a method is
required to organize and connect these items together in a cohesive manner. The term is
also used to describe complex computer_ software tools. Systems Architecture is a
generic discipline to handle objects (existing or to be created) called "systems", in a way
that supports reasoning about the structural properties of these objects. A system
architecture is the conceptual model that defines the structure, behavior, and more views
of a system.
There are three main components to any system architecture of the system theses includes: storage,
connectivity, and user experience.

Figure 15: System Architecture

4.4 Deployment Diagram
Deployment diagram is a structure diagram which shows architecture of the system as deployment
(distribution) of software artifacts to deployment targets.
A deployment diagram is used to depict (show) the relationship among run-time

components and hardware nodes. A web server, for example, is a component that
provides services to Web browsers. It shows the physical architectures of the new system
and how hardware is connected. When it comes time to think about deploying the system,
deployment diagrams are crucial because they show the processors on the system and the
connections between them. A component is a physical unit of implementation with wel
ldefined interfaces that is intended to be used as a replaceable part of a system. The
deployment diagram for this system is shown in the following figure.

Figure 16: Deployment diagram

4.5 Persistence Data management
Persistent data management describes the persistent data stored by the system and the data
management infrastructure required for it. This section typically includes the description
of data schemes, the selection of a database, and the description of the encapsulation to
the database.
The system will use the MYSQL database to store persistent data. In addition to the various
benefits of using a modern relational database management system.
It is also used to describe the persistence data aspect of the system. The following diagram
indicates the persistence diagram of the system.

Figure 17 :persistence data management diagram
4.6 Access Control and Security

Access control and security is very important for our system. Good security requires
physical access control, reliable personal, trust worthily. Installation and configuration
procedure, secure communications and control of data base operation. Such as selecting,
viewing, updating or deleting data base records. All of our system is designed to meet
customer needs to protect your customer from unwelcome intruders. Restrict
unauthorized access to the places and during the time you specify all information and
resources are protecting from unauthorized people with respect to confidentiality and

integrity. This system is locked to prevent people from accessing your private document
and resources.
To describe the Access control and security we use the following tables. The rows
represent the actor of the system and the column represents the classes of the system and
operation that actors are allowed to performed.
Actor Object
Account item order Report
Customer -view() -view() -view()
Admin -view() update() View() -report()

view()
delete()
4.7 User interface design

This user interface design shows the sample of our project implementation part.

Figure 18: home page user interface

Figure 19:customer login page user interface

Figure 20: customer registration user interface

Figure 21:Admin login page user interface

Figure 22:Admin page user interface

Figure 23:product register page user interface

Figure 24:shopping cart user interface

Figure 25:customer transfer money user interface

Figure 26:Customer buy page

CHAPTER FIVE
5. Implementation and Testing
5.1. Objective of the Implementation

The objective of system implementation phase is to convert the final physical system
specification in to working and reliable software and hardware, document the word that
has been done, and provide help for current and future users.
5.2. Constraint of Implementation

Constraints are situations that limits on implementing the new system. To develop our project so
many things we face from these: -
 Lack of full and fast internet service

 Lack of hardware tools like laptop.
 Power fluctuation.
5.3. Sample code and description

Sample code for item list display for customer:-
<?phpsession_start();?>
<html>
<head>
<title>online shopping</title>
<meta http-equiv="Content-type" content="text/html; charset=utf-8" />
<link rel="shortcut icon" href="imz/su.jpg" />
<link rel="stylesheet" href="css1/style.css" type="text/css" media="all" />

<script src="js1/jquery-1.6.2.min.js" type="text/javascript" charset="utf-8"></script>
<script src="js1/jquery.jcarousel.min.js" type="text/javascript" charset="utf-8"></script> <script

src="js1/functions.js" type="text/javascript" charset="utf-8"></script>
</head>
<body>
<div id="wrapper">
<div id="search">
<div class="shell">
<form action="#" method="get" accept-charset="utf-8">
</form><div class="cl"> </div>
</div></div>
<div id="header" class="shell">
<h1 align="center"><imgsrc="images/12.png" align="center" height=100 width=950

/></h1>
</div>
<div id="navigation">
<div class="shell"><ul>
<li><a href="loghome.php" title="Home"><h3

style="color:#FFFFFF">Home</h3></a></li>
<li><a href="productdisplayin.php" title="product"><h3

style="color:#FFFFFF">Product</h3></a></li><li><a href="stock.php" title="view
item"><h3 style="color:#FFFFFF">view items</h3></a></li>
<li><a href="custaccount.php" title="create account"><h3

style="color:#FFFFFF">create account</h3></a></li>
<li><a href="main.php" title="change

password"><h3 style="color:#FFFFFF">Go to shop</h3></a></li>

</ul>
<div class="cl"> </div>
</div></div><div id="slider">
<div class="slider-outer">
<div class="slider-inner shell"><ul class="slider-items"><li><imgsrc="images/gi.jpg"

alt="Slide Image 1" /><div class="slide-entry"></div>
<a href="#" class="more" title="View More">View More</a></li><li>
<imgsrc="images/products/ac.png" alt="Slide Image 2" height=300 width=975 />
<div class="slide-entry">
</div><a href="#" class="more" title="View More">View More</a></li><li>
<imgsrc="images/gi.jpg" alt="Slide Image 3" />
<div class="slide-entry"></div>
<a href="#" class="more" title="View More">View More</a></li>
<li><imgsrc="images/products/q.png" alt="Slide Image 2" height=300 width=975 />
<a href="#" class="more"title="View More">View More</a></li><li>
<imgsrc="images/tr.png" alt="Slide Image 2" height=300 width=975 />
<a href="#" class="more" title="View More">View More</a></li></ul>
<div class="cl"> </div>
<div class="slider-controls">
</div></div></div>
<div class="cl"> </div></div>
<div id="main">

<div class="inner">
<div class="shell">
<?php
include("connected.php");
if(isset($_SESSION['user']))
$username=$_SESSION['user'];
echo "User name :".$username;
} else {
?> <script> alert('You Are Not Logged In !! Please Login to
access this page'); window.location='login.php';
</script>
<?php
?>
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<script type="text/javascript" src="js/functions.js"></script>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Online Shopping</title>
<link href="css/online.css" rel="stylesheet" type="text/css" />
<style type="text/css" media="all">

@import "online.css";
</style>
<script language="javascript">
function logoutcon()
varconlog = confirm('Are you sure you want to log out !!');
if(conlog)
alert(window.location="logout.php");
} else
{ return
false;
</script>
</head>
<body background="images/bg.jpg">
<div class="twoColFixLtHdr">
<div id="header">
</div>
<div id="container">
<div id="container1"></div>

<div id="sidebar1">
<div id="subsidebar1">
<div id="subsidebar3"> Navigation </div> <div id="subsidebar4">Display
<ul><a href="productdisplayin.php" title="list of product">Product </a></ul></div
<div id="subsidebar2"><a href="Main.php" title="you can go to the shopp">Go to

Shop</a></div>
<div id="subsidebar2"><a href="delivered.php" title="deliver report">Delivery

Reports</a></div>
<div id="subsidebar2"><a href="mailcompose.php" title="send

message">Compose</a></div>
<div id="subsidebar2"><a href="mesageview.php" title="view message">message

view</a></div>
<div id="subsidebar4">Account Settings
<ul><a href="changepassword.php" title="change password">Change Password</a></ul></div><div

id="subsidebar2"><a href="" title="logout" onClick="logoutcon();">Logout</a>
</div></div></div>
<div id="mainContent">
<div id="mainContent1">
<div id="middletxtheadermain">
<blink><div id="middletxtheader" align="right"><h1 align="center"

style="color:#FFFFFF">WELL COME TO THE SYSTEM</h1></div></blink>
<div id="middletxt1">
<div align="center"><imgsrc="images/r.png" alt="Online Shopping" width="650"

height="100"/></div></div></div>
<div id="middletxt">
<div id="middletxtheader" align="right"></div>

<div align="center"><imgsrc="images/tr.png" alt="Shopping " width="680"

height="420" align="center" /></div></div></div></div>
<div id="footer1">
<marquee behavior="alternate" scrollamount="10"><h2>online butics shopping

system</h2></marquee>
</div></div></div>
</body>
</html>
</div></div></div>
<div id="footer">
<div class="shell">
<p class="bottom-menu"><a href="loghome.php" title="Home">Home</a><span>|</span><a

href="productdisplayin.php" title="product">product</a><span>|</span><a href=""
title="Log In" onClick="logoutcon();">Log out</a><span>|</span><a href="signup.php"
title="Account"></a><span></p>
<div class="cl"> </div></div></div></div>
</body>
</html>
5.4. Testing Overview

Testing is a process of executing a program with the intent of finding an error. A good test
case is one that has a probability of finding an as yet undiscovered error. A successful test
is one that uncovers an as yet undiscovered error. Our Objective is to design test
processes that systematically uncover different classes of errors and do so with minimum
amount of time and effort.
5.4.1 Test by scope

Software testing is a process of running with intent of finding errors in software.it assures
the quality of software and represents final review of other phases of software like
specification, design, code generation etc.
5.4.2 Unit testing
The module interface is tested to ensure that information properly flows into and out of
the program unit under test. The unit testing is normally considered as an adjunct step to
coding step. Because modules are not a standalone program, drivers and/or stubs software
must be developed for each unit. A driver is nothing more than a “main program” that
accepts test cases data and passes it to the module. A stub serves to replace the modules
that are subordinate to the modules to be tested. A stub may do minimal data
manipulation, prints verification of entry and returns. For example:-
Test Case 1: Login
Test case objective : To login to the system
Test case description: Admin enters Username and Password, then presses login button.
Client program contacts with server, server contacts with the database, and database checks for
authentication and displays administrator page.
Requirements Verified: Yes
Test Environment: WAmpmysql server must be in running state, Database Should contain
appropriate table and link must be established between server and client program.
Pre-Conditions: AWmapserver should be in running state and Username and Password fields
should be filled correctly.
Actions Expected Results
The administrator should enter the correct user name and Displays administrator page.
password to login.
The user name and password are not correctly. Administrator username and
password do not mach.

Table 12: Test case to Admin Login

5.4.3. Integration testing
If they all work individually, they should work when we put them together. The problem of
course is putting them together. This can be done in two ways:
Top down integration: Modules are integrated by moving downwards through the
control hierarchy, beginning with main control module are incorporated into the structure
in either a depth first or breadth first manner.
Bottom up integration: It begins with construction and testing with atomic modules i.e.
modules at the lowest level of the program structure. Because modules are integrated
from the bottom up, processing required for the modules subordinate to a given level is
always available and the need of stubs is eliminated.
5.4.4. Testing by requirements

Testing by requirements insures that the entire integrated software system meets
requirements. It tests a configuration to insure known and predictable results. It is based
on process description and flows, emphasizing pre-driven process links and integration
points. In essence testing by requirements is not about checking the individual parts of
design, but about checking the system as a whole.
Test the system by using requirements of software and hardware components such as
computer with operating system containing: - WAMP server: a server used to run the
codes.
PHPMY Admin: front-end, to develop the PHP programming of the system translation.
MYSQL: to hold data base and to store data.

These are used for testing all the functional requirements are function able and access able
inthe environment of WAMP server.
Web browser: for internet connection.

5.4.5. Test implementation (Validation testing)
Validation succeeds when software functions in a manner that can be reasonably expected by the
customer. It covers the following: -
Validation test criteria: Performance, functional characteristics and uncovered deviation

from specification
Configuration review: Ensures that all the elements of software configuration have been
properly developed cataloged and have support for the maintenance phase of software life
cycle

CHAPTER SIX
6. Conclusion and Recommendation
6.1 Conclusion
In this project, the user is provided with an e-commerce system that can be used to buy
butics product item online .The Internet has become a major resource in modern business,
thus butics shopping has gained significance not only from the entrepreneur’s but also
from the customer’s point of view. For the entrepreneur, butics shopping generates new
business opportunities and for the customer, it makes comparative shopping possible.
The project began by laying out the foundation that determines the development process.
This involved defining the system development methodology, identifying resource
requirements, and setting the project schedule.
Requirements analysis is performed to discover the needs of the new solution to proposed
system. This phase consists of drawing out functional and non-function requirements of
the system.
In analysis, the proposed system is modeled using UML diagrams: use case diagrams, sequence
diagrams, Class diagrams.
We have designed the project to provide the user with easy navigation, retrieval of data
and necessary feedback as much as possible. To implement this system was used PHP and
MySQL also JavaScript were the major software and database used for developing the
entire system.
A good shopping cart design must be accompanied with user- friendly shopping cart
system. It should be convenient for the customer to view the contents of their cart and to
be able to remove or add items to their cart.

Generally, the system would take as a means for butics shop to deliver efficient and
effective report generating, recording categories, products, displaying product information
and information sharing.
The system that we developed is the one that is relatively minor in its type, but it can be a breakthrough
for other system developers to further implementation on the system.
6.2 Recommendation
This system will give a solution for some of the problems in EDERES Butics shopping
system.
 This project will promote e-commerce and online marketing on the Internet, complying with
the information technology more develop.
 Firstly, we recommend EDERES Butics shop to apply and use this system.
 Training for users: -We need to give training for those users of the system.
(Administrator).
 The system is developed for the first time, and it may have some limitation, so we are
willing to welcome every interested person’s idea and we need support of the program to
make the best.
 Server: - The server should be available at all time

 We recommend that who are voluntary to include other features of the system to be fulfilled.
 The system that developed is the one that is relatively minor in its type, but it can be a
breakthrough for other system developers to further implementation on the system.

Reference
[1] Dangar, K. 14 May 2012. Understanding ASP.NET MVC (Model View Controller)
Architecture for Beginners.URL:
[2] Joey F et al (2001) OOSAD course Object-Oriented Systems Analysis and Design.
[3] Diwakar, H., Marathe, M. (2000). The architecture of a one-stop web-window shop.
December, ACM SIGecom Exchanges, Volume 2 Issue 1.
[4] G. Booch, Object-Oriented Analysis and Design with Applications, 2nd ed.,
Benjamin/Cummings, Redwood City, CA, 1994.meth
[5] M. Fowler, UML Distilled: A Brief Guide To The Standard Object Modeling
[6] T. De Marco, Structured Analysis and System Specification, Yourdon, New York,
1978.me
[7] Dennis A., Wixom B. H. and Roth R. M. 2006. Systems Analysis and Design, Third
Edition. ISBN: 978-0-471-72257-1. Wiley.
[8] Prentice object oriented software engineering

Online Butics Shopping System

Uploaded by

Copyright:

Available Formats

Online Butics Shopping System

Uploaded by

Document Information

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

Online Butics Shopping System

Uploaded by

Copyright:

Available Formats

SAMARA UNIVERSITY

COLLEGE OF ENGINEERING AND TECHNOLOGY

DEPARTEMENT OF COMPUTER SCIENCE

ONLINE BUTICS SHOPPING SYSTEM FOR DUBTI EDERES IN

IN PARTIAL FULFILLMENT FOR THE REQUIRMENTS FOR THE

ADVISOR NAME: YEHENEW .ADDIS June 2018, SAMARA

COLLEGE OF ENGINEERING AND TECHNOLOGY

DEPARTMENT OF COMPUTER SCIENCE

EXAMINERS’ APPROVAL SHEET

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

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

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

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

Project Approved by:

Head, Computer Science Signature Date

S.No Name ID Signature Date

1. GIZACHEW MINALE CET0040/07 _______ _________

2. YOSEPH WAKGARI CET0096/07 ________ ___________

3. BINIYAM ADMASS CET0055/07 _________ __________

4. HEVEN BELEW CET0046/07 __________ __________

5. MUZAMILE MUSA CET0064/07 _________ __________

6. GASHAW YISMAW CET0038/07 _________ __________

7. NABIYOU ABARA CET0065/07 ________ __________

Advisor’s Name: Mr.YHENEW ADDIS(MSc)

SU CS 4th YEAR FINAL PROJECT I

SU CS 4th YEAR FINAL PROJECT II

CHAPTER ONE ............................................................................................................................

SU CS 4th YEAR FINAL PROJECT Page III

1.6.2 Limitation ..........................................................................................................

CHAPTER TWO ......................................................................................................................... 8

SU CS 4th YEAR FINAL PROJECT IV

2.2 Weakness and strength of the existing system........................................................ 9

CHAPTER THREEE ............................................................................................................... 13

SU CS 4th YEAR FINAL PROJECT Page V

4.1 Design Goal ............................................................................................................ 44

CHAPTER FIVE ..................................................................................................................... 59

SU CS 4th YEAR FINAL PROJECT Page VI

SU CS 4th YEAR FINAL PROJECT Page VII

Table 8: Use-case description for Update Item.................................................................

SU CS 4th YEAR FINAL PROJECT Page VIII

Figure 9: update item sequence diagram.......................................................................... 38

SU CS 4th YEAR FINAL PROJECT Page IX

Figure 26:Customer buy page ...........................................................................................

SU CS 4th YEAR FINAL PROJECT Page X

CSS Cascading Style Sheet

HTML Hypertext Markup Language

MYSQLMY Structured query language

OBSS Online Butics Shopping System

PHP Hypertext pre processor

RAM Random Access Memory

UML Unified Modeling Language

SU CS 4th YEAR FINAL PROJECT XI

1. System requirement specification

1.2. Background of the organization

1.3. Background of the study

SU CS 4th YEAR FINAL PROJECT Page XII

1.2 Literature Review

1.3. Statement of the problem

 There is information gap between the customer and administrator.

SU CS 4th YEAR FINAL PROJECT Page XIII

1. GIZACHEW MINALE CET0040/07 _ ___

2. YOSEPH WAKGARI CET0096/07 ___

3. BINIYAM ADMASS CET0055/07 _ __

4. HEVEN BELEW CET0046/07

5. MUZAMILE MUSA CET0064/07 _ __

6. GASHAW YISMAW CET0038/07 _ __

7. NABIYOU ABARA CET0065/07 __