CAMPUS ASSESSMENT SYSTEM

by

SIVASANKARAN.N

(Registration Number: 17370043)

Project report submitted in partial fulfillment of the requirements for the award of the degree
of
MASTER OF COMPUTER SCIENCE

Under the guidance of

Dr. K. SURESH JOSEPH

Assistant Professor

DEPARTMENT OF COMPUTER SCIENCE

SCHOOL OF ENGINEERING & TECHNOLOGY

PONDICHERRY UNIVERSITY

May 2018
BONAFIDE CERTIFICATE

This is to certify that this project work entitled “CAMPUS ASSESSMENT SYSTEM”
is the Bonafide record of work done by
MR.SIVASANKARAN .N (Reg. No.: 17370043) in partial fulfillment for the award of
degree of Master of Science in Computer Science, Department of Computer Science, School
of Engineering And Technology, Pondicherry University.

This work has not been submitted elsewhere for the award of any other degree to the best of
our knowledge.

GUIDE HEAD OF THE DEPARTMENT

Dr. K. Suresh joseph Dr. T. Chithralekha
Assistant Professor Associate Professor and Head
Department of Computer Science Department of Computer Science
School of Engineering &Technology School of Engineering &Technology
Pondicherry University Pondicherry University
Pondicherry – 605 014 Pondicherry – 605 014

Submitted for the Viva-Voce Examination held on _____________

INTERNAL EXAMINER EXTERNAL

EXAMINER
TABLE OF CONTENT
ACKNOWLEDGEMET

1. INTRODUCTION

1.1 Introduction

1.2 Problem introduction

1.3 Modules in the project

1.4 Plan Of The Project

2. REQUIREMENTS SPECIFICATION

2.1 Introduction

2.2 Hardware requirements

2.3 Software requirements

3. ANALYSIS

3.1 Existing System

3.2 Proposed System

3.3 Feasibility study

3.4 Software specification

4. DESIGN

4.1 System Design

4.1.1 Introduction to UML

4.1.2 UML Diagrams of our project

5. TESTING

5.1 Introduction

5.2 testing methods

6.CONCLUSION

7. BIBLOGRAPHY
8.APENDIX

SCREENSHOTS

Campus Assessment System

ABSTRACT
The main purpose of this System is to develop a process/ system through which the efficiency
of an Institution can be increased by continuous monitoring and assessment of various
practices right from academic offerings to infrastructural facilities adopted by the institution.
The main aim of the system is to identify whether the services of the institution under
different segments such as Teaching/Learning mechanism, student support services (such as
training, placement, career guidance), infrastructural support are in accordance with the
expected level of performance. The system further points out the deviations/deficiencies, if
any, and suggests possible control measures to bring back the services on the expected level
of performance. This is achieved by gathering opinions/feedback from the stakeholders of the
system such as heads of departments, teacher, and student.
This application can be used as Intranet / Internet Application. Using intranet HODs can post
the queries and their related options on the site. The authentication for both student and
faculty is provided in this system. Any authenticated user can log in and post the views,
feedbacks, and suggestions for consideration.
When it comes to the student, depending on the queries one can choose the options.
Depending on the knowledge provided the HODs will be able to analyze and take a precise
decision.
The system further maintains an address book containing the email ids and contact details of
all the students, faculty members, and other staff members so that they can be contacted as
and when needed.

MODULES
 HOD
 Teacher
 Student
 Admin
 Reports

LIST OF REQUIREMENTS
The given requirements are defined below.
 Internal campus assessment Application system should have the Login screen. By this
feature the Faculty / Student enters into the system.
 A login box should appear to the Faculty / Student, when the system is invoked.
 The logins are assigned by the Administrator only, not by the other users of the
system.
 The System should display proper error messages in case of an error.
 The System should enable the user to Logout. This feature ensures the security of the
application such that no more transactions can be carried out, once user logs out.
 The application must adhere to usability and interoperability norms so that system can
be more user friendly by virtue of providing necessary screens and navigations.
SCOPE (IN AND OUT) OF THE PROJECT
Description of what features are in the scope and out of the scope of the Project.
In Scope
 Internal campus assessment system should have the login screen, by this feature the
