online exam

i

Final Year Project Report

ON

ONLINE EXAMINATION SYSTEM

By

1. Md.Abdullah-Al-Roman ID # 11126239 26th Batch

2. Shoriful Islam ID # 11126268 26th Batch

Project Supervisor: Tahmina Akter

Department of Computer Science and Engineering

CITY UNIVERSITY Ashulia khagan Dhaka, Bangladesh

April 2015

ii

BY

1. Md.Abdullah-Al-Roman ID # 11126239 26th Batch

Signature………………………Date……………………

2. Shoriful Islam ID # 11126268 26th Batch

Signature………………………Date……………………

Approved by……………………………………………………………

Project Supervisor Date…………………………..

City University Ashulia, Savar, Dhaka

iii

CERTIFICATE

This is to certify that the dissertation titled “Online Examination System”

is done by Md. Abdullah-Al-Roman & Shoriful Islam bear’s registration

ID No. 11126239 & 11126268 is a partial fulfillment of requirements of

Bachelor of Science in Computer Science and Engineering degree from

the City University, Dhaka, Bangladesh.

The dissertation has been carried out under my guidance and is a record

of work carried out successfully. No part of this dissertation consists of

materials copied or plagiarized from any published or unpublished works.

Signature of Supervisor

Tahmina Akter

Lecturer

Department of Computer Science & Engineering

iv

DECLARATION

I hereby do solemnly declare that the work presented in this dissertation has been

carried out by me and has not been previously submitted to any other University for

an academic degree.

This dissertation being submitted as a particular fulfillment of the requirement for the

Degree of Bachelor of Science in Computer Science and Engineering commenced

from April 2015 of City University is the result of my own dissertation work. That no

part of this dissertation consists of materials copied or plagiarized from published or

unpublished work of the writers and that all materials borrowed or reproduced from

other published or unpublished source have either been put under quotation or duly

acknowledged with full reference in appropriate places(s).

Signature of Author

Md.Abdullah-Al-Roman

Id. No: 11126239

Bachelor of Science in Computer Science and Engineering

City University, Dhaka, Bangladesh.

Shoriful Islam

Id. No.: 11126268

Bachelor of Science in Computer Science and Engineering

City University, Dhaka, Bangladesh.

1

ACKNOWLEDGEMENT

First of all I would like to pay my sincerest gratitude to the almighty Allah for

keeping me in sound mind and health during the work and giving me the ability to

work hard successfully.

This Project itself is an acknowledgement to the inspiration, drive and technical assistance contributed by many individuals. This project would have never seen the light of this day without the help and guidance we have received.We express our gratitude to

Professor Dr. Md. Motiur Rahman Dean, Department of Computer Science

and Engineering, City University for providing us with excellent infrastructure and awesome environment that laid potentially strong foundation for my professional life.

I express my gratitude to Professor Shafaet Hossain, Head,

Department of Computer Science and Engineering, City University

for providing me with excellent infrastructure and awesome

environment that laid potentially strong foundation for my professional

life.

I would like to express my since re thanks my project

supervisor Tahmina Akter. His constant supervision, constructive criticism,

valuable advice, scholarly guidance and encouragement at all stage of my work have

made it possible to complete this project. I shall be grateful to him for his contribution

and support.

I also express my deep grati tude to our beloved teachers Md.

Abdur Rashid, Md Asraful Hauque , Most Rokey Akter jui , Al -Mahadi

Hasan, Md Rafiqul Islam and all of other teachers for their keen

interest, timely suggestions and help for completing of this project.

With sincere regards

Md.Abdullah-Al-Roman

Id. No.: 11126239

Bachelor of Science in Computer Science and Engineering

City University, Dhaka, Bangladesh.

Shoriful Islam Id. No.: 11126268

Bachelor of Science in Computer Science and Engineering

City University, Dhaka, Bangladesh.

2

Abstract

Online Examination is an Internet based questionnaire. The questions can be

categorized according to type, topic etc. The test is compiled with questions from

different libraries. Tests are created on a random basis per student with a particular

time limit during which they are to be answered.

Online examination helps students and its mission is to offer a quick and easy way to

appear for the exam. It also provides the results immediately after the exam and

security. The user can enter to write the exam only with their valid username and

password. This examination contains multiple choice questions and appropriate

number of options. There are no limitations on number of options and it can be

randomized. More than one option can be correct but the user can select only one

option. This provides time limit. The user can see their results after completing the

exam. This helps the students to write the exam from far distance and which can

provide security and simplicity and other beneficial features to the user.

TABLE OF CONTENTS Name of The Contents Page No.

Certificate

Declaration

Acknowledgement

Abstract of the Dissertation

Table of Contents

List of Figures

List of Tables

1. Introduction 1.1 Name of the Project

1.2 Objective

2. System Analysis

2.1 Purpos

2.2 Existing System

2.2.1Limitations

2.3 Feasibility Study

2.3.1Technical Feasibility

2.3.2Economic Feasibility

2.3.3Operational Feasibility

2.4 Fact Find Techniques

2.5 Proposed System

2.5.1 Advantages

4

3 .Software Requirements Specification

4. System Architecture

5.System Requirements Specification

5.1 Purpose, scope And Overview

5.2 General Description

5.2.1 Product Perspective

5.2.2 Product Functions

5.2.3 User Characteristics

5.2.4 General Constraints

5.3 Functional Requirements

5.4 User Interface Requirements

5.5 Performance Requirements Non Functional Requirements

6. System Models

7. System Evolution

8. System Environment

8.1 Hardware Specification

8.2 Software Specification

9. System Design 9.1Introduction

9.2Context Diagram

5

9.3 Models 9.4 Activity diagram

9.5Sequence diagram

9.6 Database Design

9.7 Architectural Design

10. Snapshot

11. Testing 11.1 Testing Plan 11.2 Testing Strategy

11.3 Unit Testing

11.4 Integration Testing

11.5 System testing

11.6 Performance Testing

12 . Sample Code

13.System Maintenance

14.Scope and Limitation

15. Conclusion

16. Appendices

Biography

References

6

INTRODUCTION

1.1 Online Examination System

This document will propose all features and procedures to develop “Online Examination

System”.This document specially containing details about objectives, scope limitation,

process model, primary requirements, team development, possible project risks, project

schedule, and finally monitoring and reporting mechanisms.

Online Exam is being launched because a need for a destination that is beneficial for

both institutes and students. With this site, institutes can register and host online exams.

Students can give exams and view their results. This site is an attempt to remove

the existing flaws in the manual system of conducting exams.

Online Exam System is very useful for Educational Institute to prepare an exam, safe the

time that will take to check the paper and prepare mark sheets. It will help the Institute to

testing of students and develop their skills. But the disadvantages for this system, it takes

a lot of times when you prepare the exam at the first time for usage. And we are needs

number of computers with the same number of students.

The effective use of "Online Exam System", any Educational Institute or training centers

can be use it to develop their strategy for putting the exams, and for getting better results

in less time.

1.2 Objective and concentrations

Corporate between the data stored in the server of the Institution

and our On-line Exam system. To deal with On-line System in an

easy way and an efficient mannered. (connection process)

Create strong and secrete data base that allow for any connection in

a secret way, to prevent any outside or inside attacks.

7

Specify a privilege for each person to allow each person use this

system to create his own exam. And have a complete control on his

exam.

Allow each person to create more than one exam with different way

to create variant questions.

Chapter-2: System Analysis

2.1 Introduction

The various tasks in the system analysis include the following.

Understanding application.

Planning.

Scheduling.

Developing candidate solution.

Performing trade studies.

Performing cost benefit analysis.

Recommending alternative solutions.

Selling of the system.

Supervising, installing and maintaining the system.

System analysis involves the study of an application area to fully understand the

problem being posed. Activities are focused on developing a comprehensive

knowledge of the existing system, its strengths and weaknesses and the reasons for

the need to restructure, replace, or automate the existing system. Risk assessments

and risk containment plan, cost estimation and plans for the remainder of the

development are results usually prepared by the system analyst as a by-product of

system analysis.

8

Feasibility Study

Once scope has been identified (with the concurrence of the customer), it is reasonable to

ask: “Can we build software to meet this scope? Is the project feasible?” All too often,

