Press "Enter" to skip to content

Computer adaptive examination system

1. Introduction

Examination system today, is based on the generalized set of paper. Equitized question paper is formulated keeping in mind the different intellectual levels of students. Idea here, is to create a system that can challenge the high intellect of intelligent students by providing them with more intimidating question at the same time allowing the low intelligence examinee to answer questions according to his/her intellectual level. It is important to note that this system should be fair in terms of grading parameters. Question’s correctness score should be based on the level of challenge it can imply. Software should allow teachers to add different types of questions with the help of “easy to use interface”. This software will change the way of conducting examination.

Haven't found the right essay?
Get an expert to write you the one you need
GET YOUR PAPER NOW

1.1. Purpose

Traditional pen-paper examination system utilizes a great deal of papers which will never be used again as they are records. Storing such records also need a large storage facility. An online examination system overcomes many such problems. Traditional pen-paper examination works of a unified set of questions which proves to be less effective when it comes to two extremes of the intellect levels. Hence the requirement of an adaptive system is justified.

1.2. Intended audience and use

This application can be used by client’s who wants to conduct an evaluation test for all the applicants. This software will help the client in better screening of the applicants. The major demand for this application will be in educational sector. Target audience for this application will be students and teachers of all age. Hence the interface should be as simple as possible at both teacher’s and examinee’s end.

1.3. Definitions and Acronyms

CAOES – Computer based Adaptive Online Examination System.

Admin – Administration.

Exam – Examination/Evaluation process.

2. Overall Description

CAOES is a system based on three modules. Hypothetical names be admin-end, teachers-end and student/examinee-end.

Administration – end:

Only one administration account will be allocated per deployment/purchase/institution. Administration account will hold the access and decision-making responsibility. ID for teacher and student end can only be generated via administration account. If a new request (Sign Up) is issued for either student or teacher end, that account will not be accessible until administrator approves(authenticate) that request. The admin account should be able to generate 3 types of notification. 1) notification to teachers only, 2) notification to students only, 3) notification to both teachers and students. Whenever any teacher schedules an exam, that request should will go to admin account for the approval. Once the examination is approved, every student will get a notification saying that the exam has been scheduled. Admin account will have all the rights to database, i.e. Read, Write, Update, Delete. This end/ module will have a simple interface so that even a non-technical person can easily handle the module alone.

Other essay:   Auditorium automation system

Teachers – end:

This end/module will have multiple accounts. Each account will be verified/accepted by admin. A teacher account has the right to read and write the data i.e. read results of all the examinees for the evaluation conducted through that account. User is free to enter any type of question at any point of time. Before scheduling the exam, it is must that for the subject the exam is conducted, should have at least 10 to 12 times the questions (to the number of questions to be asked in the exam), in that subject’s question bank. After the exam deadline is processed the evaluation report for each examinee should be assessible by the exam creator as well as admin. Each account should get the notification for all the exams scheduled. Permission to schedule only one exam per day. Teacher-end’s account will have access to send the notification to students/examinees (if required). Account will have a personalized notes section – it will add/delete any kind of note (important info.) and will be limited to that account only.

Student/examinee – end:

Every user at this end will have the unique username and password. Password and some personal details can be modified later on by the user. Once the user gets the notification on the exam being created, he/she can apply for the exam that concerns them. Once registered user will receive an email acknowledging them about every useful data regarding that exam. On the day and time of exam, user will click on take exam and the user will be redirected to examination portal. On that portal user will conduct the exam. After completion of time the system will autosave the data and will evaluate the performance of the examinee. Results for the same will be provided at that very moment. The performance will be recorded and the examinee can view the outcome of the exam on his account.

2.1. User Needs

• Display/GUI should be simple in terms of its weight on the server.

• Application should be user friendly and can easily be understood by a new user.

• Loading new page should not take more than 5 seconds.

• During exam, backend calculation should not take more time. Next question should be displayed within 2 seconds after answering the current question.

• Teacher should be able to add a new question in the bank with the help of few clicks only.

Other essay:   Learning management system

2.2. Assumptions and Dependencies

• This system works on the assumption that each and every examinee’s initial intellect is 50%.

• Question bank should have at least 10 to 12 times the questions asked in exam.

3. System Features and Requirements

3.1. Functional requirements

• When ever a new request (of any kind) is generated, affected user (from any end) will be notified the acceptance of request via e-mail.

• Admin will have an eye on everything, Including tracking the students which are performing low and should be able to take required action on such matters.

• Application’s most of the calculation like keeping the track of clock and write the clock as data will be done on client’s end. i.e. on user’s browser. In addition, result calculation should also be calculated on user end. Server should perform minimal tasks but the most important ones.

• During exam, backend calculation should not take more time. Next question should be displayed within 2 seconds after answering the current question.

• Teacher should be able to add a new question in the bank with the help of few clicks only

3.2. Nonfunctional requirements

• Application will require constant calculation. Hardware of the server should be compatible to handle such processing quickly

• Application is expected to encounter heavy load of users at the same time. System should not crash in such conditions.

• Each question in the bank for each account needs to be encrypted by 128-bit encryption data for the security of that user’s data.

• Application should be independent of the platform. i.e. it should be able to work exactly the same way in mobile device’s browser and pc/laptop’s browser.

• Each user should be allocated the minimum of 5GB of free storage space. Scalability will be paid.

• Application should be tested for all the types to penetration attacks.

• Account will be secured by the means of 2 level security check.

• Each institution will have its own server under admin’s watch. All the servers and its data will be backed up on the central server to prevent the data loss in case any of the server fails.

3.3. Expected expenses for the project

• Project is expected to cost around 2 to 3 lakhs.

3.4. Basic flowchart expected

• The underlaying chart explains the minimum features and access each type of user will get.

• All the decision and request will go to admin for the approval.

• If admin decline any request, that request will be deleted forever. New request has to be developed to request again.

Other essay:   The changes in the planning system after 2010

4. Layout of the application

4.1. Student’s end

4.1.1. Dashboard will include all the notifications.

4.1.2. Dashboard will include score of all the exam with exam name and date.

4.1.3. Dashboard will show all the upcoming exams and a reminder of exam user has already registered to.

4.1.4. Register for exam will display detailed view of all the exams created and are not registered by that account holder.

4.1.5. User can register for any exam applicable, though Register for exam page.

4.1.6. Take exam page should redirect user to examination portal and bring him back to dashboard once exam is completed.

4.1.7. View result page will show detailed evaluation of the exams completed by that user.

4.1.8. Edit profile page will allow user to change certain fields as per his continence.

4.2. Teacher’s end

4.2.1. Dashboard will show details of all the subjects undertaken by that user.

4.2.2. Dashboard will display number of questions entered in each subject.

4.2.3. Schedule exam will allow user to create a new request for an exam, with detailed instruction regarding that exam.

4.2.4. Question bank page will display all the questions entered by the user in each subject.

4.2.5. Question bank page will allow user to add a new question in any of his subjects.

4.2.6. View exam performance page will allow user to see the result of all the examinees that appeared for the exam that user created.

4.2.7. Edit profile page will allow user to change certain fields as per his continence.

4.3. Admin’s end

4.3.1. Dashboard will show all the notification of any type of new request which is unattended.

4.3.2. Generate student id will allow user to create new id and password(temporary), for any new student end user.

4.3.3. Generate student id will allow user to create new id and password(temporary), for any new teacher end user.

4.3.4. Generate exam id will allow user to generate a unique exam id once the user approves that create exam request.

4.3.5. Generate subject id will allow user to generate a unique subject id once the user approves that create subject request.

4.3.6. User will have all the rights to view/update/delete the data related to any student end or teacher end user.

4.3.7. View result page will allow the user to view/ make changes in the result of any student end user.

4.3.8. Edit request page will help user to edit the unauthorized fields in student and teacher’s end.

Be First to Comment

Leave a Reply

Your email address will not be published.

0 Shares
Share via
Copy link

Spelling error report

The following text will be sent to our editors: