Online Shoppingcorrect

Department of computer science
GROUP
MEMBERS
NAME ID
Getachew girum------------------------02725 /11
Abebe simegn------------------------02725/11
Ayelegn dereje------------------/
Getnet ayana-------------------------02706/11
Bereket angagrie---------------------02714/11
G/Michael bimrew----------------------02657/11
DEPARTEMENT OF COMPUTER SCIENCE Page ii

Contents
Acknowledgement-----------------------------------------------------------------------vi
Abstract---------------------------------------------------------------------------------------vii
Chapter 1 Introduction-----------------------------------------------------------------1
1.1. Background of the project----------------------------------------------------1

1.1.1. Mission--------------------------------------------------------------------------------2
1.1.2. Vision-------------------------------------------------------------------------------------2
1.2. Statement of The problem----------------------------------------------------2
1.3. Objective of the Project------------------------------------------------------3
1.3.1. General Objective-------------------------------------------------------------------------3
1.3.2. Specific Objective--------------------------------------------------------------------3
1.4. Scope of The project-----------------------------------------------------------3
1.5. Limitation of the Project-----------------------------------------------------4
1.6. Constraints----------------------------------------------------------------------4
1.7. Alternative Solution---------------------------------------------------------------4
1.8. Significance and beneficiaries of The Project----------------------------------5
1.8.1. Significance of the Project--------------------------------------------------------5
1.8.2. Beneficiaries of the Project------------------------------------------------------------5
1.9. Feasibility of the Project----------------------------------------------------------6
1.9.1. Technical Feasibility----------------------------------------------------------------------6
1.9.2. Schedule Feasibility----------------------------------------------------------------------6
1.9.3. Operational Feasibility---------------------------------------------------------------6
1.9.4. Economic Feasibility----------------------------------------------------------------6
1.9.5. Behavioral/political Feasibility----------------------------------------------------7
1.10. Methodology of The project--------------------------------------------------------7
1.10.1. Data collection-----------------------------------------------------------------------8
1.10.2. Development operation-----------------------------------------------------------8
1.10.3. Development Tool----------------------------------------------------------------------9
1.11. Team Composition and Management-----------------------------------------------10
1.12. Schedule of the Project----------------------------------------------11
1.13. Overall Cost Analysis-------------------------------------------------12
DEPARTEMENT OF COMPUTER SCIENCE Page iii

Chapter 2 Analysis-----------------------------------------------------------------------13
2.1. Study of the Current System-------------------------------------------------14

2.2. Overview of the New System-------------------------------------------------14
2.3. Requirement Analysis----------------------------------------------------------14
2.3.1. Functional Requirement-----------------------------------------------------------14
2.3.2. Non Functional Requirement-------------------------------------------------15
2.4. DFD Diagram---------------------------------------------------------------------16
2.5. Use Case Diagram---------------------------------------------------------------25
2.6. Actor specification -------------------------------------------------------------25
2.7. Use Case Identification---------------------------------------------------------25
2.8. Sequence Diagram--------------------------------------------------------------42
2.9. Activity Diagram-----------------------------------------------------------------53
Chapter 3 Design--------------------------------------------------------------------------59
3.1. Introduction---------------------------------------------------------------------59
3.2. Class Modeling and normalization-------------------------------------------59
3.3. Component Modeling and E-R Relationships--------------------------------66
3.4. Deployment modeling---------------------------------------------------------67
Chapter 4 Conclusion and Recommendation-----------------------------70
5.1. Conclusion---------------------------------------------------------------------70
5.2. Recommendation-------------------------------------------------------------71
5.3. Reference----------------------------------------------------------------------72
List of Tables
Table: 1.1 Team Compositions--------------------------------------------10
Table 1.2 Schedule feasibility -------------------------------------------11
Table 1.3 Cost Estimation ------------------------------------------------12
Table 1. Use case Create Account-------- ------------------------------31
Table 2. Login------------ -------------------------------------------------32
Table 3. Change Password------------------------------------------------33
Table 4. Search Item------------------------------------------------------34
Table 5. View Item--------------------------------------------------------35
Table 6. Order Item------------ ------------------------------------------36

DEPARTEMENT OF COMPUTER SCIENCE Page iv
Table 7. View Report- ----------------------------------------------------37
Table 8. Update Item-----------------------------------------------------38
Table 9. Item Registration-----------------------------------------------39
Table 10. Generate report-----------------------------------------------40
Table 11. Logout----------------------------------------------------------41
List of Figures
Figure 1: DFD Diagram-------------------------------------------------------17
Figure 2: Use case Diagram------------------------------------------------27
Figure 3: Login Sequence---------------------------------------------------42
Figure 4: Create-------------------------------------------------------------43
Figure 5: Change Password-----------------------------------------------44
Figure 6: Search item-----------------------------------------------------45
Figure 7: View item-------------------------------------------------------46
Figure 8: Order Item-------------------------------------------------------47
Figure 9: view Order-------------------------------------------------------48
Figure 10: Update item----------------------------------------------------49
Figure 11: Register----------------------------------------------------------52
DEPARTEMENT OF COMPUTER SCIENCE Page v

