Delhi University

B.Sc. (H) Computer Science

Software Engineering Project

Examination and Result

Management System
TutorialsDuniya.com
Note: This project is made by a student of B.Sc. (H)
Computer Science and may contain some errors. You can
report the errors at contact@tutorialsduniya.com

Website: https://www.tutorialsduniya.com
FaceBook: https://www.facebook.com/tutorialsduniya
YouTube: https://www.youtube.com/user/TutorialsDuniya
LinkedIn: https://www.linkedin.com/company/tutorialsduniya
 Examination and Result

Management System

Software Engineering Project Report

o m
.c
i ya
un
sD

Submitted By :
al

Abhishek Sharma Ankit Singh Manoj Minesh

ri

16035500000 16035500000 16035500000 16035500000

to
Tu

B.Sc. (H) Computer Science

Keshav Mahavidyalaya
University Of Delhi

1
 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
our gratitude to the people who have been instrumental in the successful

m
completion of this project.
The completion of any inter-disciplinary project depends upon cooperation, co-

o
ordination and combined efforts of several sources of knowledge.

.c
We are eternally grateful to our TutorialsDuniya.Com for his even willingness to

ya
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.
sD

We are highly thankful to our project internal guide TutorialsDuniya.Com and

TutorialsDuniya.Com, whose invaluable guidance helped us, understands the
project better.
al

Although there may be many who remain unacknowledged in this humble note of
ri

gratitude, there are none who remain unappreciated.

to
Tu

Abhishek Sharma Ankit Singh Manoj Minesh

16035500000 16035500000 16035500000 16035500000

Certificate
2
This is to certify that Software Engineering project report entitled “Examination
and Result Management System” is the work carried out by Abhishek Sharma ,
Ankit Singh , Manoj , Minesh, student of B.Sc(H) Computer Science 4th Semester,
Keshav Mahavidyalaya, University of Delhi under the supervision of
TutorialsDuniya.Com.

m
This report has not been submitted to any other organization/institution for the

o
award of any other degree/diploma.

.c
i ya
un
sD
al
ri
to
Tu

TutorialsDuniya.Com TutorialsDuniya.Com
TutorialsDuniya.Com
(Project Supervisor) (Principal) (H.O.D.)

3
 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
blessings of technology is web application. It allows users to interact with the

m
system from anywhere as long as they are connected to the internet.

o
.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
sD

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
al

well as user friendly. So here, we are going to implement a web system, which we
already stated above, having all the features that will make it more user friendly
ri

and accessible.
to

The aim of this project was to develop a System that would help an institution to
Tu

manage all its data.

It is having mainly three modules. One is at Administration Level, second is at

Teacher Level and the other one is of student level.

4
The Application maintains authentication in order to access the application.
Administrator task includes managing all the students and teachers records. To
achieve this aim, a database was designed in order to allow the Institution’s
operators to enter, and store all the information about students like their result,
datesheet, syllabus etc.

m
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

o
and construction to provide same comfort and ease to the user.

.c
i ya
un
sD
al
ri
to
Tu

5
 Table of Contents

1. Software Requirement Specification

9
1.1 Introduction

m
9

o
1.1.1 Problem Statement
9

.c
1.1.2 Process Model

ya
10
1.1.3 Purpose
10 i
un
1.1.4 Document Conventions
11
sD

1.1.5 Intended Audience and Reading Suggestions

11
al

1.1.6 Product Scope

11
ri

1.1.7 References
12
to

1.2 Overall Description

Tu

12
1.2.1 Product Perspective
12
1.2.2 Product Functions
13

6
1.2.3 User Classes and Characteristics
13
1.2.4 Operating Environment
14
1.2.5 Design and Implementation Constraints
14

m
1.2.6 User Documentation
15

o
1.2.7 Assumptions and Dependencies

.c
15

ya
1.3 External Interface Requirements
15
1.3.1 User Interfaces i
un
16
1.3.2 Hardware Interfaces
sD

16
1.3.3 Software Interfaces
17
al

1.3.4 Communication Interfaces

ri

17
1.4 System Features
to

17
1.5 Other Non-Functional Requirements
Tu

