PRESENTED BY: PRIYANKA SINGH (77) RADHIKA MANDIL (78) RAKSHA JADHAV (80) SHIVANGI JAIN (104)

PROJECT GUIDE : Mr.PRAVEEN YADAV SIR

27/2/2012

OIST

INTRODUCTION :
This Web Application provides facility to conduct intranet examination within organization. This System forms the lifeline of the Educational Institutes to the functioning of the Examination.

It saves time as it allows number of students to give the exam at a time and displays the results as the test gets over.
This will help to keep track of the student academics. Administrator has a privilege to create , modify and delete the test papers and its particular questions.

User can register , login and give the test with his specific id , and can see the results as well.

27/2/2012

OIST

STUDY OF CURRENT SYSTEM :

The Current system of examinations is highly complicated and expensive. Whenever exams are to be conducted there are various tasks that have to be done again and again Setting question paper Checking for errors Printing question papers Scheduling Exams Conducting Exams Checking Answer Papers Preparing Result Charts Solving Question Paper Automated Mark sheet Generation
27/2/2012 OIST 3

MOTIVATION :
Monthly and surprise(weekly )test helps in assessment of the students.
Exam scheduling takes lot of time which results in the proroguing of the exam. Manual evaluation of exam copies is quite hectic for faculty .

27/2/2012

OIST

EXISTING SYSTEM:

Taking surprise tests of students is also not feasible in the current system as planning for the exam and checking answer papers takes a lot of time and thus cannot be completed on schedule.
It also has no measures to prevent students from copying the answers rather than printing different sets of question papers which in turn can result expensive.

Report/Result generation takes too much time.

27/2/2012

OIST

Features of the New System :

The new system has been designed as per the user requirements so as to fulfill almost all of them Quick Scheduling Immediate Results and Solutions Easy to Store and Retrieve Information Cost Effective

27/2/2012

OIST

FEASIBILITY ANALYSIS :

To allow faculty to create questions ;questions can have multiple choices but have only one correct option. To allow faculty to create tests and answer key. To allow students to give their exams in an effective manner in less time and obtain their results instantly after finishing his exam. To allow automatic evaluation which can be recorded per test. The Intranet Examination System will include various subjects for conducting examinations. With the effective use, any Institute can apply the Intranet Examination System for conducting quick examinations and getting better results in less time. Cost benefit analysis: this project is cost effective as it saves a lot of time in conducting exams manually by using pen and papers, and saves time in evaluation of results.
OIST 7

27/2/2012

SCOPE OF PROJECT :
Scope of this project is very broad in terms of other manually taking exams few of them are:IES is designed for Educational Institutes like Schools, Colleges, and Private Institutes to conduct logic tests of their students on a regular basis. No restriction that examiner has to be present when the candidate takes the test. 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. The existing system is weak when it comes to surprise test organizations whereas this system can make it possible very easily.

27/2/2012

OIST

SOFTWARE ENGINEERING APPROACH:

27/2/2012

OIST

ADVANTAGES & DISADVANTAGES :

ADVANTAGES OF INCREMENTAL MODEL
It generates working software quickly and early during the software life cycle. Flexibility is more and less costly. Testing and debugging becomes easier during a smaller iteration. Risk can be managed more easily because they can be identified easily during iteration

Early increments can be implemented with fewer people.

DISADVANTAGES OF INCREMENTAL MODEL

Each phase of an iteration is rigid and do not overlap each other. Problems may arise pertaining to system architecture because not all requirements are gathered up front for the entire software life cycle.

27/2/2012

OIST

10

SYSTEM DESIGN:
USE CASE DIAGRAM:

27/2/2012

OIST

11

 ENTITY-RELATIONSHIP DIAGRAM:

27/2/2012

OIST

12

Conclusion :

Software development approach should be time bounded and systematic and the models adapted should be strictly followed to get the expected outcome i.e. the delivery of good software .

27/2/2012

OIST

13

REFERENCES:
SOFTWARE ENGINEERING BY PRESSMAN HODGE
www.w3schools.com www.roseindia.com www.wikipedia.com

27/2/2012

OIST

14