Figure 12: view report-----------------------------------------------------53
Figure 13: logout------------------------------------------------------------54
Figure 14: Login Activity Diagram--------------------------------------53
Figure 15: Search item----------------------------------------------------54
Figure 16: create Account ------------------------------------------------55
Figure 17: View Item -----------------------------------------------------56
Figure 18: Change Password --------------------------------------------57
Figure 19:Logout--------------------------------------------------------------58
DEPARTEMENT OF COMPUTER SCIENCE Page vi

Department of computer science
ACKNOWLEDGMENTS
We would like to express our deep gratitude and special thanks to instructor
Mr.misganew our lecture, for his patient guidance, enthusiastic encouragement and
useful critiques in time of learning, in his lecture time. 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 Tilahun electronics 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
informatics of computer science department, who gave us by preparing laboratory
class and internet to done our project. We would also like to extend our thanks to the
technicians of the laboratory of the computing department for their help in offering us
the resources in running the program. Finally, we wish to thank our friends, past
students and families for their support and encouragement throughout our study/work/.
DEPARTEMENT OF COMPUTER SCIENCE vii

ABSTRACT
Most of shopping system can be done manually including small shops to higher shops
like supermarket. The products that can be sold are stored and documented using papers
and also labors that’s why it is making the process too late. And the customer does not
satisfy their needs this makes the merchant having loss.
This project documentation includes about the development steps of the new system
that makes the sellers profitable, easy manage their organization and fulfill their
customers need. From the beginning phase that concern on the introduction,
background, constraints, objectives, methodology and analysis specifically on
requirements of the new system to the middle phases that concern on the design,
including DFD diagram, use case diagram, class modeling, E -R diagram and
relationships, activity diagram and sequence diagram to the last phases that concern on
the implementation testing and some sample of code viewing included in this
documentation.
DEPARTEMENT OF COMPUTER SCIENCE viii

CHAPTER ONE
1. INTRODUCTION
Technology is spreading its wing in almost every walks of human life activities.
Now a day it is better if every activity is done using new technology in order to
fulfill the need of human being, Organization and Enterprise etc. As today’s world
there are many organizations and each organizations needs to be preferable,
computable and work on fastest way in order to satisfy users interest etc... (I.e.
they should have facilitated their activities in computerized way).
Hence online shopping system is a management system that is designed to improve

accuracy and to enhance the performance of the task in the shopping. It is a
computer based system which helps to the employee inside the shop to facilitate
the activity of the shopping in a manner way.
At present manual system is being utilized in the shopping. It requires the

merchant to manually monitor available in the shop. This usually leads to mistakes
as the workload of the merchant increases.
1.1.Background of the project

The tilahun electronics shop in Gondar town was started its work in 2000 E.C in
the form of small shopping within a few amounts of items. Then After a few years,
the shop becomes a large by adding many electronics materials such as television,
mobile, laptop, flash, CD, DVD, fridge etc.
SUBMMITED TO: MR. ZEWUDU TIGABU SUBMMITED DATE: 09/06/2011

Now it gives an honorable service for the society. Supply and demand of GECH
electronics shop is based on market needs. The Employee uses the manual system
in order to manage the overall activity of the shop.
Today with the growth of population number, our world is facing serious
problems. Many organizations are in trouble to accommodate these large numbers
of people according to their needs. Many problems in the organizations are
associated with the increasing number of customers and way of helping them.
Currently, all activities of shop system are going on manually, which lead to
wastage of time, labor, accuracy, and speed. Shopping System is the backbone of
the growth of country. So it should be advanced and computerized to provide fast
services for the community and also for other users of the system.
1.1.1 Mission: the missions of the company are as follows

 Providing well standard online shopping for electronics shop.
 Satisfy the need of the customer by providing online shopping.
1.1.2 Vision: the visions of the company are as follows

 See a community those are adapting online shopping.
 Facilitating the company business.
 Give facilitated service for the customers.
1.2 STATEMENT OF THE PROBLEM

 Managing a very large shop with records on papers will be tedious and
difficult to keep track of inventory with regards to the electronics in the stock
inside the shop.
 Since it is manual system quantity of electronics available based on the
categories and their functions can’t be easily known. Due to this the patient
can’t get the electronics they want.
DEPARTEMENT OF COMPUTER SCIENCE Page 2

 Difficulty of getting full information about electronics when needed
immediately.
 Preparing report for each electronics takes long time.
 It is difficult to identify which electronics are out dated or expired.
 The most sensitive data is lost because of they are paper based.
 Most of the time redundant data occur.
1.3 OBJECTIVES OF THEPROJECT

1.3.1 General objective
 the general objective of the project is to change the existing manual
based system in the computerized system for GECH PLC Company.
1.3.2 Specific objective
 To advertise information about various products in different category.
 To establish a database for electronics shop and store products
 To enable the customer can purchase product’s online
 To makes fast searching and give information service about goods.
 To search system that used to check the customers product need.
1.4 SCOPE OF THE PROJECT

our project will 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 tilahun company in Gondar town.
Generally some parts of our project will address:-
 View register customer, view item, order item, Update item, register item,
View order and generate report.
 Searching products using dropdown menu.
 Sending and receiving messages between Administrator and Customer.

 The system announces the total price of the purchase product.
 Update product items from database by administrator

 The system generate delivered report
