ACKNOWLEDGEMENT

The successful completion of this project mark the beginning of an ever - going
learning experience of converting ideas and concepts into real life, practical
system. This project was a quite a learning experience for me at each and every
step. At the same time it has given me confidence to work in professional setup.
I feel the experience gained during the project will lead me to gain the bright
prospect in the future. First of all I would like to give thanks to Head,
Education and Training, Mr. Altaf, for giving me the opportunity to work in
this esteemed organization, which not only has increased our awareness about
latest fields but also taught me the importance of team building. With the deep
sense of gratitude, I express my sincere thanks to Ms. Swati Sethi, for her active
support and continuous guidance without which it would have been difficult for
me to complete this project. I will also like to the other working staff teachers
at WEBTEK LIMITED for taking keen interest in my project and giving
valuable suggestions and helping me directly or indirectly to complete this
project.

1
 CONTENTS

Introduction
Hardware and Software Requirements
Development Environment
System Design
Implementation
Conclusion
Acknowledgement
References

2
 INTRODUCTION

ORGANISATION PROFILE:

WebTek Labs Pvt. Ltd. is recognized as a leading IT solution providing organization

with a dynamic and fast growing team of diversely talented individuals. Incorporated in
2001, in our aim to provide the best talent, we initially started with Recruitment &
Staffing services. We paralleled this by providing knowledge and skill development
certification training programs. WebTek Certified Tester (WCT) Program that aims to
provide IT companies trained software Testers has reached soaring heights of
recognition over the years. Few years later after its inception, WebTek Labs added
Software development & testing services to the portfolio.

Having partnered and worked with some of the leading names across Education, IT,
ITES, Banking, Insurance, Aviation, Retail, Healthcare, Hospitality, Media,
Manufacturing and FMCG sectors, WebTek Labs has explored business opportunities in
software solutions with the Government, Corporate and Institutes.

With over a decade of experience we create and deliver high-impact solutions, enabling
our clients to achieve their business goals and enhance their competitiveness. In our
pursuit of excellence, WebTek's Research & Development team consistently innovates to
provide up-to-date solutions keeping in pace with changing times. Our mission is for
businesses to leverage the internet and mobility to work smarter and grow faster. We
work as your outsourcing and consulting partner. Our business verticals are:

• Recruitment & Staffing

• Software Development and Testing Services
• Digital Marketing
• Enterprise Mobility
• Certifications & Trainings for Career Management
• Software solutions

WEBTEK TEAM has expertise ranging from design to development, training to

placements and solutions to implementaion. We combine this knowledge with proactive
thinking and strategic planning to approach new challenges with your overall business
objectives in mind. WebTek Lab's management team brings together a wealth of
experience in both technological and organizational development that is critical in
helping our customers achieve their goals.
INTRODUCTION OF PROJECT

3
INTRODUCTION

This system is basically concerned with making the students enable to take to the quiz
at their own convenience. The need of this system arose because there exist some
problems faced by the manual examination systems that are delay in result processing
, filing poses a problem , filtering of records is not easy , the chance of loss of
records is high and also record searching is difficult. These problems can be easily
overcome by Quiz System. Maintenance of the results and results is also very difficult
and takes a lot of time and effort in case of manual examinations. Students can choose
the subject of their own choice and take the quiz which will efficiently display result at
the end of it , enabling student to get to know of his/her performance. This system will
be very fast and result processing will be fast and accurate. By computerizing the
system, we will be able to overcome many of its limitations and will be able to
make it more efficient. The handling of data and records for such a vast system
is a very complex task if done manually but it can be made much easier if the
system is computerized.

This project has 2 parts:

1. User Database Section.
2. User Result Generation After Quiz.

This project include:

1. Login options for the student.
2. Saving details of the student in the database.
3. Giving choice to the students to select a subject.
4. A no of MCQ flash in front of students to solve.
5. Result generation at the end according to student’s performance.

PROBLEM SPECIFICATION:

This problem is assigned to me during my core java training to design an

application on “ Quiz System ” using Netbeans 8.1 and Oracle database.

PROBLEM DEFINITION:

A data base is maintained of information regarding student’s details like Name , Roll
No. , School who have logged in the system with the intention of taking quiz.

4
This project works by storing the details of students in the database and then enabling
the student to choose the subject of his/her choice on which he/she wants to take quiz
and evaluate their performance. Later generation of the result at the end of the quiz
based on the performance of the student.

LIMITATION OF EXISTING SYSTEM:

1. Data redundancy:

It means that same data fields appear in many different files and often in different
formats. In Manual system it poses quite a big problem because the data has to
be maintained in large Volumes, but in our system, this problem can be overcome
by providing the condition that if The data entered is duplicate, it will not be
entered otherwise updating will take place.

2. Difficulty in accessing the data:

In manual system, searching information is time consuming but in our system,

any information Can be accessed by providing the primary key.

3. Unsatisfactory security measures:

In manual system, no security measures were provided but in this system, Password
security Has been provided. The person can access the system by providing the
correct password Otherwise he is denied the access.

FEASIBILITY STUDY

An initial investigation in a proposal that determines whether an alternative system

is feasible. A proposal summarizing the thinking of the analyst is presented to the
user for review. When approved, the proposal initiates feasibility study that describes
and evaluates candidate systems and provides for the selection of best system that
meets system performance requirements.
To do a feasibility study, we need to consider the economic, technical factors in
system development. First a project team is formed. The team develops system
flowcharts that identify the characteristics of candidate systems, evaluate the
performance of each system, weigh system performance and cost data and select
the best candidate system for the job. The study culminates in a final report to
the management.

HARDWARE AND SOFTWARE REQUIREMENTS

5
1. HARDWARE REQUIREMENT:-

• PROCESSOR : Pentium IV processor or Greater

• RAM : 128 Mega Byte (MB) or Greater
• HARDDISK : 1.2 Giga Byte (GB) or Greater
• Keyboard & Mouse
• MONITOR : Colour (For Best Result)
• Printer

2. SOFTWARE REQUIREMENTS:-

• Operating System : Windows 2000/ XP /7/8

• Front-End : Netbeans ide 8.1
• Back-end : oracle database

DEVELOPMENT ENVIRONMENT

1. INTRODUCTION TO ORACLE :-

An Oracle database is a collection of data treated as a unit. The purpose

of a database is to store and retrieve related information. A database
server is the key to solving the problems of information management. In
general, a server reliably manages a large amount of data in a multiuser
environment so that many users can concurrently access the same data. All
this is accomplished while delivering high performance. A database server
also prevents unauthorized access and provides efficient solutions for
failure recovery.

Oracle Database is the first database designed for enterprise grid

computing, the most flexible and cost effective way to manage information
and applications. Enterprise grid computing creates large pools of
industrystandard, modular storage and servers. With this architecture, each
new system can be rapidly provisioned from the pool of components.
There is no need for peak workloads, because capacity can be easily
added or reallocated from the resource pools as needed.

6
 The database has logical structures and physical structures. Because the
physical and logical structures are separate, the physical storage of data
can be managed without affecting the access to logical storage structures.

2. ORACLE DATABSE OBJECTS:-

Aschemais a collection of logical structures of data, or schema objects. A

schema is owned by a database user and has the same name as that user.
Each user owns a single schema.

Schema objects can be created and manipulated with SQL and include the
following types of objects:

• clusters
• Database links
• Database triggers
• Dimensions
• External procedure libraries
• Indexes and index types
• Java classes, Java resources, and Java sources
• Materialized views and materialized view logs
• Object tables, object types, and object views
• Operators
• Sequences
• Stored functions, procedures, and packages
• Synonyms
• Tables and index-organized tables
• Views

Other types of objects are also stored in the database and can be created and
manipulated with SQL but are not contained in a schema:

• Contexts
• Directories
• Profiles
• Roles
• Tablespaces
• Users

Some of the most common schema objects are defined in the following section.

• Tables: -

7
Tables are the basic unit of data storage in an Oracle database. Database
tables hold all user-accessible data. Each table has columns and rows. A
table that has an employee database, for example, can have a column
called employee number, and each row in that column is an employee's
number.

• Indexes:-

Indexes are optional structures associated with tables. Indexes can be

created to increase the performance of data retrieval. Just as the index in
this manual helps you quickly locate specific information, an Oracle index
provides an access path to table data.

When processing a request, Oracle can use some or all of the available
indexes to locate the requested rows efficiently. Indexes are useful when
applications frequently query a table for a range of rows (for example, all
employees with a salary greater than 1000 dollars) or a specific row.

Indexes are created on one or more columns of a table. After it is

created, an index is automatically maintained and used by Oracle. Changes
to table data (such as adding new rows, updating rows, or deleting rows)
are automatically incorporated into all relevant indexes with complete
transparency to the users.

• Views:-

Views are customized presentations of data in one or more tables or other

views. A view can also be considered a stored query. Views do not
actually contain data. Rather, they derive their data from the tables on
which they are based, referred to as the base tables of the views.

