Você está na página 1de 71

Bug Reporting System

Project Report

Submitted By

Vishal Kumar.S

Reg.No:08bit58

Under the Guidance of

Mrs. C.Bhuvaneshwari MCA, M.Phil

In partial fulfillment of the requirements for the Award of the Degree of

Bachelor of Science in Information Technology

School of Information Technology & Science


Dr. G R Damodaran College of Science
(Autonomous, affiliated to the Bharathiar University)
Re –accredited at the ‘A’ Grade level by the NAAC
An ISO 9001:2008 Certified Institution
Coimbatore 641-014
APRIL – 2011
CERTIFICATES
School of Information Technology & Science
Dr. G R Damodaran College of Science
(Autonomous, affiliated to the Bharathiar University)
Re –accredited at the ‘A’ Grade level by the NAAC
An ISO 9001:2008 Certified Institution
Coimbatore 641 014

Certificate

This is to certify that this project report entitled

Bug Reporting System

is a bonafide record of project work done by

Vishal Kumar. S

Reg. No:08bit58

Submitted in partial fulfillment of the requirements for the degree of

BACHELOR OF SCIENCE IN INFORMATION TECHNOLOGY

_____________

___________________

Faculty Guide Head of the Department


(Guide’s name with Qualification) (HOD Name with Qualification)

Submitted for Viva-Voce Examination held on ____________________

________ _________
Internal Examiner External Examiner
ACKNOWLEDGEMENT
ACKNOWLEDGEMENT

It has been said that gratitude is the memory of heart. My gratitude to all those who helped
me to do this project work is beyond words.

I extend my sincere thanks to Dr. A. PONNUSAMY MA (SW), M.Phil PGDPM DLL


PhD, Principal, Dr. G. R. Damodaran College Of Science, Coimbatore for his
overwhelming support.

I also thank Dr. G. Radhamani MSc., MPhil., PhD., Director for their great support that
helped me in undergoing this project

My sincere thanks is expressed to Mrs. T. Santha MSc., MPhil.,(Ph.D), Head Of


Department, provided valuable guidance and help given for the completion of the project.

I would like to express my gratitude to Mr. K. Joy Fernandes, CEO, SOTHINK


SOURCETEC SOFTWARE, Coimbatore, for permitting to undergo this project work at
their concern and extending all help.

My heart thanks to all Teachers, Friends, and Well-wishers, who through their Support and
Assistance made my Academic Life a Memorable one.

Last but not least, I owe my Parents and Siblings who untiringly gave me strength and
sustenance, without which the dream never has been accomplished.
ABSTRACT
ABSTRACT

This project is shaped with design and development of Testing and Maintains, the
process of software development, Test case and Defect tracking for both development
document and also reports are included. It’s prepared in Windows’XP Environment By
Using Simplest, Flexible and compact PHP with MySQL.

This system provides all details about the Testing, Bug tracking and Reports. That is
first we receive the requirement from customers or New Clients, this is entered into the
Process Instruction, then it is divided into many operations for processing the Testing
Reports.
TABLES OF CONTENT
TABLES OF CONTENT

S.No TITLE P.No

ACKNOWLEDGEMENT iii

ABSTRACT iv

LIST OF TABLES v

LIST OF FIGURES vii

1. INDTRODUCTION 1

1.1 System Environment 2


1.3 Tools & Technologies Used 2

2. SYSTEM ANALYSIS 4

2.1 Project Overview 4


2.2 Existing System 5
2.3 Proposed System 5
2.4 Problem Definition 6

3. DESIGN & DEVELOPMENT PROCESS


3.1 Design Notations 7

3.1.1. Data flow Diagram 7


3.1.2. Structure Chart 8
3.1.3. E-R Diagram 12

3.2 Design process


3.2.1. Input design 12
3.2.2. Output design 16

4. TESTING & IMPLEMENTATIONS

4.1System testing 19
4.2System Implementation 22
4.3System Maintenances 22
4.4 Test Cases 23

5. CONCLUSSION 24

6. FUTURE ENHANCEMENT 25

ANNEXURE

A.1.1 SAMPLE CODINGS 26


A.1.2 SCREEN SHOTS 34

BIBLIOGRAPHY 51
LIST OF TABLES & FIGURES
LIST OF TABLES