18
1.5.1 Performance Requirements
18
1.5.2 Safety Requirements
18

7
1.5.3 Security Requirements
19
1.5.4 Software Quality Attributes
19
1.6 Data Flow Diagrams
20

m
1.6.1 Level – 0
20

o
1.6.2 Level – 1

.c
21

ya
1.7. Data Dictionary
22
2. Estimation & Scheduling i
un
23
2.1 Size Estimation
sD

23
2.2 Cost Estimation
26
al

2.3 Scheduling
ri

27
2.3.1 Gantt Chart
to

27
3.Architectural Design
Tu

28
4.Risk Analysis
29
4.1 RMMM
30

8
5.Implementation
35
5.1 HTML File
35
5.2 CSS File
36

m
5.3 PHP File
36

o
5.4 Snapshots of module

.c
38

ya
6.Testing
40
6.1 Black Box Testing i
un
40
6.1.1 Equivalence class testing
sD

40
6.1.1.1 Input equivalence class
40
al

6.1.1.2 Output equivalence class

ri

40
6.2 White Box Testing
to

41
6.2.1 Basis path testing
Tu

41
6.3 Program flow graph
42
6.4 Cyclometric Complexity
43

9
6.5 Independent Paths
43
7. User Manual
44
7.1 Introduction
44

m
7.2 Getting Started
44

o
7.2.1 Quick Start

.c
44

ya
7.2.2 System Requirements
45
7.3 Troubleshooting i
un
45
8. Conclusions
sD

47
9. References
48
al
ri
to
Tu

10
 TutorialsDuniya.com
Get FREE Compiled Books, Notes, Programs, Books, Question Papers with Solution*
etc of following subjects from https://www.tutorialsduniya.com.

 C and C++  Computer System Architecture

 Programming in Java  Discrete Structures
 Data Structures  Operating Systems
 Computer Networks  Algorithms
 Android Programming  DataBase Management Systems
 PHP Programming  Software Engineering
 JavaScript  Theory of Computation
 Java Server Pages  Operational Research
 Python  System Programming
 Microprocessor  Data Mining
 Artificial Intelligence  Computer Graphics
 Machine Learning  Data Science

 Compiled Books: https://www.tutorialsduniya.com/compiled-books

 Programs: https://www.tutorialsduniya.com/programs
 Question Papers: https://www.tutorialsduniya.com/question-papers
 Python Notes: https://www.tutorialsduniya.com/python
 Java Notes: https://www.tutorialsduniya.com/java
 JavaScript Notes: https://www.tutorialsduniya.com/javascript
 JSP Notes: https://www.tutorialsduniya.com/jsp
 Microprocessor Notes: https://www.tutorialsduniya.com/microprocessor
 OR Notes: https://www.tutorialsduniya.com/operational-research
 Chapter - 1

Software Requirements Specification

1.1 Introduction

o m
This document lays out a project plan for the development of “Examination and

.c
Result Management System”.

The plan will include, but is not restricted to, a summary of the system

ya
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
sD

preliminary glimpse of the software application’s User Interface (UI). The

document will also cover hardware, software, and various other technical
al

dependencies.
ri
to

1.1.1 Problem Statement

Tu

In our current examination conduction and result processing system, there is too
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
So, there is always a risk of loss of information due to various reasons.

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,
automatically calculate the percentage and grade point of the students.

m
With the use of our software, the span required for declaration of result and use of

o
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.
sD

The requirements are added in the prototype as and when they are understood.

Software reviews are applied at various points during software engineering and
al

serve to uncover the errors and defects that can be removed.

ri

1.1.3 Purpose
to

The goal of this project is to provide a mobile application for all the students and
Tu

teachers and Institute’s administrators , to build an online system to manage all the
records related to examination and result of students and teachers to ease the
service of examination and result management.

12
1.1.4 Document Conventions

This document features some terminologies which readers may be unfamiliar with
:
SRS : Software Requirement Specification
DESC : Description

m
1.1.5 Intended Audience and Reading Suggestions

o
The intended audience is any person who wants to :

.c
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
sD

The “Examination and Result Management System” is a mobile application, which

helps students and teachers to find all the up-to-date information related to
al

examination and result.

The Examination and Result Management System is composed of two main
ri

