Online Mobile Shopping

BS Software Engineering
Session 2012-2016

Supervised by:
Engr, Fawad Ghafoor

Submitted by:
Numan Yousaf
Roll no:121105
BSSE

Department of Computer and Software Technology

University of swat

1
 Online Mobile Shopping

Approval sheet
University of swat
External Examiner:

Signature:

Name:

Designation:

Internal supervisor:

Signature:

Name:

Designation:

University of swat
Session 2012-2016

2
 Dedication

My parents who shaped my life and made me what i am today, my teachers who have been my
source of inspiration, my siblings and friends who support and encourage me in my endeavors,
and to the greatest person (saww) who brightened the world with the light of his wisdom and
knowledge.

3
 Acknowledgement
In the name of ALLAH, the most merciful who created the universe and wisdom the search
for secrets. We are thankful to him who has given us courage and patience to complete this project.
We are further deeply grateful to our Advisor Engr. Fawad Ghafoor (Lecturer in Software
engineering department in UOS) for his well-coordinated guidance, advice, inspiration and help
in the completion of our satisfactory duty embodied in this project.
Our parents, brothers, sisters‟ relatives and all the family members whose cooperation and
patience for our study at BS level as well as their prayers for our success in all activities related to
knowledge and project throughout our life also deserves acknowledgements and thanks.
Finally, we will always respect the endless patience displayed by our parents who
supported us morally and financially throughout our studies and in every walk of life.

4
5
 Table of Contents
Dedication ....................................................................................................................................... 3
Acknowledgement .......................................................................................................................... 4
Table of Figures .............................................................................................................................. 8
Table of Tables ............................................................................................................................... 8
Chapter 1. Introduction ............................................................................................................... 9
1.1 Purpose of the project ....................................................................................................... 9
1.2 Project Objectives ............................................................................................................ 9
1.3 Project Benefits .............................................................................................................. 10
Chapter 2 Software Project Plan ................................................................................................. 11
2.1 Overview ........................................................................................................................ 11
2.2 Software Process Model ................................................................................................. 11
2.2.1 Incremental Model ...................................................................................................... 11
2.3 Project responsibilities ................................................................................................... 12
2.4 Work Break Down Structure .......................................................................................... 13
Chapter 3 Risk Management Plan ............................................................................................... 14
3.1 Introduction .................................................................................................................... 14
3.2 Purpose ........................................................................................................................... 14
3.3 Risk List ............................................................................................................................... 14
Chapter 4 Requirement Analysis and Specification ................................................................... 16
4.1 Introduction .................................................................................................................... 16
4.2 Goals of the project ........................................................................................................ 16
4.3 Requirements .................................................................................................................. 16
4.3.1 Non Functional Requirements .................................................................................... 16
Chapter 5 Software Design ......................................................................................................... 19
5.1 Introduction .................................................................................................................... 19
5.2 Data Flow Model ............................................................................................................ 19
5.3 Use Case Diagram .......................................................................................................... 20
Chapter 6 Tools and Technology ................................................................................................ 22
6.1 Introduction .................................................................................................................... 22
6.1.1 Introduction to PHP: ................................................................................................... 22

6
 6.1.2 HTML............................................................................................................................ 23
6.1.3 Adobe Dreamweaver ..................................................................................................... 23
6.1.4 MYSQL ......................................................................................................................... 24
6.1.5 SQL Functions: ............................................................................................................. 24
6.1.6 Database: ....................................................................................................................... 24
Chapter 7 Testing ........................................................................................................................ 26
7.1 Testing Objective:................................................................................................................ 26
Test Cases:.............................................................................................................................. 28
Chapter 8 User Guide .................................................................................................................. 32
References ..................................................................................................................................... 35

7
 Table of Figures