TABLE NO TABLE NAME PAGE NO

Test Cases 23

LIST OF FIGURES

FIGURE NO FIGURE NAME PAGE NO

2.1.1 0th Level DFD 8

2.1.2 Admin Level 1 DFD 9

2.1.3 Bug Level 1 DFD 9

2.1.4 Test Level 1 DFD 10

A.1 Admin Login Module 34

A.2 Admin Page 35

A.3 Other Registration 36

A.4 Project Details 37

A.5 Client Details Form 38

A.6 Assign Project 39

A.7 View/Edit Add Employee 40

A.8 Project Details 41

A.9 Test Plan Details 42

A.10 Test Case Details 43

A.11 Bug Details 44

A.12 Priority List 45

A.13 Add Status 46

A.14 View Status 47


A.15 Total Test Plan Report 48

A.16 Total Test Case Report 49

A.17 Total Bug Report 50


INTRODUCTION

1
HARDWARE CONFIGURATION

Processor : Pentium IV

RAM : 256 MB

Hard disk : 40 GB

SOFTWARE CONFIGURATION

Operating system : MS-Windows XP

Front End Tool : PHP

Back End Tool : MySQL

2
TOOLS AND TECHNOLOGIES USED

PHP

A PHP file may contain text, HTML tags and scripts. Scripts in a PHP file are executed
on the server.

PHP is mainly focused on server-side scripting, so you can do anything any other CGI
program can do, such as collect form data, generate dynamic page content, or send and
receive cookies. But PHP can do much more.

MySQL

MySQL, the most popular Open Source SQL database management system, is developed,
distributed, and supported by MySQL AB. MySQL AB is a commercial company, founded
by the MySQL developers, that builds its business by providing services around the MySQL
database management system.

A database is a structured collection of data. It may be anything from a simple shopping


list to a picture gallery or the vast amounts of information in a corporate network. To add,
access, and process data stored in a computer database, you need a database management
system such as MySQL Server. Since computers are very good at handling large amounts of
data, database management systems play a central role in computing, as stand-alone utilities
or as parts of other applications.
SYSTEM ANALYSIS
3
SYSTEM ANALYSIS

PROJECT OVERVIEW

Module Description:
The project is entitled “Bug Reporting System”. This project is fully developed for the
testing team of Software Development Companies. All project’s test particulars are saved
and retrieved by the testing engineers easily. Following are the main modules of the present
system.

 Admin Module
 Testing
 Bug Tracking
 Report

These modules are categorized into different sub modules.

Admin Module

This Admin module is divided into two sub modules


 Login Module
 User Registration

The login module is used for authenticating the existing user and the user
registration module is used to take information like personal details, educational details, and
technical skills and work experience from the users. After the user has registered him he will
be given a login name and password using which he can enter into his work space. It is
helpful to set the security for the project.
Testing

The Testing module is divided into three parts


 Project description module
 Test plan
 Test case
Bug tracking
By using this module we can maintain and track information regarding the bug,
assigned to, status, priority, severity, detected by and detected date etc.
Report
It consists of two modules
 Total test report
 Total bug report
4
Existing System

The existing system is computerization with excel sheet. These systems are
maintained by Software testing total reports. Software testing is a complex process
involving the development and execution of thousands of tests. Often, tests are required for
multiple hardware platforms and software versions. Managing all aspects of the testing
process can be time-consuming and difficult

The Main Function of Software Testing maintenance system is to Accept


Requirement, test plan, test case, and Defect Tracking form various Projects. There are four
steps to provide this System Maintains
Disadvantages Existing System
Existing system is maintaining the information about testing only Excel sheet. Many
processing that can be done by computer as performed manually. The existing system also
uses Test plan, Test case, Defect Tracking, to handle Excel sheet.

This Existing is having problem is like we can’t find out particular test case with in
our time. if the daily report, weekly report and total testing report creation is difficult.

The Excel sheet is not having that much security. Any one can open and edit that test
case.
PROPOSED SYSTEM

Necessity of Proposed System:

Bug Tracking helps you maintain a project database of tests that cover all aspects of
your application’s functionality. To meet the various goals of a project, we organize the tests
from our project database into unique groups.
With Bug Tracking, you maintain a project—a database of tests, from a project, you
can build test sets—groups of tests executed to achieve a specific goal. For example, you
can create a test set that checks a new version of the software, or one that checks a specific
feature. As you execute tests, Test Director lets you report defects detected in the software.
The report creation is difficult in excising system Compare to proposed system.
The difficulties of the existing system and their requirements and the new system
are developed with the following Advantages:

Easy to maintain and manipulate


5
Generate Reports Easily

Generate Information to User

Reduce the manual errors

Problem Definition:

This system provides details about the testing and total information of the software.
All of the forms are designed according to the needs of the users and management's
specification.
The main function of Bug Tracking Maintains is to accept Requirement, test plan,
test case, and Defect Tracking form various Projects. There are four steps to provide this
System Maintains

Types of Process:

I. Writing Test plan

II. Writing Test case & Executing Test Case

III. Bug Tracking

IV. Reports

Test Plan

Test plan is a “living document” throughout the new information is added, and old
information is updated. The major testing activities are the function acceptance and
regression testing. These tests however are performed in a specific order and may be
concurrent.
DESIGN AND DEVELOPMENT PROCESS
6
DESIGN AND DEVELOPMENT PROCESS

DESIGN NOTATIONS

DEVELOPING SOLUTION STRATEGIES:

Analysis is a process of breaking the problems in to the successively manageable


parts for individual study. System analysis is the study of various operations that has to be
done to solve the problems. One aspects of the system analysis is defining the boundaries of
the system and determining whether or not the proposed system should consider other
related system. During the analysis, data are collected on the available files, decision points
and transaction handled by the existing system.
Various tools are available to perform the system analysis. Some of the tools are data
flow diagram, interviews, onsite observation and questionnaires regarding the proposed
system, interviews and DFD are the commonly used tools in analysis. The interviews is the
face-to-face interpersonal role situations in which the designed questions are asked to gather
information’s about the personal area. The interviews are the oldest and most often used
device for gathering information in system analysis. The two main purpose of interviews
are,
 Used exploratory devices to identify relations or verify information.
 To capture the information as it exists.

DATA FLOW DIAGRAM


A data flow diagram is graphical tool used to describe and analyze movement of the
data through a system.

DFD SYMBOLS
In the DFD, there are four Symbols
1. A square define a source or destination system data
2. An arrow identified data flow. It is the pipeline through which the
information flow
3. A circle or a bubble represents a process that transforms
4. Incoming data flow into outgoing data flows
5. An open rectangle is a data store, data at rest or a temporary of data
7
Process that transformation data flow

Source or Destination of data

Data Flow

Data Store

0th Level DFD

1.0
Admin
Details d1 User
Admin User Details User Database
Details
ID,Pas
s Word

2.0
Test
Databas Test
d1 Test Plane
e case Login
Test Id
Detail
s

3.0
Bug
d1 Databas
R e p o rt
defect Tracking Defect e
Details
8
Admin Level 1 DFD

Admin 1.0
Details User Details
User
Admin Database
Register

User
Id,PassWord

2.0
Project
Descripti on
R ep o rt
Report project Login
Details Details

Bug Level 1 DFD

1.0

Bug Bug Information D1 Test


D1 database Database
Bug Test Id
Details

Defect id

2.0 2.1 Test


Bug Information
D2 databas
Defect tracking Store Defect Defect e
Tracking
Details Details
Bug
Informatio
n

R ep o r t
10
Test Level 1 DFD:

1.0 Test
Test Plane
Details Plane Id Test
Test Plane Fetching D1
Databas
e
Test Case Id
Test Plane

2.0 2.1 3.1

Write Test
Test Case Test Store
Case Test
Case Case
Details

3.0

Test Plane Execute Test


Test Plane case
Details
11
Overall DFD:

Admin 1.0
Details User Details
User
Admin Database
Register

User
Id,PassWord

1.1
Project
Description
project Login
Details

2.0
Test Plane Test Plane
Details Id
Test Plane D1 Test
Fetching
Database

Test Case Id Test Id


Test Plane
3.0

Bug Bug
2.1 2.2 2.4 D1 databas Information
e Bug
Details
Defect
Test Case Write Test Case Store id
Test Case Test Case
Details
3.1 3.2

Bug
Defect D2
Store Defect Defect databa
tracking Trackin se
Details
g Detail Bug
2.3
s Informat
ion
Test Plane Execute Test
Test Plane case
Details R ep ort
12
ER DIAGRAM:

3.2DESIGN PROCESS
INPUT DESIGN
Input design is a part of overall system design. The main objective during the
input designs the input designs is given bellow:
 To produce a cost-effective method of input.
 To achieve the highest possible level of accuracy
 To ensure that the input is acceptable and understood by the user.
INPUT STAGES
The main input stages can be listed bellow:
 Project Details
 Test Plane
 Test Case
 Bug Tracking
INPUT TYPES
13
It is necessary to determine the various types of inputs can be categorized as follows:
 External inputs, which are prime inputs for the system
 Internal inputs, which are user communication with the system.
 Operational, which are computer department’s communication to the system
 Interactive, which are inputs entered during a dialogue
INPUT MEDIA
At this stage choice has to be made the input media. To conclusion about the
input media consideration has to be given to:
 Type of output
 Flexibility of format
 Speed
 Accuracy
 Verification methods
 Rejection rates
 Ease of correction
 Storage and handling requirements
 Security
 Easy to use
 Portability
Keeping in view the above description of the input types and input media, it can be
said that most of the inputs are of the form of internal and interactive. As input data is to be
the directly keyed in by the user, the keyboard can be considered to be the most suitable
input device.
ERROR AVOIDANCE
As this stage care is to be taken to ensure that input data remains accurate form the
stage at which it is recorded up to the stage in which the data is accepted by the system. This
can be achieved only by means of careful control each time the data is handled
14
ERROR DETECTION
Even though every effort is make to avoid the occurrence of errors, still a small
proportion of errors are always likely to occur, these types of errors can be discovered by
using validation to check the input data.
DATA VALIDATION
Procedures are designed to detect error in data at a lower level of detail. Data
validations have been included in the system in almost every area where there is a
possibility for the user to commit errors. The system will not accept invalid data. Whenever
an invalid data is keyed in, the system immediately prompts the system will accept the data
only if the data is correct. Validations have been included where necessary.
The system is designed to be a user friendly one. In other words the system has been
designed to communicate effectively with the user. The system has been designed with
popup menus.
USER INTERFACE DESIGN

It is essential to consult the system users and discuss their needs while designing the
user interface. The user interface system can be broadly classified as:
 User initiated interface the user is in charge. Controlling the computer-
initiated interface, the computer selects the next stage in the interaction.
 Computer initiated interfaces
In the computer initiated interfaces the computer guides the progress of the
user/computer dialogue. Information is displayed and tJhe user response of the computer
takes action or display further information.
USER INITIATED INTERFACE
User initiated interface fall into two approximate classes:
 Command driven interfaces: in this type of interface the user inputs
commands or queries which are interpreted by the computer.
 Forms oriented interface: the user calls up an image of the form to his/her
screen and fills in the form. The forms oriented is chosen because it is the
best choice.
15
COMPUTER-INITIATED INTERFACE
The following computer-initiated were used:
 The menu system for the user is presented with a list of alternatives and the
user chooses on: of alternatives.
 Question –answer type dialog where the computer asks question and takes
action based on the basis of users reply.
Right form the start the system is going to be menu driven; the opening menu
displays the available options. Choosing one option gives another popup menu with more
option. In this way every option leads the users to data entry where the user can key in the
data
ERROR MESSAGE DESIGN
The design of the error massages is a important part of the user interface design. As
user is bound to commit some error or other will design a system should be design to be
helpful by providing the user information regarding the error he/she has committed. This
application is able to produce the output at different modules of different inputs.
PERFORMANCE REQUIREMENT
Performance is measured in terms of report generation weekly and monthly.
Requirement specification is play important parts in the analysis of the system. Once the
requirement specifications are properly given, it is possible to design the system, which will
fit into the required environment. It rests largely in the par of the user of existing system to
give the requirement specification because they are the people who finally use the system.
This is because the requirements have to be known during the initial stages so that the
system can be designed according to those requirements. It is very difficult to change the
system once it has been designed and on the other hand designing a system, which does not
cater to the requirements of the user, is of no use. Stage as given bellow:
 The system to able to interface with the existing system
 The system is to be accurate
 The system to be better than the existing system
The existing system is completely dependent on the staff to perform all duties.

16
OUTPUT DEFINITION
The output should be defined in terms of the following points:
 Type of the output
 Content of the output
 Format of the output
 Location of the output
 Frequency of the output
 Volume of the output
 Sequence of the output
It is not always desirable to print to display data as it is held on a computer. It should
be decided as which form of the output is the most suitable.
OUTPUT MEDIA
In the next stage it is to be decided that which medium is the most appropriate for
the output. The main consideration when deciding about the output media are:

The suitability or the device to the particular application.


 The need for hard copy
 The response time required
 The location of the users
 The software and hardware available
 The cost
Keeping in view the above description the project is to have outputs mainly coming under
the category of internal outputs. The main outputs desired according to the requirement
specification are:
 The outputs were needed to be generated as a hot copy and as well as queries
to be viewed on the screen.
 Keeping in view these outputs
 The format for the output is taken form the outputs
 Which are currently being obtained after manual processing
 The standard printer is to be used as output media for hard copies
17
PROJECT TESTING

Testing is the most important phases in the software development activity. In software
development life cycle (SDLC), the main aim of the testing process in the quality, the
developed software is tested against attaining the required functionality and performance.

During the testing process the software is worked with some particular test case and the
output of the test cases are analyzed whether the software is working according to the
expectations or not.

LEVEL OF TESTING

Since the error in the software can be injured at any stage. so, we have carry out the
testing process at different levels during the development. The basic levels of testing are
 Unit Testing
 Integration Testing
 System Testing
 Acceptance Testing.
UNIT TESTING
Unit testing mainly focused first in the smallest and low level modules, proceeding one
at a time. Bottom-up testing was performed on each module. As developing a driver program, the test
modules by developed or used. But for the purpose of testing modules themselves were used as stubs,
to print verification of the actions performed. After the lower level modules were tested, the modules
that the next higher level those make use of the lower modules were tested

The unit testing has been tested with sample data and adequate corrections were made as
per the user requirement, such that login module was tested with user id and code and
appropriate error messages are provided for errors like data entry error, id error,etc.
INTEGRATION TESTING

Integration testing is a systematic technique for constructing the program structure,


while at the same time conducting tests to uncover error associated with interfacing. As the system
consists of the

18

number the edges of the two modules. The software tested under this incremental bottom-up
approach.

Bottom-up approach integration strategy was implemented with the following steps.

 Low modules were combined into clusters that perform specific software sub function.
 The clusters were tested

TESTING PROCESS
A number of activities must be performed for testing software. Testing start with
test plan. Test plan identifies all testing related activities that need to be performed along with the
schedule and guide lines for testing. The plan also specified the levels of testing that need to be done,
by identifying the different testing units. For each unit specified in the plan first the test cases and
reports are produced. These report are analyzed.
TEST PLAN
Test plan is a general document for entire project, which defines the scope, approach to
be taken and the personal responsible for different activities of testing. The inputs for forming test
plan are
Project Plan
Requirements Document System Design
There are two basic approaches for testing. They are
Functional Testing
Structural Testing
TESTING AND IMPLEMENTATION

19

TESTING AND IMPLEMENTATION


SYSTEM TESTING
Series of different tests whose primary purpose is to fully exercise the computer-based
system. It also tested to find discrepancies between the system and its original objective, current
specifications.10011
EXECUTION TESTING
This program was successfully loaded and executed. Due to programming there were
no execution errors as fall as possible.
QUALITY ASSURANCE
Quality assurance defines the objectives of a project and reviews the overall activities so
that errors are corrected early in the development process.
LEVELS OF QUALITY ASSURANCE
Quality Assurance comes in three main levels namely
Testing
Validation
Certification

TESTING
In system testing a common view is to eliminate program errors. This is
extremely difficult and time consuming. Since designers cannot prove 100% accuracy. A
successful test, then, is one that finds errors.
VALIDATION
It checks the quality of the software in both simulated and live environments.
In the Simulated approach the developers test the product on their workplace to make the
products meet its requirements. In the Live Environment phase the product is given to the
customer to evaluate the product’s functionality.

20

Validation refers to the different set of activities that ensure that software correctly
implements a specific function and the software that been built is traceable to customer
requirements. Verification and validation can be defined in a way like:

 Verification
 Validation