HOD /Faculty Student / Administrator enters into the system.
 The logins are assigned by the administrator only, for various user types as Faculty,
Student and Departmental-heads.
 Validation of users and based on user type giving different user interfaces.
 Allocation of users to system by Administrator.
 Survey Entry provision must be with the Administrator.
 Generation of different reports based on the survey.
 When the Survey Entries are made by the Admin and when the Faculty/ student logs
into the system they must be able to see different surveys that can be attempted by
them.
 Head of the Department must be able to view the reports in different formats.
 Administrator must be able to enter the master data related to sections, sub-sections,
Academic years and so on.
 Also the process of mapping the Survey to Section must be in Administrator login.

1.4 PLAN OF THE PROJECT

This report helps us to understand
the schedule and time taken to finish the project.
This also tells how the project is planned and
completed in a given schedule.
This gives an clarification for user
about the intentions and output expected for work
being done.
S.NO. ACTIVITY STARTING FINISHING
1 INITIL STUDY OF 12/12/2018 23/01/2019
THE PROBLEM
2 DESIGN THE 26/01/2019 15/02/2019
MODULES OF THE
PROJECT
3 DESIGN UI 18/02/2019 25/04/2019
SCREAN FOR THE
PROJECT
4 CODING OF THE 10/12/2019 25/04/2019
PROJECT
5 EXECUTING THE 25/01/2019 25/04/2019
PROJECT
6 TESTING THE 15/02/2019 23/04/2019
PROJECT
7 FINAL 24/04/2019 26/04/2019
DOCUMENTATION
REQUIREMENT SPECIFICATION

2.1 INTRODUCTION:
To be used efficiently, all computer software needs certain hardware components or the other
software resources to be present on a computer. These pre-requisites are known as(computer)
system requirements and are often used as a guideline as opposed to an absolute rule. Most
software defines two sets of system requirements: minimum and recommended. With
increasing demand for higher processing power and resources in newer versions of software,
system requirements tend to increase over time. Industry analysts suggest that this trend plays
a biggerpart in driving upgrades to existing computer systems than technological
advancements.

2.2 HARDWARE REQUIREMENTS:

The most common set of requirements defined by any operating system or software
application is the physical computer resources, also known as hardware. A hardware
requirements list is often accompanied by a hardware compatibility list (HCL), especially in
case of operating systems. An HCL lists tested, compatibility and sometimes incompatible
hardware devices for a particular operating system or application. The following sub-sections
discuss the various aspects of hardware requirements.

HARDWARE REQUIREMENTS FOR PRESENT PROJECT:

PROCESSOR : Intel dual Core ,i3

RAM : 1 GB

HARD DISK : 80 GB

2.3 SOFTWARE REQUIREMENTS:

Software Requirements deal with defining software resource requirements and pre-requisites
that need to be installed on a computer to provide optimal functioning of an application.
These requirements or pre-requisites are generally not included in the software installation
package and need to be installed separately before the software is installed.

SOFTWARE REQUIREMENTS FOR PRESENT PROJECT:

OPERATING SYSTEM : Windows 7/ XP/8

FRONT END : Html,css, javascript, jquery

SERVER SIDE SCRIPT : PHP

DATABASE : Mysql
CHAPTER 3
ANALYSIS

3.1EXISTING SYSTEM:
Hospitalscurrently use a manual system for the management and maintainance of critical
information.The current system requires numerous paper forms,with data stores spread
through out the hospital management infrastructure.Often information is incomplete or does
not follow management standards.Forms are often lost in transit between departments
requiring a comprehensive auditing process to ensure that no vital information is
lost.Multiple copies of the same information exist in the hospital and may lead to
inconsistencies in data in various data stores.

3.2 PROPOSED SYSTEM:

The Hospital Management System is designed for any hospital to replace their existing
manual paper based system.The new system is to control the information of patients.
Roomavailability,staff and operating room schedules and patient invoices.These services are
to be provided in an efficient,cost effective manner,with the goal of reducing the time and
resources currently required for such tasks .

3.3 FEASIBILITY STUDY

The feasibility of the project is analysed in this phase and business proposal is put
forth with a very general plan for the project and some cost estimates. During system analysis
the feasibility study of the proposed system is to be carried out. This is to ensure that the
proposed system is not a burden to the company. For feasibility analysis, some understanding
of the major requirements for the system is essential.

Three key considerations involved in the feasibility analysis are:

3.3.1 Economic Feasibility

This study is carried out to check the economic impact will have on the system
will have on the organization. The amount of fund that the company can pour
into the research and development of the system is limited. The expenditures
must be justified. Thus the developed system as well within the budget and
this was achieved because most of the technologies used are freely available.
Only the customised products have to be purchased.

3.3.2 Technical Feasibility

This study is carried out to check the technical feasibility, that is,the technical
requirements of the system. Any system developed must not have a high
demand on the availableavailable technical resources. This will lead to high
demands being placed on the client. The developed system must have a
modest requirement, as only minimal or null changes for the implementing
this system.

3.3.3 Operational Feasibility

The aspect of study is to check the level of acceptance of the system by the
user. This includes the process of training the user to use the system
efficiently. The user must not feel threatened by the system, instead must
accept it as a necessity. The level of acceptance by the users solely
depends on the methods that are employed to educate the user about the
system and to make him familiar with it. His level of confidence must be
raised so that he is also able to make some constructive criticism, which is
welcomed, as he is the final user of the system.

3.4 SOFTWARE SPECIFICATION

HTML:
HTML or Hypertext Markup Language is the standard markup language used to
create web pages.
HTML is written in the form of HTML elements consisting of tags enclosed in angle
brackets (like <html>). HTML tags most commonly come in pairs like <h1> and </h1>,
although some tags represent empty elements and so are unpaired, for example <img>. The
first tag in a pair is the start tag, and the second tag is the end tag (they are also
called opening tags and closing tags). Though not always necessary, it is best practice to
append a slash to tags which are not paired with a closing tag.
The purpose of a web browser is to read HTML documents and compose them into visible or
audible web pages. The browser does not display the HTML tags, but uses the tags to
interpret the content of the page. HTML describes the structure of a website
semantically along with cues for presentation, making it a markup language rather than
a programming language.
HTML elements form the building blocks of all websites. HTML allows images and
objects to be embedded and can be used to create interactive forms. It provides a means to
create structured documents by denoting structural semantics for text such as headings,
paragraphs, lists, links, quotes and other items. It can embed scripts written in languages such
as JavaScript which affect the behavior of HTML web pages.

CASCADING STYLE SHEETS (CSS):

It is a style sheet language used for describing the look and formatting of a document written
in a markup language. While most often used to style web pages and interfaces written
in HTML and XHTML, the language can be applied to any kind of XML document,
including plain XML, SVG and XUL. CSS is a cornerstone specification of the web and
almost all web pages use CSS style sheets to describe their presentation.
CSS is designed primarily to enable the separation of document content from document
presentation, including elements such as thelayout, colors, and fonts.[1] This separation can
improve content accessibility, provide more flexibility and control in the specification of
presentation characteristics, enable multiple pages to share formatting, and reduce complexity
and repetition in the structural content .
CSS can also allow the same markup page to be presented in different styles for different
rendering methods, such as on-screen, in print, by voice (when read out by a speech-based
browser or screen reader) and on Braille-based, tactile devices. It can also be used to allow
the web page to display differently depending on the screen size or device on which it is
being viewed. While the author of a document typically links that document to a CSS file,
readers can use a different style sheet, perhaps one on their own computer, to override the one
the author has specified. However if the author or the reader did not link the document to a
specific style sheet the default style of the browser will be applied.
MySQL:

MySQL is developed, distributed, and supported by Oracle Corporation. MySQL is a

database system used on the web it runs on a server.MySQL is ideal for both small and large
applications.It is very fast, reliable, and easy to use.It supports standard SQL.MySQL can be
compiled on a number of platforms.
The data in MySQL is stored in tables. A table is a collection of related data, and it consists
of columns and rows.Databases are useful when storing information categorically.
FEATURES OF MySQL:
Internals and portability:
 Written in C and C++.

 Tested with a broad range of different compilers.

 Works on many different platforms.

 Tested with Purify (a commercial memory leakage detector) as well as with Val grind, a
GPL tool.
 Uses multi-layered server design with independent modules.

Security:
 A privilege and password system that is very flexible and secure, and that enables host-