Like tables, views can be queried, updated, inserted into, and deleted
from, with some restrictions. All operations performed on a view actually
affect the base tables of the view.

Views provide an additional level of table security by restricting access to

a predetermined set of rows and columns of a table. They also hide data
complexity and store complex queries.

• Clusters:-

8
 Clusters are groups of one or more tables physically stored together
because they share common columns and are often used together. Because
related rows are physically stored together, disk access time improves.

Like indexes, clusters do not affect application design. Whether a table is

part of a cluster is transparent to users and to applications. Data stored in
a clustered table is accessed by SQL in the same way as data stored in a
non-clustered table.

• Synonyms:
Asynonymis an alias for any table, view, materialized view, sequence,
procedureFunction, package, type, Java class schema object, user-defined
object type, or another Synonym. Because a synonym is simply an alias,
it requires no storage other then Definition in the data dictionary.

Sequences

Tables usually have a primary key which uniquely identifies a row in a

table. A sequence is a unique number generator which can be assigned to
the primary keys of the tables.

Partitions

Partitioning provides tremendous advantages to applications by improving

manageability, performance, and availability.
Partitioning allows a table, index or index-organized table to be subdivided
into smaller pieces.
Each piece of database object is called a partition.

Techniques for partitioning tables:

- Range Partitioning
- List Partitioning
- Hash Partitioning
- Composite Range-Hash Partitioning
- Composite Range-List Partitioning

Clusters

A cluster is a schema object that contains data from one or more tables,
all of which have one or more columns in common.
All the rows from all the tables that share the same cluster key are
stored.
9
 After you create a cluster, you add tables to it. A cluster can contain a
maximum of 32 tables.

Stored procedures and packages

A procedure is a PL/SQL block alike the functions of the 3rd generation

languages. You just have to compile them so as to use them later. When
a procedure is created, it is compiled and stored in the database in the
compiled form.
Parameters can be passed to a procedure.
A procedure call is a PL/SQL statement by itself. A procedure is a
PL/SQL block with a declarative section, an executable section and an
exception handling section.

Package:
Packages are PL/SQL constructs that allow related objects to be stored
together. A package has two separate parts. Each of them is stored
separately in the data dictionary.
A package can include procedures, functions, cursors, types, and variables.

User-defined data types

User defined data types are PL/SQl types that are based on the existing
types. Subtypes are used to gives an alternate name to for a type.

Table spaces

A table space is an area on disk which comprises of one or more disk

files. A tablespace can contain many tables, clusters or indexes.
One or more tablespaces together make a database.
Each table has a single area of disk space called a segment set aside for
it in the table space.
Each segment has an initial area on disk space set aside for it in the
table space called the initial extent.
Once it has been used up, another extent is set aside for it.

Constraint

Constraints help understand how the tables and columns are related to
each other.
The constraint information is accessible under the USER_constraint view.

10
The constraints include the following columns

Owner of constraint
Constraint_name
Constraint_type
Table_name
Search_condition
R_Owner - - owner of the foreign key referenced table.
R_constraint_name
Delete_rule
Status

11
 TESTING AND IMPLEMENTATION

TESTING:-

Testing is the process of exercising software with the intent of finding errors and
ultimately correcting them. The following testing techniques have been used to
make this project free of errors.

Content Review

The whole content of the project has been reviewed thoroughly to uncover
typographical errors, grammatical error and ambiguous sentences.

Navigation Errors

Different users were allowed to navigate through the project to uncover the
navigation errors. The views of the user regarding the navigation flexibility and
user friendliness were taken into account and implemented in the project.

Unit Testing

Focuses on individual software units, groups of related units.

• Unit – smallest testable piece of software.
• A unit can be compiled /assembled / linked/loaded; and put under a test
harness.
• Unit testing done to show that the unit does not satisfy the application and
/or its implemented software does not match the intended designed structure.

Integration Testing

Focuses on combining units to evaluate the interaction among them

• Integration is the process of aggregating components to create larger
components.
• Integration testing done to show that even though components were
individually satisfactory, the combination is incorrect and inconsistent.

System testing

Focuses on a complete integrated system to evaluate compliance with specified

requirements (test characteristics that are only present when entire system is run)
A system is a big component.

12
• System testing is aimed at revealing bugs that cannot be attributed to a
component as such, to inconsistencies between components or planned
interactions between components.
• Concern: issues, behaviors that can only be exposed by testing the entire
integrated system (e.g., performance, security, recovery)each form encapsulates
(labels, texts, grid etc.). Hence in case of project in V.B. form are the basic
units. Each form is tested thoroughly in term of calculation, display etc.

