final docu online exam

8/8/2019 Final Docu Online Exam

1/44

1 INRODUCTION

1.1. The Organization Profile

N Solutions is an emerging provider of IT development solutions, servicing

customers nationwide.

The ability of N Solutions is to anticipate future technological requirements and

capabilities is vital to the success of their business and that of their clients. The objective

of N Solutions is to work, communicate and support customers as the pace of change

accelerates and demands grow.

N Solutions business lines include:

Tailor-made software solutions development

Outsourcing software development

Business solutions deployment and integration

IT Consulting

IT Infrastructure building / maintenance and related services including technical

support to both customers and IT companies.

N Solutions software development services cover the complete project life cycle,

from requirement assessment and task definition, to solution development, to

implementation and integration, followed by support and maintenance. The ability to

integrate software with existing systems by expanding information systems infrastructure

is an important advantage of N Solutions as a turn-key solution provider.

N Solutions expertise covers the following areas:

Enterprise Application Integration Data Warehousing and Decision Support

Electronic Document Management

Information Security

Internet/Intranet and e-Commerce solutions

1


2/44

1.2. PROJECT OVERVIEW

There are two modules in the project

The Admin module deals with adding new questions, setting the exam paper and online

reports of student performance.

The Exam module and deals with student examination. A student will be listed with his

exam paper after authorization and every time the questions will be randomly generated

from the database. At the end of the exam, the score is evaluated and stored to the

database. The candidate can attempt again in case he has failed.

ADMIN MODULE

User / Password Management

In this module, the new student sign ups are be monitored and the password

changing options are provided. New admin users can also be added to the database.

Question Bank Editor

In this module, the questions and the four options as answers with the specific

images if applicable will be entered by the admin user to the database. The questions can

later be modified or deleted. Each question will come under a subject. New subjects can

be added to the subject master.

Exam Pattern Customization

In this module, the exam pattern can be set by the admin users as to long term

exam, short term exam, internal exam, final exam, no of questions, total marks, subjects

2


3/44

and so on. The student will be able to write the exams only on the specified dates and on

the specified patterns.

Exam Evaluation

In this module, the answers entered by the students will be processed and the final

score is evaluated.

Student Performance Evaluation

The student examination details entered in the database like total no of questions,

no of questions attended, no of correct answers, no of incorrect answers, no of unattended

answers, final score and result etc. will be displayed.

Grade/Rank Generation

Here the students mark statements will be processed to arrive at the final ranked

statements with the performance summaries.

EXAM MODULE

New Student Signup / Login

New students will be required to sign up and provide their details. They can

change their passwords also.

Instructions and Question Pattern Selection

The instructions for exam will be displayed here. The question patterns applicable

to the student will be displayed here. The student can select the pattern and view the

scheme of marking and other details.

3


4/44

Exam Question Paper Generation

When the user opts to start the exam, a set of questions as per the pattern will be

randomly generated from the database and displayed to the student. The examination will

be timed and the exam will end at the end of the specified duration.

Performance Record

A student after logging in can view his own performance details about the exam.

The examination details like total no of questions, no of questions attended, no of correct

answers, no of incorrect answers, no of unattended answers, final score and result etc.

will be displayed for the student. He can view his rank and result.

4


5/44

2 SYSTEM ANALYSIS

2.1 Study on Existing System

The existing system is fully based on manual system. Though it is programmed in such a

way to give good performance, it is proposed to go for computerized one which is

explained in this project.

Demerits Of Existing System

Retrieving of information is time consuming.

Considerable manpower is wasted.

Data stored is insecure

2.2 Study on Proposed System

The proposed project is to develop an automated system for handling all the activities

involved in conducting an exam and evaluating it. The various processes involved are for

the administrator to enter the details of the test like the subjects, questions and answers

for the subjects and also authorized users of the software. The candidate after being

properly authorized has to attend the test and has to complete it in the specified time

duration. After the completion the marks are to be calculated for the candidate.

5


6/44

2.3 System Specification

2.3.1 Hardware Specification

Processor : Pentium III

Speed : 433 MHZ

Ram : 128MB

Hard Disk : 20 GB