based verification.

 Password security by encryption of all password traffic when you connect to a server.

Scalability and Limits:

 Support for large databases. We use MySQL Server with databases that contain 50 million
records. We also know of users who use MySQL Server with 200,000 tables and about
5,000,000,000 rows.

 Support for up to 64 indexes per table (32 before MySQL 4.1.2). Each index may consist
of 1 to 16 columns or parts of columns. The maximum index width is 767 bytes
for InnoDB tables, or 1000 for MyISAM; before MySQL 4.1.2, the limit is 500 bytes. An
index may use a prefix of a column for CHAR, VARCHAR, BLOB, or TEXT column types.

CONNECTIVITY:
Clients can connect to MySQL Server using several protocols:

 Clients can connect using TCP/IP sockets on any platform.

 On Windows systems in the NT family (NT, 2000, XP, 2003, or Vista), clients can
connect using named pipes if the server is started with the --enable-named-
pipe option. In MySQL 4.1 and higher, Windows servers also support shared-
memory connections if started with the --shared-memory option. Clients can
connect through shared memory by using the --protocol=memory option.

 On UNIX systems, clients can connect using Unix domain socket files.

LOCALIZATION:
 The server can provide error messages to clients in many languages.
 All data is saved in the chosen character set.
CLIENTS AND TOOLS:

 MySQL includes several client and utility programs. These include both
command-line programs such as mysqldump and mysqladmin, and graphical
programs such as MySQL Workbench.
 MySQL Server has built-in support for SQL statements to check, optimize, and
repair tables. These statements are available from the command line through
the mysqlcheck client. MySQL also includes myisamchk, a very fast command-
line utility for performing these operations on MyISAM tables.
 MySQL programs can be invoked with the --help or -? option to obtain online
assistance.

WHY TO USE MySQL:

 Leading open source RDBMS
 Ease of use – No frills
 Fast
 Robust
 Security
 Multiple OS support
 Free
 Technical support
 Support large database– up to 50 million rows, file size limit up to 8 Million TB
JAVASCRIPT:
JavaScript is the scripting language of the Web. All modern HTML pages are using
JavaScript. A scripting language is a lightweight programming language.JavaScript code can
be inserted into any HTML page, and it can be executed by all types of web browsers.
JavaScript is easy to learn.
WHY TO USE JAVASCRIPT:
JavaScript is one of the 3 languages all web developers must learn:
 HTML to define the content of web pages
 CSS to specify the layout of web pages
 JavaScript to specify the behavior of web pages
Example
x = document.getElementById("demo"); //Find the HTML element with id="demo"
x.innerHTML = "Hello JavaScript"; //Change the content of the HTML element
document.getElementById() is one of the most commonly used HTML DOM methods.
OTHER USES OF JAVASCRIPT:
 Delete HTML elements
 Create new HTML elements
 Copy HTML elements
 In HTML, JavaScript is a sequence of statements that can be executed by the web
browser.

JAVASCRIPT STATEMENTS:

 JavaScript statements are "commands" to the browser.

 The purpose of the statements is to tell the browser what to do.
 This JavaScript statement tells the browser to write "Hello Dolly" inside an HTML
element with id="demo":

Semicolon;
 Semicolon separates JavaScript statements.
 Normally you add a semicolon at the end of each executable statement.
 Using semicolons also makes it possible to write many statements on one line.
JAVASCRIPT CODE:
 JavaScript code (or just JavaScript) is a sequence of JavaScript statements.
 Each statement is executed by the browser in the sequence they are written.
 This example will manipulate two HTML elements:
 Example
 document.getElementById("demo").innerHTML="Hello Dolly";
document.getElementById("myDIV").innerHTML="How are you?";
JAVASCRIPT PROPERTIES:
 Properties are the values associated with a JavaScript object.
 A JavaScript object is a collection of unordered properties.
 Properties can usually be changed, added, and deleted, but some are read only.

PHP:
WHAT IS PHP?
 PHP is an acronym for "PHP Hypertext Preprocessor"
 PHP is a widely-used, open source scripting language
 PHP scripts are executed on the server
 PHP costs nothing, it is free to download and use
WHAT IS PHP FILE?
 PHP files can contain text, HTML, CSS, JavaScript, and PHP code
 PHP code are executed on the server, and the result is returned to the browser as plain