software engineers rush past this questions (or are pushed past them by impatient

managers or customers), only to become mired in a project that is doomed from the onset.

When we are developing the system (software), we must know the proposed system will

be feasible or i.e. practically implemented or not it may possible the proposed( candidate

) system may not implemented due to many reasons like it may take long time in

development than the specified time limit ,cost may increase than proposed one etc.

Therefore we must analyze thefeasibility of the system. Feasibility is the analysis of risks,

costs & benefits relating to economics, technology & user operation.

There are several types of feasibility depending on the aspect they covers.

Some important feasibilities is as follows:-

(I) Technical Feasibility

(II) Operational Feasibility

III) Economical Feasibility

Technical Feasibility :

The technically feasibility study basically centers on alternatives for hardware, software

and design approach to determine the functional aspects of system. This project on

Online Examination will be platform independent since it is being coded in JAVA

language (using JSP and SERVLETS).HTML is used to create web pages. MS-Access

database will be used for storing data. Hardware requirements used are compatible with

all O.S. Only authorized person would be able to use the website so it would be secure.

The system can also be expanded as per the needs of requirement specification.

Operational Feasibility:

Operational Feasibility is a measure of how people are able to work with system. This

type of feasibility demands if the system will work when developed and installed.

Since website is very user friendly so users will find it comfortable to work on this site.

Economical Feasibility:

9

Economic analysis is the most frequently used evaluating the effectiveness of proposed

system, more commonly known as Benefit analysis. The Benefit analysis is to determine

benefits and savings which are expected from candidate system and compare them with

cost. If the benefits are more than the cost, then decision is made to design and implement

the system. The cost and benefits may be direct or indirect and tangible or intangible.

2.4 Proposed System

The project aims at relieving the user of the hardships, mentioned above in the

existing system. The passengers can enquire about various bus services specifying

their source place and destination place. They will be provided with the details of

the next available services immediately so that they can plan their journey

accordingly. It is an easy to use application and any person with an internet access

can use it. The passengers can reserve tickets.

2.4.1 Advantages of Proposed System

It is very simple to use.

It is a relatively fast approach to know the Timebase exam system.

Is highly reliable, no need physical destination .

10

Chapter-3: Software Requirement Specification

Introduction:

The purpose of this SRS document is to write the functional and non functional user or

system requirements that represent the characteristics of Online Examination System.

The scope and limitation of this system is:

The online exam system design to educational institutes.

Hold all operation and generate reports to student, teachers and administrator.

Support multiple choices questions.

Allow the student to prochoice the answer and to see his mark.

Verify a security, authority and safty.

User Requirements Definition

The user requirement for this system is to make the system fast, flexible, less prone to

error, reduce expenses and save the time.

•Time can be saved by scheduling the exams, if it is available a question bank to store

questions for different subjects.

•A system can be given a mark by checking the students answers, and give the result as

soon as students finish his exam.

•A facility to generate a result chart as pre required without manual interface. •The

system should have records of students and faculty that can be access to the system which

can be used only for the authorized person.

•The system should be more secure for management user records and more reliable to

work at any conditions.

2.1 The products and process features:

This system must be designed as user required. So, the complete requirement must be

found:

2.2Quick scheduling:

The system helps the faculty member to generate an automatic exam instead of using

papers. Which save a time for writing, checking and for input marks. Also, student can

see the exam when he login as an individual to the system.

11

2.3 Immediate results and solutions:

When the student finishes his exam, the system checks her answers and compared with

the correct answer. And the system saves the incorrect and correct answers and calculates

the mark of correct answers. Then give the total mark. And send a report for student to

see where he is fault.

2.4 Easy to store and retrieve information:

Rather to save the information on a papers or in separate sheets. There are a data base

management to store and retrieve the information needed by the administrator or Faculty

member or student according a report generated by the system.

Chapter-4: System Architecture

Web Browser

Data

Transaction Management for OES Database

Security

Manager

OES

Appointment

Manager

Data Import

& Export

Report

Generation

Login

Login

Role

checkin

g

Form & Menu

Manager

Data Validation

12

Chapter-5: System Requirements Specification

5.1Purpose

The purpose of the project is to provide online facility to Institutes to conduct online

exams and to Students to give online exams. Institutes can enter and edit the questions

