Online Shopping 2017-18

Bahir Dar University

Bahir Dar Institute of Technology
Faculty of computing
Industrial Project I on
Online Shopping System for Ziguara electronics
Submitted to the faculty of computing in partial fulfillment of the
requirements for the degree of Bachelor of Science in Computer
Science

By:

1. Mekonen Moke 0701030

2. Meklit Mena 0701029

3. Mulugeta Tesfaye 0701062

4. Mekuanint Tilahun 0701032

Advisor: - Gebremaryam Dagnew

January, 2018

BAHIR DAR, ETHIOPIA

|final year documentation

 Online Shopping 2017-18

Declaration
The Project is our own and has not been presented for a degree in any other university and
all the sources of material used for the project have been duly acknowledged.

Name Signature

1. Mekonen Moke ___________________

2. Meklit Mena ___________________
3. Mulugeta Tesfaye ___________________
4. Mekuanint Tilahun ___________________

Faculty: Computing

Program: Computer science

Project Title: Online shopping for Ziguara electronics

This is to certify that I have read this project and that in my opinion it is fully adequate, in
scope and quality, as a project for the degree of Bachelor of Science.

Name of Advisor Signature

Gebremaryam Dagnew ________________

Examining committee members signature Date

1. Examiner 1:____________________ ______________ ______________

2. Examiner 2:____________________ ______________ ______________

It is approved that this project has been written in compliance with the formatting rules laid
down by the faculty.

i|final year documentation

 Online Shopping 2017-18

Acknowledgment

First of all we give praise for our God, who brought us to accomplish our job and who has
given us success, helping us to pass safely through many difficulties.

we would also like to forward our sincerely appreciation and gratitude to our advisor, Mr.
G/Maryam Dagnew for his priceless patience whole hearted encouragement and for his
effort on each and every activities of the project by advising, giving technical guidelines,
helpful comments and suggestions for the completion of this project as we need.

Next we would like to thank the Manager Nasir Ahmed and employees of Ziguara
electronics shop for their contribution and support by giving different information about
the shop.

ii | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Abstract
Online electronics shopping system is mainly designed for Ziguara Electronics Shop and
customer to buy items simply. The main objective of this system is to make buying and
selling process interactive and easy to use. It makes searching, viewing and selecting a
product easier. It contains sophisticated search methods for users to search items they want.
The user can then view the complete detail of each product. The system also provides user
to add a product to the shopping cart by selecting the item they want to buy. The main
emphasis lies in providing customer to order item in easy way by using add to cart or select
one item .The system generates receipt when customer successfully orders the item.

iii | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

List of acronyms
TV –television

GUI –graphical user interface

NFR-nonfunctional requirement

TB- Terabyte

RAM- Random access memory

GB- gigabyte

iv | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

List of Figures

Figure 2.1: Use case diagram ................................................................................................ 12

Figure 2.2: User Interface Prototype ..................................................................................... 26
Figure 2.3: activity diagram for login ................................................................................... 28
Figure 2.4: activity diagram for create account .................................................................... 29
Figure 2.5: activity diagram for change password ............................................................... 30
Figure 2.6: activity diagram for search item......................................................................... 31
Figure 2.7 activity diagram for view item ............................................................................ 32
Figure 2.8: activity diagram for order item .......................................................................... 33
Figure 2.9: activity diagram for view order .......................................................................... 34
Figure 2.10: activity diagram for update item ...................................................................... 35
Figure 2.11: activity diagram for register item..................................................................... 36
Figure 2.12: activity diagram for register seller ................................................................... 37
Figure 2.13: activity diagram for manage employee account ............................................. 38
Figure 2.14: activity diagram for generate report ................................................................ 39
Figure 2.15: activity diagram for logout ............................................................................... 40
Figure 2.16: sequence diagram for login .............................................................................. 41
Figure 2.17: sequence diagram for create account ............................................................... 41
Figure 2.18: sequence diagram for change password .......................................................... 42
Figure 2.19: sequence diagram for search item .................................................................... 43
Figure 2.20: sequence diagram for view item ...................................................................... 44
Figure 2.21: sequence diagram for order item...................................................................... 45
Figure 2.22: sequence diagram for update item ................................................................... 46
Figure 2.23: sequence diagram for register item .................................................................. 47
Figure 2.24: sequence diagram for register employee ......................................................... 48
Figure 2.25: sequence diagram for manage employee account........................................... 49
Figure 2.26: sequence diagram for generate report .............................................................. 50
Figure 3.1: Component diagram............................................................................................ 57
Figure 3.2: Deployment diagram .......................................................................................... 58
Figure 3.3: Class diagram for online shopping .................................................................... 59

v|final year documentation

 Online Shopping 2017-18

Figure 3.4: Persistent diagram ............................................................................................... 60

Figure 3.5: User interface of homepage................................................................................ 61
Figure 3.6: User interface of Login ....................................................................................... 62
Figure 3.7: User Interface of Search Item ............................................................................ 62
Figure 3.8: User interface of add to cart ............................................................................... 63
Figure 3.9: User interface to view item on cart .................................................................... 64
Figure 3.10: User Interface of charge balance...................................................................... 65
Figure 3.11: User interface of generate card ........................................................................ 65