components: a client-side application which will run on Android handsets, and a

to

server-side application which will support and interact with client-side queries.
The server-side verifies logins as Student , Teacher or Administrator and manages
Tu

user information. The data will be held in an Access database on the server.
The administrator logins to upload information about creating/updating a record of
a student or a teacher, or handle the complaints and queries put forward by
students/teachers.
The application should be free to download from either a mobile phone application
store or similar services.

13
1.1.7 References

1. IEEE Software Engineering Standards Committee, “IEEE Std 830-1998,

IEEE Recommended Practice for Software Requirements Specifications”,
October 20, 1998.

m
[IEEE] The applicable IEEE standards are published in “IEEE Standards
Collection,” 2001 edition.

o
.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.
sD

1.2 Overall Description

al

1.2.1 Product Perspective

ri

All system information is maintained in a database, which is located on a server.

to

This includes user and admin information as well as information related to

Tu

examination and result i.e. syllabus, result, datesheet etc.

An Internet connection is necessary to access the system , to fetch and display
results and to log in . Since this is a data-centric product it will need somewhere to
store the data. For that, a database will be used. The mobile application will
communicate with the database. All of the database communication will go over
the Internet.

14
1.2.2 Product Functions

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
features are essential to the application’s operation, whereas additional features

m
simply add new functionalities.

o
1.2.3 User Classes and Characteristics

.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.
sD

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
al

literate. The user interface will be as intuitive as possible. Thus, technical expertise
and Android experience should not be an issue.
ri
to

1.2.4 Operating Environment

Tu

The main component of the Examination and Result Management System is the
software application, which will be limited to the Android operating system
(specifically Android 4.0 and above). The application is not resource- or graphics-
intensive, so there are no practical hardware constraints.
The app will rely on several functionalities built into Android’s Application
Programming Interface (API), so ensuring appropriate usage of the API will be a

15
major concern. Beyond that, the application is a self-contained unit and will not
rely on any other Android-related software components.

1.2.5 Design and Implementation Constraints

The primary design constraint is the mobile platform. Since the application is

m
designated for mobile handsets, limited screen size and resolution will be a major

o
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
un
responsive, so each feature must be designed and implemented with efficiency in
mind.
sD

1.2.6 User Documentation

al

As the product is available in play-store, On-line help system becomes a critical

ri

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
to

provided.
Tu

1.2.7 Assumptions and Dependencies

The System will run on Android Device with Internet Connectivity.

The product shall take initial load time depending on internet connection strength
which also depends on the media from which the product is run.

16
The performance shall depend upon hardware components of the client/customer’s
mobile handset.

1.3 External Interface Requirements

m
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

o
interfaces and provides basic prototypes of the user interface.

.c
The protocol used shall be HTTP.

ya
The Port number used will be 80.

There shall be logical address of the system in IPv4 format.

i
un
1.3.1 User Interfaces
sD

A first-time user of the mobile application should see the log-in page when he/she
al

opens the application.

If the user is not a first-time user, he/she should be able to see profile directly
ri

when the application is opened.

An administrator should be able to log in to the Application where he/she can
to

administer the system by for instance editing user and other information.
Tu

1.3.2 Hardware Interfaces

Examination and Result Management app is intended as a mobile application for

the Android platform and hence is solely supported on Android-powered devices.
The Android platform supports push messages that will be used to synchronize

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
connect internet will be hardware interface for the system. As for e.g.Wi-Fi,

m
mobile data.
The hardware connection to the database server is managed by the underlying

o
operating system on the mobile phone.

.c
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
sD

Android operating systems using the Java JDK (Java Development Kit) and the
Android SDK (software development kit) tools.
al
ri

1.3.4 Communications Interfaces

The Examination and Result Management app shall use the HTTP protocol for
to

communication over the internet and for the intranet communication will be
Tu

through TCP/IP protocol suite.

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
1.4 System Features
The System maintains information about the examination and result. Of course ,
this Project has a high priority because it is very difficult to manage all the
information about the examination and result manually.
 To solve the problem of physically managing all the information about the
examination and result , our application provides several features, such as :-

m
 View result (All Users)

o
 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)
sD

 Create/Update User profile (Only Admin)

al

1.5 Other Nonfunctional Requirements

ri

1.5.1 Performance Requirements

to

Performance should not be an issue because all of our server queries involve small
Tu

pieces of data. Changing screens will require very little computation and thus will
occur very quickly. Server updates should only take a few seconds as long as the
phone can maintain a steady signal.

19
1.5.2 Safety Requirements

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.
The user’s password should always be echoed with special characters representing

m
typed characters.
The system’s back-end servers shall only be accessible to authenticated

o
administrators.

.c
The system’s back-end databases shall be encrypted.

1.5.3 Security Requirements

i ya
un
This application assumes that only the user having the user id and password will
have access to his/her Android handset.
sD

1.5.4 Software Quality Attributes

al

The graphical user interface (GUI) of Examination and Result Management app is
ri

to be designed with usability as the first priority. The app will be presented and
to

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
Tu

errors in the algorithm that computes result and percentage of the students.

20
 TutorialsDuniya.com
Get FREE Compiled Books, Notes, Programs, Books, Question Papers with Solution*
etc of following subjects from https://www.tutorialsduniya.com.

 C and C++  Computer System Architecture

 Programming in Java  Discrete Structures
 Data Structures  Operating Systems
 Computer Networks  Algorithms
 Android Programming  DataBase Management Systems
 PHP Programming  Software Engineering
 JavaScript  Theory of Computation
 Java Server Pages  Operational Research
 Python  System Programming
 Microprocessor  Data Mining
 Artificial Intelligence  Computer Graphics
 Machine Learning  Data Science

 Compiled Books: https://www.tutorialsduniya.com/compiled-books

 Programs: https://www.tutorialsduniya.com/programs
 Question Papers: https://www.tutorialsduniya.com/question-papers
 Python Notes: https://www.tutorialsduniya.com/python
 Java Notes: https://www.tutorialsduniya.com/java
 JavaScript Notes: https://www.tutorialsduniya.com/javascript
 JSP Notes: https://www.tutorialsduniya.com/jsp
 Microprocessor Notes: https://www.tutorialsduniya.com/microprocessor
 OR Notes: https://www.tutorialsduniya.com/operational-research
 1.6 Data Flow Diagram

6.1 Level – 0 DFD

USER

o m
.c
EXAMINATION AND

ya
RESULT
COMPUTATION SYSTEM
i
un
a lsD
ri

DATESHEET RESULT SYLLABUS USER

ADMIT CARD PROFILE
to
Tu

21
 6.2 Level – 1 DFD

DATABASE USER DATABASE

m
LOGIN

o
.c
VIEW
DATESHEET CREATE
DATESHEET
VIEW USER

ya
ADMIT PROFILE
CARD

i
un
sD

STUDENT TEACHER ADMIN

al
ri
to

VIEW VIEW CREATE CREATE

RESULT SYLLABUS RESULT CREATE ADMIT
SYLLABUS CARD
Tu

DATABASE

22
1.7 Data Dictionary
a. User Credentials = UserID + Password + Role of user

b. Create Result = RollNo + Subject + Course + M.O. + M.M.

c. Create Syllabus = Subject + Course + Chapters

m
d. Create Datesheet = Subject + Date + RoomNo. + Time + Duration

o
e. Create Admit Card = Name + RollNo. + Sem + Subject + PaperCode + M.M.

.c
i ya
un
sD
al
ri
to
Tu

23
 Chapter – 2

Estimation And Scheduling

2.1 Size Estimation

m
 Function-oriented software metrics use a measure of the functionality

o
delivered by the application as a normalization value. Since

.c
‘functionality’ cannot be measured directly, it must be derived
indirectly using other direct measures.

ya
 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
sD

software complexity.
 Function points are computed by completing the table as shown below.
Five information domain characteristics are determined and counts are
al

provided in the appropriate table location. Information domain values

ri

are defined in the following manner:


to

 Number of user inputs. Each user input that provides distinct

Tu

application oriented data to the software is counted. Inputs should be

distinguished from inquiries, which are counted separately.
 Number of user outputs. Each user output that provides application

oriented information to the user is counted. In this context output refers