along with the students list. Also they can view the result. Students can login and give

their respective exams and view their score then and there. Others can view sample

papers to get look and feel of the online examination system.

5.2 Scope

The website to conduct online examination is “Online Examimation ”. This website

provides facility to institutes to conduct online exams by providing a unique id to each

institute. The institute provides questions along with positive and negative marks. Institute

also enters the list of eligible students. All the information entered can be later edited by the

institute. In turn student can login with their id, name and instituteid to give the exams and

can view their result then and there. Institutes can also view the result of their students.

5.3 Abbreviations

JSP stands for Java Server Pages

HTTP stands for HyperText Transfer Protocol

5.4 Benefits:

This website reduces the manual work, maintaining accuracy, increasing efficiency and

saving time. Also institutes need not go to develop a new software each time, instead they

just register and conduct a test. For students, it saves time of going to far away centers

and also they can view their result then and there.

5.5 Overview The rest of this SRS document describes the various system requirements, interfaces, features

and functionalities in detail.

13

5.5.1Overall Description

In Online examination system institute can register to conduct a online test and view the

records later. Students can give the test and their respective records, which include their

marks for each test given by them, will be maintained separately. No student can take a

particular exam more than once.

5.5.2User Classes and Characteristics

a. Educational level: Users should be comfortable with the English language.

b. Experience: Users should have prior information regarding the online examinations.

c. Skills: Users should have basic knowledge and should be comfortable using general

purpose applications on computers.

5.5.3 Constraints

- Since the DBMS being used is MS Access 2000, which is not a very popular DBMS,

it will not be able to store a very huge number of records.

- Due to limited features of DBMS being used performance tuning features will not be

applied to the queries and thus the system may become slow with the increase in

number of records being stored.

- An extra security as SSL must be used to secure the marks details and other

examination information.

5.5.4 Assumptions & Dependencies

The examinations are all objective. Students can give each exam just once.

It depends that the one should follow the international standards for the generating the

User ID & should fill the related information in the proper format.

5.5.5 Apportioning of Requirements:

The future versions of the website will be having a better database to handle larger

number of records, in a more secure way.Also separate profile will be maintained later

for all students so that he can view all his previous test performances.

5.6 Functional System Requirement:

This section gives a functional requirement that applicable to the Online Exam system.

There are three sub modules in this phase.

Candidate module.

14

Examiner module.

Administrator module.

The functionality of each module is as follows:

Candidate module: The candidate will logon to the software and take his

examination. He can also check his previous examinations marks and his details.

The candidate will get result immediately after the completion of the examination.

Examiner module: The database is prepared & loaded into the software. Selection

for examination can be done language wise by the examiner. The results will be

displayed immediately after completion of the examination.

Administrator module: The administrator collects all the results after successful

completion of the examination and sends to the head quarters as and when

required.

The features that are available to the Administrator are:

The administrator has the full fledged rights over the OES.

Can create/delete an account.

Can view the accounts.

Can change the password.

Can hide any kind of features from the both of users.

Insert/delete/edit the information of available on OES.

Can access all the accounts of the faculty members/students.

The features available to the Students are:

Can view the different categories of Test available in their account.

Can change password.

Can view their marks.

Can view the various reading material.

Can view and modify its profile but can modify it to some limited range.

The features available to the Examiner are:

Can view the different categories of Test conducted by users.

Can change password.

Can view their marks.

Can view and modify Results.

15

5.7 Non-Functional System Requirements:

5.7.1 Performance Requirements

Some Performance requirements identified is listed below:

The database shall be able to accommodate a minimum of 10,000 records of

students.

The software shall support use of multiple users at a time.

There are no other specific performance requirements that will affect

development.

5.7.2 Safety Requirements

The database may get crashed at any certain time due to virus or operating system failure.

Therefore, it is required to take the database backup.

5.7.3 Security Requirements

Some of the factors that are identified to protect the software from accidental or

malicious access, use, modification, destruction, or disclosure are described below. Keep

specific log or history data sets

Assign certain functions to different modules

Restrict communications between some areas of the program

Check data integrity for critical variables

Later version of the software will incorporate encryption techniques in the

user/license authentication process.

Communication needs to be restricted when the application is validating the user

or license. (i.e., using https).

5.7.4 Software Quality Attributes

The Quality of the System is maintained in such a way so that it can be very user friendly

to all the users.

The software quality attributes are assumed as under:

Accurate and hence reliable.

Secured.

Fast speed.

Compatibility.

5.7.5 System Interfaces:

This section describes how the software interfaces with other software

products or users for input or output.

16

5.7.6 User Interface

Application will be accessed through a Browser Interface. The interface

would be viewed best using 1024 x 768 and 800 x 600 pixels resolution

setting. The software would be fully compatible with Microsoft Internet

Explorer for version 6 and above. No user would be able to access any part of

the application without logging on to the system.

5.7.6Hardware Interfaces

Server Side:

Operating System: Windows 9x/xp ,Windows ME

Processor: Pentium 3.0 GHz or higher

RAM: 256 Mb or more

Hard Drive: 10 GB or more

Client side:

Operating System: Windows 9x or above, MAC or UNIX.

Processor: Pentium III or 2.0 GHz or higher.

RAM: 256 Mb or more

5.7.7 Software Interfaces

Client Side: .HTML, Web Browser, Windows XP/2000/Vista

Web Server: .HTML, Windows XP/2000/Vista

5.7.8 Communications Interfaces

The Customer must connect to the Internet to access the Website:

Dialup Modem of 52 kbps

Broadband Internet

Dialup or Broadband Connection with a Internet Provider.

17

Chapter-6: System Models

In this system we are use waterfall model to apply these ideas. Which is help us to

separate each step and when we finish a one phase the output of it is the input to the next

phase. Also, we can backwards if there is a new requirement or to apply any update.

Chapter-7: System Evolution

7.1 Including image support:

o Allow to adding students, faculty members and administrator images to

the system. Which available for student to ensure that exam for his

teacher. Also, the teacher can see his student's image.

7.2 Flags:

o Allow the student to put a symbol near the question that helps the student

to return and review the questions and change them accordingly.

7.3 Enable and disable exam:

o Allow the faculty member to control for enable or disable the exam for his

students.

7.4 Allow to transfer exam from one subject to another:

o So, that saves the time to rewrite the questions for future course.

7.5 Allow to upload the exam from word or excel file:

o So, that saves the time to enter a question in the on-line system, if the

teacher needs not the direct answers.

7.6 Enhanced the questions to be appear as random for each student:

o Make the order of questions as random, or select random questions from a

set of questions.

18

Chapter-8. System Environment

8.1 HARDWARE SPECIFICATION

Processor : P4, 1GHz

RAM : 256 MB memory Hard Disk Drive : 20 GB disk space

Monitor : Resolution 1024 x 768

Keyboard : 10 1/102 Natural Keyboard

Mouse : PS/2Compatible

CD ROM Drive : 52x max

8.2 SOFTWARE SPECIFICATION

Client : Internet Explorer, Google Chorm

Server : Xampp, Wamp

Language :PHP, HTML, JAVA,CSS,JQUERY

19

Chapter-9. SYSTEM DESIGN

Introduction:

Design is the abstraction of a solution; it is a general description of the solution to a

problem without the details. Design is view patterns seen in the analysis phase to be a

pattern in a design phase. After design phase we can reduce the time required to create

the implementation.

In this chapter we are introduce context diagram, models, system architecture, principal

system object, design model and object interface.

Context Diagram:

This diagram represents what are the bounders and scope of Online Exam System project.

It describes the main objective of the system and its entities involved.

Figure (3.2.1): the context diagram of On-line Exam System

Online Exam

system

Administrator

Student Faculty

20

The Administrator can be done the following: Create/delete accounts (add a list of faculty names and list of his student)

Change password for Faculty/Student

Create/ delete/update courses (subject).

The Faculty can be done the following: Change password.

Insert questions.

Specify the answers.

Update mark of questions and answers.

The Student can be done the following:

Change password.

Choose exam.

Review answers.

See his exam mark.

View other material.

Models: Interaction model: Is a dynamic model that shows how the system interacts with its environment. We

use a data flow diagram.

use case diagram:

Figure (3.3.1.1.1): the basic function for each actor

Administrator

View Reports

Student

Insert Questions

Give Exam

Registration

Process

21

Activity diagram:

(a)

(b)

(c)

Figure (3.3.1.2.1): the activity diagram for basic operation in OES. (a) for administrator, (b) for

Faculty and (c) for student.

Administrator Registration

Process

Receiving details

Course details

Faculty details

Subject details

Receive master

Subject master

Course master

Faculty master

Request Report

View Report

Faculty

Insert

Questions Insert question Subject

master Question

master

Request Report

View Report

Studen

t

Give exam Registe

r

Receive

master Subject

master

Exam

master

User

master

Request Report

View Report

Control

master

22

Sequence diagram:

Receive Faculty course subject

Administrator New

registration:

Registration

process:

Receive

master DB:

Subject

master DB:

If new Insert

Faculty

master DB:

Course

master DB:

Accept/ reject

Insert

Insert

Insert

23

Figure (3.3.1.3.2): the insert question operation done by Faculty.

Enter user name and password

Faculty Login: Select

subject:

Subject

master DB:

Insert

question:

Verify

Request subject

Question

master DB:

Accept/ reject

Store question

Subject selection

Return subject

Accept/ reject

Accept/ reject

If Accept

24

Figure (3.3.1.3.3): present how student take an exam and give the result.

Store result

in DB:

Enter user name and password

Student Login

:

Select

subject:

Subject

master

DB:

Select

question

:

Verif

y Request subject

Question

master

DB:

Invalid

subject Inactive subject

Verif

y

Verif

y If

Accept

Unavailable question

Unavailable question

Start

exam

If

Accept

If

Accept

Return result and finish the exam

25

26

27

28

Data design:ER Diagram

29

Chapter-10: Snapshot

10.1 User Login Form

30

10.2 User Signup Form

31

10.3 Examination Form

32

Finish Time Remaining :20min

33

Result

34

Admin Login Form:

35

Admin Area

Chapter-8 : Sample Code

36

37

38

39

Chapter-11: Testing

Testing

- Software testing is the process of executing a program with intension of finding

errors in the code. It is a process of evolution of system or its parts by manual or

automatic means to verify that it is satisfying specified or requirements or not.

- Generally, no system is perfect due to communication problems between user and

developer, time constraints, or conceptual mistakes by developer.

- To purpose of system testing is to check and find out these errors or faults as early as

possible so losses due to it can be saved.

- Testing is the fundamental process of software success.

- Testing is not a distinct phase in system development life cycle but should be

applicable throughout all phases i.e. design development and maintenance phase.

- Testing is used to show incorrectness and considered to success when an error is

detected

11.1 UNIT TESTING

In computer programming, Unit testing is a procedure used to validate that individual

units of source code are working properly. A unit is the smallest testable part of an

application. In procedural programming a unit may be an individual program, function,

procedure etc, while in object oriented programming the smallest unit is a method, which

may belong to a base/super class, abstract class or derived/child class.

Ideally, each test case is independent from the others; mock or fake objects as well as test

harnesses can be used to assist testing a module in isolation. Unit testing is typically done

by software developers to ensure that the code they have written meets software

requirements and behaves as the developer intended.

In this test we test each module individually but not integrate the whole system. It focuses

verification efforts even in the smallest unit of software design in each module. In this

testing each ,module is focused to work satisfactorily as regard to the expected output

from the module .There are some validation checks for the fields.

40

11.2 INTEGRATION TESTING

Integration testing (sometimes called, Integration and testing, abbreviated I&T) is the

phase of software testing in which individual software modules are combined and tested

as a group. It follows unit testing and precedes system testing.

Integration testing takes as its input modules that have been unit tested groups them in

larger aggregates, applies test defined in an integration test plan to those aggregates, and

delivers as its output the Integrated system ready for system testing.

Data can be lost across an interface, one module can have adverse effect on the other sub-

functions, when combined may not produce the desired functions. Integration testing is

the systematic testing to uncover the errors within the interface. This testing is done with

simple data. The need for an integrated system is to find the overall performance.

The purpose of Integration testing is to verify functional, performance and reliability are

exercised through their interfaces using black box testing, success and error cases being