vi | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

List of Tables
Table 1.1: developing environment and programming tools................................................. 6
Table 2.1: use case description for login .............................................................................. 13
Table 2.2: Use case description for change password ......................................................... 15
Table 2.3: Use case description for search item ................................................................... 16
Table 2.4: Use case description for view item ..................................................................... 16
Table 2.5: Use case description for order item ..................................................................... 17
Table 2.6: Use case description for view order .................................................................... 18
Table 2.7: Use case description for update item .................................................................. 18
Table 2.8 Use case documentation for register item ............................................................ 19
Table 2.9 Use case documentation for register employee ................................................... 19
Table 2.10Use case documentation for manage seller account ........................................... 20
Table 2.11: Use case documentation for charge balance ..................................................... 20
Table 2.12: Use case documentation for transfer balance ................................................... 21
Table 2.13Use case documentation for generate report ....................................................... 22
Table 2.14: Use case documentation for logout ................................................................... 22
Table 2.15: Use case documentation for generate card ....................................................... 23
Table 2.16 Use case documentation for deliver item ........................................................... 23
Table 2.17 Use case documentation for return item ............................................................ 24
Table 2.18: Use case documentation for payment ............................................................... 24

vii | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Table of Contents
Declaration ................................................................................................................................. i

Abstract ................................................................................................................................... iii

List of acronyms ......................................................................................................................iv

List of Figures........................................................................................................................... v

List of Tables ..........................................................................................................................vii

Chapter One .............................................................................................................................. 1

1. Introduction ...................................................................................................................... 1

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

1.2. Objectives of the Project ......................................................................................... 2
1.2.1. General Objective ........................................................................................... 2
1.2.2. Specific Objective ............................................................................................ 2
1.3. Statement of the Problem ........................................................................................ 2
1.4. Significant of project ............................................................................................... 2
1.5. Beneficiaries of project ........................................................................................... 3
1.6. Limitation of project ................................................................................................ 3
1.7. Scope of the Project ................................................................................................. 3
1.8. Methodology for the Project ................................................................................... 4
1.8.1. Data Gathering Methods ................................................................................ 4
1.8.2. Analysis and Design Approach ...................................................................... 5
1.8.3. Development Environment and Programming Tools.................................... 6

Chapter Two ............................................................................................................................. 7

2. System features ................................................................................................................ 7

2.1. The Existing System ................................................................................................ 7

2.2. Proposed System...................................................................................................... 8
2.3. Requirement Analysis ............................................................................................. 9
2.3.1. Functional requirement ................................................................................... 9
2.3.2. System Use case ............................................................................................ 10

viii | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

[Link]. Use case Diagram .......................................................................................... 10

[Link]. Use case documentation................................................................................ 13
2.3.3. Business Rules ............................................................................................... 25
2.3.4. User Interface prototype ............................................................................... 26
2.3.5. Activity Diagram ........................................................................................... 27
2.3.6. Sequence Diagram ........................................................................................ 40
2.3.7. Logic Model ................................................................................................... 50
2.4. Nonfunctional Requirement .................................................................................. 53
2.5. System requirement .................................................................................................... 55
2.5.1. Hardware requirements ...................................................................................... 55
2.5.2. Software requirements ........................................................................................ 55

Chapter Three ......................................................................................................................... 56

3. System Design................................................................................................................ 56

3.1. Introduction ................................................................................................................. 56

3.2. Architectural Design.............................................................................................. 56
3.2.1. Component modeling .................................................................................... 56
3.2.2. Deployment Modeling ................................................................................... 57
3.3. Detail Design ......................................................................................................... 58
3.3.1. Analysis class Model ..................................................................................... 58
3.3.2. Persistent modeling ....................................................................................... 59
3.4. User Interface Design ............................................................................................ 60

References............................................................................................................................... 66

Appendices ............................................................................................................................. 67

ix | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Chapter One
1. Introduction
1.1. Background of the project
Ziguara shop is located in Bahir Dar Town, capital city of Amhara region, which is 569km
far away from Addis Ababa. The establishment of Ziguara shop was on 2000 E.C. The
owner of the Shop is Ato Nasir Ahmed. At this time the Shop gives different services to
customers such as Laptops, TV, Refrigerators and other shopping goods. For the future,
the owner of the shop has an idea to build a wide store for the shopping material.

Currently the World is going to be come in once. The introduction of modern computers
since1940’s changing the way people live, learning their environment and the way they
gather information, process, and store data and communicate accurate and timely
information in their daily activities. Therefore without using recently technological
products especially computers, it is impossible to think about social, cultural and economic
development. So in this century using information and communication technology
especially the sophisticated and amusing machine known as computer and modern
information handling in any aspect is a question of survival.

Therefore the system we do to analyze in this project is about Ziguara Shopping

