OnlineExamination Project Report

A PROJECT REPORT ON
"ONLINE EXAMINATION SYSTEM"

Submitted in partial fulfillment of the
requirements for the award of the degree of
“BACHELOR OF COMPUTER APPLICATIONS”
2018-2019
Submitted by
Reg. No:
Under the guidance of

Ms.
Department of Computer Applications
Carmel College, Bangalore
This is to certify that the project entitled “ONLINE
EXAMINATION SYSTEM” has been carried out by
Seeraj, Ramesh chopra of Class III B.C.A. Semester VI
for the year 2013-2014 Submitted in partial
fulfillment Of the requirements for the award of the
degree of “Bachelor of Computer Applications” of
Carmel College.
Valued at the End Semester Examination of M a r c h 2014
Examiners:
1.......................
2........................
Date:.................
………………
Project Guide
…………………………………. ………………….
Head of the Department Principal
DECLARATION
I hereby declare that this project report titled as “ONLINE EXAMINATION

SYSTEM” has been prepared by me and my friend during the year 2018-2019 under the
valuable guidance and supervision of Ms. Manasi, lecturer and project guide, Carmel
college, Modankap in partial fulfillment of the requirement for the award of Bachelor’s
degree in Computer Applications.
I also declare that this project is the result of our own efforts and has submitted to
any other university for the award of any degree.
Place: Bangalore
Date:
Ramesh
(123034)
ACKNOWLEDGEMENT
“The satisfaction and happiness that accompanies the successful completion of

my project would be incomplete without the mention of the people who are responsible for
the completion of the project. It is a privilege to express my gratitude and respect to all
those who inspired and helped me in the completion of this project”.
First and foremost I would like to thank our beloved Principal PROF. ABC for
his encouragement to carry out the project in our college.
I express our deep gratitude to Mr. jignesh, Ms. Ranesh, Ms. Mark, Ms. John,
lectures and project guiders for their valuable guidance and suggestions during the course
of my project.
Finally, I extend my thanks to parents and friends who were directly or indirectly
involved in the completion of this project.
Place: Bangalore
Date:
Ramesh
(123034)
ABSTRACT
This is a project on “Online Examination System”. This project has been made very
interactive keeping in mind its reusability and user friendliness.
The project has been developed using PHP as a front end and MYSQL SERVER as
back end. The user is provided with a database where the information is stored and can be
retrieved any time when required.
Security is maintained for the system, there is a User Name and Password for an authorized
person only that person can access the data in the system.
Contents
Chapter 1: Synopsis
1.1 Title of the Project........................................................................................................1
1.2 Members Name with Reg.No.......................................................................................1
1.3 External Guid Name.....................................................................................................1
1.4 Objectives of the Project..............................................................................................1
1.5 Problem Statement........................................................................................................1
1.6 Project Scope................................................................................................................2
1.7 Project Category...........................................................................................................2
1.8 Hardware and Software Requirements........................................................................2
1.8.1 Software Specifications......................................................................................2
1.8.2 Hardware Specifications....................................................................................2
1.9 Limitations..................................................................................................................3
1.10 Future Scope of the Project...................................................................................3
Chapter 2: System Requirement and Specifications

2.1 Introductions………………………………………………………………………….…4
2.1.1 Purpose..............................................................................................................4
2.1.2 Scope.................................................................................................................4
2.1.3 Definition, Acronyms, Abbreviations...............................................................4
2.1.4 References.........................................................................................................5
2.1.5 Overview...........................................................................................................5
2.2 Overall Descriptions……………………………………………………………….…....5
2.2.1 Product Perspective...........................................................................................5
2.2.2 Product Features...............................................................................................5
2.2.3 User classes and Characteristics.......................................................................6
2.2.4 General Constraints...........................................................................................6
2.2.5 Assumptions and Dependencies.......................................................................6
2.3 Specific Requirements…………………………………………………………………..7
2.3.1 External Interface Requirements.............................................................................7
2.3.1.1 User Interface..............................................................................................7
2.3.1.2 Hardware Interface......................................................................................7
2.3.1.3 Software Interface.......................................................................................7
2.3.1.4 Communication Interface............................................................................7
2.3.2 Functional Requirements........................................................................................8
2.3.2.1 Login Module..............................................................................................8
2.3.2.2 Accounts Module........................................................................................8
2.3.2.3 Examination Module...................................................................................8
2.3.2.4 Dashboard Module......................................................................................8
2.3.2.5 Question Bank Module...............................................................................8
2.3.2.6 Result Module.............................................................................................9
2.4 Other Non-functional Requirements……………………………………………………9
2.4.1 Performance Requirements.....................................................................................9
2.4.2 Safety Requirement.................................................................................................9
2.4.3 Any Other Requirements........................................................................................9
Chapter 3: System Design

3.1 Introduction…………………………………………………………………………... 10
3.1.1 System Analysis……………………………………………………………….. 10
3.1.2 System Design……………………………………………………………….....10
3.2 Program Description…………………………………………………………………..10
3.2.1 Context Flow Diagram.........................................................................................10
3.3 Data Flow Diagram……………………………………………………………...…....11

3.3.1 Notation in the DFD............................................................................................11
3.4 Description of Components……………………………………………………..…….17

Chapter 4: Database Design
4.1 Introduction……………………………………………………………………………19
4.1.1 Database……………………………………………………………..…….........19
4.1.2 Database Design……………………………………………………………...…19
4.2 Database Tables………………………………………………………………………..19
4.3 Entity Relationship Diagram…………………………………………………………..24
Chapter 5: Detailed Design
5.1 Introduction……………………………………………………………………….…...26
5.1.1 Applicable Document...........................................................................................26
5.1.2 Structure Software Package..................................................................................26
5.1.3 Modular Decomposition.......................................................................................26
5.2 Module Design………………………………………………………………………...27
5.2.1 Administrator, Examiner, Student Sign in
page....................................................27
5.2.2 Module Design of Component 2...........................................................................28
5.3 Component Description……………………………………………………………......30
5.3.1 Login Page............................................................................................................30
5.3.2 Student Page.........................................................................................................31
5.3.3 Write Exam...........................................................................................................31
5.3.4 Result Page............................................................................................................31
5.3.5 Administrator Page...............................................................................................32
5.3.2 Student Page.........................................................................................................32
5.3.6 Student Details......................................................................................................32
5.3.7 Examiner Details...................................................................................................32
5.3.8 Create Exam..........................................................................................................33
5.3.9 Print Result............................................................................................................33
Chapter 6: Coding
6.1 Introduction………………………………………………………………………........34
6.2 Coding Standards………………………………………………………………….......34
6.2.1 Code Review and Walkthroughs…………………………………………….....34
6.3 Codes…………………………………………………………………………………..35
Chapter 7: Testing
7.1 Introduction………………………………………………………………………...….40
7.2 Levels of Testing……………………………………………………………………....40
7.2.1 Unit
Testing...........................................................................................................40
7.2.2 Integration Testing................................................................................................40
7.2.3 System Testing......................................................................................................40
7.3 White Box Testing………………………………………………………….………….41
7.4 Black Box Testing………………………………………………………………..……41
7.5 Unit Test Cases…………………………………………………………………….......41
Chapter 8: Screen Shots
8.1 Screen Shots…………………………………………………………………………..51
Chapter 9: Conclusion
9.1 Conclusion………………………………………………………………….………….72
Chapter 10: Future Enhancement
10.1 Future Enhancement………………………………………………………………….73
Chapter 11: Bibliography
11.1 References……………………………………………………………………………74
11.2 Websites……………………………………………………………………………..74
SYNOPSIS
1. SYNOPSIS
1.1 Title of the Project
“Online Examination System”

1.2 Members Name with reg. no.
Seeraj : 34324
Mahesh : 234234
1.3External Guide Name
Rajesh
Lecturer
Carmel College Bangalore
1.4Introduction and Objectives

The purpose of this project is to develop Online Examination System. This is a web
based Online Examination System which will help in conducting the Online Examination.
The purpose of this Online Examination System project is to provide a web application
which will considerably reduce the time required to give the exam and know the results.
This project will provide an efficient platform both for the students and the teachers, by
enabling examinations to be taken online.
1.5 Problem Statement

Presently, if the teachers conduct any objective examination, they have to check the
answer sheets manually which is time consuming and the generation of results manually
might result in errors.
Online examination helps students of schools/ College/ Institutions is to offer a
quick and easy way to appear for the exam. It also provides the results immediately after
the exam. The students have to enter a valid user id and password to attend the exam. This
examination contains multiple choice questions and appropriate number of options. There
are no limitations on number of options and it can be randomized. This examination project
provides time limit to finish the exam. The user can see their results after completing the
exam.
1.6 Project Scope

 Online Examination system is designed for Educational Institutions (like
schools, colleges, universities, training Institutions).
 It can be used anywhere any time as it is a web based application.
 It reduces the time of taking examinations of the students manually.
 This system will provide better security and transparency in the examination.
 The system handles all the operations, and generates reports as soon as the test is
finish, that includes name, mark, time spent to solve the exam.
 Allows students to check correct answers after the examination.
 The type of questions is only multiple choice or true and false.
1.7 Project category

Web Application.
1.8 Hardware and Software requirements
1.8.1 Software Specifications

 XAMPP Software
 Server: Apache server
 Database: MySQL
 Adobe Dreamweaver CS 6.0
1.8.1 Hardware Requirements:
 Processor: Intel dual core or above
 Processor Speed:1.0GHZ or above
 RAM: 1 GB or above
 Hard Disk: 20 GB or above
 Operating system: Windows XP or above.
1.9 Limitations
 In the case of system failure/crash it is not possible to conduct online
examination.
 It is very difficult to answer the examination where there is slow internet
connection.
 Computer knowledge is must to answer online examination.
1.10 Future Scope of the Project

This project covers all functionalities related to Online Examination but some parts
of the project have remained uncompleted due to some reasons. One of the main future
enhancements of our system is to add a mail response from the administrator to the user,
so that the user can understand whether he/she is eligible for appearing the exam.
SOFTWARE
REQUIREMENT
AND
SPECIFICATIONS
2. SYSTEM REQUIREMENT AND SPECIFICATION
2.1 Introduction
SRS – is a complete description of the behaviour of a system to be developed. It
includes a set of use cases that describe all the interactions the users will have with the
software. It deals with the requirements of the proposed system. It describes what the
proposed System should do without describing how the System will do it. An SRS provides
a reference for the validation of the final product; the SRS helps the client to determine if
the System meets the requirements.
2.1.1 Purpose
The purpose of the system is to develop Online Examination system,
used to conduct examinations through network for Educational institutions.
The manual procedure used for conducting examination is time consuming
process and error prone due to human limitations. The System purpose is to
completely automate the old manual procedure of conducting examination
to Online Web Based Examination System.
2.1.2 Scope
 This web application is Useful for school, college and university
teachers and professor to conduct class test, internal objective type
examination.
 This process will help the examiner to conduct examination, checking
answers and preparing grade card.
 Online examinations can be conducted at any time and does not incur
higher cost as traditional exam scenario as there is no paper work
involved(eg: printing question papers, prepare paper admissions etc).
 It provides limited time to answer the questions and after the time expiry
the question answer will be disabled automatically and the result will be
sent to the students.
 It Allows students to check correct answers after their examination.
2.1.3 Definitions, Acronyms, Abbreviations

SRS - Software Requirements Specifications
DFD - Data Flow Diagram
E-R - Entity Relationship diagram
DBMS - Data Base Management System
2.1.4 References
 An Integrated Approach to Software Engineering, Third Edition,
by Pankaj Jalote.
 www.w3schools.com– PHP and MySQL tutorials.
 www.php.net– PHP Official site.
 www.mysql.com – MySQL Database official site.
2.1.5 Overview
Online Examination is a Multiple Choice Questions based examination
system that provides a user friendly environment for examiners to conduct
examination and Students to answer exam.
2.2 Overall Descriptions

This section of the SRS describes all general factors of the product and its
requirements.
2.2.1 Product Perspective

The Online Examination system is consisting of a web server with a
database facility. This server is configured with proper security measures.
Students can connect through the internet with a latest web browsers
(eg: Internet Explorer, Mozilla Firefox etc) to the server and take the exam.
Even Examiners can connect to the server through the internet or through the
intranet for setting up question papers and to do other related tasks. It’s a
powerful dynamic website executes on apache server and all the records
stores in MySQL Database.
2.2.2 Product Features

The product features will include the following areas:
 The application is capable enough to store all the records and also
perform some editing on them that is added.
 User Friendliness is provided in the application with various controls

provided by system Rich User Interface.
 The system handles all the operations, and generates reports as soon as
