Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 61

MAHATMA GANDHI COLLEGE

KEEZHUR P.O, IRITTY


670703

BELL-IT
By
ARAVIND V R [MG18CCSR20]
RASHID N P [MG18CCSR26]

Under the Guidance of

REJEESH E

Project Report
Submitted to the Mahatma Gandhi College, Iritty in partial fulfillment of the
requirements
For the award of the degree of
B.Sc. COMPUTER SCIENCE (2020-2021)

~1~
CERTIFICATE

This is to certify that the project entitled “BELL-IT” prepared by ARAVIND V


R AND RASHID N P is a Bonafide record of work done by them towards the
partial fulfillment for the award of Bachelor of Degree in Computer Science
under the Kannur University during the period 2020-2021.

Signature of Asst. Professor in charge Signature of Head of the


Dept.

Submitted for the University examination

Examiners:
1.
2.

~2~
DECLARATION

We hereby declare that this project entitled BELL-IT has been prepared by

us during the year 2020-2021 under the supervision of REJEESH E, Assist. Prof.

of computer science department at Mahatma Gandhi College Iritty, in partial

fulfillment of the requirement of bachelor of computer science degree of Kannur

University.

We also declare that this project is the result of our known effort and has

not been submitted to any other institution for the award of any other degree.

Date : ARAVIND V R , RASHID N P


Place :

~3~
ACKNOWLEDGEMENT

We have immense pleasure in acknowledging the service and cooperation


rendered by umpteen people in their non-fields and ways. The success of any
task accomplished lies not only in hands of the accomplisher but also the guiding
light offered by all those around, towards the road to success, they did much to
shape up the success.
We are grateful to our college Principal Dr. AJITHA V. for extending
facilities required throughout my project work. We are also grateful to our
(department HOD) Dr. Shijo M Joseph for his valuable suggestions and
encouragement throughout the course of this project.
We wish to express my deepest sense of gratitude to my guide REJEESH E
(Assist. Prof.) whose generous support, constant encouragement and healthy
criticism have been of invaluable help to me throughout the course of this
project.
We also express my heart full thanks to my classmates for providing
valuable suggestions.

~4~
TABLE CONTENT

Serial Page
TOPIC
No No

1 ABSTRACT

2 INTRODUCTION

2.1 INTROUDUCTION TO THE SYSTEM

2.2 ABOUT THE PROJECT

3 PROBLEM FORMULATION

3.1 OBJECTIVES

3.2 PROBLEM STATEMENT

3.3 SOFTWARE USED

3.4 PLATFORM REQUIREMENTS

4 SYSTEM ANALYSIS

4.1PRESENT SYSTEM

4.2PROPOSED SYSTEM

4.3USE CASE ANALYSIS

4.4 FEASIBILITY ANALYSIS

~5~
5 SYSTEM DESIGN

5.1 INTRODUCTION

5.2 FUNDAMENTAL DESIGN CONCEPT

5.3 INPUT DESIGN

5.4 OUTPUT DESIGN

5.5 DATABASE DESIGN

5.6 TABLES

5.7 CONCEPTUAL SYSTEM DESIGN

5.8 VALIDATION AND CHECKS

6 SYSTEM DEVELOPMENT

7 SYSTEM CODING AND TESTING

7.1 SYSTEM TESTING

7.2 LEVELS OF TESTING

7.3 TESTING THE SYSTEM

8 SYSTEM IMPLEMENTATION AND MAINTANENCE

9 FORMS

10 SAMPLE CODE

11 CONCLUSION

12
BIBLIOGRAPHY

~6~
1.ABSTRACT
The online auction system is a model where we participate in a bid for products
and service. This auction is made easier by using online software which can
regulate processes involved. The requirement for online auction or online bidding
can be more accurately specified by the client. It should be healthy and will be a
good practice when it is made more transparent as a matter of fact. Online
Bidding has become more wide spread in all sorts of industrial usage. It not only
includes the product or goods to be sold, it also has services which can be
provided. Due to their low cost this expansion made the system to grow. Online
bidding has become a standard method for procurement process. Bidders can be
maintained in a single database according to the preference, and they can be
monitored. User’s data can be maintained in a confidential way for validity and
integrity of contractual documentation. Online bidding is based upon lowest or
the highest price which is initiated but not the best value for the product.
Although there is a chance to fix the criteria against the fact expected to have
desired value by the seller. The application proposed to do is a selling and buying
online portal with auction facility

~7~
2.INTRODUCTION
There are several different types of auctions and certain rules exist for each
auction. There are variations for an auction which may include minimum price
limit, maximum price limit and time limitations etc. Depending upon the auction
method bidder can participate remotely or in person. Remote auction includes
participating through telephone, mail, and internet. Shopping online has widely
grown; the sytem is implemented to buy and sell old or already used
products ,with auction facility. online auction system is increasing rapidly.
Online auction is becoming more and more popular in electronic commerce and
hence it should system must increase its quality and security. The online auction
system is a model where we participate in a bid for products and service. This
auction is made easier by using online software which can regulate processes
involved. The requirement for online auction or online bidding can be more
accurately specified by the client. It should be healthy and will be a good practice
when it is made more transparent as a matter of fact. Online Bidding has become
more wide spread in all sorts of industrial usage. It not only includes the product
or goods to be sold, it also has services which can be provided. Due to their low
cost this expansion made the system to grow. Online bidding has become a
standard method for procurement process. Bidders can be maintained in a single
database according to the preference, and they can be monitored. User’s data can
be maintained in a confidential way for validity and integrity of contractual
documentation. Online bidding is based upon lowest or the highest price which is
initiated but not the best value for the product. Although there is a chance to fix
the criteria against the fact expected to have desired value by the seller. The
application proposed to do is a selling and buying online portal with auction
facility.

~8~
2.2 ABOUT THE PROJECT

The project BELL-IT uses the facility of auction. It makes a convenient way to
sell and buy through an app. The project is developed using the efficient
technology Android Studio (Android Application-which uses Java and XML)
and PHP, MySQL and XAMPP.

3.PROBLEM FORMULATION
3.1 OBJECTIVES
Objective of the Project
The main objective of this project is to extend the existing system in online
manner. The proposed project is designed to serve both seller and buyer. This
system allows users to manage their online selling and buying in an efficient
manner.
The objective of the project is to make a good mobile application with an
overall performance. The App should be easy to work. The App should be able to
extract information from database very easily. The App is designed in such a way
that the future plans of expansion can be implementing easily without affecting
the existing features and also using the existing features.

Problem definition and based on the problem definition system requirement


specification is produced.
 Easiness in finding a buyer

 No physical location

 Time and money saving

 No anonymous bidders

 No rude bidders

 Auction facility

3.2 PROBLEM STATEMENT

~9~
The traditional or physical systems of auction system has easy to do fraud
schemes or bids from the historical auction data using data mining techniques
and other accomplices. One of the most currently fraud schemes is that the
bidders are making false identity or accounts in order to increase the sale price.
Currently there are two approaches mostly being implemented such as policy-
based and reputation-based trust management, which also lag certain security
issues.he existing "OPEN Auction House" is managed manually. Prior to each
auction the day of auction, the (venue and the items on auction are announced
through news media. Those who wish to take part in the auction have to arrive at
the venue on that day on time. This conventional method most of the times
prevent aspiring bidders from participating in the bidding process. Another
headache of the old system is to track each bidding process and to make it
culminate in financial settlement. So the system has to keep records of both
buyers and sellers until the end of settlement. The process is very cumbersome
and time consuming.
The disadvantages of the existing system are:
Anonymous bidder
The online auction does not take place face to face which creates anonymous
bidders. The auctioneers cannot have a hold on who is participating in the
bidding. This can lead to anonymity in identifying the bidders.
False bidding
There is option available for false bidding with the auction in order to
discourage or mislead the bidding.
Product genuineness
One can view only the product photo on the auction website. One cannot
inspect the product about its condition and usability physically which may lead
to lack of product genuineness. Some of the online auction does not support
refund.
Rude buyers
This is a genuine issue. There could be people who are rude in an market and
in all such public places. They really disturb all by their way of approach and
also wastes time which is very valuable.

~ 10 ~
3.3 SOFTWARE USED
OPERATING SYSTEM
An operating system (OS) is system software that manages computer
hardware and software resources and provides common services for computer
programs. The operating system is an essential component of the system software
in a computer system. Application programs usually require an operating system
to function. Time-sharing operating systems schedule tasks for efficient use of
the system and may also include accounting software for cost allocation of
processor time, mass storage, printing, and other resources. For hardware
functions such as input and output and memory allocation, the operating system
acts as an intermediary between programs and the computer hardware, although
the application code is usually executed directly by the hardware and frequently
makes system calls to an OS function or be interrupted by it. Operating systems
are found on many devices that contain a computer—from cellular phones and
video game consoles to web servers and supercomputers. Examples of popular
modern operating systems include ((Android, BlackBerry, BSD, Chrome OS, IOS,
Linux, OS X, QNX, Steam OS, Microsoft Windows (and variant Windows Phone),
and z/OS. The first nine of these examples share roots in UNIX. Popular hard real
time operating systems include FreeRTOS, ((Miriam and VxWorks)).
PHP
Rasmers Lerdarf- software engineer, apache team member and
international man of mystery is the creator and original driving force behind
PHP.PHP is the web development language written by and for web developers.
PHP stands for Hyper Text Preprocesses. The product was originally named
Personal Home Page Tool. But as it expanded in scope, a new and more
appropriate name was selected by community rate. PHP is currently in its fifth
major rewrite called PHP5 or just plain PHP. PHP is a server scale language which
can be embedded on HTML or used as a standalone binary proprietary product in
this niche are Microsoft’s active server pages. Some tech journalists used to call
PHP ‘the open source ASP’ because its functionality is similar to that of the MS
product although this formulation was misleading as PHP ASP was developed
before. Over the past few years however, PHP and server side java have gained
momentum, while ASP has lost mindshare, so this comparison no longer seems
appropriate. Server side scripting is a collection of super- HTML or small
programs that run inside your web-pages except on the server scale, before they
~ 11 ~
get sent to the browser. For example, you can use PHP to add common headers
and footers to all the pages on a site or to store form-submitted data in a
database. PHP is an official module of Apache HIT server, the market-leading free
web server that runs about 67 percent of the www. This means that the PHP
scripting engine can be built into the web server itself, leading to itself, leading to
faster processing, more efficient memory allocations and greatly simplified
maintenance. Like Apache server, PHP is fully cross platform, meaning of runs
native on several flavors of UNIX as well as on windows and now on mac OSX. All
projects under the Apache Software Foundation-including PHP are open source
software’s.

Features of PHP

 Cost is low

 PHP is an open source software

 PHP is easy to learn

 PHP is embedded within HTML

The HTML embeddedness of PHP has many helpful consequences:

 PHP can quickly be added to code produced by WYSIWYG editors.

 PHP lends itself to a division of labor between designers and scripters.

 Every line of HTML does not need to be rewritten in a programming language.

 PHP can reduce labour costs and increase efficiency due to its shallow learning
curve and ease of use.

 PHP has cross-platform compatibility

 PHP is not tag-based.

 PHP is stable means

 The software doesn’t change radically and incompatibly from release to release

 The server doesn’t need to be rebooted often

~ 12 ~
 PHP is much faster for almost every use than CGI scripts

 PHP makes it easy to communicate with other programs and protocols

 PHP is fast becoming one of the most popular choices for so-called two-tier
development

 PHP is developed and supported in a collaborative fashion by a worldwide


community of users.

XAMPP SERVER
XAMPP is a free and open-source cross-platform web server solution stack
package developed by Apache Friends, consisting mainly of the Apache HTTP
Server, MariaDB database, and interpreters for scripts written in the PHP and
Perl programming languages. Since most actual web server deployments use the
same components as XAMPP, it makes transitioning from a local test server to a
live server possible. XAMPP's ease of deployment means a WAMP or LAMP stack
can be installed quickly and simply on an operating system by a developer. With
the advantage of common add-in applications such as WordPress and Joomla!
can also be installed with similar ease using Bitnami.

Sublime Text Editor


Sublime Text Editor is a full featured Text editor for editing local files or a
code base. It includes various features for editing code base which helps
developers to keep track of changes. Various features that are supported by
Sublime are as follows :-
● Syntax Highlight
● Auto Indentation
● File Type Recognition
● Sidebar with files of mentioned directory
● Macros
● Plug-in and Packages

Sublime Text editor is used as an Integrated Development Editor (IDE) like Visual
Studio code and NetBeans. The current version of Sublime Text editor is 3.0 and
is compatible with various operating systems like Windows, Linux and MacOS.

~ 13 ~
It is a suitable Text editor, you can enjoy its rich beneficial features. Sublime
Text offers its users the following benefits .
● Ability to solve linker errors.
● Keeping track of all files and folders to work with.
● Connectivity with version control systems like Git, Mercurial.
● Problem solving capabilities.
● Keeping color combination for syntax combination.

Since new version , Sublime supports syntax highlighting for the following
languages out of the box:
● ActionScript
● Active Server Pages (ASP).
● C#
● Cascading Style Sheets (CSS)
● ColdFusion
● EDML
● Extensible Hyper Text Markup Language (XHTML)
● Extensible Markup Language (XML)
● Extensible Stylesheet Language Transformations (XSLT)
● Hyper Text Markup Language (HTML)
● Java
● JavaScript
● PHP
● Visual Basic (VB)
● Visual Basic Script Edition (VBScript)
● Wireless Markup Language (WML)

MySQLI
MySQLI is an open-source relational database management system
(RDBMS). Its name is a combination of "My", the name of co-founder Michael
Wideness’s daughter, and "SQL", the abbreviation for Structured Query
Language. The MySQL development project has made its source code available
under the terms of the GNU General Public License, as well as under a variety of
proprietary agreements. MySQL was owned and sponsored by a single for-profit
firm, the Swedish company MySQL AB, now owned by Oracle Corporation. For
~ 14 ~
proprietary use, several paid editions are available, and offer additional
functionality. MySQLI is a central component of the LAMP open-source web
application software stack (and other "AMP" stacks). LAMP is an acronym for
"Linux, Apache, MySQL, Perl/PHP/Python". Applications that use the MySQL
database include: TYPO3, MODx, Joomla, WordPress, Simple Machines Forum,
phpBB, MyBB, and Drupal. MySQL is also used in many high-profile, large-scale
websites, including Google (though not for searches), Facebook, Twitter, Flickr,
and YouTube.
FEATURES:
MySQLI is offered under two different editions: the open source MySQL
Community Server and the proprietary Enterprise Server. ] MySQL Enterprise
Server is differentiated by a series of proprietary extensions which install as 17 E-
university AL-JAMIA ARTS AND SCIENCE COLLEGE server plugins, but
otherwise shares the version numbering system and is built from the same code
base.
Major features as available in MySQLI:
● A broad subset of ANSI SQL 99, as well as extensions
● Cross-platform support
● Stored procedures, using a procedural language that closely adheres
to SQL/PSM
● Triggers , Cursors
● Updatable views
● Online DDL when using the InnoDB Storage Engine.
● Information schema
● Performance Schema that collects and aggregates statistics about
server execution and query performance for monitoring purposes.
● A set of SQL Mode options to control runtime behavior, including a
strict mode to better adhere to SQL standards.
● X/Open XA distributed transaction processing (DTP) support; two
phase commits as part of this, using the default InnoDB storage en-
gine
● Transactions with save points when using the default InnoDB Stor-
age Engine. The NDB Cluster Storage Engine also supports transac-
tions.

~ 15 ~
● ACID compliance when using InnoDB and NDB Cluster Storage En-
gines
● SSL support
● Query caching
● Sub-SELECTs (i.e. nested SELECTs)
● Built-in replication support (i.e., master-master replication and
master slave replication) with one master per slave, many slaves per
master. Multimaster replication is provided in MySQL Cluster, and
multi-master support can be added to un-clustered configurations
using Galera Cluster.
● Full-text indexing and searching
● Embedded database library
● Unicode support
● Partitioned tables with pruning of partitions in optimizer
● Shared-nothing clustering through MySQL Cluster
● Multiple storage engines, allowing one to choose the one that is most
effective for each table in the application.
● Native storage engines InnoDB, MyISAM, Merge, Memory (heap),
Federated, Archive, CSV, Blackhole, NDB Cluster.
● Commit grouping, gathering multiple transactions from multiple
connections together to increase the number of commits per second.
The developers release minor updates of the MySQL Server approximately
every two months. The sources can be obtained from MySQL's website or from
MySQL's GitHub repository, both under the GPL license.

3.4 PLATFORM REQUIREMENTS

Hardware and software requirements for the installation and smooth


functioning of this product could be configured based on the requirements
needed by the component of the operating environment that works as a front-end
system; here we suggest minimum configuration for the both hardware and
software components. Working off with this software is specific to system
environments. It includes two phases.

 HARDWARE REQUIREMENTS
~ 16 ~
o INPUT DEVICE : MOUSE,KEYBOARD

o OUTPUT DEVICE : MONITOR

o MEMORY : 2 GB RAM(MINIMUM)

o PROCESSOR : PENTIUM 4 above

 SOFTWARE REQUIREMENTS

o OPERATING SYSTEM : WINDOWS 7/8/10 or better


performance Server

o Coding : PHP Designing

o Technology : Html5

o BACK END : MYSQLI

o IDE (for web) : Sublime Text Editor

o SOFTWARES USED : Adobe Photoshop/Microsoft Office

o WEB BROWSER : Edge/Google Chrome/Firefox(for web


application)

o WEB SERVER : XAMPP

4.SYSTEM ANALYSIS

~ 17 ~
4.1 PRESENT SYSTEM

The traditional or physical systems of auction system has easy to do fraud


schemes or bids from the historical auction data using data mining techniques
and other accomplices. One of the most currently fraud schemes is that the
bidders are making false identity or accounts in order to increase the sale price.
Currently there are two approaches mostly being implemented such as policy-
based and reputation-based trust management, which also lag certain security
issues.he existing "OPEN Auction House" is managed manually. Prior to each
auction the day of auction, the (venue and the items on auction are announced
through news media. Those who wish to take part in the auction have to arrive at
the venue on that day on time. This conventional method most of the times
prevent aspiring bidders from participating in the bidding process. Another
headache of the old system is to track each bidding process and to make it
culminate in financial settlement. So the system has to keep records of both
buyers and sellers until the end of settlement. The process is very cumbersome
and time consuming
4.2 PROPOSED SYSTEM

The development of this new system contains the following activities,


which try to develop the web-application entire process keeping in the view of
database integration approach:
This system will provide secure registration and profile management of the users.
Administrators would authorize the product to auction, set auction dates &
minimum auction amount for that product.
Prior to each bid, the user’s mobile number must be authenticated and
authorized.
An auction house needs to have products to auction/ so in the proposed
system this is done using product registration module. The module is open to
user who is registered sellers and they need to authenticate before they register
any product. The system controls the closing date by adding 1 days to the
submitting date there by restricting the bidding process to go on in definitely.
Another important module in the proposed project is the Bidding module . Here
one can see the details of any particular product bid. The user can bid on that
item by entering any amount greater than or equal to the incremental bid

~ 18 ~
amount. Here also system checks to see whether the user has his credential
verified otherwise he, she will be directed to the login, registration page. The last
but the least module is the "Administration module”. The module is only open to
the web administrator due to security reasons. This module the administrator
can view products, users, bid prices and dates. This will be necessary when some
of the details of the product need to be edited for one reason or other. There is
another module which runs more or less like background process. The process is
automatic and hidden from other users.

Advantages of proposed system


The advantages of proposed system are:
No physical location
The products for auction does not need any physical location in case of online
auction. The inventory can be managed online and upon sale the product can be
shipped physically. This makes it flexible to hold an auction online site.

Time & money saving


Online auction saves time and money. There is no dedicated time required to
travel and reach an auction place. Just logging into the site makes it possible for
the user to participate in auction which also saves money spent for reaching the
auction spot.
Quick result with instant price update
As bidders participate via online, the results are also instantly flashed on the
website without any time delay. The bid amount or price is updated as and when
the bidding is placed. The results are showed on the site immediately when a
bidder wins the product.
Compare prices
The main advantage of bidding via online is that it provides the opportunity to
compare the price online. The bidder can do a small research regarding the
product price and quality with other online auction site before participating in the
bidding.
No rude bidders
Some bidders can become very aggressive in their attempt to win an item.
Name calling, inappropriate hand gestures and in some rare instances even

~ 19 ~
becoming physically violent (shoving chairs for example) toward their competitors.
Online auctions do not provide bidders the chance to get huffy with one another.

4.3 USE – CASE ANALYSIS

Use - Case diagrams are used to graphically display the entities that can
invoke an activity in the application, and also what those entities can do. An
important part of the Unified Modeling Language (UML) is the facilities for
drawing use case diagrams. Use cases are used during the analysis phase of a
project to identify and partition system functionality. A use case diagram models
the capabilities of your web site. It models the users of your system and anything
that can trigger an activity in your application. The person or thing that can
trigger an activity in your application is called an actor. Use case diagrams are
one way to graphically display what your application does. Throughout the
planning of your application, your use case diagrams change, and evolve as more
requirements are received from your users. It is very important to have a use case
diagram, because you can ensure that your system provides all the capabilities
required.

4.4 FEASIBILITY ANALYSIS

Feasibility is defined as the practical extent to which a project can be performed


successfully. The objective of feasibility study is to establish the reasons for
developing the software that is acceptable to the users, adaptable to changes and
conformable to the established standards. Feasibility study lets the developer
foresee the future of the project and its usefulness. It is used for: Finding out
whether a new system is required or not.

~ 20 ~
 Determining the potentials and drawbacks of the existing system.
 Finding out the various alternatives available.
 Knowing what should be incorporated in the new system.
 Defining the ingredients and objectives involved in the project.
 Identifying whether the proposed system could meet the end needs of the
users.
 Providing technical, economic, operational feasibility of the proposed sys-
tem.
 Identification of user requirements and the benefits expected by the user
from the resulting system.

Various types of feasibility that are commonly considered include:

● Technical Feasibility
● Operational Feasibility
● Economic Feasibility

 Operational Feasibility

The system is operationally feasible as this application is independently


usable by workers and customers as they wish. It is just required basic mobile
operation ability is required. It is android application, so that no more equipment
is required, only just a mobile phone with internet connection. Moreover, no
special environment facilities are required to operate the functionalities of the
system. The operating efficiency and speed will be much better in the proposed
system and will be operationally efficient and much faster. And in future if any
organization administrates this application, they can easily add additional
features as they wish and we can use this application without any trained staffs,
there also may just need basic system operation ability.

 Technical Feasibility

~ 21 ~
The system must be evaluated from the technical point of view first. The
assessment of this feasibility must be based on an outline design of the system
requirement in the terms of input, output, programs, procedure and staff. Having
identified outlines, the investigation must go on to suggest the type of the
equipment, required method developing the system, or running the system once
it has been designed. The project should be developed such that the necessary
function and performance are achieved within the constraints. The project is
developed within the latest technology. Though the technology becomes obsolete
after some period of time, due to the fact that newer versions of some software
supports older versions, the system may still be used. So, there are only minimal
constraints involved with this project. The system has been developed using
ANDROID and PHP, and the project is technically feasible for development.
The considerations that are normally associated technical feasibility include:

 Development risk.
 Resource Availability.
 Technology.
Here I had used android studio as front end, which is one of the best ways to
develop android application, this project just needed a laptop with 4 GB ram, and
software sublime, PHP and XAMPP as web server and mysqli as backend. There
are really very easy to organize and no more extra cost is needed. And in future
also, this system is easy to modify using the same. This shows the system is
technically feasible.

 Economic Feasibility

The developing system must be justified by cost and benefit. Criteria


to ensure that effort is concentrated on a project, which will give best, return at
the earliest. One of the factors which affect the development of a new system is
the cost it would require. Since the system developed as part of project work,
there is no manually cost to spend for the proposed system. Also, all the
resources are already available, it gives an indication that the system is
economically possible for development. The analyses raise financial and economic
questions during the preliminary investigation to estimate the following:

 The cost to conduct a full systems investigation

~ 22 ~
 The cost of hardware and software for the class of application of the
project being considered.
 The benefits in the form of reduced costs or fewer costly errors.
 The cost if nothing changes.
To be judged feasible, a proposal for the specific project must pass all
these tests, otherwise it is not considered as a feasible project.

5. SYSTEM DESIGN

5.1 INTRODUCTION

System analysis is one of the important activities which are to be


completed before starting the activities like designing, coding etc. If we will not do
the analysis part with ample importance or if we skip some functional areas of
the system at the time of system analysis it is sure that the system developed by
using the data obtained from that case not work in a proper way. Analysis is the
first step towards solving the problem statement. It deals with devising a precise,
concise, understandable and correct modal of the real system. Analysis helps to
understand the requirements and the real-world environment in which the
system will exist. The result of analysis should understand the problem as a
preparation for design.

~ 23 ~
The analysis model addresses the three aspects of the objects.

 Static Structure
 Sequencing of Interaction.

 Data Transformations.

5.2 FUNDAMENTAL DESIGN CONCEPT

System design is the process of developing specifications for a candidate


system that meet the criteria established in the system analysis. Major step in
system design is the registration of customers and workers separately and the
interaction between them, in a form applicable to the user.

The main objective of the system design is to use the package easily by
any mobile operator. System design involves various stages as:

 Profile Creation
 Requesting
 Approval
 Chat
 Complaints

System Design is the creative act of invention, developing new inputs, a


database, offline files, method, procedures and output for processing business to
meet an organization objective. System design builds information gathered during
the
Requiremen
ts
Definition
System and
S/w Design

Implementati
on & Unit
tttttttestingTes
ting
Integration &
system testing

~ 24 ~
Operation &
Maintenance
system analysis.

Figure 2: Waterfall Model


Requirement Analysis and definition
The system's services, constraints and goals are established by
consultation with the system users. They are defined in a manner, which is
understandable, by the users and development staff.

System and software design


The system design process partitions the requirement to either
hardware or software system. It establishes overall system architecture. Software
design involves representing the software systems functions in a form that may
be transformed in to one or more executable programs.

Implementation and unit testing

During this stage, the software design is realized as a set of programs or


programs units. Unit testing involves that each unit meets its specification.

Integration and system design

The individual program units or programs are integrated and tested as a


complete system to ensure that the software requirements have been met. After
testing, the software system is delivered to the customer.

Operation and maintenance


Normally this is the longest life cycle phase. The system is installed
and put into practical use. Maintenance involves correcting errors which were not
discovered in earlier stages of life cycle, improving the implementation of system
units and enhancing the system's services as new requirements are discovered.

5.3 INPUT DESIGN

Input design is the primary step in system design. Input is the process of
converting a user-oriented description of the input to a computer-based system.

~ 25 ~
It is a part of overall system design which requires very careful attention. The
objective of input design is to create an input layout that is easy to follow and
does not include operating errors. Input design is the link that ties the
information system into the world of its users.
● An experiment is a method to get an answer to a problem, which is
obtained from proper interpretation of a set of observations. For en-
tering these observations appropriate messages will be displayed on
the screen. According to this message the user can enter the data
for this suitable data entry screen. In the proposed system, the va-
lidity of checking inputs is available.
● If not valid, a message will be displayed on the screen and the user
can again key for correct input so that only the valid data will be
displayed by the system. Objective during inputs design are as fol-
lows:
• Produce cost effective method input.
• Achieve high-level accuracy.
• Ensure that inputs are free of ambiguity.
The screens are designed in such a way that the user can find the needed
components like options, actions etc. with ease of use. The input design is the
link between the information system and the user. It comprises developing
specification and procedures for data preparation and those steps that are
necessary to put input data into a usable form for processing data entry. The
design of input focuses on controlling the amount of input required, controlling
errors, avoiding delay, avoiding extra steps and keeping the process simple.

5.4 OUTPUT DESIGN

The output is the most important and direct source of information to the
user. The output should be provided in a most efficient formatted way. The
output design has been done so that the results of processing should be
communicated to the user. Effective output design will improve the clarity and
performance of outputs. Output is the main reason for developing the system and
the basis on which they will evaluate the usefulness of the application. Output
design phase of the system is concerned with the convergence of the information
to the end user-friendly manner. The output design should be efficient,
~ 26 ~
intelligible so that system relationship with the end user is improved and thereby
enhancing the process of decision making. The various types of outputs required
by most systems are:
● External output: Whose destination is outside the organization and
which requires special attention.
● Internal output: Whose destination is within the organization and
which requires careful design because they are the user's main in-
terface with the computer.
● Operational output: Whose use is purely within the computer de-
partment.
● Interactive output: Which involves the user in communicating with
the computer.

5.7 CONCEPTUAL SYSTEM DESIGN

After study and the analysis of the existing system the functional
operational requirements were identified. Based on these requirements the
conceptual model of the system is designed. The objective of the system design is
to improve the existing system or design a new system with improved facilities.

 Data Flow Diagram

A Data Flow Diagram (DFD) is a graphical representation of flow of data through


an information system, modelling its process aspects. Often, they are preliminary
steps used to create the overview of a system which can later be elaborated. DFD
is also used for visualization of data processing (Structured design).
A DFD shows what kind of information will be input to and output from the
system, where the data will come from and go to and where the data will be
stored. It does not show information about the timing of the process, or
information about whether the process will operate in sequence or in parallel.

Symbol Name Function

Process Performs some transformation of


input data to yield output data.
~ 27 ~
Data Flow Used to connect processes to each
other, to sources or sinks; the
arrow head indicates direction of
dataflow.
Source A source of system inputs or sinks
of system outputs.
or sink
(External
Entity)
Data store A repository of data

The DFD at the simplest level is referred to as the context analysis


diagram. These are referred to as explaining its process in detail. Processes
are numbered for easy identification and the data stores, source and
destination of data are normally labelled in block letters. Each data flow is
labelled for easy understanding.

Level 0

Level 1 Admin

~ 28 ~
Level 2 Seller

Level 3 Buyer

~ 29 ~
5.6 TABLE DESIGN

Database design manages large bodies of information. Database is the


collection of related data. It provides safety information. A database is a collection
of interrelated data stored with minimum redundancy to save many users quickly
and effectively. Databases run parallel without application design.

Data Normalization
The normalization simplifies the entries, removing redundancies from the
system data and finally builds a data structure, which is both flexible and
adaptable to the system. Normalization usually involves dividing a database into
two or more tables and defining relationships between the tables. The objective is
to isolate data so that additions, deletions, and modifications of a field can be
made in just one table and then propagated through the rest of the database via
the defined relationships.
The different normal forms applied during the design of the database are:
● First Normal Form: A relationship is said to be in first normal form if and
only if it satisfies the constraints that it contains atomic values. It states
that the domain of an attribute must include only atomic (simple, indivisi-
ble) values and that the value of any attribute in a tuple must be a single

~ 30 ~
value from the domain of that attribute. It was defined to disallow multival-
ued attributes, composite attributes, and their combinations. First normal-
ization used in all tables in the database.

● Second Normal Form: A relationship is said to be in second normal form if


it satisfies the 1NF condition for the primary key and every non-primary
key attribute of the relation should not depend on the primary key alone.
Second normal form (2NF) is based on the concept of full functional depen-
dency. A functional dependency X - Y is a fully functional dependency if re-
moval of any attribute A from X means that the dependency does not hold
any more. This normalization can be used in all the tables in the database
because all the tables contain a primary key.

● Third Normal Form: A relationship is said to be in third normal form if


and only if it satisfies all the 2NF conditions and non-key attributes of the
relation should not depend on other non-key attributes. Third normal form
(3NF) is based on the concept of transitive dependency. A functional depen-
dency X ~ Y in a relation schema R is a transitive dependency if there is a
set of attributes Z that is neither a candidate key nor a subset of any key of
R, and both X -Z and Z –Y hold. This normalization can be used in tables.
Tables

 TABLE: tbl_login

SL Attribute Name Data type Constrains


No
1 login_id INT(11) Primary Key
2 username VARCHAR(20)
3 password VARCHAR(20)
4 role INT(11)
 TABLE: tbl_register

SL Attribute Name Data type Constrains


No
1 register_id INT(11) Primary Key
2 name VARCHAR(20)
3 email VARCHAR(20)
4 Mobile_no VARCHAR(20)
~ 31 ~
5 login_id INT(11)

 TABLE: tbl_auction

SL Attribute Name Data type Constrains


No
1 auction_id INT(11) Primary key
2 product_id INT(11)
3 user_id INT(11)
4 auction_price VARCHAR(20)

 TABLE: tbl_product

SL Attribute Name Data type Constrains


No
1 product_id INT(11) Primary Key
2 product_name VARCHAR(50)
3 product_desc VARCHAR(500)
4 price VARCHAR(20)
5 start_time Date
6 end_time Date
7 image VARCHAR(500)
8 user_id INT(11)

5.8 VALIDATION AND CHECKS

Software validation is achieved through a series of tests that demonstrate


conformity with requirements. Validation succeeds when software functions in a
manner that can be reasonably expected by the customer. Here used line by line
checking for to find errors. Comment line facility is used for checking errors.
Testing is necessary for the success of the system. During testing, a program to
be tested is executed with a set of test data and the output of the program for test
data is evaluated to determine if the programs are performing as expected.
Validation means checking the quality of software in both simulated and
live environments. System validation ensures that the user can in fact match
his/her claims, especially system performance. True validation is verified by

~ 32 ~
having each system tested. First the application goes through a phase often
referred as alpha testing in which the errors and failures based on simulated user
requirements are verified and studied. The modified software is then subjected to
phase two called beta testing in the actual user’s site or live environment. After a
scheduled time, failures and errors are documented or final correction and
enhancements are made before the package is released.

6.SYSTEM DEVELOPMENT

System development is a series of operations performed to manipulate data


to produce output from a computer system. This highly depends on the
programming language used. Programming techniques include the concept of
"object-oriented programming." Object-oriented programming centers on the
development of reusable program routines (modules) and the classification of data
types (numbers, letters, dollars, etc.) and data structures (records, files, tables,
etc.). Linking pre-scripted module objects to predefined data-class objects reduces
development times and makes programs easier to modify. The development phase
involves converting design specifications into executable programs. Effective
development standards include requirements that programmers and other project
participants discuss design specifications before programming begins. The
procedures help ensure programmers clearly understand program designs and
functional requirements. The principle activities performed during the development
phase can be divided into two major related sequences. They are:

 External system development.


 Internal system development.

The major External system development activities are:


 Implementation
 Planning
 Preparation of manual
~ 33 ~
 Personal training
 Equipment acquisition
 Installation

The major system internal development activities are:


 Computer program development
 Performance testing

7. SYSTEM CODING AND TESTING

7.1 SYSTEM TESTING

Testing is vital to the success of the system. It makes a logical assumption that
if all the parts of the system are correct, the goal will be successfully achieved. It
is the stage of implementation, which ensures that the system works accurately
and effectively before the live operation commences. It is a confirmation that all
are correct and an opportunity to show users that the system must be tested and
show that the system will operate successfully and produce expected results
under expected conditions. Software testing is a crucial element of software
quality assurance and represents the unlimited review of specification, design
and coding. Testing represents an interesting anomaly for the software. During
the earlier definition and development phase, it was attempted to build the
software from an abstract concept to implement. System testing is designed to
uncover weaknesses that are not found in the earlier tests. This includes forced
system failure and validation of the total system, as its users in the operational
environment will implement it. Generally, it begins with a low volume of
transactions based on live data. The volume is increased until the maximum level
for each transaction type is reached. The total system is tested for recovery and
fallback after various major failures to ensure that no data are lost during the

~ 34 ~
emergency. All this is done with the old system still in operation. After the
candidate system passes the test, the old system is discontinued. System testing
involves unit testing, integration testing, acceptance testing. Careful planning
and scheduling are required to ensure that modules will be available for
integration into the evolving software product when needed.
A test plan has the following step:
● Prepare test plan
● Specify conditions for user acceptance testing
● Prepare test data for program testing
● Prepare test data for transaction path testing
● Plan user training
● Compile/assemble programs
● Prepare job performance aids
System testing is the stage of implementation that is aimed at ensuring that the
system works accurately and efficiently before live operation commences. The
system on a whole was tested for the following:
● Validation of inputs
● Referential integrity test
● Sequential tests
● Consistency of the application
System testing, asks a logical assumption that if all the parts of the system are
correct, the system will be successfully achieved. The objective of testing is to
discover errors. To fulfill these objectives a series of tests were planned and
executed. The logical design and the physical design should be thoroughly and
continually examined on paper to ensure that they will work when
implementation should be a confirmation that all is correct and an opportunity to
show users that the system works.

 Black Box Testing

Black box testing treats the software as black box without any
Understanding of internal behavior. It aims to test the functionality according to
the requirements. Thus, the tester inputs data and only sees the output from the
test object. This level of testing usually requires through test cases to be provided
to the tester who then can simply verify that for a given input, the output value is

~ 35 ~
the same as the expected value specified in the test case. There are many
approaches to software testing. Reviews, walkthroughs or inspections are
considered as static testing, whereas actually running the program with a given
set of test cases in a given development stage is referred to as dynamic testing.
Software testing is used in association with verification and validation:
● Verification: Have we built the software, right.
● Validation: Have we built the right software.

 White Box Testing

White box testing, however, is the tester access to the internal data
Structures, codes and algorithms. White box testing methods include creating
tests to satisfy some code coverage criteria. White box testing includes all static
testing. This testing is based on knowledge of the internal logic of an application’s
code. Internal software and code working should be known for this type of
testing. Tests are based on coverage of code statements, branches, paths,
conditions.

7.2 LEVELS OF TESTING

 Unit Testing

Unit testing is usually conducted as part of a combined code and unit test
phase of the software lifecycle, although it is not uncommon for coding and unit
testing to be conducted as two distinct phases. All modules were tested
individually as soon as they were completed and were checked for their correct
functionality. Unit testing deals with testing a unit as a whole. This would test
the interaction of many functions but confine the test within one unit. This
testing is carried out during the programming stage itself. In this testing step
each Module is found to be working satisfactorily as regard to the expected
output from the module.
Precisely In unit testing:
1. Module interface is tested to ensure that information properly flows
into and output of the program under test.

~ 36 ~
 Local data structures are examined to ensure that data stored
temporarily maintains its integrity during all steps in algorithm
execution.
 Boundary condition is tested to ensure that the module operates properly
at boundaries established to limit or restrict processing.
 All independent paths through the control structures are executed to
ensure that all statements in the module have been executed at least
once.
 Error handling paths are also tested.
Unit testing focuses verification effort on the smallest unit of software design, the
module. Here, there are basically two modules: customer side and worker side.
Both are coded and tested whether they are working. A module is taken as the
part after registration, where customers and workers have different dashboards
and settings on them. Module interfaces, local data structure, boundary
conditions, and all independent paths and last but not the least, all error
handling paths were verified by inputting false data. Tests of data flow across
each module interface of this software were done before any other test was
initiated.

 Integration Testing

Integration testing is a systematic technique for testing to overcome the errors


associated within the interface. In this System all the modules such as login,
registration, worker module, customer module in android and the final hardware
and software are combined or integrated and then the entire program is tested as
a whole. Integration checks if the modules are combinable each other and
whether there occur any unexpected situations. Thus, in the integration testing
step all the errors in the implementation of the system are corrected. Data can be
lost across an interface; one module can have an adverse effect on others; sub-
function when combined may not produce the desired major functions;
integration testing is a systematic testing for constructing the program structure.
The objective is to take unit tested modules and to combine them and test it as a
whole.
● The system contains various components and they have to be com-
bined and tested.

~ 37 ~
● Android part is integrated as different pages are combined and
tested.
● The modules are combined and tested.
● Different PHP parts and XAMPP are combined and tested.

There are two strategies of Integration testing.


 Top down integration
 Bottom up integration

 Validation Testing

Validation testing is done to ensure complete assembly of the error-free


software. Validation can be termed successful only if it functions in manner that
is reasonably expected by the customer.
Under Validation test:
 Alpha testing
 Beta testing
Alpha testing is where the end user tests the system rather than the
developer, but in a controlled environment. The software is used on a natural
setting with the developer monitoring the user using the system. The developer
records the errors and usage problems encountered by the user.
Thus, as I have developed this system, so that I gave different values as
demo and checked whether all units are working properly.
The sales person conducts beta testing at one more site. The developer is
not present during the tests. Hence, beta test can be said as the live application
of the software on an environment that cannot be controlled by the developer.
The sales person takes down the problems encountering during beta testing and
reports these to the developer at regular intervals. The developer makes suitable
modifications of the software henceforth.
Here beta testing is also done by me, by giving values like original, that
similar to the actual persons entry. And also, the application was installed on
different devices and tried to run. As it worked on those devices and entered
different values like original existing persons as workers and customers.

 System Testing

~ 38 ~
System testing is actually a series of different tests whose primary
purpose to fully exercise the computer-based system. Each test works to verify
that all system elements have been properly integrated.
Types of system tests are:
1. Recovery Testing
2. Security Testing
3. Stress Testing.
4. Performance Testing

7.3 TESTING THE SYSTEM


We test the system by running it in several ways by inputting various
values in the respective forms.
The main concerns in our testing are following:
 Browse compatibility: This test validates consistent applications performance
on variety of browser type and configuration.
 Functional correctness: These tests validates that the application function
correctly.
 Integration: These test the integration between browsers and servers,
applications and data, hardware and software.
 Usability: These test the overall usability of a web page or a web application,
including appearance clarity and navigation.
 Security: These test the adequacy and correctness of security controls
including access control and authorizations.
 Performance: These test the performance of the web applications under load.
 Verification of codes: This validate that the code used in building application
has been used in a correct manner.

8. SYSTEM IMPLEMENTATION & MAINTENANCE


~ 39 ~
8.1 SYSTEM IMPLEMENTATION

Crucial phase in the systems life cycle is the successful implementation


of the new system design. Implementation means converting a new system into
operation.
In the implementation phase, the team builds the components either
from scratch or by composition. Given the architecture document from the design
phase and the requirement document from the analysis phase, the team should
build exactly what has been requested, though there is still room for innovation
and flexibility. For example, a component may be narrowly designed for this
particular system, or the component may be made more general to satisfy a
reusability guideline. The architecture document should give guidance.
Sometimes, this guidance is found in the requirement document the
implementation phase deals with issues of quality, performance, baselines,
libraries, and debugging. The end deliverable is the product itself.
Implementation is the stage in the project where the theoretical design is
turned into a working system and is giving confidence on the new system for the
users that it will work efficiently and effectively. It involves careful planning,
investigation of the current system and its constraints on implementation, design
of methods to achieve the changeover, and evaluation of change over methods.
Apart from planning, major tasks of preparing the implementation are education
and training of users.
There are three types of implementation:
● Implementation of a system to replace a manual system.
● Implementation of a new system to replace an existing one.
● Implementation of a modified application to replace an existing one,
using the same computer.
The implementation plan includes a description of all the activities that
must occur to implement the new system and to put it into operation. It identifies
the personnel responsible for the activities and prepares a time chart for
implementing the system. The implementation plan consists of the following
steps. List all files required for implementation.

~ 40 ~
● Identify all data required to build new files during the implementa-
tion.
● List all new documents and procedures that go into the new system.

The implementation plan should anticipate possible problems and must be able
to deal with them. The usual problem may be missing documents; mixed data
formats between current and
files, errors in data translation, missing data etc... System implementation is the
final phase i.e., putting the utility into action. Implementation is the state in the
project where theoretical design turned into a working system. The most crucial
stage is achieving a new successful system and giving confidence in the new
system that it will work efficiently and effectively. The system is implemented only
after thorough checking is done and if it is found working according to the
specification. It involves careful planning, investigation of the current system and
constraints on implementation, design of method to achieve.

8.1 SYSTEM MAINTENANCE

The maintenance phase of the software cycle is the time in which the software
products perform useful work. After a system is successfully implemented, it
should be maintained in a proper manner. System maintenance is an important
aspect in the software development life cycle. The system maintenance is to make
it adaptable to the changes in the environment. There may be social, technical
and other environmental changes, which affect the systems behavior. Software
product enhancements may involve providing new functional capabilities,
improving user displays and mode of interaction, upgrading the performance
characteristics of the system. So only through proper system maintenance
procedures, the system can be adapted to come up with these changes. The first
maintenance activity occurs because it is unreasonable to assume that testing
will uncover all latent errors in a large software system. During the use of any
large program, errors will occur and be reported to the developer. The process
that includes the diagnosis and connection of one or more errors is called
corrective maintenance. The second activity that contributes to a definition of
maintenance occurs because of rapid change that is encountered in every aspect
~ 41 ~
of computing. Therefore, adapting maintenance is an activity that modifies
software to properly interface with a changing environment is both necessary and
commonplace. The third activity that may be applied to the definition of
maintenance occurs when a software package is successful. As the software is
used, recommendations for new capabilities, modification for existing functions,
and general enhancement are received from the user. To satisfy requests in this
category, perfective maintenance is performed. The fourth maintenance activity
occurs when the software is changed to improve maintainability or reliability or to
provide a better basis for future enhancements.

9. FORMS

~ 42 ~
~ 43 ~
~ 44 ~
~ 45 ~
~ 46 ~
~ 47 ~
10.SAMPLE CODE
REGISTER.XML

<?xml version="1.0" encoding="utf-8"?>

<ScrollView

android:layout_width="match_parent"

android:layout_height="match_parent"

android:background="#F4F6F7"

xmlns:android="http://schemas.android.com/apk/res/android">

<androidx.constraintlayout.widget.ConstraintLayout

xmlns:android="http://schemas.android.com/apk/res/android"

xmlns:app="http://schemas.android.com/apk/res-auto"

xmlns:tools="http://schemas.android.com/tools"

android:layout_width="match_parent"

android:layout_height="match_parent"

android:background="#F4F6F7"

android:padding="20dp"

tools:context=".register">

<LinearLayout

android:layout_width="match_parent"

android:layout_height="wrap_content"

android:orientation="vertical"

android:padding="10dp"

app:layout_constraintBottom_toBottomOf="parent"

app:layout_constraintEnd_toEndOf="parent"

app:layout_constraintHorizontal_bias="0.6"

~ 48 ~
app:layout_constraintStart_toStartOf="parent"

app:layout_constraintTop_toTopOf="parent"

app:layout_constraintVertical_bias="0.539">

<TextView

android:id="@+id/textView2"

android:layout_width="wrap_content"

android:layout_height="wrap_content"

android:layout_gravity="center"

android:text="Register"

android:textStyle="bold"

android:layout_marginBottom="40dp"

android:textColor="#800080"

android:textSize="40sp" />

<EditText

android:id="@+id/name"

android:background="@drawable/rounded_white"

android:layout_width="match_parent"

android:hint="Name"

android:textColorHint="@color/white"

android:padding="10dp"

android:layout_height="60dp"

android:layout_marginTop="20dp" />

<EditText

android:id="@+id/email"

android:background="@drawable/rounded_white"

~ 49 ~
android:layout_width="match_parent"

android:hint="E-mail"

android:textColorHint="@color/white"

android:padding="10dp"

android:layout_height="60dp"

android:layout_marginTop="20dp" />

<EditText

android:id="@+id/mobile_no"

android:background="@drawable/rounded_white"

android:layout_width="match_parent"

android:hint="Mobile No"

android:textColorHint="@color/white"

android:padding="10dp"

android:layout_height="60dp"

android:layout_marginTop="20dp" />

<EditText

android:id="@+id/username"

android:background="@drawable/rounded_white"

android:layout_width="match_parent"

android:hint="Username"

android:textColorHint="@color/white"

android:padding="10dp"

android:layout_height="60dp"

android:layout_marginTop="20dp" />

<EditText

~ 50 ~
android:id="@+id/password"

android:background="@drawable/rounded_white"

android:layout_width="match_parent"

android:hint="password"

android:inputType="textPassword"

android:textColorHint="@color/white"

android:padding="10dp"

android:layout_height="60dp"

android:layout_marginTop="20dp" />

<Button

android:id="@+id/register"

android:background="@drawable/rounded_white"

android:layout_width="wrap_content"

android:layout_height="wrap_content"

android:layout_gravity="center"

android:layout_marginTop="30dp"

android:textColor="@color/white"

android:textSize="30sp"

android:text="Register" />

<TextView

android:id="@+id/signin"

android:text="Login"

android:layout_marginTop="20dp"

android:layout_gravity="center"

android:textColor="#800080"

~ 51 ~
android:layout_width="wrap_content"

android:layout_height="wrap_content"/>

</LinearLayout>

</androidx.constraintlayout.widget.ConstraintLayout>

</ScrollView>

REGISTER.JAVA

package com.futuralab.auction;

import androidx.appcompat.app.AppCompatActivity;

import android.content.Intent;

import android.os.Bundle;

import android.view.View;

import android.widget.Button;

import android.widget.EditText;

import android.widget.TextView;

import android.widget.Toast;

import com.android.volley.Request;

import com.android.volley.RequestQueue;

import com.android.volley.Response;

import com.android.volley.VolleyError;

import com.android.volley.toolbox.JsonObjectRequest;

import com.android.volley.toolbox.Volley;

~ 52 ~
import org.json.JSONException;

import org.json.JSONObject;

import java.util.HashMap;

import java.util.Map;

public class register extends AppCompatActivity {

TextView login;

EditText name,email,mobile_no,username,password;

Button register;

String u_name,u_email,u_mobile,u_username,u_password;

@Override

protected void onCreate(Bundle savedInstanceState) {

super.onCreate(savedInstanceState);

setContentView(R.layout.activity_register);

getSupportActionBar().hide();

name=findViewById(R.id.name);

email=findViewById(R.id.email);

mobile_no=findViewById(R.id.mobile_no);

username=findViewById(R.id.username);

password=findViewById(R.id.password);

register=findViewById(R.id.register);

login=findViewById(R.id.signin);

login.setOnClickListener(new View.OnClickListener() {

@Override

public void onClick(View view) {

~ 53 ~
Intent intent=new Intent(register.this,login.class);

startActivity(intent);

});

register.setOnClickListener(new View.OnClickListener() {

@Override

public void onClick(View view) {

u_name=name.getText().toString();

u_email=email.getText().toString();

u_mobile=mobile_no.getText().toString();

u_username=username.getText().toString();

u_password=password.getText().toString();

String emailPattern = "[a-zA-Z0-9._-]+@[a-z]+\\.+[a-z]+";

String MobilePattern = "[0-9]{10}";

if(u_name.equals(""))

Toast.makeText(register.this, "Enter name",


Toast.LENGTH_SHORT).show();

else if(!u_email.matches(emailPattern))

Toast.makeText(register.this, "Enter email",


Toast.LENGTH_SHORT).show();

else if(!u_mobile.matches(MobilePattern))

Toast.makeText(register.this, "Enter mobile no",


Toast.LENGTH_SHORT).show();
~ 54 ~
}

else if(u_username.equals(""))

Toast.makeText(register.this, "Enter username",


Toast.LENGTH_SHORT).show();

else if(u_password.equals(""))

Toast.makeText(register.this, "Enter password",


Toast.LENGTH_SHORT).show();

else

String base_url=getResources().getString(R.string.base_url);

String url=base_url+"register.php";

Map<String,String> params=new HashMap<String,String>();

params.put("name",u_name);

params.put("email",u_email);

params.put("mobile_no",u_mobile);

params.put("username",u_username);

params.put("password",u_password);

JSONObject parameter=new JSONObject(params);

JsonObjectRequest jsonObjectRequest=new
JsonObjectRequest(Request.Method.POST, url, parameter, new
Response.Listener<JSONObject>() {

~ 55 ~
@Override

public void onResponse(JSONObject response) {

try {

int success=response.getInt("success");

if(success==1)

Toast.makeText(register.this, "Register Success",


Toast.LENGTH_SHORT).show();

else

Toast.makeText(register.this, "Register Failure",


Toast.LENGTH_SHORT).show();

} catch (JSONException e) {

e.printStackTrace();

}, new Response.ErrorListener() {

@Override

public void onErrorResponse(VolleyError error) {

);

~ 56 ~
RequestQueue requestQueue=
Volley.newRequestQueue(getApplicationContext());

requestQueue.add(jsonObjectRequest);

});

LOGIN.PHP

<?php

include "db.php";

$jsonarray=json_decode(file_get_contents('php://input'),true);

@$username=$jsonarray['username'];

@$password=$jsonarray['password'];

$query=mysqli_query($conn,"SELECT * FROM tbl_login WHERE


username='$username' and password='$password'");

$result=mysqli_fetch_assoc($query);

if(mysqli_num_rows($query)>0)

$result['success']=1;

echo json_encode($result);

~ 57 ~
}

else

$result['success']=0;

echo json_encode($result);

?>

~ 58 ~
11.CONCLUSION
Conclusion is the summing up of arguments described in this article. This
software provides a user-friendly approach towards the system. This system has
been well developed and when implemented, is bound to satisfy most of the
requirements. Painstaking efforts have been taken to make the software
impeccable and upgradeable. There is a hope that this software will be utilized to
its maximum and will do a good job in the long run. With blessings of God, the
exertions are hoped to bear fruit. The program for carrying out various activities
have been run and successfully tested to ensure that the software developed
meets the needs satisfactorily. Any users can process the Android Application
without any experience in any software products. The major advantages of
software products are:
 Fast retrieval of entries from database
 Cost effective.
 Quick implementation results.
 Available in diskette.
 Convenience
 Ubiquity.
The project is developed as a model for manual system, which will
surely help if it is kept in act. The drawbacks of the system were analyzed and
carefully studied. The new system was designed and its reusability checked at
later stage. System has been successfully tested and implemented with running
on different mobile phones and it is seen that the system has high degree of
accuracy and user friendliness. The system is user-friendly system and further
changes can be incorporated into the system easily.

The project “BELL-IT” has been developed, tested, documented and implemented
successfully. The main objective of the system was brought into effect. The
system is developed in ANDROID and PHP as front-end tool and SQL Server as
back end tool. Any system that has been used for a number of years gradually
decays and becomes less effective because of the changes in environment to
which it has to adopt. For a time, it is possible to overcome problems by

~ 59 ~
amending and minor modifications to acknowledge the need of fundamental
changes.

12. BIBLIOGRAPHY

12.1 REFERENCES

1. Learning PHP.MySQLi,AJAX and CSS:A step-by-step guide to creating Dy-


namic websites –by Robin Nixon
2. Learning PHP, MySQLi and AJAX with query.CSS and HTML5-by OReilly
3. PHP and MySQLi for Dynamic website: Visual QuickPro guide by Larry Ull-
man
4. Bootstrap reference guide: Quickly references all classes and common code
snippets (Bootstrap 4 tutorial Book2) [Print Replica] Kindle Edition

12.2 WEB REFERENCES

 FOR WEB LINKING

https://www.w3schools.com/php/func_filesystem_link.asp

 FOR SQL

https://www.php.net/manual/en/book.mysqli.php

 FOR PHP

https://www.w3schools.com/php/
 FOR AJAX

https://www.guru99.com/php-ajax.html

~ 60 ~
~ 61 ~

You might also like