HTML
 PHP files have extension ".php"

WHAT CAN PHP DO?

 PHP can generate dynamic page content
 PHP can create, open, read, write, delete, and close files on the server
 PHP can collect form data
 PHP can send and receive cookies
 PHP can add, delete, modify data in your database
 PHP can restrict users to access some pages on your website
 PHP can encrypt data
With PHP you are not limited to output HTML. You can output images, PDF files, and even
Flash movies. You can also output any text, such as XHTML and XML.

WHY PHP?
 PHP runs on various platforms (Windows, Linux, Unix, Mac OS X, etc.)
 PHP is compatible with almost all servers used today (Apache, IIS, etc.)
 PHP supports a wide range of databases
 PHP is free. Download it from the official PHP resource: www.php.net
CHAPTER 4
DESIGN

4.1 SYSTEM DESIGN:

4.1.1INTRODUCTION TO UML:

UML Design

The Unified Modeling Language (UML) is a standard language for specifying,

visualizing, constructing, and documenting the software system and its components. It is a
graphical language , which provides a vocabulary and set of semantics and rules. The UML
focuses on the conceptual and physical representation of the system. It captures the decisions
and understandings about systems that must be constructed. It is used to understand, design,
configure, maintain, and control information about the systems.

The UML is a language for:

 Visualizing

 Specifying

 Constructing

 Documenting

Visualizing
Through UML we see or visualize an existing system and ultimately we visualize
how the system is going to be after implementation. Unless we think, we cannot
implement. UML helps to visualize, how the components of the system communicate
and interact with each other.

Specifying

Specifying means building, models that are precise, unambiguous and complete
UML addresses the specification of all the important analysis design, implementation
decisions that must be made in developing and deploying a software system.

Constructing

UML models can be directly connected to a variety of programming language

through mapping a model from UML to a programming language like JAVA or C++
or VB. Forward Engineering and Reverse Engineering is possible through UML.

Documenting

The Deliverables of a project apart from coding are some Artifacts, which are critical
in controlling, measuring and communicating about a system during its developing
requirements, architecture, desire, source code, project plans, tests, prototypes
releasers, etc...

4.2 UML Approach

UML Diagram

A diagram is the graphical presentation of a set of elements, most often rendered

as a connected graph of vertices and arcs .you draw diagram to visualize a system
from different perspective, so a diagram is a projection into a system. For all but
most trivial systems, a diagram represents an elided view of the elements that
make up a system. The same element may appear in all diagrams, only a few
diagrams , or in no diagrams at all. In theory, a diagram may contain any
combination of things and relationships. In practice, however, a small number of
common combinations arise, which are consistent with the five most useful views
that comprise the architecture of a software-intensive system. For this reason, the
UML includes nine such diagrams:

 Class diagram

 Object diagram

 Use case diagram

 Sequence diagram
 Collaboration diagram

 State chart diagram

 Activity diagram

 Component diagram

 Deployment diagram

USE CASE DIAGRAM:

A usecase diagram in the Unified Modeling Language(UML) is atype of behavioral diagram

defined by and created from a use-case analysis.its purpose is to present a graphical overview
of the functionality provided by a system in terms of actors, their goals(represented as use
cases),and any dependencies between those use cases.

Use case diagrams are formally included in two modeling languages defined by the
OMG:theunfied modeling language(UML) and the systems modeling language(sysML)

CHAPTER 6
TESTING
6.1 INTRODUCTION TO SYSTEM TESTING:

The purpose of testing is to discover errors. Testing is the process of trying to

discover every conceivable fault or weakness in a work product. It provides a way to check
the functionality of components, sub assemblies, assemblies and/or a finished product It is the
process of exercising software with the intent of ensuring that the

Software system meets its requirements and user expectations and does not fail in an
unacceptable manner. There are various types of test. Each test type addresses a specific
testing requirement.

TYPES OF TESTING:

Unit testing:
Unit testing involves the design of test cases that validate that the internal program logic is
functioning properly, and that program inputs produce valid outputs. All decision branches
and internal code flow should be validated. It is the testing of individual software units of the
application .it is done after the completion of an individual unit before integration. This is a
structural testing, that relies on knowledge of its construction and is invasive. Unit tests
perform basic tests at component level and test a specific business process, application,
and/or system configuration. Unit tests ensure that each unique path of a business process
performs accurately to the documented specifications and contains clearly defined inputs and
expected results.

Integration testing:

Integration tests are designed to test integrated software components to determine if

they actually run as one program. Testing is event driven and is more concerned with the
basic outcome of screens or fields. Integration tests demonstrate that although the
components were individually satisfaction, as shown by successfully unit testing, the
combination of components is correct and consistent. Integration testing is specifically aimed
at exposing the problems that arise from the combination of components.

Functional test:
Functional tests provide systematic demonstrations that functions tested are available as
specified by the business and technical requirements, system documentation, and user
manuals.

Functional testing is centered on the following items:

Valid Input : identified classes of valid input must be accepted.

Invalid Input : identified classes of invalid input must be rejected.

Functions : identified functions must be exercised.

Output : identified classes of application outputs must be exercised.

Systems/Procedures: interfacing systems or procedures must be invoked.

Organization and preparation of functional tests is focused on requirements, key functions,

or special test cases. In addition, systematic coverage pertaining to identify Business process
flows; data fields, predefined processes, and successive processes must be considered for
testing. Before functional testing is complete, additional tests are identified and the effective
value of current tests is determined.

System Test:
System testing ensures that the entire integrated software system meets requirements. It
tests a configuration to ensure known and predictable results. An example of system testing
is the configuration oriented system integration test. System testing is based on process
descriptions and flows, emphasizing pre-driven process links and integration points.
White Box Testing:
White Box Testing is a testing in which in which the software tester has knowledge of the
inner workings, structure and language of the software, or at least its purpose. It is purpose.

It is used to test areas that cannot be reached from a black box level.

Black Box Testing:

Black Box Testing is testing the software without any knowledge of the inner workings,
structure or language of the module being tested. Black box tests, as most other kinds of
tests, must be written from a definitive source document, such as specification or
requirements document, such as specification or requirements document. It is a testing in
which the software under test is treated, as a black box .you cannot “see” into it. The test
provides inputs and responds to outputs without considering how the software works.

Unit Testing:

Unit testing is usually conducted as part of a combined code and unit test phase of the
software lifecycle, although it is not uncommon for coding and unit testing to be conducted
as two distinct phases.

Test strategy and approach

Field testing will be performed manually and functional tests will be written in detail.

Test objectives
 All field entries must work properly.
 Pages must be activated from the identified link.
 The entry screen, messages and responses must not be delayed.

Features to be tested
 Verify that the entries are of the correct format
 No duplicate entries should be allowed
 All links should take the user to the correct page.

Integration Testing:
Software integration testing is the incremental integration testing of two or more
integrated software components on a single platform to produce failures caused by interface
defects.

The task of the integration test is to check that components or software applications,
e.g. components in a software system or – one step up – software applications at the company
level – interact without error.

Test Results:

All the test cases mentioned above passed successfully. No defects encountered.

Acceptance Testing:
User Acceptance Testing is a critical phase of any project and requires significant
participation by the end user. It also ensures that the system meets the functional
requirements.

Test Results:

All the test cases mentioned above passed successfully. No defects encountered.

8.CONCLUSION:
In the previous system everything was happening manually. So we
have automated the process so that the information like about Placement,
Symposium reaches everyone. It increases the bond between staffs and
student it helps them to communicate with each other and students can
easily make a complaint on any issue and students can be able to see on
which stage The recovery for a problem is going on.

9. BIBLOGRAPHY

1. PHP MySQL Website Programming: Problem - Design – Solution byChris

Lea, Mike Buzzard, DilipThomas ,Jessey White-Cinis
2. Beginning PHP5, Apache, and MySQL Web Development (Programmer to
Programmer) by Elizabeth Naramore
3. MySQL/PHP Database Applications, 2nd Edition by Brad Bulger
4. How to Do Everything with PHP and MySQL by VikramVaswani

APENDIX SCREENSHOTS
LOGIN

USER ACCOUNT DETAILS

EXTRACURRICULAR ACTIVITIES
SYMPOSIUM

PLACEMENT
COMPLAINT

COUNSELLING