Operating System : Windows 2000

Disk Drives : 1.44 Floppy Disk Drive, 40 x Compact Disk

Monitor : 14 Color Monitor

2.3.2 Software Specification

Front-End : Microsoft ASP dot net

Back-End : Microsoft Access

Operating System : Windows 2000/ XP

Web Server : Internet IIS Server

6


7/44

3 DESIGN AND DEVELOPMENT PROCESS

3.1 Fundamental Design Concepts

Although the degree of interest in each concept has varied over the years, each has stood

the test of time. Each provides the software designer with a foundation from which more

sophisticated design methods can be applied. Fundamental design concepts provide the

necessary framework for getting it right.

3.2 Design Notations

Sets of fundamental design concepts are evolved over the past three decades.

Although the degree of interest in each concept has varied over the years, each has stood

the test of time. Each provides the software designer with a foundation from which more

sophisticated design methods can be applied. Design is defining a model of the new

system and continues by converting this model to a new system. The method is used to

convert the model of the proposed system into computer specification. Data models are

converted to a database and processes to user procedures and computer programs. Design

proposes the new system that meets these requirements. The detailed design starts with

three activities, database design, user design and program design. Database design uses

conceptual data model. In the proposed system the need for database design is mandatory

as all the information is maintained in a properties file. The details of server configuration

are fetched from a properties file.

3.2.1 Data Flow Diagram

The data flow diagram (DFD) is one of the most important tools used by system analysts.

Data flow diagrams are made up of a number symbols, which represent system

components. Most data flow modeling methods use four kinds of symbols. These

symbols are used to represent four kinds of system components such as Processes, data

stores, data flows and external entities.

Circles in DFD represent processes. Data Flow is represented by a thin line in the

DFD and each data store has a unique name and rectangle represents external entities.

7


8/44

Unlike detailed flow chart, Data Flow Diagrams do not supply detailed description of the

modules but graphically describes a systems data and how the data interact with the

system.

An arrow identifies the data flow in motion. It is a pipeline through whichinformation is flown like the rectangle in the flowchart. A circle stands for process that

converts data into information. An open-ended box represents a data store, data at rest or

a temporary repository of data. A square defines a source or destination of system data.

3.2.2 ER Diagram

The entity relationship diagram is based on a perception of real world that

consists of a collection of basic objects, called entities and of relationship among the

objects. Entities are described in a database by a set of attributes. The set of all entities

of the same type, and the set of all relationships of the same type, are termed as an entity

set, and relationship set respectively. The overall logical structure of a database can be

expressed graphically by an entity relationship diagram, which is built up using the

notations.

3.3 Design Process

Design begins when management approves the feasibility study produced during

detailed analysis and authorizes the necessary funds and personnel to continue. It

concludes when management approves the design and authorizes development of the

actual system. Design of the input and the output are the important features of design

specification.

3.3.1 Database Design

Database Design is a crucial factor in the performance of a system, both in terms

of system timings and in the case with which the system can be maintained or modified.

To permit simple retrieval of data in response to query and response requests.

To simplify the maintenance of data through updates, insertions and deletions.

To reduce the need to restructure or reorganize data when new application

requirements arise.

8


9/44

A collection of data designed to be used by different people is called a database. It

is collection interrelated data stored together with controlled redundancy to serve one or

more applications in an optional fashion.

The data is stored in such a fashion that it is independent of the programs of people

using the data. A common and controlled approach is used in adding new data and

modifying and retrieving existing data with in the database.

The Following are tables used in Database design:

Login table

User table

User Exams

All Exams

Qbank

3.3.2 Input Design

The input design is the link that ties the information system into the world of its

users. It is a process of converting user-originated inputs to a computer-based format.

Input data are collected and organized into a group of similar data. Once identified,

processing.

The goal of designing input data is to make entry easy, logical and free form

errors. In input data design, we design source document that capture the data and then

select the media used to enter them into the computer. The input forms are developed in a

user-friendly way so that a layman also can easily understand everything. Menus are

provided to users and different icons are designed so the proposed system design looks

decorative. Input design is the part of the overall system design.

Source documents initiate a processing cycle as soon as they are entered into the

