print.pdf

i
TANA ONLINE ELECTRONIC SHOPPING
Acknowledgment
We would like to say thanks to almighty God for giving us power to complete this
documentation. Then we would like to thank our advisors (MSc) Amalework and instructor
Habtamu for them constructive opinion and willingness to participate in each part of our
project and his effective direction, assistance and guidance for the accomplishing of this project
documentation.
We also wish to thank the owner of Tana electronic shopping, who gave us the required
information about the Tana electronic shopping
Finally, we would like to thank the teaching staffs of computer science who have contributed
greatly to the success of this project documentation.

ii
Contents
Acknowledgment ....................................................................................................................... i
Abstract....................................................................................................................................iii
Acronyms, abbreviation and definition.................................................................................... ix
Chapter One: Introduction ........................................................................................................ 1
1.1. Background .................................................................................................................... 1
1.2. Existing system study..................................................................................................... 2
1.3. Statement of the Problem............................................................................................... 2
1.4. Feasibility Study............................................................................................................. 2
1.4.1 Operational Feasibility ............................................................................................. 2
1.4.2 Technical Feasibility................................................................................................. 3
1.4.3 Economic Feasibility................................................................................................ 3
1.4.4. Schedule feasibility.................................................................................................. 5
1.4.5. Legal feasibility....................................................................................................... 6
1.5. Objectives of the Project ................................................................................................ 6
1.5.1 General Objectives ................................................................................................... 6
1.5.2 Specific Objectives................................................................................................... 6
1.6. Scope and limitation....................................................................................................... 6
1.6.1. Scope ....................................................................................................................... 7
1.6.2. Limitation ................................................................................................................ 7
1.7. Significance of the Project ............................................................................................. 7
1.8. Methodology .................................................................................................................. 8
1.8.1. Data gathering mechanism ...................................................................................... 8
1.8.2. Design methodology................................................................................................ 9
1.8.3. Implementation methodology................................................................................ 10
1.8.4. Testing methodology............................................................................................. 11
Chapter Two: Requirement and Description .......................................................................... 13

iii
2. 1. Overview of the existing System ................................................................................ 13
2.1.1. Activities of the Existing System........................................................................... 13
2.1.2 .SWOT analysis...................................................................................................... 14
2.2. Overview of proposed system...................................................................................... 15
2.2.1. Functional Requirement ........................................................................................ 15
2.2.2. Non-functional Requirement ................................................................................. 16
2.2.3. System Requirement.............................................................................................. 16
2.2.4. User requirements.................................................................................................. 17
2.2.5 Business Rules........................................................................................................ 18
Chapter Three: System Modeling........................................................................................... 20
3.1. Use case modeling........................................................................................................ 20
3.1.1 Actor specification.................................................................................................. 20
3.1.2. Use Case Description............................................................................................. 22
3.2. Sequence Diagram........................................................................................................ 32
3.3. Class Diagram .............................................................................................................. 40
3.4. Activity Diagram.......................................................................................................... 41
Chapter Four: System Design ................................................................................................. 46
4.1. Design Goal.................................................................................................................. 46
4.2. System decomposition.................................................................................................. 46
4.3. System architecture ...................................................................................................... 47
4.4. Deployment diagram.................................................................................................... 48
4.5. Persistence data management....................................................................................... 49
4.6. Access control and security policy............................................................................... 50
4.7 user interface design...................................................................................................... 51
Chapter Five: Implementation ................................................................................................ 55
5.1. Tools............................................................................................................................. 55
5.1.1. Hard ware tools:- ................................................................................................... 55
5.1.2. Software tools:....................................................................................................... 55
5.2. Algorithm (used) .......................................................................................................... 56
5.3. Environments ............................................................................................................... 58
5.4. Sample code and sample output................................................................................... 58

iv
Chapter Six: Testing ............................................................................................................... 68
6.1. Unit testing................................................................................................................... 68
6.2. Integration testing......................................................................................................... 69
6.3. System testing .............................................................................................................. 70
6.4. Acceptance testing........................................................................................................ 70
Chapter Seven: Conclusion and Recommendation................................................................. 72
7.1. Conclusion.................................................................................................................... 72
7.2. Recommendation.......................................................................................................... 72
Reference ................................................................................................................................ 74
APPENDICES ........................................................................................................................ 75

i
List of Table
Table 1..Cost reduction............................................................................................................. 4
Table 2.Cost estimation ............................................................................................................ 5
Table 3.Time schedule to write our documentation.................................................................. 5
Table 4.user requirement 1 ..................................................................................................... 17
Table 5.use requirement 2....................................................................................................... 18
Table 6.user requirement 3 ..................................................................................................... 18
Table 7.System use case for login........................................................................................... 22
Table 8.use case for Register .................................................................................................. 23
Table 9.Use case description for generate report.................................................................... 24
Table 10.Use case description for view item.......................................................................... 25
Table 11.Use case description for update item
................................................................................................................................................. 26
Table 12.Use case description for order item ......................................................................... 27
Table 13.Use case description for add item............................................................................ 29
Table 14.Use case description for process comment.............................................................. 30
Table 15.Delete user ............................................................................................................... 31
Table 16.hardware Tools ........................................................................................................ 55
Table 17.For authentication of member login......................................................................... 69

vi
List of Figures
Figure 1.Use Case Diagram ----------------------------------------------------------------------------21
Figure 2. Sequence diagram for registration ---------------------------------------------------------34
Figure 3.Sequence diagram for generate report in the system-------------------------------------35
Figure 4. Sequence diagram for search item---------------------------------------------------------36
Figure 5. Sequence diagram for update item---------------------------------------------------------37
Figure 6.Sequence diagram for add item -------------------------------------------------------------38
Figure 7.Sequence diagram for order item -----------------------------------------------------------39
Figure 8.Sequence diagram for payment -------------------------------------------------------------40
Figure 9. Class diagram for the system --------------------------------------------------------------41
Figure 10.Activity diagram for login use case-------------------------------------------------------42
Figure 11.Activity Diagram for registration ---------------------------------------------------------43
Figure 12. Activity Diagram for register new customer -------------------------------------------44
Figure 13.Activity Diagram for payment-------------------------------------------------------------45
Figure 14.System decomposition----------------------------------------------------------------------47
Figure 15.System architecture -------------------------------------------------------------------------48
Figure 16. Deployment diagram ----------------------------------------------------------------------49
Figure 17.persistence diagram for e-shopping-------------------------------------------------------50
Figure 18.home of our system -------------------------------------------------------------------------51
Figure 19. Register form--------------------------------------------------------------------------------52
Figure 20.user interface for login----------------------------------------------------------------------53
Figure 21.for reading order form ----------------------------------------------------------------------54
Figure 22.Sample code for login ----------------------------------------------------------------------60
Figure 23.Sample output for login --------------------------------------------------------------------62
Figure 24.Sample output for order Item --------------------------------------------------------------65
Figure 25.Sample output for payment ----------------------------Error! Bookmark not defined.
Figure 26.Acceptance testing --------------------------------------------------------------------------71

