ONLINE QUIZ SYSTEM

SOFTWARE ENGINEERING LAB - INT 386

Submitted by
M.R.RAGASUDHA (9909008059) in partial fulfillment of BACHELOR DEGREE IN INFORMATION TECHNOLOGY

DEPARTMENT OF INFORMATION TECHNOLOGY KALASALINGAM UNIVERSITY (Kalasalingam Academy of Research and Education) KRISHNANKOIL 626 126

KALASALINGAM UNIVERSITY (Kalasalingam Academy of Research and Education) KRISHNANKOIL 626 126

BONAFIDE CERTIFICATE

Certified that this lab report ONLINE QUIZ SYSTEM is the bonafide work of M.R.RAGASUDHA(9909008059) who carried out the lab project under my supervision.

SIGNATURE

SIGNATURE

DR.V.VASUDEVAN Head Of The Department Information Technology Kalasalingam University, Anand Nagar, Krishnankoil-626190.

Ms.P.DEEPAVATHI Assistant Professor Information Technology Kalasalingam University, Anand Nagar, Krishnankoil-626190.

ACKNOWLEDGEMENT

I wish to express special thanks to Dr.S.Radhakrishnan, Vice Chancellor, Kalasalingam University, Krishnankoil, for providing nice environment for studies and research in campus and hostels. I would also like to thank Dr.V.Vasudhevan HOD, Department of Information Technology for giving inspiration and encouraging students to actively take part in all events and provide full freedom throughout the course in Kalasalingam University. I would also like to thank our assistant professor Ms.P.Deepavathi the staff in charge of Software Engineering Lab (INT-386) for being with us, helping us all through our way to complete our project successfully. I also express my gratitude to all Staff Members, Information Technology, Kalasalingam University for their constant help and encouragement which led to the accomplishment of this project.

ABSTRACT
Our project is on online Quiz System. The vital purpose of this project is to make the participant to take part actively in the on-line quiz, from their area itself. The existing system indicates that the participant want to come to the place, to take part, where the event is conducted and has to wait for the result till the event gets completed which wastes the participant time and also the coordinator time. The proposed system overcomes the wastage of time, and also increases the number of participants to take part in the quiz from their home site itself, which paves the participants to upgrade more knowledge from the current trends. The project is dynamic in nature. The system has been developed to satisfy the participant about his knowledge in all subjects. It reduces the job of calculating the mark manually. This system can be further developed to be useful to all sorts of quiz with slight modifications.

ACTION PLAN

S.NO 1 2 3

DATE 2.1.2012 9.1.2012 23.1.2012

WEEK 1 2 3

TASK PERFORMED TITLE SELECTION SCOPE,PROBLEM DEFINITION SOFTWARE REQUIREMENT ANALYSIS DESIGN-DESCRIBE THE MODULES OF PROJECT,IDENTIFY DELIVERABLE DATA MODELLING,SYSTEM ARCHITECTURE USE CASE,CLASS DIAGRAM SEQUENCE, COLLABORATION DIAGRAM STATE AND ACTIVITY DIAGRAM IMPLEMENTATION CODING IMPLEMENTATION CODING IMPLEMENTATION CODING TESTING-PREPARE TEST PLAN,COVERAGE ANALYSIS,DEVELOP TEST CASE HIERARCHY

MARK

SIGN

30.1.2012

13.2.2012

6 7

20.2.2012 27.2.2012

6 7

8 9 10 11 12

5.3.2012 12.3.2012 26.3.2012 2.4.2012 9.4.2012

8 9 10 11 12

TABLE OF CONTENTS CHAPTER

1 INTRODUCTION 1.1 Purpose 1.2 Scope 1.3 Definition, Acronyms, and Abbreviations 1.4 References 1.5 Technologies to be used 1.6 Overview 2 REQUIREMENT ANALYSIS 7 2.1 Software Requirement Hardware Requirement 2.2 2.3 2.4 2.5 Product Functions User Characteristics Identifying the Actors Identifying the Use Cases 7 8 8 9 9 5 5 5 5 6 6

PARTICULARS

PAGE NO

CHAPTER
3 DESIGN 3.1

PARTICULARS

PAGE NO

UML Diagram 3.1.1 Use case diagram 3.1.2 Class diagram 3.1.3 Sequence diagram 3.1.4 Collaboration diagram 3.1.5 3.1.6 3.1.7 Activity diagram State diagram ER diagram 10 11 12 13 14 15 16 17 21 27 54 58