1.5 LIMITATION OF THE PROJECT

 It does not search the item by color.
 The system not consider for backward item from customer.
 The system is also does not consider ATM.
 The system does not support GPS.
 The system transact only in CBE.
1.6 CONSTRAINTS
Because the current manual based shopping system performs different activities, due
to the time and budget made available to this project, Failure of network connection,
seller are not free to give the required information, due to the current situation of the
town to Gondar there was also a great problems using the specified time.
1.7 ALTRNATIVE SOLUTION

In order to overcome tilahun electronics shopping problems, our team members finds
different solutions. These are:
Web based applications: is heavily depending on internet connection, which means

if there is no internet connection the software users are not able to use this software
(product). The major advantage of web based application is that the users can have an
access to the system where ever they are if there is an active internet connection from
the client end to the server end. It uses HTTP as its primary communication protocol.
Desktop application: This application is accessible only from the stand alone
desktop or laptop computer where the application is installed. It needs a direct
contact of users with the computer in which the software is installed.

1.8SIGNIFICANCE AND BENEFICIARIES OF THE PROJECT
1.8.1 Significance of the project
 Good time management for both the customer and seller
 Faster and quicker
 Good documentation and registration
 Not costly
 Computerized handling of data
 Effective and efficient
 Customer satisfaction
1.8.2 Beneficiaries of the project

Both the company and the community are the beneficiaries of this project.
 for employees/electronics shop owners/:-  Save their
time.
 Reduce workers load
 Decrease errors in information access of the manual system.
 Improve quality service for their customers.
 for customers:-
 Saving their time.
 Reduce complexity.
 Control and reduce data redundancy.
 Increase access of information as well as products
 Enables to compare the quality and cost of the products.
1.9FEASIBILITYOF THE PROJECT
1.9.1 Technical feasibility
Usually new systems established in order to overcome the technical
illness of the previous system. In the same way, this system is

technically big enough to be applied easily to the problem identified in
the existing system. In addition; the both hard ware’s and soft ware’s for
this system are highly available and can be owned with small cost.
Therefore, it can be concluded that the system is technically feasible.
1.9.2 Schedule feasibility

Time evaluation is the most important consideration in development of
the project. So the concerned project should be completed within fixed
scheduled time as far as system is concerned. As we know new system
needs much time to develop, as much as possible we tried to develop
within few days.
In addition we are scarifying us to prepare the system very carefully with
IT professionals in the winter program as computer science taker.
1.9.3 Operational feasibility

The project is operational feasibility because; the new system can be
easily operated and accessed by the users who interact to the system. It
contains user friendly commands which leads users interact to the
system interfaces. The system has can be easily operated by some
technical it professional persons like with it secretary or TVT IT
students.
1.9.4 Economic feasibility

Our project is economically feasible. Because it does not require much
more money and also the materials to implement the system. Plus to that
whenever the web based system is applied in tilahun electronics the
following costs will be gained. Such as manual system will be
computerized and the human resource power will be decrease these can
be calculated as 50 payday and 1500 per month and 6000 birr per year
will be minimized approximately. Other cost related advantage is that

it’s faster as compare to the traditional system and this will compensate
up to 20 birr per a day and 600 birr per month.
1.9.5 Behavioral/Political feasibility

Since the proposed system is user friend, solve difficulties (problems)
with society regarding to traditional shopping system and accepted
almost by all the customers behaviorally it is feasible.
1.10METHEDOLOGY OF THE PROJECT

The team chooses object oriented analysis and design approach to analyze and design
the system, based on our preliminary analysis of the old system.
In our project the team will use some concepts of Object Oriented Software
Development Methodology (OOSD) because it has the following advantages:-
 Increase reusability: - the object oriented provides opportunities for
reuse through the concepts of inheritance, polymorphism,
encapsulation and modularity.
 Increased extensibility: - when there is a need to add new feature to
the system you only need to make changes.
 Improved quality: - quality of our system must be on time and meet
our exceeded the expectation of the users of our system, improved
quality comes from increased participation of users in the system
development.
1.10.1 Data collection

The team will use the following requirement determination methodology for
the development of our project:
 Interview: -The team will use open interview method to get the basic
information and background information about the existing system

structure we ask different question for employees of the tilahun PLC
(Specially the manager of tilahun Company).
 Interview questions
 When was the tilahun established?

 What type of technique is the current system use?
 What is the basic problem of the current shopping system?
 Where did you store items information?
 What kind of features would you expect from the new system?
 Observations:-We observed physically the current existing system
which is done manually and observe how they perform each activity.
 Questionnaires:-Since the shopper as well as higher officials of the

shop have work load they cannot able to answer/give information what
we ask. So we prepare some sample questions to get précised
information.
1.10.2 Development Approach

For designing purpose we use object oriented because a developer applies
implementation constraints to the conceptual model produced in object
oriented analysis. When requirements are completed, one proceeds to
design. The software in question is designed and a blueprint is drawn for
implementers (coders) to follow this design should be a plan for
implementing the requirements given. When the design is complete, an
implementation of that design is made by coders. Towards the later stages of
this implementation phase, separate software components produced are
combined to introduce new functionality and reduced risk through the
removal of errors.