ALPHA AND BETA TESTING
The alpha testing is conducted at the developer’s site by the customer. the software
is used in the natural setting with the developer”looking over the developer” and recording
errors and usages problems. Alpha test is conducted in controlled environment.

The beta testing is conducted at one or more customer site by the end user of the software.
Unlike software testing the developer is generally not present. Therefore beta test is live
application of the software in an environment that cannot be controlled by the developer

VALIDATION CHECK APPLIED IN THE PROJECT


 The files entered in the project must only have the doc extension
 The data entered must have only one format
 One should not make a enter into without checking the password
 The qc must enter into the status column only accepted or not accepted
 File which are already be registered should not be registered once again or other
time
 Qc can’t enter the file which are not entered by the dc
 Qc should enter the file into corresponding filenames registered by the dc
 Files which are registered and not accepted for the first time should not be
registered again but the reentry of date and status should be done only
CERTIFICATION
Certification is to certify that the program or software package is correct and
confirms to standards. With growing trend towards purchasing ready to use software,
certification has become more important.
21

System Security
Software integrity has become increasingly important in the age of hackers and
firewalls. This attributes measures a system ability to withstand attacks (both accidental and
intentional) to its security. Attacks can be made on all three components of software
program, data, and documents
To measure integrity, two additional attributes must be defined
o Thread
o Security
THREAD
Threat is the probability (which can be derived or estimated from empirical
evidence) that an attack of specific type occur with in a specific time.
SECURITY
Security is the probability (which can be estimated or derived from empirical
evidence) that attack on the specific type will be repelled.
SECURITY TESTING
Any computer based system that manages sensitive information or causes action that can
improperly harm(or benefit) individuals is the target for improper or illegal penetration.
Penetration spans a board range of activities; hackers who penetrate system for sport;
disgruntled employee who attempt to penetrate for revenge; dishonest individual who
penetrate for illicit personnel gains
Security testing to verify that protection mechanism built into a system will in
fact provide proper protection form improper penetration. During system testing, the tester
plays the role of the individual who desires to penetrate the system. Anything goes! The
tester may attempt to acquire password through external clerical means; may attack the
system with custom software designed to break down any defenses that have been
constructed may overwhelm the system thereby denying the service to other; may purposely
cause system errors.

22

SYSTEM IMPLEMENTATION

Implementation is used here to mean the process of converting a new or


revised system design into operational one; conversion is one aspect of implementation. the
other aspect is post implementation review and software and maintenance

There are three type of implementation:

 Implementation of a computer system


 Implementation of new computer system
 Implementation of a modified application
IMPLEMENTATION OF THE COMPUTER SYSTEM
It’s should be replace a manual system the problems encountered are converting
files, training users creating accurate files, and verifying printouts for integrity
IMPLEMENTATION OF NEW COMPUTER SYSTEM
It’s should be replace an existing one this is usually a difficult conversion. if not
properly planned there can be many problems. Some large computer system have taken even
years to convert
IMPLEMENTATION OF A MODIFIED APPLICATION
It’s should be replace an existing one using the same computer. This type of
conversion is relativity easy to handle, provided there are no major changes to the file

SYSTEM MAINTENANCE

After the system has successfully implemented maintenance activity may require
continuous involvement of the developers. Provision must be made for environmental
changes, which may affect either the computer, or other parts of computer based system:
such activity is normally called maintenance. It includes both the improvement of system
functions and the correction of faults that arise during the operation of a system.

Maintenance activity may require the continuing involvement of a large proportion


of computer department resources. Maintenance works may arise due to two reasons.
23
 Error that creep up during normal running.
 Request for changes by the service providers. As part of the normal running
of the system when errors are found.

TEST CASES:

S.NO DATA EXPECTED ACTUAL STATUS

RESULT RESULT

1 CLICK THE LIST ALL THE LIST ALL THE PASS

BUTTON DETAILS DETAILS


2 AFTER LIST WEEKLY LIST THE PASS

ENTERED REPORT WEEKLY

CLICK DETAILS REPORT

DETAILS

3 LOGIN SUCCESSFUL SUCCESSFUL PASS

VALIDATION LOGIN LOGIN


CONCLUSION

24

CONCLUSION
The BUG REPORTING SYSTEM developed has been designed to meet the

requirements of development. It maintains the data consistency by avoiding manual