3.2 4 5 6 7

Modules

FORM DESIGN IMPLEMENTATION TESTING CONCLUSION

CHAPTER-1
1.0 INTRODUCTION: SOFTWARE REQUIREMENT SPECIFICATION: 1.1 Purpose: The Quiz System is a Web application that provides facility to graduating/learning student. It provides a competitive platform, where a student not only judges their knowledge/skill but also they can improve their knowledge/skill at the same time. Quiz system can take test of a large collection of candidate at same time and display score card & solution online. 1.2 Scope: The main objective of this project is to conduct online test which will help them to become self paced learners and to make them aware of examination pattern of many competitive exams such as GATE, TOFEL, and various PSUs .Some of the aim of the project includes:1. Help students to go beyond their normal curriculum and learn about various aspects which are apart from academic education. other

2. To provide an examination system where, there is virtually no scope of errors and the results are much faster. And the system is more transparent. 3. To provide an environment where students not only can learn but also analyze their performance simultaneously. 4. To train the students to work within time limit with constraints . 1.3 Definitions, Acronyms, and Abbreviations: HTML (Hyper Text Markup Language): It is used to create static web pages. JSP (Java Server Pages): It is used to create dynamic web content.

1.4 References: IEEE STD 830-1998(Revision of IEEE Std 830-1993). IEEE STD 828-1998, IEEE Standard for Software Configuration Management Plans.
8

IEEE STD 610.12-1990, IEEE Standard Glossary of Software Engineering Terminology. IEEE STD 730-1998, IEEE Standard for Software Quality Assurance Plans.

R. Pressman 5E, reference book.

1.5 Technologies to be used: J2EE: (Server, JSP, JAXP, Java Beans) Application architecture. JAVA: Application architecture. Dreamweaver 8: 1.6 Overview: The SRS will include two sections, namely: Overall Description: This section will describe major components of the system, interconnections, and external interfaces. Specification Requirements: This section will describe the functions of actors, their roles in the system and the constraints faced by the system.

CHAPTER-2

2.0 REQUIREMENT ANALYSIS: 2.1 Hardware Requirements: MONITOR MEMORY PROCESSOR KEYBOARD 15 SVGA Colour Monitor 512 MB RAM and more Pentium-IV and more Standard keyboard FLOPPY DISK HARD DISK CD ROM MOUSE Standard 1.44 FDD 40 GB Standard 52x CD-ROM PS-2 WITH SCROLLING 101/102 keys or Microsoft natural

Software Requirements: OPERATING SYSTEM PROGRAMMING LANGUAGE WEB SERVER DATABASE GUI Windows 9x,Xp Html Apache tomcat MS Access Dreamweaver8.0

10

2.2 Product Functions: The product includes many functionalities of the organization. These

functionalities are: New student registration. Score evaluation. To conduct test. Security management.

2.3 User Characteristics:

Many users such as Administrator, Students, can use system. Only administrator of the system should be able to enter user or modify any kind of information in the system, but every user with a valid login ID and password should be able to view his details such as marks in previous tests, performance graph etc. Following table indicates all the user characteristics:

User Administrator

Access Privileges Add question. Modify database. Remove question.

Users

View score. Give test.

11

2.4 Identifying the Actors: Administrator. Course. Professor. Student.

2.5 Identifying the Use Cases: Maintain Student Information. Done Registration. View Report Card. Register Course. Select subjects to teach Check for validity. Submit grades.

12

CHAPTER-3
3.0Design:

3.1.1 Use Case Diagram:

13

3.1.2 Class Diagram:

14

3.1.3 Sequence Diagram:

15

3.1.4 Collaboration Diagram:

16

3.1.5 Activity Diagram:

17

3.1.6 State Diagram:

18

3.2 Modules: 1. 2. 3. 4. 5. conditions Login Select options to answer Display score card Winner list

Module 1: 1. Conditions: 1. The number of participants should be of 30. 2. The duration for quiz is 30 minutes so a timer has to kept which should show time duration. 3. The number of questions should be 40 chosen randomly from the database in 3 different areas namely i) Information Technology ii) logical reasoning and iii) General Knowledge. 4. The questions should be of objective type with multiple options. For each correct answer the participant will receive 1Point and wrong answer .25Point will be deducted for each wrong answer. 5. At the end of the quiz the user score will be displayed. 6. Once a Student answered for question he cant changes his answer later. Module 2: 2. Login: 2.1 Description The use case describes how a Participant logs into the Quiz System 2.2 Flow of Events 2.2.1 Basic Flow This use case starts when the Participant wishes to Login to the Quiz System 1. The System requests that the participant enter his/her name and password
19

2. The participant enters his/her name and password 3. The System validates the entered name and password and logs the participant into the System 2.2.2 Alternative Flows Invalid Name/Password If, in the Basic flow, the participant enters an invalid name and/or password, the system displays an error message. The participant chooses to either return to the beginning of the Basic flow or cancel the login, at which point the use case ends. 2.3 Special Requirements The Number of participants should be 30 2.4 Pre-Conditions None 2.5 Post-Conditions If the use case was successful, the participant is now logged into the system. If not, the system State is unchanged. 2.6 Extension Points None Module 3: 3. Select Options to Answer 3.1 Description This use case allows the Participant to select appropriate answer to the question. 3.2 Flow of Events
20

3.2.1 Basic flow This use case starts when the participant logs into the system. The Participant will be given a set of questions with answers in multiple options. The participant selects the answer from the set of options. Once the participant answered for a question next question will be displayed. 3.2.1 Alternate Flow Once the time slot allotted for the participant is over scorecard will be displayed. 3.3 Special Requirements None 3.4 Pre-Conditions The Participant must login into the System for answering the question 3.5 Post-Conditions If the use case was successful, the participant will be able to view the next question. 3.6 Extension Points None Module 4: 4. Display Score Card 4.1 Description The use case gives the scorecard along with No of Correct and wrong answers.

21

4.2 Flow of Events 4.2.1 Basic Flow Once the participant had completed answering to the questions within the stipulated time, he/she will be given a scorecard with final score. 4.2 Alternative Flow None 4.3 Special Requirements None 4.4 Pre-Conditions The participant should have completed the questions within stipulated time. 4.5 Post-Conditions If the use case was successful, the participants can logout from the system. 4.6 Extension Points None

Module 5: 5. Winner List 5.1 Description This use case gives winner list based on the scores obtained by the participant.

22

5.2 Flow of Events 5.2.1 Basic Flow This use case gives the coordinator the winner list based on the scored obtained. 5.2.2 Alternative Flow If the coordinator logged into the system even before the quiz was over he will empty List. 5.3 Special Requirements None 5.4 Pre-Conditions If all the participants had answered for the questions then the winner list has to be generated. 5.5 Post-Conditions None 5.6Extension Points None

23

CHAPTER-4
4.0 FORM DESIGN: APPLICATION FORM

24

LOGIN FORM

25

TOPICS

26

QUESTIONS

27

RESULT

28

THANK YOU :

29

CHAPTER-5
5.0 CODING:

FORM 1:
Private Sub cmdTchLog_Click() Set rs = con.Execute("select * from login where user='" + txtUsername.Text + "' and Pword='" + txtPassword.Text + "'") If (Not rs.EOF) Then MsgBox "Login Success" Form2.Show Unload Me End If End Sub Private Sub Form_Load() connectdb End Sub Private Sub frmLogin_DragDrop(Source As Control, X As Single, Y As Single) End Sub

FORM 2:
Dim Qcnt As Integer Dim mark As Integer Dim s As Integer Dim rslt As String
30

Dim sel As String Private Sub Command1_Click() If (Option1.Value = True) Then sel = Option1.Caption ElseIf (Option2.Value = True) Then sel = Option2.Caption ElseIf (Option3.Value = True) Then sel = Option3.Caption ElseIf (Option4.Value = True) Then sel = Option4.Caption End If If (ans = Selected) Then mark = mark + 1 End If MsgBox mark & "-" & ans & "-" & sel Qcnt = Qcnt + 1 If (Qcnt <= 10) Then Set rs = con.Execute("select * from Question where qn=" & Qcnt & "") If (Not rs.EOF) Then lblQno.Caption = Qcnt lblQst.Caption = rs(0) Option1.Caption = rs(1) Option2.Caption = rs(2) Option3.Caption = rs(3) Option4.Caption = rs(4)
31

ans = rs(5) End If Else MsgBox "Exam Completed" Command1.Enabled = False Command2.Enabled = True Option1.Enabled = False Option2.Enabled = False Option3.Enabled = False Option4.Enabled = False End If End Sub Private Sub Command2_Click() If (mark >= 5) Then rslt = "Passed" Else rslt = "Failed" End If Text1.Text = rslt End Sub Private Sub Form_Load() connectdb mark = 0 Qcnt = 1 Set rs = con.Execute("select * from Question where qn=" & Qcnt & "")
32

If (Not rs.EOF) Then lblQno.Caption = Qcnt lblQst.Caption = rs(0) Option1.Caption = rs(1) Option2.Caption = rs(2) Option3.Caption = rs(3) Option4.Caption = rs(4) ans = rs(5) End If rs.Close Command2.Enabled = False Text1.Enabled = False End Sub Private Sub Frame2_DragDrop(Source As Control, X As Single, Y As Single) End Sub

33

LOGIN:

34

QUESTION:

35

COMPLETION PART:

36

RESULT:

37

DATABASE:

38

CHAPTER-6 TESTING

6.0 TEST OBJECTIVE

Testing is the process of executing a program with the intend of finding error. A good test is one that has high probability of finding error. A successful test is one that uncovers an undiscovered error. If testing is done successful, it will uncover errors in the software. Testing demonstrates that software functions appear to be working according to the specification that behavioral and performance requirement appear to have been met. Data collected as testing is conducted to provide good indication of software reliability and some indication of software quality as a whole.

TEST PLAN
Before testing is to be done, test plan must be done in order to identify which testing method is to be implemented for the project. The test cases must be identified.

6.1 SOFTWARE TESTING:

Testing is the process of executing a program with the intend of finding errors

GUIDELINESS FOR SOFTWARE TESTING:

Determine when to stop testing

Assign the responsibility of testing program to tester. Avoid non-reproducible testing Write test cases for valid and invalid conditions Assign most creative programs to testing.

39

6.2 MAJOR GROUPINGS OF SOFTWARE TESTING:

The 2 major groupings of software testing are:

I.

BLACK BOX OR FUNCTIONAL TESTING:

This approach focuses on inputs, outputs and principle function of a software module.

II.

STRUCTURAL OR GLASS BOX TESTING:

This approach looks into the structure of the code for a software module.

6.3

TYPES OF TESTING:

6.3.1 FUNCTIONAL TESTING:

This includes any testing that verifies the functional requirements of an application or system.

UNIT TESTING:
Test particular functions or code modules. It is performed during the coding stage of the project.

SYSTEM TESTING:
It is based on overall requirement specification, covers all combined parts of the system.

INTEGRATION TESTING:
Various hardware and software elements are combined and tested.

USER ACCEPTANCE TESTING:

Test based on it meets all of the user requirements. This test validate the systems ability to produce outputs accept inputs and produce expected results.

END TO END TESTING:

Testing of a complete application environment in a situation that minimizes real world use.

40

REGRESSION TESTING:
Re-testing after fixes or modification of the software or its environment.

EXCEPTION TESTING:
Exercise the exception handling behavior of the application.

DESTRUCTIVE TESTING:
Exercise valid entries such as field lengths, boundaries , data ranges etc.,

6.3.2

NON-FUNCTIONAL TESTING:

This includes any testing that verifies the non-functional requirements of an application/system.

PERFORMANCE TESTING:
Verifies the changes introduced by the project to system.

LOAD TESTING:
Ensures the system functions properly and maximum loads dont compromise any elements.

STRESS TESTING:
It intends to find error due to extended usage of the application under test. When the application is subjected to maximum virtual user loads for extraordinary periods of time.

VOLUME TESTING:
Subjects the application under test to large amount of data . This can be used to predict future prediction loads.

LIMIT TESTING:
It is carried out for each of the documented application limits.

41

DISASTER AND RECOVERY TESTING:

It simulates problems in the production environment to test the alternative processing environment.

COMPATIBILITY TESTING:
The product should be compatible with the old data used by the users.

CONSISTENCY TESTING:
The data and results are verified to be consistent across the application.

RELIABILITY TESTING:
Testing for reliability requires periods of prolonged use at varying loading levels or constant values at peak levels.

USER INTERFACE TESTING:

Interfaces are evaluated for ease of understanding and use.

INSTALLATION TESTING:
Testing of full, partial or upgrade install/uninstall process.

42

CHAPTER-7 CONCLUSION
This system has been developed for user environment under GUI and is found working efficiently. The system accommodates the existing requirements. It overcomes the existing difficulties. It satisfies the user and has been designed efficiently with future adaptability.

43