simulated via appropriate parameter and data inputs. Simulated usage of shared data areas

and inter process communication is tested and individual subsystems are exercised

through their input interface. Test cases are constructed to test that all components within

assemblages interact correctly, for eg across procedure calls or process activations, and

this is done after testing individual modules, ie, unit testing.

11.3 VALIDATION TESTING

At the culmination of black box testing (here the structure of program is not considered),

software is completely assembled as a package. Interface errors have been uncovered and

correct and final series of test, ie and validation test begins. The customer defines

validation with a simple definition and validation succeeds when the software functions

in manner than can be reasonably accepted.

11.4 ALPHA TESTING

Alpha testing refers to tests in which user or operator team from customer or client a

separate system. The user or operator team frequently employs their own operational time

lines and applications. The approach brings in additional test cases, new operators, and

more operating time on the system. Failure occurrences are documented carefully and

forwarded to the test team.

41

11.5 BETA TESTING

Beta testing involves delivery of one or more copies of the software or system to

client/customer site(s). Those sites that are given the status of beta site must commit to

reporting failures to the test team. Again with more users, with different operators, with

more operational time lines, and with more CPU time on the system, more faults will be

exposed.

11.6 TEST CASES

Test case is an object for execution for other modules in the architecture does not

represent any interaction by itself. A test case is a set of sequential steps to execute a test

operating on a set of predefined inputs to produce certain expected outputs. There are two

types of test cases:-manual and automated. A manual test case is executed manually

while an automated test case is executed using automation

In system testing , test data should cover the possible values of each parameter based on

the requirements. Since testing every value is impractical, a few values should be chosen

from each equivalence class. An equivalence class is a set of values that should all be

treated the same.

Ideally, test cases that check error conditions are written separately from the functional

test cases and should have steps to verify the error messages and logs. Realistically, if

functional test cases are not yet written, it is ok for testers to check for error conditions

when performing normal functional test cases. It should be clear which test data, if any is

expected to trigger errors.

42

11.7 OBJECTIVES OF SOFTWARE TESTING

The software testing is usually performed for the following objectives:-

SOFTWARE QUALITY IMPROVEMENT:-

The computer and the software are mainly used for complex and critical applications and a

bug or fault in software causes severe losses. So a great consideration is required for hecking

for quality of software.

VERIFICATION AND VALIDATION:-

Verification means to test that we are building the product in right way .i.e. are we using the

correct procedure for the development of software so that it can meet the user requirements.

Validation means to check whether we are building the right product or not.

SOFTWARE RELIABILTY ESTIMATION:-

The objective is to discover the residual designing errors before delivery to the customer.

The failure data during processare taken down in order to estimate the software reliability.

PRINCIPLES OF SOFTWARE TESTING

Software testing is an extremely creative and challenging task. Some important principles

of software testing are as given:-

All tests should be traceable to customer requirements.

Testing time and resources should be limited i.e. avoid redundant testing.

It is impossible to test everything.

Use effective resources to test.

Test should be planned long before testing begins i.e. after requirement phase.

Test for invalid and unexpected input conditions as well as valid conditions.

Testing should begin in “in the small” and progress towards testing “in the large”.

For the most effective testing should be conducted by an independent party.

Keep software static (without change mean while) during test.

Document test cases and test results.

Examining what the software not doing which it expected to do and also checking

what it is doing that was not expected to do.

43

STRATEGY FOR SOFTWARE TESTING

Different levels of testing are used in the test process; each level of testing aims to test

different aspects of the system.

Unit Testing

The first level is unit testing. In this testing, individual components are tested to

ensure that they operate correctly. It focuses on verification efforts.

Integration Testing

The second level is integration testing. It is a systematic technique for constructing

the program structure. In this testing, many tested modules are combined into the

subsystem which are then tested. The good here is to see if the modules can be

integrated properly.

Third level is integration testing. System testing is actually a series of different tests

whose primary purpose is to fully exercise computer based system. These tests fall

outside scope of software process and are not conducted solely by software engine

44

Chapter- 12. System Maintenance

The results obtained from the evaluation process help the organization to determine

whether its information systems are effective and efficient or otherwise. As the

organization existing in a dynamic and competitive environment evaluation is a