management system. We try the best way to make the complicated process of Ziguara
Shopping Management System as simple as possible using Structured & Modular
technique & Menu oriented interface. We are going to design the website in such a way
that customer may not have any difficulty in using this package & further expansion is
possible without much effort. Even though we cannot claim that this work to be entirely
exhaustive, the main purpose of this project is to make each customers and workers activity
in computerized way rather than manually which is time consuming.

1|final year documentation

 Online Shopping 2017-18

1.2. Objectives of the Project

1.2.1. General Objective

The general objective of this project is to develop interactive web based shopping system
for Ziguara electronics shop to facilitate selling and buying process.

1.2.2. Specific Objective

To achieve the above mentioned general objective, the project addressed the following
specific objectives. The system provides the following:
 Reviewing the existing system problems
 Requirement gathering
 Requirement analysis
 Designing GUI
 Implementation and deploying.

1.3. Statement of the Problem

We have seen problems in the current system and we noticed that we can cope up with
these problems by our field of study.

There is time wastage, when the customer want to buy goods they should come to the
shopping Center, at that time they waste their time as well as they may not get what they
wants exactly. Other problem of existing system is that there is no advertisement so all
customers do not know what goods are there in Ziguara electronics shop. Reach ability is
also another problem, which means, the shop is only restricted in Bahir Dar. In addition
that the current system does not work 24 [Link] is difficult to generating report.

1.4. Significant of project

Significant of this project is:-

 To have more customers.

 To get more profit.

 To address all customers that are used internet needs our item.

2|final year documentation

 Online Shopping 2017-18

 To meet customer satisfaction.

 To promote the item of the company using internet.

 To provide simple and efficient way of online shopping system.

 To store information in to database with less effort, less cost and accurate way.

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

 To let customers to view and order goods online from any part of area.

 To allow business grows larger and faster.

 To find the solution for the problem found in existing system.

 To design and build a particular model of this proposed system.

1.5. Beneficiaries of project

The beneficiaries of this project are:-

 Customers:-gets fast access to see what types of goods they want.

 Manager: - System reduces time wastage and work load.

 Company: - Provide more effective system and reduce need of man power,
increase number of customer and lose of paper because they use manual system.
 Group member:-to increase knowledge, skills and mental satisfaction.

1.6. Limitation of project

Our system will not address the following

 Payment is not connected to the bank.

 It does not search the item by color, discount ,number

1.7. Scope of the Project

The scope of the project has following features.

3|final year documentation

 Online Shopping 2017-18

 The project is developed to perform selling and buying process for customers who
lives in Ethiopia.
 To order item customer must have sufficient balance.

 To order item customer must be registered.

 Login privilege is given for registered user only.

 To create account for manager the privilege is given for administrator only.

 To create account for employees the privilege is given for manager only.

1.8. Methodology for the Project

1.8.1. Data Gathering Methods

Data collection is one of the important tasks in determining and analyzing the existing
system. The data that need to develop the new system are obtained from Ziguara shopping
Center. To gather data and information related to shopping from the related sources of the
existing system the team used the following techniques.
Interview

The most important method that helped us to get most important and critical information
about the general view of the Shop is by interviewing manager of the Shop, seller of the
Shop and some customers.

We ask some questions for Example:-

 How do they work currently?

We have got responses from the Ziguara shop employees and they said that, customer
comes physically to the shop and buy items. As they said when customer buy item from
the shop they pay money to the seller then seller prepare receipt for item and customer take
item.

 Have they any computerized system?

4|final year documentation

 Online Shopping 2017-18

Ziguara shop manager said that, the current system uses manual system that means all
activities are performed by agenda.

 What is the problem of the current system?

Firstly as the shop manager said, to control employees, item and customer information it
is very complex and difficult. Then, as the employee of shop express to identify amount of
item that have in the shop is very difficult. Lastly we asked customers and their response
was buying item from the shop is consumes time and also there is no price agreement
between seller and customer.

Observation

We have observed physically by going to the different shop. Also the service that the Shop
provides were not available easily. The team observed that reservation is only by face to
face.

1.8.2. Analysis and Design Approach

We use object oriented methodology to design and develop our project. It is a style
of programming that focuses on using object and design builds applications.

The reasons why we choose Object Oriented are:-

 It is used to develop much simple and secured system.

 It eliminates redundancy and extends the use of existing classes.

 It has principal of data hiding.

 To construct program from standard working module

 Software complexity can be easily managed.
 To develop quality of software.

 More scalable than their of structured programming root.

 It is a real world modeling in a more complete fashion than do traditional

method.

5|final year documentation

 Online Shopping 2017-18

1.8.3. Development Environment and Programming Tools

There are different hardware and software tools that helped us in order to develop online
shopping system.
Some of these are:

Activities Tools
Platform MS Windows Version 7 and 10
Database XAMP MySQL
Coding language PHP
Documentation MS Word
User Training and Presentation MS PowerPoint
Modeling and scheduling Edraw Max and Visual paradigm
Graphics’ Design Tools Adobe Photoshop CS, Macromedia flash
Table 1.1: developing environment and programming tools

6|final year documentation

 Online Shopping 2017-18

Chapter Two

2. System features

2.1. The Existing System

This illustrates the actors involved in the current system. Those actors in the existing
system are:-

1. Shop manager comes with the following activities:-

 Plan in the Shop

 Organize the sellers
 Control on a daily basis activities
 Make decision
 Control the bill
 Generate report

2. The seller comes with the following activities

 Activate in the customer service

 Keep materials properly

 Obtain customer order

 Check availability

 Show items for the customer

 Tells the price of the item

 Give the items to the customers

 Receive pay from customer

 Submitted total payment to the cashiers

3. Customers come with the following activities:-

 Ask information

7|final year documentation

 Online Shopping 2017-18

 Order item as they want

 Asking price of the item

 Takes items from the seller

 Pay the cost of item

4. Cashiers come with the following activities:-

 Collect bill from the sellers

 Calculate the total bill

 Submitted the bills to manager

Generally, in the current system customers cannot gain access from the Shop by means of
online. There are many services in the Shop and they are done by contact with face to face
to the Shop seller.

2.2. Proposed System

The proposed system is an online shopping system, which provides online shopping facility
available for everyone. Any type of the electronics item will be available for customers,
and it can be easily purchased faster. Online shopping system concentrates more on user
friendly interface and promotes users to purchased faster and easier. There is a facility
available to do online purchase. The registration process of guest is faster and easier.
Customer can avail this facility and buy items easily. All items in the website will be
highlighted with image of the items with cost of each items.

The proposed system have the following purposes:-

 Reserve items to customers as the customer demand. .

 Customers check the availability of items online.
 Enables the customer to search different information about the item.
 The system keep the records of customers order and the items allotted to them.
 The proposed system can generate report.
 Proposed system Reduce files duplications.
 Reduce time and cost.

8|final year documentation

 Online Shopping 2017-18

 This new system is a web based system that enables the users to access the services
given by the system through the Internet.
 Proposed system Changes traditional data processing and handling mechanism into
web based application and database system respectively.
 System gives brief, secure and easy file control system.

2.3. Requirement Analysis

2.3.1. Functional requirement

Functional requirement 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
Guest
 System allows guest to create account.

 System allows guest to search item.

Customer
 System allows customer to login to the system.

 System allows customer to change their password

 System allows customer to search item by name, brand, category

 System allows customer to view items with full information(type, image,

price, number)
 System allows customer to order the item.

 System allows customer to logout from the system.

Manager

 System allows manager to login to the system

 System allows manager to change password.
 System allows manager to view item.

 System allows manager to register employee.

9|final year documentation

 Online Shopping 2017-18

 System allows manager to manage employee account.

 System allows manager to generate monthly report

 System allows manager to generate card.
 System allows manager to logout from the system
Seller

 System allows seller to login to the system

 System allows seller to change password

 System allows seller to search item.
 System allows seller to view order.
 System allows seller to update item

 System allows seller to register new item

 System allows seller to logout from the system

Shop assistant

 System allows shop assistant to login to the system

 System allows shop assistant to change password

 System allows shop assistant to view order.
 System allows shop assistant to update status of ordered item

 System allows shop assistant to logout from the system

2.3.2. System Use case

[Link].Use case Diagram

A use case is a sequence of action that provides a measurable value to an actor another way
to look at it is that a use case describes a way to which a real world to interacts with the
system. An essential use case sometimes called a business the case is simplified, abstract,
generalized use case that captures the intention of the user in a technology and
implementation independent manner. The case models are used to document the behavioral

10 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

(functional) requirement of a system or the “what “of the system. (Scott [Link], 2001,
p. 139)

 A use case describes a sequence of action that provides a measurable value to an

actor and draw as a horizontal ellipse.

 An actor is a person, organization, or external system that plays a role in one or

more interactions with the system and draw as stickman figure. Relationship
between actors and use cases exists whenever an actor is involved with an
interaction described by a use case and modeled as a line connecting use cases and
actors.

11 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Figure 2.1: Use case diagram

12 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

[Link].Use case documentation

Use-case name LOGIN

Use-case number UC01
Description use case to ensure security in system usage
Actor user: (customer, manager, seller, shop assistant and Admin)
Pre-condition User must have username and password
Post-condition User gets access to the system according to their predefined system privilege and
finally he/she logout of the page.
Basic course of actions User action System Response
1. User activates the system. 2. System displays login interfaces and
3. User fills his or her user ID and prompts the user for the user ID and
password and click login button. password.
5. User authenticated and gets access to 4. System verifies user ID and Password.
the system. 6. System displays its main window.
[Link] case ends.
1. if user enters wrong user ID and or password
Alternative course of I. System displays an incorrect user ID and password message.
action II. Go to step 2
III. The use case resumes at step 3 of flow of events.
2. Use case ends.
Table 2.1: use case description for login

13 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Use-case name Create account

Use-case number UC02
Description Use case to allow guest to create account.
Actor Guest
Pre-condition Guest must visit website.
Post-condition User account is created successfully
Basic course of actions User action System Response
1. Guest visit home page and 2. System displays register account user
click on signup link. interface and form.
3. guest fills the form correctly
4. 4. System checks if the form is filled
and clicks on “Register” button correctly
5. 5. System display successful registered
messages and store information in
database
6. Use case Ends.
If form fill information is incorrect
Alternative course of action System display error message and go back to step 2
Table 2.2. Use case description for create account

14 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Use-case number UC03

Use-case name Change Password
Description Use case to allow users to change their password.
Actor Seller, Admin, Customer, Assistant and Manager
Pre-condition UC01
Post-condition password is changed successfully
Basic course of actions User action System Response
1. User clicks “change 2. System displays change password interface and form.
password” link. 4. 4. System controller verifies the form.
3. User fills the form and
5. 5. System displays successfully changed message.
clicks on “change”
6. 6. Use case Ends.
button.
Alternative course of If form fill information is incorrect
action 1. System display error message and returns back to step 2
Table 2.2: Use case description for change password

15 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Use-case number UC04

Use-case name Search Item
Description Use case to retrieve item from data base.
Actor Guest and Customer
Pre-condition User Must visit the system
Post-condition The item is successfully retrieved.
Basic course of actions User action System Response
1. Users enters the name of the 2. System checks from database.
item and click on “search” 3. System displays the item from database.
button. [Link] case ends
If the item is not found in database the system displays not found message and
Alternative course of action returns to step 1
Table 2.3: Use case description for search item

Use-case number UC05

Use-case name view Item
Description This use case allows Manager and seller to view or display all items with their
detail description about the item.
Actor manager and Seller
Pre-condition UC01
Post-condition view all item with full information
Basic course of actions User action System Response
1 Manager and seller clicks the 2. System displays item information from
item button. the data base.
3. Use case ends.
If the item is not found in database the system displays not found message and
Alternative course of action returns to step 1
Table 2.4: Use case description for view item

16 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Use case number UC-06

Use case Name Order Item
Actor: Customer
Description Customers’ order the item, when he/she wants to buy the item.
Precondition  UC04
 Customer selects the item.
 The customer must be register.
Post condition When items are ordered total amount of items must be decreased.
Basic course of action User action System response

1. Customer visit the system. 2. System displays search form.

3. Customer enter item name and 4. System verifies the input from
clicks on search button. database.
6. Customer select the item. 5. System retrieves search result
8. Customer select quantity of 7. System displays quantity of item,
item and click “add to cart “button price and add to cart button.
10. Customer clicks on cart link 9. System adds the item on cart.
12. Customer clicks on checkout 10. System displays list of item on cart
button. 13. system displays personal information
14. customer fills form and click on form
order button 15. system controller checks form and
17. customer prints receipt add information in database
16. System creates receipt with
confirmation code
18. use case ends
Alternative course of action 1. If the item is not found the system state is unchanged.
2. If there is no enough balance system display “not enough” message.

Table 2.5: Use case description for order item

17 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Use-case Number UC-07

Use-case Name View Order
Actor Seller and shop assistant
Description Use case allow Seller and shop assistant to view list of ordered items.
Pre-condition UC-01
Post-condition Seller and shop assistant views customers order.
Basic course of Action User Action System Response
1. Seller and shop assistant initiates to 2. System displays order link.
view orders on main menu. 4. System sends the requested order to DB
3. Seller and shop assistant clicks the and display orders on order UI.
order link. 5. use case ends
Table 2.6: Use case description for view order

Use case number UCO8

Use case Name update Item
Actor: Use case to edit or change the existing item information.
Related use case Seller
Description Item must exist in database
Precondition System updates the item information.
Post condition update Item
Basic course of User action System response
action
1. Seller enters main menu 2. System displays list of items
3. Seller select item and clicks on 4. System displays update item user interface.
update button. 6. System controller verifies the form
5. Seller fills item information. 7. System successfully updates information.
8. Use case Ends.

Alternative course of 1. If item is not found returns back to basic course of action 2 to update item.
action
Table 2.7: Use case description for update item

18 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Use case number UCO9

Use case Name Register Item
Actor: Seller
Description Use case to insert items into item table.
Precondition UC01
Post condition Items are registered to the data base.
Basic course of action User action System response

1. Seller enters into main menu and clicks on 2. System displays item
register item button. registration form.
3. Seller fills information about the item and 4. System controller verifies a
clicks on register button. form store into database.
5. System displays message.
6. Use case Ends.
Alternative course of action 2. If item is not correctly filled returns back to basic course of action 2 to
register item.
Table 2.8 Use case documentation for register item

Use-case Number UC-10

Use-case Name Register Employee
Actor Manager
Description Use case to register employee.
Pre-condition UC-01
Post-condition The seller is successfully registered.
Basic course of Action User Action System Response

1. The manager enters to main 2. System displays registration form.

menu and clicks on register employee 4. The system controller verifies the form.
button. 5. The system stores into database.
3. The manager fills the form and 6. System displays message.
clicks on register button. 7. Use case Ends.

