A Project Report

On
Online Test Engine
2009

Road Ahead Technologies (I)Pvt. Ltd.

Jaipur

Under The Supervision Of

Mr. Abhishek Jain

Training Co-ordinator & Director
Road Ahead Technologies Pvt. Ltd.
Jaipur

Submitted by :-
 Index

1. Company profile

2. Acknowledgement

3. features of project

4. hardware and software requirement Concepts of software engg.

a. What is sdlc
b. All modals
c. Testing

5. technologies used

6. Screen shots of project and database

7. Future enhancement in project

8. Trouble shooting

9. Bibliography

Company Profile
 INTRODUCTION TO
R O A D A H E A D T E C H N O LO G I E S

Road Ahead Technologies(I) Pvt. Ltd. is a pioneer in providing

Quality Training and learning solution to the young IT students .
Road Ahead Technologies started its operations on September 4th
2004 and since then it has emerged as the most trusted name for
Providing software training to the students.
Road Ahead Technologies specialize in the following skills of
Software & Web development:
∞ J2SE – Core Java
∞ J2EE – Advance Java
∞ J2ME – Mobile Java
∞ C#.net – Window Development
∞ ASP.net – Web Development
∞ Open Source Development Via PHP
∞ And Many more

Road Ahead Technologies has taken a number of initiatives for

improvising the software training & software training and amongst
those initiative the most popular is a club of IT student known as TECH
UNITED which proved out to be a huge success in its very first phase
attracting more than 500 members from the state.

Acknowledgement

This is a great opportunity to acknowledge and to thanks all those persons

without whose support and help this project would have been impossible. We
would like to add a few heartfelt words for the people who were part of this
project in numerous ways.

I would like to thanks to my project guide “Mr. Abhishek Jain”, for his
indefatigable guidance, valuable suggestion, moral support, constant
encouragement and contribution of time for the successful completion of
project work. I am very grateful to him, for providing all the facilities needed
during the project development.

I thank my Counselors for his indispensable support and encouragement

thought the project. I would like to thank all those who helped me directly or
indirectly.

Thank you

Conclusion
After analyzing the cost benefit analysis of the current
system, automated system , we conclude that the
automated system is best. This software is going toserve
the long term need of Online Test Conducting System.
This software will increase the good will of the Institute.
It also reduces the burden of work on part of cheking
manually and making all system efficient and fast. Nowbt
introducing this system the transaction and report become
instantaneous. As a result more viewer will be attract
towards the Online Test Conducting System .

SYSTEM REQUIREMENTS

 Minimum Hardware Requirements:

  Pentium 3
 RAM 128MB
 Color VGA Monitor
 Keyboard
 Mouse
 Minimum Software Requirement:
 MySql
 Java Runtime Environment
 Internet Browser
 Systems Development Life Cycle

(SDLC)

Systems Development Life Cycle (SDLC), or Software Development Life

Cycle, in systems engineering and software engineering refers to the process of
creating or altering systems, and the models and methodologies that people use
to develop these systems. The concept generally refers to computer or
information systems.

Systems Development Life Cycle (SDLC) is any logical process used by a

systems analyst to develop an information system, including requirements,
validation, training, and user ownership. An SDLC should result in a high
quality system that meets or exceeds customer expectations, reaches
completion within time and cost estimates, works effectively and efficiently
in the current and planned Information Technology infrastructure, and is
inexpensive to maintain and cost-effective to enhance.

Computer systems have become more complex and often (especially with
the advent of Service-Oriented Architecture) link multiple traditional
systems potentially supplied by different software vendors. To manage this
level of complexity, a number of system development life cycle (SDLC)
models have been created: "waterfall," "fountain," "spiral," "build and fix,"
"rapid prototyping," "incremental," and "synchronize and stabilize."
Although the term SDLC can refer to various models, it typically denotes a
waterfall methodology.

In project management a project has both a life cycle and a "systems

development life cycle," during which a number of typical activities occur.
The project life cycle (PLC) encompasses all the activities of the project,
while the systems development life cycle focuses on realizing the product
requirements.
Systems Development Life Cycle (SDLC)

