BHOPAL, (M.

P)

A
PROJECT REPORT
ON

SQL EDITOR
Submitted in partial fulfillment of the requirement for
the
BACHELOR OF ENGINEERING
OF
RAJIV GANDHI PRODYOGIKI VISHWAVIDYALAYA BHOPAL
(University of Technology Madhya Pradesh)

SUBMITTED BY:
PURTI BAJAJ
SOURABH MISHRA
UJJWAL KUMAR

SANTOSH MEHTA
Enrolment No.0115cs111075
Department of computer Science

BHOPAL, (M.P)

DEPARTMENT OF COMPUTER SCIENCE

CERTIFICATE
This is to certify that this project entitled SQL EDITOR submitted in partial
fulfillment

of

the

degree

of

B.E

to

the

Rajiv

Gandhi

Proudyogiki

Vishwavidyalaya,Bhopal through (NRI Institute Of Science And Technology),

done by Miss. PURTI BAJAJ,Roll No.0115CS111075

is an

carried out by her during the academic session under our

authentic work
guidance and

supervision. The matter embodied in this project has not been submitted for
award of any degree to the best of my knowledge and belief.
MISS.
M.R

POOOJA

KOSE

N.K DAS GUPTA

PROJECT
H.O.D (CSE)
DEPT. OF CSE

GUIDE

BHOPAL, (M.P)

DECLERATION

I hereby declare that the project work which is being presented in the
project report entitled SQL EDITOR submitted in partial fulfillment of
the requirements and carried out by us under the supervision and project
coordinator Miss. POOJA KOSE, Department of computer science,
NRI Institute of information Science and Technology, Bhopal, is an
authentic record of my project carried at Rajiv Gandhi Proudyogiki
Vishwavidyalaya Bhopal (M.P.) .
Place: Bhopal

Name:Purti Bajaj

Santosh Mehta
Sourabh Mishra
Ujjwal Kumar
Date: 26-04-2014

Signature:

ACKNOWLEDGEMENT
We began working on our project SQL EDITOR. The task involved various Stages of
preliminary observation, identifying the problem, proposing an effective solution.
The satisfaction that accompanies the successful completion of any test would be incomplete
without the mention of people whos ceaseless cooperation made it possible, whos constant
guidance crown all the efforts with success.
While working on each phase of the project, we received full guidance from our respected
H.O.D Sir. Mr. N.K DAS GUPTA and our project guide Miss.POOJA KOSE, who through
their patience and efforts has inspired and guided our work from start till end through which
we have learned about the various aspects of IT world.
I am very thankful to the Head of Department Mr.N.K DAS GUPTA for extending all the
help whenever we desired.
We extend our sincere thanks and deep sense of gratitude to for providing us the opportunity
to work in organization for completion of the project.
We also recognized the constructive efforts of all our teachers who have helped me in some
or other way. The inspiration and support of our families is surely the grace that helped me to
achieve this piece of work. Our sincere thanks to whole staff of computer department for
their kind co-operation.

I am very much grateful to all my colleagues who made a pleasant and workable environment
around me. Last but not the least we want to thank the Almighty God to give us such
confidence to complete the task.

Student Name: Purti Bajaj

Enrollment no.:0115cs111075

INTRODUCTION
SQL Editor is a light weight intelligence enabled
database
query
tool.
This
document defines and
describe the functional and non-functional requirement
for SQL Editor. It will be uses as the basic for the
development
stages. SQL Editor
is
used
to
edit ,
format
and execute. SQL statement or SQL script. It
is a tool for exploring oracle database and changing
the definition of
database
objects.

OBJECTIVES
The rest of the document is composed of overall description
and requirement specification. The overall description section
presents a background of the general factor that affect the
products and the requirements. the requirement specification
section defines and describe the system functional and nonfunctional requirement is enough detail manner to enable
designer and tester to design and text the system so satisfy the
requirement of the customers.

SCOPE
The primary overall objective target of SQL editor is to develop
a customizable editor that allow individual easily, efficiently and
precisely. Faster use of database as compared to write complex
query every time.The primary target of customer for SQL editor
is the database developer who is dealing with complex or
unfamiliar oracle database can work in a way which otherwise
require an intimate knowledge of the database involved.
simplicity of this program is one of our main objective.