Table 2.9 Use case documentation for register employee

19 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Use-case Number UC-11

Use-case Name Manage employee account
Actor Manager
Description Use case to control employee account.
Pre-condition UC-01
Post-condition Manager control seller account.
Basic course of Action User Action System Response

1. The manager enters into main menu 2. System displays list of seller
and clicks on manage seller link. and search form.
2. The manager enable or disable seller 4. Use case Ends.
account.
.
Table 2.10Use case documentation for manage seller account

Use-case Number UC-12

Use-case Name Charge balance
Actor Customer,
Description Use case to allow customer to insert money into their account.
Pre-condition Customer must buy card from shop.
Post-condition The amount is successfully charged and added to customers’ account
Basic course of Action User action System Response

1. Customer clicks on recharge balance. 2. System displays charging

3. Customer enters hidden number and clicks interface
recharge button. 4. System adds balance to
customers account and send
message.
5. Use case Ends.
Alternate course of Action 4.1 If the card number is not correct, system displays error message.

Table 2.11: Use case documentation for charge balance

20 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Use-case Number UC-13

Use-case Name Transfer balance

Actor Customer
Description Use case to allow customer to transfer balance to another customer.
Pre-condition Customer must have enough balance in his/her account.
Post-condition The balance is transferred successfully.
Basic course of Action User action System Response

1. Customer clicks on recharge 2. System displays transfer

balance button. balance link.
3. Customer clicks on transfer 4. System requests customers
balance button. email to transfer balance.
5. Customer fills the email of the 6. System requests amount of
customer. money to be transferred.
7. Customer enters amount of money 8. System displays “are you sure
to be transferred and clicks on to transfer” message with
transfer button. “yes/no” option.
9. Customer clicks on “yes” option. 10. System displays message.
11. Use case Ends.
Alternate course of Action 8.1. If customer clicks on “no” option system returns back to home.
9.1. If there is no enough balance from customer account, system
displays “you have not enough balance please recharge” message.

Table 2.12: Use case documentation for transfer balance

21 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Use-case Number UC-14

Use-case Name Generate Report
Actor Manager
Description Use case to allow manager to generate a report about the item information.
Pre-condition UC-01
Post-condition Generate monthly report.
Basic course of Action User action System Response
1. Manager enter to the main menu and 2. System request criteria to
clicks on generate report button. generate report.
3. Manager select criteria and fills the 4. System generates report.
selected criteria. 5. Use case Ends.

Alternate course of 3.1 If the selection information is empty or not found go to 3.

Action

Table 2.13Use case documentation for generate report

Use-case Number UC-15

Use-case Name Logout
Actor Admin, Seller, Customer, Manager and Shop assistant
Description Use case to sign out from the system.
Pre-condition UC-01
Post-condition User logouts from the system
Basic course of User Action System Response
Action 1. User clicks on logout button. 2. System responds the requested action.
3. Use case Ends.

Table 2.14: Use case documentation for logout

22 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Use-case Number UC-16

Use-case Name Generate card
Actor Manager
Description Use case to allow manager to prepare card number.
Pre-condition UC01
Post-condition Card number is successfully generated
Basic course of Action User Action System Response
1 Manager click on “generate card” link 2. system request amount of each
3. Manager enter amount of card generated card
4. system save generate card in
database
5. system display generated card
6. use case ends
Table 2.15: Use case documentation for generate card

Use-case Number UC-17

Use-case Name deliver item
Actor Shop assistant
Description Use case to give Ordered item for customer
Pre-condition item must be ordered
Post-condition Customer received the item from shop assistant
Basic course of Action User Action System Response
1 shop assistant click on “Delivered” 1. system request order id
button 4. system checks order id
3. shop assistant enter order id 5. use case ends
Alternative course of action If the order id is not correct
1. System displays “please enter the correct order id ”
2. After three times trial System returns back to shop assistant homepage.
Table 2.16 Use case documentation for deliver item

23 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Use-case Number UC-18

Use-case Name Return item
Actor Customer
Description Use case to return ordered items if it has a problem.
Pre-condition Customer must have enough reason.
Post-condition Item is returned or changed by other item.
Basic course of Action User Action System Response
1. Customer clicks return link. 2. System displays return form.
3. Customer fill form and clicks on submit
button.
4. use case ends

Table 2.17 Use case documentation for return item

Use-case Number UC-19

Use-case Name Payment
Actor Customer
Description Use case to pay money for ordered items.
Pre-condition Customer must have enough balance
Post-condition Customer received the item from shop assistant
Basic course of User Action System Response
Action 1. Customer clicks on cart link 2. System displays list of item on cart
3. Customer clicks on checkout button. and total price.
5. customer fills form and click on order 4. system displays personal information
button form
6. System checks balance of customer
and store information in database.
7. use case ends
Alternative course of 1. If there is enough balance in customer account, system displays message to
action recharge balance.

Table 2.18: Use case documentation for payment

24 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

2.3.3. Business Rules