The application domain represents all aspects of the user’s problem. This
includes 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.
1.10.3 Development tools

A. Software Tools
 Documentation
 MS-word:-used for documentation of each phase.
 MS paint to draw/edit photo
 Adobe photo shop cs3 to edit photo
 WAMP Server 2012
 Rational Rose, Visual Paradigm, E draw:-For designing
UML diagrams associated with the project.
 PHP programming language: - for the software developing.
 Edit plus and sublime text: for writing code  Operating
system
 Window 7
 Interface language
 English Language
B. Hardware Components
 Laptop/desktop
 Paper and pen

 USB Flash(8GB)
 RAM:2GB
 CPU:2Ghz
 Hard disk:400 GB
 Monitor: LCD
1.11TEAM COMPOSITION AND MANAGEMENT

Table 1.1: Team composition and management
NAME ID ROLE IN TEAM
Getachew Girum 02725/11 PROGRAMMER
Abebe Simegn 02638/11 SYSTEM ANALYST
Getnet Ayana 02706/11 MANAGER
Bereket Anegagrie 02714/11 DESIGNER
G/Michael Bimrew 02657/11 Data collector
1.12 SCHEDULE OF THE PROJECT (using Gantt chart)

This involves questions such as how much time is available to build the new system,
when it can be built.

Table 1.2: Schedule feasibility table using column chart
6
jan20-2014
5
jan25-2014
4
3 jan30-2014
feb10-2014
2
feb20-2014
1
1.13 COST ANALYSIS

To complete our project starting down from the beginning up to the end of this project
we planned the following cost list.
Table 1.3: shows the cost of the proposed system

No Item quantity Price per item Total price
1 Paper 60 50 30
2 CD 2 10 20
3 Pen 1 15 15

4 Mobile card 2 25 50
5 Miscellaneous - - 550
cost
6 Transport 120 120

Total 6 - - 785
CHAPTERTWO
2. Analysis
In day to day life, we will need to buy lots of goods or products from a shop. It is
only items. Now days, it is really hard to get some time to go out and get them by
ourselves due to busy life style or lots of works. In order to solve this, ECommerce
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.

The existing system of buying goods has several disadvantages. 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. More over the shop from where we would like to
buy something may not be open 24*7*365. Hence we have to adjust our time with
the shopkeeper’s time or vendor’s time.
In order to overcome these, we have E-commerce solution, i.e. one place where we
can get all required goods/products online. The proposed system helps in building
a website to sell products or goods for the customer using their bank account. User
can choose different products based on categories, delivery services and hence
covering the disadvantages of the existing system and making the buying easier
and helping the vendors to reach wider market.
2.1STUDY OF THE CURRENT SYSTEM

In Tilahun shopping the system is performed manually. Since the process of selling
and buying is done manually it is tedious, require more manpower, unreliable, lack
of detailed report, and consume more time.
2.2 OVERVIEW OF THE NEW SYSTEM

The new system after the development of this project the shop gain many
advantages by reducing manpower, increasing reliability, avoid wastage of time,
and displaying more detailed information about the shopping process.
2.3 REQUIREMENT ANALYSIS
2.3.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 proposed system must:
 Enable to allow customer and administrator to login to the system. 

Enable to allow customer to create account.
 Enable to allow customer and administrator to change their password
 Enable to allow customer to view items with full information(type,
image, price)
 Enable to allow customer to order the item.  Enable to allow
manager to register item.
 Enable to allow manager to generate report
 Enable to allow customer and manager to logout from the system
2.3.2Nonfunctional requirement
A. user interface and human
requirements
Customer’s background of technology and their acquaintance to recent
information technology facilities different such as:-
 The system provides to customers with easy to interface.

 Interaction of customers with the system through graphical user
interface.
 The forms should be user friendly. Which means it should not be
complicated and does not need any extensive training.
 The interface should be attractive and give easy feeling.

B. performance
Our performance focus online shopping system ,it has growing volume of
products and accessed by a number of customers currently.
Input error is handled by the client computer through different validation
techniques of programming language before sent to the server machine. As
a result the performance of the system will be improved.
C. security
Accessed to different part of the system should required authorization.
D. error handling
our project system should handled invalid inputs and display user information
error messages.
E. Storage requirement
The system should store all the data related with all the tasks performed into the
database.
2.4 DFD DIAGRAM

Data Flow Diagrams show the flow of data from external entities into the
system, and from one process to another within the system. There are four
symbols for drawing DFD:
1. Rectangles representing external entities, which are sources or destinations
of data.
2. Ellipses representing processes, which take data as input, validate and
process it and output it.
3. Arrows representing the data flows, which can either, be electronic data or
physical items.

4. Open-ended rectangles or a Disk symbol representing data stores,
including electronic stores such as databases or XML files and physical
stores such as filing cabinets or stacks of paper.
Figures 3 - 14 are the Data Flow Diagrams for the current system. Each
process with in the system is first shown as a Context Level DFD and later as a
Detailed DFD. The Context Level DFD provides a conceptual view of the
process and its surrounding input, output and data stores. The Detailed DFD
provides a more detailed and comprehensive view of the interaction among the
sub -processes within the system.

Fig 1: DFD Diagram
DFD Diagrams:
Context Level (0th Level) Diagram:

Login DFD
A
dmin Details Data Flow:

1st Level DFD Diagram:
2nd Level DFD for Manage Product

2.5USE CASE DIAGRAM
Use Case represents interaction between a user (human or machine) and the system.
Use case components:

 Actor: is a person, or external entity that plays a role in one or more interaction with the
system.
 Use case: describes a sequence of actions that provides something of measurable value
to an actor and is drawn as a horizontal ellipse.
 System boundary: indicates the scope of the system project. Anything within the box
represent functionalities in side with in scope.

2.5.1Actor 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 and act as admin.
2.5.2: Use case identification

Each Use Case describes the functionality to be built in the proposed
system, which can include another Use Case's functionality or extend
another Use Case with its own behavior. The most important and basic use
cases of this system are the following:-
 Login
 Search items
 Create account
 Delete account
 Change password
 View items
 Change password
 Create account
 Order items
 Transfer money
 View customer
 Register items
 Update items
 Generate report
Fig 2: use case diagram

Shopping Cart Web Portal
<<extend>>
Category Management
<<extend>>
Product Management
<<extend>>
Content Management
Customer
<<extend>> Admin
Order Management
<<extend>>
Customer Management
Purchase Module
Category Management
View Category
Add Category
Customer Update Category Admin

Customer Management
View Customer Details
List Customer
Customer Add Customer Admin
Update Customer
Delete Customer
Content Management
View Content Page
Update Content Page
Customer Admin

Catalog Management
Manage Country
<<extend>> <<extend>>
<<extend>>
ViewCountry AddCountry UpdateCountry
Manage State
<<extend>>
<<extend>> <<extend>>
ViewState AddState UpdateState
Manage City
Customer Admin
<<extend>> <<extend>> <<extend>>
ViewCity AddCity UpdateCity

2.5.3Use case documentation
Table1: Use case description for create account
Use case number Uc-01
Use case name Create account
Actor Customer
Description These use case allows customer
create account to the system
Pre-condition Customer wants to create
account on our system
Basic course of action User action System response
1. The customer 1. The system creates
home register
account user interface
page to create
and form.
account 2.The system controller
and click on verifies a
create form and check the form
account link. is verified.(If it does not
2. The customer verify back to
step 3 or re-enter their
fill form
information)
on create account 3. The system send
form and create request to database to
account. save account and reply
account created is saved
to the
controller.

Table 2: Use-case description for Login
Use-case Number Uc-02
Use-case Name Login

Actor Manager ,Customer
Description This use case describes how manager and customer , to login to the
buying system
Pre-condition Actor must have Account
Post-condition 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 of User Action System Response
Action
1.The manager and customer 1. The system prompts the

are open home page to login to manager and customer to enter user
name and password.
the system
2. If they have an account the
2. The manager and customer system verifies that all the filled
submit username and password. have been filled out and the login
3. If they have no username and controller check username and
password create new account password are valid.
and apply 2&3. 3. The controller request to login
the database and it retrieve the
information and send to the
controller.
4. If the authentication false it back
to the login form and if True back
to main menu.
5. The system successfully logged
in the system.
6. Use case Exit
Alternate course 3.1 If all fields are not filled out and not matched to the username and password
of Action the system notifies the actor message username and password is incorrect and
nzjjdjs
Then go back or return to step 2 of basic course of action to enter again
Table 3: Use-case description for Change Password

Use-case UC-03
Number
Use-case Change Password
Name
Actor Customer and Manager
Description These use case allow customer and manager to change
password from the system.
Pre-condition Customer and Manager wants to change password.
Action 1. The user wants to 1. The system creates change
change password on password user interface and
main menu and click form.
change password link. 2. The system controller verifies
2. The user fills a form the form and check the form is
and change password on verified.(if not back to step 3 or
the form. Renter the required information)
3. The controller send request to
database to change password
and it send the changed
password to controller.
4. The system replay password
successfully changed on change
password user interface.
5. Use case Ends.
Table4: Use-case description for Search Item

Use-case Number UC-04

Use-case Name Search Item
Actor Customer
And manager
This use case permits Administrator and Customer to search item from
Description item list in order to display.
Pre-condition UC-2
Basic course of Action User Action System Response
1. The Administrator or 1. The search controller verify item

customers enter to home name and check item is verified.
page to search the item. 2. The system controller sends the
2. The Administrator or request item to database and it retrieve
Customer enters the item the information and back to controller.
name on search form. 3. 3. If the item is found it display on
Clicks on search button. the home page user interface, if not
display item is not matched message.
4. Then the system display all
information about the item based
selected list.
5. Use case End.
Alternate course of Action 5.1 If any lists are not selected from the search system goes back or
returns to step 2 of basic course of Action to search the item.
Table 5: Use-case description for View Item

Use-case Name
View Item
Actor Manager and Customer
Description This use case allows Administrator and Customer to view or display
all items with their detail description about the item.
Pre-condition Item select

Action
1. The 1. The system send request item to

Administrator or database.
Customer opens the 2. The system display item on home
system to enter home page user interface.
page.
3. Use case Exit.
Table 6: Use-case description for Order Item

Use case number UC-06
Use case name Order item
Actor Customer
Description This use case allows customer to the system.
Pre-condition UC-02
Basic Course of User action System response
action 1. The customer is in home page. 1. The system creates search form.
2. The customer writes and search 2. The system controller verifies the
item on search form. input and check input is verified.
3. If the item found the customer 3. The system retrieves the item and
select it on main menu. the retrieved search result and also the
4. The customer click add to cart result not found put on home page.
link and click the cart and display cart 4. The system create order button.
user interface. 5. The system creates confirmation
5. The customer click order button. and clicks and sends text to customer and
6. The customer writes the message saves to the DB.
and confirm on email form. 6. The system verify message on
database and send message ordered
is successful on cart user Interface.
7. Use case Ends.
Alternative course 6.1. if the item is not found the system state is unchanged
of action

Table 7: Use-case description for View Order
Use case number UC-07
Use case name View order
Actor Manager
Description These use case allow Manager to view order from the system
Pre-condition UC-02
Post-condition The Manager views the customer order
Basic Course of action User action System response
1. The manager initiates to view 1. The system create order link.

orders on main menu. 2. The system sends the requested
2. The manager clicks the order order to DB and display orders on order
link. UI.

Table 8: Use-case description for Update Item
Use-case UC-08
Number
Use case name Update item
Actor Manager
Description This use case permits staff to update or modify item information.
Pre-condition UC_01 and UC-02
Post-condition Update item information
Basic course of User action System response
action 1. The manager enter 1. The system creates update it
main menu to update item. user interface and form.
2. The manager writes the 2. The system controller
item and search on search verifies form and check form is
form. verified.
3. The manager enters 1. The system controller send
update item information request item to database and it
and click update. retrieve item and back to
controller and display item
information on update item user
interface.
2. The controller verifies the
form and send request to update
item database.
3. The employee Successfully
updates information into
database.
4. Use case Ends. he system
Alternate 6.1 If item is not found back to basic course of action 6 to

course of action update item.

Table 9: Use-case description for Item Registration
Use-case ID UC-9
Use-case name Item registration
Actor Manager
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 manager enters the main menu to 1. The item controller verifies a
register item. form and check if it is valid form.
2. The manager clicks the item register link 2. The controller register the item
and creates its user interface and form. in database and it send the registered
3. The manager fills information about the item to controller.
item and registers the item in item registration 3. If the item correctly registered it
form. display on the item register user
4. If the item registration form not found the interface.
employee create the form. 4. The system displays successful
item summary.
5. Use case Exit.
Alternative 2.1. If all fields are not filled out and matched to the registration form the system notifies the
course of actor message the item information is incorrect and then goes back or returns to step 2 of basic
Action course of action to register again

Table 10: Use-case description for Generate Report
Use-case Name Generate Report
Actor Manager
Description These use case allow Manager of the organization

to generate a report about the item information of a
month.
Pre-condition Manager wants to see report , UC-02
Post-condition Generate monthly report information.
Basic course of User action System Response
Action
1. The Manager 1. The system request to
wants to generate retrieve the report into
report and enter to database.
the main menu. 2. The system retrieved
2. The Manager and generates report on
clicks report pages. report UI.
3. Use case Ends.

Alternate course of 4.1 If the selection information is empty or not
Action found go to
Table 11: Use-case description for Logout
Use-case Name Logout
Actor Customer and manager
Description These use case allow customer and manager to logout from the system
at a time of accomplishing there work.
Pre-condition UC-02
Post-condition System logout
Basic course of action User action System response

1. The customer or 1. The system responds to the
manager wants to requested action.
logout and enter to main menu. 2. The system successfully
2. The customer or logout back to home page.
manager clicks the 3. Use case Ends.
logout button.

2.5.4Sequence 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.
Figure 3: Login Sequence Diagram

Figure 4: Create account Sequence Diagram
Page 41
DEPARTEMENT OF COMPUTER SCIENCE
Figure 5: Change password Sequence Diagram

Figure 6: Search Item Sequence Diagram
Page 43
Figure 7: View Item Sequence Diagram

Figure 8: Order Item Sequence Diagram

Figure 9: View Order Sequence Diagram

Figure 1: View Order Sequence Diagram
Figure 10: Update Item Sequence Diagram

admin
Figure 11: Register Item Sequence Diagram
Page 48
Figure 12: Generate report Sequence Diagram

Figure 13: Logout Sequence Diagram
Page 50
2.5.5Activity diagrams
Figure 14: Login activity Diagram

Figure 15: search items activity Diagram

Figure 16: create account activity Diagram

Figure 17: view items activity Diagram

Figure 18: change password activity Diagram

Figure 19: Logout activity Diagram

CHAPTER THREE
3. SYSTEM DESIGN
3.1 INTRODUCTION
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.
3.2 class modeling and normalization

“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.”[Prentice object oriented
software engineering] 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 the class can execute. They are also left-aligned
and the first letter is lowercase.
Normalization
Normalization is the process of organizing and designing a data model to efficiently store
data in a database. The end result is that redundant data is eliminated, and only data related to
the attribute is stored within the table.
Logical design the following steps of normalization: -
First normal form
 Requires that all column values in a table are atomic (e.g., a number is an atomic
value, while a list or a set is not).
We have two ways of achieving this:
1. Putting each repeating group into a separate table and connecting them with a
primary key-foreign key relationship
2. Moving this repeating groups to a new row by repeating the common
attributes. If so then Find the key with which you can find all data
A table (relation) is in 1NF If
 There are no duplicated rows in the table. Unique identifier  Each cell