Description
SQL Editor is a light weight intelligence enabled
database
query
tool.
This
document defines and
describe the functional and non-functional requirement
for SQL Editor. It will be uses as the basic for the
development
stages. When a user enters in the SQL editor
they can see short description of SQL editor. A user can login
into the system as authorized user or administrator .if a user is
not registered he/she have to register into it.after joining the
system users get the right to use the system. There will be
stored query SQL tools for execute SQL query.

WORK BREAKDOWN
STRUCTURE

S.N Work
Breakdown
O
1.
2.
3.
4.
5.

structure/mod
ules
Analysis
Design
Coding
Testing

Project Team
Member,Respo
nsible

Santosh Mehta
Purti Bajaj
Purti Bajaj
Ujjwal Kumar
Implementati Sourabh Mishra

on

Propose Date
For
Completion
24-02-2014
10-03-2014
10-04-2014
26-04-2014
28-04-2014

Work Breakdown
/Structure
Modules
Analysis:

Module Description

The software gains some

foundation

as

the

developers will know what

to work on.it deals about
basic responsibility of the
project.

Design :

Coding:

Testing:

Implementation:

Responsibilities:

The specifics of the software are

elaborated in this stage of web
development.
Developers
will
now create a layout of how the
software should perform. The
workflow is eventually established
and the front-end of the software
is laid out.
coding is the operations of the
software
development
plan.
Everything is realized during this
stage. The colors and the
functions are gradually developed
at this point. Developers will
make use of different kinds of
coding
techniques
in
their
preferred platforms.
Of course the program, on its first
run will not perfect or wouldnt
exactly work as planned. It has to
go through rigorous testing. In
this stage, bugs are found and
some irregularities in the software
are somehow fixed.
After removing the errors,the final
software is use and ready for
implementation of that particular
software.

5.2

Work Break
down/Structure
Analysis
Design

Responsible

Coding

Purti Bajaj

Testing

Ujjwal Kumar

Implementation

Sourabh Mishra

Santosh Mehta
Purti Bajaj

5.2 Time Of Completion:

Work Break
down/Structure
Analysis
Design

Time Of Completion

Coding

10-04-2014

Testing

26-04-2014

Implementation

28-04-2014

24-02-2014
10-03-2014

Project Completion Date: 28-04-2014

REQUIREMENT
SPECIFICATIONS
Hardware Requirements:
UserEnd: At the user end a website is execute in browser so the
hardware at user end generally require the hardware needed by the
browser to run a page.
Processer min. 233Mhz
RAM min.- 256 MB
Hard disk - 20 GB
Disk Space- approx 100MB (depend on browser)

ServerEnd
My SQl-5.1.36(version)

Software Requirements:

Server requirements
Operating system

Any of the following is required:

Microsoft Windows Server 2012

Microsoft Windows Server 2008 R2

Microsoft Windows Server 2008 64 bit*

Microsoft Windows Server 2008*

* All service packs are supported.

Web server

Any of the following must be installed as part of the

Windows Server installation:

Microsoft Internet Information Services (IIS) 7.0

Microsoft Internet Information Services (IIS) 7.5

Microsoft Internet Information Services (IIS) 8.0

Apache Tomcat

NOTE IIS 6 is no longer supported. Refer to Upgrading from

IIS 6 to IIS 7 for more information.

Database

Any of the following is required:

Microsoft SQL Server 2008 64 bit*

Microsoft SQL Server 2008 R2 64 bit*

Microsoft SQL Server 2012 64 bit*

* All service packs are supported.

Html/Python Editor

Eric 5.4.0 IDE

Wing IDE

Data Analysis:
7.1 Data Flow Diagram:

Data Flow Diagram symbolizes the flow of information between various

modules of the developed application. In Data Flow Diagram the

abstraction increases with the increase in the levels. And Data Flow
Diagram helps the developer to easily understand the flow of

information. A data flow diagram (DFD) is a graphical representation of

the "flow" of data through an information system. DFDs can also be used
for the visualization of data processing (structured design).On a DFD, data
items flow from an external data source or an internal data store to an
internal data store or an external data sink, via an internal process. A DFD
provides no information about the timing of processes, or about whether
processes will operate in sequence or in parallel. It is therefore quite
different from a flowchart, which shows the flow of control through an
algorithm, allowing a reader to determine what operations will be
performed, in what order, and under what circumstances, but not what
kinds of data will be input to and output from the system, nor where the
data will come from and go to, nor where the data will be stored .