Waterfall model
The waterfall model is a popular version of the systems development
life cycle model for software engineering. Often considered the
classic approach to the systems development life cycle, the waterfall
model describes a development method that is linear and sequential.
Waterfall development has distinct goals for each phase of
development. Imagine a waterfall on the cliff of a steep mountain.
Once the water has flowed over the edge of the cliff and has begun
its journey down the side of the mountain, it cannot turn back. It is the
same with waterfall development. Once a phase of development is
completed, the development proceeds to the next phase and there is
no turning back.

The advantage of waterfall development is that it allows for

departmentalization and managerial control. A schedule can be set
with deadlines for each stage of development and a product can
proceed through the development process like a car in a carwash,
and theoretically, be delivered on time. Development moves from
concept, through design, implementation, testing, installation,
troubleshooting, and ends up at operation and maintenance. Each
phase of development proceeds in strict order, without any
overlapping or iterative steps.

The disadvantage of waterfall development is that it does not allow for

much reflection or revision. Once an application is in the testing
stage, it is very difficult to go back and change something that was
not well-thought out in the concept stage. Alternatives to the waterfall
model include joint application development (JAD), rapid application
development (RAD), synch and stabilize, build and fix, and the spiral
model.
Waterfall model
 SYSTEM DESIGN

Introduction
System design provides the understandings and procedural details necessary
for implementing the system recommended in the system study. Emphasis is
on the translating the performance requirements into design specifications.
The design phase is a transition from a user-oriented document (System
proposal) to a document oriented to the programmers or database personnel.

System design goes through two phases of development:

1) Logical Design

2) Physical Design

A data flow diagram shows the logical flow of the system. For a system it
describes the input (source), output (destination), database (data stores) and
procedures (data flows) all in a format that meets the user’s requirement.
When analysis prepare the logical system design, they specify the user needs
at a level of detail that virtually determines the information flow into an out
of the system and the required data resources. The logical design also
specifies input forms and screen layouts.

The activities following logical design are the procedure followed in

the physical design e.g., producing programs, software, file and a working
system. Design specifications instruct the user about what the system should
do.
Logical and Output Design:

The logical design of an information system is analogous to an

engineering blue print of an automobile. It shows the major features and how
they are related to one another. The detailed specification for the new system
was drawn on the bases of user’s requirement data. The outputs inputs and
databases are designed in this phase.

Output design is one of the most important features of the information

system. When the outputs is not of good quality the users will be averse to
use the newly designed system and may not use the system. There are many
types of output, all of which can be either highly useful or can be critical to
the users, depending on the manner and degree to which they are used.

Outputs from computer system are required primarily to communicate

the results of processing to users, They are also used to provide a permanent
hard copy of these results for later consultation. Various types of outputs
required can be listed as below:

 External Outputs, whose destination is outside the organisation

 Internal outputs, whose destination is with the organisation

 Operational outputs, whose use is purely with in the computer

department e.g., program-listing etc.

 Interactive outputs, which involve the user is communicating directly

with the computer, It is particularly important to consider human factor when
designing computer outputs. End user must find outputs easy to use and
useful to their jobs, Without quality output, user may find the entire system
unnecessary and avoid using it. The term “Output” in any information
system may apply to either printer or displayed information. During the
designing the output for this system, it was taken into consideration, whether
the information to be presented in the form of query of report or to create
documents etc.

Other important factors that were taken into consideration are:

The End user, who will use the output.

 The actual usage of the planned information

 The information that is necessary for presentation

 When and how often output and their format is needed. While designing
output for project based Attendance Compilation System, the following
aspects of outputs designing were taken into consideration.

 The outputs (i.e., well formatted table outputs in the screen itself)
designed are simple to read and interpret.

 Format of each output was another important point taken into

consideration. Output media, for each output appropriate media is decided
whether it will be displayed on screen or will be taken to printer or both.

 Other output design related specifications, i.e., how frequently the