is single-valued (i.e., there are no repeating groups).
 Entries in a column (attribute, field) are of the same kind.
Second normal form

 No partial dependency of a non-key attribute on part of the primary key. This will
result in a set of relations with a level of Second Normal Form.

Any table that is in 1NF and has a single-attribute (i.e., a non composite) key is automatically
also in 2NF.
A table (relation) is in 2NF If

1. It is in 1NF and
2. If all non-key attributes are dependent on the entire primary key. i.e. no
partial dependency.
Third normal form
 Eliminate Columns Dependent on another non-Primary Key - If attributes do not
contribute to a description of the key, remove them to a separate table. This level
avoids update and delete anomalies.
A table (Relation) is in 3NF If
3. It is in 2NF and
4. There are no transitive dependencies between a primary key and non-
primary key attributes.
1. Supermarket Table
Suid Suname Suemail sutel Su city Su region
02706/11 gech gech@gmal.com 0582620075 Gondar Amhara
• This table is satisfying 1NF. b/c each attribute is a single value.
• This table is satisfying 2NF b/c not partial dependency and has one primarykey.
• This table is satisfying 3NF b/c not transitive dependency
2.Employee table
ESSN E F name E Lname E Sex Eaddress ESalary E P h o n e
1234 melkamu mihretu M Gondar 8000 0978654345

89705 Menberu G/hiwot M Gondar 9000 0935754678
• This table is 1NF b/c each attribute is a single value.
• This table is2NF b/c not partial dependency and has one primary key.
• This table is in 3NF b/c no transitive dependency.

3.Customer table
Cussn Cufname Surname Cuaddress Cusex Cuphone Cuage
2233 kassahun Taddese Gondar M 0965432123 21
4354 mastewal Demeke Gondar F 0987563421 20
0986544323
This not in first normal form b/c attribute have multiple value.
New customer table

Cussn Cufname Culname Cuaddress Cusex Cuphone Cuage
2233 kassahun Taddese Gondar M 0965432123 21
• This table
is1NF b/c each
attribute is a
single value.
• This table is
2NF b/c not
partial
dependency
and has one
primary key.
• This table
is3NFb/c not
transitive
dependency.

Figure 20: Class modeling

Credit card 1:1 has 1:1 Customer 1:1 write: 0:M Review
1:1 1:1 0:M
has file Has has

das
1:1 1:M 1:1
Shipping Type 1:1 has 0:M Order d Detail Shopping cart Inventory
items
0:M 0:M
is in s has
s
s
f
d
g 0:1 1:1
g
h
h
d
y
f
S Purchase history state tax
i
s
i
Figure 2 Entity Relationships

3.3 component modeling
Component diagram is types of physical diagram that shows the software components of
a system and how they are related to each other. These relationships are called
dependencies. Components represent the physical packaging of a module of code. The
dependencies between the components show how changes made to one component may
affect the other components in the system. Dependencies in a component diagram are
represented by a dashed line between two or more components. Component diagrams
can also show the interfaces used by the components to communicate to each o
Figure 21: component modeling

3.4DEPLOYEMENT MODELLING
Deployment modeling 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 well-
defined 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 22: deployment modeling

CHAPTER FOUR
CHAPTER FIVE
Conclusion and recommendation
5.1 conclusion
The Internet has become a major resource in modern business, thus
shopping has gained significance not only from the entrepreneur’s but also from
the customer’s point of view. For the entrepreneur, shopping generates new
business opportunities and for the customer, it makes comparative shopping
possible. As per a survey, most consumers of online stores are impulsive and
usually make a decision to stay on a site within the first few seconds. “Website
design is like a shop interior. If the shop looks poor or like hundreds of other shops

the customer is most likely to skip to the other site [16]”. Hence we have designed
the project to provide the user with easy navigation, retrieval of data and necessary
feedback as much as possible.
A good shopping cart design must be accompanied with user- friendly shopping
cart application logic. 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. The
shopping cart application described in this project provides a number of features
that are designed to make the customer more comfortable.
This project helps in understanding the creation of an interactive web page and the
technologies used to implement it. The design of the project which includes Data
Model and Process Model illustrates how the database is built with different
tables, how the data is accessed and processed from the tables. The building of the
project has given me a precise knowledge about how ASP.NET is used to develop
a website, how it connects to the database to access the data and how the data and
web pages are modified to provide the user with a shopping cart application.
5.2 Recommendation
From this study, a shopping Centre website providing online market and web site
package under the same domain is successfully implemented.
Using the principle of content management, online market provides all functions which
customers need for conducting online shopping. Furthermore, the website package
service well known among online store owners is convenient and flexible for any
potential users. For website development open source software is mostly used due to its
low cost of development. Provided services are like wise relatively low in price and
suitable for online market. This website also promotes ecommerce and online marketing
on the Internet, complying with the information technology policy of the government.