to reports, screens, error messages, etc. Individual data items within a
report are not counted separately.

24
  Number of user inquiries. An inquiry is defined as an on-line input

that results in the generation of some immediate software response in

the form of an on-line output. Each distinct inquiry is counted.

 Number of files. Each logical master file (i.e., a logical grouping of

m
data that may be one part of a large database or a separate file) is
counted.

o
.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
sD
al
ri
to
Tu

 To compute function points (FP), the following relationship is used :

FP = count total [0.65 + 0.01 Σ ( Fi)]

Where count total is the sum of all FP entries .

25
 The Fi (i = 1 to 14) are "complexity adjustment values" based on responses.

Functional Types Simple Medium Complex

External I/P 4 3 1
External O/P 1 4 1

m
Logical Interface 1 2 1
External Interface 0 0 0

o
External Enquiry 3 2 0

.c
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 +
i
un
4*2
= 12 + 12 + 6 + 4 + 20 + 7 + 7 + 20 + 15 + 9 + 8
= 120
sD

 CAF = 0.65 + ∑i=1 to 14 Fi * 0.01

al

= 0.65 + 0.01 X 14 X 3
= 1.07
ri
to

 FP = UFP * CAF
= 120 X 1.07
Tu

= 128.4
= 128 (approx)

2.2 Cost Estimation

We have used COCOMO2 model for the cost estimation of our project.

26
  COCOMO2 ( COnstructive COst Model 2) is an algorithmic cost
estimation technique proposed by Boehm, which works in a
bottom-up manner.
 It is designed to provide some mathematical equations to estimate software
projects.
 These mathematical equations are based on historical data and use

m
project size in the form of KLOC.
 The COCOMO model uses a multivariable size estimation model

o
for effort estimation.

.c
i ya
un
 Object Point = ∑3 i =1 ∑3 i =j Cij * Wij
lsD

SIMPLE MEDIUM COMPLEX

a

SCREENS 1 3 2
ri
to

REPORT 1 3 1
Tu

3GL 0 0 1
(1X1+3X2+2X3)+(1X2+3X5+1X8)+(1X10)
= 13+25+10
= 48

27
  NOP = Object Point * ( 1 - % reuse/100)
= 48 * (1-0)
= 48

 Efforts = NOP/ PROD

= 48/13

m
= 3.7

o
.c
NOP = New Object Point

ya
PROD = Productivity
We have assumed nominal developer experience
i
un
sD
al
ri
to
Tu

28
2.3 Scheduling

2.3.1 Gantt Chart

Group Topic : Examination and Result Management System

m
Steps End Date

SRS - 20 February

o
Cost & Size Estimation - 27 February

.c
Design - 13 March

ya
Implementation - 20 March
Testing - 27 March
User manual - i 3 April
un
Source code & Deployment - 10 April
sD
al
ri
to
Tu

29
 Chapter – 3

Architectural Diagram

m
Examination and Result
Management System

o
.c
ya
Student Admin

i
un
sD

View Result View

Syllabus

View View Admit

Datesheet Card
al

Edit/Delete Edit/Delete Edit/Delete

Syllabus User
ri

Result

Edit/Delete Edit/Delete
to

Datesheet Admit Card

Tu

30
 Chapter – 4
Risk Management
 Risk always involves two characteristics:

m
a. Uncertainty - The risk may or may not happen. There are no 100% probable
risks.

o
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
sD

their probability of occurrence. Plans will then be made to avoid each risk,

to track each risk to determine if it is more or less likely to occur, and to

al

plan for those risks should they occur.

ri

 It is the organization’s responsibility to perform risk mitigation, monitoring,

to

and management in order to produce a quality product.

 The quicker the risks can be identified and avoided, the smaller the chances
Tu

of having to face that particular risk’s consequence. The fewer

consequences suffered as a result of good RMMM plan, the better the

product, and the smoother the develop-ment process.

Risk Table
31
 Risks Category Probability Impact

Computer Crash Technical Risk 70% 1

Late Delivery Project Risk 30% 1

End Users Resist Project Risk 20% 1

m
System

o
Changes in Project Risk 20% 2

.c
Requirements

Impact Values:
1 – Catastrophic i ya
un
2 – Critical
3 – Marginal
sD

4 – Negligible
al

Risk 1 : Computer Crash

ri

 Mitigation
to

The cost associated with a computer crash resulting in a loss of data is crucial. A
Tu

computer crash itself is not crucial, but rather the loss of data. A loss of data will

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
organization is taking steps to make multiple backup copies of the software in

development and all documentation associated with it, in multiple locations.

 Monitoring

When working on the product or documentation, the staff member should always

m
be aware of the stability of the computing environment they’re working in. Any

o
changes in the stability of the environment should be recognized and taken

.c
seriously.

ya
 Management

i
un
The lack of a stable-computing environment is extremely hazardous to a software

development team. In the event that the computing environment is found

sD

unstable, the development team should cease work on that system until the
al

environment is made stable again, or should move to a system that is stable and

continue working there.

ri
to
Tu

Risk 2 : Late Delivery

 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

m
A schedule has been established to monitor project status. Falling behind schedule

o
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
sD

course. If it becomes apparent that the project will not be completed on time, the

only course of action available would be to request an extension to the deadline

al

form the customer.

ri
to

Risk 3 : End Users Resist System

Tu

 Mitigation

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

program convenient and pleasurable.

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

phases. Specifically the user-interface developer will be sure to get a thorough

m
opinion from others.

o
 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
sD
al
ri

Risk 4 : Changes in Requirements

to

 Mitigation
Tu

In order to prevent this from happening, meetings (formal and informal) will be

held with the customer on a routine business. This insures that the product we are

producing, and the requirements of the customer are equivalent.

 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

m
requirements differs from those of the customer, the customer should be

o
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
sD
al
ri
to
Tu

36
 TutorialsDuniya.com
Get FREE Compiled Books, Notes, Programs, Books, Question Papers with Solution*
etc of following subjects from https://www.tutorialsduniya.com.

 C and C++  Computer System Architecture

 Programming in Java  Discrete Structures
 Data Structures  Operating Systems
 Computer Networks  Algorithms
 Android Programming  DataBase Management Systems
 PHP Programming  Software Engineering
 JavaScript  Theory of Computation
 Java Server Pages  Operational Research
 Python  System Programming
 Microprocessor  Data Mining
 Artificial Intelligence  Computer Graphics
 Machine Learning  Data Science

 Compiled Books: https://www.tutorialsduniya.com/compiled-books

 Programs: https://www.tutorialsduniya.com/programs
 Question Papers: https://www.tutorialsduniya.com/question-papers
 Python Notes: https://www.tutorialsduniya.com/python
 Java Notes: https://www.tutorialsduniya.com/java
 JavaScript Notes: https://www.tutorialsduniya.com/javascript
 JSP Notes: https://www.tutorialsduniya.com/jsp
 Microprocessor Notes: https://www.tutorialsduniya.com/microprocessor
 OR Notes: https://www.tutorialsduniya.com/operational-research
 Chapter – 5
Implementation
 Implementing module for result creation

m
5.1 HTML File

o
<!DOCTYPE html>

.c
<html>
<head>

ya
<title>Create Result</title>
</head>
i
un
<body>
<h1>Create Result</h1><br/><hr/><br/>
<form action="se.php" method="POST">
sD

<label for="roll">Roll No.</label>

<input type="text" name="roll" /><br/><br/>
al

<label for="subject">Subject</label>
<input type="text" name="subject" /><br/><br/>
ri

<label for="MO">Marks Obt.</label>

to

<input type="text" name="MO" /><br/><br/>

<label for="MM">Max. Marks</label>
Tu

<input type="text" name="MM" /><br/><br/>

<input type="button" value="Create Result" />
</form>
</body>
</html>

37
 5.2 CSS file

h1{
text-align:center;
}
form{

m
text-align:center;
}