system through the keyboard. A source should be logical and easy to understand.

Objectives of Input Design:

1 To achieve the highest possible level of accuracy.

2 To ensure that the input is acceptable and understood by the user.

9


10/44

3.3.3 Output Design

Output forms are also designed in a specific manner as per the user requirement.

Results are formatted to enhance clarity. Depending on the user the system would

generate appropriate output. The output forms are designed in such a way that the entire

user required data is presented.

While designing an output, the system analyst must accomplish the following.

Determine what information to present

Decide whether to display, print or speak information and select the output

medium.

Arrange the presentation of information in an acceptable form.

Decide how to distribute the output to intended users.

3.4 Development Approach

The ultimate aim of the proposed system is to provide service to the customers.

They need to get trained to use the newly proposed system. Hence developing a system

without the users feedback will lead to discard of the system. So Rapid Application

model was used to develop the system.

A rough interface of the system is given to the users for their feedback and

suggestions. Then the modifications are done. But as the system evolved and after a

series of interactions and demonstrations, the user felt comfortable with the newly

developed system.

The system went through the following stages:

The software request is evaluated

Product requirements are collected

Design specification for the prototype is prepared

Prototype software is developed, tested and refined

Prototype is given to the user, who tested the system any gave suggestions

for further refinement

10


11/44

The process during the development of the software using the RAD model is

11

Requirement

Gathering

Abbreviated

Representation

Prototype

Generation

Testing andRefinement

Online Exam

EvaluationSystem


12/44

4. TESTING AND IMPLEMENTATION

4.1 System Testing

Testing is a process used to help identify the correctness, completeness and

quality of developed computer software. There are many approaches to software testing,

but effective testing of complex products is essentially a process of investigation, not

merely a matter of creating and following rote procedure. One definition of testing is "the

process of questioning a product in order to evaluate it", where the "questions" are things

the tester tries to do with the product, and the product answers with its behavior in

reaction to the probing of the tester.

The quality of theapplication can and normally does vary widely from system to

system but some of the common quality attributes include reliability, stability, portability,

maintainability and usability.

Testing objectives include

1. Testing is a process of executing a program with the intent of finding an error.

2. A goodtest case is one that has a high probability of finding an as yet undiscovered

error.

3. A successful test is one that uncovers an as yet undiscovered error.

Testing should systematically uncover different classes of errors in a minimum

amount of time and with a minimum amount of effort. A secondary benefit of testing is

that it demonstrates that the software appears to be working as stated in the

specifications. The data collected through testing can also provide an indication of the

software's reliability and quality. But, testing cannot show the absence of defect -- it can

only show that software defects are present.

12
http://www.onestoptesting.com/Introduction/http://www.onestoptesting.com/Introduction/http://www.onestoptesting.com/Introduction/http://www.onestoptesting.com/Introduction/http://www.onestoptesting.com/Introduction/http://www.onestoptesting.com/Introduction/http://www.onestoptesting.com/Introduction/http://www.onestoptesting.com/Introduction/http://www.onestoptesting.com/Introduction/http://www.onestoptesting.com/Introduction/http://www.onestoptesting.com/Introduction/


13/44

4.1.1 Software Testing Strategies

Black box testing

Black box testing attempts to derive sets of inputs that will fully exercise all the

functional requirements of a system. It is not an alternative to white box testing. This type

of testing attempts to find errors in the following categories:

1. incorrect or missing functions,

2. interface errors,

3. errors in data structures or external database access,

4. performance errors, and

5. Initialization and termination errors.

White box testing

This testing is based on knowledge of the internal logic of an applications code.

Also known as Glass box Testing. Internal software and code working should be known

for this type of testing. Tests are based on coverage of code statements, branches, paths,

conditions. White box testing is a test case design method that uses the control structure

of the procedural design to derive test cases. Test cases can be derived that

Guarantee that all independent paths within a module have been exercised at least

once.

Exercise all logical decisions on their true and false sides.

Execute all loops at their boundaries and within their operational bounds.

Exercise internal data structures to ensure their validity.

13
http://www.onestoptesting.com/types/Whitebox.asphttp://www.onestoptesting.com/types/Whitebox.asphttp://www.onestoptesting.com/types/Whitebox.asphttp://www.onestoptesting.com/types/Whitebox.asp


14/44

Static Testing

The Verification activities fall into the category of Static Testing. During static

testing, you have a checklist to check whether the work you are doing is going as per the

set standards of the organization. These standards can be for Coding, Integrating and

Deployment.

Dynamic Testing

Dynamic Testing involves working with the software, giving input values and

checkingif the output is as expected. These are the Validation activities. Unit Tests,

Integration Tests, SystemTests and Acceptance Tests are few of the Dynamic Testing

methodologies.

Unit Testing

Unit testing is concerned with the testing of a small module. Using the detailed

design description as a guide, important control paths are tested to uncover the errors

within the boundary of the module. The module interface is tested to ensure that the

information flows in and out of the program unit under test. The local data structure is

ensured that the variables are handling valid information. All independent paths are

exercised to ensure that all statements in the module are executed at least once. The

modules of Online Service Relationship Management System are unit tested for all the

above-mentioned strategies. Number of input/output operations, database exceptions and

expressions are also tested in each and every module.

Integration Testing

Integration testing is proceeded with bottom up approach. In bottom up integration

testing, an individual module is first tested from a test harness. Once a set of individual

module has been tested, they are then combined into a collection of modules, known as

builds, which are then tested by a second harness. This process can combine until the

build consists of the entire application. The main objective of the integration testing is to

take the unit tested modules and to build a program structure that has been dictated by

14
http://www.onestoptesting.com/types/dynamic.asphttp://www.onestoptesting.com/types/dynamic.asphttp://www.onestoptesting.com/types/dynamic.asphttp://www.onestoptesting.com/types/dynamic.asphttp://www.onestoptesting.com/types/dynamic.asphttp://www.onestoptesting.com/types/dynamic.asphttp://www.onestoptesting.com/types/dynamic.asphttp://www.onestoptesting.com/types/dynamic.asp


15/44

design. Once all modules are unit tested they are put together for integration testing. This

test is a must and is an important part of the testing process. All the unit-tested modules

are combined and integrated. This type of testing is a must because the information can

be lost across an interface. One module can have an inadvertent, adverse effect on the

other sub functions may not produce desired results when integrated.

Alpha and Beta Testing

This is where the software is released to the actual end users. An initial release,

the alpha release, might be mad to selected users who would be expected to report bugs

and other detailed observations back to the production team. Once when the application

has passed through the alpha phase, beta release possibly incorporating changes

necessitated by the alpha phase can be made to a larger more representative set users

before the final release is made to all users.

Validation Testing

This testing runs the system in a live environment using real data. During this

validation, we are testing a number of items.

Systems Performance

Peak workload-processing Performance

Human engineering tests

Methods and Procedures test

Backup and Recovery testing

15


16/44

System Testing

Regression testing

Specific test, with which this version of the software is tested with the automated

test harness, is used in previous versions to ensure that the required features of the

previous are still working in the new versions.

Recovery testing

Where the software is deliberately interrupted in the number of ways, for example

taking its hard disk offline or even turning the computer off, to ensure that the appropriate

techniques for restoring any lost data will function.

Security testing

Here unauthorized attempts to operate the software or its parts are attempted. It

might also include attempts to obtain access the data, or harm the software installation or

even the system software. As with all type of security it is recognized that someone

sufficiently determined would lead to obtain unauthorized access and the best that can be

achieved is to make this process as difficult as possible.

Stress testing

Where abnormal demands are made upon the software by increasing the rate at

which it is asked to accept data, or the rate at which it is asked to produce information.

More complex tests may attempt to create very large data sets or cause the software to

make excessive demands on the operating system.

Acceptance testing

Acceptance testing involves planning and executing of functional tests,

performance tests and stress tests in order to demonstrate that the implemented system

satisfies its requirements. Functional test causes involve excising the code with nominal

input values for which expected results are known. The proposed system is developed in

the above manner that satisfies the user needs, confirms to its requirement and design

16


17/44

specification and exhibits absence of errors. This ensures that all requirement

