Examination and Result Management System - TutorialsDuniya
Examination and Result Management System - TutorialsDuniya
COM
Management System
om
Software Engineering Project Report
.c
i ya
un
D
ls
Submitted By :
ia
Keshav Mahavidyalaya
University Of Delhi
Acknowledgement
Apart from the efforts of team, the success of any project depends largely on the
encouragement and guidelines of many others. We take this opportunity to express
om
our gratitude to the people who have been instrumental in the successful
completion of this project.
The completion of any inter-disciplinary project depends upon cooperation, co-
.c
ordination and combined efforts of several sources of knowledge.
ya
We are eternally grateful to our TutorialsDuniya.Com for his even willingness to
give us valuable advice and direction; under whom we executed this project. His
constant guidance and willingness to share his vast knowledge made us understand
i
un
this project and its manifestations in great depths and helped us to complete the
assigned tasks.
D
project better.
ia
Although there may be many who remain unacknowledged in this humble note of
gratitude, there are none who remain unappreciated.
t or
Tu
Certificate
2
om
TutorialsDuniya.Com.
This report has not been submitted to any other organization/institution for the
.c
award of any other degree/diploma.
i ya
un
D
ls
ia
t or
Tu
TutorialsDuniya.Com TutorialsDuniya.Com
TutorialsDuniya.Com
(Project Supervisor) (Principal) (H.O.D.)
Abstract
In today's tech era, IOT (Internet of things) has become much popular around the
world. Almost all the devices, which are known as smart device, can connect to
the internet and access data from any corner of the world. There was a time when
people used to waste their valuable times just to get a piece of information. Now
the technology is more advance then compare to any previous times. One of the
om
blessings of technology is web application. It allows users to interact with the
system from anywhere as long as they are connected to the internet.
.c
This report presents the work done on the project "Examination and Result
Management System" which is a web application. As we already discussed above
ya
that internet has made the user’s interaction through the system easier, so this web
application can connect to respective servers for accessing data which will surely
i
help students to get information about their syllabus, result and much more other
un
information . Moreover, in recent decays it has become much difficult to manage
all the student’s records in physical files. So, it is very much needed to build a
D
system which can store and display all these information in a database. In this
modern tech era we want a system that will enhance the portability, accessibility as
ls
well as user friendly. So here, we are going to implement a web system, which we
ia
already stated above, having all the features that will make it more user friendly
and accessible.
or
The aim of this project was to develop a System that would help an institution to
t
om
With the advent of computer technology and the internet , users prefer to conduct
their business electronically to their convenience; This paper focuses on the need
.c
and construction to provide same comfort and ease to the user.
i ya
un
D
ls
ia
t or
Tu
Table of Contents
om
1.1 Introduction
9
1.1.1 Problem Statement
.c
9
1.1.2 Process Model
ya
10
1.1.3 Purpose
10 i
un
1.1.4 Document Conventions
11
D
1.1.7 References
or
12
1.2 Overall Description
t
12
Tu
om
14
1.2.6 User Documentation
15
.c
1.2.7 Assumptions and Dependencies
15
ya
1.3 External Interface Requirements
15
1.3.1 User Interfaces i
un
16
1.3.2 Hardware Interfaces
16
D
17
1.3.4 Communication Interfaces
ia
17
1.4 System Features
or
17
1.5 Other Non-Functional Requirements
t
Tu
18
1.5.1 Performance Requirements
18
1.5.2 Safety Requirements
18
om
20
1.6.1 Level – 0
20
.c
1.6.2 Level – 1
21
ya
1.7. Data Dictionary
22
2. Estimation & Scheduling i
un
23
2.1 Size Estimation
23
D
26
2.3 Scheduling
ia
27
2.3.1 Gantt Chart
or
27
3.Architectural Design
t
28
Tu
4.Risk Analysis
29
4.1 RMMM
30
5.Implementation
35
5.1 HTML File
35
5.2 CSS File
om
36
5.3 PHP File
36
.c
5.4 Snapshots of module
38
ya
6.Testing
40
6.1 Black Box Testing i
un
40
6.1.1 Equivalence class testing
40
D
40
6.1.1.2 Output equivalence class
ia
40
6.2 White Box Testing
or
41
6.2.1 Basis path testing
t
41
Tu
om
44
7.2 Getting Started
44
.c
7.2.1 Quick Start
44
ya
7.2.2 System Requirements
45
7.3 Troubleshooting i
un
45
8. Conclusions
47
D
9. References
48
ls
ia
t or
Tu
10
Chapter - 1
om
1.1 Introduction
This document lays out a project plan for the development of “Examination and
.c
Result Management System”.
ya
The plan will include, but is not restricted to, a summary of the system
functionality, the scope of the project from the perspective of the “Examination
and Result Management System” team (me and my mentors), project risks and
i
un
how those risks will be mitigated, the process approach to develop the project, and
metrics and measurements that will be recorded throughout the project. This
document will cover each of the system’s intended features, as well as offer a
D
document will also cover hardware, software, and various other technical
dependencies.
ia
or
In our current examination conduction and result processing system, there is too
Tu
much manual and paperwork used for conduction of exam and computation of
result.
It becomes very difficult to manage record of all students manually which results
in heap of files.
11
Also, there is imbalance between the man power availability and magnitude of the
examination work which results in inaccuracy and delay in declaration of result.
Our software is designed to efficiently manage all the records of the students,
om
automatically calculate the percentage and grade point of the students.
With the use of our software, the span required for declaration of result and use of
man power will be reduced to a great extent.
.c
ya
1.1.2 Process Model
i
un
In our software, we are following prototyping Model (Evolutionary) as initially
the requirements are not clear.
D
The requirements are added in the prototype as and when they are understood.
ls
Software reviews are applied at various points during software engineering and
serve to uncover the errors and defects that can be removed.
ia
1.1.3 Purpose
or
The goal of this project is to provide a mobile application for all the students and
teachers and Institute’s administrators , to build an online system to manage all the
t
Tu
records related to examination and result of students and teachers to ease the
service of examination and result management.
12
This document features some terminologies which readers may be unfamiliar with
:
SRS : Software Requirement Specification
om
DESC : Description
.c
The intended audience is any person who wants to :
1.3.1. Check the examination and result details (both student and administrator
ya
mode).
1.3.2. Add/Delete details in examination and result. (only administrator mode).
i
un
1.1.6 Product Scope
D
helps students and teachers to find all the up-to-date information related to
examination and result.
ia
server-side application which will support and interact with client-side queries.
The server-side verifies logins as Student , Teacher or Administrator and manages
t
user information. The data will be held in an Access database on the server.
Tu
13
1.1.7 References
om
October 20, 1998.
[IEEE] The applicable IEEE standards are published in “IEEE Standards
Collection,” 2001 edition.
.c
2. The principle source of text book material is “Software Engineering A
ya
PRACTITIONER ’ S APPROACH” by Roger S. Pressman.
i
3. The principle source of text book material is “A Concise Introduction to
un
Software Engineering” by Pankaj Jalote.
D
14
The following list offers a brief outline and description of the main features and
functionalities of the Examination and Result Management System. The features
are split into two major categories: core features and additional features. Core
om
features are essential to the application’s operation, whereas additional features
simply add new functionalities.
.c
There are three types of users that interact with the system:-
ya
a) Students
b) Teachers
c) Administrator i
un
Each of these types of users has different use of the system so each of them has
their own requirements.
D
The students can only use the application to view their profile, result, datesheet,
syllabus and Admit Card. This means that the user is expected to be Internet
ls
literate. The user interface will be as intuitive as possible. Thus, technical expertise
and Android experience should not be an issue.
ia
or
The main component of the Examination and Result Management System is the
Tu
15
major concern. Beyond that, the application is a self-contained unit and will not
rely on any other Android-related software components.
om
The primary design constraint is the mobile platform. Since the application is
designated for mobile handsets, limited screen size and resolution will be a major
design consideration.
.c
Creating a user interface which is both effective and easily navigable will pose a
difficult challenge.
ya
Other constraints such as limited memory and processing power are also worth
considering. Examination and Result Management app is meant to be quick and
i
responsive, so each feature must be designed and implemented with efficiency in
un
mind.
D
component of the system which shall provide specific guidelines to a user for
using the product. To implement online user help, online user manual shall be
or
provided.
t
16
om
This section provides a detailed description of all inputs into and outputs from the
system. It also gives a description of the hardware, software and communication
.c
interfaces and provides basic prototypes of the user interface.
ya
The Port number used will be 80.
A first-time user of the mobile application should see the log-in page when he/she
ls
17
data between the local application and the main application server. Information
will be sent using TCP/IP and the HTTP protocol.
The Android platform provides abstractions for all network communication
interfaces and thus the hardware as well.
Since the application must run over the internet, all the hardware shall require to
om
connect internet will be hardware interface for the system. As for e.g.Wi-Fi,
mobile data.
The hardware connection to the database server is managed by the underlying
.c
operating system on the mobile phone.
ya
1.3.3 Software Interfaces
i
The communication between the database and the application consists of operation
un
concerning both reading and modifying the data.
The Examination and Result Management app is to be developed under the
D
Android operating systems using the Java JDK (Java Development Kit) and the
Android SDK (software development kit) tools.
ls
ia
The Examination and Result Management app shall use the HTTP protocol for
communication over the internet and for the intranet communication will be
t
The communication between the different parts of the system is important since
they depend on each other. However, in what way the communication is achieved
is not important for the system and is therefore handled by the underlying
operating systems for the mobile application.
18
om
examination and result , our application provides several features, such as :-
View result (All Users)
View Syllabus (All Users)
.c
View admit card (All Users)
View Datesheet (All Users)
ya
View his Profile (All Users)
Create/Update Result (Only Teacher and Admin)
i
un
Create/Update Syllabus (Only Admin)
Create/Update Datesheet (Only Admin)
Create/Update Admit Card (Only Admin)
D
Performance should not be an issue because all of our server queries involve small
t
pieces of data. Changing screens will require very little computation and thus will
Tu
occur very quickly. Server updates should only take a few seconds as long as the
phone can maintain a steady signal.
19
Examination and Result Management app will not affect data stored outside of its
servers nor will it affect any other applications installed on the user’s phone. It
cannot cause any damage to the phone or its internal components.
om
The user’s password should always be echoed with special characters representing
typed characters.
The system’s back-end servers shall only be accessible to authenticated
administrators.
.c
The system’s back-end databases shall be encrypted.
The graphical user interface (GUI) of Examination and Result Management app is
to be designed with usability as the first priority. The app will be presented and
or
organized in a manner that is both visually appealing and easy for the user to
navigate. To ensure reliability and correctness, there will be zero tolerance for
t
errors in the algorithm that computes result and percentage of the students.
Tu
20
om
USER
.c
ya
EXAMINATION AND
RESULT
COMPUTATION SYSTEM
i
un
D
ls
ia
PROFILE
t
Tu
21
om
LOGIN
.c
VIEW
DATESHEET CREATE
DATESHEET
VIEW USER
ya
ADMIT PROFILE
CARD
i
un
D
DATABASE
22
om
c. Create Syllabus = Subject + Course + Chapters
.c
e. Create Admit Card = Name + RollNo. + Sem + Subject + PaperCode + M.M.
i ya
un
D
ls
ia
t or
Tu
23
Chapter – 2
om
Function-oriented software metrics use a measure of the functionality
delivered by the application as a normalization value. Since
.c
‘functionality’ cannot be measured directly, it must be derived
ya
indirectly using other direct measures.
Function-oriented metrics were first proposed by Albrecht, who
i
suggested a measure called the function point. Function points are
un
derived using an empirical relationship based on countable (direct)
measures of software's information domain and assessments of
software complexity.
D
24
om
data that may be one part of a large database or a separate file) is
counted.
.c
Number of external interfaces. All machine readable interfaces (e.g., data
files on storage media) that are used to transmit information to another
ya
system are counted.
i
un
D
ls
ia
t or
Tu
25
om
External O/P 1 4 1
Logical Interface 1 2 1
External Interface 0 0 0
.c
External Enquiry 3 2 0
ya
UFP = ∑5 i =1 ∑3 i =j Cij * Wij
= 3*4 + 4*3 + 6*1 + 4*1 + 5*4 + 7*1 + 7*1 + 10*2 + 15*1 + 3*3 +
4*2
i
un
= 12 + 12 + 6 + 4 + 20 + 7 + 7 + 20 + 15 + 9 + 8
= 120
D
= 0.65 + 0.01 X 14 X 3
ia
= 1.07
or
FP = UFP * CAF
= 120 X 1.07
t
= 128.4
Tu
= 128 (approx)
26
om
These mathematical equations are based on historical data and use
project size in the form of KLOC.
The COCOMO model uses a multivariable size estimation model
.c
for effort estimation.
i ya
un
Object Point = ∑3 i =1 ∑3 i =j Cij * Wij
D
=
ls
SCREENS 1 3 2
or
REPORT 1 3 1
t
3GL 0 0 1
Tu
(1X1+3X2+2X3)+(1X2+3X5+1X8)+(1X10)
= 13+25+10
= 48
27
om
= 48/13
= 3.7
.c
NOP = New Object Point
ya
PROD = Productivity
We have assumed nominal developer experience
i
un
D
ls
ia
t or
Tu
28
2.3 Scheduling
om
Steps End Date
SRS - 20 February
.c
Cost & Size Estimation - 27 February
Design - 13 March
ya
Implementation - 20 March
Testing - 27 March
User manual i
- 3 April
un
Source code & Deployment - 10 April
D
ls
ia
t or
Tu
29
Chapter – 3
Architectural Diagram
om
Examination and Result
Management System
.c
ya
Student Admin
i
un
View Result View
D
Syllabus
Datesheet Card
Edit/Delete
or
Edit/Delete
Datesheet Admit Card
t
Tu
30
Chapter – 4
Risk Management
Risk always involves two characteristics:
om
a. Uncertainty - The risk may or may not happen. There are no 100% probable
risks.
b. Loss - If a risk becomes a reality, unwanted consequences or losses will
.c
occur.
ya
The goal of the risk mitigation, monitoring and management plan is to identify as
many potential risks as possible. The project will then be analysed to determine
any project-specific risks. i
un
When all risks have been identified, they will then be evaluated to determine
their probability of occurrence. Plans will then be made to avoid each risk,
D
The quicker the risks can be identified and avoided, the smaller the chances
t
Tu
Risk Table
31
om
End Users Resist Project Risk 20% 1
System
.c
Changes in Project Risk 20% 2
Requirements
Impact Values:
1 – Catastrophic i ya
un
2 – Critical
3 – Marginal
D
4 – Negligible
ls
Mitigation
or
The cost associated with a computer crash resulting in a loss of data is crucial. A
t
computer crash itself is not crucial, but rather the loss of data. A loss of data will
Tu
result in not being able to deliver the product to the customer. This will result in a
not receiving a letter of acceptance from the customer. Without the letter of
acceptance, the group will receive a failing grade for the course. As a result the
32
Monitoring
om
When working on the product or documentation, the staff member should always
be aware of the stability of the computing environment they’re working in. Any
.c
seriously.
ya
Management
i
un
The lack of a stable-computing environment is extremely hazardous to a software
unstable, the development team should cease work on that system until the
ls
environment is made stable again, or should move to a system that is stable and
ia
Mitigation
The cost associated with a late delivery is critical. A late delivery will result in a
late delivery of a letter of acceptance from the customer. Without the letter of
33
acceptance, the group will receive a failing grade for the course. Steps have been
taken to ensure a timely delivery by gauging the scope of project based on the
delivery deadline.
Monitoring
om
A schedule has been established to monitor project status. Falling behind schedule
would indicate a potential for late delivery. The schedule will be followed closely
.c
during all development stages.
ya
Management
i
Late delivery would be a catastrophic failure in the project development. If the
un
project cannot be delivered on time the development team will not pass the
course. If it becomes apparent that the project will not be completed on time, the
D
Mitigation
Tu
In order to prevent this from happening, the software will be developed with the
end user in mind. The user-interface will be designed in a way to make use of the
34
Monitoring
The software will be developed with the end user in mind. The development team
will ask the opinion of various outside sources throughout the development
om
opinion from others.
Management
.c
Should the program be resisted by the end user, the program will be thoroughly
ya
examined to find the reasons that this is so. Specifically the user interface will be
i
investigated and if necessary, revamped into a solution.
un
D
ls
ia
Mitigation
t
In order to prevent this from happening, meetings (formal and informal) will be
Tu
held with the customer on a routine business. This insures that the product we are
Monitoring
35
The meetings with the customer should ensure that the customer and our
organization understand each other and the requirements for the product.
Management
Should the development team come to the realization that their idea of the product
om
requirements differs from those of the customer, the customer should be
immediately notified and whatever steps necessary to rectify this problem should
.c
be taken. Preferably a meeting should be held between the development team and
ya
the customer to discuss at length this issue.
i
un
D
ls
ia
t or
Tu
36
Chapter – 5
Implementation
Implementing module for result creation
om
5.1 HTML File
<!DOCTYPE html>
.c
<html>
ya
<head>
<title>Create Result</title>
</head>
i
un
<body>
<h1>Create Result</h1><br/><hr/><br/>
<form action="se.php" method="POST">
D
37
h1{
text-align:center;
}
form{
om
text-align:center;
}
html{
.c
background-color:#0face0;
ya
5.3 PHP File
i
un
<?php
if (isset($_POST['submit']))
{
D
$roll= $_POST['roll'];
$subject= $_POST['subject'];
ls
$MO= $_POST["MO"];
ia
$MM= $_POST["MM"];
or
$host = "174.136.13.253";
$name = "tricksd3_abhi";
t
$password = "result9101";
Tu
$DB = "tricksd3_result";
$conn = mysqli_connect($host,$name,$password,$DB);
if(!$conn)
38
die("Connection failed :
".mysqli_connect_error());
om
if(mysqli_query($conn,$sql))
echo "RECORD created successfully";
else
.c
echo "Error connecting database :
ya
".mysqli_error($conn);
mysqli_close($conn);
i
un
echo "<script>alert('RECORD created
successfully')</script>";
D
header("Location:index.html");
ls
}
?>
ia
t or
Tu
39
om
.c
i ya
un
D
ls
ia
or
40
om
.c
i ya
un
D
ls
ia
41
om
.c
ya
i
un
f. Generate Datesheet g. Generate Syllabus
D
ls
ia
t or
Tu
42
om
.c
i ya
un
D
ls
CHAPTER – 6 Testing
ia
43
om
O3 = { per = 80 && per > 70 , Grade = ‘B+’ }
O4 = { per = 70 && per > 60 , Grade = ‘B’ }
O5 = { per = 60 && per > 50 , Grade = ‘C’ }
.c
O6 = { per = 50 && per > 40 , Grade = ‘D’ }
O7 = { per = 40 && per >= 33 , Grade = ‘E’ }
ya
O8 = { per < 33 && per >= 0 , Grade = ‘F’ }
i
un
D
ls
ia
t or
Tu
44
om
1. {
2. int Grade;
3. int Total_Marks = Sub1 + Sub2 + Sub3 + Sub4;
4. int per = Total_Marks/ Total_Max_Marks * 100;
.c
5. if ( per > 90 )
ya
6. Grade = ‘A+’;
7. else if ( per > 80 )
8. Grade = ‘A’; i
un
9. else if ( per > 70 )
10. Grade = ‘B+’;
11.else if ( per > 60 )
D
19.else
Tu
45
om
6 7
.c
9
10
ya
11
i 12
un
13
14
D
15
ls
16
ia
17
or
18
19
t
20
Tu
21
46
Edges (e) = 28
Vertices (v) = 21
Cyclometric Complexity ( CC) = e–v+2
om
= 28 – 21 + 2
= 7+2
= 9
.c
Hence , there will be 9 independent paths.
ya
6.5 Independent Paths
i
a.) 1 --> 2 --> 3 --> 4 --> 5 --> 6 --> 21
un
b.) 1 --> 2 --> 3 --> 4 --> 5 --> 7 --> 8 -->21
D
d.) 1 --> 2 --> 3 --> 4 --> 5 --> 7 --> 9 --> 11 --> 12 --> 21
e.) 1 --> 2 --> 3 --> 4 --> 5 --> 7 --> 9 --> 11 --> 13 --> 14 --> 21
ia
f.) 1 --> 2 --> 3 --> 4 --> 5 --> 7 --> 9 --> 11 --> 13 --> 15 --> 16 --> 21
or
g.) 1 --> 2 --> 3 --> 4 --> 5 --> 7 --> 9 --> 11 --> 13 --> 15 --> 17 --> 18 --> 21
t
h.) 1 --> 2 --> 3 --> 4 --> 5 --> 7 --> 9 --> 11 --> 13 --> 15 --> 17 --> 19 --> 21
Tu
i.) 1 --> 2 --> 3 --> 4 --> 5 --> 7 --> 9 --> 11 --> 13 --> 15--> 17 --> 19--> 20--
>21
47
Chapter – 7
User Manual
1.0 Introduction
om
The “Examination and Result Management System” application allows students a
simple interface to access their account from a mobile device to view their Result,
Syllabus, Datesheet etc. This document will provide instructions for using the
.c
application.
STEP 1 : Tap the “Examination and Result Management System” icon in your
or
STEP 2 : Students need to Log In to use the application by providing their user
t
STEP 4 : Now, a student can view their Result , Datesheet , Syllabus and Admit
Card.
48
om
Smartphone with Android versions 5.0(Lollipop) and above.
.c
ya
3. Troubleshooting
49
Chapter -8
Conclusions
The entire project has been developed and deployed as per the requirements stated
om
by the user. It is found to be bug free as per the testing standards that are
implemented.
The whole system’s activities divided are into three major parts like
.c
Student, Teacher and Admin. For implementing the system Android studio is
used.
The estimated cost of the project is (efforts) 4.53 and the estimated size of the
project is (FP) 153.
Finally, we like to conclude that we put all our efforts throughout the development
of our project and tried to fulfill most of the requirements of the user.
50
Chapter - 9
References
om
1. https://www.tutorialsduniya.com
.c
Recommended Practice for Software Requirements Specifications”, October 20,
1998.
i ya
3. The principle source of text book material is “Software Engineering A
PRACTITIONER ’ SAPPROACH” by Roger S. Pressman.
un
4. The principle source of text book material is “A Concise Introduction to
D
5. https://www.tutorialsduniya.com
ia
t or
Tu
51