o
html{

.c
background-color:#0face0;

ya
5.3 PHP File
i
un
<?php
if (isset($_POST['submit']))
{
sD

$roll= $_POST['roll'];
$subject= $_POST['subject'];
al

$MO= $_POST["MO"];
$MM= $_POST["MM"];
ri
to

$host = "174.136.13.253";
$name = "tricksd3_abhi";
Tu

$password = "result9101";
$DB = "tricksd3_result";

$conn = mysqli_connect($host,$name,$password,$DB);

if(!$conn)

38
 die("Connection failed :
".mysqli_connect_error());

$sql = "INSERT INTO Result values($roll, $subject,

$MO, $MM);";

m
if(mysqli_query($conn,$sql))
echo "RECORD created successfully";

o
else

.c
echo "Error connecting database :

ya
".mysqli_error($conn);

mysqli_close($conn);
i
un
echo "<script>alert('RECORD created
successfully')</script>";
sD

header("Location:index.html");
}
al

?>
ri
to
Tu

39
5.4 Snapshots of Module
a. View Profile (Student) b. View Profile (Teacher)

o m
.c
ya
i
un
sD
al
ri
to

c. View Result d. Generate New Result

Tu

( only Teacher & Admin )

40
 o m
.c
i ya
un
sD
al
ri

e. View Result - Course wise (only Teacher & Admin)

to
Tu

41
 o m
.c
ya
i
un
f. Generate Datesheet g. Generate Syllabus
sD
al
ri
to
Tu

42
 o m
.c
i ya
un
sD
al

CHAPTER – 6 Testing
ri

6.1 Black Box Testing

to

6.1.1 Equivalence Class Testing

Tu

6.1.1.1 Input Equivalence Class

 Valid Input Classes

I1 = { 16035570000 <= Roll_No<16035570100 }

I2 = { 0 <= ObtMarks <= MaxMarks }

43
 6.1.1.2 Output Equivalence Class
 Output Classes
O1 = { per = 100 && per > 90 , Grade = ‘A+’ }
O2 = { per = 90 && per > 80 , Grade = ‘A’ }
O3 = { per = 80 && per > 70 , Grade = ‘B+’ }

m
O4 = { per = 70 && per > 60 , Grade = ‘B’ }
O5 = { per = 60 && per > 50 , Grade = ‘C’ }

o
O6 = { per = 50 && per > 40 , Grade = ‘D’ }

.c
O7 = { per = 40 && per >= 33 , Grade = ‘E’ }

ya
O8 = { per < 33 && per >= 0 , Grade = ‘F’ }

i
un
sD
al
ri
to
Tu

44
6.2 White Box Testing

6.2.1 Basic Path Testing

void CalcGrade ( Sub1, Sub2, Sub3, Sub4, Total_Max_Marks )

1. {

m
2. int Grade;
3. int Total_Marks = Sub1 + Sub2 + Sub3 + Sub4;

o
4. int per = Total_Marks/ Total_Max_Marks * 100;

.c
5. if ( per > 90 )
6. Grade = ‘A+’;

ya
7. else if ( per > 80 )
8. Grade = ‘A’; i
un
9. else if ( per > 70 )
10. Grade = ‘B+’;
11.else if ( per > 60 )
sD

12. Grade = ‘B’;

13.else if ( per > 50 )
al

14. Grade = ‘C’;

ri

15.else if ( per > 40 )

16. Grade = ‘D’;
to

17.else if ( per >= 33 )

18. Grade = ‘E’;
Tu

19.else
20. Grade = ‘F’;
21.}

45
6.3 Program Flow Graph
START 1
2
3
4
5

m
6 7

o
8

.c
9

10

ya
11

i 12
un
13

14
lsD

15

16
a
ri

17
to

18

19
Tu

20

21

46
6.4 Cyclometric Complexity Calculation

Edges (e) = 28
Vertices (v) = 21
Cyclometric Complexity ( CC) = e–v+2
= 28 – 21 + 2

m
= 7+2
= 9

o
Hence , there will be 9 independent paths.

.c
ya
6.5 Independent Paths
i
a.) 1 --> 2 --> 3 --> 4 --> 5 --> 6 --> 21
un
b.) 1 --> 2 --> 3 --> 4 --> 5 --> 7 --> 8 -->21
sD

c.) 1 --> 2 --> 3 --> 4 --> 5 --> 7 --> 9 --> 10 --> 21

d.) 1 --> 2 --> 3 --> 4 --> 5 --> 7 --> 9 --> 11 --> 12 --> 21
al