Any organization has its own rule and regulation to run the system in good manner. A
business rule is effectively an operating principles or policy that software must satisfy and
it is what a guidelines that are fulfilled by the functional requirement. Identifying and
documenting business rules are thus important because it enables us to refer easily rules
for other development artifacts, such as models and use cases. Thus business rules of
Online shopping system are described as follows.

To access the system the customer must be in network coverage area.

Customer must be good in computer usage.
The seller must check if order is exist or not from the customer.
Customer must know English language.
Customer must know the address of web.
The system will be platform independent.
When customer buy card from shop, he/she checks card number is hidden or not
To return item customer must give enough reason.
If customer wants to return item they must report between 24 hour intervals.

25 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

2.3.4. User Interface prototype

Figure 2.2: User Interface Prototype

26 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

2.3.5. Activity Diagram

An activity diagram illustrates the dynamic nature of a system by modeling the flow of
control from activity to activity. An activity represents an operation on some class in the
system that results in a change in the state of the system. Typically, activity diagrams are
used to model workflow or business processes and internal operation. Because an activity
diagram is a special kind of state chart diagram, it uses some of the same modeling
conventions. Activity diagrams are mainly used as a flow chart consists of activities
performed by the system. But activity diagram are not exactly a flow chart as they have
some additional capabilities. These additional capabilities include branching, parallel flow
etc. (K.K. Agarwal, 2005, p. 222)

27 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Figure 2.3: activity diagram for login

28 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Figure 2.4: activity diagram for create account

29 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Figure 2.5: activity diagram for change password

30 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Figure 2.6: activity diagram for search item

31 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Figure 2.7 activity diagram for view item

32 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Figure 2.8: activity diagram for order item

33 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Figure 2.9: activity diagram for view order

34 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Figure 2.10: activity diagram for update item

35 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Figure 2.11: activity diagram for register item

36 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Figure 2.12: activity diagram for register seller

37 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Figure 2.13: activity diagram for manage employee account

38 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Figure 2.14: activity diagram for generate report

39 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Figure 2.15: activity diagram for logout

2.3.6. Sequence Diagram

A sequence diagram is a UML interaction diagram. It represents the chronology of the
passing of messages between system objects and actors. It used to illustrate a possible
scenario of a use case, the execution of an operation, or simply an interaction scenario
between classes of the system.

To use one or more sequence diagrams to pass a use case or to identify all the possibilities
of a complex behavior. A sequence diagrams conveys the same kind of information it
concentrates on the chronology of messages passing between the objects in place of their
structure.

A sequence diagram shows actors, objects (instances of classes) and the messages sent
between them. By default, Power Designer provides an "interaction frame", which
surrounds the objects in the diagram. Messages can originate from or be sent to any point
on the interaction frame, which acts as the exterior of the system being modeled, and
these gates can be used in place of actor objects.

40 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Figure 2.16: sequence diagram for login

Figure 2.17: sequence diagram for create account

41 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Figure 2.18: sequence diagram for change password

42 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Figure 2.19: sequence diagram for search item

43 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Figure 2.20: sequence diagram for view item

44 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Figure 2.21: sequence diagram for order item

45 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Figure 2.22: sequence diagram for update item

46 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Figure 2.23: sequence diagram for register item

47 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Figure 2.24: sequence diagram for register employee

48 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Figure 2.25: sequence diagram for manage employee account

49 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Figure 2.26: sequence diagram for generate report

2.3.7. Logic Model

Pseudo code is one type of algorithm representation method by using English language

.Method name=”Login

Input

50 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

 Username
 Password

Return type: void

Procedure

Begin

Prompt username
Prompt password
Retrieve usernames from database
Retrieve password from database
If (entered username and password don’t match retrieved username and
password)
{
Display error message “username or password incorrect”
Prompt username and password again
}
Take user to appropriate interface page
End

Method name=”Register product”

Input

 Product Id
 Product Name
 Product category
 Brand name
 Quantity
 Price

51 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

 Image
 description

Return type: void

Procedure

Begin

Prompt username
Prompt password
Retrieve usernames from database
Retrieve password from database
If (entered username and password don’t match retrieved username and
password)
{
Display error message “username or password incorrect”
Prompt username and password again
}
Take user to appropriate interface page
End

Method name=”Create account”

Input

 First Name
 Last Name
 Email
 City
 Phone no.
 Country
 Username
 Password
 status

52 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Return type: void

Procedure

Begin

Prompt First Name

Prompt Last Name
Prompt Email
Prompt City
Prompt Phone no.
Prompt Username
Prompt Password
Retrieve username and email from database
If (username or email exists)
{
Display error message “username or email already exist”
}
Store all fields in database
End

2.4. Nonfunctional Requirement

A Non-functional requirement defines the overall qualities or attributes of the system. It

place restrictions on the system being developed, the development process, and specify
external constraints that the system must meet.

Usability

NFR1:- The system provides a help and support menu in all interfaces or give direct input
for the user to interact with the system.

NFR2:- The user can use the system by reading help and support.

53 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Security

NFR3:- The system provides username and password to prevent the system from
unauthorized access.
NFR4:- The user recommended the password greater than eight characters combination
of digit, letter, and special characters.
NFR5:- The authenticate users should have privilege to access the database.

Performance
NFR6:- speed of the system operation is very high. That means the accuracy
and response time of the system should be very fast.

Availability

NFR8:- The system should always be available for access at 24 hours, 7 days
a week. Also in the occurrence of any major system malfunctioning, the
system should be available in 1 to 2 working days, so that business process is
not severely affected.

Reliability

NFR9:- The developed system should able to perform a required function

under stated

Conditions for a specified period of time.

Portability

NFR10:- The system supports every operating system.

54 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

2.5. System requirement

2.5.1. Hardware requirements

For the efficient deployment of the new proposed system, the following hardware
components are expected:-
 8GBRAM or above.

 Corei3 processor or above

 1TB Hard disk or above.

2.5.2. Software requirements

 Windows operating system

 Web browser

55 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Chapter Three

3. System Design

3.1. Introduction
The purpose of design is to determine how the system is going to build and to obtain the
information needed to drive the actual implementation of the system. It focuses on
understanding the model how the software will be built. System design is the detail
investigation of system elements from logical view.

It is designed to simplify functions of the manual system and it is capable of doing large
amount of works in short period of time with more accuracy and reliability. Generally this
project design describes how the project is designed, what tasks done under this project
and different modules and their way of functioning.

3.2. Architectural Design

Architecture design is the process of defining a structured solution that meets all of the
technical and operational requirements, while optimizing common quality attributes such
as performance, security, and manageability. It involves a series of decisions based on a
wide range of factors, and each of these decisions can have considerable impact on the
quality, performance, maintainability, and overall success of the application.

Architecture design encompasses the set of significant decisions about the organization of
a software system including the selection of the structural elements and their interfaces by
which the system is composed; behavior as specified in collaboration among those
elements; composition of these structural and behavioral elements into larger subsystems;
and an architectural style that guides this organization

3.2.1. Component modeling

In this Diagram components of the system will be wired showing that there is relation
among components, management of the system, database and operations performed on
databases such security issue. The diagram shows which component or objects will be

56 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

accessed by whom and what type of security infrastructures are used. The diagram is
simulated below.

Figure 3.1: Component diagram

3.2.2. Deployment Modeling

Deployment diagrams show the configuration of run-time processing elements and the
software components, processes, and objects that live on them. Software component
instances represent run-time manifestations of code units. (Martin Schader; Axel
Korthaus;, Dec 6, 2012) Hence, the diagram below depicts how the software architecture
and hardware components are going to be organized at the time of deployment.

57 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Figure 3.2: Deployment diagram

3.3. Detail Design

3.3.1. Analysis class Model

Design class modeling is used to model the static structure of how the software will be
built. In particular, class modeling shows classes, their internal structure, and their
relationships. And also shows a collection of (static) declarative model elements, such as
classes, interfaces, and their relationships, connected as a graph to each other and to their
contents.

Class diagram provide a graphical notation for modeling classes and their relationship.
They are concise, easy to understand, and work well in practice. Class diagrams are the
backbone of almost every object-oriented method including UML.

58 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Figure 3.3: Class diagram for online shopping

[Link] modeling
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. (Bernd Bruegge, Allen [Link], 2010) The database will store information

regarding Brand, Categories, Items, Shopping cart, users or customers.

59 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Figure 3.4: Persistent diagram

3.4. User Interface Design

60 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Figure 3.5: User interface of homepage

61 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Figure 3.6: User interface of Login

Figure 3.7: User Interface of Search Item

62 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Figure 3.8: User interface of add to cart

63 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Figure 3.9: User interface to view item on cart

64 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Figure 3.10: User Interface of charge balance

Figure 3.11: User interface of generate card

65 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

References
1) Bernd Bruegge, Allen [Link]. (2010). Object-oriented Software Engineering:
Using UML, Patterns, and Java. Prentice hall.

2) BrueggeBernd. (2000). Object oriented Soft ware Engineering Conquering

Complex and Changing System. Upper Saddle River: Prentic Hall.

3) Jeffery, D. (2001). Object Oriented System Analysis and Design Method . (5th ed.).
USA: Irwin\McGraw-Hill Inc.

4) K.K. Agarwal. (2005). Software Engineering. New Age International.

5) Martin Schader; Axel Korthaus;. (Dec 6, 2012). The Unified Modeling Language:
Technical Aspects and Applications. Germany: Springer Science & Business
Media.

6) Scott [Link]. (2001). Object primer: The application Developer Guide to

Object Oriented and UML. (2nd rev. edition ed.). England: The Cambridge
University.

66 | f i n a l y e a r d o c u m e n t a t i o n
 Online Shopping 2017-18

Appendices
Samples of questions are asked to Ziguara electronics shop workers and the responses are
also recorded as follows

 What type of system do they use?

 Have they any computerized system?

 What is the problem of the current system?

67 | f i n a l y e a r d o c u m e n t a t i o n