Mettu University Online Shopping

METTU UNIVERSITY
FACULITY OF ENGINEERING AND TECHNOLOGY

DEPARTEMENT OF INFORMATION TECHNOLOGY
Title - ONLINE SHOPPING SYSTEM
BY
GROUP MEMBERS ID
1. ZIYAD ALIYA …………………………………..RET/2173/08

2. WENDALE MHRET …………………………………..RET/2162/08
3. HUSEN MOHAMMED………………………………..RET/2049/08
4. HIWOT BIKSE ……………………………….. RET/2048/08
5. JEDED YUYE ……………………………….. RET/2050/08
A senior project:
Submitted to Department of Information Technology, Mettu University, and Engineering and
Technology faculty, in Partial fulfillment for the requirement of the Degree of Bachelor Science
in Information Technology.
Advisor:Mr.Abue
Submitted Date 5/06/2011Ec
METTU UNIVERSITY
ENGINEERING AND TECHNOLOGY FACULTY
DEPARTMENT OF INFORMATION TECHNOLOGY
APPROVAL SHEET
------------------------------------------------------------------------------------------------ ---
This is to certify that the senior project titled “Online Shopping System of Yemewodsh
Electronics “.
Submitted by:
1. ZIYAD ALIYA …………………………………..RET/2173/08
2. WENDALE MHRET …………………………………..RET/2162/08
3.HUSEN MOHAMMED………………………………..RET/2049/08
4.HIWOT BIKSE ……………………………….. RET/2048/08
5.JEDED YUYE ……………………………….. RET/2050/08
2.
Submitted to Department of Information Technology, Mettu University, Engineering and

Technology faculty, in Partial fulfillment for the requirement of the Degree of Bachelor Science
in Information Technology.
The contents of this document in full, or in parts, have not been submitted to any other institute
or university for the award of any degree or diploma.
Advisors:
Name__________________________ Signature_______________ Date _________
Name_______________________________ Signature_______________ Date _________
Examiners:
Name____________________________ Signature_______________ Date _________
Name_______________________________ Signature_______________ Date _________
ii
Table Content
Abstract .......................................................................................................................................................... I
Chapter One .................................................................................................................................................. 2
1. Introduction ............................................................................................................................................... 2
1.1. Background of the project ...................................................................................................................... 3
1.2 Background of shop ................................................................................................................................ 3
1.3 Existing System ...................................................................................................................................... 4
1.4 statement of Problem .............................................................................................................................. 4
1.5 Objectives of the project ......................................................................................................................... 5
1.5.1 General Objectives ........................................................................................................................... 5
1. 5.2 Specific Objectives ......................................................................................................................... 5
1.6 Project scope and limitation ................................................................................................................ 5
1.6.1 Scope of the study .............................................................................................................................. 5
1.6.2 Limitation of the project .................................................................................................................. 6
1.7 Methodology of the project ..................................................................................................................... 6
1.7.1. Method for data collection .............................................................................................................. 6
1.7.2 Methodology for system analysis and design .................................................................................. 7
1.7.3 System development Tools .............................................................................................................. 8
1.7.3.1 Hardware tools .......................................................................................................................... 8
6.3.2. Software tools ............................................................................................................................. 9
1.8 Feasibility Assessment ............................................................................................................................ 9
1.8.1 Economical feasibility ..................................................................................................................... 9
Intangible cost ..................................................................................................................................... 10
1.8.2PoliticalFeasibility .......................................................................................................................... 11
1.8.3 Technical Feasibility ...................................................................................................................... 11
1.8.4 Operational Feasibility ................................................................................................................... 12
iii
1.8.5 Schedule Feasibility ....................................................................................................................... 12
1.8.6 Legal/Contractual Feasibility ......................................................................................................... 13
1.9 Significance of the project .................................................................................................................... 13
1.10 Risk Assessment and management ..................................................................................................... 14
1.10.1 Risk Assessment .......................................................................................................................... 14
1.10.2 Risk management ......................................................................................................................... 14
1.11 Organization of the project ................................................................................................................. 14
Chapter Two ................................................................................................................................................ 15
Introduction ................................................................................................................................................ 15
2.1 Overview the Existing System ............................................................................................................... 15
2.2 Supplementary Requirements .............................................................................................................. 15
2.2.1 Business rules ................................................................................................................................. 15
2.2.2 Constraints ..................................................................................................................................... 16
2. 3 Overview of the Proposed System ....................................................................................................... 16
2.4 Software requirement specification (SRS) ............................................................................................ 16
2.4. 2 Non Functional Requirements ...................................................................................................... 17
2.4.3 System requirement ...................................................................................................................... 17
2.5 Use case Diagram .................................................................................................................................. 18
2.5.3Sequence Diagram .............................................................................................................................. 29
2.5.4 Activity diagram ................................................................................................................................. 38
Figure12 : Activity diagram for Customer registration ............................................................................... 39
Figure 8: Activity diagram for purchase product ........................................................................................ 45
2.5.5. Class Diagram .................................................................................................................................... 46
2.5.6 User interface prototype ................................................................................................................... 47
2.2.7 Identifying change cases .................................................................................................................... 49
Chapter Three: System Design Document ................................................................................................. 50
3. Purpose and goals of design ................................................................................................................... 50
3.1. INTRODUCTION .................................................................................................................................... 50
3.2. Purpose of System Design.................................................................................................................... 50
3.3. Design Goals ......................................................................................................................................... 51
3.4 Class modeling Diagram ........................................................................................................................ 51
3.5. Current Software Architecture ............................................................................................................ 52
iv
3.6. Proposed Software Architecture ......................................................................................................... 52
3.6.1. Subsystem Decomposition................................................................................................................ 52
3.4.6.1 Boundary Conditions ...................................................................................................................... 64
3.4.6.2 Exception Handling .................................................................................................................... 66
v
List Of Figure
Figure 1:Use Case diagram............................................................................. Error! Bookmark not defined.
Figure 2: Sequence Diagram for login ........................................................... Error! Bookmark not defined.
Figure 3:Sequence Diagram for add new product ......................................... Error! Bookmark not defined.
Figure 4:Sequence Diagram for registration ............................................................................................... 31
Figure 5:Sequence Diagram for update product ........................................................................................ 32
Figure 6:Sequence Diagram for generate report ........................................................................................ 33
Figure 7:Sequence Diagram for send comment ............................................ Error! Bookmark not defined.
Figure 8:Sequence Diagram for view comment.......................................................................................... 34
Figure 9: Sequence Diagram for order product ............................................. Error! Bookmark not defined.
Figure 10: Sequence Diagram for Manage Account ...................................... Error! Bookmark not defined.
Figure 11:Activity diagram for customer registration.................................... Error! Bookmark not defined.
Figure 12:Activity diagram for user login ....................................................... Error! Bookmark not defined.
Figure 13:Activity diagram for Create User Account ..................................... Error! Bookmark not defined.
Figure 14:Activity diagram for Order Products .............................................. Error! Bookmark not defined.
Figure 15: Activity diagram for update product ......................................................................................... 39
Figure 16: Activity diagram for generate report ......................................................................................... 41
Figure 17: Activity diagram for Give Comment........................................................................................... 42
Figure 18: Activity diagram for Manage Account ....................................................................................... 42
Figure 19: Activity diagram for View Comment .......................................................................................... 43
Figure 20: Activity diagram for View item .................................................................................................. 43
Figure 21: Activity diagram for Manage Product ........................................................................................ 44
Figure 22:Class Diagram .............................................................................................................................. 46
Figure 23:User interface prototype for administrator ................................................................................ 47
Figure 24: User interface prototype for warehouse employee ..................... Error! Bookmark not defined.
Figure 25: User interface prototype for Warehouse Employee Information ............................................. 48
Figure 26: User interface prototype for Administrator Information .......................................................... 48
Figure 27:User interface prototype for Customer Information .................................................................. 49
Figure 28:Class modeling Diagram .............................................................................................................. 51
Figure 29: proposed software architectures .............................................................................................. 52
Figure 30: System decomposition ............................................................................................................... 53
Figure 31: Subsystem- Interface ................................................................................................................. 54
Figure 32: Subsystem- Registration Management...................................................................................... 55
Figure 33: Subsystem- Request Management ............................................................................................ 56
Figure 34: Subsystem-Account Management ............................................................................................. 56
Figure 35: Subsystem- Stock Management ................................................................................................ 57
Figure 36: Subsystem- Data Management.................................................................................................. 58
Figure 37: Component Diagram .................................................................................................................. 59
Figure 38: Deployment Diagram ................................................................................................................. 60
Figure 39: User interface Design for Admin Login ...................................................................................... 66
Figure 40: User interface Design for comment ........................................................................................... 67
Figure 41: User Interface Design for Customer Registration ...................................................................... 68
vi
Acronyms
OOA It stands for -: Object Oriented Analysis
OOSAD -Object Oriented System Analysis and Design