errors. The system reduces the work load of the employees. It produces accurate,

adequate and timely information as and when needed for user.

This system is easily understandable and it satisfies almost all the design

issues considered during the planning stage. Thus it reduces the human effort and

saves the time of both customers and the employees.


25

Scope for Future Enhancement

Bug Tracking helps you maintain a project database of tests that cover all aspects of
your application’s functionality. To meet the various goals of a project, we organize the tests
from our project database into unique groups.
With Bug Tracking, you maintain a project—a database of tests, from a project, you
can build test sets—groups of tests executed to achieve a specific goal. For example, you
can create a test set that checks a new version of the software, or one that checks a specific
feature. As you execute tests, Test Director lets you report defects detected in the software.

Bug reporting system can be more effective and efficient in the coming future by the
addition or implementing the Administrative Tool in the coming future.
ANNEXURE
26

ANNEXURE

Sample Coding:

Login Code:

<html>

<body bgcolor="#FFFF99">

<?php

$a=$_POST["tuser"];

$b=$_POST["tpwd"];

$con=mysql_connect("localhost","root","");

mysql_select_db("bugreporting",$con);

if(isset($con))

else

echo "Error";

$select=mysql_query("select * from adminlogin where username='$a' and password='$b'",

$con);

if(mysql_fetch_array($select))