Figure 1 Incremental Model .............................................................................................. 12
Figure 2 work break down structure .................................................................................. 13
Figure 3 Data Flow Diagram ............................................................................................. 19
Figure 4 Use Case Diagram ............................................................................................... 20
Figure 5 Home Page .......................................................................................................... 32
Figure 6 Downloading page ............................................................................................. 33
Figure 7 Purchasing page .................................................................................................. 33
Figure 8 Signup page ......................................................................................................... 34

Table of Tables
Table 1 Risk ................................................................................................................................. 15

8
Chapter 1. Introduction

The project entitled “Online Mobile Shopping” enables customer to buy mobiles or
accessories from anywhere through online. This application advertises some of the products
for shopping. To buy products, customer has to create an account. Those who does not have
an account, they can only view the available product. They can’t buy it. Once the customer has
created account, not only he can view the products, he can also add the product to the cart and
also he can place an order to buy those products. This application then generates bill for that
particular customer. After the confirmation, the customer has to enter his credit card details to
buy those products.

1.1 Purpose of the project

The projects are designed to achieve specific targets define in terms of aims, tasks or a
purpose. The nature and size of the project depends upon complexity of the task, realization of the
aim and scope of the purpose any organization wants to achieve, in short a project has to be aimed
for achieving certain task in a given time frame.

1.2 Project Objectives

The main objective of this section is to provide an overview of how requirements specified
during the requirement phase and transferred in to an executable program. It shows some key
features the system works and provides some output snapshots.

 Helping the customer to search his specific MOBILE with a robust search tool.
 Online booking of Mobiles with the delivery status notification system.
 Providing Secured Environment for secured data access wherever necessary.
 Retrieval of data from database using easy buttons, links and interfaces in a very fast and
efficient manner.
 On-line updating of all types of data. Updating Data using web based interfaces and with the
help of buttons & links in an easy & convenient way.

Developing a viable candidate system that fulfills the following requirements: -

 Faster and accurate information retrieval.
 Easy registration.
 Login dependent information retrieval and updating.
 Correct and consistent maintenance of data and its
quick retrieval.
 Minimizing the page download time and hence less Investment.
 Improving the switches button and hyperlink so that the candidate shall
find all the queries they need at first sight.

9
  Maintaining the fast download of the page by using the flavors of cookies.
 Smooth transition and easy access to the pages not requiring much training
to the end user.

The overall objective of the system is to bring the MOBILE sellers and purchasers round the globe
closer to each other so that one can have the perfect buy.

1.3 Project Benefits

 The system is consistent.

 It provides a user-friendly environment.
 Searching any particular mobile phone is easier than manual system.
 The chances of data damage are very less and if it happens then the recovery of data is
possible by using any one of the multiple available recovery tools.
 The user will register him in the website.
 After registering himself he can search any mobile phone that he wants to buy.
 The user can also search other mobile phones at the same time within a short interval of
time.
 The user can also know the price of mobile phone and availability at the same time.
 There is no threat of any type of fraud.

1.4 Project Features

1. Secure registration and profile management facilities for Customers.
2. Browsing through the e-Mall to see the items that are there in each category of products.
3. Creating a Shopping cart so that customer can Shop N number of items and checkout finally
with the entire shopping cart
4. Customers should be able to mail the Shop about the items they would like to see in the
Shop
5. Secured mechanism for checking out from the Shop (Credit card verification mechanism).
Updates to customers about the Recent Items in the Shop.
6. Uploading Most Purchased Items in each category of products in the Shop.

10
Chapter 2 Software Project Plan

A document that describes the external requirement for any system. The requirement
analyst has to identify the requirements by talking to the clients and understanding and
responding to their needs.
The requirement phase translates the ideas of clients into a formal document. The inputs are
gathered from different resources. Input given by the clients may not be consistency. It might
change according to the modern requirements.

2.1 Overview

A project is an activity with specific goals which takes place over a finite period of time.”
A temporary organization that is needed to produce a unique and pre-defined outcome or result at
pre-specified time using pre-determined resources”. Projects are often implemented as mean f
achieving an organization’s strategic plan. Operations and projects differ primarily in that
operations are ongoing and repetitive while projects are temporary and unique. A project can thus
be defined in terms of its distinct characteristics that “A project is a temporary endeavor undertaken
to create a unique product or service”. For many organizations, projects are a mean to respond to
those requests that cannot be addressed within organization’s normal operational limits.