SRS -Software Requirement Specification
RAM - Random Access Memory
UML -Unified modeling language
MYSQL -structured query language
GHZ -Gigahertz
BR -Business Rule
HTML -hypertext markup language
CSS -cascading style sheet
TVM -Time value of money

GB -Gigabyte
ID -Identification Card
CD -Compact Disk
MS - Microsoft
SDLC -system Development life cycle
PHP -Hyper text preprocessor
vii
viii
1
Online Shopping System of Yemewodsh Electronics 2019
Abstract
The Online Shopping is a web based application intended to online for customer. The main
objective of this application is to make it interactive and its ease of use. It would make searching,
viewing and selection of a product easier.
This project is concern about online shopping system for literature materials like electronic
product. The customer can view the complete detail of each product. The application also
provides to customer can add a product to the shopping cart and also they may view the contents
of their shopping cart at any time and may they remove items at will finally Our system provides
automatically calculates the total price then display for the customer. The main emphasis lies in
providing customer to order item in easy way by using add to cart or select one item The system
generate receipt for the customer when successfully order item The Admin have many privilege
in the system, such as create and delete employee account, viewing order. For sales person,
search item, view comment and view report. The warehouse employee also has privilege such as
manage product (add, delete, update product) and view order.
I
Chapter One
1. Introduction
Online Shopping center is the system that involves selling and buying transaction process. Such
transaction is concentrate on literature materials like Electronic product such as, Computer, Cell
phones, printer, scanner, Photo copier and other kinds of electronic materials. Current Ethiopian
shopping centers are most of them are use a manually system to sale their products. The Online
Shopping Cart website allows to customer online shopping collecting items in a shopping cart.
They may view the contents of their shopping cart at any time and add or delete items at will.
This system provides automatically calculates the total price of the product, and provide payment
system. This is website which helps you to do the major part of online shopping by using this site
and can be managed by online. Customer can do the all major transaction in a secured way. Here
the customer will feel shopping by adding the selected product to his/her cart in addition to that
he/she can also does bulk addition into the cart before purchasing. This all options are done by
session management. To ensure the authentication of the customer, he/she must have to register
before purchasing. Therefore, the online shopping system we planned to analyze in this project
we will try the best way to make the complicated process of the shopping system as simple as
possible using Structured, Modular technique and Menu oriented interface. We are going to
design the website in such a way that customer may not have any difficulty in using this package
& further expansion is possible without much effort. Even though we cannot claim that this work
to be entirely exhaustive, the main purpose of this project is to make each customers and sellers
activity in automated or computerized way rather than manually.
2
1.1. Background of the project

After a simple meeting with the shop management, we were able to gain more details and
processes that need to be considering in developing the system. Requirement gathering process
was done by using some techniques such as interviewing and observations. Interviewing with the
manager, workers and customers face to face is beneficial to the system and clear out many
differences regarding requirements about the system. We found the all requirements that have to
be computerizing such as customer’s details, products details. The requirements gathering we
have done helped us in identifying the entities, attributes and the relationships of the scenario of
the shop and the information we gathered helped us to decide the data that we should handle in
the system database.
The functions of the system that is going to be designed has to be met with the customer
requirements and the outcomes of the functions should have to be addressed the problems that
we have encountered during the requirement gathering phase. The customer requirements
identified during the requirements and analysis activity are organized into a SRS document. The
important components of this document are functional requirements and non-functional
requirements. After the requirements gathering we identified the needs of the shop and begin the
project.
1.2 Background of shop

The Shop’s those our project is intended are located western part of the country in Mettu
town, which is 600km far away from Addis Ababa.
This Shop found in mettu town provides a chance of employee for many workers and more
beneficial socially and economically for local people.For requirement gathering we select
Yemewodsh electronics shop. Yemewodsh electronics was established at the end of 1998
E.C. by Yemewodsh Engda. The shop providing job opportunity for over 2 people.As the
shop manager Weizero Yemewodsh says, the shop uses micro management system which
requires the manager himself to work on every aspect of the shop other than just managing
3
others. From this the shop benefits inspiration among the employees to work hard. The
shopplans to add more employees, and provide suitable services for any customer that comes
to town.
1.3 Existing System