documentation has been produced, is in the correct format and is of acceptable quality.

Website Cookie Testing

Cookie is small information stored in text file on users hard drive by web server.

This information is later used by web browser to retrieve information from that machine.

Generally cookie contains personalized user data or information that is used to

communicate between different web pages.

Cookies are nothing but the users identity and used to track where the user

navigated throughout the web site pages. The communication between web browser and

web server is stateless.

Test cases:

1) As a Cookie privacy policy make sure from your design documents that no personal or

sensitive data is stored in the cookie.

2) If you have no option than saving sensitive data in cookie make sure data stored in

cookie is stored in encrypted format.

3) Make sure that there is no overuse of cookies on your site under test. Overuse of

cookies will annoy users if browser is prompting for cookies more often and this could

result in loss of site traffic and eventually loss of business.

4) Disable the cookies from your browser settings: If you are using cookies on your site,

your sites major functionality will not work by disabling the cookies. Then try to access

the web site under test. Navigate through the site. See if appropriate messages are

displayed to user like For smooth functioning of this site make sure that cookies are

enabled on your browser. There should not be any page crash due to disabling the

cookies

17


18/44

5) Accepts/Reject some cookies: The best way to check web site functionality is, not to

accept all cookies. If you are writing 10 cookies in your web application then randomly

accept some cookies say accept 5 and reject 5 cookies. For executing this test case you

can set browser options to prompt whenever cookie is being written to disk. On this

prompt window you can either accept or reject cookie. Try to access major functionality

of web site. See if pages are getting crashed or data is getting corrupted.

6) Delete cookie: Allow site to write the cookies and then close all browsers and

manually delete all cookies for web site under test. Access the web pages and check the

behavior of the pages.

7) Corrupt the cookies: Corrupting cookie is easy. You know where cookies are stored.

Manually edit the cookie in notepad and change the parameters to some vague values.

Like alter the cookie content, Name of the cookie or expiry date of the cookie and see the

site functionality. In some cases corrupted cookies allow to read the data inside it for any

other domain. This should not happen in case of your web site cookies.

8 ) Checking the deletion of cookies from your web application page: Some times cookie

written by domain say rediff.com may be deleted by same domain but by different page

under that domain. This is the general case if you are testing some action tracking webportal. Action tracking or purchase tracking pixel is placed on the action web page and

when any action or purchase occurs by user the cookie written on disk get deleted to

avoid multiple action logging from same cookie.

9) Cookie Testing on Multiple browsers: This is the important case to check if your web

application page is writing the cookies properly on different browsers as intended and site

works properly using these cookies. You can test your web application on Major used

browsers like Internet explorer (Various versions), Mozilla Firefox, Netscape, Opera etc.

10) If your web application is using cookies to maintain the logging state of any user then

log in to your web application using some username and password. In many cases you

can see the logged in user ID parameter directly in browser address bar.

18


19/44

4.2 System Implementation

Implementation is the stage of the project where the theoretical design is turned

into a working system. At this stage the main work load and the major impact on the

existing system shifts to the user department. If the implementation is not carefully

planned and controlled, it can cause chaos and confusion.

Implementation includes all those activities that take place to convert from the old

system to the new one. The new system may be totally new, replacing an existing manual

or automated system or it may be a major modification to an existing system. Proper

implementation is essential to provide a reliable system to meet the organization

requirements.

The process of putting the developed system in actual use is called system

implementation. The system can be implemented only after thorough testing is done and

it is found to be working according to the specifications. The system personnel check the

feasibility of the system. The most crucial stage is achieving a new successful system and

giving confidence on the new system for the user that it will work efficiently and

effectively. It involves careful planning, investigation of the current system and its

constraints on implementation. The system implementation has three main aspects. They

are education and training, system testing and changeover.

The implementation stage involves following tasks.

Careful planning

Investigation of system and constraints

Design of methods to achieve the changeover.

Training of the staff in the changeover phase

Evaluation of the changeover method

19


20/44

4.2.1 Implementation Procedures

Implementation of software refers to the final installation of the package in its real

environment, to the satisfaction of the intended users and the operation of the system. The

people are not sure that the software is meant to make their job easier. In the initial stage

they doubt about the software but we have to ensure that the resistance does not build up

as one has to make sure that.

The active user must be aware of the benefits of using the system

Their confidence in the software built up

Proper guidance is impaired to the user so that he is comfortable in using

the application

Before going ahead and viewing the system, the user must know that for viewing the

result, the server program should be running in the server. If the server object is not

running on the server, the actual processes will not take place.

4.2.2 User Training

To achieve the objectives and benefits expected from the proposed system it is

essential for the people who will be involved to be confident of their role in the new

system. As system becomes more complex, the need for education and training is moreand more important.

Education is complementary to training. It brings life to formal training by

explaining the background to the resources for them. Education involves creating the

right atmosphere and motivating user staff. Education information can make training

more interesting and more understandable.

Training on the Application Software

After providing the necessary basic training on the computer awareness, the users

will have to be trained on the new application software. This will give the underlying

philosophy of the use of the new system such as the screen flow, screen design, type of

help on the screen, type of errors while entering the data, the corresponding validation

check at each entry and the ways to correct the data entered. This training may be

different across different user groups and across different levels of hierarchy.

20


21/44

4.2.3 Operational Documentation

Once the implementation plan is decided, it is essential that the user of the system is

made familiar and comfortable with the environment. A documentation providing the

whole operations of the system is being developed. Useful tips and guidance is given

inside the application itself to the user. The system is developed user friendly so that the

user can work the system from the tips given in the application itself.

4.3 System Security

A computer-base system is a combination of many assets or resources designed to

perform some function or to provide some services. Each of these assets is threatened by

one or more of the following unacceptable events:

Interruption

Disclosure

Removal

Destruction

Security Issues

The term security can be divided into four related issues

Security

Integrity

Privacy

Confidentiality

Authentication

In the system brief log on procedure for the customer was provided in order to enter and

access the system. This process is done in order to identify the valid user.

These attributes are stored in a table that cannot be easily trapped by unauthorized

persons.

21


22/44

File protection

The various files and database tables are also highly secured in this system. The

necessity for securing the files and the table evolves because some persons who were not

given authorization for access may hacker files and corrupt the tables with wrong data

which will response tremendous hazards to the operations of the system. So in order to

avoid these things, the data encryption standards engine is attached to all files and

database tables associated with the system, which will facilitate encryption and

decryption of files. Backup of the system are also taken as a preventive measure.

4.4 System Maintenance

The maintenance phase of the software cycle is the time in which software

performs useful work. After a system is successfully implemented, it should be

maintained in a proper manner. System maintenance is an important aspect in the

software development life cycle. The need for system maintenance is to make adaptable

to the changes in the system environment. There may be social, technical and other

environmental changes, which affect a system which is being implemented. Software

product enhancements may involve providing new functional capabilities, improving user

displays and mode of interaction, upgrading the performance characteristics of the

system. So only thru proper system maintenance procedures, the system can be adapted

to cope up with these changes.

Software maintenance is of course, far more than finding mistakes. We may

define maintenance by describing four activities that are undertaken, after a product is

released for use.

Corrective Maintenance

The first maintenance activity occurs because it is unreasonable to assume that

software testing will uncover all latent errors in a large software system. During the use

of any large program, errors will occur and be reported to the developer. The process that

includes the diagnosis and correction of one or more errors is called Corrective

Maintenance.

22


23/44

Adaptive Maintenance

The second activity that contributes to a definition of maintenance occurs because

of the rapid change that is encountered in every aspect of computing. Therefore Adaptive

maintenance termed as an activity that modifies software to properly interfere with a

changing environment is both necessary and commonplace.

Perceptive Maintenance

The third activity that may be applied to a definition of maintenance occurs when

a software package is successful. As the software is used, recommendations for new

capabilities, modifications to existing functions, and general enhancement are received

from users. To satisfy requests in this category, Perceptive maintenance is performed.

This activity accounts for the majority of all efforts expended on software maintenance.

Preventive Maintenance

The fourth maintenance activity occurs when software is changed to improve

future maintainability or reliability, or to provide a better basis for future enhancements.