7.2 Structural Diagram

7.2.1 Class
Diagram

A class diagram in the Unified Modeling Language(UML) is a type of

static structure diagram that describes the structure of a system
by showing the system's classes, their attributes, operations (or
methods), and the relationships among objects . A class diagram is
a type of static structure diagram that describes the structure of a
system

by

showing

the

systems

classes,

their

attributes,

operations(or), methods and the relationship between the classes.

It is used both for general conceptual modeling of the systematic
of the application and for detailed modeling translating the models
into programming code. The classes in a class diagram represent
both the main objects and or interaction in the application and the
objects to be programmed. In the class diagram, class is
represented by an icon

7.2.2 Architecture Diagram:

The diagrams within this work product are meant to portray a reasonably
high level view of the architecture which provides an overview of a
particular architecture or sub part of architecture. These types of
diagrams are meant to communicate something to a particular audience
and closely match the idea of an architectural view in TOGAF. UML
diagrams are not likely to appear in this work product since these are
normally at a more detail component level; they are normally included in a
Component Model.

7.3 Behavioural Diagram:

7.3.1 Usecase Diagram:
A use case diagram is a type of behavioral diagram defined by
and created from a use-case analysis. Its purpose is to present
a graphical overview of the functionality provided by a system
in terms of actors, their goals and any dependencies between
those use cases. The main purpose of a use case diagram is to
show what system functions are performed are which actor,
roles of actors in the system can be depicted. Interaction
among actors is not shown on the use case diagram.

History Of Usecase:
In its short history, information technology has already
produced a plethora of methods and notations. We have
methods and notations for design, structure, processing, and
storage of information. We also have methods for the planning,
modeling, implementation, assembly, testing, documentation,
adjustment, etc. of systems. Some of the concepts used are
relatively fundamental, and because of that, they can also be
found beyond the field of information technology. One example
of that is inheritance, which is present in nature, but is also a
cornerstone of object-oriented programming.
Until about the 1970s, software developers viewed the
development of software as an artistic venture. But because
systems became more and more complex, software
development and maintenance could no longer be conquered

with this creative-individual approach. Eventually, this approach

led to the software crisis.

7.3.2 Sequence Diagram:

The sequence diagram is used primarily to show the interactions between

objects in the sequential order that those interactions occur. Much like the
class diagram, developers typically think sequence diagrams were meant
exclusively for them. However, an organization's business staff can find
sequence diagrams useful to communicate how the business currently
works by showing how various business objects interact. Besides
documenting an organization's current affairs, a business-level sequence
diagram can be used as a requirements document to communicate
requirements for a future system implementation.

7.4 Database Diagram

7.4.1 E.R Diagram
E.R Diagram
Entity-Relationship Diagrams (ERDs) illustrate the logical structure
of databases. An entity is an object or concept about which you
want

to

store

information.

Attributes

are

the

properties

or

characteristics of an entity. A key attribute is the unique,

distinguishing, and characteristic of the entity.
Relationships illustrate how two entities share information in the
database structure. Cardinality specifies how many instance of an
entity relate to one instance of another entity. Ordinarily is also
closely

linked

to

cardinality.

While

cardinality

specifies

the

occurrences of a relationship, ordinarily describes the relationship

as either mandatory or optical. In other words, cardinality specifies
the maximum number of relationship and ordinarily specifies the
absolute minimum number of relationships.

Entity Relationship Diagram

Notations
Peter Chen developed ERDs in 1976. Since then Charles Bachman and James
Martin have added some sligh refinements to the basic ERD principles.

Entity
An entity is an object or concept about which you want to store information.

Weak Entity
A weak entity is an entity that must defined by a foreign key relationship with
another
entity as it cannot be uniquely identified by its own attribute.

Key attribute
A key attribute is the unique, distinguishing characteristic of the entity. For
example, an employee's social security number might be the employee's key
attribute.

Multivalued attribute
A multivalued attribute can have more than one value. For example, an
employee entity
can have multiple skill values.

Derived attribute
A derived attribute is based on another attribute. For example, an employee's
monthly salary is based on the employee's annual salary.

Relationships
Relationships illustrate how two entities share information in the
database structure.

Cardinality
Cardinality specifies how many instances of an entity relate to one instance of another entity.
Ordinality is also closely linked to cardinality. While cardinality specifies the occurences of a
relationship, ordinality describes the relationship as either mandatory or optional. In other words,
cardinality specifies the maximum number of relationships and ordinality specifies the absolute
minimum number of relationships.