the test is finish; this includes name, mark, percentage, etc.
 The system will provide tool for creating, conducting and evaluating
examinations.
2.2.3 User Classes and Characteristics

There are 3 kinds of users in the proposed system.
 Student: The student will logon to the system and take his/her
examination. He can also check his previous examinations marks and
his/her details. The student will get result immediately after the
completion of the examination.
 Examiner: Examiners of each course will prepare questions and its
options and loaded into the software. Examiners will approve student
certificates generated by system.
 Administrator: The administrator is the main user of the system, and he
can control complete website.
2. 2.4 General Constraints

 The main constraint here would be the checking the genuineness of the
buyer, which is not always possible. There can be security risks
involved.
 The developed system should run under any platform (Unix, Linux,
Mac, Windows etc..) that contains a web browser which supports PHP,
JavaScript and AJAX.
 Internet connection is required and it should have a speed of 512KBPS
or higher.
2.2.5 Assumptions and Dependencies

 The login details of students provided manually.
 Administrator is created in the system already.
 Roles and tasks are predefined.
 The type of questions is only multiple choices.
2. 3 Specific Requirements
2.3.1 External Interface Requirements
2.3.1.1 User Interface
Each part of the user interface intends to be as user friendly as
possible. The fonts, form controls and buttons used will be intended to be
very fast and easy to load on web pages. The pages will be kept light in
space so that it won’t take a long time for the page to load. If any errors,
the error message will be displayed in message boxes.
2.3.1.2 Hardware Interface
Hardware requirements are:
 CPU : Pentium or Higher.
 Monitor: Any monitor which is capable of displaying the signals
sent by the computer.
 Keyboard: A standard QWERTY keyboard for data entering.
 Mouse: Any standard mouse.
 Printer: Any printer it could be Laser printer, Inkjet Printer or even
a Dot- matrix printer will work fine for the software.
 Operating system: UNIX, Linux, Mac, Windows etc...
2.3.1.3 Software Interface

Software Requirements are:
 Development tool : Adobe Dreamweaver CS6 .0
 Software : XAMPP 1.8.2
 HTTP Web Server : Apache server
 Front End: PHP (Hypertext pre-processor)
 Data Base : MySQL Server.
2.3.1.4Communication Interface
 Web Browsers:Google chrome,Internet Explorer (7, 8), Mozilla
Firefox, Opera, etc.
 LAN Connection
2.3.1 Functional Requirements

2. 3.2.1 Login Module
In this module user can login to the website by entering login ID and
password. After Login the system links to Profile page.
2.3.2.2 Accounts Module

The module maintains the details for each student as well as provides
a facility for editing the student details and the students can change their
own passwords in this module if required.
2.3.2.3 Examination Module
In this module students can take the exam and submit the answers.
The system can automatically create exams by randomly choosing
questions from database. It provides limited time to answer the questions.
When the student starts the exam the timer will start automatically
and show the student how much time is left. After the exam this module
will be disabled automatically and Results can be viewed immediately
upon Submission.
2.3.2.4 Dashboard Module

Only Administrator and Examiner can access this module. here
administrator or examiner can view student details, Marks report,
examination report, etc. It has a facility to Add students details, view
Student List as well as Edit student details and Also administrator can
manage users details, course and subject details.
2.3.2.5 Question Bank Module

Questions bank will have a program to add, modify and delete
questions from subject. Here Examiner can upload questions and set
valuation schemes and test duration. The questions have different
attributes like subject, topic, marks, question text, options and the answer.
The question can be text or image.
2.3.2.6 Results Module

In this module students and examiners will get instant results.
Results can also be printed as soon as the test finishes.
2.4 Other non-functional Requirements

2.4.1 Performance Requirements
 Should be capable of giving access to concurrent users without degrading
the system performance and accept answers.
 Sessions of each candidate should be synchronized with server and
duration calculations should be done according to the server time.
2.4.2 Safety Requirements

 The system should be designed in as a secured system applying safety
measures.
 Special exception handling mechanism should be in place to avoid system
errors.
2.4.3 Any Other requirements

None
SYSTEM
DESIGN
3. SYSTEM DESIGN
3.1 Introduction
3.1.1 System Analysis
The system analysis approach emphasizes a closer look on all parts of the
system. The analyst must consider all the system elements, their input, output, control,
feedback and the environment when the system is being constructed.
3.1.2 System Design

The goal of system design phase is to produce a model or representation of the
system, which can be used to build the system. Here the emphasis is on translating the
requirements of the system into design specification.
3.2 Program Description

3.2.1 Context Flow Diagram
Context flow diagram is a top level data flow diagram. It only contains one
process node that generalises the function of the entire system in relationship to
external entities. In context diagram the entire system is treated as a single process and
all its inputs, outputs, sinks and sources are identified and shown.
course, subject,
registration,examination questions
Online
Students Examination Users
hall ticket, result System
result, report
certificate
Exam
3.3 Data Flow Diagram
A data flow diagram is a graphical representation of the flow of data through an
information system. A data flow diagram can also be used for the visualization of the data
processing. It is common practice for a designer to draw a context level DFD. It shows the
interaction between the system and the outside entities. This context level DFD, is then
exploded to show more detail of the system being modelled.

A DFD represents flow of data through a system. Data flow diagrams are commonly
used during problem analysis. It views a system as a function that performs the input into
the desired output. A DFD shows movement of data through the different transformations
or processes in the system.
Data Flow diagrams can be used to provide the end users with the physical idea of
where the data they input ultimately has an effect upon the structure of whole system from
order to dispatch to restock how any system is developed can be determined through data
flow diagram. The appropriate register saved in database and maintained by appropriate
authorities.
3.3.1 Notation in the DFD
Symbol Description
The circle or bubble represents a process. A

process is named and each process is represented
by a named circle.
The source or sink is represented as a rectangular

box. The source or sink is the net originator or the
consumer of the data that flows in the system.
The arrow represents the flow of data through the

system. The labeled arrows enter or leave the
bubbles.
The database is represented with the open box

symbol.
DFD Level-1
1.0
Login
name, password
2.0
questions
Upload Questions Questions
3.0 student detail

New Student Students
User
Registration
date time, student
datetime
4.0 Exam
Scheduling Exam
Record answer
5.0 Results
Attend Exam
answer
6.0
Calculate Results totalmarks Certificate
DFD Level-2 for Admin
course details
Admin
2.1 course name, description

Add New
Course
Course
subject
details
2.2
Adding
Examiner Subjects courseid,course
name
Subjects
subjectname,
passmarks
questions,option.
answer 2.3
Adding Question
and Answers
subjectcode,subjectname,
questions,option.
answer
2.4
Adding correct Questions
Answer
Result
DFD Level-2 for Admin
regno,name,password,coursename
Admin
invalid student 3.1

details
Get Student
Details
regno
3.2
Verify
login information Registration registration
details
Student Student
login credentials 3.3 regno,password

Login authenticate
authenticate id
3.4 contact details

Update
profile details
DFD Level-2 for Examiner
student details
Examiner
4.1 regno,name
Assigning Students
Students
4.2 subject code

Select Subject
Subject
subject code
schedules 4.3 studentid
Schedule Exam
regno,subjectcode,datetime
Exam
4.4
Student
Generate Hall ticket
DFD Level-2 for Student
DFD Level-2 for User
3.4 Description Of Components

 Login
This deals with giving privileges to the users to enter into the system. This
component includes:
 Inputs : Regno, Password, Course Name
 Output: If validation is correct it will be added to data base , or
respective message will be displayed .
 Upload Questions
Here examiner will add questions, options and Correct answer option to
the particular subjects.in order to upload questions Administrator has to add
course and Subjects .
 Inputs: course details, subject detail, question options, answer.
 Output: question adds to the database.
 New Student Registration

Here Administrator verifies the registration by getting the student details.
The system updates the profile details.
 Inputs: regno, name, password, course name.
 Output: updates the profile details.
 Scheduling Exam
Here administrator adds student details and it schedules Date and time for
examination. The system generate hall tickets for the students.
 Inputs: student details.
 Output: hall ticket will be generated.
 Attend Exam
Here Student can attend the Exam.
 Inputs: subject name.
 Output: after attending exam result will be displayed.
 Calculate Result
Here users evaluate the answers to provide certificates to the student.
 Inputs :
 Output: Student can collect the certificate.
DATABASE
DESIGN
4. DATABASE DESIGN
4.1 Introduction
4.1.1 Database
A Database is collection of related data, which can be of any size and
complexity. By using the concept of Database, we can easily store and retrieve the data.
The major purpose of a database is to provide the information, which utilizes it with the
information’s that the system needs according to its own requirements.
4.1.2 Database Design

Database design is done before building it to meet needs of end-users within a
given information-system that the database is intended to support. The database design
defines the needed data and data structures that such a database comprises. The database
is physically implemented using MySQL.
The database for Online Examination System is organized into 8 tables:
 Users
 Course
 Students
 Subjects
 Exam
 Questions
 Results
 Certificate
Each entity can be described as follows along with its attributes:

4.2 DATABASE TABLES
TABLE NAME: USERS
This table is used to store User details.
Column Type Size Constraint Description
Userid Int 10 Primary Key User ID
Coursed Int 11 Foreign Key Course ID
Name varchar 50 Not Null User Name

Designation varchar 25 Not Null User Designation
Usertype varchar 25 Not Null User Type
Username varchar 25 Not Null User Name
Password varchar 25 Not Null User Password
Createdat date Not Null User Creation Date
Lastlogin datetime Not Null User Last Login
Status varchar 25 Not Null User Status
TABLE NAME: COURSE
This table is used to store course details.
Coursed int 10 Primary Key Course ID
Coursename varchar 25 Not Null Course Name
Description Text Not Null Course Description
Status varchar 25 Not Null Course status
TABLE NAME: STUDENT
This table is used to store Student details.
Regno int 10 Primary Key Student Register number
Password varchar 25 Not Null Student Password
Coursed varchar 25 Foreign Key Student Course ID
Name varchar 50 Not Null Student Name
Dob date Not Null Student Date Of Birth
Address text Not Null Student Address
contactnumber varchar 20 Not Null Student Contact Number
Createdat date Not Null Student Creation Date
Lastlogin datetime Not Null Student Last Login
Status varchar 25 Not Null Student Status

TABLE NAME: SUBJECTS
This table is used to store subject details.
Subjectcode varchar 25 Primary Key Subject Code
Coursed Int 11 Foreign Key Course ID
Subjectname varchar 25 Not Null Subject Name
Rules Text Not Null Subject Description
Totalmarks float 10,2 Not Null Subject Total M arks
Passmarks float 10,2 Not Null Subject Pass Marks
Status varchar 25 Not Null Subject Status
TABLE NAME: EXAM
This table is used to store Exam details.
Examid int 10 Primary Key Exam ID
Regno int 10 Foreign Key Exam Register Number
Subjectcode varchar 25 Not Null Exam Subject Code
Datetime datetime Not Null Exam DateTime
Status varchar 10 Not Null Exam Status
TABLE NAME: QUESTIONS
This table is contains questions.
Queid Int 10 Primary Key Question ID
Subjectcode varchar 25 Foreign Key Subject Code
Question Text Not Null Question
Uploads Text Not Null Question Uploads

option1 Text Not Null Option1
Answer Int 5 Not Null Answer
Description Text Not Null Question description
Status varchar 25 Not Null Question Status
TABLE NAME: RESULTS
This table is used to store Result details.
Resulted int 10 Primary Key Result ID
Examid int 11 Foreign Key Result Exam ID
Queid int 11 Not Null Result Question ID
Answeredid varchar 25 Not Null Result Answered ID
TABLE NAME: CERTIFICATE
This table is used to store Certificate details.
Certificateid int 10 Primary Key Certificate ID
Examid int 11 Foreign Key Certificate Exam ID
Scoredmarks float 10,2 Not Null Certificate Scored Marks
Result varchar 25 Not Null Certificate Result
Date date Not Null Certificate Date
Status varchar 25 Not Null Certificate Status
TABLE RELATION
4.3 Entity-Relationship Diagram
An entity-relationship (ER) diagram is a specialized graphic that illustrates the
relationships between entities in a database. ER diagrams often use symbols to represent
three different types of information. Boxes are commonly used to represent entities.
Diamonds are normally used to represent relationships and ovals are used to represent
attributes.
Notation
Name Notation Description
Entity is represented by a box within the

ERD. Entities are abstract concepts, each
representing one or more instances of the
Entity concept in question. .Entities are
equivalent to database tables in a
relational database, with each row of the
table representing an instance of that
entity.
Relationships are represented by

Diamonds. A relationship is a named
Relationship collection or association between entities
or used to relate to two or more entities
with some common attributes or
meaningful interaction between the
objects.
Attributes are represented by Oval. An

attribute is a single data item related to a
Attributes database object. The database schema
associates one or more attributes with
each database entity.
Entity Relationship Diagram (E-R Diagram)

courseid courseid
coursename password name
dob
description regno
address
1 N
Course Belongs to Student
status
status contctno
1
1
N
Assignes
Has Attend
confirm
status password subjectcode courseid status examid
N N subjectname M
password
status
Users Subjects rules Exam regno

username
examduration datetime
totalmarks
subjectcode Generates
usertype userid
description passmarks 1
1
1
certificateid examid
name N
courseid Contains Calculates
status queid resultid

subjectcode From Certificates
M
description N
1 M
certificateid
answer scoredmarks
Questions questions Results status
queid
option4 uploads result
date
examid
option3 option1 answerid
option2
DETAILED
DESIGN
5. DETAILED DESIGN
5.1 Introduction
Detailed design is a second level of design process. During detailed design we

specify how the module in the system interacts with each other and internal logic of each of
modules specified during system design is decided, hence it is also called as logic design.
Detailed design essentially expands the system design and database design to
contain a more detailed description of the processing logic and data structures so that the
design is sufficiently complete for the coding.
5.1.1 Applicable Document

The detailed design refines the system document. Hence first applicable
document here is system design. Also we are referring the data structure. Hence
second applicable document is database design.
5.1.2 Structure of Software Package

The software package contains of following functional components:
 Functional component 1: Home page
 Functional component 2: Student page
 Functional component 3: Examiner page
 Functional component 4: Administrator page
 Functional component 5: Exam page
 Functional component 6: Logout
5.1.3 Modular Decomposition of component:
 Save:
This module is used to SAVE any particular record into our database.
 New:
This module is used to create NEW record into our database.
 Delete:
This module is used to DELETE particular record from database.
 Edit:
We can EDIT any selected record for our convenience.
 Clear:
This module is used to CLEAR the fields of any particular record.
 Update :
This module is used to make the changes and save the changes of
any particular into our database.
 Close:
Every form contains this module. This module is used to CLOSE
the any opened form in the screen.
 Print:
This module is used to PRINT the required details in a particular
format.
5.2 Module Design

5.2.1 Module Design of Component 1
Home Page
Home page is the first page of project. It is the starting page.From the home
page we can start the various roots (i.e. visit various pages) of the website or
project. Basically pages that we visit from Home Page are following
Administrator, Examiner, Student Sign in page
Here Student, Examiner, Administrator can enter into the account by

entering user name and password.
5.2.2Module Design of Component 2

Student Page:
 Student login.
 Student account
 Student profile
 Time table
 Hall ticket
 Student applied exam
 Student result
 Certificate
Student Page
Student Student Student Applied Student

Time Table Hall Ticket Certificate
Login Account Profile Exam Result
5.2.3 Module Design of Component 3
Examiner Page
 Assign subjects
 Add questions & answers (options)
 Rules and regulations

Examiner Page
Add Question &

Assign Subjects Rules & Regulation
Answer
5.2.4 Module design of Component 4
Administration Page
 Student registration
 Student exam fee & registration
 Issue hall ticket

Administrator Page
Student Generate
Issue Hall Tickets
Registration Certificates
5.3 Component Descriptions
5.3.1 Login Page
Purpose: This page provides link to login page & user. Examiner, Admin
can enter username and password.
Function: It check in database entered username is valid or not.
Subordinates:
 Administrator Login
 Examiner Login
 Student Login
Dependencies: None
5.3.2 Student Page:
Purpose: To attempt the exam.
Function: This page provides the facility for to read student details and
they can write the online exam. The result can be displayed.
Input: In this page they should select answer among multiple choices.
Subordinates:
 Write exam
 View Result
Output: The result can be displayed for submitted answer paper.
Dependencies: Login Page
5.3.3 Write Exam
Purpose: To write online exam.
Function: this page provide the facility for tick the answer for multiple choice
question.
Input: Select the answer
Subordinates: None
Output: This page displays the result for the answer paper.
Dependencies: Student Page.
5.3.4 Result Page
Purpose: To view result.
Function: Using this component the result can be displayed after submitting
the answer page. The result is set by the administrator department.
Subordinates: None
Dependencies: Student Page.
5.3.5 Administrator Page
Purpose: The administrator maintains the Examiner .
Function: The administrator adds students and students registered exam
details. These record stores in student, exam table.
Subordinates:
 Student Detail
 Examiner Detail
 Create Exam
 Print Result
Dependencies: Login Page
5.3.6 Student Detail:

Purpose: To enter the information of the student into the student registration
table which are in database.
Function: This page provides the facility for store the details of the student
and used to view the student details which we are entered in which they are
stored in the database.
Input: We should enter the details like user name, password etc.
Subordinates: None
Output: It displays the all details of the student registration table.
Dependencies: Administrator Page.
5.3.7 Examiner Details
Purpose: To make a preparation of the question paper pattern.
Function: This module provides the facility for enter the information into
the student details and administrator details table and creation of the
question paper and Evaluation of question paper.
Subordinates: None.
Output: It displays all Examiner details.
Dependencies: Examiner Page
. 5.3.8 Create Exam:
Purpose: To make creation of the question paper pattern to write online
exam.
Function: This page provides the facility for creation of question paper
that includes question with multiple choices the answer will also added
and it contain edit and delete question.
Input:We should enter the different question & multiple choices &
identify the correct answer.
Subordinates: None.
Output: The created question paper can displayed for write the exam.

5.3.9 Print Result
Purpose: To display the result.
Function: The page can be used to view the result after submitting the
answer paper.
Subordinates: None.

CODING
6. CODING
6.1 Introduction
All the software engineering steps have been discussed so far are directed to words
are final objective of translating the module into the software form that could be
understood by the computer. Coding is an important aspect in system development and
proper care has been taken to ensure that the application is efficient and suits the
requirement specified. Coding id viewed as natural consequences of design.
Development guidelines
The coding is done with following characteristics in mind. They are:
 Code efficiency
 Response time
 Maintainability
 Security
 Simple ease to understand code
 Ease of design code translation.
6.2. Coding Standards

The coding standards are necessary for a system because, people another than
programmers can easily understand the orderly convention of system. Standards facilitates
easy maintain of system as someone else other than developers, can later modify or
upgrade the system. The naming convention used here is similar to that window classes.
6.2.1 Code Review and Walkthroughs

Review is "A process or meeting during which artifacts of software
product are examined by project stockholders, user representatives, or other
interested parties for feedback or approval”. Software Review can be on Technical
specifications, designs, source code, user documentation, support and maintenance
documentation, test plans, test specifications, standards, and any other type of
specific to work product, it can be conducted at any stage of the software
development life cycle.
Purpose of conducting review is to minimize the defect ratio as early

as possible in Software Development life cycle. As a general principle, the earlier a
document is reviewed, the greater will be the impact of its defects on any
downstream activities and their work products. Magnitude cost of defect fixing
after the release of the product is around 60-100x. Review can be formal or
informal. Informal reviews are referred as walkthrough and formal as Inspection.
Walkthrough Process
Author describes the artifact to be reviewed to reviewers during the
meeting. Reviewers present comments, possible defects, and improvement
suggestions to the author. Recorder records all defect, suggestion during
walkthrough meeting. Based on reviewer comments, author performs any necessary
rework of the work product if required. Recorder prepares minutes of meeting and
sends the relevant stakeholders and leader is normally to monitor overall
walkthrough meeting activities as per the defined company process or
responsibilities for conducting the reviews, generally performs monitoring
activities, commitment against action items etc.
The Purpose of walkthrough is to
Find problems
Discuss alternative solutions
Focusing on demonstrating how work product meets all requirements.
IEEE 1028 recommends three specialist roles in a walkthrough leader.
6.3 CODES
dbconnection.php:
CODE FOR CONNECTION TO THE DATABASE
<?php
session_start();
$con=mysqli_connect("localhost","root","technology","onlineexamination");
//check connection
if(mysqli_connect_errno())
{
echo "Failed to connect to MySQL: " . mysqli_connect_error();
}
?>
index.php:
CODE FOR LOGIN
<?php
$dt = date("Y-m-d h:i:s");
if(isset($_POST[submitstudent]))
{
$sqlstudent ="SELECT * FROM students WHERE
regno='$_POST[studentusername]' AND password='$_POST[studentpassword]'";
$stquery = mysqli_query($con,$sqlstudent);
if(mysqli_num_rows($stquery) == 1)
{
$sqlupd = "UPDATE students SET lastlogin='$dt' WHERE
regno='$_POST[studentusername]'";
mysqli_query($con,$sqlupd);
$_SESSION[regno] = $_POST[studentusername];
header("Location: myaccount.php");
}
else
{
$errmsg1 = " Failed to login.";
}
}
if(isset($_POST[submitteacher]))
{
$sqlteacher ="SELECT * FROM users WHERE
username='$_POST[teacherusername]' AND password='$_POST[teacherpassword]' AND
usertype='Examiner'";
$tequery =mysqli_query($con,$sqlteacher);
if(mysqli_num_rows($tequery) == 1)
{
$rs = mysqli_fetch_array($tequery);
$sqlupd = "UPDATE users SET lastlogin='$dt' WHERE

regno='$rs[userid]'";
$errmsg2 = " Employee logged in

successfully..";
$_SESSION[examinerid] = $rs[userid];
$_SESSION[usertype] = $rs[usertype];
$_SESSION[courseid] = $rs[courseid];
header("Location: examinerpanel.php");
}
else
{
$errmsg2 = " Failed to
login..";
}
}
if(isset($_POST[submitadmin]))
{
$sqladmin ="SELECT * FROM users WHERE
username='$_POST[adminusername]' AND password='$_POST[adminpassword]' AND
usertype='Administrator'";
$adquery =mysqli_query($con,$sqladmin);
if(mysqli_num_rows($adquery) == 1)
{
$rs = mysqli_fetch_array($adquery);
$sqlupd = "UPDATE users SET lastlogin='$dt' WHERE

regno='$rs[userid]'";
$errmsg3 = " Administrator logged in

successfully..";
$_SESSION[userid] = $rs[userid];
$_SESSION[usertype] = $rs[usertype];
header("Location: dashboard.php");
}
else
{
$errmsg3 = " Failed to
login...";
}
}
?>
student.php
CODES FOR INSERTING RECORDS TO THE TABLE
$sql="INSERT INTO students (regno,password, name, dob, address, contactnumber,
createdat, courseid, status) VALUES ('$_POST[regno]', '$_POST[npassword]',
'$_POST[name]', '$_POST[dateofbirth]', '$_POST[address]', '$_POST[contactnumber]',
'$text', '$_POST[course]', '$_POST[status]')";
if(!mysqli_query($con,$sql))
{
die('Error: ' . mysqli_error($con));
}
else
{
$res = "One record is added";
$resi = 1;
}
}
}
}
Student.php:
CODES FOR UPDATING RECORDS TO THE TABLE
$sql="UPDATE students SET password='$_POST[npassword]', name='$_POST[name]',
dob='$_POST[dateofbirth]', address='$_POST[address]',
contactnumber='$_POST[contactnumber]', courseid='$_POST[course]',
status='$_POST[status]', createdat='$text' WHERE regno='$regno'";
if (!mysqli_query($con,$sql))
{
die('Error: ' . mysqli_error($con));
}
else
{
$res = "1 record updated";
$resi=1;
}
Student.php:
CODES FOR DELETING RECORDS TO THE TABLE
$sqldel ="DELETE FROM students where regno='$_GET[delid]'";
$seldelresult = mysqli_query($con,$sqldel);
if(mysqli_affected_rows($con) == 1)
{
$delresult = "Record deleted
successfully..";
TESTING
7. Testing
7.1 Introduction
Testing is the major quality control measure used during software development. It
is a basic function to detect errors in the software. During the requirement analysis and
design the output of the document that is usually textual and non-executable after the
coding phase the computer programs are available that can be executed for testing purpose.
This implies that testing not only has to uncover errors introduce during the previous phase.
The goal of testing is to uncover requirement, design, coding errors in the program.
Testing determines whether the system appears to be working according to the

specifications. It is the phase where we try to break the system and we test the system with
real case scenarios at a point.
7.2 Levels of Testing
7.2.1 Unit Testing
The unit testing of the source code has to be done for every individual unit of
module that was developing part of the system and some errors were found for
every turn and rectified. This form of testing was use to check for the behavior
signified the working of the system in different environment as an independent
functional unit.
7.2.2 Integration Testing
From the individual parts to the cohesion of each part to make the system as a
whole, there is need to test the working between the assembled modules of the
system. The modules are integrated to makeup the entire system. The testing
process is concerned with finding errors that result from unanticipated interaction
between the sub-system and system component. It is also concerned with validating
the system meets its functional and non-functional requirement.
7.2.3 System Testing

The requirement specification document that is the entire system is to be
tested to see whether it meets the requirement or not.
7.3 White Box Testing

White –box testing, sometimes called glass-box testing, is a test case design
philosophy that uses the control structure described as part of component-level design to
derive test cases. Using White box testing methods it can be ensured that:
 All independent paths within a module have been exercised at least once
 Exercise all logical decisions.
 Execute all loops at their boundaries and within their operational bounds.
 Exercise internal data structures to ensure their validity.
7.4 Black Box Testing

Black Box Testing is testing without knowledge of the internal workings of
the item being tested. For example, when black box testing is applied to software
engineering, the tester would only know the "legal" inputs and what the expected outputs
should be, but not how the program actually arrives at those outputs. It is because of this
that black box testing can be considered testing with respect to the specifications, no other
knowledge of the program is necessary.
7.5 Unit Test Cases

A test case has a component that describes an input, action or event and
an expected response, to determine if a feature of an application is working
correctly. The basic objective of writing test cases is to validate the testing
coverage of the application. Unit testing enables us to detect errors and correct it
without affecting any other modules.
Test Unit: Login Component.

Student
Serial No. Condition Expected Result Result
To be Tested
1. On the load of login form. No data should be PASS

supplied.
2. When the student does not Should display error PASS

enter any fields and clicks message “please enter
“login” register number and
password”

enter valid register number message “invalid register
and password. number and password”.

enter password. message “failed to login”.
5. When the user enters Should go to the home PASS
password and username and page.
clicks login.
Examiner
To be Tested

supplied.
2. When the examiner does not Should display error PASS

enter any fields and clicks message “failed to login”.
“login”.

enter user name. message “please enter the
user name”.

enter password. message “please enter valid
password”.
5. When the examiner enters Should go to the home PASS

password and username and page.
clicks login.
Administrator
To be Tested

supplied.
2. When the administrator does Should display error PASS

not enter any fields and message “failed to login”.
clicks “login”.

not enter user name. message “please enter the
user name”.

not enter password. message “please enter
valid password”.
5. When the administrator Should go to the home PASS

enters password and page.
username and clicks login.
Test Unit: Users

To be Tested
1 On the load of login form. No data should be PASS

supplied.
2 When admin does not Should display error PASS

enter any values and clicks message
‘submit’ “please enter the name”
3 When the admin does not Should display error PASS

select the course and message
clicks’submit’
“please select the course”

enter the designation and message
clicks’submit’ “please enter the
designation”

select the usertype and message
clicks’submit’
“please select user type”

enter the username and message
clicks’submit’
“please enter user name”

enter the password and message
clicks’submit’
“please enter password”

select the status and message
clicks’submit’ “please select status”
9 When the admin enter Should display error PASS

numbers instead of letters message “Enter only
in the field letters”
“ name ”
10 When the admin enters all Should display message PASS

the fields and clicks “one record is added ”
“Submit”
Test Unit: course
Serial Condition Expected Result Result

No. To be Tested
1 On the load of login form. No data should be supplied. PASS
2 When admin does not enter Should display error message PASS
any values and clicks ‘submit’ “please enter the course name”
3 When the admin does not Should display error message PASS
enter the description and
“please enter the description”
clicks’submit’
select the status and “please select status”
clicks’submit’
5 When the admin enter Should display error message PASS

numbers instead of letters in “Enter only letters”
the field
“ name ”
6 When the admin enters all the Should display message “one PASS
fields and clicks “Submit” record added ”
Test Unit: subject

No. To be Tested
any values and clicks ‘submit’ “please enter the subject name”
select the course and
“please select the course”
clicks’submit’
enter the rules and “please enter the rules”
clicks’submit’
enter the total marks and
“please enter total marks”
clicks’submit’
enter the passmarks and
“please enter passmarks”
clicks’submit’
clicks’submit’

the field
“ name ”
9 When admin enter letters Should display error message PASS

instead of numbers in the field
“marks” “Enter Only numbers”
fields and clicks “Submit” record is added ”
Test Unit : questions :

No. To be Tested
any values and clicks ‘submit’ “please enter the course”
enter the subject and clicks
“please enter the subject”.
’submit’
enter the question and clicks “please enter the question”
’submit’
enter option A and clicks
“please enter option A”
’submit’
enter option B and clicks
“please enter option B”
’submit’
enter option C and clicks
“please enter option C”
’submit’
enter option D and clicks
“please enter option D”
’submit’
enter the answer and clicks
“please enter answer”
’submit’
select the status and clicks “please select status”
’submit’

the field
“ name ”
fields and clicks “Submit” record is added ”
Test Unit: student

To be Tested
2 When admin does not enter Should display error PASS

any values and clicks message
‘submit’ “please enter the name”

enter the registration no and message
clicks’submit’
“please enter the registration
number”

enter the new password and message
clicks’submit’ “please enter the new
password”

enter the confirm password
and clicks’submit’ message
“please enter confirm

password”

enter the course and message “pleaseenter
clicks’submit’ course”

enter the date of birth and message
clicks’submit’
“please enter date of birth”

enter the address and message
clicks’submit’
“please enter address”

enter the contact number message
and clicks’submit’
“please enter contact
number”

select the status and message
clicks’submit’ “please select status”
11 When the admin enter Should display error PASS

numbers instead of letters message “Enter only letters”
in the field
“ name ”
12 When admin enter letters Should display error Pass

instead of numbers in the message “Enter Only
field “regno” numbers”
13 When the admin enters all Should display message PASS

the fields and clicks “one record is added ”
“Submit”
Test Unit: Exam
To be Tested
2 When admin does not Should display error message PASS

enter any values and clicks “please enter the register
‘submit’ number”
select the subjects and
“please select the subject”
clicks’submit’
select the date and “please select the date”
clicks’submit’
select the time and
“please select the time”
clicks’submit’
clicks’submit’

numbers instead of letters “Enter only letters”
in the field
“ name ”
9 When admin enter letters Should display error message PASS

instead of numbers in the “Enter Only numbers”
field “regno”
10 When the admin enters all Should display message “one PASS
the fields and clicks record is added ”
“Submit”
Test Unit : change password

To be Tested
1. On the load of login form. No data should be supplied. PASS
2. When the student does not Should display error message PASS
enter any fields and clicks “please enter the registration
“change password”. number”.

enter new password and message “please enter the
clicks “change password”. new password”.
4. When the student does not Should display error message PASS
enter confirm password “please enter confirm
and clicks “change password”.
password”..
5. When student enter letters Should display error message PASS

instead of numbers in the “Enter Only numbers”
field “regno”
6. When the student enters all Should display message PASS

the fields and clicks “password updated
“change password” successfully”
SCREEN
SHOTS
9. Screen Shots
Login Page for Administrator, Examiner and Student

This is a login page where the student, examiner and the admin can login by
entering a valid user name and password.
Administrator Page
This is the main page which displays when the admin login is successful. Here admin
can perform various operations
Examiner Page
This is the Examiner page which displays when the Examiner login is successful.
Here Examiner can perform various operations.
Student Account Page
This is the Student Account page which displays when the student login is successful.
Here Student can perform various operations.
Users
Here admin can add new user name and their information by clicking the “Submit” button,
the selected user will be added in the database.
Here admin does not enter any field and clicks “submit” it should display “please enter the
name”
Here admin enter numbers instead of letters in the field “name” and clicks “submit” it
should display “please enter valid character”
Here admin does not select course and clicks “submit” it should display “please
select the course”
Here admin does not enter designation and clicks “submit” it should display “please enter
designation”
Here admin does not select username and clicks “submit” it should display “please select
username”
Here admin does not enter user type and clicks “submit” it should display “please enter
user type”
Here admin does not enter password and clicks “submit” it should display “please enter
password”
Here admin does not enter confirm password and clicks “submit” it should display “please
enter confirm password”
When admin does not enter valid password and clicks “submit” it should display
“password and confirm password not matching”
In this page the Admin can add user by clicking the “submit” button. On clicking submit
button the user record will be added to the database.
In this page when admin can add all the fields of user and clicks “submit button” the record
will be added. And these fields will be stored in the table.
VIEW USERS
In this page admin can view the users.

Student
In this page the Admin can add student by clicking the “submit” button. On clicking submit
button the student record will be added to the database.
View Student
In this page admin can views the student details.

COURSE
In this form the Admin can add new course by clicking the “submit” button. On
clicking submit button the course record added to the database.
View Course
In this page admin can view the entire new course which stores in the database.
Subjects
In this page the Admin can add subjects by clicking the “submit” button. On clicking
submit button the subject’s record will be added to the database
View Subjects
In this page admin can view the subjects.

Hall Ticket
Exam
In this page the Examiner can add exam details by clicking the “submit” button. On
clicking submit button the exam record will be added to the database.
View Exam
In this page Examiner can views the Exam details.
Questions
In this page the examiner can add different questions by clicking the “submit”
button. On clicking submit button the questions record will be added to the database.
View Questions
In this page admin can views the questions, Options and correct answer.
Attend Exam
In this page student can attend the exam by clicking the “click here” option.
In this page student can answer the exam. after finishing exam as to click finish exam
button.
Examination Result
In this page after pressing the button the exam result will be displayed.
View Correct Answers

In this page student can view the correct answer after finishing exam.
Certificate
In this page the exam certificate will be generated it contains result of the student.
CONCLUSION
9. Conclusion
This Web Application provides facility to conduct online examination world

wide. 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, so no need to wait for the result.
It is automatically generated by the server.
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.
FUTURE
ENHANCEMENT
10. Future Enhancement
This project covers all functionalities related to Online Examination but some
parts of the project have remained uncompleted due to some reasons. One of the main
future enhancements of our system is to add a mail response from the administrator to the
user, so that the user can understand whether he/she is eligible for appearing the exam.
BIBLIOGRAPHY
11. Bibliography
References:
 “An Integrated Approach To The Software Engineering
By “Pankaj Jallote”.
 PHP and MySql web development (4th Edition)
By “Luke Welling and Laura Thomson”.
Web sites:
 www.w3schools.com
 www.php.net

OnlineExamination Project Report

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OnlineExamination Project Report

Uploaded by

Copyright:

Available Formats

A PROJECT REPORT ON

"ONLINE EXAMINATION SYSTEM"

Under the guidance of

I hereby declare that this project report titled as “ONLINE EXAMINATION

“The satisfaction and happiness that accompanies the successful completion of

Chapter 2: System Requirement and Specifications

Chapter 3: System Design

3.3 Data Flow Diagram……………………………………………………………...…....11

3.4 Description of Components……………………………………………………..…….17

1.1 Title of the Project

“Online Examination System”

1.4Introduction and Objectives

1.5 Problem Statement

1.6 Project Scope

1.7 Project category

1.8 Hardware and Software requirements

1.8.1 Software Specifications

1.10 Future Scope of the Project

2.1.3 Definitions, Acronyms, Abbreviations

2.2 Overall Descriptions

2.2.1 Product Perspective

2.2.2 Product Features

 User Friendliness is provided in the application with various controls

2.2.3 User Classes and Characteristics

2. 2.4 General Constraints

2.2.5 Assumptions and Dependencies

 Administrator is created in the system already.

 Roles and tasks are predefined.

 The type of questions is only multiple choices.

2.3.1.3 Software Interface

2.3.1 Functional Requirements

2.3.2.2 Accounts Module

2.3.2.4 Dashboard Module

2.3.2.5 Question Bank Module

2.3.2.6 Results Module

2.4 Other non-functional Requirements

2.4.2 Safety Requirements

2.4.3 Any Other requirements

3.1.2 System Design

3.2 Program Description

3.3 Data Flow Diagram

A data flow diagram is a graphical representation of the flow of data through an

exploded to show more detail of the system being modelled.

The circle or bubble represents a process. A

The source or sink is represented as a rectangular

The arrow represents the flow of data through the

The database is represented with the open box

3.0 student detail

2.1 course name, description

invalid student 3.1

login credentials 3.3 regno,password

3.4 contact details

4.2 subject code

3.4 Description Of Components

 New Student Registration

4.1.2 Database Design

Each entity can be described as follows along with its attributes:

TABLE NAME: USERS

This table is used to store User details.

Column Type Size Constraint Description

Userid Int 10 Primary Key User ID

Coursed Int 11 Foreign Key Course ID

Name varchar 50 Not Null User Name

Usertype varchar 25 Not Null User Type