The current system of Yemewodsh electronics are not provide goods or products online and has
not provide online banking system to make payment, to their purchased items. And also no
anyway of method and awareness on preparing report and receipt. They simply selling and
purchasing items to their customers and only generate the day to day income of the shop. The
activity of the retailer is selling the items dealing within a customer.
The current system for shopping is to visit the shop manually and from the available product
choose the item customer want and buying the item by payment of the price of the item.
1.4 statement of Problem

The overall activities in the existing system are completely manual. The Customer is completely
depending on the manual process for buying the products. Manual process is a time consuming
factor. And when customer approaches for a manual shopping directly, actually he/she does not
have an idea about things like, price range, items, etc. The time which has been spent by the
customer in manual shopping can equates to multiple number of shopping. As customer can sit at
home and browse in a fraction of seconds. Thus we need to change to a system like “Online
Shopping “.
Some of the problems exist in the system: -
 It is a time consuming process.
 Use more labor
 There is not written item descriptions and price
 It takes more time to process transaction
 There is no advertisement of product
 The shop open in a day 10 hours only
4
 The customer must be waiting until another customer is served.

 It is difficult to identify the required product.
 Description of the product limited.
 It is a time consuming process
 It is less user-friendly.
1.5 Objectives of the project

1.5.1 General Objectives
The general objective of this project is to design and develop online shopping system.
1. 5.2 Specific Objectives
In order to fulfill the above objectives, we need to accomplish the following specific objectives.
 To conduct online payment
 Upload the Products
 To advertise products by online
 Transaction will be carried on time
 To satisfy customer with the service
 Analyzing the existing system
1.6 Project scope and limitation
1.6.1 Scope of the study

The scope of this project is defined in terms of the tasks that the system accomplishes.
Thus, the scope of the project is limited to:
 The system deducts the total amount of price from the customer account
 Customer can add and remove items from the cart
5
 Display the expire date of the product
 Online ordering systems
 Register new customers
 Customer can view his/her cart with total price of the product
 Managing products (adding, deleting, and updating).
 Generating reports.
 Display ordered items information
 Generate advertisement for items which price is discount and when new item is
registered.
1.6.2 Limitation of the project

Due to different reasons like shortage of time, lack of materials and others, our project do not
implement the whole services. These services are:
 Rate of taxes
 salary of the employees
1.7 Methodology of the project
1.7.1. Method for data collection
We use primary data collection methods have been implemented for the identification of the
problem and understanding the existing system.
Some of the methods we use: -
Interview
The most important method that helps us to get most important and critical information about the
general view of the Shop is by interviewing owner of the Shop, seller of the Shop and some
customers.
We ask some questions for Example: -
 Have you any computerized system?
6
 Do you have an items list with their descriptions and price?

 What is the problem of the current system?
 How many employees you have?
We get responses from the persons and they also say that, the current system is used manual
system that means all activates performed by agenda. So that the system is complex, more time
consuming and redundant activity.
Questionnaire
This method of knowing all about system by preparing questionnaire.We use both open ended
and closed ended. The proposed people give the answer by writing.
Observation
This method is also used to collect data, done by direct seeing the working environment.
We have observed physically by going toYemewodsh electronic shop in Mettu town. Also we
observed that there is no any computerized system in the Shop and also information about the
Shop and the service that the Shop provides were not available easily. The team also observes
that ordering is only by face to face.
Document analysis
By collecting information from different references, projects and web sites about our project title
and by discussing and analyzing the problems with project teams.
1.7.2 Methodology for system analysis and design

We decided to use object oriented system analysis and design (OOSAD) because of the
following reasons.
 It would facilitate code reuse since it implements the concepts of object oriented method
like, inheritance, encapsulation and polymorphism. From development method, we use
prototyping and from testing method we use integration and system testing.
The main reason behind using OOA is:
 Objects are easier for people to understand
 object are derived from the business that we are trying to automate
 Data and process are kept together the main reason we decide to use the object approach
 Code can be reused easily this means we are constantly looking for objects that would be
useful in the system. Even if when a new system has minor differences we are much
more likely to be able to change our existing code to fit.
7
From various types of SDLC methodologies, we specifically choose the iterative methodology
by considering the following advantages.
 Easy to plan and manage

 It is more flexible
 Intermediate product of each phase will be an input for the next phase.
1.7.3 System development Tools

We will use various hardware and software in order to develop our system. Some of these are
1.7.3.1 Hardware tools
No Purpose Hardware name
1 Training Papers
2 Writing Something Pen
3 Writing Soft copy of Documentation Part Computer (Desktop or Laptop)
4 Printing Purpose Printer
5 Storing File CD
6 File Transferring Flash 16 GB
8
6.3.2. Software tools

No Purpose Programs Reason
1 Code Writing Dreamweaver, Notepad++ Easy to use

2 Database Server XAMP Server Database server for PHP
3 Web Server Apache (IIS) Web server for PHP
4 Server side Scripting PHP Understand by server
5 Client Side Coding HTML It works with PHP
6 Client Side Scripting JavaScript Easy way to validate form
7 Coding Language PHP Easy to writing code
8 Cascading Style Sheet CSS It works with HTML and PHP
9 Browsers IE, Mozilla Firefox, Google Better for displaying web
Chrome, Spark browser pages
10 Documentation MS Word 2010 Easy to use

11 User Training MS PowerPoint Best for presentation
12 Modeling and Scheduling Edraw,Visio2013,Visio Easy to design diagrams

2010
1.8 Feasibility Assessment

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