Regarding website quality, implementing various techniques of web design and
database management system coupled with other additional services, the website is
quite responsive.
Moreover, to obtain the highest system performance, it utilizes full options of
both hardware and operating system software. With all mentioned techniques, the
website operates with low resource consumption at its massive size. This website will
expand e-commerce business to cover most of available Internet devices and
technology, such as mobile phone, mobile payment, and wireless application protocol
and pocket personal computer.
Reference
1. "The Alibaba phenomenon". The Economics. March 23, 2013.
2. 1982 Videotext Communications, Collected Papers Aldrich Archive, University of Brighton
December 1982
3. 1980 TV paves the way for Information Brokerage, Minicomputer News p. 12 London May
1980, the most comprehensive report of the March 1980 Press Conference launching the
Redifon R 1800/50 computer system. Is 'Information Brokerage' aka 'browser industry'?
4. 2011 M. Aldrich 'Online Shopping in the 1980s' IEEE 'Annals of the History of Computing'
Vol 33 No4 pp57-61 October–December 2011 ISSN 1058-6180 5. 1980 Checking on the
check-outs, Financial Times London 12 July 1980
6. Palmer, Kimberly.(2007) News & World Report.
7. Bignes, Enrique (2005). "The Impact of Internet User Shopping Patterns and Demographics
on Consumer Mobile Buying Behavior". Journal of Electronic Commerce Research 6.
8. "More Consumers Using Tablets to Holiday Shop [STUDY]". Mashable. December 8,
2011.
9. PCI Security Standards Council. "PCI Data Storage Do’s and Don’ts". Retrieved 24 March
2013.

Tanku!

Online Shoppingcorrect

Uploaded by

Document Information

Original Description:

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 Shoppingcorrect

Uploaded by

Copyright:

Available Formats

Department of computer science

DEPARTEMENT OF COMPUTER SCIENCE Page ii

1.1. Background of the project----------------------------------------------------1

DEPARTEMENT OF COMPUTER SCIENCE Page iii

2.1. Study of the Current System-------------------------------------------------14

Chapter 4 Conclusion and Recommendation-----------------------------70

Table: 1.1 Team Compositions--------------------------------------------10

Table 1.2 Schedule feasibility -------------------------------------------11

Table 1.3 Cost Estimation ------------------------------------------------12

Table 1. Use case Create Account-------- ------------------------------31

Table 2. Login------------ -------------------------------------------------32

Table 3. Change Password------------------------------------------------33

Table 4. Search Item------------------------------------------------------34

Table 5. View Item--------------------------------------------------------35

Table 6. Order Item------------ ------------------------------------------36

Table 8. Update Item-----------------------------------------------------38

Table 9. Item Registration-----------------------------------------------39

Table 10. Generate report-----------------------------------------------40

Table 11. Logout----------------------------------------------------------41

Figure 1: DFD Diagram-------------------------------------------------------17

Figure 2: Use case Diagram------------------------------------------------27

Figure 3: Login Sequence---------------------------------------------------42

Figure 5: Change Password-----------------------------------------------44

Figure 6: Search item-----------------------------------------------------45

Figure 7: View item-------------------------------------------------------46

Figure 8: Order Item-------------------------------------------------------47

Figure 9: view Order-------------------------------------------------------48

Figure 10: Update item----------------------------------------------------49

Figure 11: Register----------------------------------------------------------52

DEPARTEMENT OF COMPUTER SCIENCE Page v

Figure 13: logout------------------------------------------------------------54

Figure 14: Login Activity Diagram--------------------------------------53

Figure 15: Search item----------------------------------------------------54

Figure 16: create Account ------------------------------------------------55

Figure 17: View Item -----------------------------------------------------56

Figure 18: Change Password --------------------------------------------57

DEPARTEMENT OF COMPUTER SCIENCE Page vi

DEPARTEMENT OF COMPUTER SCIENCE vii

satisfy their needs this makes the merchant having loss.

DEPARTEMENT OF COMPUTER SCIENCE viii

Hence online shopping system is a management system that is designed to improve

At present manual system is being utilized in the shopping. It requires the

1.1.Background of the project

SUBMMITED TO: MR. ZEWUDU TIGABU SUBMMITED DATE: 09/06/2011

1.1.1 Mission: the missions of the company are as follows

1.1.2 Vision: the visions of the company are as follows

1.2 STATEMENT OF THE PROBLEM

DEPARTEMENT OF COMPUTER SCIENCE Page 2

1.3 OBJECTIVES OF THEPROJECT

 To establish a database for electronics shop and store products

 To enable the customer can purchase product’s online

 To makes fast searching and give information service about goods.

 To search system that used to check the customers product need.

1.4 SCOPE OF THE PROJECT

DEPARTEMENT OF COMPUTER SCIENCE Page 3

 Update product items from database by administrator

1.5 LIMITATION OF THE PROJECT

1.7 ALTRNATIVE SOLUTION

Web based applications: is heavily depending on internet connection, which means

DEPARTEMENT OF COMPUTER SCIENCE Page 4

1.8.2 Beneficiaries of the project

DEPARTEMENT OF COMPUTER SCIENCE Page 5

1.9.2 Schedule feasibility