{
27

echo "<div align='center'><b><font size='6' face='Berlin Sans FB Demi'

color='#660000'>Welcome Admin....</font></b></div>";

echo "<br>";

echo "<div align='center'><b><font face='Arial' size='5' color='#FF6600'><a

href=admin.html target='_parent' >CLICK HERE</a></font></b></div>";

echo "<br>";

echo "<br>";

echo "<font color='#330000' size='4'><b>You Want to Add the New Employee ?

</b><a href='mainureg6.html' target='_parent'><b><font color='#CC0000'>Register

Here</font></b></a></font>";

else

echo "Sorry!! You are not Authorised to access ADMIN";

?>

Registration Code:

<?php

$a=$_POST["tfname"];

$b=$_POST["tlname"];

$c=$_POST["tuid"];
28

$d=$_POST["tpwd"];

$e=$_POST["temail"];

$f=$_POST["tcmpny"];

$g=$_POST["tpcmpny"];

$h=$_POST["tquali"];

$i=$_POST["tskill"];

$j=$_POST["tdesg"];

$k=$_POST["texp"];

$l=$_POST["tadrs"];

$m=$_POST["tphno"];

$n=$_POST["tmobno"];

$o=$_POST["tcity"];

$p=$_POST["tpin"];

$q=$_POST["tstate"];

$con=mysql_connect("localhost","root","");

mysql_select_db("bugreporting",$con);

if(isset($con))

echo "";

else

{
29

echo "Connection Error";

//$sel=mysql_query("select * from userregistration");

$insert=mysql_query("insert into userregistration

values('$a','$b','$c','$d','$e','$f','$g','$h','$i','$j',$k,'$l','$m','$n','$o',$p,'$q')");

$in=mysql_query("insert into userregistration values('daya')");

if(isset($insert))

echo "";

else

echo "Error....";

?>

Bug Code:

<html>

<body>

<pre>

<?php

$q=$_GET[q];
30

$con = mysql_connect("localhost","root","");

mysql_select_db("bugreporting", $con);

$e="select projectname,description,modulename from projectdescription where id='$q'";

$j="select projectname from projectdescription where id='$q'";

$x=mysql_query($e);

while($row=mysql_fetch_array($x))

$pname=$row['projectname'];

echo"<strong><div align='left'><font face='Arial'>PROJECT NAME </font></strong>

<input type='text' name='pname' readonly='true' value=".$pname." ></div>";

?>

</pre>

</body>

</html>

View Priority Code

<?php

$a=$_POST["tid"];

$b=$_POST["tname"];

$c=$_POST["trank"];

$d=$_POST["tdesc"];

echo "<table border=1><tr>


31

<th>PRIORITY_ID</th>

<th>PRIORITY_NAME</th>

<th>RANK</th>

<th>DESCRIPTION<th>

$con=mysql_connect("localhost","root","");

mysql_select_db("bugreporting",$con);

$select=mysql_query("select * from priority",$con);

while($row=mysql_fetch_array($select))

$a1=$row["PRIORITY_ID"];

$b1=$row["PRIORITY NAME"];

$c1=$row["RANK"];

$d1=$row["DESCRIPTION"];

echo "<tr>

<td>echo $a1</td>

<td>echo $b1</td>

<td>echo $c1</td>

<td> echo $d1</td>

echo "<table>";

<strong>

Choose the record ID to Edit</strong>


32

<input type="text" name="pedit"><input type="submit" name="Submit" value="EDIT">

?>

structure for table `Adminlogin`

CREATE TABLE `adminlogin` (`username` varchar(50) NOT NULL, `password`

varchar(50) NOT NULL) ENGINE=InnoDB DEFAULT CHARSET=latin1;

structure for table `Bug`

CREATE TABLE `bug` ( `pid` varchar(30) default NULL, `did` varchar(30) default

NULL,`detectedby` varchar(40) default NULL, `dateassign` varchar(50) default NULL,

`priority` varchar(40) NOT NULL,`status` varchar(40) NOT NULL,`bugname` varchar(40)

default NULL `des` varchar(40) default NULL,`remark` varchar(50) default

NULL,`assignto` varchar(50) default NULL, `name` varchar(50) default NULL, `mailid`

varchar(50) default NULL) ENGINE=InnoDB DEFAULT CHARSET=latin1

structure for table `CLIENT`

CREATE TABLE `client` ( `pid` varchar(50) NOT NULL,`cid` varchar(50) default

NULL,`company` varchar(50) default NULL, `address` varchar(50) default NULL,`state`

varchar(50) default NULL, `city` varchar(50) default NULL,`pin` varchar(50) default

NULL, `phno` varchar(50) default NULL, `mobno` varchar(50) default NULL

`requirement` varchar(50) default NULL,`resprsn` varchar(50) default NULL,`email`

varchar(50) default NULL,KEY `pid` (`pid`)) ENGINE=InnoDB DEFAULT

CHARSET=latin1;
33

structure for table `PRIORITY`

CREATE TABLE `priority` ( `projectid` varchar(40) NOT NULL, `pid` int(10) NOT NULL

auto_increment,`name` varchar(50) default NULL, `rank` int(5) default NULL,

`description` varchar(50) default NULL, PRIMARY KEY (`pid`)) ENGINE=InnoDB

DEFAULT CHARSET=latin1 AUTO_INCREMENT=6 ;


34

ADMIN LOGIN MODULE:

ADMIN LOGIN MODULE


35

ADMIN PAGE:

A.1. ADMIN PAGE


36

OTHER REGISTRATION:

A.2. OTHER REGISTRATION


37

PROJECT DETAILS :

A.3.PROJECT DETAILS
38

CLIENT DETAILS FORM:

A.4.CLIENT DETAILS FORM


39

ASSIGN PROJECTS:

A.5. ASSIGN PROJECTS


40

VIEW/EDIT ADD EMPLOYEES:

A.6. VIEW/EDIT ADD EMPLOYEES


41

PROJECT DETAILS:

A.7. PROJECT DETAILS


42

TESTPLAN DETAILS:

A.8. TESTPLAN DETAILS


43

TEST CASE DETAILS:

A.9. TEST CASE DETAILS


44

BUG DETAILS:

A.10. BUG DETAILS


45

PRIORITY LIST:

A.11. PRIORITY LIST


46

ADD STATUS:

A.12. ADD STATUS


47

VIEW STATUS:

A.13. VIEW STATUS


48

TOTAL TEST PLAN REPORT:

A.14. TOTAL TEST PLAN REPORT


49

TOTAL TEST CASE REPORT:

A.15. TOTAL TEST CASE REPORT


50

TOTAL BUG REPORT:

A.16. TOTAL BUG REPORT:


BIBLIOGRAPHY
51

BIBLIOGRAPHY

REFERENCE BOOKS:

PHP & MYSQL Web Development Author Luke Welling And Laura Thomson

PHP Visual Quick Start Guide Author Larry Ullman

PHP visual Quick Pro Guide Author Larry Ullman

PHP objects,Patterns and Practice Author Matt Zandstra

WEB-SITE:

http://w3schools.com/php/default.asp

http://w3schools.com/php/php_mysql_intro.asp

http://wwww.cegonsoft.com