Economic feasibility attempts to weight the costs of developing and implementing a new system,
against the benefits that would occur from having the new system in place. This feasibility study
9
gives the top management the economic justification for the new system. There could be various
types of tangible and intangible benefits and costs on account of automation.
Benefits: the benefits of one system can be expressed in terms of tangible benefit and intangible
benefit.
A. Tangible benefits:
In the project going to be computerized there will be reduction of cost for materials used for manual
operation such as: pen, paper, human power, space needed to keep data record, and save data storage
and time that we are induced or brought in during manual system.
The team calculated the corresponding tangible benefits based on the technique called the time
value of money (TVM).
1. Cost Reduction and Avoidance: - To calculate these following things will be considered. Total
Number of Employee in existing system= 10
Average Salary of each Employee per month = 1000.00Birr
Total money required for payment per year= 10*1000*12= 120,000Birr
Average Number of Employee needed when the new system is deployed= 5
Average salary of each of them per month = 1200.00Birr
Total money required for payment per year= 5*1200*12= 72,000.00Birr
Difference b/n before and after deployment money required for payment
Cost Reduction and Avoidance= 120,000.00Birr-72,000.00Birr= 48,000.00Birr
B. Intangible Benefits
This refers to benefits that cannot easily be measured in terms of money and with certainty.
Some of the intangible benefits of the proposed system are: -
 It minimizes the work load of the worker

 Increase speed of activity
 Efficient work flow
 Save the loss of documents
 Increase flexibility
 On time information
 Increase security
Cost: This is the tangible and intangible cost of the proposed system.
Intangible cost
Intangible cost is our project benefit that can’t convert into monetary values. They are measured
by person’s satisfaction.
10
 Knowledge gain by project developer.

 Increasing the competitiveness of the individual.
 Improving the morale of our team.
 Facilitating information processing of our team.
B. Tangible cost
Hardware cost
Hardware Quantity Price Total

cost per unit price
Name the
material
Pen 3 6:00 18birr

Printing 80 75cent 50birr
Paper 5 50 2:50birr
coverage
Paper(A4) 15 40cen 20birr
Flash 1 180bi 180birr
disk(2GB)
CD disk 1 15bir 15birr
Total 300birr
1.8.2PoliticalFeasibility
Is a measure of how well the system will be accepted by a set of decision makers and the
general public? For a procedure to be enacted and implement, it must be politically
acceptable. Our proposed system is free of any kind of political case so, our project is
politically feasible
1.8.3 Technical Feasibility

The proposed system can be technically feasible because the technical resources needed to
develop, install and to operate is available in the present infrastructure. Evaluating the technical
feasibility is the trickiest part of a feasibility study. A number of issues have to be considered
while doing a technical analysis.
Understand the different technologies involved in the proposed system: Before commencing the
project, we have to be very clear about what are the technologies that are to be required for the
development of the new system.
11
Find out whether the organization currently possesses the required technologies:
Is the required technology available with the organization?
If so is the capacity sufficient?
For instance- “Will the current printer be able to handle the new reports and forms required fort
the new system?”
The technical issue usually raised during the feasibility stage of the investigation includes the
following:
 Does the necessary technology exist to do what is suggested
 Do the proposed equipment’s have the technical capacity to hold the data required to use
the new system?
 Can the system be upgraded if developed?
 Will the proposed system provide adequate response to inquiries, regardless of the
number or location of users?
1.8.4 Operational Feasibility

The proposed system can be used effectively after it has been developed. Users will not have any
difficulty with the new system to produce the expected benefits. System will be developed based
on the policies of the organization and it doesn’t require much training for users. And the new
system will not place any new demands on users nor requires any operating changes. Since the
proposed system was to help reduce the hardships encountered. In the existing manual system,
the new system was considered to be operational feasible.
o User-friendly
o Reliability
o Security
o Portability
o Maintainability
1.8.5 Schedule Feasibility

As we know planning is the first phase of any system so we need to start with the schedule
programs and our project is intended to be with in fixed time interval. Unless and otherwise we
may fall in difficulty in cost estimation and as well as we may fall in the financial problem. To
overcome such problems, we fixed the time interval in which we should finish the development
of the whole time among different section of project by using the techniques of schedule like
Gant chart.
12
Gantt Chart Project Schedule
S.N Phase 2011 E.C

Dec Jan Feb Mar Apr May Jun
1 Project
Proposal
2 Requirement
Analysis
3 Design
4 Implementation
5 Installation &
Testing
6 Project Closure
1.8.6 Legal/Contractual Feasibility
Develop new applications for use on new computers may require new or expanded and more
costly system software license. Concerns the developing system is protected by law not
duplicated without the permission of the developed team and also not re programmed it.
1.9 Significance of the project

 To fulfill what customers need:- Customers need your product or service to function
the way they need in order to solve their problem or desire
 Items deliver on time: -the product can be deliver easily
 Decrease the work load and number of employee:- easily sell through online
 Be reliable and honest:- the product can be deliver or reach special one
 24 hours working time: - that mean the customer can be buying any time and any where
 To describe detail information of the item:- expired date etc….
13
 Safety way of data storage
 The society able to get fast and better service

 Well organized administration
 Easy to access information about the shop
 Maximizing profit
1.10 Risk Assessment and management

1.10.1 Risk Assessment
 Operating system failure
 Shortage of enough lab
 The serious problem is shortage of internet accesses
 Sudden fluctuation of power

 Sickness of group members
 If the project attack by virus
 Dedicated lab room
1.10.2 Risk management

 To use secondary storage device
 backup and recovery
1.11 Organization of the project
This project documentation is organized into five chapters. The first chapter is deals about
introduction and background of the general (as world) and the background of Online Shopping.
The second chapter deals about the system analysis. The third chapter covers about design of the
system. The fourth chapter also deals the implementation of the project. And the fifth chapter
encompasses the conclusion and recommendation for future studies.
14
Chapter Two: Analysis
Introduction
Purpose
Considering the main problem of the online shopping system, the major purpose of this
proposed system is to organize and manage the items which is purchase and sold as well as the
systems also aim generating the daily, monthly, semi and yearly transaction reports and receipts
for each sold items. In addition to this some of the main purpose of this project is:
 Advertising products
 Decrease time and resource of customers etc.
 Provide sale and buy service to customer
 Provide good and fast service to customer
2.1 Overview the Existing System

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

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

The proposed system is concern about the Online Shopping System transaction in order to provide an
alternative solution for the online shopping. For doing activities of the Online Shopping System such as
recording purchased and sold items and generating transaction of it. And also these new systems protect
and secure the Online Shopping System data files in secured way.
2.4 Software requirement specification (SRS)

2.4.1 Functional Requirements
The Functional Requirements Specification documents the operations and activities that a system
must be able to perform. Functional requirements should include functions performed by specific
screens, outlines of work flows performed by the system, and other business requirements the
system must meet
Administrator
Manages Employees
Accept Comment
View order
View report
16
Customer
Register and login to site.
View item, add to cart and Remove items from cart.
Send Comment
Order product
Warehouse employee
Add, update and delete products
View customer order
Update profile.
2.4. 2 Non Functional Requirements

