PHONE AND ACCESSORIES SHOPPING SYSTEM

SUBMITTED BY MWENDWA MUSYOKA

REGISTRATION NUMBER:19/06159

FACULTY OF COMPUTING AND INFORMATION TECHNOLOGY

FINAL REPORT FOR PHONE AND ACCESSORIES SHOPPING SYSTEM

COURSE: DBIT

UNIT: DBIT 506

SUPERVISOR:MRS WINNIE OKONG’O

THIS SOFTWARE DEVELOPMENT PROJECT HAS BEEN DEVELOPED IN PARTIAL FULFILMENT FOR THE
ACQUISITION OF DIPLOMA IN BUSINESS INFORMATION TECHNOLOGY
ACKNOWLEDGEMENT

I want to thank my supervisor, Mrs. Winnie Okong’o for his full support and guidance in the
documentation and system work with this project and appreciate the good feedback in accordance to
the consultation and most of all to thank the Almighty Lord for grace and gift of life in the successful
making of this project
DECLARATION

I solemnly declare that the software development project titled PHONE AND ACCESSORIES SHOPPING
SYSTEM
is based on my work carried out during the course of our study and research under the supervision of
MRS WINNIE OKONG’O

I assert the conclusions drawn as an outcome of my research and I further certify that

I)The work contained in the report is original and has been done under the supervisor

ii)I have followed the guidelines provided by the university

Signature…………… Date……………….
 ABSTRACT

The purpose of this project phone and accessories shopping system

is to develop a software that is user friendly, fast and affordable and interactive to the users concerning
mobile phones and the accessories .it deals with the collection of users details and. Traditionally it was
done manually so the system is computerized and its main function is to register and store users’ details
and brand details also the support staff as they can provide products to the users recommended by the
specific brands and to retrieve these details when required. The system output is to get the payment
receipt containing the warranty and product purchased. the system can be accessed using a username
and password in the log in page and accessed by an administrator. the admin can add data into the
database and data can be accessed and retrieved without difficulty, the data is also protected and is fast
and efficient for the user
Table of Contents
CHAPTER ONE..............................................................................................................................................7
1.INTRODUCTION....................................................................................................................................7
1.2BACKGROUND....................................................................................................................................7
1.3. PROBLEM STATEMENT.....................................................................................................................7
1.4. PROPOSED SOLUTION.......................................................................................................................7
1.5 MODULES..........................................................................................................................................7
3. OBJECTIVES..........................................................................................................................................8
4. JUSTIFICATION.....................................................................................................................................8
CHAPTER TWO.............................................................................................................................................9
2.1LITERATURE REVIEW...........................................................................................................................9
CHAPTER THREE..........................................................................................................................................9
3.1. METHODOLOGY................................................................................................................................9
3.1.1RESEARCH METHODOLOGY.........................................................................................................9
3.1.2DEVELOPMENT METHODOLOGY.................................................................................................9
4. HARDWARE REQUIREMENTS:............................................................................................................11
5. SOFTWARE REQUIREMENTS:.............................................................................................................11
SOFTWARE SPECIFICATION....................................................................................................................12
CONNECTIVITY:......................................................................................................................................13
LOCALIZATION:......................................................................................................................................13
CLIENTS AND TOOLS:.............................................................................................................................13
UML Design...........................................................................................................................................16
UML Diagram.....................................................................................................................................16
USE CASE DIAGRAM:..........................................................................................................................17
DATABASE DESCRIPTION.......................................................................................................................19
DEPLOYMEMT DIAGRAM.......................................................................................................................20
CHAPTER FIVE............................................................................................................................................21
SYSTEM IMPLEMENTATION...................................................................................................................21
5.1 Introduction:................................................................................................................................21
5.2 SAMPLE CODE..............................................................................................................................21
CHAPTER 6.................................................................................................................................................33
 6.1 INTRODUCTION TO SYSTEM TESTING:..........................................................................................33
UNIT TESTING........................................................................................................................................33
TYPE OF TEST.........................................................................................................................................33
MODULE TESTING..................................................................................................................................34
INTEGRATION TESTING..........................................................................................................................34
SYSTEM TESTING...................................................................................................................................35
VALIDATION TESTING............................................................................................................................35
USABILITY TESTING................................................................................................................................35
SECURITY TESTING.................................................................................................................................36
TESTING TOOLS AND ENVIRONMENT....................................................................................................36
CHAPTER 7.................................................................................................................................................37
SAMPLE SCREENSHOTS..........................................................................................................................37
7.0 DATABASE SAMPLES....................................................................................................................37
8.CONCLUSION:.........................................................................................................................................38
9. BIBLOGRAPHY........................................................................................................................................39
 CHAPTER ONE

1.INTRODUCTION

This chapter deals with the background of the study, problem statement, proposed solutions, objectives
and significance of the project

1.2BACKGROUND

In the era of network information, information technology is widely used in all walks of life including
creating an electronic store (e-store) for an electronic commerce (e-commerce). These electronic store
applications have become an important sales channel which has gain ground as an accepted and used
business paradigm.

More businesses are implementing various technologies in providing functionality for performing
commercial transactions over the internet and doing online sale

This Phone and accessories system entails the online sale of mobile phones and their accessories
specifically. It has sales agents who help in the sale of the mobile phones and other accessories at the
shop. The products are shipped from other countries. The store is located in Umoja Nairobi which entails
electronics of a small enterprise and with no official website whatsoever.

it allows customers to browse through mobile brands only and then check the different type of mobile
phones available in the market for a specific brand and make sure there’s reliability and its guaranteed.

This thought is derived as when we go to online sale portals, they deal with a lot of products and
customers sometimes may feel it be too huge and confused with mobile categories that are available.
Hence came up with mobile online shopping.

This system will help users communicate efficiently to the and explain their needs and wants to the sales
person without fear of which their data will be recorded in a technological system by the managers and
they can get their products with ease as the system will generate reports on the sales of mobile phone
accessories. This project will help compute the Store work in a computerized way

3. PROBLEM STATEMENT

With a clear review on the operations at Scartek Shop, notice has been outlined that the firm do not
have any electronic store they only depend on their manual offline way of selling their products.
However, problems associated with this method of selling their products were

 time consuming: It took a lot of time to go shopping to a store. Distance from house or
workplace to the store is time consuming. It is also time consuming while searching a particular
product.

 
  Bargaining: Customer tend to do physical bargaining to the seller unlike shopping online, where
buyer cannot do bargain as the price of the product isfixed

 Stock records were kept manually and it is not efficient: Sometimes, the stocks are old and are
up for reduction and sale, the manual way of stock records is not efficient in keeping tracks of
old products.

 Geographical restrictions: The store is located only in Umoja and people cannot access it from
other locations, imagine that they have to drive for hours to just walk in to the store

Nowadays people find it tiresome to get to specific mobile centers which deal with mobile sales .

It has become also quite difficult to access the specific original phones that relate to the brand you need
is quality reliability as customers get confused with the brands available as they are many they also get
misguided information by the sales person and end up not getting what they need in the end

1.4. PROPOSED SOLUTION

I developed a phone and accessories system that will connect patients to available brands and easily
purchase their phones

It will be an easy to browse or use website which will showcase only mobile products. It allows
comparison of prices for a particular price range mobiles of different brands thereby allowing the
customer to select one of them as per the features and reliability. This application will also deal with
mobiles spare parts or accessories too for all brands.

If the user is not able to efficiently use the system, then he or she can contact the shop and visit
physically for the proper guidance they need

1.5 MODULES

Modules:
Admin Panel: It will allow managing customer info and save the data related to all info for customers
and vendors. It will allow the addition of mobiles, mobile accessories in details. Products will be saved to
the database via admin panel. Products can be added to the system by vendors. Each vendor will be
allowed to add a product after being registered. Whenever a vendor or customer registers it is saved to
the database via admin panel. It provides a secure and reliable way of saving the data to the database.
Admin panel as managed by admin will have the option to manage the delivery status of products
ordered. Admin will update the status of an order as delivered or in progress from admin panel. Admin
will also have the option to attach a delivery executive to be linked to an order.

Dashboard: It will display available mobile brands and a bit of info wherever needed. A user accessing
the application or website can click on a product to search for the different category of mobile. It will
provide info related to mobile accessories that are available on the website and vendor information to
which are actually providing the mobile and its related accessories to be on sale on the website.

Cart: It will basically manage the orders placed by customers; the option will be provided to remove an
already added item. Increase the quantity of the products if needed, it will allow the customer to
manage address to be delivered, also an option to check the delivery status. Once products are added to
a cart, the delivery boy will be assigned to it by admin in admin panel and manage the delivery status.

Vendor: A vendor will initially register and it will be approved by admin. Once registered, the vendor has
to add info related to mobile products which will be added for sale on the website. They have to add
mobile accessories also which they deal with.

3. OBJECTIVES

. OBJECTIVES

The specific objectives of this project are:

4.1 The main objective

is to develop the system the SCARTEK MOBILE PHONE AND ACCESORIES SYSTEM which will manage the
details of the Mobile all the sales and inventory in the,the purpose of the project is to build an
application program to reduce the manual work.

4.2.Other Objectives

 To reduce the cumbersome job of maintaining several documents.

 To eliminate the delays in the generation of reports that which item has sold to whom.
 Searching will become more efficient and faster.
 To store product detail using a secure database
 To provide a channel that will ensure that products are deliver to their customers
 To provide Security of data which is very important due to the fact that hackers and intruders
are very disruptive to any kind of system.
4.3.The System objectives of of this project are:

 To build an environment where various salesperson will ensure that products are deliver to their
customers
 Assist to maintain the records and atomicity by using the proper table to save records so that
no one can access it and one person purchases the product
 The System will secure the Mobile and accessories and its records by generating passcodes to
access.

4. JUSTIFICATION

I would love to bring encouragement and improve each person’s preference on phones so that people
would be comfortable and rely in the mobile brand they need in the future

CHAPTER TWO

2.1LITERATURE REVIEW

While researching I found store called Skartek 254 that deals with mobile and other device accessories
and ships products from USA, CHINA, Korea and UK etc.

They deal with phones and machines users can access mobiles physically you can buy them all over East
Africa and you can visit the store located in Umoja and get the product you need

This is efficient only when the customer goes to get the product, he/she wants but there’s no online
accessibility whatsoever in the stores to solve your problem it can be efficient yes but with no
modernized way of purchasing phones in case a user stays far and wants to purchase the phone in the
shop is disadvantaged

I found this analogue since they have no platform for the users to access the devices and they only have
the seller physically whose only work is to sell the products but not to provide full guidance for the
product for users in need which is crucial and costly

Reference: scartek.co.ke/

There were also similar stores that only provided physical services with a basic platform for viewing
the products and buying them physically without good management systems with non-involvement of
the inventories of the Products e.g:
A mobile store called Umoja Mobile shop which is a Destination for Retail trade, , Retail sale of
computers, peripheral units, software and telecommunications equipment in specialized stores, Mobile
phone stores, Telecommunications in Kenya .

The Store was established in Donholm, Moi Drive Nairobi, Kenya.

Reference :https://www.africabizinfo.com/KE/umoja-mobile-phone-repair-0715-289171/

this is an analogue method of retailing since they have no platform for the users to access the devices
and they only have the seller physically whose only work is to sell the products but not to provide full
guidance for the product for users in need which is crucial and costly.

Therefore, it is possible to say that e-commerce develops according to current trends and tries

to respond in time to customers’ demand, as Weitzel (2014) said,

 “ECommerce will continue to evolve, and marketers will find innovative ways to use online ordering to
reach new markets and create new selling occasions”.

CHAPTER THREE

3.1. METHODOLOGY

3.1.1RESEARCH METHODOLOGY

In order to get information concerning phones and accessories in this system I had to visit a phone
brand company inquire and get information and explore more about mobile consultations using
interviews and observation methods

3.1.2DEVELOPMENT METHODOLOGY

In this system the Agile methodology is convenient to develop the system

Agile methodology is a software development process that utilize incremental changes with a focus on
quality and attention to detail
Phase1; Requirements –an initial documentation that will list all requirements before designing e.g. end
result of project, features that will support it e.g. different font sizes, features that won’t support t e.g.
animations

Phase 2: Design-during first iteration the product owner assembles their development team and
introduces the requirements created during previous stage

Phase3: Development and coding

Writing the code and converting design documentation into the actual software within software
development process

Phase 4: integration and testing

Making sure the software is bug free and compatible with everything else that the developers have
written before

A series of tests is conducted to ensure the code is clean

Phase 5: Implementation and deployment

Application is deployed on to the servers and provided to the customers either for the demo or the
actual use

Phase 6: Review

Once all of the previous deployment phases are complete the product owner reviews the progress made
towards completing the requirements

4. HARDWARE REQUIREMENTS:

The most common set of requirements defined by any operating system or software application is the
physical computer resources, also known as hardware. A hardware requirements list is often
accompanied by a hardware compatibility list (HCL), especially in case of operating systems. An HCL lists
tested, compatibility and sometimes incompatible hardware devices for a particular operating system or
application. The following sub-sections discuss the various aspects of hardware requirements.

HARDWARE REQUIREMENTS FOR PRESENT PROJECT:

PROCESSOR: Intel dual Core, i3

RAM: 1 GB

HARD DISK: 80 GB

5. SOFTWARE REQUIREMENTS:

Software Requirements deal with defining software resource requirements and pre-requisites that need
to be installed on a computer to provide optimal functioning of an application. These requirements or
pre-requisites are generally not included in the software installation package and need to be installed
separately before the software is installed.

SOFTWARE REQUIREMENTS FOR PRESENT PROJECT:

OPERATING SYSTEM: Windows 7/8

FRONT END: HTML

SERVER-SIDE SCRIPT: Php

DATABASE : MySQL

SOFTWARE SPECIFICATION

MySQL:

MySQL is developed, distributed, and supported by Oracle Corporation. MySQL is a database system
used on the web it runs on a server. MySQL is ideal for both small and large applications. It is very fast,
reliable, and easy to use. It supports standard SQL. MySQL can be compiled on a number of platforms.

The data in MySQL is stored in tables. A table is a collection of related data, and it consists
of columns and rows. Databases are useful when storing information categorically.

FEATURES OF MySQL:

Internals and portability:

Written in C and C++.

Tested with a broad range of different compilers.

Works on many different platforms.

Tested with Purify (a commercial memory leakage detector) as well as with Val grind, a GPL tool.

Uses multi-layered server design with independent modules.

Security:

A privilege and password system that is very flexible and secure, and that enables host-based
verification.

Password security by encryption of all password traffic when you connect to a server.

Scalability and Limits:

Support for large databases. We use MySQL Server with databases that contain 50 million records. We
also know of users who use MySQL Server with 200,000 tables and about 5,000,000,000 rows.

Support for up to 64 indexes per table (32 before MySQL 4.1.2). Each index may consist of 1 to 16
columns or parts of columns. The maximum index width is 767 bytes for InnoDB tables, or 1000
for MyISAM; before MySQL 4.1.2, the limit is 500 bytes. An index may use a prefix of a column
for CHAR, VARCHAR, BLOB, or TEXT column types.

CONNECTIVITY:

Clients can connect to MySQL Server using several protocols:

Clients can connect using TCP/IP sockets on any platform.

On Windows systems in the NT family (NT, 2000, XP, 2003, or Vista), clients can connect using named
pipes if the server is started with the --enable-named-pipe option. In MySQL 4.1 and higher, Windows
servers also support shared-memory connections if started with the --shared-memory option. Clients
can connect through shared memory by using the --protocol=memory option.

On UNIX systems, clients can connect using Unix domain socket files.

LOCALIZATION:

The server can provide error messages to clients in many languages.

All data is saved in the chosen character set.

CLIENTS AND TOOLS:

MySQL includes several client and utility programs. These include both command-line programs such as
MySQL dump and mysqladmin, and graphical programs such as MySQL Workbench.

MySQL Server has built-in support for SQL statements to check, optimize, and repair tables. These
statements are available from the command line through the MySQL check client. MySQL also
includes myisamchk, a very fast command-line utility for performing these operations
on MyISAM tables.

MySQL programs can be invoked with the --help or -? option to obtain online assistance.

WHY TO USE MySQL:

Leading open-source RDBMS

Ease of use – No frills

Fast

Robust

Security

Multiple OS support

Free

Technical support

Support large database– up to 50 million rows, file size limits up to 8 Million TB

PHP:

WHAT IS PHP?

PHP is an acronym for "PHP Hypertext Preprocessor"

PHP is a widely-used, open-source scripting language

PHP scripts are executed on the server

PHP costs nothing, it is free to download and use

WHAT IS PHP FILE?

PHP files can contain text, HTML, CSS, JavaScript, and PHP code

PHP code are executed on the server, and the result is returned to the browser as plain HTML

PHP files have extension ".php"

WHAT CAN PHP DO?

PHP can generate dynamic page content

PHP can create, open, read, write, delete, and close files on the server

PHP can collect form data

PHP can send and receive cookies

PHP can add, delete, modify data in your database

PHP can restrict users to access some pages on your website

PHP can encrypt data

With PHP you are not limited to output HTML. You can output images, PDF files, and even Flash movies.
You can also output any text, such as XHTML and XML.

WHY PHP?

PHP runs on various platforms (Windows, Linux, Unix, Mac OS X, etc.)

PHP is compatible with almost all servers used today (Apache, IIS, etc.)

PHP supports a wide range of databases

PHP is free. Download it from the official PHP resource: www.php.net

UML Design

The Unified Modeling Language (UML) is a standard language for specifying, visualizing, constructing,
and documenting the software system and its components. It is a graphical language, which provides a
vocabulary and set of semantics and rules. The UML focuses on the conceptual and physical
representation of the system. It captures the decisions and understandings about systems that must be
constructed. It is used to understand, design, configure, maintain, and control information about the
systems.

The UML is a language for:

Visualizing

Specifying

Constructing

Documenting

UML Diagram

A diagram is the graphical presentation of a set of elements, most often rendered as a connected graph
of vertices and arcs. you draw diagram to visualize a system from different perspective, so a diagram is a
projection into a system. For all but most trivial systems, a diagram represents an elided view of the
elements that make up a system. The same element may appear in all diagrams, only a few diagrams, or
in no diagrams at all. In theory, a diagram may contain any combination of things and relationships. In
practice, however, a small number of common combinations arise, which are consistent with the five
most useful views that comprise the architecture of a software-intensive system

USE CASE DIAGRAM:

A use case diagram in the Unified Modeling Language (UML) is a type of behavioral diagram defined by
and created from a use-case analysis. Its purpose is to present a graphical overview of the functionality
provided by a system in terms of actors, their goals (represented as use cases), and any dependencies
between those use cases.

Use case diagrams are formally included in two modeling languages defined by the OMG: the
unified modeling language (UML) and the systems modeling language(sysML)

USECASE DIAGRAM FOR PHONE AND ACCESSORIES SYTEM

USE CASE DIAGRAM

In this diagram responsibilities of each user in the system are shown, e.g. of each

use case involved in the system

8.ER Relation Diagram

An entity-relationship model (ER Mode) describes inter-related things of interest

in a specific domain of knowledge. An ER model is composed of entity types (which
classify the things of interest) and specifies relationships that can exist between
instances of those entity types.

DATABASE DESCRIPTION
Has the database design which includes a conceptual design and it outlines the functions including
design of interactions, processes sand strategies

CLASS DIAGRAM
The class diagram seeks to identify the various objects to be inherent in the system. Objects are real life
entities that have an identity, a state and exhibits some certain form of behavior.

class diagram will show the class modeling the various objects that are interacting with each other and
the association
DEPLOYMEMT DIAGRAM
CHAPTER FIVE

SYSTEM IMPLEMENTATION

5. IMPLEMENTATION:

5.1 Introduction:

Implementation is the stage of the project when the theoretical design is turned out into a working
system. Thus, it can be considered to be the most critical stage in achieving a successful new system and
in giving the user, confidence that the new system will work and be effective.

The implementation stage involves careful planning, investigation of the existing system and its
constraints on implementation, designing of methods to achieve changeover and evaluation of
changeover methods.

5.2 SAMPLE CODE

<?php

/**

* WordPress User Page

* Handles authentication, registering, resetting passwords, forgot password,

* and other user handling.

* @package WordPress

*/

/** Make sure that the WordPress bootstrap has run before continuing. */
require __DIR__ . '/wp-load.php';

// Redirect to HTTPS login if forced to use SSL.

if ( force_ssl_admin () && ! is_ssl() ) {

if ( 0 === strpos( $_SERVER['REQUEST_URI'], 'http' ) ) {

wp_safe_redirect( set_url_scheme( $_SERVER['REQUEST_URI'], 'https' ) );

exit;

} else {

wp_safe_redirect( 'https://' . $_SERVER['HTTP_HOST'] . $_SERVER['REQUEST_URI'] );

exit;

/**

* Output the login page header.

* @since 2.1.0

* @global string $error Login error message set by deprecated pluggable wp_login() function

* or plugins replacing it.

* @global bool|string $interim login Whether interim login modal is being displayed. String 'success'

* upon successful login.

* @global string $action the action that brought the visitor to the login page.

* @param string $title Optional. WordPress login Page title to display in the `<title>` element.

* Default 'Log In'.

* @param string $message Optional. Message to display in header. Default empty.

* @param WP_Error $wp_error Optional. The error to pass. Default is a WP_Error instance.

*/
function login_header( $title = 'Log In', $message = '', $wp_error = null ) {

global $error, $interim_login, $action;

// Don't index any of these forms.

add_filter( 'wp_robots', 'wp_robots_sensitive_page' );

add_action( 'login_head', 'wp_strict_cross_origin_referrer' );

add_action( 'login_head', 'wp_login_viewport_meta' );

if ( ! is_wp_error( $wp_error ) ) {

$wp_error = new WP_Error();

// Shake it!

$shake_error_codes = array( 'empty_password', 'empty_email', 'invalid_email',

'invalidcombo', 'empty_username', 'invalid_username', 'incorrect_password',
'retrieve_password_email_failure' );

/**

* Filters the error codes array for shaking the login form.

* @since 3.0.0

* @param array $shake_error_codes Error codes that shake the login form.

*/

$shake_error_codes = apply_filters( 'shake_error_codes', $shake_error_codes );

if ( $shake_error_codes && $wp_error->has_errors() && in_array( $wp_error-

>get_error_code(), $shake_error_codes, true ) ) {

add_action( 'login_footer', 'wp_shake_js', 12 );

}
 $login_title = get_bloginfo( 'name', 'display' );

/* translators: Login screen title. 1: Login screen name, 2: Network or site name. */

$login_title = sprintf( __( '%1$s &lsaquo; %2$s &#8212; WordPress' ), $title, $login_title );

if ( wp_is_recovery_mode() ) {

/* translators: %s: Login screen title. */

$login_title = sprintf( __( 'Recovery Mode &#8212; %s' ), $login_title );

/**

* Filters the title tag content for login page.

* @since 4.9.0

* @param string $login_title The page title, with extra context added.

* @param string $title The original page title.

*/

$login_title = apply_filters( 'login_title', $login_title, $title );

?><!DOCTYPE html>

<html <?php language_attributes(); ?>>

<head>

<meta http-equiv="Content-Type" content="<?php bloginfo( 'html_type' ); ?>; charset=<?php

bloginfo( 'charset' ); ?>" />

<title><?php echo $login_title; ?></title>

<?php

CONFIGURATION SAMPLE CODE FOR WORD PRESS

<?php

/**

* The base configuration for WordPress

* The wp-config.php creation script uses this file during the

* installation. You don't have to use the web site, you can

* copy this file to "wp-config.php" and fill in the values.

* This file contains the following configurations:

* * MySQL settings

* * Secret keys

* * Database table prefix

* * ABSPATH

* @link https://wordpress.org/support/article/editing-wp-config-php/

* @package WordPress

*/

// ** MySQL settings - You can get this info from your web host ** //

/** The name of the database for WordPress */

define(‘DB_NAME', 'database_name_here' );

/** MySQL database username */

define( 'DB_USER', 'username_here' );

/** MySQL database password */

define( 'DB_PASSWORD', 'password_here' );

/** MySQL hostname */

define( 'DB_HOST', 'localhost' );

/** Database Charset to use in creating database tables. */

define( 'DB_CHARSET', 'utf8' );

/** The Database Collate type. Don't change this if in doubt. */

define( 'DB_COLLATE', '' );

/**#@+

* Authentication Unique Keys and Salts.

* Change these to different unique phrases!

* You can generate these using the {@link https://api.wordpress.org/secret-key/1.1/salt/

WordPress.org secret-key service}

* You can change these at any point in time to invalidate all existing cookies. This will force all users
to have to log in again.

* @since 2.6.0

*/

define( 'AUTH_KEY', 'put your unique phrase here' );

define( 'SECURE_AUTH_KEY', 'put your unique phrase here' );

define( 'LOGGED_IN_KEY', 'put your unique phrase here' );

define( 'NONCE_KEY', 'put your unique phrase here' );

define( 'AUTH_SALT', 'put your unique phrase here' );

define( 'SECURE_AUTH_SALT', 'put your unique phrase here' );

define( 'LOGGED_IN_SALT', 'put your unique phrase here' );

define( 'NONCE_SALT', 'put your unique phrase here' );

/**#@-*/

/**

* WordPress Database Table prefix.

* You can have multiple installations in one database if you give each

* a unique prefix. Only numbers, letters, and underscores please!

*/

$table_prefix = 'wp_';

/**

* For developers: WordPress debugging mode.

* Change this to true to enable the display of notices during development.

* It is strongly recommended that plugin and theme developers use WP_DEBUG

* in their development environments.

* For information on other constants that can be used for debugging,

* visit the documentation.

* @link https://wordpress.org/support/article/debugging-in-wordpress/

*/

define( 'WP_DEBUG', false );

/* That's all, stop editing! Happy publishing. */

/** Absolute path to the WordPress directory. */

if ( ! defined( 'ABSPATH' ) ) {
 define( 'ABSPATH', __DIR__ . '/' );

/** Sets up WordPress vars and included files. */

require_once ABSPATH . 'wp-settings.php';

<?php

/**

* Handles Comment Post to WordPress and prevents duplicate comment posting.

* @package WordPress

*/

if ( 'POST' !== $_SERVER['REQUEST_METHOD'] ) {

$protocol = $_SERVER['SERVER_PROTOCOL'];

if ( ! in_array( $protocol, array( 'HTTP/1.1', 'HTTP/2', 'HTTP/2.0' ), true ) ) {

$protocol = 'HTTP/1.0';

header( 'Allow: POST' );

header( "$protocol 405 Method Not Allowed" );

header( 'Content-Type: text/plain' );

exit;

/** Sets up the WordPress Environment. */

require __DIR__ . '/wp-load.php';

nocache_headers();

$comment = wp_handle_comment_submission( wp_unslash( $_POST ) );

if ( is_wp_error( $comment ) ) {

$data = (int) $comment->get_error_data();

if ( ! empty( $data ) ) {

wp_die(
 '<p>' . $comment->get_error_message() . '</p>',

__( 'Comment Submission Failure' ),

array(

'response' => $data,

'back_link' => true,

);

} else {

exit;

$user = wp_get_current_user();

$cookies_consent = ( isset( $_POST['wp-comment-cookies-consent'] ) );

/**

* Perform other actions when comment cookies are set.

* @since 3.4.0

* @since 4.9.6 The `$cookies_consent` parameter was added.

* @param WP_Comment $comment Comment object.

* @param WP_User $user Comment author's user object. The user may not exist.

* @param bool $cookies_consent Comment author's consent to store cookies.

*/

do_action( 'set_comment_cookies', $comment, $user, $cookies_consent );

$location = empty( $_POST['redirect_to'] ) ? get_comment_link( $comment ) : $_POST['redirect_to'] .

'#comment-' . $comment->comment_ID;
// If user didn't consent to cookies, add specific query arguments to display the awaiting moderation
message.

if ( ! $cookies_consent && 'unapproved' === wp_get_comment_status( $comment ) && !

empty( $comment->comment_author_email ) ) {

$location = add_query_arg(

array(

'unapproved' => $comment->comment_ID,

'moderation-hash' => wp_hash( $comment->comment_date_gmt ),

),

$location

);

/**

* Filters the location URI to send the commenter after posting.

* @since 2.0.5

* @param string $location The 'redirect_to' URI sent via $_POST.

* @param WP_Comment $comment Comment object.

*/

$location = apply_filters( 'comment_post_redirect', $location, $comment );

wp_safe_redirect( $location );

exit;

BLOG HEADER
<?php

/**

* Loads the WordPress environment and template.

* @package WordPress

*/

if ( ! isset( $wp_did_header ) ) {

$wp_did_header = true;

// Load the WordPress library.

require_once __DIR__ . '/wp-load.php';

// Set up the WordPress query.

wp();

// Load the theme template.

require_once ABSPATH . WPINC . '/template-loader.php';

}
 CHAPTER 6

SYSTEM TESTING

6.1 INTRODUCTION TO SYSTEM TESTING:

The purpose of testing is to discover errors. Testing is the process of trying to discover every
conceivable fault or weakness in a work product. It provides a way to check the functionality of
components, sub-assemblies, assemblies and/or a finished product It is the process of exercising
software with the intent of ensuring that the Software system meets its requirements and user
expectations and does not fail in an unacceptable manner. There are various types of tests. Each test
type addresses a specific testing requirement.

UNIT TESTING

TYPE OF TEST

Unit testing

AREAS TESTED EXPECTED RESULTS

Numeric fields Should accept numbers only

Character fields Should accept only text

Login Should accept the correct

password and username.

DataGrid view Should be able to display

database information.

Date fields Should be selected from

calendar.

Buttons Should be clicked to direct the

user.
MODULE TESTING

Involves testing for reliability and a module constitutes related components;

TYPE OF TEST

Module Testing

AREAS TESTED EXPECTED RESULTS

New module Should add new record to the database

Delete module Should remove records from the database

Search module Should find records specified by user from the database

Edit module Should allow one to modify existing records

INTEGRATION TESTING

This test proves that all areas of the system interface with each other correctly and that there are no
gaps in the data flow. Final integration Test proves that the system works as integrated unit when all the
fixes are complete.

TYPE OF TEST AREA TESTED EXPECTED OUTCOME

Integration Testing Do changes, updates and Input/changes or/and updates

inputs
made reflect the ones in the
made on the system reflect the
database respectively
changes in the database?
SYSTEM TESTING

This is whereby all units, sub-systems and objects are integrated together to form the whole system. The
tests in this case include testing integration of the various units and checking that the overall system
gives the desired results from the input entered.

TYPE OF TEST AREA TESTED EXPECTED OUTCOME

System Testing Does the system connect successfully to the database?

Connection is successful

TYPE OF TEST AREA TESTED EXPECTED OUTCOME

System Testing Does the system connect Connection is successful

successfully to the database?

VALIDATION TESTING

This is intended to show that the system confirms to its specifications and that it meets the expectation
of the customer buying the system. It involves checking processes like inspection and reviews at each
stage of the development. It checks whether the system has met the functionalities of the users or the
requirements. The outcomes are:

A deviation from the system and deficiency list is uncovered.

The functional characteristics confirm to the specification are acceptable.

The system is released to the users or customers to interact with it and in case there are problems, the
developer makes changes to the required parts of the system

USABILITY TESTING

It involves looking for bugs not in the functionality of the system program, but in the layout and utility of
the user interface. It is often performed on a prototype before the actual system code is written, so it’s
easy to change if needed. This is a situation where the user gives an opinion on what the user interface
is like. It also focuses on making sure the system is user friendly and users can use it comfortably.
ACCEPTANCE TESTING

This is the verification that the final product meets the institutions” requirements. It ensures that all the
components of the system are tested. It describes the acceptance testing process, such as the features
to be tested, pass/fail criteria, approach to testing, roles and responsibilities, resources requirements
and schedule.

It also defines the functionality to be tested, the requirements verified by the test, test precondition,
test steps and test.

SECURITY TESTING

The system is secure from unauthorized users. Error message box pop out every time wrong credentials
are provided. The system is only accessible by users with the correct credentials or valid details. The
login mechanism is put in place to ensure only registered customers will gain access to the system
information.

Different users of the system are provided with different login details that allow them access different
functionalities of the system.

TESTING TOOLS AND ENVIRONMENT

HARDWARE REQUIREMENTS

Flash disk.

Computer

Printer

Compact disk

Uninterruptible power supply (UPS)

SOFTWARE REQUIREMENTS

Operating system; windows 8.1

Programming language; PHP, HTML

Database system; My SQL

Antivirus software; AVG and 360 Total Security

POST CONDITIONS
Alpha test

In this test, international testers run live data through the system checking out for bugs not found in
integration test.

Beta test

This is the next step where the program is actually released to the users with the understanding that the
program is being tested. Through this the expected user is able to identify the errors, which are reported
to the developer and then corrected.

Test Results:
All the test cases mentioned above passed successfully. No defects encountered.

Acceptance Testing:
User Acceptance Testing is a critical phase of any project and requires significant
participation by the end user. It also ensures that the system meets the functional
requirements.

Test Results:
All the test cases mentioned above passed successfully. No defects encountered .
CHAPTER 7

SAMPLE SCREENSHOTS

7.0 DATABASE SAMPLES

8.CONCLUSION:

Since we are entering details of the USERS electronically in the Scartek phone and accessories
System, data will be secured. Using this application, we can retrieve users history with a single click.
Thus, processing information will be faster. It guarantees accurate maintenance of their details. It easily
reduces the physical efforts of consultation with efficiency
9. BIBLOGRAPHY

1. PHP MySQL Website Programming: Problem - Design – Solution by Chris

Lea, Mike Buzzard, Dilip Thomas, Jessey White-Cinis

2. Beginning PHP5, Apache, and MySQL Web Development (Programmer to

Programmer) by Elizabeth Naramore

3. MySQL/PHP Database Applications, 2nd Edition by Brad Bulger

4. How to Do Everything with PHP and MySQL by Vikram Vaswani