iii
Abstract
This project concern about Tana electronic shopping system, Tana electronic shopping is found
Debre Tabor town. Today the overall activities of the Tana Electronic Shopping are under
taken manually. There repetitive and bulky activities like registering users, reservation,
updating records periodically, generating reports and difficult to integrate data from different
individual records, unable to interest different user request.
Based on the above problem this project is to design web based electronic shopping system
for tana organization and solving manual system problems and selling and buying electronics
online and commercial system in the organization.
The system that we designed works on User registration, electronic material reservation. It
allows the manager to generate report in easy way and enables customer’s online payment. The
administrator updates periodical information. The customer order Item online. The system
allow to the customers to search Item in a fast mechanism. Customers should be able to post
comments to the system about the items.
The system also allows the shipping assistant to view ordered products, check delivery, and
pending information, print receipt, and delete delivered information.

ix
Acronyms, abbreviation and definition
OOSD –Object Oriented System Development
CSS – Cascading Style Sheet
ER – Entity Relationship
E-commerce – Electronic Shopping
HTML – Hyper Text Markup Language
Id – Identification
Int – Integer
i.e. - That is to say
IP – Internet Programming
Sd –sequence diagram
MySQL – My Structured Query Language
PHP – PHP Hyper Text Preprocessor
REQ – Requirement
UC – Use Case
UML – Unified Modeling Language
OOA-object oriented analysis
OOD-object oriented design
SRS-System Requirement specification
SWOT-strength, weakness, opportunity and threats

1 | P a g e
Chapter One: Introduction
E-Commerce (electronic commerce) is the process of buying and selling products and
services over the Internet, utilizing technologies such as the Web, electronic data
interchange, e-mail, electronic fund transfers, and smart cards.
In recent years, e-commerce has exploded, and future trends indicate that more and more
businesses would connect themselves to the Internet. It is now becoming imperative for
some organizations to engage in e-commerce in order to remain competitive. And 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. Therefore the system
we planned to analyze in this project is about Tana Electronic Shopping management
system. We would tried the best way to make the complicated process of Tana Electronic
Shopping Management System as simple as possible using Structured & Modular
technique & Menu oriented interface. 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.1. Background
The establishment of Tana electronic shop was on 1999 E.C. It is located central part of
Debre Tabor City, which is 5km far away from the University. In 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 have 4 employees. And works from 2:00am-2:00pm in a day.
Nowadays the shopping is becoming popular and wider in service. But the way of serving
customers is tidy, difficult to manage and inefficient in different aspects due to its low
performance and poor ability to host many costumers at a time so a better solution is
required.

2 | P a g e
1.2. Existing system study
In our country the existing system works manually selling and buying of electronic are in
one place. When we want to buy the electronics we would search so many places to get it.
The problem in the existing system are listed below
 We can’t save our many and time
 It is limited in terms of space and budget
 No easy mechanism to make electronics shopping.
 We can’t buy at any time and any where
1.3. Statement of the Problem
The overall activities of the Tana Electronic Shopping are under taken manually. There
repetitive and bulky activities like registering users, reservation, updating records
periodically and generating reports. Due to these the store is facing a lot of problems that
need much improvement in order to assist in realizing organizational objectives. Also
another problem since a customer has to wait in line while another customer is being served.
Security is also one problem since there is no way of protecting the employees from being
cheated.
Customers also waste their time and energy when waiting for their turn to be served. And
also In Tana electronics shopping has currently many problems that initiated the group
members to develop this online system. These problems are uses manual system to process
data. For instance, different information about every situation of the electronics shopping
is done by paper, inflexible service since the shopping can't hold many customers at once
and it’s also hard to tell the items that are out of stock. View of this, the E-commerce
technology would be implemented to facilitate efficient services for customers by avoiding
those previously mentioned problems.
1.4. Feasibility Study
1.4.1 Operational Feasibility
It might not be possible to see fully operational system within the given resource and the
given limit of time for full Web development. However with great cooperation of the

3 | P a g e
project team and the help of the advisor system can address over all problems of the
current system those mentioned in the above. Also the system would operate on any
operating systems which have wampserver installed. Therefore the system would operate
in any kind of platforms .so system is operationally feasible. The proposed system would
be developed using user friendly interface that are easy to use and interact
1.4.2 Technical Feasibility
Usually new systems established in order to overcome the technical weakness of the
previous system. In the same way, this system is technically big enough to be applied
easily to the problem identified in the existing system. In addition; the both hardware and
software for this system are highly available and can be purchased with small cost. The
system is accessible by any computing device that permit internet access like any other
system from where ever and at any time. Therefore, it can be concluded that the system
is technically feasible.
1.4.3 Economic Feasibility
The new system is economically feasible some of the benefit and cost that are estimated
to be show in short and long run are:-
Benefits:
This feasible Can be expressed as tangible or intangible. Benefit that are considered as
money is called tangible benefit and benefit which resulted from the design of the new
system which cannot be considered as money called intangible benefit. The following are
tangible and intangible benefit.
Tangible benefits:
 Reduce cost for manual data management.
 Avoid delaying the products.
 Avoid cost for materials used for manual operation such as: pen, paper, space
needed to keep data record, and save data storage and time that we are induced or
brought in during manual system which are listed below. So our system reduced
those costs

4 | P a g e
Table 1..Cost reduction
Material cost for the current system
Item Quantity per
year
Unit price Total price per a year
Papers 3 packet 90.00 birr 270.00 birr
Pen 1 packet 3.50 birr 175.00 birr
Ticket and
receipt
144 packet 25.00 birr 3600.00 birr
Total material cost 4045.00 birr
Intangible benefits:
The following benefits are intangible benefits of the new system:
 Increased consistency and correctness.
 Enable to make fast communication.
 Improved processing speed.
 Improved up to dated data timely.
Cost:

5 | P a g e
We have spent some money to complete our project starting from the beginning up to the
end, the total costs we have paid was listed in the following table.
Table 2.Cost estimation
Tool name Quantity Price (birr) Total price
Flash USB 8GB 2 150.00 300.00
Pen 10 5.00 50.00
CD_ROM 2 27.00 54.00
Notebook 1 25.00 25
Transport 5 12.00 60
Printing paper 2 100.00 200
Total 589
1.4.4. Schedule feasibility
Schedule feasibility describe the time frame given for every activity and making
measurement whether activity Completion date can be met or not .The project team
members complete given activity on time without any delay.
Table 3.Time schedule to write our documentation
No. Task Name
2009 EC.
Nov15-17 NOV 2o – DCE 5 DCE 2o – Feb-2 feb25-june 17
1 Requirement
gathering

6 | P a g e
2 SRS
3 Design Document
4 Implementation and
testing
1.4.5. Legal feasibility
The system to be developed is not conflict with any government directives, because it gives
services for the people effectively and efficiently, all the stakeholders also agreed before
the system developed.
1.5. Objectives of the Project
1.5.1 General Objectives
The general objective of the project is to design web based electronic shopping system for
tana electronic shopping.
1.5.2 Specific Objectives
The specific objectives of the project are:
 Study the existing manual system:-Studying the business functional work flows
timing of critical process and procedures
 Identifying the problems under the current system:- identify what kinds of
problems that are faced by users in the current system
 Requirement analysis of the system: -Gathering all the requirements that have
direct relationship with the current system. And design of the new system.
 Designing the new system: -to solve the problems faced by the society easily and
quickly we need to design the online electronic testing.
 Testing and maintenance: - apply testing to see each modules independently and
integrate each other.
1.6. Scope and limitation

7 | P a g e
1.6.1. Scope
The scope of this project is clearly stated below as a result of what the system is expected
to perform. The proposed system would cover the following main tasks:
 This electronic shopping system is applicable for only tana organization and the
system controlled by the tana organization
 User registration
 Reserve electronic material
 Administration process
 Online payment
 Maintaining employee and user detail information
 Shopping cart
 Generate report( about sold electronic material and not sold )
 Customer ordered electronic material online
1.6.2. Limitation
Our system works only for some parts of Ethiopia.
It would have been of paramount importance if the entire e-shopping for Electronic of the
city under investing action was thoroughly analyzed however ,as it has restriction in
relation to time and finance ,this project is limited to e-shopping of the Electronic and
facilitating the system in line with addressing the problems that are stated understatement
of problem area. Our project is also May vulnerable to the following obstacles.
 The project may be difficult to apply at the end i.e. our society is most illiteracy
and most live in rural area.
 Most people are highly adapted on manual system.
1.7. Significance of the Project
Some of the significances of the project are:
 Enables the customer’s to get fast access and help to the organization in service
giving operations.

8 | P a g e
 Contributes in realizing organizational goals and objectives by supporting for
employees in up grading and updating their careers, which provides good store
service.
 Protect unauthorized access(by secured the data base , password encryption)
 Avoiding improper resource consumption
 Avoiding data loss because of improper data storage
1.8. Methodology
1.8.1. Data gathering mechanism
Data collection methodologies are methods used to collect different data from
different data sources (documents, users and organizations etc.)
The following are the data collection methods used for requirement elicitation
Primary data source
 Interview: We used interview as one of the major data collection
method. During interview our team got different necessary
information from the owner of Tana electronics shop.
 Direct observation: During this time we would directly enter in to the
internal activities of the tana electronic shopping to view what things are
done? And what are the limitations and strength of the shopping? The
essentiality of this method is that, to be confident with the data that we
would collect using an interview method because nowadays the reliability
of peoples decreases time to time
Secondary data source
 Internet: Internet aids us to see the available sample on the internet
and to download different types of tutorials which help us in doing the
project.

9 | P a g e
1.8.2. Design methodology
Object Oriented System Analysis and Design (OOSAD) Methodology is used, OOSD is
a system development paradigm which uses objects together with their interaction in
order to develop a system.
We used OOSAD because of the following important features:
 Increase reusability: - the object oriented provides opportunities for
reuse through the concepts of inheritance, polymorphism, encapsulation
and modularity.
 Increased extensibility: - when you to need to add new feature to the
system you only need to make changes in one part of the applicable class.
 Improved quality: - quality of our system must be on time, on budget and
meet our exceeded the expectation of the users of our system, improved
quality comes from increased participation of users in the system
development.
 Financial benefits:- reusability, extensibility and improved quality are all
the financial benefits, because they led to the business benefits of the
object- oriented from the point of view of the users, the real benefits are we
can built, system faster and cheaper
 Reduced maintenance cost: - Software organizations currently spend
significant resources maintain operating system so the object oriented
development methods helps us to overcome his problem.
 Managed complexity:-The object-oriented methods solve software
complexity in the following way, design your software the expectation that
it would modified and being able to respond quickly when your
environment changed.
In our project we use the two phase of objected oriented those are listed below in details
Object Oriented Analysis (OOA)

10 | P a g e
During this phase the team used to model the function of the system (use case modeling),
find and identify the business objects, organize the objects and identify the relationship
between them and finally model the behavior of the objects.
Object Oriented Design (OOD)
During this phase the team uses rational rose software to refine the use case model, and to
reflect the implantation environment, model object interactions and behavior that support
the use case scenario, and finally update object model to reflect the implementation
environment.
1.8.3. Implementation methodology
To develop the new system the team identified programming languages and database
management software as tools to be used and we have to use the following hard ware.
Hard ware requirement
The hardware requirements that we used for developing the system are:-
Laptop computer
digital camera
2.0 GHz CPU
 2 GB RAM
500 GB HDD
Software requirement
The programming languages we used is PHP. The reason we have selected this
programming language is we have seen how to develop web based system using PHP last
year in detail and it is easy for us.
Back End Design tool
PHP MYSQL, wampserver software data base system would be used in developing and
managing the database at back end.
Front End design tool

11 | P a g e
The user interface would be developed using HTML, CSS, JavaScript integrated
development environment since it easily designing the front end and connected in to data
base realizing rapid application development with constraints on the hand.
The tools we would use for document preparation or documentation:
 Microsoft office.
 Visual Paradigm for UML Enterprise Edition.
 E-draw max for UML
 Power point for presentation.
 MS-access for persistence design.
1.8.4. Testing methodology
The strategies and approaches used to test a particular product to ensure it is fit
for purpose.
Unit testing
The part of a testing methodology that is the testing of individual software modules or
components that makes up an application or system. So we would test each modules that
make up our system.
Integration testing
The Integration testing part of a testing methodology is the testing of the different
modules/components that have been successfully unit tested when integrated together to
perform specific tasks and activities (also known as scenario testing). So we would have
to make integration testing after unit testing.
System testing:-
The system testing part of a testing methodology involves testing the entire system for
errors and bugs. This test is carried out by interfacing the hardware and software

12 | P a g e
components of the entire system (that have been previously unit tested and integration
tested).

13 | P a g e
Chapter Two: Requirement and Description
2. 1. Overview of the existing System
It is necessary to know the existing system of a given organization to develop a better
system. Existing system currently performs different activities includes reservation,
maintain and update records, prepare report in manually. The shop is located at distance
about 5KM from the Debre Tabor University and to the central direction of the Debre Tabor
city. The target area of this proposed system is online electronic shopping system (i.e.
change manual system in to computerized system.
2.1.1. Activities of the Existing System
Input
The inputs in the electronics shopping are the items that are brought or purchased by the
owner of the tana electronic shop from Addis Ababa. The owner of this shop does not have
his own distributor to get its resources constantly, but he purchase from the place where
he can get the items that he want at proper, stable and appropriate cost.
Process:
 The new items would be registered on the manual file.
 Reporting all the activities that are done to the manager
Output:
The main output of this shopping is making the items ready to the customers of Debre tabor
societies or for all customers with clear and fair price, including the summary of purchases.
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

14 | P a g e
 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 seller
3. Customers come with the following activities:-
 Ask information
 Order item as they want
 Asking price of the item
 Take items from the seller
 Pay the cost of item 2.1.2 .Problem of Existing System
2.1.2 .SWOT analysis
Weakness
The existing system has a weakness like:
 The numbers of employees needed to handle the customers are limited.
 It takes time to calculate price of each items and serve many customer at the same
time.
 It is also time consuming in identifying the individual prices of each goods.
Therefore these stated problems make the performance of the existing system
unsatisfactory.
Regarding to the information, the current system or the existing system has lack of the
information in terms of timeliness, accuracy and format.

15 | P a g e
Strength
The current system has three employees and one manager, the employee works
cooperatively with each other with good approach. Although strength of the existing system
stated below. Those are:
The way of attracting the customer towards the market with good approach: Most people’s
chose this electronics shop in case of they get good electronics with a good cost and with a
best performance so the customers are delighted.
Opportunities:
 Increase job opportunity for employees: the current system give job
opportunity for some employees.
Threats:
 Virus: there is some case which affects the proposed system with viruses
but not in current system.
2.2. Overview of proposed system
The system that the team is planning to develop, ecommerce system for electronic shopping
is a system that would provide the shopping with a modern system, which would improve
the problems of the current system by developing the new developed system. The team
intended to do this by computerizing the current system and making it readily available to
both users and employees alike.
2.2.1. Functional Requirement
These requirements which are the basic for the system or simply functional requirements
that the system must satisfy. The new computerized system is providing all ecommerce
related services and functionalities, like online selling of the product. These groups of
requirement stress functionality that the system should support for the user.
 User registration
 Electronic material registration.
 It would generate report in easy way.
 Online payment.
 The administrator updates periodical information.

16 | P a g e
 The customer order Item online.
 Customers should be able to post comments to the system about the items.
 Customers use a Shopping cart.
2.2.2. Non-functional Requirement
A Non-functional requirement defines the overall qualities or attributes of the resulting
system. It place restrictions on the system being developed, the development process, and
specify external constraints that the system must meet.
User Interface
The system has own functionality that needs interaction with users. The system provides
different categories of users of different level. The users of the system vary from novice to
experts. Apart from this, the system entertains different information types in different
formats. Thus to address the above requirement the interface shall be user friendly.
Hardware Considerations
The system should run on a pc with a dedicated server to contain the database and other
server components.
Security issues
This system have a mechanism to restrict some resources to unauthorized users. The system
requires the user to provide his identifications before allowing accessing a secure resource.
Performance
The performance of the system is reliable and the response time of the system would be
short.
Maintainability
The system must be easily maintainable. In order to accommodate future demands of
system users, the system should be easy to understand and maintain.
2.2.3. System Requirement
System requirements are the requirements for the system as a whole. In a system containing
software components, software requirements are derived from system requirements. PHP
language, The Unified Modeling Language (UML), and HTML and css codes.

17 | P a g e
2.2.4. User requirements
The software requirements document is a written statement of what the software would
do. What the software does is directly supposed by its users. When an external system
submits a request of a certain form, it gets a particular response. The main purpose of
requirements document is to serve as an agreement between the developers and the users
on what the application would do. Users are individuals that use the system or software in
its environment. User requirements are their verified needs for that system or software.
The user requirements in our system are listed below using table.
Table 4.user requirement 1
Requirement id REQ-1
Source Gust
Requirement The system shall allow gusts to sign up free account.
Description Anyone may sign up for a customer account if s/he is not a
member before.
Category Sign up
Priority High

18 | P a g e
Table 5.use requirement 2
Source Gust
Requirement The system shall accept user name, password and email address to signup.
Description The user must fill required information correctly.
Category Sign up
Priority High
Table 6.user requirement 3
Source Gust
Requirement The system shall confirm (validate) user name, email and password are
acceptable.
Description User name, password and email address must be unique and validated in the
system.
Category Sign up
Priority High
2.2.5 Business Rules
The business unit also implements its own business rule and regulation which are followed
to perform work in easier and best manner. The businesses control the sales i.e. whenever
the customer purchases any item. The business unit must provide the receipt for each item
that is sold to the customer. When an item is purchased, the employee should have to fill

19 | P a g e
all necessary information required from him on the receipt after that the original receipt
would be given to the customers and the copy of the original receipt is left for the business
unit and this receipt helps both the customers and the owner of the business unit for the
privacy purposes or else to certify either the customer or the owner would purchase with
an appropriate or exact price of the items or not because almost all items has some time
guaranties given by the business unit.
The customer can only pay in cash not using any other system. The customer and also the
seller have no full guarantee for fault item and delay payment.
A business rule is effectively and working principle or polices that we try to specify for
both the existing system and the new system must satisfy. The business rule is a principle
or a policy in which the proposed system works accordingly. It deals with access control
issues.
It often concerns to access control issues, working policies and principles of the
organization. The organization has the following principles in the existing system which
includes:
 It does not reach electronic devices to customers to their address.
 The organization does not functional on holiday.
Our proposed system includes the following working principles or rules:
 Business Rule1:Customer should have valid credit card number
 Business Rule2: the customer fills the form properly.
 Business Rule3: the system gives fast responses to the customer.
 Business Rule4: the system should work 24 hours and 7 days per a week.
 Business Rule5: the system helps to arrive the electronic devices to the customer
place.
 Business Rule6: the Shop should give services to the registered customer only.
 Business Rule7:do not try to registered again within the same user name

20 | P a g e
Chapter Three: System Modeling
This section consists of the modeling of the proposed system using object oriented
methodology by applying unified modeling language (UML).
All the activities performed by the actors (such as the customer, salesperson and the
administrator) are analyzed by using different modeling diagrams.
Model is an abstraction of the real world. It allows us to deal with the complexity current
in a real-world problem by focusing on the essential and interesting features of an
application.
This chapter mainly focuses on the following points:
 System use case modeling
 Use case documentation
 Sequence diagram
 Class diagram(conceptual modeling)
 Activity diagram
3.1. Use case modeling
The use case model describes the proposed functionality of the new system. A use case
represents a discreet unit of interaction between a user (human or machine)
And the system. A use case is a single unit of meaningful work.
3.1.1 Actor specification
Customer: - someone who buys product.
Administrator: -a special user of the system who can setup access right for other users.
Store manager: a user of the system who is responsible for managing the catalog of the
products.

21 | P a g e
Shipping assistant: performs login and view order item.
Bank: an external company that processes visa card transaction.
Figure 1.Use Case Diagram
Register

22 | P a g e
3.1.2. Use Case Description
A textual description of each use case process. The use case documentation needs the
List of Actors and List of user interface.
Table 7.System use case for login
Name: Login use case
Identifier: UC-001
Actors: user: (customer, manager and Administrator)
Description: use case to ensure security in system usage
Pre-condition: The user must have user name and password.
Post condition: User get access to the system according to their predefined
system privilege and finally he/she logout or turn off the page.
Basic Course of
Action:
1. User activates the system.
2. System response by displaying the login interfaces and
prompts the user for the user ID and password.
3. User fills his or her user ID and password and click login
button.
4. System verifies user ID and Password.
5. User authenticated and gets access to the system.
6. System displays its main window.
7. Use case ends.
Alternate
Course of Action:
(if user enters wrong user ID and / or password)
1. User is not authenticated and is denied access to the
system.

23 | P a g e
Table 8.use case for Register
2. System displays an incorrect user ID and password
message.
3. The system informs the user to reenter username and/or
password
4. The use case resumes at step 3 of flow of events.
5. Use case ends.
Name: Register
Identifier: UC-002
Actors: Customer
Description: Customers would be registered for membership.
Pre-condition: The customer should have bank account.
Basic Course of
Action:
Actor action System Action
step1. Browse the site.step2. The system displays home page.
Step3.Click on the registration page step4. The system displays
registration page
step5. Enter the required input. step6. The system checks the
validity of the input Data
step7. The system registers the user.
.

24 | P a g e
Table 9.Use case description for generate report
.
Alternate
Course of Action:
If the information provided is not valid
 The system displays error message
 The system prompts to re input the information.
If the customer already registered
 The system display already registered message.
Post condition The customer can login and order an item.
Name: generate report
Identifier: UC-003
Actors: Manager
Description: Use case to generate report.
Pre-condition: The manager he/she an employee and have managerial skill about
human resource and should have skill to integrate different
information.
Post condition: System has successfully shown the reports to the administrator or
printed the reports.

25 | P a g e
Table 10.Use case description for view item
Basic Course of
Action:
1. Manager can view the reports. Manager clicks the “View
report” button.
2. The system loads the sales data from database and
displays it as a report.
3. Managers can print these reports
4. Use case ends.
Alternate
Course of Action:
 When there is there no sale record in the database, “No
Sale Record Found” message would be displayed.
 When there is select Search report with respect to
specific time and date, the message “Invalid dates
Entered” would be displayed.
Name: view item
Identifier: UC-004
Actors: manager and administrator
Description: Use case to view item.
Pre-condition: Register, order item.
Post condition: View all item with full information.

26 | P a g e
Easy way for above table:
Use case name: view item
Identifier: UC04
Description: use case to view item.
Actor: manager and administrator
Precondition: register, order item.
Post condition: view all item with full information.
Basic course of action:
1 manager or administrator clicks the View button.
2 The system loads the item information from the data base.
3. Use case ends.
Table 11.Use case description for update item
Basic Course of
Action:
1. Manager or administrator clicks the View button.
2. The system loads the item information from the data base.
3. Use case ends.
Name: Update item
Identifier: UC-006
Actors: Administrator
Description: Use case to edit or update the existing item information.

27 | P a g e
Table 12.Use case description for order item
Pre-condition: Administrator he/she must be an employee and have a certificate
in DBMS.
Post condition: System updates the item information.
Basic Course of
Action:
1. Administrator selects item detail.
2. Administrator clicks the search button from item detail
interface.
3. Use displays the search form.
4. Administrator enters item id on the search forms and click
search.
5. System retrieves the item particulars.
6. Administrator edits the item particulars or information.
7. Administrator clicks update button.
8. Use case ends.
Alternate
Course of Action:
(if administrator enters wrong ID)
1. This ID is not authenticated and is not exist in the data base.
2. System displays an item is not exist message.
3. System enables administrator to try again.
Name: Order item
Identifier: UC-007

28 | P a g e
Actors: Customer
Description: Use case to order Item to browse from store collection.
Pre-
condition:
The customer must be a member.
Post
condition:
System display information about the item its holding.
Basic course of action:
Basic
Course of
Action:
1. Customer views product catalogue to select products.
2. Customer selects a product by clicking “Add to cart” button and enters
the quantity of the products in the cart or clicks the “Add to cart” button
as many times as the required quantity.
3. The system adds the products to the cart.
4. Now customer can view his selected products. To view the selected items,
the customer clicks the “View cart” button.
5. The system displays the selected products along with the aggregated total
at the end of the cart.
6. Customer can delete a product(s) from the cart. To delete product(s) from
the cart, the customer checks the checkboxes (given with each product)
of the product(s) to delete and clicks the “Remove”.
7. The system removes the product(s) from cart.
8. After selecting product(s), customer clicks the “Checkout” button to
complete his order.
9. The system asks the credit card information from customer.
10. Customer enters the credit card information to pay the bill and clicks the
“Pay” button.
11. The system deducts the total bill amount from the credit card amount.
12. Now the order is complete. The system shows an “Order ID” and
“Delivery Time” on the screen.
13. Customer receives an email of order details.

29 | P a g e
Table 13.Use case description for add item
Alternate
Course of
Action:
(user entered an order key word that doesn’t much in the system)
1. Customer orders a quantity of the product that is not available, “Sorry, The
item is
Not available” message would be displayed.
 Customer clicks “Checkout” button, when there is no item in the cart,
the message
“Your cart is empty” would be displayed
 When there is not enough money in the customer payment account, the
message
“Sorry, amount is too low.” would be displayed.
Name: Add item
Identifier: UC-008
Description: Use case to add item.
Pre-condition: Administrator wants to add item to the data base.
Post condition: System adds the item to the data base.
Basic Course of
Action:
1. Include login use case.
2. Administrator selects record link.
3. Administrator clicks the add button from displayed record
link.
4. System displays the add item form.
5. Administrators fill the form and upload the image of the
item.

30 | P a g e
Table 14.Use case description for process comment
6. Administrator clicks the add button.
7. Systems save the item information in data base.
8. End use case.
Name: Process comment
Identifier: UC-009
Actors: Administrator, Manager
Description: Use case to view and delete comment.
Pre-condition: View
Post condition: Systems See and delete the comment from data base.
Basic Course of
Action:
1. Manager or administrator clicks the View comment link.
2. The system loads the comment from the data base.
3. Manager or administrators view the comment.
4. Manager or administrator deletes the comment.
5. The system deletes the comment from data base.
6. Use case ends.

31 | P a g e
Table 15.Delete user
Name: Delete User’s
Identifier: UC-010
Description: This activity is performed when the administrator want to delete an existing user.
Pre-condition: The administrator is logged on to the system.
Basic Course of
Action:
Actor action System Action
step1. Administrator select delete user step2.Displays delete user
Account account home page.
Step3.administrator enters the step-4 The system display
Users the user details.
Step-5.Administrator deletes the step6.system asks for confirmation
Account.
step7. The administrator confirms step8system deletes the user’s account
The Deletion. And displays deleted successfully msg
Alternate
Course of Action:
If the user name is incorrect
 Re input the user name.

32 | P a g e
3.2. Sequence Diagram
A sequence diagram is a UML interaction diagram. The sequence diagram is used
primarily to show the interactions between objects in the sequential order that those
interactions occur.
A life line illustrates what is happening to an object in a chronological fashion.And also
Sequence diagram are used to show how objects interact in a given situation. They
illustrate the objects that participate in a use case and the messages that pass between
them over time for one use case. A sequence diagram is a dynamic model that shows the
explicit sequence of messages that are passed between objects in a defined interaction.
Post condition A user’s account would be deleted.

33 | P a g e
Figure 2.Sequence diagram for login to the system

34 | P a g e
Figure 2. Sequence diagram for registration

35 | P a g e
Figure 3.Sequence diagram for generate report in the system

36 | P a g e
Figure 4. Sequence diagram for search item

37 | P a g e
Figure 5. Sequence diagram for update item

38 | P a g e
Figure 6.Sequence diagram for add item

39 | P a g e
Figure 7.Sequence diagram for order item

40 | P a g e
Figure 8.Sequence diagram for payment
3.3. Class Diagram
Class 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 objects
and do not represent any particular processing.
Class diagram is representation of an object, template of which objects are created. It is
modeled as rectangle with three sections. Class have name and attributes that display full
information of described name and methods that returns value.

41 | P a g e
Figure 9. Class diagram for the system
3.4. Activity Diagram
Activity diagrams are graphical representations of workflows of stepwise activities and
actions with support for choice, iteration and concurrency. In the Unified Modeling
Language, activity diagrams can be used to describe the business and operational step-by-
step workflows of components in a system. An activity diagram shows the overall flow of
control and.
An activity diagram illustrates the dynamic nature of a system by modeling the flow of
control from activity to activity. 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.

42 | P a g e
Figure 10.Activity diagram for login use case

43 | P a g e
Figure 11.Activity Diagram for registration

44 | P a g e
Figure 12. Activity Diagram for register new customer

45 | P a g e
Figure 13.Activity Diagram for payment

46 | P a g e
Chapter Four: System Design
The purpose of designing is to show the direction how the web page is built and to obtain
clear and enough information needed to drive the actual implementation of web page. It is
based on understanding of the model the web page built on system design also focuses on
decomposing the system in to manageable parts. During system design we concentrate on
the process of data structures and software and hard ware components necessary to
implement it.
4.1. Design Goal
The objectives of designing are to model a system with high quality. Implementing of high
quality system depends on the nature of the design created by the designer .If one wants to
make changes to the system after it has been put in to operation depends on the quality of
the system design. So if the system is designed perfectly, it would be easy to make changes
to it.
The goal of the system design is to manage complexity by dividing the system in to
manageable pieces.
Some of the goals are listed below.
 Security: The system should be secured from unauthorized user.
 Modifiability: The system should be modifiability to modify different services
depending on the need of the institute.
 Flexibility: The system able to change to suit new condition or situation.
 Efficiency: The system must do what it is supposed to do efficiently without the
problem.
4.2. System decomposition
Decomposition refers to the process by which a complex problem or system is broken
down into parts that are easier to conceive, understand, program, and maintain. It results
large systems in to a set of loosely dependent parts which make up the system.
To reduce the complexity of the solution domain, we decompose a system into simpler
parts, called subsystems, which are made of a number of solution domain classes.

47 | P a g e
Figure 14.System decomposition
4.3. System architecture
The newly proposed software architecture of our system consists of three users interface
with their accessibility. MySQL is used for our data base .we retrieve information from
database and display from the form. Persistence is used for my database for securing the
data from external access.

48 | P a g e
Figure 15.System architecture
4.4. Deployment diagram
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.

49 | P a g e
Figure 16. Deployment diagram
4.5. Persistence data management
Persistence Diagram shows the relationship between the one entity to another entity of an
objects. The persistence Diagram increases the maintainability, extensibility and portability
of your application. Persistence Diagram also called data model or Entity relationship (ER)
models, are used to communicate the design of a database, usually a relational database, to
both users and other developers. Persistence are used the schema of database.

50 | P a g e
Figure 17.persistence diagram for e-shopping
4.6. Access control and security policy
Unauthenticated users are not allowed to edit any information that is displayed in each page
and also information that is stored in the web database. In addition to the one specified
above, DB-Administrator are obliged to come up with some account information (for
example, their user name and password) to get a required service from the tana electronic
shopping. The shop would have provision mechanism for those who have forgotten their
password. One way to showing who can access what is by using an access control matrix.
The following table depicts an actor who is involved in the scene, and the possible
privileges assigned to the actor. Many levels of security protect sensitive documents and
files from unauthorized viewers. Each user has a security access level and each document
has a sensitivity level. Depending upon the access level of the user, they would see only
the list of documents that is appropriate for their security access level. Generally, all users
have their own user names and passwords to control security access levels and document
sensitivity level.

51 | P a g e
4.7 user interface design
In this system users would be communicate with the system through the following user
interfaces.
Home page: -This form appears on the site in which the system deployed is opened and
contains some links which lead the user to other page according to his privilege.
Figure 18.home of our system

52 | P a g e
Figure 19. Register form

53 | P a g e
Figure 20.user interface for login
Order form:

54 | P a g e
Figure 21.for reading order form

55 | P a g e
Chapter Five: Implementation
Implementation refers to the Coding of the all documents gathered starting from
requirement analysis to Design phase. So now the team is in a position of converting all
documents gathered and designed into the code so that the system would be implemented
for the user to be used for the purpose it developed. To implement it the user must have a
server on which the system would be hosted because this system can run on intranet site
with connection available or on internet connection.
5.1. Tools
To develop the system we are going to use different hardware and software tools.
5.1.1. Hard ware tools:-
Table 16.hardware Tools
No. Material Material
name
specification
1. Laptop Hp RAM 4GB,
processor,
hard disk
2. Flash disk SanDisk 8GB
3. Cd RW/DVD 720MB
4. Printing Hp Laser
Printer
5.1.2. Software tools:
Software Tools used for developing the system:-
 Web Presentation:HTML, CSS ,PHP
 Client – side Scripting: JavaScript
 Browser: chrome/Mozilla/

56 | P a g e
 Operating System: Windows 8.1/2008.
 Adobe Dreamweaver css 5 or higher version
5.2. Algorithm (used)
Before writing any piece of computer code, you have to know what the program is
supposed to do. Going straight to coding can be very confusing. Before you write
one line of code in any language, it is a good idea to write algorithms in a simple.
Algorithm for Login
1. Function login (email, password)
2. If password length =0
3. Display error message “Please fill password and Account type”
4. Return
5. Pass=Retrieve Password
6. If password! =email
7. Display error message “email and password doesn’t match please Try Again”
8. Return
9. pass =Retrieve Password
10. If password ==email
11. Display members page
12. //end of the function login
Algorithm for register
1. Function register (customer)
2. If filed length =empty
3. Display error message “Please fill this filed ”
4. Return
5. account =Retrieve account information
6. If password! =confirm password
7. Display error message “Password does not match please Try Again”
8. Return

57 | P a g e
9. email =Retrieve email
10. If email! =xxxx@gmail/yahoo.com
11. Display error message “Error creating”
12. //end of the creating function
Algorithm for order item
1. Function order (member login)
2. If filed length =empty
3. Display error message “Please fill this filed”
4. Return
5. Pass=Retrieve Password
6. If password! =email
7. Display error message “email and password doesn’t match please Try Again”
8. Return
9. If email ==password
10. Display order page
11. Select product to buy
12. If product==0
13. Display “sold out”
14. Return
15. If product==product+1
16. Display “unavailable”
17. Return
18. If select==product
19. Display “add to cart”
20. If add to cart==0
21. Display “fill this field”
22. Return
23. Display agree with terms and agreement
24. If select! =terms and condition
25. Display “please agree with terms and condition”
26. Return
27. If select ==terms and condition

58 | P a g e
28. Go to delivery information
//end of the if function
5.3. Environments
When we are develop our system we use the following tools in the development
environment.
 Personal computer to be able to run the system.
 PHP MYSQL (wamp), software data base system would
be used in developing and managing the database.
 Web browser to run our system which is tana online
electronic system.
5.4. Sample code and sample output
Sample code
These are some of the sample codes that we have done it.
Sample code for register
<?php
if(isset($_POST['submitMain']) )
{
$fname=$_POST['fname'];
$date=$_POST['lname'];
$month=$_POST['gender'];
$year=$_POST['mail'];
$pass=$_POST['pass'];
$rpass=$_POST['rpass'];
$mo=$_POST['mobile'];
$cou=$_POST['cou'];
$cit=$_POST['city'];
$role=$_POST['role'];

59 | P a g e
if($pass==$rpass){
$query="INSERT INTO
user(Name,Lname,gender,email,password,re_typepassword,Mobile,country,city,status)";
$query.="VALUES
('{$fname}','{$date}','{$month}','{$year}','{$pass}','{$rpass}','{$mo}','{$cou}','{$cit}','{$
role}');";
$result=mysql_query($query);
if(!$result){
echo"<p class='wrong'> This E-Mail Is Ordey Existing!!!</p>";
}
else{
echo"<p class='success'> congratulations </p>";
echo'meta content="5;login.php" http-equiv="refresh"/>';
}}
else{
echo"<p class='wrong'> Password Not Match</p>";
echo'<meta content="5;singup.php" http-equiv="refresh" />';
}
mysql_close($conn);
}
?>

60 | P a g e
Sample output for register
Figure 22.Sample code for login
<?php
if(isset($_POST['submitMain']))
{
$user =$_POST['mail'];
$_SESSION['mail']=$_POST['mail'];
$password=$_POST['pass'];

61 | P a g e
$_SESSION['pass']=$_POST['pass'];
$query = "SELECT * FROM user WHERE email= '{$user}' AND password=
'{$password}';";
$result = mysql_query($query);
// TO check that at least one row was returned
$rowCheck = mysql_num_rows($result);
$row=mysql_fetch_array($result);
if($row['status']==1){
$_SESSION['SESS_MEMBER_ID']=$confirmation;
echo"<script>window.location='http://localhost/tanaonlineshopping/admin/product.php';<
/script>";
} else if($row['status']==2){
echo"<script>window.location='http://localhost/tanaonlineshopping/admin/manager/man
ager.php';</script>";
}
else if($row['status']==3){
echo"<script>window.location='http://localhost/tanaonlineshopping/admin/shop.php';</sc
ript>";
}
else if($row['status']==4){
echo'<meta content="1;order.php" http-equiv="refresh" />';
}
else {

62 | P a g e
echo"<p class='wrong'>User Name & Password Not Match !!</p>";
echo'<meta content="5;login.php" http-equiv="refresh" />';
}}
mysql_close($conn);
?>
Figure 23.Sample output for login
Sample code for order Item
<?php
$result = mysql_query("SELECT * FROM products");
while($row=mysql_fetch_assoc($result))
{
echo '<a rel="facebox"
href="orderpage.php?product_id='.$row['product_id'].'&trnasnum='.$transnum.'">
<img src="images/upload/'.$row['product_photo'].'" title="'.$row['BrandName'].'"
width="110" height="110" class="pngfix" /></a>';

63 | P a g e
}
?>
<div id="orderlist">
<table width="80%" border="1" cellpadding="2" cellspacing="2" align=center>
<tr><td width="25"><div align="center"><strong ><font
color=black>Action</strong></div></td>
<td width="25"><div align="center"><strong ><font
color=black>Qty</strong></div></td>
<td width="100"><div align="left"><strong><font
color=black>Name</strong></div></td>
<td width="100"><div align="left"><strong><font
color=black>Price</strong></div></td><td width="25"><div
align="center"><strong><font color=black>Amount</strong></div></td>
</tr>
<?php
$i=1;
$result3 = mysql_query("SELECT * FROM orders WHERE confirmation='$transnum'");
while($row3 = mysql_fetch_array($result3))
{
echo '<tr>';
echo '<td><a href="deleteorder.php?id='.$row3['id'].'" class="delbutton" ><img
src="images1/delete.png" title="Click To Delete"
onclick="isdelete();"></img></a></td>';
echo '<td><div align="center">'.$row3['qty'].'</div></td>';
echo '<td>'.$row3['product'].'</td>';
echo '<td>'.$row3['price'].'</td>';
echo '<td><div align="center">'.$row3['total'].'</div></td>';

64 | P a g e
echo '</tr>';
}
?><tr>
<td colspan="4"><div align="right"><span style="color:black; font-size:13px; font-
weight:bold; font-family:Arial, Helvetica, sans-serif;">Total </span></div></td>
<td><div align="center">
<?php
$result5 = mysql_query("SELECT sum(total) FROM orders WHERE
confirmation='$transnum'");
{
echo $row5['sum(total)'];
$sfdddsdsd=$row5['sum(total)'];
}
?>
Sample output for order Item

65 | P a g e
Figure 24.Sample output for order Item
Sample output for payment
<?php
$x=1;
If (isset ($_POST ['submitMain'])) {
$transnum=$_POST['transnum'];
$na=$_POST['fname'];
$bank=$_POST['lname'];
$tra=$_POST ['transfer'];
$a=$_POST ['account'];
$amount=$_POST ['price'];
$card=$_POST ['secu'];
$query = "SELECT * FROM bank where account number= '{$a}' AND fname='{$na}'
AND security='{$card}';";

66 | P a g e
$result_set=mysql_query ($query,$conn1);
$count=mysql_num_rows ($result_set);
If (! $result_set) {
die ("query is failed”. Mysql_error ());
}
If ($count==0)
{
$del = mysql_query ("DELETE from reservation WHERE confirmation='$transnum'",
$conn2) or die (mysql_error ());
$dl = mysql_query ("DELETE from orders WHERE confirmation='$transnum'",$conn2)
or die(mysql_error());
echo '<div align="center"><strong><font color="#FF0000">You Have No Account On
This Branch!!!</font></Strong></div>';
}
else{
if(mysql_num_rows($result_set))
{$result ="SELECT * FROM bank where accountnumber= '{$a}' AND
security='{$card}';";
$re=mysql_query($result,$conn1);
while($row = mysql_fetch_array($re))
{
if($row['amountbirr']<=$amount){
$del = mysql_query("DELETE from reservation WHERE
confirmation='$transnum'",$conn2) or die(mysql_error());
$de = mysql_query("DELETE from orders WHERE confirmation='$transnum'",$conn2)
or die(mysql_error());

67 | P a g e
echo'<strong><center><font color="#FF0000">Your account balance is
low</font></center></Strong>';
} else{
$value = mysql_query("UPDATE bank set amountbirr='{$row['amountbirr']}'-
'{$amount}' where accountnumber= '{$a}';",$conn1);
echo "<script>window.location='print.php?id=$transnum';</script>";
if($x==1) {
$query1 = "SELECT * FROM bank where fname= '{$tra}';";
$result_set=mysql_query($query1,$conn1);
if(!$result_set){
die("query is failed".mysql_error());
}
if(mysql_num_rows($result_set)>0)
{
$result1 = mysql_query("SELECT * FROM bank where fname= '{$tra}';",$conn1);
{
$value = mysql_query("UPDATE bank set
amountbirr='{$row1['amountbirr']}'+'{$amount}' where fname= '{$tra}';",$conn1);
} }}}}}
else { echo'<strong><center><font color="#FF0000">Please Try
Aging!!</font></center></Strong>';
} }
mysql_close($conn1);mysql_close($conn2);}?>
Sample output for payment

68 | P a g e
Chapter Six: Testing
Testing a program consists of providing the program with a set of test inputs (or test
cases) and observing if the program behaves as expected. If the program fails to behave as
expected, then the conditions under which failure occurs are noted for later debugging
and correction.
Testing plays a vital role in the success of the system. System testing makes a logical
assumption that if all parts of the system are correct and successfully achieved. Once
program code has been developed, testing begins.
The testing process focuses on the logical internals of the software, ensuring that all
statements have been tested, and on the functional externals, that is conducted tests to
uncover errors and ensure that defined input would produce actual results that agree with
required results.
Conducting various tests to ensure that the information system delivers what is expected
of it. In order to deliver what is expected to our system we have taken different testing
methodology.
Testing is potentially endless. We cannot test till all the defects are unearthed and removed
it is simply impossible.
At some point, we have to stop testing and ship the system.
Some types of testing are:
 Unit test
 Integration test
 System testing
 Acceptance testing and etc.
6.1. Unit testing

69 | P a g e
Unit testing is a software verification and validation method in which a programmer tests
if individual units of source code are fit for use. During the implementation of the system
each module of the system was tested separately to uncover errors within its boundaries.
Unit testing is a level of software testing where individual units/ components of a
software are tested. The purpose is to validate that each unit of the software performs as
designed, so we tested login, customer registration, and other entire forms by using this
testing method.
Examples for unit testing
Table 17.For authentication of member login
Unit test=authentication of member login
Assumption =login to the appropriate page
Test data=email, password(empty,valid,invalid)
Steps to be executed Test data Expected
result
Empty email, password email=” ”,,password=” “ Please fill out
the field
Valid email, invalid password email=mail and Password=12 Please enter
valid password
Valid username and password Username=user
password=1234
Open member
page
6.2. Integration testing

70 | P a g e
The Integration testing part of a testing methodology is the testing of the different
modules/components that have been successfully unit tested when integrated together to
perform specific tasks and activities (also known as scenario testing). After we test each
unit of the proposed system we would perform an integration test to check whether
the system meets all the functional requirements. When we are integrating each
modules it meets required tasks. For instance when we are testing a member login and
order page they integrated and perform the expected requirements.
6.3. System testing
System test insures that the entire integrated software system meets requirements. It tests
a configuration to insure known and predictable results. System testing is based on
process description and flows, emphasizing pre-driven process links and integration
points. In system testing is not about checking the individual parts of design, but about
checking the system as a whole. In effect it is one giant component. System testing
insures the features of functional and non-functional requirements and the specifications.
6.4. Acceptance testing
Acceptance testing is a testing technique performed to determine whether or not the
software system has met the requirement specifications .It is formal testing with respect to
user needs, requirements, and business processes conducted to determine whether or not a
system satisfies the acceptance criteria and to enable the user, customers or other authorized
entity to determine whether or not to accept the system. The client satisfying all the
requirements specified by them has also developed the software within the time limitation
specified. A demonstration has been given to the client and the end-user giving some of
operational features. Where product being delivered to customer and then customer execute
the acceptance test see whether the expectation of the functionality meet or fulfill user
requirements. Here is the general diagram of Acceptance testing.

71 | P a g e
Figure 25.Acceptance testing
Alpha: - As the team we test our implemented code before releasing to the tana
organization by using two phases.
 First phase that we follow as the developer we debug by using our wampserver and
different browser.
 In the second phase we follow the methods that is asking information and technology
staff and computer science staffs for additional testing.
Beta: - We conducted some users to ensure whether or not accept our implemented system.

72 | P a g e
Chapter Seven: Conclusion and Recommendation
7.1. Conclusion
We have developed web based electronic shopping system to tana organization that enables
them to selling electronics online.
This is a system development project involves two phases:-
The first phase deals with the analysis phase of the life cycle, and the next phase addresses
the Design phase. As the end of the first phase, we need to review that we have covered in
accordance with what we have planned at the beginning.
We began our work by identifying the significance of web based system for the tana
electronic shopping and the overall techniques to be used in the development process. This
involved defining the system development methodology, identifying process, cost
requirements, and setting the deliverable and scheduled for the project. The business area
Analysis helps the team to truly understand the major functional areas and processes of the
system. Through this we evaluate the existing system weakness and strength. After that, we
performed requirements elicitation to discover user and system requirements.
This phase consisted of drawing the functional as well as non-functional requirements of
the system. Then we have undertaken a major phase in system development process: object
oriented Analysis. Here, we tried to model the new system we proposed using UML
diagrams: Use case, sequence, and activity and class diagrams. Also, we designed the new
system user interface prototype.
7.2. Recommendation
The system that we are trying to develop is not a fully electronics shopping system. Because
card, tax and functional of other banking system of the store are not integrated in the system.
This is mainly due to different challenges such as time the like. But by the cooperation of
all the group members and an advisor, the team is now able to reach to this proposed result.

73 | P a g e
Finally: - we suggest the following features need to be incorporated in any further revision
and extension attempt.
 Not only functional for in commercial bank of Ethiopia but also apply other banking
system like awash bank, Dashen bank, Abay bank, Abyssinia bank etc. for the
future.
 Integration with other section of the system.
 The system should develop the card payment system for the future.
- .

74 | P a g e
Reference
1. Ambler, Scott (2001) The Object primer: The application Developers Guide to
Object Oriented and the UML.2nd
rev. Ed England: The Cambridge University
Press.
2. Bruegge, Bernd (2000) Object oriented Soft ware Engineering Conquering
Complex and Changing System. Upper Saddle River: Prentice Hall.
3. On the w3 school,1000 project.com and some web sites.

75 | P a g e
APPENDICES
Appendix
Questioner
Q1. What are the objectives of your organization?
Q2. How does your current system work?
A. Is it manual?
B. is it computerized?
C. is it semi-automated?
Q3. How you make relationship with the customer?
Q4.What is the procedures or steps when customers get service of the organization?
Q5.What qualifications are expected from a customer who wants to register to the system?
Q6.What are the problem that you get when the organization use the existed system?
Q7. How payment is done?

print.pdf

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to print.pdf

Similar to print.pdf (20)

Recently uploaded

Recently uploaded (20)

print.pdf