Non-functional requirement is a requirement that specifies criteria that can be used to
judge the operation of a system, rather than specific behaviors this requirement does not
directly affect the performance of the proposed system but, they concerned with security,
performance, usability, maintainability, reliability, efficiency, portability (across
operating systems) testability, understandability etc.
The non-functional requirements of the system are presented below: -
User Interface: - user friendly interface with easy navigational scheme.
Error handling Mechanism: - handles invalid inputs and display user error in
meaningful messages.
Security issue: - provides security tasks such as for registering, for modifying user’s
information and viewing needs authentication and authority.
Maintainability: -When the website fails, it can be maintained easily. What does it mean
to say the web has failed? Over time the number of people using the system will
dramatically grow and customer demands will grow and change. So this website can
easily be rebuilt to fit the evolving customer demands and the newly arriving changes. So
it can be easily maintained and can grow to a better version.
Performance: -the performance of our website is measured in terms of load time and
number of requests handled. So it is fast in accepting inputs and displays the result as
well as requires small space.
Modifiability: -The system is can easily modify or change the given information.
Availability: -The system will be available for 24 hours to users with internet connection
2.4.3 System requirement

:-Our website requires software and hardware requirements. These are: -
A) Hardware requirement
 Flash 16 GB
 Laptop
 RAM size 4 GB or more
 Processor speed 2.5 GHZ or more
B) Software requirement
 Notepad ++
 XAMP Server
17
 EdrawMaxUML
 Mozilla Firefox, Baidu browser
 Microsoft office word 2016
2.5 Use case Diagram

A use case is a sequence of transactions performed by a system that yields an outwardly visible,
measurable result of value for a particular actor. A use case typically represents a major piece of
functionality that is complete from beginning to end. An actor represents whoever or whatever (person,
machine, or other) interacts with the system. The actor is not part of the system itself and represents
anyone or anything that must interact with the system.
System Use Case
Figure 1:Use Case diagram
18
System Use Case Description
Use case name Register
Participating Actor Customer
Description New Customer of the site is registered here.
Precondition The Customer must be new user
Flow of events 1. The customer wants to register

2. The customer click on registration button
3. The system displays a registration form
4. The customer enters all required inputs
5. The system validates the data entered
6. The customer clicks on Register button.
7. The system send data to validate
8. The systems establish connection
9. The system return msg
10. The system performs the query
12. The system displays successfully registered
message and login page.
13. The use case end
Alternate Course A: Invalid data entered.

A.5. The system displays error massage
A.6. The system asks to re-enter valid data
A.7. The use case end
19
Alternate Course B: If the customer already

registered
B.12. The system displays already registered message

B.13. The system displays login page
B.14. The use case end
Post condition The customer is registered.
Use case name Login
Participating Actor Customer, Administrator, Ware house employee
Description Only the registered users will login, it may be the

customer, Administrator or Ware house employee
Precondition The user have to be already register
Flow of events Basic Action:

1. The user wants to login
2. The user clicks on login button
3. The system displays a login form
4. The user enters user name and password
5.The system validates the data entered

6. The user clicks on Login button.
7. The system send data to validate based on
Bussness Rule 1
8. The system establish connection
10. The system performs the query
20
12. The system displays successfully logged in

message.
A.7. The use case resume to step 4
Alternate Course B: If the user is not having an
account
B.12. The system displays your user name and
password is incorrect
B.13. The use case resumes to step 4
Alternate Course C: If the user forgot password
C.12. The system displays your user name and
password is incorrect
C.13. The user must have to click on forgot password
button
C.14. The system asks to fill username and email
address
C.15. The customer clicks on Change button

C.16. The system sends the password to his/her email
account
C.17. The use case end
Post condition A user is logged into the system
21
Use case name Order product
Description The Customer Orders the products what he wants to

buy and it includes login before order
Precondition The customer must add an items before ordering

1. The customer wants to order products
2. The customer clicks on products button
3. The system displays product list form
4. The customer add an items to cart
5. The customer click on Order button based on
Business Rule 6
6. The system displays a login form
7. The customer enters user name and password
9. The customer clicks on Login button.
11. The systems establish connection
13. The system perform the query
14. The system return msg and display on cart page
15. The customer click on Order button
16. The system send data to the controller
17. The system check the customer Coupon account
18. The system Return msg
19. The system deduct from customer Coupon
account
21. The system execute save to order table
22

23. The system display successfully ordered products.
Alternate Course A: If the customer not added
products.
A.14. The system display your cart is empty massage
A.15. The system ask to add items
A.16. The customer click on product button
A.17. The system display product list page
A.18. The customer added an item to his/her cart
Alternate Course B: If the customer not has
enough money in coupon account.
B.18. The system display account not have enough
money massage
Alternate Course c: If the customer wants to

cancel order.
c.24. The customer clicks on cancel order button
based on Bissness Rule 2
c.25. The system cancel the customer ordered product
and add balance to customer
coupon account
D.27. The use case end
Post condition The customer get the product
Use case name Remove items from cart
23
Description The customer removes the product from the cart
Precondition The customer added a product to the cart.

1. The customer wants to remove an items from
his/her cart
2. The customer clicks on cart button
3. The system display customer cart with items
information.
4. The customer selects item to remove from the cart.
5. The customer clicks on the Remove item link.
6. The system asks the user for the confirmation.
7. The customer confirms the removal
8. The system removes the item from the customer
cart.
9. The system displays the products is removed
successfully
Alternate Course A: If The user not confirms to

remove the item
A7. The use case go to step 3.
Post condition The products is successfully removed
Use case name Add new product
Participating Actor Warehouse employee
24
Description The Warehouse employee creates the product

category list
Precondition The Warehouse employee must be logged in

1. The warehouse employee wants to add new
product based on Bissness Rule 4
2. The warehouse employee clicks on add new
product button.
3. The system displays add new product form
4. The warehouse employee fills all required inputs
6. The warehouse employee clicks on add button.
8. The system established connection
10. The system excute the query
12. The system displays successfully added message.

Alternate Course B: If the product already
available.
B.14. The system displays the product already
available message
B.15. The system displays add new product page
25
Post condition The category list of the product is created.
Use case name Update product
Participating Actor Warehouse employee
Description The Warehouse employee updates the product

category list
Precondition The Warehouse employee must be logged in