Often called preventive maintenance, this activity is characterized by reverse engineering

and re-engineering techniques.

23


24/44

5 SCOPES FOR FUTURE ENHANCEMENT

This project can be further enhanced by including options for uploading student

resume so that the mandatory information about student can be stored in database

and can be used for further reference.

The project is at the recruitment exam level and it can be enhanced upto board

entrance level by adding additional futures

The website developed for search engine can be made more attractive by using

Adobe, Flash and Maya (3Dmax).

24


25/44

CONCLUSION

The project titled Online Exam Evaluation has been successfully completed as

per the requirements. The project has been tested under various phases for its accuracy

with various testing strategies.

This project can also be implemented in various study centers, schools and

colleges. This project helps the management to take various decisions regarding the

maintenance of their concern. The project provides maximum flexibility to the user. The

entire system is menu associated and highly interaction. The system has been tested using

all possible test data that can work in any conditions. No programming skill is required

to handle the system. The system is flexible and can be updated when need arises.

This project will satisfy all the requirements of the organization and it is

implemented after carrying out various types of testing and was found to run efficiently.

25


26/44

BIBLIOGRAPHY

REFERANCE

Comdex .NET Programming Course Kit , Vikas Gupta & Kogent Solutions Inc,

Publisher: DreamTech Press , Edition: Aug 2007

ASP.NET Bible, Mridula parihar et al, WILEY-Dreamtech India Pvt. Ltd,

Edition :2003

ASP.NET : A Beginners Guide, Dave Mercer, TATA McGraw-Hill Publishing

Company Limited,Edition:2002

Software Engineering A practitioners approach , TATA McGraw-Hill

Publishing Company Limited, Fourth Edition:1997

System Analysis and Design, Ellis M. Awad, Galgotia Publication, Edition 1997

WEB SITES

www.asp.net/

msdn.microsoft.com/asp.net/

en.wikipedia.org/wiki/ASP.NET

www.w3schools.com/aspnet/default.asp

samples.gotdotnet.com/quickstart/aspplus

26


27/44

ANNEXURES

Table Design

1 ) Tablename : Login

Fieldname Datatype Description

AUid Text Userid

APassword Text Password

UUid Text UseridUPassword Text Password

2) Table name : exam_pattern

Primary key :Ecode


Ecode Text Examcode

Ename Text Examname

Tque Number Totalquestions

TPercent Number Total Percentage

Tmark Number Totalmark

3 ) Table name : Q-bank

Primary key :Q_id


Q_id Number Question_id

Question Text Question

SCode Number SubjectcodeOptA Text OptionA

OptB Text OptionB

OptC Text OptionC

Ans Text Answer

27


28/44

4 ) Table name : Student

Foregin key:Userid


Fname Text Firstname

Lname Text Lastname

Dob Date / time Date Of Birth

Gender Text Gender

Street Text Street

City Text City

State Text StateCountry Text Country

Pco Number PostalCode

Phno Number Phone Number

5) Table name : ExamResult

Primary key :Userid

Foregin key :Ecode

Fieldname Datatype Descriptionuser_id Text User_id

EName Text Exam Name

Tques Text Total questions

CorrectAns Number CorrectAnswer

WrongAns Number WrongAnswer

SPercentage Number ScorePercentage

Res Text Result

28


29/44

SYSTEM FLOW DIAGRAM

29

Admin

Questions Editing

Login

Performance Report

Instructions

Student

Exam Evaluation

SignUp

Attend Exam

Instructions, Customization

LogoutLogout


30/44

Data Flow Diagram for Overall System

30

Enter Questions &

Exam Patterns

Admin User ExamEvaluation

Student User

Retrieve Question

Paper

View Student

Performance


31/44

DATAFLOW DIAGRAM

AttendExam

Exam_pattern

31

User

ExamCustomization

LoginExam_pattern

EditQuestions

Q-Bank

Student

Reports

ResultQ-Bank


32/44

FORM DESIGN

32


33/44

33


34/44

34


35/44

35


36/44

36


37/44

37


38/44

38


39/44

39


40/44

40


41/44

REPORTS

41


42/44

42


43/44

43


44/44

final docu online exam

Documents