continuing activity. On the basis of the feedback provided by the evaluation process the

organization in order to keep its system at the highest levels of effectiveness and

efficiency of course within cost constraints must respond by taking corrective actions. It

may include removing errors and enhancing the existing system. The process of

monitoring, evaluating and modifying of existing information systems to make required

or desirable improvements may be termed as system maintenance.

When the system is in maintenance phase, some people with in the system are

responsible for collecting maintenance requests from users and other interested parties.

The process of maintaining system is the process of returning to the beginning of system

development phase until changes implemented.

System maintenance is the activity that occurs following the delivery of the software

product enhancement to software products adapting products to new environment and

correcting errors. Software products enhancement may involve providing new functional

capabilities improving user displays and modes of intersection or upgrading the performance

characteristics of the system.

The maintenance includes three set of activities.

Corrective.

Adaptive.

Perfective.

45

13.Scope and limitations:

•On-line Exam system is designed for Educational Institutes (like schools,

universities, training centers).

•The system handles all the operations, and generates reports as soon as the

test is finish, that includes name, mark, time spent to solve the exam.

•Allow students to see or display his answers after the exam is finish.

•The type of questions is only multiple choice or true and false.

14.Conclusion

This Web Application provides facility to conduct online examination world wide. It

saves time as it allows number of students to give the exam at a time and displays the

results as the test gets over, so no need to wait for the result. It is automatically generated

by the server. Administrator has a privilege to create, modify and delete the test papers

and its particular questions. User can register, login and give the test with

his specific id, and can see the results as well.

46

15.Appendices:

Definition of online examination system:

Introduction:

Online Examination System is a software application which allows a particular company

or institute to arrange, conduct and manage any objective examination via online.

Purpose:

The purpose of this application is to conduct and process various types of certificate/non-

certificate exams at different centers across any country via online.

Features:

Any institute or company can register their various types of certificate/non-certificate programs and conduct an online examination for the same.

Just register the programs, their fees (if paid) and the centers (where the exam will be conducted) in order to start the examination process.

Questions and answers would be objective type and the format would be as per the company’s choice.

User can select the company, its program, exam schedule and pay fees online in order to give his exam at the selected center.

Advantages:

Today, most of the companies or institutes are conducting their exams online to be a part of this fastest growing world.

Online Examination System covers almost all type of problems faced by a company or institute while conducting online examinations.

User can give any available exam at any available center as per his/her choice.

The results of the online exam will help a company or institute to list out the outstanding exam takers all over the country.

47

Bibliography

The following books were very helpful during the completion of project

BOOK:

System Analysis and Design : Elias M Awad

Elements of System Analysis and design: Marvin Gore/John W

Software Engineering

-K.K. Aggarwal and Yogesh Singh

Web Enabled Commercial Appplication Development

-Ivan Bayross

Head First Servlets and JSP

-Bryan Basham,Kathy Sierra and Bert Bates

48

References: 1. [1] Software Requirements Specification for project iTest, 2008

2. [2] http:// www.scribd.com/doc/33852099/on-line-examiniation-system-project-

report

3. Tu. 21/12/2011.

4. [3]http://whatis.techtarget.com/definition/0,,sid9_gci1103696,00.html, Sat.

29/10/2011.

5. [4] Software Requirements Specification for Problem Based Learning Module,

Souman Mandal, 2010.

6. [5] Software Design Specification (SDS) Acropolis Course Management System,

2011

7. [6] IEEE Recommended Practice for Software Requirements Specifications,

Software Engineering Standards Committee of the IEEE Computer Society. 1998

8. [7] Software Requirements Specification for PPDP Contact Management System

(CMS)

9. [8] http://www.ehow.com/facts_5156877_preface-book.html, Sat. 29/10/2011.

10. [9]http://www.sil.org/lingualinks/literacy/referencematerials/glossaryofliteracyter

ms/WhatIsAPreface.htm, Sat. 29/10/2011.

11. [10] http://www.deftinfosystems.com/index.php/application/e-education-

system/online-examination-system.html, Mon. 9/1/2012.

12. [11] Software Requirement Specifications, Online Examination System.

13. www.phppoint.com

14. www.programmar2programmar.com

15. www.kasparia.com