1. The warehouse employee wants to update product
based on Bissness Rule 4
2.The warehouse employee enter product code in the
search form
3. The warehouse employee clicks on search button.
4. The system send data
5. The system established 6. The system return msg
7. The systems execute the query
9. The system displays searched product .
10. The warehouse employee click on Edit button
11. The system display product information
12. The warehouse employee update the product
information
13.The system validate the data entry
14. The warehouse employee clicks on update link
button
15. The system send data
16. The system established connection
26
18. The system executes the query

20. The system display successfully updated msg
Post condition The category of the product is updated.
Use case name Delete Employee
Participating Actor Administrator
Description The Administrator wants to delete user
Precondition The Administrator is logged in
Flow of events Basic Course of Action:

1. The Administrator wants to delete employee
account based on Bissness Rule 5
2. The Administrator clicks on Delete Employee
button.
3. The system displays Employee page
4. The Administrator enter employee name in the
search form
5. The Administrator clicks on search button.
6. The system send data to fetch employee
7. The system displays searched employee.
8. The Administrator clicks on delete link button
9. The system asks for confirmation
27
10. The administrator confirms the deletion.

11. The system display successfully deleted account.
12. The use case end.
Alternate Course A: If the administrator enters in
correct Employee Name
A.7. The system displays there is no employee with
this name message
A.8. The system asks to re input the employee
information.
Alternate Course B: If the user is does not exist
B.7. The system display the employee is doesn’t exist
B.8. The system resume at step 3
Alternate Course C: If the administrator confirms
not to delete
B.10. The system resume at step 7
Post condition The employee is deleted
28
2.5.3Sequence Diagram
Diagrams model the dynamic aspects of a software system. The emphasis is on the “sequence” of messages
Rather than relationship between objects. A sequence diagram maps the flow of logic or flow of control with
in a usage scenario into a visual diagram enabling the software architect to both document and validate
the logic during the analysis and design stages. Sequence diagrams provide more detail and show the
Message exchanged among a set of objects over time. Sequence diagrams are good for showing the behavior
Sequences seen by users of a diagram show only the sequence of messages not their exact timing. Sequence
diagrams can show concurrent signals.
Figure 2: Sequence Diagram for login
29
Figure 3: Sequence Diagram for add new product
30
Figure 4: Sequence Diagram for registration
31
Figure 5: Sequence Diagram for update product
32
Figure 6: Sequence Diagram for send comment
Figure 7: Sequence Diagram for generate report
33
Figure 6: Sequence Diagram for view comment
34
Figure 9: Sequence Diagram for Order Product
35
Figure 10 : Sequence Diagram for Manage Account
36
Figure 11: Sequence Diagram for Payment
37
2.5.4 Activity diagram

Introduction
An Activity diagram is a type of flow chart with additional support for
parallel behavior.
This diagram explains overall flow of control.
Activity diagram is another important diagram in UML to describe
dynamic aspects of the system.
Activity diagram is basically a flow chart to represent the flow from
one activity to another activity
The activity can be described as an operation of the system.
The control flow is drawn from one operation to another. This flow
can be sequential, branched or concurrent. This distinction is
important for a distributed system.
The following diagrams show the internal behavior of our system
Figure11: Activity diagram for login.
38
Figure12 : Activity diagram for Customer registration
Figure 13: Activity diagram for update product
39
Figure 14: Activity diagram for Order Products
40
Figure 15: Activity diagram for generate report
41
Figure 16: Activity diagram for Give Comment
Figure 17: Activity diagram for Manage Account
42
Figure 18: Activity diagram for View Comment
Figure 19: Activity diagram for View item
43
Figure 20: Activity diagram for Manage Product
44
Figure 21: Activity diagram for purchase product
45
2.5.5. Class Diagram
Figure 22:Class Diagram
46
2.5.6 User interface prototype

User interface prototype is to indicate the surface that can be used by user and the system to
communicate to each other, but, not actual work area. Here the prototype of applicant registration
form and employee search detail is listed.
User interface prototype for administrator
47
User interface prototype for Employee Information
User interface prototype for Administrator Information
48
User interface prototype for Customer Information

Figure 7: User interface prototype
2.2.7 Identifying change cases

Change cases will used to describe potential modifications requirements to the system. To
describe the potential change to the existing requirements, indicate the likeliness of that change
occurring, and indicate the potential impact of that change The system is ready to change if the
organization has been open different branches and also if new material has been imported to the
camp, in this case the system is easily scalable and ready to be changed.
49
Chapter Three: System Design Document
3. Purpose and goals of design
3.1. INTRODUCTION
System design is the transformation of the analysis model into a system design model. That
takes into account the nonfunctional requirements and constraints described in the problem
statement and the requirements analysis document. It is used to show how the new system
should be implemented. In this phase the overall procedures, activities and methods of
execution during the implementation phase of the project are included. The following
subtopics are discussed in this phase. Subsystem decomposition, hardware/software
mapping, persistent data management and access control and security of the system. More
generally, System Design document specifies how the system should be realized. The design
part is very important so as to make the implementation very easy. The different types of the
system modeling techniques that are used for the implementation of the system such as
deployment and component modeling are show in detail.
3.2. Purpose of System Design

The main purpose of system design is to provide architecture design, design goals of the
system, detailed class design and database design for the system. It is the process of defining
and developing systems to satisfy specified requirements of the user. Design converts
functional models from analysis into models that represent the solution. This project is
designed in a manner that solves the problems of the organization by minimizing the work
load of the existing system and workers. It provides more efficient, reliable and time saving
system.
50
3.3. Design Goals

The design goals of a system are derived mainly from the non-functional requirement or from the
application domain. It helps us in identifying the qualities that the system is optimized to satisfy.
3.4 Class modeling Diagram

Diagrams are used to represent the structure of the system in terms of objects, their notes and
nature of relationship between classes. It shows the static features of the actors and do not
represent any particular processing. It is an abstraction of the real environment class of seller,
patron (user) and Administrator. The purpose of a class diagram is to depict the classes within a
model. In an object oriented application, classes have attributes (member variables), operations
(member functions) and relationships with other classes. The UML class diagram can depict all
these things quite easily
Figure 8:Class modeling Diagram
51
3.5. Current Software Architecture

The existing system of the shopping system of yemewodsh electronics system is manual
system and hence there is no Existing software architecture that will be considered. As a
result, we only describe the software architecture of the newly proposed system.
3.6. Proposed Software Architecture