Regression Testing

Each time a new form is added to the project the whole project is tested thoroughly
to rectify any side effects. That might have occurred due to the addition of the
new form. Thus regression testing has been performed.

White-Box testing

White-box testing (also known as clear box testing, glass box testing, transparent
box testing and structural testing) tests internal structures or workings of a program,
as opposed to the functionality exposed to the end-user. In white-box testing an
internal perspective of the system, as well as programming skills, are used to
design test cases. The tester chooses inputs to exercise paths through the code and
determine the appropriate outputs.

This is analogous to testing nodes in a circuit, e.g. in-circuit testing (ICT).

While white-box testing can be applied at the unit, integration and system levels
of the software testing process, it is usually done at the unit level. It can test
paths within a unit, paths between units during integration, and between subsystems
during a system–level test. Though this method of test design can uncover many
errors or problems, it might not detect unimplemented parts of the specification or
missing requirements.

Techniques used in white-box testing include:

API testing (application programming interface) – testing of the application

using public and private APIs

Code coverage – creating tests to satisfy some criteria of code coverage (e.g., the
test designer can create tests to cause all statements in the program to be executed
at least once)

Fault injection methods – intentionally introducing faults to gauge the efficacy

of testing strategies

13
Code coverage tools can evaluate the completeness of a test suite that was created
with any method, including black-box testing. This allows the software team to
examine parts of a system that are rarely tested and ensures that the most important
function points have been tested. Code coverage as a software metric can be
reported as a percentage for:
Function coverage, which reports on functions executed
Statement coverage, which reports on the number of lines executed to complete
the test
100% statement coverage ensures that all code paths, or branches (in terms of
control flow) are executed at least once. This is helpful in ensuring correct
functionality, but not sufficient since the same code may process different inputs
correctly or incorrectly.

Black-box testing

Black-box testing treats the software as a "black box", examining functionality

without any knowledge of internal implementation. The tester is only aware of
what the software is supposed to do, not how it does it. Black-box testing methods
include: equivalence partitioning, boundary value analysis, all-pairs testing, state
transition tables, decision table testing, fuzz testing, model-based testing, use case
testing, exploratory testing and specification-based testing.
Specification-based testing aims to test the functionality of software according to
the applicable requirements. This level of testing usually requires thorough test
cases to be provided to the tester, who then can simply verify that for a given
input, the output value (or behaviour), either "is" or "is not" the same as the
expected value specified in the test case. Test cases are built around specifications
and requirements, i.e., what the application is supposed to do. It uses external
descriptions of the software, including specifications, requirements, and designs to
derive test cases. These tests can be functional or non-functional, though usually
functional.

Specification-based testing may be necessary to assure correct functionality, but it

is insufficient to guard against complex or high-risk situations.
One advantage of the black box technique is that no programming knowledge is
required. Whatever biases the programmers may have had, the tester likely has a
different set and may emphasize different areas of functionality. On the other hand,
black-box testing has been said to be "like a walk in a dark labyrinth without a
flashlight." Because they do not examine the source code, there are situations when
a tester writes many test cases to check something that could have been tested by
only one test case, or leaves some parts of the program untested.

14
This method of test can be applied to all levels of software testing: unit, integration,
system and acceptance. It typically comprises most if not all testing at higher
levels, but can also dominate unit testing as well.

Alpha Testing

Alpha testing is simulated or actual operational testing by potential users/customers

or an independent test team at the developers' site. Alpha testing is often employed
for off-the-shelf software as a form of internal acceptance testing, before the
software goes to beta testing.
Beta Testing

Beta testing comes after alpha testing and can be considered a form of external
user acceptance testing. Versions of the software, known as beta versions, are
released to a limited audience outside of the programming team. The software is
released to groups of people so that further testing can ensure the product has few
faults or bugs. Sometimes, beta versions are made available to the open public to
increase the feedback field to a maximal number of future users.

15
 CONCLUSION

The project “ Quiz System” aims to simplify the process of testing or evaluating
the student’s performance by computerizing it and making it user friendly.

This project makes the whole process automated as user just need to enter few
details in this to get started and then he can choose the subject of his choice on which
he want to take quiz so as to evaluate and enhance his performance. Result is generated
automatically in the end enabling student to improve his performance.

This project cover very much every function needed by user in supermarket
management system.

16
 References

1. The complete reference, Java 2, 5th edition by Herbert Schildt.

2. www.javatpoint.com/java
3. www.google.co.in
4. Oracle : A Beginner’s Guide by Michael Abbey and Michael J. Korey.

17