In some cases, entities can be self-linked. For example, employees can supervise other employees.

8. Software Design

The term design is used in two ways.while used as verb,it means-the

design process and used as noun,it means-the result of design
process.Design is a meaningful engineering representation of something
that is to be built.The result of a design process is called design model

or the design of a system.

8.1 FUNCTIONAL
REQUIREMENT:
In software
engineering (and Systems
Engineering),
a functional
requirement defines a function of a system or its component. A function
is described as a set of inputs, the behavior, and outputs (see
also software). Functional requirements may be calculations, technical
details, data manipulation and processing and other specific functionality
that define what a system is supposed to accomplish. Behavioral
requirements describing all the cases where the system uses the
functional requirements are captured in use cases.
The Functional Requirements Specification documents the operations and
activities that a system must be able to perform.
Functional Requirements should include:

Descriptions of data to be entered into the system.

Descriptions of operations performed by each screen.

Descriptions of work-flows performed by the system.

Descriptions of system reports or other outputs.

Who can enter the data into the system.

system meets applicable regulatory requirements.

Functional Requirement of our

project:
USERS:

When a user enters in the SQL editor they can see short description of
SQL editor. A user can login into the system as authorized user or
administrator .if a user is not registered he/she have to register into
it.after joining the system users get the right to use the system.
ADMIN:

All the functionality which authorized user have.Right to generate new

authorized user.Right to drop any user or change his / her account.Admin
have all the system privileged.Right to create and drop roles.

Basic functionality of our project:

It acts as a tool for creating and executing query.
It provides a platform where an individual can perform SQL query.
It allows user to create and edit or modify SQL text for the query and view the
result of execution.
It provides a facility like cut , paste, undo , redo of existing file.
There will be stored query SQL tools for execute SQL query the user use the
system as:
Create the table.
Store the table.
Update the record.
Delete the record.
Modify the record.

NON FUNCTIONAL REQUIREMENT:

In systems engineering
and
requirements engineering, a non-functional
requirement is a requirement that specifies criteria that can be used to judge the
operation of a system, rather than specific behaviors. This should be contrasted
with functional requirements that define specific behavior or functions. The plan
for implementing functional requirements is detailed in the system design. The
plan
for
implementing non-functional requirements
is
detailed
in
the system architecture.

Non functional requirement of our project:

It is more user interactive and user friendly.

It is more reliable.
It provides facility like cut, copy,paste, undo, redo of existing files.
Appropriate error messages display on the query related if error
come while executing query .

It is more flexible and secure.

24 X 7 facility.

9. Validation Check:
Validation checking is to occur in the presentation tier, business tier
and database tier. The primary purpose of performing validation on
the presentation tier is to quickly relay user friendly messages the
client. The primary purpose of performing validation in the business
tier is to ensure all data is database ready and to ensure all required
error checking occurs regardless of the front end bolted to the
business layer.

10.Testing:
Software testing is a critical element of software quality
assurance and represents the ultimate review of specification,
design and coding. In fact, testing is the one step in the
software engineering process that could be viewed as
destructive rather than constructive.
A strategy for software testing integrates software test case
design methods into a well-planned series of steps that result
in the successful construction of software. Testing is the set of
activities that can be planned in advance and conducted
systematically. The underlying motivation of program testing
is

to

affirm

software

quality

with

methods

that

can

economically and effectively apply to both strategic to both

large and small-scale systems.

STRATEGIC

APPROACH

TO

SOFTWARE TESTING:
The software engineering process can be viewed as a spiral.
Initially system engineering defines the role of software and
leads to software requirement analysis where the information
domain, functions, behavior, performance, constraints and
validation criteria for software are established. Moving inward
along the spiral, we come to design and finally to coding. To
develop computer software we spiral in along streamlines that
decrease the level of abstraction on each turn.

A strategy for software testing may also be viewed in the

context of the spiral. Unit testing begins at the vertex of the
spiral and concentrates on each unit of the software as
implemented in source code. Testing progress by moving
outward along the spiral to integration testing,

where the

focus is on the design and the construction of the software

architecture. Talking another turn on outward on the spiral we
encounter validation testing where requirements established
as part of software requirements analysis are validated
against the software that has been constructed. Finally we
arrive at system testing, where the software and other system
elements are tested as a whole.