Software architecture is structured into three layers by dotted lines. Each layer is an
abstraction of functionality. The layer on the bottom offers data management functionality to
the services layer. And the services layer offers functionality to several clients on the Internet.
Each layer is built onto the functionality of the next layer down the stack.
Figure 9: proposed software architectures
3.6.1. Subsystem Decomposition

Subsystem decompositions will help reduce the complexity of the system. The
subsystems can be considered as packages holding related classes/objects. These
subsystems are further decomposed into other subsystems. The major subsystems
identified in shopping System are Interface Subsystem, Registration Subsystem,
Account Mgt Subsystem, Stock Mgt Subsystem, Report Mgt. Subsystem, Data Mgt
52
Subsystem, and Request Mgt Subsystem. The subsystem decomposition and their
interactions are shown in the figure below and subsequently the subsystems are
described in detail under the respective subsections.
Figure 10: System decomposition

Interface subsystem
The interface subsystem is primarily responsible for interaction with the other
subsystems. It allows end users interact with the system. Also it used by the system to
interact with other systems. The interface subsystem includes the following classes.
53
 Registration management subsystem Interface: - This interface enables

authorized user interacts with registration subsystem.
 Report management subsystem Interface:-This interface enables authorized user
interacts with report subsystem.
 Stock management subsystem Interface:-This allows the user to interact with
manage stock subsystem.
 Account management subsystem Interface:-This is used to interface the manage
account subsystem
 Request management subsystem Interface:-this interface enable to authorized
user interact with request subsystem.
 Registration management subsystem:-This subsystem is responsible with
registration of shop and customer information.
 Data Management Subsystem Interface: This allows interfacing with the Data
Management Subsystem.
Figure 11: Subsystem- Interface
54
 Registration management subsystem

This subsystem is responsible with management of the Registration maintenance. And it
is made up of the following classes;
Shop Management: It is responsible with information registration, update and deletion
of a Shop.
Customer Management: It is responsible with information registration, update and
deletion of product.
Figure 12: Subsystem- Registration Management

 Request management subsystem
This subsystem is responsible with management of the Request maintenance. And it is made up
of the following classes;
Shop Reqst. Management: It is responsible with information Request, view of a Shop.
Customer Reqst . Management: It is responsible with information Request, view of customer.
55
Figure 13: Subsystem- Request Management

This subsystem is responsible with Account management. It is responsible with create, view, Update,
and delete Account
Figure 14: Subsystem-Account Management

Stock management subsystem
This subsystem is responsible with setup of product information registration
and Updates.
56
Figure 15: Subsystem- Stock Management

Data Management Subsystem
This is a subsystem responsible with data management tasks like storage, update and retrieval
requests triggered by the subsystems.
Data Storage: This class is responsible to handle persistent data storage activities.
Data Access: The actual data manipulation activity will be carried out though this class.
This class will serve all data entry and retrieval activities in the system
Message: Errors, warning and confirmation messaging activities related to data entry and
retrieval will be carried on this class.
57
Figure 16: Subsystem- Data Management

3.4.2. Component diagram
The component diagram helps to model the physical aspect of an object-oriented software
system. It illustrates the architectures of the software components and the dependences between
them. In the Unified Modeling Language, a component diagram depicts how components are
wired together to form larger components and or software systems. They are used to illustrate the
structure of arbitrarily complex systems. A component is something required to execute a
stereotype function. Examples of stereotypes in components include executable, documents,
database tables, files, and library files. Components are wired together by using an assembly
connector to connect the required interface of one component with the provided interface of
another component. This illustrates the service consumer - service provider relationship between
the two components.
58
Figure 17: Component Diagram

3.4. 3.Deployment diagram
Deployment diagram in the Unified Modeling Language models the physical deployment of artifacts on
nodes. To describe a web site, for example, a deployment diagram would show what hardware
components exist what software components run on each node and how the different pieces are
connected. Deployment modeling is used to show the hardware of the system, the software that is
installed in the hardware and also the middleware that is used to connect the disparate machines to one
and other. It also shows how the software and the hardware components work together. The
deployment diagram helps to model the physical aspect of an object-oriented software system. It
models the run-time configuration in a static view and visualizes the distribution of components in an
application. In most cases, it involves modeling the hardware configurations together with the software
components that lived on.
59
Figure 34: Deployment Diagram
60
3.4.4 Persistent Modeling/ Database Design

Persistent data management deals with how the persistent data i.e. file, database, etc. are stored
and managed and to outlives a single execution of the system. Database design is the process of
producing a detailed data model of a database. This data model contains all the needed logical and
physical design choices and physical storage parameters needed to generate a design in a data definition
language, which can then be used to create a database. A fully attributed data model contains detailed
attributes for each entity.
4.1. Table Structure

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

ENTITY NAME ATTRIBUTES DATA TYPE PRIMARY KEY FOREIGN KEY
NO
CUSTOMER cus_ID number(20) text(50) cus_ID user_name
2
fname text(50)
lname varchar(50)
user_name varchar(50)
phone number(20)
sex varchar(50)
age number(20)
state text(50)
city text(50) text(50)

kebele number(20)
house num number(20)
email varchar(50)
61
4.3 Database tables

NO
PRODUCTS ID number(20) ID product code
3
product type text(50)
product code varchar(50)
product name varchar(50)
price varchar(50)
product image varchar(50)
product_desc number(20)
quantity number(20)
4.4 Database tables

NO
Order order_id number(20) order_id product_code
4
cus_fname text(50) user_name
cus_lname text(50)
pro_code number(20)
order date date(20)
usernames varchar(50)
quantity number(20)
4.5 Database tables

NO
Employee emp_id number(20) emp_id usernames
5
fname text(50)
lame text(50)
usernames varchar(50)
user image varchar(50)
62
account type text(50)

phone number(20)
sex text(50)
age number(20)
3.4.5 Access control and security
Access control and security describes the user model of the system in terms of access matrix.
Upon start up, the system will display the user a login screen. Then the user will enter username
and password. After the user entered the username and password, the system verifies whether the
username and password entered are valid or not. If it is valid, the system will allow access to the
application based on the privilege to which the user belongs. Accordingly to the following access
control list is given for the system.
Actors operations
Produc
Contact Account Target Employee Email
t
Create() : Boolean     
Edit() : integer     
User Search():integer     
(Employee) View(): Boolean     
Assign(): Boolean 
Send(): Boolean  
Customer Respond(): Boolean  
(Contact) View (): Boolean  
Create() : Boolean 
System
Edit() : integer 
Admin
Search():integer 
(Employee)
View (): Boolean 
63
3.4.6.1 Boundary Conditions

Shopping system will have boundary conditions to start, shutdown, and handle failures of the
system. The system is not expected to be started and shutdown at all times rather the system
should be available all the time to prop up different services to the user. But when some
conditions like maintenance, security purpose and so on occur, the system will be shutdown and
will start up again. It also considers the need of starting the system when failure occurs.
The following tables show different boundary conditions of Shop System for Yemewodsh
electronics.
Boundary condition for start up the system
Name Start Shop System for Yemewodsh electronics

Actor Yemewodsh electronics administrator
Entry condition Shop System Apache server launch
Flow of events 1. The Yemewodsh electronics administrator launches the Apache server
2. The Yemewodsh electronics administrators start up the Shop System
for Yemewodsh electronics.
3. The system launches the MySQL server
Exit condition Exit when both the MySQL and Apache servers have been launched and
running.
Table 1 Boundary condition for start up the system
Boundary condition for Shutdown the system
Name Shut down Shop System for Yemewodsh electronics

Actor Yemewodsh electronics administrator
Entry condition Shop on working condition.
Flow of events 1. The system instigates the MySQL server
2. The system then also instigates the Apache server
3. The shop administrator clicks on shutdown the system
4. Confirmation for shut down displayed
64
5. Click on shut down the system.
Exit condition
The system shut down when all the connections are cancelled.
Special The administrator has the appropriate access level to shut down the
requirement system.
Table 2 Boundary condition for Shutdown the system
Boundary condition for database failure
Name Shop System for Yemewodsh electronics Database

Actor Shop System for Yemewodsh electronics administrator
Entry condition Shop System for Yemewodsh electronics system connected to the
database
Flow of events 1. The shop administrator starts up the shop system for
Yemewodsh electronics Connection between the system and
the database created and the system launches the MySQL
server
2. Access the database.
Exit condition The use case ends when connection ends.
If the database fails to launch, a diagnostic message is displayed and

Exceptions the appropriate error log is updated.
Special The shop administrator has the appropriate access level to access the
requirement database
Table 3 Boundary condition for database failure
65
3.4.6.2 Exception Handling

If either server fails to launch, a diagnostic message is displayed and the
Exceptions Appropriate error log is updated.
Special The shop administrator has appropriate access level to control Shop
requirement System for Yemewodsh electronics
Table 4 exception handling
3.5 USER Interface Design
The user interfaces and functions that will be available to the user depend on the User
Designation of the user and determined upon successful user logon of the user. The
following are some of screen mockups projected to be implemented.
Figure 18: User interface Design for Admin Login
66
3.2. Sample code for product form
Figure 36: User interface Design for comment
67
Figure 37: User Interface Design for Customer Registration
68
Reference
[1] (e-commerce and online shopping websites., Feb 6, 2019)
[2] (Amazon's Kindle Books online store, Sep 7, 2009 )
[3] (Flipkart Online Shopping India's favourite online shopping destination!

http://www.flipkart.com.)
[4] (online purchases using Flipkart.com, 2014)
[5] ( eBay Online Shopping 101, Jan 22, 2019)
[6] (eBay is an electronic storefront and online, Nov 16, 2018)
[7] (20+ Electronic Online Stores Deals, Aug 22, 2017 -)
Component Diagrams are used to diagram the high level components which you will be developing. For example , in my
application, i use COM to separate the modules. Each COM object runs in its own executable and is a modeled as a component
Component diagrams show the physical placement of the components in the system
Component Diagrams are used to diagram the high level components which you will be developing. For example , in my
application, i use COM to separate the modules. Each COM object runs in its own executable and is a modeled as a component
Deployment diagrams
are used to diagram the actual runtime modules which are required to complete the system. This
include your modules and any hardware / software which is required to complete your system.
show the interconnection of the hardware and software components
69
70
71
72
73

Mettu University Online Shopping

Загружено:

Сведения о документе

Авторское право

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Mettu University Online Shopping

Загружено:

Авторское право:

METTU UNIVERSITY

FACULITY OF ENGINEERING AND TECHNOLOGY

1. ZIYAD ALIYA …………………………………..RET/2173/08

Submitted to Department of Information Technology, Mettu University, Engineering and

OOSAD -Object Oriented System Analysis and Design

UML -Unified modeling language

MYSQL -structured query language

TVM -Time value of money

SDLC -system Development life cycle

PHP -Hyper text preprocessor

1.1. Background of the project

1.2 Background of shop

1.3 Existing System

1.4 statement of Problem

 Use more labor

 There is not written item descriptions and price

 It takes more time to process transaction

 There is no advertisement of product

 The shop open in a day 10 hours only

 The customer must be waiting until another customer is served.

1.5 Objectives of the project

1. 5.2 Specific Objectives

1.6 Project scope and limitation

1.6.1 Scope of the study

 Customer can add and remove items from the cart

 Display the expire date of the product

 Online ordering systems

 Register new customers

 Managing products (adding, deleting, and updating).

 Display ordered items information

1.6.2 Limitation of the project

1.7 Methodology of the project

1.7.1. Method for data collection

 Do you have an items list with their descriptions and price?

1.7.2 Methodology for system analysis and design

The main reason behind using OOA is:

 Objects are easier for people to understand

 Easy to plan and manage

1.7.3 System development Tools

1.7.3.1 Hardware tools

No Purpose Hardware name

2 Writing Something Pen

3 Writing Soft copy of Documentation Part Computer (Desktop or Laptop)

4 Printing Purpose Printer

6 File Transferring Flash 16 GB

6.3.2. Software tools

1 Code Writing Dreamweaver, Notepad++ Easy to use

Chrome, Spark browser pages

10 Documentation MS Word 2010 Easy to use

12 Modeling and Scheduling Edraw,Visio2013,Visio Easy to design diagrams

1.8 Feasibility Assessment

1.8.1 Economical feasibility

 It minimizes the work load of the worker

 Knowledge gain by project developer.

Hardware Quantity Price Total

Pen 3 6:00 18birr

1.8.3 Technical Feasibility

 Does the necessary technology exist to do what is suggested

1.8.4 Operational Feasibility

1.8.5 Schedule Feasibility

Gantt Chart Project Schedule

S.N Phase 2011 E.C

1.8.6 Legal/Contractual Feasibility

1.9 Significance of the project

 Safety way of data storage

 The society able to get fast and better service

1.10 Risk Assessment and management