outputs will be generated, how many pages or sheets approximately it will
keep up, what is its planned use and output distribution to users are also
taken into account.

These were a few major designing issues, which were taken into
consideration, while deciding the output specifications for the system. As
direct beneficiary of reports is the user community, they were consulted
constantly at every level. Formats and screen design for various reports were
identified, taking into account the user requirements. Before finalising these
were given to users for any improvement and suggestions. End users issues
taken into consideration were Readability, Relevance and Acceptability.

Once all the output reports to be generated by ACS system were

identified, they were given to users for their acceptance. For prototyping
various outputs, final outputs models were created with dummy data, before
they were finalised.

Output Sources:

Output contents originate from these sources:

 Retrieval from a data source.

 Transmission from a process or system activity.

 Directly from an input source.

The information produced in an output can be presented as

 Tabular contents

 Graphic format

 Using Icons

Output Definition:

The output should be defined in terms of:

Types of outputs

 Content-headings, numeric, alphanumeric, etc.,

 Format-hardcopy, screen, microfilm, etc.,

 Location-local, remote, transmitted, etc.,

 Frequency-daily, weekly, hourly, etc.,

 Response-immediate with in a period, etc.

Data items

The name given to each data item should be recorded and its
characteristics described clearly in a standard form:

 Whether alphanumeric or numeric

 Legitimate and specific range of characteristics

 Number of characters

 Positions of decimal point, arithmetic design, etc.

Input Design:

The input design is the link that ties the information system into the user’s
world. Input specifications describe the manner in which data enters the
system for processing. Input design features can ensure the reliability of the
system and produce results from accurate data, or they can result in the
production of erroneous information.

Input Design consists of

 developing specifications and procedures for data preparation

 Steps necessary to put data into a usable form for processing.

 Data entry, the activity of putting data into the computer processing.
Objectives of Input design

Five objectives of design input focus on

 Controlling the amount of input required

 Avoid delay

 Avoiding errors in data

 Avoiding extra steps.

 Keeping the process simple.

Input stages several activities have to be carried out as part of te overall

input process. They include some or all of the following.

Data recording (i.e., collection of data)

Data encapsulation(i.e.,transfer of data)

Data conversion(i.,e.,controlling the flow of data)

Data transmission(i.e.,transporting te data)

Data validation(i.e.,checking te input data)

Data correction(i.e.,correcting the errors)

Input Performa were designed, after a careful discussion with users. It was
attempted to cover all user requirements. Designed Performa were given to
user for any suggestion and final approval.
Various data items were identified and wherever necessary were recorded.

Input designs are aimed at reducing the chances of mistakes of errors.

As the human beings are prone to errors there is always a possibility of
occurrence of chance of errors. Adequate validation checks are incorporated
to ensure error free data storage. Some of the data validation checks applied
are as following:

 Redundancy of data is checked. It means the records of primary key do

not occur twice.

 Primary key field of any table must not be left blank.

 Wherever items are coded, input code is checked for it’s validly with
respect to several checks.

 Utmost care has been taken to incorporate the validation at each stage of
the system. E.g. when entering records into employee information table for
employee, it is checked that whether the corresponding employee exists in
the employee information table etc.,

Enough messages and dialogue boxes are provided while design screen,
which does guide user at the time of any errors, or at time of entry. This
feature provides a user-friendly interface to native users. It can be
emphasized that input deigns of CRM is so designed that it ensures easy and
error free data entry mechanism. Once one is sure of input data the output
formatting becomes an routine work.
 DataBase: - MySQL

The MySQL database system uses a client-server architecture that centers

around the server,
mysqld. The server is the program that actually manipulates databases.
Client programs don't
do that directly; rather, they communicate your intent to the server by
means of queries
written in Structured Query Language (SQL). The client program or
programs are installed
locally on the machine from which you wish to access MySQL, but the server
can be installed
anywhere, as long as clients can connect to it. MySQL is an inherently
networked database
system, so clients can communicate with a server that is running locally on
your machine or
one that is running somewhere else, perhaps on a machine on the other side
of the planet.
Clients can be written for many different purposes, but each interacts with
the server by
connecting to it, sending SQL queries to it to have database operations
performed, and
receiving the query results from it.
One such client is the mysql program that is included in MySQL distributions.
When used
interactively, mysql prompts for a query, sends it to the MySQL server for
execution, and
displays the results. This capability makes mysql useful in its own right, but
it's also a valuable
tool to help you with your MySQL programming activities. It's often
convenient to be able to
quickly review the structure of a table that you're accessing from within a
script, to try a query
before using it in a program to make sure it produces the right kind of
output, and so forth.
mysql is just right for these jobs. mysql also can be used non-interactively,
for example, to
read queries from a file or from other programs. This allows you to use it
from within scripts
or cron jobs or in conjunction with other applications.
This chapter describes mysql's capabilities so that you can use it more
effectively. Of course,
to try out for yourself the recipes and examples shown in this book, you'll
need a MySQL user
account and a database to work with. The first two sections of the chapter
describe how to use
mysql to set these up. For demonstration purposes, the examples assume
that you'll use
MySQL as follows:
The MySQL server is running on the local host.
Your MySQL username and password are cbuser and cbpass.
Your database is named cookbook.
For your own experimentation, you can violate any of these assumptions.
Your server need
not be running locally, and you need not use the username, password, or
database name that
are used in this book. Naturally, if you don't use MySQL in the manner just
described, you'll
need to change the examples to use values that are appropriate for your
system. Even if you
do use different names, I recommend that you at least create a database
specifically for trying
the recipes shown here, rather than one you're using currently for other
purposes. Otherwise,
the names of your existing tables may conflict with those used in the
examples, and you'll
have to make modifications to the examples that are unnecessary when you
use a separate
database
HTML:- Hypertext Markup Language

HTML is a document-layout and hyperlink-specification

language. It defines the
syntax and placement of special, embedded directions
that aren’t displayed by the
browser, but tell it how to display the contents of the
document, including text,
images, and other support media. The language also tells
you how to make a
document interactive through special hypertext links,
which connect your document
with other documents—on either your computer or
someone else’s, as well
as with other Internet resources, like FTP.
Servlet Technology

The servlet technology is the foundation of web application development using the
Java
programming language. It is one of the most important Java technologies, and it is
the underlying
technology for another popular Java technology for web application development:
JavaServer
Pages (JSP). Therefore, understanding the servlet technology and its architecture is
important if
you want to be a servlet developer. Even if you plan to develop your Java web
application using
JSP pages alone, understanding the servlet technology helps you build a more
efficient and
effective JSP application.

Snapshots :-

Login Page :-
 R
egistration Page :-

Welcome Page
Questions

Review Page
Result
DataBase :-

Registration Table
First Name
Last Name
Gender
DOB
City
State
Country
PinCode
Email
Password
Phone no
Mobilenumber

Snapshot

Question

Qno number
Question
OP1
OP2
OP3
OP4
Cans.
Question Of Java

Question Of C

Question of C++
Result Table

Total Question
Attempt question
Correct Answer
Wrong Answer
Marks
Total Marks
 FUTURE SCOPE
This software can be easily upgraded in the future.
And also include many more features for existing system.

 It is connected with the internet for easily Test

Conduction
 All the information can be easily accessed the
Students details, marks

 Transaction. It can be modify and the others

details can be easily provided to Student

 In Future all the Work Transfer on the internet

then the OLTS have a great scope
 Trouble shooting

This Project Properly Tested for any runtime error

If there are some problem occurs than some advice
from us
 Logout and Relogin
 In Registration page please fill all the fields
 BIBLIOGRAPHY

S. No. TITLE AUTHOR PUBLICATION EDITION

1. THE COMPLETE PATRICK NAUGHTON TATA McGraw 1994

REFERENCE JAVA2 HERBERT SCHILDT HILL

2. JAVA JAWORSICK TECH.MEDIA 1998

CERTIFICATION Publication

3. COMPLETE JAVA 2 ROBERT HELLERS DPB 1998

ERNEST PUBLICATIONS