e.) 1 --> 2 --> 3 --> 4 --> 5 --> 7 --> 9 --> 11 --> 13 --> 14 --> 21
ri

f.) 1 --> 2 --> 3 --> 4 --> 5 --> 7 --> 9 --> 11 --> 13 --> 15 --> 16 --> 21
to

g.) 1 --> 2 --> 3 --> 4 --> 5 --> 7 --> 9 --> 11 --> 13 --> 15 --> 17 --> 18 --> 21
Tu

h.) 1 --> 2 --> 3 --> 4 --> 5 --> 7 --> 9 --> 11 --> 13 --> 15 --> 17 --> 19 --> 21

i.) 1 --> 2 --> 3 --> 4 --> 5 --> 7 --> 9 --> 11 --> 13 --> 15--> 17 --> 19--> 20--
>21

47
 Chapter – 7
User Manual

1.0 Introduction

The “Examination and Result Management System” application allows students a

m
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

o
application.

.c
2.0 Getting Started
i ya
un
Download and install the “Examination and Result Management System”
application available on play store or AppleStore . The application is compatible
sD

with Android versions 5.0(Lollipop) and above.

al

2.1 Quick Start : Students

ri

STEP 1 : Tap the “Examination and Result Management System” icon in your
to

device menu. The Login screen will be brought up.

STEP 2 : Students need to Log In to use the application by providing their user
Tu

name and password.

STEP 3 : Once you are logged in , Your profile will be opened.

STEP 4 : Now, a student can view their Result , Datesheet , Syllabus and Admit
Card.

48
STEP 5 : To view his Result/Datesheet/Syllabus/Admit Card , he simply needs to
click on the respective button displayed on his profile.

2.2 System Requirements

Smartphone with Android versions 5.0(Lollipop) and above.

m
Internet connection for Application to function.

o
.c
ya
3. Troubleshooting

Missing or Incorrect Password or E-Mail

i
un
A message will be displayed in the event incorrect login information is entered.
Try again with proper credentials to access
sD
al
ri
to
Tu

49
 Chapter -8

Conclusions

The entire project has been developed and deployed as per the requirements stated
by the user. It is found to be bug free as per the testing standards that are

m
implemented.

o
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 system comprise of following features :

i ya
un
 View result (All Users)
 View Syllabus (All Users)
 View admit card (All Users)
sD

 View Datesheet (All Users)

 View his Profile (All Users)
al

 Create/Update Result (Only Teacher and Admin)

ri

 Create/Update Syllabus (Only Admin)

 Create/Update Datesheet (Only Admin)
to

 Create/Update Admit Card (Only Admin)

 Create/Update User profile (Only Admin)
Tu

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

1. https://www.tutorialsduniya.com

o m
2. IEEE Software Engineering Standards Committee, “IEEE Std 830-1998, IEEE

.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
sD

Software Engineering” by Pankaj Jalote

al

5. https://www.tutorialsduniya.com
ri
to
Tu

51
 TutorialsDuniya.com
Get FREE Compiled Books, Notes, Programs, Books, Question Papers with Solution*
etc of following subjects from https://www.tutorialsduniya.com.

 C and C++  Computer System Architecture

 Programming in Java  Discrete Structures
 Data Structures  Operating Systems
 Computer Networks  Algorithms
 Android Programming  DataBase Management Systems
 PHP Programming  Software Engineering
 JavaScript  Theory of Computation
 Java Server Pages  Operational Research
 Python  System Programming
 Microprocessor  Data Mining
 Artificial Intelligence  Computer Graphics
 Machine Learning  Data Science

 Compiled Books: https://www.tutorialsduniya.com/compiled-books

 Programs: https://www.tutorialsduniya.com/programs
 Question Papers: https://www.tutorialsduniya.com/question-papers
 Python Notes: https://www.tutorialsduniya.com/python
 Java Notes: https://www.tutorialsduniya.com/java
 JavaScript Notes: https://www.tutorialsduniya.com/javascript
 JSP Notes: https://www.tutorialsduniya.com/jsp
 Microprocessor Notes: https://www.tutorialsduniya.com/microprocessor
 OR Notes: https://www.tutorialsduniya.com/operational-research