10.1 Types of Testing:

UNIT TESTING

MODULE TESTING
UNIT TESTING
Component Testing

SUB-SYSTEM TESING
MODULE TESTING

Component Testing
Integration Testing

SYSTEM TESTING
SUB-SYSTEM TESING

ACCEPTANCE TESTING
User Testing
Integration PROJECT
Testing

SYSTEM TESTING

USE:UNIT TESTING:
ACCEPTANCE TESTING

User Testing

Unit testing focuses verification effort on the smallest unit of software design,
the module. The unit testing we have is white box oriented and some modules
the steps are conducted in parallel.

1.

WHITE BOX TESTING

This type of testing ensures that

All independent paths have been exercised at least once

All logical decisions have been exercised on their true and false sides

All loops are executed at their boundaries and within their operational bounds

All internal data structures have been exercised to assure their validity.
To follow the concept of white box testing we have tested each form .we have
created independently to verify that Data flow is correct, All conditions are
exercised to check their validity, All loops are executed on their boundaries.
2.

BASIC PATH TESTING

Established technique of flow graph with Cyclomatic complexity was used to

derive test cases for all the functions. The main steps in deriving test cases
were:
Use the design of the code and draw correspondent flow graph.
Determine the Cyclomatic complexity of resultant flow graph, using formula:
V(G)=E-N+2 or
V(G)=P+1 or
V(G)=Number Of Regions
Where V(G) is Cyclomatic complexity,
E is the number of edges,

N is the number of flow graph nodes,

P is the number of predicate nodes.
Determine the basis of set of linearly independent paths.

3.

CONDITIONAL TESTING

In this part of the testing each of the conditions were tested to both true and
false aspects. And all the resulting paths were tested. So that each path that
may be generate on particular condition is traced to uncover any possible
errors.

4. DATA FLOW TESTING

This type of testing selects the path of the program according to the location of
definition and use of variables. This kind of testing was used only when some
local variable were declared. The definition-use chain method was used in this
type of testing. These were particularly useful in nested statements.

10.2 Test Cases:

Te
st
Ca
se
TC1

TC2

Check
item

Test case
objective

Test
Data/in
put

Login pageLeave all fields as blank

click on login button

Login
page

Enter invalid userid

and password

Expected Result

by leaving fileds as blank clicking

k On login button, an alert will
be displayed indicating
message that the fields are
mandatory.

Click
login
button

Test
resu
lt

By entering invalid user id

and password an error page
showing message invalid
userid and password is

Corre
ct

corre
ct

displayed
TC-

Login

Enter correct userid

Click

The user is allowed to

Corre

page

and password

login

proceed further i.e. now user

ct

button

can enter his/her classroom

TC-

Registra

Leave all fields as

Click

By leaving fields blank and

Corre

tion

blank and click on

submit

clicking on submit button, an

ct

form

submit button

button

alert will be displayed

indicating message that fields
are mandatory

TC5

Registra
tion
form

Leave any one or

two mandatory field
blank and click on
submit button

Click
Submit
button

By leaving mandatory field an

alert message for that
particular field will be
generated indicating that the
field is mandatory

Corre
ct

TC6

Registra
tion
form

Filling invalid data

in particular field

Click
submit
button

If any invalid data is filled in

any particular field like invalid
mobile no. an alert will be
generated indicating please
input valid data

Corre
ct

10.3 Test Plan:

1.Testing process:
In this section various phases of testing is described.

2.Requirement Traceability:
Traceability should be palnned to meet all the requirement.
3.Tested Item:
The tested products of software are tested.

4.Testing Schedule:
It includes the testing schedule and resource allocation for this
schedule.

5.Test recording Procedures:

After running the tests,it is necessary to record those tests in

order to check whether test are conducted systematically or
not.

6.Hardware and Software Requirements:

The required software tests and hardware utilization is specified
under this section.

7.Constraints:
All the factors affecting the test process are listed under this
section.

10.4 Test Report:

11.Market Potential And

Competitive Advantage:
Before anything is implemented or written, SDLC should
always understand their customers in the first place. Its just
basic business to consider what is required and whats in
demand in today's market. An abstract program could be
created from this stage. Since researchers are technically not
the developers, all they could do is create a list of what could
be used by the public. This will basically be the mission of
the software to meet and exceed the needs that are
laid out by the market research team.

12.Likely Benefits: