Online examination system
60,960 views
41 slides
Mar 14, 2013
Slide 1 of 41
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
About This Presentation
Online Examination Series (OLES) is a Multiple Choice Questions (MCQ) based
examination system. It provides an easy to use environment for both Test Conductors
and Students appearing for Examination. The main objective of OLES is to provide
all the features that an Examination System must have, w...
Slide Content
Online Examination System
A mini project report submitted in partial fulfillment of III semester in degree of
MASTER OF COMPUTER SCIENCE
specialization in
Artificial Intelligence
By:
VIKRAM SINGH SLATHIA
Enroll. No.2011MAI025
RAJESH SAHU
Enroll. No.2011MAI014
Under the Supervision of:
Mehul Mahrishi
Department of Computer Science
School of Mathematics Statistics and Computer Science
CENTRAL UNIVERSITY OF RAJASTHAN
AJMER
November 2012
A mini project report submitted in partial fulfillment of III semester in degree of
MASTER OF COMPUTER SCIENCE
specialization in
Artificial Intelligence
By:
VIKRAM SINGH SLATHIA
Enroll. No.2011MAI025
RAJESH SAHU
Enroll. No.2011MAI014
Under the Supervision of:
Mehul Mahrishi
Department of Computer Science
School of Mathematics Statistics and Computer Science
CENTRAL UNIVERSITY OF RAJASTHAN
AJMER
November 2012
ii
CANDIDATES DECLARATION
I hereby declare that the work presented in this Mini project report entitled, Online
Examination System in partial fulfilment for the III semester of Degree of Master of
Computer Science in Computer Science with specialization in Artificial Intelligence and
submitted in Department of Computer Science, Central University of Rajasthan is a record
of my own investigations carried under the guidance of Mehul Mahrishi, department of
Computer Science.
I have not submitted the matter presented in this report anywhere for the award of any
other degree.
Date: 26
th
of November, 2012
(Signature)
Place: Curaj Vikram Singh Slathia
Enroll. No 2011MAI025
Rajesh Sahu
Enroll. No 2011MAI014
CANDIDATES DECLARATION
I hereby declare that the work presented in this Mini project report entitled, Online
Examination System in partial fulfilment for the III semester of Degree of Master of
Computer Science in Computer Science with specialization in Artificial Intelligence and
submitted in Department of Computer Science, Central University of Rajasthan is a record
of my own investigations carried under the guidance of Mehul Mahrishi, department of
Computer Science.
I have not submitted the matter presented in this report anywhere for the award of any
other degree.
Date: 26
th
of November, 2012
(Signature)
Place: Curaj Vikram Singh Slathia
Enroll. No 2011MAI025
Rajesh Sahu
Enroll. No 2011MAI014
iii
CERTIFICATE
This is to certify that the mini project report (Code MAI 316) entitled Online Examination
System done by Vikram Singh Slathia, Enrollment No 2011MAI025 and Rajesh Sahu,
Enrollment No 2011MAI0 is an authentic work carried out by him at University under my
guidance. The matter embodied in this dissertation/project work has not been submitted
earlier for the award of any degree or diploma to the best of my knowledge and belief.
Date: 26
th
of November, 2012
Mehul Mahrishi
Assistant Professor
Dept. of Computer Science
Central University of Rajasthan
CERTIFICATE
This is to certify that the mini project report (Code MAI 316) entitled Online Examination
System done by Vikram Singh Slathia, Enrollment No 2011MAI025 and Rajesh Sahu,
Enrollment No 2011MAI0 is an authentic work carried out by him at University under my
guidance. The matter embodied in this dissertation/project work has not been submitted
earlier for the award of any degree or diploma to the best of my knowledge and belief.
Date: 26
th
of November, 2012
Mehul Mahrishi
Assistant Professor
Dept. of Computer Science
Central University of Rajasthan
iv
ACKNOWLEDGEMENT
I would like to take this opportunity to express my sincere gratitude towards my
supervisor .Mehul Mahrishi for his invaluable guidance during the progress from the
beginning to the completion of this project.
I also wish to thank all the faculty members of Central University of Rajasthan who
gave me valuable knowledge through their lectures. At this place, I have got plenty of
fundamental and advanced knowledge for my career.
I am indebted my mother, my father and friends for all the encouragement and moral
support.
Vikram Singh Slathia
Rajesh Sahu
ACKNOWLEDGEMENT
I would like to take this opportunity to express my sincere gratitude towards my
supervisor .Mehul Mahrishi for his invaluable guidance during the progress from the
beginning to the completion of this project.
I also wish to thank all the faculty members of Central University of Rajasthan who
gave me valuable knowledge through their lectures. At this place, I have got plenty of
fundamental and advanced knowledge for my career.
I am indebted my mother, my father and friends for all the encouragement and moral
support.
Vikram Singh Slathia
Rajesh Sahu
v
ABSTRACT
Online Examination System is web based application for technical evaluation. OLES not only
replace paperwork but also releases the workload of faculty. Most of e-examination system
only have fixed no of question without randomization, so they have pool scalability. The
proposed system has a comprehensive test engine with randomization of questions and it also
allow users to give feedback of system The OLES overcomes the shortcoming of existing
online examination systems and has better extensibility and flexibility.
ABSTRACT
Online Examination System is web based application for technical evaluation. OLES not only
replace paperwork but also releases the workload of faculty. Most of e-examination system
only have fixed no of question without randomization, so they have pool scalability. The
proposed system has a comprehensive test engine with randomization of questions and it also
allow users to give feedback of system The OLES overcomes the shortcoming of existing
online examination systems and has better extensibility and flexibility.
vi
TTTaaabbbllleee ooofff CCCooonnnttteeennntttsss
Abstract v
List of Figures viii
List of Screen shots viii
List of tables viii
Definitions, Acronyms & Abbreviations viii
Chapter Page no.
1. Introduction 1-2
1.1 Introduction 1
1.2 Scope 1
1.3 Taxonomy of OLES 1-2
1.3.1 Administrators 1
1.3.2 Faculty 2
1.3.3 Student 2
1.4 Existing systems 2
1.5 Disadvantages of existing systems 2
1.6 Objective of proposed system 2
1.7 Limitation 2
1.8 Origination of reports 2
2. Analysis 3-6
2.1 Introduction 3
2.2 Feasibility study 3-4
2.2.1 Economical Feasibility 3
2.2.2 Technical Feasibility 4
2.2.3 Legal Feasibility 4
2.2.4 Operational Feasibility 4
2.2.5 Behavioural Feasibility 4
2.3 Software Requirement specifications 5
2.3.1 Proposed 5
2.3.2 Scope 5
2.3.3 Specification requirement 5
2.3.3.1 Software requirement 5
2.3.3.2 Hardware requirement 5
2.4 User requirement 6
2.5 Constraints 6
2.6 Conclusion 6
3. Design 7-14
3.1 UML Diagrams 7-10
3.1.1 Class Diagrams 7
3.1.2 Use case diagrams 9
3.1.3 Sequence diagrams 10
TTTaaabbbllleee ooofff CCCooonnnttteeennntttsss
Abstract v
List of Figures viii
List of Screen shots viii
List of tables viii
Definitions, Acronyms & Abbreviations viii
Chapter Page no.
1. Introduction 1-2
1.1 Introduction 1
1.2 Scope 1
1.3 Taxonomy of OLES 1-2
1.3.1 Administrators 1
1.3.2 Faculty 2
1.3.3 Student 2
1.4 Existing systems 2
1.5 Disadvantages of existing systems 2
1.6 Objective of proposed system 2
1.7 Limitation 2
1.8 Origination of reports 2
2. Analysis 3-6
2.1 Introduction 3
2.2 Feasibility study 3-4
2.2.1 Economical Feasibility 3
2.2.2 Technical Feasibility 4
2.2.3 Legal Feasibility 4
2.2.4 Operational Feasibility 4
2.2.5 Behavioural Feasibility 4
2.3 Software Requirement specifications 5
2.3.1 Proposed 5
2.3.2 Scope 5
2.3.3 Specification requirement 5
2.3.3.1 Software requirement 5
2.3.3.2 Hardware requirement 5
2.4 User requirement 6
2.5 Constraints 6
2.6 Conclusion 6
3. Design 7-14
3.1 UML Diagrams 7-10
3.1.1 Class Diagrams 7
3.1.2 Use case diagrams 9
3.1.3 Sequence diagrams 10
vii
3.2 Data Flow Diagrams 12
3.3 Module design of system 13
3.3.1 Description of Modules 13
3.3.1.1 Student Module 14
3.3.1.2 Exam Module 14
3.3.1.3 Administrator module 14
4. Implementation and Coding 15-29
4.1 Code 15-21
4.2 Screen Shots 22-27
4.3 Tables 28-29
5. Testing and Validation 30-32
5.1 Introduction 30
5.2 Design of test cases and scenario 30
5.2.1 Integration Testing 30
5.2.2 Validation Testing 31
5.2.2.1 Validation Test Criteria 31
5.2.2.2 Configuration Review 31
5.2.3 Alpha testing and Beta Testing 31
5.2.4 System Testing 31
5.3 Generation of test cases 32
5.4 Validation 32
5.5 Conclusion 32
6. Conclusion and Future work 33
6.1 Conclusion 33
6.2 Future work 33
7. Reference 34
3.2 Data Flow Diagrams 12
3.3 Module design of system 13
3.3.1 Description of Modules 13
3.3.1.1 Student Module 14
3.3.1.2 Exam Module 14
3.3.1.3 Administrator module 14
4. Implementation and Coding 15-29
4.1 Code 15-21
4.2 Screen Shots 22-27
4.3 Tables 28-29
5. Testing and Validation 30-32
5.1 Introduction 30
5.2 Design of test cases and scenario 30
5.2.1 Integration Testing 30
5.2.2 Validation Testing 31
5.2.2.1 Validation Test Criteria 31
5.2.2.2 Configuration Review 31
5.2.3 Alpha testing and Beta Testing 31
5.2.4 System Testing 31
5.3 Generation of test cases 32
5.4 Validation 32
5.5 Conclusion 32
6. Conclusion and Future work 33
6.1 Conclusion 33
6.2 Future work 33
7. Reference 34
viii
List of Figures
3.1.1 Class Diagram 8
3.1.2 Use Case Diagram 9
3.1.3.1 Sequence diagram for login system 11
3.2 Data Flow Diagram 13
List of Screens Shots
4.2 Screen Shots 22-26
4.2.1 Home page 22
4.2.2 Login form 23
4.2.2.1 Error for login form with wrong ID and Password 23
4.2.2.2 Successfully login to test with correct ID and Password 24
4.2.3 Instruction form after successfully login 24
4.2.3 Exam form 25
4.2.4 Result form 25
4.2.4 Feedback form 26
4.2.5 FAQ form 26
List of Database tables
4.3.1 Member 27-28
4.3.2 Add question 27
4.3.3 Login table 27
4.4.4 Temp Mark Table 28
4.3.5 Marks 28
Definitions, Acronyms & Abbreviations
OLES Online Examination System
SRS Software Requirement specifications
IT Information Technology
CS Computer Science
FAQ Frequently Asked Questions
List of Figures
3.1.1 Class Diagram 8
3.1.2 Use Case Diagram 9
3.1.3.1 Sequence diagram for login system 11
3.2 Data Flow Diagram 13
List of Screens Shots
4.2 Screen Shots 22-26
4.2.1 Home page 22
4.2.2 Login form 23
4.2.2.1 Error for login form with wrong ID and Password 23
4.2.2.2 Successfully login to test with correct ID and Password 24
4.2.3 Instruction form after successfully login 24
4.2.3 Exam form 25
4.2.4 Result form 25
4.2.4 Feedback form 26
4.2.5 FAQ form 26
List of Database tables
4.3.1 Member 27-28
4.3.2 Add question 27
4.3.3 Login table 27
4.4.4 Temp Mark Table 28
4.3.5 Marks 28
Definitions, Acronyms & Abbreviations
OLES Online Examination System
SRS Software Requirement specifications
IT Information Technology
CS Computer Science
FAQ Frequently Asked Questions
1
Chapter 1
Introduction
1.1 Introduction
Online Examination Series (OLES) is a Multiple Choice Questions (MCQ) based
examination system. It provides an easy to use environment for both Test Conductors
and Students appearing for Examination. The main objective of OLES is to provide
all the features that an Examination System must have, with the "interfaces that don't
Scare it's Users!".
1.2 Scope
· The main purpose of the system is to efficiently evaluate the candidate
thoroughly through a fully automated system that not only saves a lot of time
but also gives fast results.
· It is a cost-effective and popular means of mass- evaluation system.
· The administrator of the system prepares the tests and questions for each
exam.
· The candidates can login through the client computers with their register
number given to them and can take the exam.
· The questions are shuffled in a random order so that possibilities for getting
questions in the same order for the students who are beside, is very less.
1.3 Taxonomy of OLES
Users of OLES are classified into three categories:
· Administrators,
· Test Conductors and
· Students
1.3.1 Administrators
Administrators are responsible for management of system users, tests, results and
system backup etc.
Chapter 1
Introduction
1.1 Introduction
Online Examination Series (OLES) is a Multiple Choice Questions (MCQ) based
examination system. It provides an easy to use environment for both Test Conductors
and Students appearing for Examination. The main objective of OLES is to provide
all the features that an Examination System must have, with the "interfaces that don't
Scare it's Users!".
1.2 Scope
· The main purpose of the system is to efficiently evaluate the candidate
thoroughly through a fully automated system that not only saves a lot of time
but also gives fast results.
· It is a cost-effective and popular means of mass- evaluation system.
· The administrator of the system prepares the tests and questions for each
exam.
· The candidates can login through the client computers with their register
number given to them and can take the exam.
· The questions are shuffled in a random order so that possibilities for getting
questions in the same order for the students who are beside, is very less.
1.3 Taxonomy of OLES
Users of OLES are classified into three categories:
· Administrators,
· Test Conductors and
· Students
1.3.1 Administrators
Administrators are responsible for management of system users, tests, results and
system backup etc.
Chapter 1 Introduction
2
1.3.2 Faculty
Test conductors are responsible for preparing schedule of tests and questions.
1.3.3 Students
Students are the candidates who are appearing for the Exam.
1.4 Existing system
The Existing system of conducting examination process is manual.
Existing system is a large man power process and is difficult to implement it at
different platform. It has so many problems. So we introduce a OLES system, which
is fully computerized. Existing system is a large man power process and is difficult to
implement.
1.5 Disadvantages of existing system
· The existing systems are very time consuming.
· It is difficult to analyze the exam manually.
· Results are not precise as calculation and evaluations are done manually.
· Result processing after summation of exam takes more time as it is done
manually.
1.6 Objective of proposed system
· Economic feasibility
· Time Flexibility
· Technical feasibility
· User-friendly interface
1.7 Limitation of Project
There are already many Online Examination System and they are directly launching
their own web sites which can be accessed by the users. The limitation of this project
is that it runs on a single server within the education institute or corporate world but
not over internet. An Intranet application can provide much better security.
1.8 Organisation of Report
In this project documentation we have initially put the definition and objective of the
project as well as the design of the project which is followed by the implementation
and testing phases. The project has been concluded successfully and the future
enhancements of the project also given in this documentation.
2
1.3.2 Faculty
Test conductors are responsible for preparing schedule of tests and questions.
1.3.3 Students
Students are the candidates who are appearing for the Exam.
1.4 Existing system
The Existing system of conducting examination process is manual.
Existing system is a large man power process and is difficult to implement it at
different platform. It has so many problems. So we introduce a OLES system, which
is fully computerized. Existing system is a large man power process and is difficult to
implement.
1.5 Disadvantages of existing system
· The existing systems are very time consuming.
· It is difficult to analyze the exam manually.
· Results are not precise as calculation and evaluations are done manually.
· Result processing after summation of exam takes more time as it is done
manually.
1.6 Objective of proposed system
· Economic feasibility
· Time Flexibility
· Technical feasibility
· User-friendly interface
1.7 Limitation of Project
There are already many Online Examination System and they are directly launching
their own web sites which can be accessed by the users. The limitation of this project
is that it runs on a single server within the education institute or corporate world but
not over internet. An Intranet application can provide much better security.
1.8 Organisation of Report
In this project documentation we have initially put the definition and objective of the
project as well as the design of the project which is followed by the implementation
and testing phases. The project has been concluded successfully and the future
enhancements of the project also given in this documentation.
3
Chapter 2
Analysis
2.1 Introduction
After analyzing the requirements of the task to be performed, the next step is to
analyze the problem and understand its context. The first activity in the phase is to
studying the existing system and other is to understand the requirements and domain
of the new system. Both the activities are equally important but the first activity
serves as a basis of giving the functional specifications and then successful design of
the proposed system. Understanding the properties and requirements of a new system
is more difficult and requires creative thinking as well as understanding of existing
system is also difficult. Improper understanding of present system can lead diversion
from solution
2.2 Feasibility study
Feasibility is a measure of how beneficial the development of the application will be
to an organization. This is done by investigating the existing system in the area under
investigation or generally ideas about a new system. It is a test of a system proposal
according to its workability, impact on the organization, ability to meet user needs,
and effective use of resources.
The key considerations are involved in the feasibility analysis are:
Economic, Technical, Legal, Operational and Behavioural feasibility.
.
2.2.1 Economic feasibility
Economic analysis is the most frequently used method for evaluating the effectiveness
of a proposed system. It is more commonly known as cost benefit analysis, the
procedure to determine the benefits and saving that are expected from a candidate
system and compare them with costs. If the benefits outweigh costs then a decision is
made to design and implement the system. Otherwise make alterations in the
proposed system.
The innovation of the new system has much influence on the economical
side of the company. Manual system is highly cost driven due to the high labour costs.
Chapter 2
Analysis
2.1 Introduction
After analyzing the requirements of the task to be performed, the next step is to
analyze the problem and understand its context. The first activity in the phase is to
studying the existing system and other is to understand the requirements and domain
of the new system. Both the activities are equally important but the first activity
serves as a basis of giving the functional specifications and then successful design of
the proposed system. Understanding the properties and requirements of a new system
is more difficult and requires creative thinking as well as understanding of existing
system is also difficult. Improper understanding of present system can lead diversion
from solution
2.2 Feasibility study
Feasibility is a measure of how beneficial the development of the application will be
to an organization. This is done by investigating the existing system in the area under
investigation or generally ideas about a new system. It is a test of a system proposal
according to its workability, impact on the organization, ability to meet user needs,
and effective use of resources.
The key considerations are involved in the feasibility analysis are:
Economic, Technical, Legal, Operational and Behavioural feasibility.
.
2.2.1 Economic feasibility
Economic analysis is the most frequently used method for evaluating the effectiveness
of a proposed system. It is more commonly known as cost benefit analysis, the
procedure to determine the benefits and saving that are expected from a candidate
system and compare them with costs. If the benefits outweigh costs then a decision is
made to design and implement the system. Otherwise make alterations in the
proposed system.
The innovation of the new system has much influence on the economical
side of the company. Manual system is highly cost driven due to the high labour costs.
Chapter 2 Analysis
4
So if we register with the OLES, they can automate their day-to-day activities. Thus
the system is economically feasible.
2.2.2 Technical feasibility
In examining Technical feasibility of the system, more importance is given to the
hardware interaction part of the system. In OLES Permission to the users would be
granted based on the roles specified. Therefore, it provides the technical guarantee of
accuracy, reliability and security.
OLE does not require any addition hardware or software. Since the
interface for this system is developed using the existing resources and technologies
available at NIC, There is nominal expenditure and feasibility for certain.
2.2.3 Legal feasibility
People are inherently resistant to change, and computers have been
known to facilitate change. An estimate should be made about the reaction of the user
staff towards the development of a computerized system. Computer installations have
something to do with turnover, transfers and changes in job status. The introduction of
a candidate system requires special effort to educate, sell and train the staff for
conducting the business.
The system is designed such that even a computer ignorant person can
easily interact with the system. So the OLES not requires much effort to train and
educate people, the system is that much legally feasible.
2.2.4 Operational Feasibility
Proposed projects are beneficial only if they can be turned out into information
system. That will meet the organizations operating requirements. Operational
feasibility aspects of the project are to be taken as an important part of the project
implementation.
Some of the important issues raised are to test the operational feasibility of a project
includes the following:
Is there sufficient support for the management from the users?
Will the system be used and work properly if it is being developed and implemented?
Will there be any resistance from the user that will undermine the possible application
benefits?
This system is targeted to be in accordance with the above-mentioned issues. The
well-planned design would ensure the optimal utilization of the computer resources
and would help in the improvement of performance status.
2.2.5 Behavioural feasibility
People are inherently resistant to change and computer has been known to facilitate
changes. An estimate should be made of how strong the user is likely to move towards
the development of fully computerized system. These are various levels of users in
4
So if we register with the OLES, they can automate their day-to-day activities. Thus
the system is economically feasible.
2.2.2 Technical feasibility
In examining Technical feasibility of the system, more importance is given to the
hardware interaction part of the system. In OLES Permission to the users would be
granted based on the roles specified. Therefore, it provides the technical guarantee of
accuracy, reliability and security.
OLE does not require any addition hardware or software. Since the
interface for this system is developed using the existing resources and technologies
available at NIC, There is nominal expenditure and feasibility for certain.
2.2.3 Legal feasibility
People are inherently resistant to change, and computers have been
known to facilitate change. An estimate should be made about the reaction of the user
staff towards the development of a computerized system. Computer installations have
something to do with turnover, transfers and changes in job status. The introduction of
a candidate system requires special effort to educate, sell and train the staff for
conducting the business.
The system is designed such that even a computer ignorant person can
easily interact with the system. So the OLES not requires much effort to train and
educate people, the system is that much legally feasible.
2.2.4 Operational Feasibility
Proposed projects are beneficial only if they can be turned out into information
system. That will meet the organizations operating requirements. Operational
feasibility aspects of the project are to be taken as an important part of the project
implementation.
Some of the important issues raised are to test the operational feasibility of a project
includes the following:
Is there sufficient support for the management from the users?
Will the system be used and work properly if it is being developed and implemented?
Will there be any resistance from the user that will undermine the possible application
benefits?
This system is targeted to be in accordance with the above-mentioned issues. The
well-planned design would ensure the optimal utilization of the computer resources
and would help in the improvement of performance status.
2.2.5 Behavioural feasibility
People are inherently resistant to change and computer has been known to facilitate
changes. An estimate should be made of how strong the user is likely to move towards
the development of fully computerized system. These are various levels of users in
Chapter 2 Analysis
5
order to ensure proper authentication, authorization and security of sensitive data of
the organization
Administrators are responsible for management of system users, tests, results and
system backup etc.
2.3 Software requirement specification
2.3.1 Proposed
The main objective of the Online Examination System is that it helps
educational institutions and corporate world to conduct exams to any number of
candidates at a time, in an automated manner. It reduces the time consumption and
workload that exist in the current system of examination. It also helps in storing the
record of each examination and the results are also stored in the system. This makes
the searching of the records easier than the existing system.
2.3.2 Scope
· OLES can be used in educational institutions as well as in corporate world.
· The system handles all the operations and generates reports as soon as the test is
completed which saves the precious time of faculties spent on reviewing answer
sheets.
· OLES is a cost-effective and popular means of mass- evaluation system.
· The administrator of the system prepares the tests and questions for each exam.
· The candidates can login through the client computers with their Enrolment
number given to them by the university and can take the exam.
· The questions are shuffled in a random order so that possibilities for getting
questions in the same order for the students who are sitting beside is very less.
· Can be used anywhere any time as it is a web based application.
2.3.3 Specific requirements
2.3.3.1 Software requirement
· Operating System
o Windows XP and others.
· Front End
o Visual Basic. Net Platform 2010
· Back End
o MySQL
· Browser
o Internet Explorer and others.
2.3.3.2 Hardware Requirement
· Client Side:
o Browser
Any Browser
5
order to ensure proper authentication, authorization and security of sensitive data of
the organization
Administrators are responsible for management of system users, tests, results and
system backup etc.
2.3 Software requirement specification
2.3.1 Proposed
The main objective of the Online Examination System is that it helps
educational institutions and corporate world to conduct exams to any number of
candidates at a time, in an automated manner. It reduces the time consumption and
workload that exist in the current system of examination. It also helps in storing the
record of each examination and the results are also stored in the system. This makes
the searching of the records easier than the existing system.
2.3.2 Scope
· OLES can be used in educational institutions as well as in corporate world.
· The system handles all the operations and generates reports as soon as the test is
completed which saves the precious time of faculties spent on reviewing answer
sheets.
· OLES is a cost-effective and popular means of mass- evaluation system.
· The administrator of the system prepares the tests and questions for each exam.
· The candidates can login through the client computers with their Enrolment
number given to them by the university and can take the exam.
· The questions are shuffled in a random order so that possibilities for getting
questions in the same order for the students who are sitting beside is very less.
· Can be used anywhere any time as it is a web based application.
2.3.3 Specific requirements
2.3.3.1 Software requirement
· Operating System
o Windows XP and others.
· Front End
o Visual Basic. Net Platform 2010
· Back End
o MySQL
· Browser
o Internet Explorer and others.
2.3.3.2 Hardware Requirement
· Client Side:
o Browser
Any Browser
Chapter 2 Analysis
6
o Processor :
Pentium 2.0 and above.
o RAM :
256 MB
· Server Side:
o Processor :
Pentium and above.
o RAM :
1 GB
o Hard disk space :
4GB
2.4 User Requirements:
Every user should be:
· Comfortably work with computer.
· He must also have basic knowledge of English.
2.5 Constraints:
· Graphical user interface is only in English.
· Enrolment ID and password is used for identification of user and there is no
facility for guest.
· Only registered users will be authorized to use the services.
· Limited to HTTP or HTTPS.
· This system is working for single server.
2.6 Conclusion
In this phase, we understand the software requirement specifications for the system.
We arrange all the required components to develop the project in this phase itself so
that we will have a clear idea regarding the requirements before designing the project.
Thus we will proceed to the design phase followed by the implementation phase of
the project
.
6
o Processor :
Pentium 2.0 and above.
o RAM :
256 MB
· Server Side:
o Processor :
Pentium and above.
o RAM :
1 GB
o Hard disk space :
4GB
2.4 User Requirements:
Every user should be:
· Comfortably work with computer.
· He must also have basic knowledge of English.
2.5 Constraints:
· Graphical user interface is only in English.
· Enrolment ID and password is used for identification of user and there is no
facility for guest.
· Only registered users will be authorized to use the services.
· Limited to HTTP or HTTPS.
· This system is working for single server.
2.6 Conclusion
In this phase, we understand the software requirement specifications for the system.
We arrange all the required components to develop the project in this phase itself so
that we will have a clear idea regarding the requirements before designing the project.
Thus we will proceed to the design phase followed by the implementation phase of
the project
.
7
Chapter 3
Design
3.1 UML Diagrams
Unified Modelling Language (UML) is a standardized general-purpose modelling
language in the field of software engineering. It is used to modify, visualize,
construct, specify and document the artifacts of an object-oriented software intensive
system under development. UML combines best techniques from data modelling (ER
diagrams), business modelling, object modelling, and component modelling. It can be
used with all processes, throughout a software development life cycle, and across
different implementation technologies.
3.1.1 Class Diagram
Class diagram in the UML is a type of static structure diagram that describes the
structure of a system by showing the system's classes, their attributes, and the
relationships between the classes. It is the main building block in object oriented
modelling. It is being used both for general conceptual modelling of the systematic of
the application, and for detailed modelling translating the models into programming
code.
The classes in a class diagram represent both the main objects and interactions in the
application and the objects to be programmed. In the class diagram these classes are
represented with boxes which contain 3 parts:
· The upper part holds the name of the class.
· The middle part contains the attributes of the class, and
· The bottom part gives the methods or operations the class can take.
Chapter 3
Design
3.1 UML Diagrams
Unified Modelling Language (UML) is a standardized general-purpose modelling
language in the field of software engineering. It is used to modify, visualize,
construct, specify and document the artifacts of an object-oriented software intensive
system under development. UML combines best techniques from data modelling (ER
diagrams), business modelling, object modelling, and component modelling. It can be
used with all processes, throughout a software development life cycle, and across
different implementation technologies.
3.1.1 Class Diagram
Class diagram in the UML is a type of static structure diagram that describes the
structure of a system by showing the system's classes, their attributes, and the
relationships between the classes. It is the main building block in object oriented
modelling. It is being used both for general conceptual modelling of the systematic of
the application, and for detailed modelling translating the models into programming
code.
The classes in a class diagram represent both the main objects and interactions in the
application and the objects to be programmed. In the class diagram these classes are
represented with boxes which contain 3 parts:
· The upper part holds the name of the class.
· The middle part contains the attributes of the class, and
· The bottom part gives the methods or operations the class can take.
Chapter 3 Design
8
Class Diagram
8
Class Diagram
Chapter 3 Design
9
3.1.2 Use case Diagram
Use case diagram in the Unified Modeling Language (UML) 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 (represented as use cases), and any dependencies between those use cases.
Its main purpose is to show what system functions are performed for which actor.
Roles of the actors in the system can be depicted
9
3.1.2 Use case Diagram
Use case diagram in the Unified Modeling Language (UML) 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 (represented as use cases), and any dependencies between those use cases.
Its main purpose is to show what system functions are performed for which actor.
Roles of the actors in the system can be depicted
3.1.3 Sequence Diagram:
Sequence diagrams document the interactions between classes to achieve a result,
such as a use case. Because UML is designed for object
communications between classes are known as messages. The Sequence diagram lists
objects horizontally, and time vertically, and models these messages over time.
Notation
In a Sequence diagram, classes and actors are listed as columns, with vertical lifelines
indicating the lifetime of the object over time.
Object
Objects are instances of class
arranged horizontally. The pictorial
representation for an Object is a class with
the name prefixed by the object name
(optional) and a semi
Actor
Actors can also communicate with objects,
so they too can be listed as a column. An
A
symbol, the stick figure.
Lifeline
The Lifeline identifies the existence of the
object over time. The notation for a Lifeline
is a vertical dotted line extending from an
object.
Activation
Activations,
on the lifeline, indicate when the object is
performing an action.
Message
Messages,
between Activations, indicate the
communications between objects.
Diagram:
Sequence diagrams document the interactions between classes to achieve a result,
such as a use case. Because UML is designed for object-oriented programming, these
communications between classes are known as messages. The Sequence diagram lists
izontally, and time vertically, and models these messages over time.
In a Sequence diagram, classes and actors are listed as columns, with vertical lifelines
indicating the lifetime of the object over time.
Objects are instances of classes, and are
arranged horizontally. The pictorial
representation for an Object is a class with
the name prefixed by the object name
(optional) and a semi-colon.
Actors can also communicate with objects,
so they too can be listed as a column. An
Actor is modelled using the ubiquitous
symbol, the stick figure.
The Lifeline identifies the existence of the
object over time. The notation for a Lifeline
is a vertical dotted line extending from an
object.
Activations, modelled as rectangular boxes
on the lifeline, indicate when the object is
performing an action.
Messages, modelled as horizontal arrows
between Activations, indicate the
communications between objects.
Chapter 3 Design
10
Sequence diagrams document the interactions between classes to achieve a result,
oriented programming, these
communications between classes are known as messages. The Sequence diagram lists
izontally, and time vertically, and models these messages over time.
In a Sequence diagram, classes and actors are listed as columns, with vertical lifelines
es, and are
arranged horizontally. The pictorial
representation for an Object is a class with
the name prefixed by the object name
Actors can also communicate with objects,
so they too can be listed as a column. An
using the ubiquitous
The Lifeline identifies the existence of the
object over time. The notation for a Lifeline
is a vertical dotted line extending from an
as rectangular boxes
on the lifeline, indicate when the object is
as horizontal arrows
between Activations, indicate the
Sequence diagrams document the interactions between classes to achieve a result,
such as a use case. Because UML is designed for object
communications between classes are known as messages. The Sequence diagram lists
objects horizontally, and time vertically, and models these messages over time.
Notation
In a Sequence diagram, classes and actors are listed as columns, with vertical lifelines
indicating the lifetime of the object over time.
Object
Objects are instances of class
arranged horizontally. The pictorial
representation for an Object is a class with
the name prefixed by the object name
(optional) and a semi
Actor
Actors can also communicate with objects,
so they too can be listed as a column. An
A
symbol, the stick figure.
Lifeline
The Lifeline identifies the existence of the
object over time. The notation for a Lifeline
is a vertical dotted line extending from an
object.
Activation
Activations,
on the lifeline, indicate when the object is
performing an action.
Message
Messages,
between Activations, indicate the
communications between objects.
Diagram:
Sequence diagrams document the interactions between classes to achieve a result,
such as a use case. Because UML is designed for object-oriented programming, these
communications between classes are known as messages. The Sequence diagram lists
izontally, and time vertically, and models these messages over time.
In a Sequence diagram, classes and actors are listed as columns, with vertical lifelines
indicating the lifetime of the object over time.
Objects are instances of classes, and are
arranged horizontally. The pictorial
representation for an Object is a class with
the name prefixed by the object name
(optional) and a semi-colon.
Actors can also communicate with objects,
so they too can be listed as a column. An
Actor is modelled using the ubiquitous
symbol, the stick figure.
The Lifeline identifies the existence of the
object over time. The notation for a Lifeline
is a vertical dotted line extending from an
object.
Activations, modelled as rectangular boxes
on the lifeline, indicate when the object is
performing an action.
Messages, modelled as horizontal arrows
between Activations, indicate the
communications between objects.
Chapter 3 Design
10
Sequence diagrams document the interactions between classes to achieve a result,
oriented programming, these
communications between classes are known as messages. The Sequence diagram lists
izontally, and time vertically, and models these messages over time.
In a Sequence diagram, classes and actors are listed as columns, with vertical lifelines
es, and are
arranged horizontally. The pictorial
representation for an Object is a class with
the name prefixed by the object name
Actors can also communicate with objects,
so they too can be listed as a column. An
using the ubiquitous
The Lifeline identifies the existence of the
object over time. The notation for a Lifeline
is a vertical dotted line extending from an
as rectangular boxes
on the lifeline, indicate when the object is
as horizontal arrows
between Activations, indicate the
Chapter 3 Design
11
3.1.3.1 Sequence Diagram for Login System
11
3.1.3.1 Sequence Diagram for Login System
Chapter 3 Design
12
3.2 Data Flow Diagram
The dataflow model represents the process as a set of activities each of which carries
out some data transformation. It shows how the input to the process such as
specification is transformed to an output such as design. The activities here maybe
lower than in a workflow model. They may represent transformations carries out by
people or computers. Four notations are used to complete a DFD.
These notations are given below:-
· Data flow:-
The data flow is used to describe the movement of information from one part
of the system to another part. Flows represent data in motion. It is a pipe line
through which information flows.
Data flow is represented by an arrow.
· Function:-
A circle or bubble represents a process that transforms incoming data to
outgoing data. Process shows a part of the system that transform inputs to
outputs.
· Input or Output:-
A square defines a source or destination of system data. External entities
represent any entity that supplies or receive information from the system but is
not a part of the system.
· Data store:-
The data store represents a logical file. A logical file can represent either a
data store symbol which can represent either a data structure or a physical file
on disk. The data store is used to collect data at rest or a temporary repository
of data. It is represented by open rectangle.
12
3.2 Data Flow Diagram
The dataflow model represents the process as a set of activities each of which carries
out some data transformation. It shows how the input to the process such as
specification is transformed to an output such as design. The activities here maybe
lower than in a workflow model. They may represent transformations carries out by
people or computers. Four notations are used to complete a DFD.
These notations are given below:-
· Data flow:-
The data flow is used to describe the movement of information from one part
of the system to another part. Flows represent data in motion. It is a pipe line
through which information flows.
Data flow is represented by an arrow.
· Function:-
A circle or bubble represents a process that transforms incoming data to
outgoing data. Process shows a part of the system that transform inputs to
outputs.
· Input or Output:-
A square defines a source or destination of system data. External entities
represent any entity that supplies or receive information from the system but is
not a part of the system.
· Data store:-
The data store represents a logical file. A logical file can represent either a
data store symbol which can represent either a data structure or a physical file
on disk. The data store is used to collect data at rest or a temporary repository
of data. It is represented by open rectangle.
Chapter 3 Design
13
Level 0 Online Examination Systems
3.3 Module design of system
In this phase, we understand the software requirement specifications for the system.
We arrange all the required components to develop the project in this phase itself so
that we will have a clear idea regarding the requirements before designing the project.
Thus we will proceed to the design phase followed by the implementation phase of
the project
.
The processes involved are
· Announcement
o Examination Announcement , here the date of start of examination
another details are handled
· Schedule
o The schedule of the examination is made here
· Admit card
o Student ID card use as a admit card
3.3.1 Description for Modules
There are 3 types of the modules
o Student Module
o Exam Module
o Administrator module
13
Level 0 Online Examination Systems
3.3 Module design of system
In this phase, we understand the software requirement specifications for the system.
We arrange all the required components to develop the project in this phase itself so
that we will have a clear idea regarding the requirements before designing the project.
Thus we will proceed to the design phase followed by the implementation phase of
the project
.
The processes involved are
· Announcement
o Examination Announcement , here the date of start of examination
another details are handled
· Schedule
o The schedule of the examination is made here
· Admit card
o Student ID card use as a admit card
3.3.1 Description for Modules
There are 3 types of the modules
o Student Module
o Exam Module
o Administrator module
Chapter 3 Design
14
3.3.1.1 Student Module
The student module contain another module
· Login to the online examination system.
o There is a quality window because in this person only enter by
login
o Enrolment ID of student is user id and password by which a
person enter the system.
3.3.1.2 Exam Module
Examination process
a) Login to the online examination system.
b) Attend Test
c) Submit
Test page
This is a most creative and important page in this project.
· This test page includes:-
o Timer
o Skip
o Next
o Previous
o Finish.
· The form of questions in test page:-
o Multiple choice questions
o The questions are selected at random
3.3.1.3 Administrator Module:
The module protected by user id and password. This is encrypted format. So ordinary
users of the software will not be permitted to enter the administrator module of the
software. The module will be focusing on the maintenance like Master Data entry
operation.
14
3.3.1.1 Student Module
The student module contain another module
· Login to the online examination system.
o There is a quality window because in this person only enter by
login
o Enrolment ID of student is user id and password by which a
person enter the system.
3.3.1.2 Exam Module
Examination process
a) Login to the online examination system.
b) Attend Test
c) Submit
Test page
This is a most creative and important page in this project.
· This test page includes:-
o Timer
o Skip
o Next
o Previous
o Finish.
· The form of questions in test page:-
o Multiple choice questions
o The questions are selected at random
3.3.1.3 Administrator Module:
The module protected by user id and password. This is encrypted format. So ordinary
users of the software will not be permitted to enter the administrator module of the
software. The module will be focusing on the maintenance like Master Data entry
operation.
15
Chapter 4
Implementation and Coding
4.1 Code
4.1.1 Login form
Imports MySql.Data
Imports MySql.Data.MySqlClient
Public Class login
Inherits System.Web.UI.Page
Dim dbcom As MySqlConnection
Dim stquery As String = ""
Dim sqlcmd As MySqlCommand
Dim dr As MySqlDataReader
Dim paa As String
Protected Sub Page_Load(ByVal sender As Object, ByVal e As
System.EventArgs) Handles Me.Load
End Sub
Protected Sub Button1_Click(ByVal sender As Object, ByVal e As EventArgs)
Handles Button1.Click
Try
dbcom = New
MySqlConnection("Server=localhost;Database=onlineexam;Uid=root;pwd=mysql")
stquery = "SELECT * FROM logintable where UserName='" &
TextBox1.Text & "'"
sqlcmd = New MySqlCommand(stquery, dbcom)
'MsgBox(stquery)
dbcom.Open()
dr = sqlcmd.ExecuteReader
While dr.Read
' TextBox2.Text = dr.Item("Password")
Chapter 4
Implementation and Coding
4.1 Code
4.1.1 Login form
Imports MySql.Data
Imports MySql.Data.MySqlClient
Public Class login
Inherits System.Web.UI.Page
Dim dbcom As MySqlConnection
Dim stquery As String = ""
Dim sqlcmd As MySqlCommand
Dim dr As MySqlDataReader
Dim paa As String
Protected Sub Page_Load(ByVal sender As Object, ByVal e As
System.EventArgs) Handles Me.Load
End Sub
Protected Sub Button1_Click(ByVal sender As Object, ByVal e As EventArgs)
Handles Button1.Click
Try
dbcom = New
MySqlConnection("Server=localhost;Database=onlineexam;Uid=root;pwd=mysql")
stquery = "SELECT * FROM logintable where UserName='" &
TextBox1.Text & "'"
sqlcmd = New MySqlCommand(stquery, dbcom)
'MsgBox(stquery)
dbcom.Open()
dr = sqlcmd.ExecuteReader
While dr.Read
' TextBox2.Text = dr.Item("Password")
Chapter 4 Implementation and Coding
16
paa = dr.Item("Password")
'MsgBox(paa)
End While
If TextBox2.Text <> paa Then
MsgBox("wrong username-password, try again")
Else
MsgBox("Login success")
Response.Redirect("~/examinstruction.aspx")
End If
dr.Close()
dbcom.Close()
Catch ex As Exception
' MsgBox("failure to communicate!" & vbCrLf & vbCrLf & ex.Message)
End Try
End Sub
End Class
4.1.2 Instruction page
Imports MySql.Data
Imports MySql.Data.MySqlClient
Public Class examinstruction
Inherits System.Web.UI.Page
Dim dbcom As MySqlConnection
Dim stquery As String = ""
Dim sqlcmd As MySqlCommand
Dim dr As MySqlDataReader
Dim paa As String
Protected Sub Page_Load(ByVal sender As Object, ByVal e As
System.EventArgs) Handles Me.Load
End Sub
Protected Sub LinkButton6_Click(ByVal sender As Object, ByVal e As
EventArgs) Handles LinkButton6.Click
Try
dbcom = New
MySqlConnection("Server=localhost;Database=onlineexam;Uid=root;pwd=mysql")
'For i = 1 To 20
stquery = "create table addq1 as select * from addquestion order by rand()
limit 20;"
sqlcmd = New MySqlCommand(stquery, dbcom)
dbcom.Open()
dr = sqlcmd.ExecuteReader
' dr.Read()
'While dr.Read()
'End While
dr.Close()
16
paa = dr.Item("Password")
'MsgBox(paa)
End While
If TextBox2.Text <> paa Then
MsgBox("wrong username-password, try again")
Else
MsgBox("Login success")
Response.Redirect("~/examinstruction.aspx")
End If
dr.Close()
dbcom.Close()
Catch ex As Exception
' MsgBox("failure to communicate!" & vbCrLf & vbCrLf & ex.Message)
End Try
End Sub
End Class
4.1.2 Instruction page
Imports MySql.Data
Imports MySql.Data.MySqlClient
Public Class examinstruction
Inherits System.Web.UI.Page
Dim dbcom As MySqlConnection
Dim stquery As String = ""
Dim sqlcmd As MySqlCommand
Dim dr As MySqlDataReader
Dim paa As String
Protected Sub Page_Load(ByVal sender As Object, ByVal e As
System.EventArgs) Handles Me.Load
End Sub
Protected Sub LinkButton6_Click(ByVal sender As Object, ByVal e As
EventArgs) Handles LinkButton6.Click
Try
dbcom = New
MySqlConnection("Server=localhost;Database=onlineexam;Uid=root;pwd=mysql")
'For i = 1 To 20
stquery = "create table addq1 as select * from addquestion order by rand()
limit 20;"
sqlcmd = New MySqlCommand(stquery, dbcom)
dbcom.Open()
dr = sqlcmd.ExecuteReader
' dr.Read()
'While dr.Read()
'End While
dr.Close()
Chapter 4 Implementation and Coding
17
dbcom.Close()
'Next i
Catch ex As Exception
MsgBox("failure to communicate!" & vbCrLf & vbCrLf & ex.Message)
End Try
Response.Redirect("~/examform1.aspx")
End Sub
End Class
4.1.3 Examination form
Imports MySql.Data
Imports MySql.Data.MySqlClient
Public Class examform1
Inherits System.Web.UI.Page
Dim dbcom As MySqlConnection
Dim stquery As String = ""
Dim sqlcmd As MySqlCommand
Dim dr As MySqlDataReader
Dim drtable As New DataTable
Protected Sub Button1_Click(ByVal sender As Object, ByVal e As EventArgs)
Handles Button1.Click
Try
'Button3.Visible = True
dbcom = New
MySqlConnection("Server=localhost;Database=onlineexam;Uid=root;pwd= mysql")
stquery = "select question,option1,option2,option3,option4 fr om
addq1;"
sqlcmd = New MySqlCommand(stquery, dbcom)
dbcom.Open()
dr = sqlcmd.ExecuteReader
drtable.Load(dr)
GridView1.DataSource = drtable
GridView1.DataBind()
' For i = 1 To 20
' stquery = "select * from addquestion order by ran d() limit 20;"
'stquery = "select * from addq1;"q
' sqlcmd = New MySqlCommand(stquery, dbcom)
'dbcom.Open()
'dr = sqlcmd.ExecuteReader
' dr.Read()
'While dr.Read()
' Label1.Text = dr.Item("qid")
'Label2.Text = dr.Item("question")
'RadioButton1.Text = dr.Item("option1")
'RadioButton2.Text = dr.Item("option2")
'RadioButton3.Text = dr.Item("option3")
'RadioButton4.Text = dr.Item("option4")
'End While
' dr.Close()
' dbcom.Close()
'Next i
dr.Close()
dbcom.Close()
Catch ex As Exception
MsgBox("failure to communicate!" & vbCrLf & vbCrLf & ex.Message)
End Try
Button1.Visible = False
17
dbcom.Close()
'Next i
Catch ex As Exception
MsgBox("failure to communicate!" & vbCrLf & vbCrLf & ex.Message)
End Try
Response.Redirect("~/examform1.aspx")
End Sub
End Class
4.1.3 Examination form
Imports MySql.Data
Imports MySql.Data.MySqlClient
Public Class examform1
Inherits System.Web.UI.Page
Dim dbcom As MySqlConnection
Dim stquery As String = ""
Dim sqlcmd As MySqlCommand
Dim dr As MySqlDataReader
Dim drtable As New DataTable
Protected Sub Button1_Click(ByVal sender As Object, ByVal e As EventArgs)
Handles Button1.Click
Try
'Button3.Visible = True
dbcom = New
MySqlConnection("Server=localhost;Database=onlineexam;Uid=root;pwd= mysql")
stquery = "select question,option1,option2,option3,option4 fr om
addq1;"
sqlcmd = New MySqlCommand(stquery, dbcom)
dbcom.Open()
dr = sqlcmd.ExecuteReader
drtable.Load(dr)
GridView1.DataSource = drtable
GridView1.DataBind()
' For i = 1 To 20
' stquery = "select * from addquestion order by ran d() limit 20;"
'stquery = "select * from addq1;"q
' sqlcmd = New MySqlCommand(stquery, dbcom)
'dbcom.Open()
'dr = sqlcmd.ExecuteReader
' dr.Read()
'While dr.Read()
' Label1.Text = dr.Item("qid")
'Label2.Text = dr.Item("question")
'RadioButton1.Text = dr.Item("option1")
'RadioButton2.Text = dr.Item("option2")
'RadioButton3.Text = dr.Item("option3")
'RadioButton4.Text = dr.Item("option4")
'End While
' dr.Close()
' dbcom.Close()
'Next i
dr.Close()
dbcom.Close()
Catch ex As Exception
MsgBox("failure to communicate!" & vbCrLf & vbCrLf & ex.Message)
End Try
Button1.Visible = False
Chapter 4 Implementation and Coding
18
End Sub
Private Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs)
Handles Me.Load
Response.Cache.SetCacheability(HttpCacheability.NoCache)
'dbcom = New
MySqlConnection("Server=localhost;Database=onlineex am;Uid=root;pwd=mysql")
' For i = 1 To 20
' stquery = "select * from addquestion order by ran d() limit 1;
End Sub
Protected Sub Button4_Click(ByVal sender As Object, ByVal e As EventArgs)
Handles Button4.Click
Dim a(10) As Char
Dim b(10) As Char
Dim right As Integer
Dim wrong As Integer
right = 0
wrong = 0
Try
dbcom = New
MySqlConnection("Server=localhost;Database=onlineexam;Uid=root;pwd= mysql")
stquery = "select * from addq1;"
sqlcmd = New MySqlCommand(stquery, dbcom)
dbcom.Open()
dr = sqlcmd.ExecuteReader
For i = 1 To 10
dr.Read()
a(i) = dr.Item("answer")
Next i
If RadioButtonList1.SelectedValue = "1" Then
b(1) = "1"
ElseIf RadioButtonList1.SelectedValue = "2" Then
b(1) = "2"
ElseIf RadioButtonList1.SelectedValue = "3" Then
b(1) = "3"
ElseIf RadioButtonList1.SelectedValue = "4" Then
b(1) = "4"
End If
If RadioButtonList2.SelectedValue = "1" Then
b(2) = "1"
ElseIf RadioButtonList2.SelectedValue = "2" Then
b(2) = "2"
ElseIf RadioButtonList2.SelectedValue = "3" Then
b(2) = "3"
ElseIf RadioButtonList2.SelectedValue = "4" Then
b(2) = "4"
End If
If RadioButtonList3.SelectedValue = "1" Then
b(3) = "1"
ElseIf RadioButtonList3.SelectedValue = "2" Then
b(3) = "2"
ElseIf RadioButtonList3.SelectedValue = "3" Then
b(3) = "3"
ElseIf RadioButtonList3.SelectedValue = "4" Then
b(3) = "4"
End If
If RadioButtonList4.SelectedValue = "1" Then
b(4) = "1"
ElseIf RadioButtonList4.SelectedValue = "2" Then
b(4) = "2"
18
End Sub
Private Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs)
Handles Me.Load
Response.Cache.SetCacheability(HttpCacheability.NoCache)
'dbcom = New
MySqlConnection("Server=localhost;Database=onlineex am;Uid=root;pwd=mysql")
' For i = 1 To 20
' stquery = "select * from addquestion order by ran d() limit 1;
End Sub
Protected Sub Button4_Click(ByVal sender As Object, ByVal e As EventArgs)
Handles Button4.Click
Dim a(10) As Char
Dim b(10) As Char
Dim right As Integer
Dim wrong As Integer
right = 0
wrong = 0
Try
dbcom = New
MySqlConnection("Server=localhost;Database=onlineexam;Uid=root;pwd= mysql")
stquery = "select * from addq1;"
sqlcmd = New MySqlCommand(stquery, dbcom)
dbcom.Open()
dr = sqlcmd.ExecuteReader
For i = 1 To 10
dr.Read()
a(i) = dr.Item("answer")
Next i
If RadioButtonList1.SelectedValue = "1" Then
b(1) = "1"
ElseIf RadioButtonList1.SelectedValue = "2" Then
b(1) = "2"
ElseIf RadioButtonList1.SelectedValue = "3" Then
b(1) = "3"
ElseIf RadioButtonList1.SelectedValue = "4" Then
b(1) = "4"
End If
If RadioButtonList2.SelectedValue = "1" Then
b(2) = "1"
ElseIf RadioButtonList2.SelectedValue = "2" Then
b(2) = "2"
ElseIf RadioButtonList2.SelectedValue = "3" Then
b(2) = "3"
ElseIf RadioButtonList2.SelectedValue = "4" Then
b(2) = "4"
End If
If RadioButtonList3.SelectedValue = "1" Then
b(3) = "1"
ElseIf RadioButtonList3.SelectedValue = "2" Then
b(3) = "2"
ElseIf RadioButtonList3.SelectedValue = "3" Then
b(3) = "3"
ElseIf RadioButtonList3.SelectedValue = "4" Then
b(3) = "4"
End If
If RadioButtonList4.SelectedValue = "1" Then
b(4) = "1"
ElseIf RadioButtonList4.SelectedValue = "2" Then
b(4) = "2"
Chapter 4 Implementation and Coding
19
ElseIf RadioButtonList4.SelectedValue = "3" Then
b(4) = "3"
ElseIf RadioButtonList4.SelectedValue = "4" Then
b(4) = "4"
End If
If RadioButtonList5.SelectedValue = "1" Then
b(5) = "1"
ElseIf RadioButtonList5.SelectedValue = "2" Then
b(5) = "2"
ElseIf RadioButtonList5.SelectedValue = "3" Then
b(5) = "3"
ElseIf RadioButtonList5.SelectedValue = "4" Then
b(5) = "4"
End If
If RadioButtonList6.SelectedValue = "1" Then
b(6) = "1"
ElseIf RadioButtonList6.SelectedValue = "2" Then
b(6) = "2"
ElseIf RadioButtonList6.SelectedValue = "3" Then
b(6) = "3"
ElseIf RadioButtonList6.SelectedValue = "4" Then
b(6) = "4"
End If
If RadioButtonList7.SelectedValue = "1" Then
b(7) = "1"
ElseIf RadioButtonList7.SelectedValue = "2" Then
b(7) = "2"
ElseIf RadioButtonList7.SelectedValue = "3" Then
b(7) = "3"
ElseIf RadioButtonList7.SelectedValue = "4" Then
b(7) = "4"
End If
If RadioButtonList8.SelectedValue = "1" Then
b(8) = "1"
ElseIf RadioButtonList8.SelectedValue = "2" Then
b(8) = "2"
ElseIf RadioButtonList8.SelectedValue = "3" Then
b(8) = "3"
ElseIf RadioButtonList8.SelectedValue = "4" Then
b(8) = "4"
End If
If RadioButtonList9.SelectedValue = "1" Then
b(9) = "1"
ElseIf RadioButtonList9.SelectedValue = "2" Then
b(9) = "2"
ElseIf RadioButtonList9.SelectedValue = "3" Then
b(9) = "3"
ElseIf RadioButtonList9.SelectedValue = "4" Then
b(9) = "4"
End If
If RadioButtonList10.SelectedValue = "1" Then
b(10) = "1"
ElseIf RadioButtonList10.SelectedValue = "2" Then
b(10) = "2"
ElseIf RadioButtonList10.SelectedValue = "3" Then
b(10) = "3"
19
ElseIf RadioButtonList4.SelectedValue = "3" Then
b(4) = "3"
ElseIf RadioButtonList4.SelectedValue = "4" Then
b(4) = "4"
End If
If RadioButtonList5.SelectedValue = "1" Then
b(5) = "1"
ElseIf RadioButtonList5.SelectedValue = "2" Then
b(5) = "2"
ElseIf RadioButtonList5.SelectedValue = "3" Then
b(5) = "3"
ElseIf RadioButtonList5.SelectedValue = "4" Then
b(5) = "4"
End If
If RadioButtonList6.SelectedValue = "1" Then
b(6) = "1"
ElseIf RadioButtonList6.SelectedValue = "2" Then
b(6) = "2"
ElseIf RadioButtonList6.SelectedValue = "3" Then
b(6) = "3"
ElseIf RadioButtonList6.SelectedValue = "4" Then
b(6) = "4"
End If
If RadioButtonList7.SelectedValue = "1" Then
b(7) = "1"
ElseIf RadioButtonList7.SelectedValue = "2" Then
b(7) = "2"
ElseIf RadioButtonList7.SelectedValue = "3" Then
b(7) = "3"
ElseIf RadioButtonList7.SelectedValue = "4" Then
b(7) = "4"
End If
If RadioButtonList8.SelectedValue = "1" Then
b(8) = "1"
ElseIf RadioButtonList8.SelectedValue = "2" Then
b(8) = "2"
ElseIf RadioButtonList8.SelectedValue = "3" Then
b(8) = "3"
ElseIf RadioButtonList8.SelectedValue = "4" Then
b(8) = "4"
End If
If RadioButtonList9.SelectedValue = "1" Then
b(9) = "1"
ElseIf RadioButtonList9.SelectedValue = "2" Then
b(9) = "2"
ElseIf RadioButtonList9.SelectedValue = "3" Then
b(9) = "3"
ElseIf RadioButtonList9.SelectedValue = "4" Then
b(9) = "4"
End If
If RadioButtonList10.SelectedValue = "1" Then
b(10) = "1"
ElseIf RadioButtonList10.SelectedValue = "2" Then
b(10) = "2"
ElseIf RadioButtonList10.SelectedValue = "3" Then
b(10) = "3"
Chapter 4 Implementation and Coding
20
ElseIf RadioButtonList10.SelectedValue = "4" Then
b(10) = "4"
End If
' MsgBox(b(1))
' MsgBox(b(2))
If b(1) <> a(1) Then
wrong = wrong + 1
Else
right = right + 1
End If
If b(2) <> a(2) Then
wrong = wrong + 1
Else
right = right + 1
End If
If b(3) <> a(3) Then
wrong = wrong + 1
Else
right = right + 1
End If
If b(4) <> a(4) Then
wrong = wrong + 1
Else
right = right + 1
End If
If b(5) <> a(5) Then
wrong = wrong + 1
Else
right = right + 1
End If
If b(6) <> a(6) Then
wrong = wrong + 1
Else
right = right + 1
End If
If b(7) <> a(7) Then
wrong = wrong + 1
Else
right = right + 1
End If
If b(8) <> a(8) Then
wrong = wrong + 1
Else
right = right + 1
End If
If b(9) <> a(9) Then
wrong = wrong + 1
Else
right = right + 1
End If
If b(10) <> a(10) Then
wrong = wrong + 1
Else
right = right + 1
End If
dr.Close()
dbcom.Close()
Catch ex As Exception
MsgBox("failure to communicate!" & vbCrLf & vbCrLf & ex.Message)
End Try
20
ElseIf RadioButtonList10.SelectedValue = "4" Then
b(10) = "4"
End If
' MsgBox(b(1))
' MsgBox(b(2))
If b(1) <> a(1) Then
wrong = wrong + 1
Else
right = right + 1
End If
If b(2) <> a(2) Then
wrong = wrong + 1
Else
right = right + 1
End If
If b(3) <> a(3) Then
wrong = wrong + 1
Else
right = right + 1
End If
If b(4) <> a(4) Then
wrong = wrong + 1
Else
right = right + 1
End If
If b(5) <> a(5) Then
wrong = wrong + 1
Else
right = right + 1
End If
If b(6) <> a(6) Then
wrong = wrong + 1
Else
right = right + 1
End If
If b(7) <> a(7) Then
wrong = wrong + 1
Else
right = right + 1
End If
If b(8) <> a(8) Then
wrong = wrong + 1
Else
right = right + 1
End If
If b(9) <> a(9) Then
wrong = wrong + 1
Else
right = right + 1
End If
If b(10) <> a(10) Then
wrong = wrong + 1
Else
right = right + 1
End If
dr.Close()
dbcom.Close()
Catch ex As Exception
MsgBox("failure to communicate!" & vbCrLf & vbCrLf & ex.Message)
End Try
Chapter 4 Implementation and Coding
21
Me.Dispose()
Try
dbcom = New
MySqlConnection("Server=localhost;Database=onlineexam;Uid=root;pwd= mysql")
stquery = "drop table addq1;"
sqlcmd = New MySqlCommand(stquery, dbcom)
dbcom.Open()
dr = sqlcmd.ExecuteReader
dr.Read()
dr.Close()
dbcom.Close()
Catch ex As Exception
MsgBox("failure to communicate!" & vbCrLf & vbCrLf & ex.Message)
End Try
Response.Redirect("default.aspx", False)
Response.Redirect("examform1.aspx", False)
Dim apcookie As New HttpCookie("right")
apcookie.Value = right
apcookie.Expires = DateAndTime.Now.AddHours(5)
Response.Cookies.Add(apcookie)
Dim apcookie1 As New HttpCookie("wrong")
apcookie1.Value = wrong
apcookie1.Expires = DateAndTime.Now.AddHours(5)
Response.Cookies.Add(apcookie1)
Response.Redirect("result.aspx")
End Sub
End Class
4.1.4 Coding of result form
Public Class result
Inherits System.Web.UI.Page
Protected Sub Page_Load(ByVal sender As Object, ByVal e As
System.EventArgs) Handles Me.Load
If Not Request.Cookies("right") Is Nothing Then
Dim apcookie As HttpCookie = Request.Cookies("right")
Label1.Text = apcookie.Value
End If
If Not Request.Cookies("wrong") Is Nothing Then
Dim apcookie1 As HttpCookie = Request.Cookies("wrong")
Label2.Text = apcookie1.Value
End If
Label6.Text = Label1.Text
End Sub
Protected Sub Button1_Click(ByVal sender As Object, ByVal e As EventArgs)
Handles Button1.Click
MsgBox("Thanks for given Exam")
Me.Dispose()
Response.Redirect("default.aspx")
End Sub
End Class
21
Me.Dispose()
Try
dbcom = New
MySqlConnection("Server=localhost;Database=onlineexam;Uid=root;pwd= mysql")
stquery = "drop table addq1;"
sqlcmd = New MySqlCommand(stquery, dbcom)
dbcom.Open()
dr = sqlcmd.ExecuteReader
dr.Read()
dr.Close()
dbcom.Close()
Catch ex As Exception
MsgBox("failure to communicate!" & vbCrLf & vbCrLf & ex.Message)
End Try
Response.Redirect("default.aspx", False)
Response.Redirect("examform1.aspx", False)
Dim apcookie As New HttpCookie("right")
apcookie.Value = right
apcookie.Expires = DateAndTime.Now.AddHours(5)
Response.Cookies.Add(apcookie)
Dim apcookie1 As New HttpCookie("wrong")
apcookie1.Value = wrong
apcookie1.Expires = DateAndTime.Now.AddHours(5)
Response.Cookies.Add(apcookie1)
Response.Redirect("result.aspx")
End Sub
End Class
4.1.4 Coding of result form
Public Class result
Inherits System.Web.UI.Page
Protected Sub Page_Load(ByVal sender As Object, ByVal e As
System.EventArgs) Handles Me.Load
If Not Request.Cookies("right") Is Nothing Then
Dim apcookie As HttpCookie = Request.Cookies("right")
Label1.Text = apcookie.Value
End If
If Not Request.Cookies("wrong") Is Nothing Then
Dim apcookie1 As HttpCookie = Request.Cookies("wrong")
Label2.Text = apcookie1.Value
End If
Label6.Text = Label1.Text
End Sub
Protected Sub Button1_Click(ByVal sender As Object, ByVal e As EventArgs)
Handles Button1.Click
MsgBox("Thanks for given Exam")
Me.Dispose()
Response.Redirect("default.aspx")
End Sub
End Class
Chapter 4 Implementation and Coding
22
4.2 Screen Shots
4.2.1 Home Page
.
4.2.2 Login form
· There is a quality window because in this person only enter by
login
· Enrolment ID of student is user id and password by which a
person enter the system.
22
4.2 Screen Shots
4.2.1 Home Page
.
4.2.2 Login form
· There is a quality window because in this person only enter by
login
· Enrolment ID of student is user id and password by which a
person enter the system.
Chapter 4 Implementation and Coding
23
4.2.2.1 Error for Login Page with wrong ID or Password:
23
4.2.2.1 Error for Login Page with wrong ID or Password:
Chapter 4 Implementation and Coding
24
4.2.2.2 Successfully login with correct ID or Password:
4.2.3 Instructions form after login
24
4.2.2.2 Successfully login with correct ID or Password:
4.2.3 Instructions form after login
Chapter 4 Implementation and Coding
25
4.2.4 Exam form
4.2.5 Result Page
25
4.2.4 Exam form
4.2.5 Result Page
4.2.6 Feedback form
4.2.7 FAQ form
Chapter 4 Implementation and Coding Chapter 4 Implementation and Coding
26
4.2.7 FAQ form
Chapter 4 Implementation and Coding Chapter 4 Implementation and Coding
26
Chapter 4 Implementation and Coding
27
4.3 Database Tables
4.3.1 Member
S.no Name Data type Length
1. ReNo(PK) int 9
2. Fname varchar 50
3 Lname varchar 50
4 CAddress varchar 50
5 PAdd varchar 50
6 CNo varchar 9
7 Age Int 9
8 Gender varchar 50
9 Email varchar 50
10 UserName varchr 50
11 Password varchar 50
12 CPassword varchar 50
4.3.2 Add question
S.no Name Data type Length
1 qid(PK) Int 9
2 question Varchar 50
3 Option1 Varchar 50
4 Option2 Varchar 50
5 Option3 Varchar 50
6 Option4 Varchar 50
7 answer Varchar 50
4.3.3 login table
S.no Name Data type Length
1 Username varchar 50
1 Password varchar 50
27
4.3 Database Tables
4.3.1 Member
S.no Name Data type Length
1. ReNo(PK) int 9
2. Fname varchar 50
3 Lname varchar 50
4 CAddress varchar 50
5 PAdd varchar 50
6 CNo varchar 9
7 Age Int 9
8 Gender varchar 50
9 Email varchar 50
10 UserName varchr 50
11 Password varchar 50
12 CPassword varchar 50
4.3.2 Add question
S.no Name Data type Length
1 qid(PK) Int 9
2 question Varchar 50
3 Option1 Varchar 50
4 Option2 Varchar 50
5 Option3 Varchar 50
6 Option4 Varchar 50
7 answer Varchar 50
4.3.3 login table
S.no Name Data type Length
1 Username varchar 50
1 Password varchar 50
Chapter 4 Implementation and Coding
28
4.3.4 Temp mark table
S.no Name Data type Length
1 Qid Int 9
2 UserName Varchar 50
3 NRQuestion Int 9
4 NWQuestion Int 9
5 TMark Int 9
4.3.5 Marks
S.no Name Data type Length
1 SeNo(PK) int 9
2 UserName varchar 50
3 TMark int 9
4 Percentage int 9
5 NORight int 9
6 NOWrong int 9
7 Date datetime 10
28
4.3.4 Temp mark table
S.no Name Data type Length
1 Qid Int 9
2 UserName Varchar 50
3 NRQuestion Int 9
4 NWQuestion Int 9
5 TMark Int 9
4.3.5 Marks
S.no Name Data type Length
1 SeNo(PK) int 9
2 UserName varchar 50
3 TMark int 9
4 Percentage int 9
5 NORight int 9
6 NOWrong int 9
7 Date datetime 10
30
Chapter 5
Testing and Validation
5.1 Introduction
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.
The following are the Testing Objectives:
· Testing is a process of executing a program with the intent of finding an error
· A good test has a high probability of finding an as yet undiscovered error.
· A successful test is one that uncovers an as yet undiscovered error.
5.2 Design of test cases &scenario
The objective is to design tests that systematically uncover different classes of errors
and do so with a minimum amount of time and effort. Testing cannot show the
absence of defects, it can only show that software defects are present.
5.2.1 Integration Testing
Modules integrated by moving down the program design hierarchy. Can use depth
first or breadth first top down integration verifies major control and decision points
early in design process. Top-level structure tested most. Depth first implementation
allows a complete function to be implemented, tested and demonstrated and does
depth first implementation of critical functions early. Top down integration forced (to
some extent) by some development tools in programs with graphical user interfaces.
Chapter 5
Testing and Validation
5.1 Introduction
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.
The following are the Testing Objectives:
· Testing is a process of executing a program with the intent of finding an error
· A good test has a high probability of finding an as yet undiscovered error.
· A successful test is one that uncovers an as yet undiscovered error.
5.2 Design of test cases &scenario
The objective is to design tests that systematically uncover different classes of errors
and do so with a minimum amount of time and effort. Testing cannot show the
absence of defects, it can only show that software defects are present.
5.2.1 Integration Testing
Modules integrated by moving down the program design hierarchy. Can use depth
first or breadth first top down integration verifies major control and decision points
early in design process. Top-level structure tested most. Depth first implementation
allows a complete function to be implemented, tested and demonstrated and does
depth first implementation of critical functions early. Top down integration forced (to
some extent) by some development tools in programs with graphical user interfaces.
Chapter 5 Testing and Validation
31
Begin construction and testing with atomic modules (lowest level modules).Bottom
up integration testing as its name implies begins construction and testing with atomic
modules. Because modules are integrated from the bottom up, processing required for
modules subordinate to a given level is always available and the need for stubs is
eliminated.
5.2.2 Validation Testing
Validation testing is aims to demonstrate that the software functions in a manner that
can be reasonably expected by the customer. This tests conformance the software to
the Software Requirements Specification.
5.2.2.1 Validation Test Criteria
A set of black box test is to demonstrate conformance with requirements. To check
that all functional requirements satisfied, all performance requirements achieved,
documentation is correct and ' human-engineered', and other requirements are met
e.g. Compatibility,
error recovery and
Maintainability.
When validation tests fail it may be too late to correct the error prior to scheduled
delivery. Need to negotiate a method of resolving deficiencies with the customer.
5.2.2.2 Configuration Review
An audit to ensure that all elements of the software configuration are properly
developed catalogued and has all the necessary detail to support maintenance.
5.2.3 Alpha and Beta Testing
Alpha testing
Its a acceptance testing conducted by the developed environment.
Beta Testing
Its a acceptance testing conducted by the multiple customers in the customer
environment.
5.2.4 System Testing
Software is only one component of a system. Software will be incorporated with other
system components and system integration and validation test performance.
31
Begin construction and testing with atomic modules (lowest level modules).Bottom
up integration testing as its name implies begins construction and testing with atomic
modules. Because modules are integrated from the bottom up, processing required for
modules subordinate to a given level is always available and the need for stubs is
eliminated.
5.2.2 Validation Testing
Validation testing is aims to demonstrate that the software functions in a manner that
can be reasonably expected by the customer. This tests conformance the software to
the Software Requirements Specification.
5.2.2.1 Validation Test Criteria
A set of black box test is to demonstrate conformance with requirements. To check
that all functional requirements satisfied, all performance requirements achieved,
documentation is correct and ' human-engineered', and other requirements are met
e.g. Compatibility,
error recovery and
Maintainability.
When validation tests fail it may be too late to correct the error prior to scheduled
delivery. Need to negotiate a method of resolving deficiencies with the customer.
5.2.2.2 Configuration Review
An audit to ensure that all elements of the software configuration are properly
developed catalogued and has all the necessary detail to support maintenance.
5.2.3 Alpha and Beta Testing
Alpha testing
Its a acceptance testing conducted by the developed environment.
Beta Testing
Its a acceptance testing conducted by the multiple customers in the customer
environment.
5.2.4 System Testing
Software is only one component of a system. Software will be incorporated with other
system components and system integration and validation test performance.
Chapter 5 Testing and Validation
32
5.3 Generation of test cases
S.no
Submitte
d by
Description
Detected
stage
Assigne
d to
Type of
defect
Impact Priority Injected
Agcetion
taken
1
Rajesh
Sahu
Login to
sytem with
wrong
password
Unit
testing Rajesh
Logical
Error Medium Medium Coding Fixed
2
Vikram
Singh
Slathia
When select
randomized
question
from the
database
there a
chance of
Unit
testing Rajesh
Logical
Error Medium Medium Coding Fixed
3
Rajesh
Sahu
Contents of
forms are
not static
Unit
testingVikram
Logical
Error Medium Medium Coding Fixed
4
Rajesh
Sahu
Result
Calculation
Unit
testing Rajesh
Logical
Error Medium Medium Coding Fixed
5 Vikram
Question
fetching
Unit
testingRajesh
Logical
Error Medium Medium Coding Fixed
5.4 Validation
Validation aims to demonstrate that the software functions in a manner that can be
reasonably expected by the user. An experiment has done for checking the
consistency for the user requirements regarding the username and password which
should be validated through the server and the username and password should be
matched. (showed 4.2 chapter 4)
5.5 Conclusion
In this way we also completed the testing phase of the project and ensured that the
system is ready to go live. Thus we developed a system that provides a paperless
examination.
32
5.3 Generation of test cases
S.no
Submitte
d by
Description
Detected
stage
Assigne
d to
Type of
defect
Impact Priority Injected
Agcetion
taken
1
Rajesh
Sahu
Login to
sytem with
wrong
password
Unit
testing Rajesh
Logical
Error Medium Medium Coding Fixed
2
Vikram
Singh
Slathia
When select
randomized
question
from the
database
there a
chance of
Unit
testing Rajesh
Logical
Error Medium Medium Coding Fixed
3
Rajesh
Sahu
Contents of
forms are
not static
Unit
testingVikram
Logical
Error Medium Medium Coding Fixed
4
Rajesh
Sahu
Result
Calculation
Unit
testing Rajesh
Logical
Error Medium Medium Coding Fixed
5 Vikram
Question
fetching
Unit
testingRajesh
Logical
Error Medium Medium Coding Fixed
5.4 Validation
Validation aims to demonstrate that the software functions in a manner that can be
reasonably expected by the user. An experiment has done for checking the
consistency for the user requirements regarding the username and password which
should be validated through the server and the username and password should be
matched. (showed 4.2 chapter 4)
5.5 Conclusion
In this way we also completed the testing phase of the project and ensured that the
system is ready to go live. Thus we developed a system that provides a paperless
examination.
33
Chapter 6
Conclusion and Future work
6.1 Conclusion
Online Examination System (OLES) is a web application. The key concept is to
minimize the amount of paper and convert all forms of documentation to digital form.
It can observe that the information required can be obtained with ease and
accuracy in the computerized system. The user with minimum knowledge about
computer can be able operate the system easily. The system also produces brief result
required by the management.
6.2 Future work
Developments in software technology are continuing dynamically. This has forced
developers to look for new approaches to design and development. In order to face
this situation, the modules in a package should be upgraded any time. The modules in
this package can be subjected to further enhancements. Such as
· Developed discussion forums.
· Implementation on clouds server.
· Multimedia feature supports.
· Integrate learning material.
Chapter 6
Conclusion and Future work
6.1 Conclusion
Online Examination System (OLES) is a web application. The key concept is to
minimize the amount of paper and convert all forms of documentation to digital form.
It can observe that the information required can be obtained with ease and
accuracy in the computerized system. The user with minimum knowledge about
computer can be able operate the system easily. The system also produces brief result
required by the management.
6.2 Future work
Developments in software technology are continuing dynamically. This has forced
developers to look for new approaches to design and development. In order to face
this situation, the modules in a package should be upgraded any time. The modules in
this package can be subjected to further enhancements. Such as
· Developed discussion forums.
· Implementation on clouds server.
· Multimedia feature supports.
· Integrate learning material.
34
Chapter 7
References
7.1 Books
· Introducing Microsoft .NET, 3rd Edition By David S. Platt - Microsoft Press,
2003
· Database Programming With Visual Basic .Net and Ado.Net: Tips, Tutorials
and code By F. Scott Barker - Sams
7.2 Website
· My SQl
o
https://dev.mysql.com/tech-resources/articles/dotnet/
o https://www.geeksengine.com/article/mysql-odbc.html
· .Net
o http://msdn.microsoft.com/en-us/library/gg145045.aspx
· Online Examination Sites
o http://www.indiabix.com/
o http://www.tcyonline.com/india/home
7.3 Videos
o http://www.youtube.com/watch?v=CWRwVcZOURw
o
7.4 Projects
· Online Examination system of NIIT
· Online examination system AIEEE
Chapter 7
References
7.1 Books
· Introducing Microsoft .NET, 3rd Edition By David S. Platt - Microsoft Press,
2003
· Database Programming With Visual Basic .Net and Ado.Net: Tips, Tutorials
and code By F. Scott Barker - Sams
7.2 Website
· My SQl
o
https://dev.mysql.com/tech-resources/articles/dotnet/
o https://www.geeksengine.com/article/mysql-odbc.html
· .Net
o http://msdn.microsoft.com/en-us/library/gg145045.aspx
· Online Examination Sites
o http://www.indiabix.com/
o http://www.tcyonline.com/india/home
7.3 Videos
o http://www.youtube.com/watch?v=CWRwVcZOURw
o
7.4 Projects
· Online Examination system of NIIT
· Online examination system AIEEE
Categories
GeneralDownload
Download Slideshow Get the original presentation fileQuick Actions
Statistics
- Views 60,960
- Slides 41
- Favorites 53
- Age 4645 days
Related Slideshows
22
Pray For The Peace Of Jerusalem and You Will Prosper
RodolfoMoralesMarcuc
30 views
26
Don_t_Waste_Your_Life_God.....powerpoint
chalobrido8
32 views
31
VILLASUR_FACTORS_TO_CONSIDER_IN_PLATING_SALAD_10-13.pdf
JaiJai148317
30 views
14
Fertility awareness methods for women in the society
Isaiah47
29 views
35
Chapter 5 Arithmetic Functions Computer Organisation and Architecture
RitikSharma297999
26 views
5
syakira bhasa inggris (1) (1).pptx.......
ourcommunity56
28 views