Projects are undertaken at all levels of organization. They may involve a single person or many
thousands. Their duration ranges from a few weeks to more than five years. Projects may involve
a single unit of one organization or many cross organizational boundaries, as in joint ventures and
partnering.

2.2 Software Process Model

A process model for software engineering is chosen based on the nature of the project and
application, the methods and tools to be used, and the controls and deliverables that are required.
We have used Linear Sequential Model for our system.

2.2.1 Incremental Model

This life cycle model involves multiple development cycles. The cycles are divided up into
smaller iterations. These iterations can be easily managed and go through a set of phases including
requirements, design, implementation and testing. A working version of the software is produced
during the first iteration, so working software is created early in the development process.

11
 Figure 1 Incremental Model

2.3 Project responsibilities

The undergoing project falls under INTERNET
TECHNOLOGIES & RDBMS (Relational Database Management System) category. Since the
project is mainly responsible for creation of the portal with the online database at backend. As we
know that, the Internet is huge client server architecture. The client is the web browser, it is
requesting a web based data, a file, or whatever, from some computer somewhere – anywhere – in
the world. The server is that computer that holds the information you want.PHP is a rich
programming framework for building web-based applications. It offers outstanding support for
both developers and administrators, providing improved ease-of-use, tool support, reliability,
scalability, administration and security.

12
2.4 Work Break Down Structure

Figure 2 work break down structure

13
Chapter 3 Risk Management Plan

3.1 Introduction
A risk management plan is a document that a project manager prepares to foresee
risks, estimate impacts, and define responses to issues. It also contains a risk assessment matrix.
A risk is "an uncertain event or condition that, if it occurs, has a positive or negative effect on a
project's objectives."

3.2 Purpose
A risk is an event or condition that, if it occurs, could have a positive or negative effect
on a project’s objectives. Risk Management is the process of identifying, assessing, responding
to, monitoring, and reporting risks. This Risk Management Plan defines how risks associated
with the Online Mobile Shopping project will be identified, analyzed, and managed. It outlines
how risk management activities will be performed, recorded, and monitored throughout the
lifecycle of the project.

3.3 Risk List

Project Risks:

Risk Probability Effects Risk planning strategy

The experience staff in the
team leave the project before
it is finish, or someone was ill
The methodology to solve the
problem can't work in a
proper manner.
Budget does not enough or
there is no budget.
HW requirement can't come
in the time.
Product Risks:
Risk Probability
Packages and Development high
tools does not enough.
low serious Use more than one staff for each
section, which might minimize
this risk. Also, manager tries to
increase salary for him.
high serious Must be study more than one
methodology to minimize this
risk.
low catastrophic Put a condition in the contract if
there any more expenses, the
funded side must be pay it. To
avoid this risk.
moderate serious See if there is any more time to
delay the project or not. If there is
no more time work by the team
computers, to minimize this risk.
Effects Risk planning strategy
serious Put a condition in the contract to
increase the time of project
delivery depends on the problem
occur. To avoid this risk.

14
Can't found the suitable high tolerable Programmer must have
components. professional programming skills
to write a new code, which
minimize this risk.
Business Risks:
Risk Probability Effects Risk planning strategy
Can't found the suitable place moderate tolerable Monitoring the work by E-mail
for meeting the team. every day. To avoid this risk.
Damage the electricity high serious There is a spare generator to
generator. avoid this risk.
Marketing the product low catastrophic Distribution of advertisements,
system. which minimize this risk.

Table 1 Risk

15
Chapter 4 Requirement Analysis and Specification

4.1 Introduction
The software requirement specifications (SRS) is a very important part of the software
building process, which describes the actual user level requirement from technical point of view.
I.e. what the user exactly wants? The objective of preparing the software requirement specification
is to represent the requirements of the software in such a manner that ultimately leads to successful
software implementation. It is the result of the analysis process of the software development. It
should contain all the data the software is going to process, the function it will provide, and the
behavior it will exhibit.
This Software Requirements Specifications (SRS) is defined in IEEE Std. 830-1993, IEEE
Recommended Practice for Software Requirements Specifications. the synopsis is prepared in the
way to fulfill almost all the points needed in S.R.S.

4.2 Goals of the project

The projects are designed to achieve specific targets define in terms of aims, tasks
or a purpose. The nature and size of the project depends upon complexity of the task, realization
of the aim and scope of the purpose any organization wants to achieve, in short a project has to
be aimed for achieving certain task in a given time frame.

4.3 Requirements
Requirements are the basic which are hardly need by the project .there are two
type of requirements
1. Non Functional Requirements
2. Functional Requirements
4.3.1 Non Functional Requirements

Efficiency Requirement:
When an online shopping implemented customer can purchase product in an efficient
manner.

Reliability Requirement:
The system should provide a reliable environment to both customers and owner.
All orders Should be reaching at the admin without any errors.

Usability Requirement:
The Online Mobile Shopping is designed for user friendly environment and ease of use.

16
Implementation Requirement:
Implementation of the system using css and html in front end with PHP as back end and it
will be used for database connectivity. And the database part is developed by mysql. Responsive
web designing is used for making the website compatible for any type of screen.

Delivery Requirement:
The whole system is expected to be delivered in four months of time with a weekly
evaluation by the project guide.

4.3.2 Functional Requirements

User
User Login:
Description of feature
This feature used by the user to login into system. A user must login with his user name
and password to the system after registration. If they are invalid, the user not allowed to enter the
system.

Functional requirement
- Username and password will be provided after user registration is confirmed.
- Password should be hidden from others while typing it in the field

Register New User:

Description of feature
A new user will have to register in the system by providing essential details in order to
view the products in the system. The admin must accept a new user by unblocking him.

Functional requirement
- System must be able to verify and validate information.
- The system must encrypt the password of the customer to provide security.

Purchasing An Item:

Description Of Feature
The user can add the desired product into his cart by clicking add to cart option on the
product. He can view his cart by clicking on the cart button. All products added by cart can be
viewed in the cart. User can remove an item from the cart by clicking remove. After confirming
the items in the cart the user can submit the cart by providing a delivery address. On successful
submitting the cart will become empty.

Functional requirement
- System must ensure that, only a registered customer can purchase items.

17
Admin
Manage User:

Description Of Feature
The administrator can add user, delete user, view user and block user.

Manage Moderator:
Description Of Feature
The administrator can add moderator, delete moderator, and block moderator and search
for a moderator.

Manage Products:
Description Of Feature
The administrator can add product, delete product and view product.

Manage Orders:
Description of Feature
The administrator can view orders and delete orders.

Functional requirements
-The system must identify the login of the admin.
-Admin account should be secured so that only owner of the shop can access that account

Moderator:
Description of features
A moderator is considered as a staff who can manage orders for the time being. As a future
update moderator may give facility to add and manage his own products. Moderators can reduce
the work load of admin. Now moderator has all the privilege of an admin having except managing
other moderators. He can manage users and manage products. He can also check the orders and
edit his profile.

Functional requirement
-The system must identify the login of a moderator.

18
Chapter 5 Software Design

5.1 Introduction

Software design is the process of implementing software solutions to one or more sets of
problems. One of the main components of software design is the software requirements analysis
(SRA). SRA is a part of the software development process that lists specifications used
in software engineering.

5.2 Data Flow Model

Data flow diagram is graphical representation of flow of data in an information
system. It is capable of depicting incoming data flow, outgoing data flow and stored data. The
DFD does not mention anything about how data flows through the system. Data flow diagram for
Online Mobile Shopping is shown below.

Figure 3 Data Flow Diagram

19
5.3 Use Case Diagram
A use case diagram at its simplest is a representation of a user's interaction with the
system that shows the relationship between the user and the different use cases in which the user
is involved. A use case diagram can identify the different types of users of a system and the
different use cases and will often be accompanied by other types of diagrams as well.

Figure 4 USE CASE DIAGRAM

The Basic Design Principles

The basic design principles considered during the interface design, are the
following
1. consistency
2. makes sense robustness
3. user friendly
4. flexibility and simplicity

20
1. Consistency
consistency means that throughout the system all type of information is consistent or
same. in our system interface is consistent

2. Make Sense Robustness

good user interface gives student clues about what to do next in a given situation. it is
meant to provide clear and obvious way for the user to get something done.

3.User Friendly
to make the system user friendly, right level and right kind of response should be given to
user against each user action with an input devise lock of proper feedback can be a big problem
when nothing appears to have happened.

4.Flexibility And Simplicity

it means that system should be so simple and flexible that user is able to concentrate on
getting the task at hand done with a minimum of distraction

21
Chapter 6 Tools and Technology

6.1 Introduction
The success of the project depends on the tools and technology. It has to be keeping in
mind that what technology and tools can lead our project to success in the start of the project. Our
project is feasible because all the resources it needed is available. i.e. the hardware and software
needed in the project implementation. Developing and designing can be categorized in the field of
tools. The tools and technology are the base of the project development.
Following is the list of major tools and technologies which we used in our project:

 Adobe Dreamweaver for coding.

 Php 5
 MySQL for Database connectivity.
 Adobe Photoshop CS 5.
 FTP (File Transfer Protocol).
 HTML (Hyper Text Markup Language).
 Java script.
 XAMPP Server
6.1.1 Introduction to PHP:
Php is a powerful language and the interpreter, whether included in a web server as a
module or executed as separate CGI (Common Gateway Interface) binary is able to access files,
execute commands and open network connections on server. These properties make anything run
on a web server insecure by default. PHP is designed specifically to be a more secure language for
CGI programs than Perl or C, and with correct selection of compile-time and runtime options, and
proper adding practices, it can give you exactly the combination of freedom and security and
security you need.

WHAT IS PHP?
 PHP stands for Peripheral Hypertext preprocessor.
 PHP is server side scripting language.
 PHP scripts are executed in the server.
 PHP supports many databases.
 PHP is open source software(OSS)
 PHP is free to download and use

PHP is a scripting language originally designed for producing dynamic web pages. It has evolved
to include a command line interface capability and can be used in standalone graphical
applications.

22
PHP is widely-used general-purpose scripting language that is especially suited for web
development and can be embedded into HTML. It generally runs on a web server, taking PHP
code as its input and output and creating web pages as output. It can be deployed on most web
servers and on almost every operating system and platform free of change. PHP is installed on
more than 20 million websites and 1 million web servers.

6.1.2 HTML
HTML an acronym for Hypertext Markup Language is the predominant markup language
for web. It provides a means to describe the structure of text-based information in a document by
denoting certain text s links, headings, paragraphs, lists etc. HTML is written in the form of “tags”.
That are surrounded by an angle brackets.HTML can also describe to degree, the
appearance and semantics of a document, and can include embedded scripting languages code such
as JavaScript that can affect the behavior of WEB browsers and other HTML processors.

WHAT IS HTML?
 HTML stands for Hyper Text Markup Language.
 Html is not a programming language.
 A markup language is a set of markup tags
 HTML uses markup tags to describe web pages
 HTML documents contain HTML tags and plain text
 HTML documents are also called web pages

6.1.3 Adobe Dreamweaver

Adobe Dreamweaver (formerly Macromedia Dreamweaver) is a proprietary web
development application developed by Adobe Systems. Dreamweaver was originally developed
by Macromedia, until Macromedia was acquired by Adobe Systems in 2005. Adobe Dreamweaver
is available for both Mac and Windows operating systems. Adobe Dreamweaver is a web design
and development application that provides a visual WYSIWYG editor (colloquially referred to as
the Design view) and a code editor with standard features such as syntax highlighting, code
completion, and code collapsing as well as more sophisticated features such as real-time syntax
checking and code introspection for generating code hints to assist the user in writing code.

The Design view facilitates rapid layout design and code generation as it allows users to quickly
create and manipulate the layout of HTML elements. Dreamweaver features an integrated browser
for previewing developed Webpages in the program's own preview pane in addition to allowing
content to be open in locally installed web browsers. It provides transfer and synchronization
features, the ability to find and replace lines of text or code by search terms or regular expressions
across the entire site, and a template feature that allows single-source update of shared code and
layout across entire sites without server-side includes or scripting. The behaviors panel also

23
enables use of basic JavaScript without any coding knowledge, and integration with Adobe's Spry
Ajax framework offers easy access to dynamically-generated content and interfaces.

6.1.4 MYSQL
MySQL, the most popular Open Source SQL database management system, is developed,
distributed, and supported by Oracle Corporation.
MySQL is a relational database management system. A relational database stores data in separate
tables rather than putting all the data in one big storeroom. This adds speed and flexibility. The
SQL part of “MySQL” stands for “Structured Query Language.” SQL is the most common
standardized language used to access databases and is defined by the ANSI/ISO SQL Standard.
The SQL standard has been evolving since 1986 and several versions exist. In this manual,
“SQL-92” refers to the standard released in 1992, “SQL: 1999” refers to the standard released in
1999, and “SQL: 2003” refers to the current version of the standard. We use the phrase “the SQL
standard” to mean the current version of the SQL Standard at any time.
MySQL software is Open Source. Open Source means that it is possible for anyone to use
and modify the software. Anybody can download the MySQL software from the Internet and use
it without paying anything. If you wish, you may study the source code and change it to suit your
needs. The MySQL software uses the GPL (GNU General Public License)to define what you may
and may not do with the software in different situations. If you feel uncomfortable with the GPL
or need to embed MySQL code into a commercial application, you can buy a commercially
licensed version from us.

6.1.5 SQL Functions:

 SQL can execute queries against a database
 SQL can retrieve data from a database
 SQL can insert records in a database
 SQL can update records in a database
 SQL can delete records from a database
 SQL create records in a database
 SQL can perform a lot of functions related to database.

6.1.6 Database:
A database is a collection of data which has been organized so that a computer program
can quickly select desired items. This could be something as straightforward as a list of names in
alphabetical order or an ascending list of numeric stock codes. The secret to the successful use of
database technology is the way in which data or information is structured to enable efficient
processing. Manual filing systems have drawbacks that make them inefficient. Take as an example
a simple card file index of customer information. This depends on consistent use to be effective.
For example, if the card always has the surname in the top left-hand corner then they are easy to
put in alphabetical order. However, if some cards have the postcode in this position instead, the

24
task becomes more complicated. Database tools and applications are designed to help you store
and manage data in a controlled and structured manner. Single-card file indexes can be simple, but
it is more complex to cross-reference information held in two separate files. The relational database
management system (RDBMS) makes use of common "keys" to tie related information together.
For example, a customer ID number could be used to identify an individual customer in a large list
of customers, or to link a customer with an order for specific goods.

25
Chapter 7 Testing

The application cannot overcome the requirement of the users when it is not fully
formally tested. So before it is deliver to the user it is strongly recommended that the software has
to be tested. The purpose of this module is to introduce the level of the testing for finding the errors
in the application. People use many kind of guidance to conduct systematic design testing.

7.1 Testing Objective:

Software testing is the process used to access the quality of a computer software. The main
intent of testing is to find errors in the program developed. The good test case is that one has a
high probability of finding errors in your program. The test of system is performing that the
software function appears to be working according to specifications that behavioral and
performance requirement appear to have been met. The test strategy identifies multiple test levels
which are going to be performed for the project. Activities at each level must be planned well in
advance and it has to be formally documented. Based on the individual plans only, the individual
test levels are carried out. Following are some approaches used for testing the developed software:

Unit Testing:
The unit testing mainly focuses on the smallest unit of software design, the software
component or module, so in the unit testing we have tested all form and the local data structures
examined to ensure that all the data stored temporarily maintain its integrity during all steps in
algorithm execution.

Example:
We implement the unit testing in our project while creating the different pages such as for
creating the index page we create the page in the Dreamweaver for checking this part we use unit
testing as it is the unit of project so this is a unit testing. So as creating the website we use different
pages and use the unit testing to check their performance.

Integrated Testing:
After unit testing, combined testing of the entire component is carried out; the main purpose
is to determine that all the form is correctly interacting with each other. The integrating testing is
a systematic technique for constructing the program structure while at the same time conducting
test to uncover error associated with interfacing. The objective is to take unit tested components
and build a program structure that has been dedicated by design. The integrated testing is necessary
to be performed to check all the system. Examples we use are different part of our project to check
our system whether they are working or not so for this purpose we use integrated testing.in this
type of testing we just combine different parts of the project and check for their performance.

26
System Testing:
As software is the only one element, of a large computer based system. Ultimately,
software is incorporated with other system elements i.e. hardware, software, people and all other
elements. So all of these elements have to be tested to check that the elements incorporated, work
properly. In this type of checking we test the requirements such as reliability and the hardware
requirements and also test the performance of our project. In this type of checking we check all
possible risks related to the software or project.

Test Case/Scenario for online purchasing.

 click the URL link for the online purchasing site.
 Register if not registered before, Enter user name, login id and password, Click ‘OK’ button
to submit.
 Enter your login id and password, if you are a.
 Validate the login id and password, if correct menu page will be opened.
 If not correct, display the error message “invalid login id or password” Re-enter your login
id and password.
 Click the item field and select the item.
 If available, display the cost and brand, else display ” item is unavailable”.
 click ‘YES’ to do online purchasing for the item else click ‘NO’.
 If ‘YES’ go to the payment type, else display the ‘EXIT’ page.
 Enter shipping address where all the fields are mandatory
 Enter billing address
 Enter message to be given to the consignee
 update shopping cart and proceed to payment
 click the payment type options and select the mode of payment.
 Fill the fields- account holder’s name, bank name, credit/debit card option, card detail,
price to be paid, email id etc.
 If invalid information is given, show error message ” please re-enter “
 If blank field is present, display message “all the fields are mandatory”.
 Click “SUBMIT” button.
 Display the successful submission message “successfully completed”.
 Press ‘EXIT’ button.
 Show the message ” successfully logged off”.

27
 Test Cases:

Test cases are derived to ensure that all statements in the program have been executed
at least once during testing and that all logical conditions have been executed.
Using White-Box testing methods, the software engineer can drive test cases that
 Guarantee that logical decisions on their true and false sides.
 Exercise all logical decisions on their true and false sides.
 Execute all loops at their boundaries and with in their operational bounds.
 Exercise internal data structure to assure their validity.
The test case specification for system testing has to be submitted for review before system
testing commences.

For conducting testing, a procedure was followed which consisted of preparing the test
cases and then executing them on the actual system. The test cases are shown below. The
testing of the entire application is done for all four modules: Registration page, Main
page, purchasing mobile and Display Result Page.

Test Case ID: 1

Test Case Name: System test
Test Case Title: Registration page all fields test
Description: It will check whether the system shows error or not if all the fields are not entered
by the user while registration
Steps:
1. Click on the Registration Page Shortcut.
2. In the registration page, leave at least one field blank while fill all the other fields.
3. Execute or press F8.

Expected Results: If even one field is left blank by the user then the system should show an
error that all the fields are necessary to be filled
Actual Result: It shows an error ‘You are required to fill all details’
Status(Pass/Fail): Pass

28
Test Case ID: 2
Test Case Name: System test
Test Case Title: Registration page special characters in email id test
Description: It checks that no special characters, except for one ‘@’, are added in the
email address field of the registration page.
Steps:
1. Click on the Registration Page Shortcut.
2. In the registration page email address field, enter special characters like
£, $, % etc.
3. Execute or press F8.
Expected Results: If special characters other than one single @ are entered, then
error should be displayed.
Actual Result: The error is displayed : ‘Do no fill unwanted characters’.
Status(Pass/Fai)l: Pass

Test Case ID: 3

Test Case Name: System test
Test Case Title: Model search bar
Description: To start search, the model of mobile is written in the search bar then the
search button is clicked by the user. This test will check that when search button is
clicked, whether the mobile model is displayed or there is an error
Steps:
1. Write model in the search bar
2. Click the ‘Search’ button.

Expected Results: When the search Button is clicked, the system should display the
mobile of the concerned model.
Actual Result: The mobile with the same concerned model is displayed
Status(Pass/Fail): Pass

29
 Test Case ID: 4
Test Case Name: System test
Test Case Title: Registration page special characters without email
Description: It checks that whether there are any special characters in the first or last
name fields in the registration page.
Steps:
1. Click on the Registration Page Shortcut.
2. In the registration page first or last name field, enter special characters like
£, $, % etc..
3. Execute or press F8.
Expected Results: If special characters are entered in the first name or last name fields,
then error should be displayed.
Actual Result: The error is displayed correctly.
Status(Pass/Fail): Pass

Test Case ID: 5

Test Case Name: System test
Test Case Title: Display Result test
Description: It will check that whether the result is displayed on the specific location
or not.
Steps:
1. Click on Display Result Shortcut.
2. Provide the information such as registration id, location for result and exam date.

Expected Results: The result should be displayed in the PDF format at the specified
location.
Actual Result: The result is displayed at the specified location.
Status(Pass/Fail): Pass

30
31
Chapter 8 User Guide

The Even though the internet is often referred to as a borderless market, there are still some
barriers to overcome. Online shopping is a different experience and you can make the shopping
creative over the internet as you get used to it. There can be lot of apprehensions about online
shopping when you get in to it for the first time. As you experience more and more of it those
apprehensions get disappeared slowly. Remember that if you stick to the basics, online shopping
become more enjoyable and easier than real-world shopping.

Home page:

Figure 5 Home Page

DESCRIPTION:

This is the home page which contains a slider, a news window and a flash image which contains
the use and manufacture of mobiles. The flash image shows the merits and demerits of mobile use
and manufacture.

32
DOWNLOAD PAGE

Figure 6 Downloading page

PURCHASE.PHP:

Figure 7 Purchasing page

33
DESCRIPTION:

This is the purchase page. In this page a user can search all categories of mobile and select the
mobile phone that he wants to purchase

SIGNUP PAGE:

Figure 8 Signup page

DESCRIPTION:
This is the login and sign up page. In this page a user can login and use the services of
website. Besides this it also contains sin up feature. A new user can register him in this page.

Payment Method:
Now a day’s cash on delivery method is used in our website. In future we will add the
PayPal and credit card method. As these methods will start work in Pakistan then we will also
implement these features in our website.

34
 References

In Proposed project we take help from following Books and Websites

Books Used:

Introduction to Software Engineering

Database Systems

Author Jeffrey Ullman and Jennifer Widom.

PHP Essentials, 2nd Edition Julie C. Meloni (Author) Publication Date: March 28, 2003

PHP/MySQL Programming for the Absolute Beginner Andy Harris (Author)

Publication Date: June 3, 2003

PHP and MySQL Web Development, Second Edition

Luke Welling, Laura Thomson (Authors)

Publication Date: February 12, 2003

Websites Used:

http://www.w3schools.com

http://www.ibm.com/developerworks/library/os-php-read

http://www.phpjunkyard.com

http://en.wikipedia.org/wiki/Hierarchical_organization

http://www.php.com

35