SAVITRIBAI PHULE PUNE UNIVERSITY

A PROJECT REPORT ON

PROJECT TITLE

SUBMITTED TOWARDS THE

PARTIAL FULFILLMENT OF THE REQUIREMENTS OF

BACHELOR OF ENGINEERING (Computer Engineering)

BY
Student Name Exam No:
Student Name Exam No:
Student Name Exam No:
Student Name Exam No:

Under The Guidance of

Prof. Guide Name

DEPARTMENT OF COMPUTER ENGINEERING

College Name
College Address

College Name
DEPARTMENT OF COMPUTER ENGINEERING
 CERTIFICATE

This is to certify that the Project Entitled

PROJECT TITLE

Submitted by

Student Name Exam No:

Student Name Exam No:
Student Name Exam No:
Student Name Exam No:
is a bonafide work carried out by Students under the supervision of Prof. Guide
Name and it is submitted towards the partial fulfillment of the requirement of Bach-
elor of Engineering (Computer Engineering).

Prof. Guide Name Prof. HOD Name

Internal Guide H.O.D
Dept. of Computer Engg. Dept. of Computer Engg.
Dr. V. V. Dixit
Principal RMD Sinhgad School of
Engineering

Signature of Internal Examiner Signature of External Examiner PROJECT

APPROVAL SHEET

A Project Title

(Project Title)

Is successfully completed by

Student Name Exam No:

Student Name Exam No:
Student Name Exam No:
Student Name Exam No:
at
 DEPARTMENT OF COMPUTER ENGINEERING

(COLLEGE NAME)

SAVITRIBAI PHULE PUNE UNIVERSITY,PUNE

ACADEMIC YEAR 2019-2020

Prof. Guide Name Prof. HOD Name

Internal Guide H.O.D
Dept. of Computer Engg. Dept. of Computer Engg.
Abstract

Please Write here One Page Abstract. It should mainly include introduction, moti-
vation,outcome and innovation if any.
 College Short Form Name, Department of Computer Engineering 2015-16 I
Acknowledgments

Please Write here Acknowledgment.Example given as

It gives us great pleasure in presenting the preliminary project report on ‘BE
PROJECT TITLE’.

I would like to take this opportunity to thank my internal guide Prof. Guide Name
for giving me all the help and guidance I needed. I am really grateful to them for
their kind support. Their valuable suggestions were very helpful.

I am also grateful to Prof. HOD Name, Head of Computer Engineering

Department, CollegeName for his indispensable support, suggestions.

In the end our special thanks to Other Person Name for providing various
resources such as laboratory with all needed software platforms, continuous
Internet connec- tion, for Our Project.

Student Name1
Student Name2
Student Name3
Student Name4
(B.E. Computer Engg.)
College Short Form Name, Department of Computer Engineering 2015-16 II

INDEX
1 Synopsis 1
1.1 Project Title . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2 Project Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.3 Internal Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.4 Sponsorship and External Guide . . . . . . . . . . . . . . . . . . . 2
1.5 Technical Keywords (As per ACM Keywords) . . . . . . . . . . . . 2
1.6 Problem Statement . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.7 Abstract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.8 Goals and Objectives . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.9 Relevant mathematics associated with the Project . . . . . . . . . . 3
1.10 Names of Conferences / Journals where papers can be published . . 3
1.11 Review of Conference/Journal Papers supporting Project idea . . . . 4
1.12 Plan of Project Execution . . . . . . . . . . . . . . . . . . . . . . . 4

2 Technical Keywords 5
2.1 Area of Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.2 Technical Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . 6

3 Introduction 7
3.1 Project Idea . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.2 Motivation of the Project . . . . . . . . . . . . . . . . . . . . . . . 8
3.3 Literature Survey . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

4 Problem Definition and scope 9

4.1 Problem Statement ............................................................................... 10
 4.1.1 Goals and
objectives .................................................................
10
4.1.2 Statement of
scope ....................................................................10
4.2 Major Constraints ..................................................................................10
4.3 Methodologies of Problem solving and efficiency issues........................10
4.4 Outcome 10
4.5 Applications ..........................................................................................11
4.6 Hardware Resources Required ...............................................................11
4.7 Software Resources Required ................................................................11

5 Project Plan 12
5.1 Project Estimates ...................................................................................13
5.1.1 Reconciled
Estimates ................................................................1
3
5.1.2 Project
Resources .................................................................
.....13
5.2 Risk Management w.r.t. NP Hard
analysis .............................................13
5.2.1 Risk
Identification ............................................................
.........13
5.2.2 Risk Analysis 14
5.2.3 Overview of Risk Mitigation, Monitoring,
Management ............15
5.3 Project Schedule ....................................................................................15
5.3.1 Project task set 15
5.3.2 Task network 16
5.3.3 Timeline Chart 16
5.4 Team Organization ................................................................................16
5.4.1 Team structure 16
5.4.2 Management reporting and
communication ...............................16
 6 Software requirement specification 17
6.1 Introduction ...........................................................................................18
6.1.1 Purpose and Scope of
Document ...............................................18
6.1.2 Overview of responsibilities of
Developer .................................18
6.2 Usage Scenario ......................................................................................18
6.2.1 User profiles 18
6.2.2 Use-cases 18

6.2.3 Use Case View . . . . . . . . . . . . . . . . . . . . . . . .

18
6.3 Data Model and Description . . . . . . . . . . . . . . . . . . . . . 19

6.3.1 Data Description . . . . . . . . . . . . . . . . . . . . . . .

19
6.3.2 Data objects and Relationships . . . . . . . . . . . . . . . .
19
6.4 Functional Model and Description .........................................................19
6.4.1 Data Flow
Diagram ...................................................................
20
6.4.2 Activity
Diagram: ..................................................................
...20
6.4.3 Non Functional
Requirements: ..................................................20
6.4.4 State Diagram: 20
6.4.5 Design
Constraints ...............................................................
.....20
6.4.6 Software Interface
Description ..................................................20
 7 Detailed Design Document using Appendix A and B 22
7.1 Introduction ...........................................................................................23
7.2 Architectural Design..............................................................................23
7.3 Data design (using Appendices A and B) ...............................................23
7.3.1 Internal software data
structure..................................................23
7.3.2 Global data
structure .................................................................2
4
7.3.3 Temporary data
structure ...........................................................24
7.3.4 Database
description ................................................................
.24
7.4 Compoent Design ..................................................................................24
7.4.1 Class Diagram 24

8 Project Implementation 26
8.1 Introduction ...........................................................................................27
8.2 Tools and Technologies Used ................................................................27
8.3 Methodologies/Algorithm Details ..........................................................27
8.3.1 Algorithm 1/Pseudo
Code .........................................................27
8.3.2 Algorithm 2/Pseudo
Code .........................................................27
8.4 Verification and Validation for Acceptance ............................................27

9 Software Testing 28
9.1 Type of Testing Used .............................................................................29

College Short Form Name, Department of Computer Engineering 2015-16 V

9.2 Test Cases and Test Results 29
10 Results 30
10.1 Screen shots 31
10.2 Outputs 31
11 Deployment and Maintenance 32
11.1 Installation and un-installation 33
11.2 User help 33
12 Conclusion and future scope 34
Annexure A References 36

Annexure B Project Planner 37

Annexure C Reviewers Comments of Paper Submitted 38
Annexure D Plagiarism Report 39
Annexure E Information of Project Group Members 40
College Short Form Name, Department of Computer Engineering 2015-16 VI

List of Figures

6.1 Use case diagram .................................................................................. 19

6.2 State transition diagram ........................................................................ 21

7.1 Architecture diagram ............................................................................ 23

7.2 Class Diagram ...................................................................................... 25
List of Tables

4.1 Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . 11

5.1 Risk Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

5.2 Risk Probability definitions [?] . . . . . . . . . . . . . . . . . . . . 14
5.3 Risk Impact definitions [?] . . . . . . . . . . . . . . . . . . . . . . 14

6.1 Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

B.1 IDEA Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

CHAPTER 1

SYNOPSIS
 1.1 PROJECT TITLE

Project Title
“Enabling Intelligent Environment by the Design of Personalized Virtual Assistant: A
Case of Smart Campus ”

1.2 PROJECT OPTION

Please mention type either industry sponsored, entrepreneur or internal project

1.3 INTERNAL GUIDE

Prof. Internal Guide Name

1.4 SPONSORSHIP AND EXTERNAL GUIDE

Please write if any sponsorship

1.5 TECHNICAL KEYWORDS (AS PER ACM KEYWORDS)

Please note ACM Keywords can be found : http://www.acm.org/about/class/ccs98-

html
Keywords:
Augmented Reality,
Smart Campus,
Convolutional Neural Network,
Recurrent,
Neural Network,
Emotional Recognition

1.6 PROBLEM STATEMENT

1. To develop Campus Virtual Assistant with Personalized options. This system provides a
simple voice response interface, without the need for users to find information in complex web
pages or app menus.
2. We implemented a smart campus virtual assistant based on SVM algorithm.
3. The virtual assistant is presented as a chatbot. Considering the popularity of mobile
phones, the chatbot is implemented as an app.

College Short Form Name, Department of Computer Engineering 2015-16 2

 1.7 ABSTRACT

Most of the current campus platforms are similar to the official website of the school.
There are not many examples presented in the form of chatbot or personal mobile
assistants.
We intend to develop Personalized chatbot combined with the campus student affairs web
page to implement humanized and personalized campus  virtual assistant. That will not
only keep the students updated about campus affairs but will also work on student’s
overall growth.

1.8 GOALS AND OBJECTIVES

• To make campus platform interactive.

• To keep student updated with the latest campus affairs.

• To help students to be self aware.

• To guide students to be time efficient.

1.9 RELEVANT MATHEMATICS ASSOCIATED WITH THE PROJECT

System Description:

• Input: Student Questions

• Output: Get Answers of student questions.

• Identify data structures, classes, divide and conquer strategies to exploit dis-
tributed/parallel/concurrent processing, constraints.

• Functions : Identify Objects, Morphisms, Overloading in functions, Func- tional

relations

• Mathematical formulation if possible

• Success Conditions: • Failure Conditions:

College Short Form Name, Department of Computer Engineering

1.10 NAMES OF CONFERENCES / JOURNALS WHERE PAPERS CAN BE
PUBLISHED

• IEEE/ACM Conference/Journal 1

• Conferences/workshops in IITs

• Central Universities or SPPU Conferences

• IEEE/ACM Conference/Journal 2

1.11 REVIEWOF CONFERENCE/JOURNAL PAPERS SUPPORTING PROJECT

IDEA

Atleast 10 papers + White papers or web references

Brief literature survey [ Description containing important description of at least 10 papers

1.12 PLAN OF PROJECT EXECUTION

College Short Form Name, Department of Computer Engineering 2015-16 4

PERT chart/ Gantt chart
A work plan is a complete accounting of how a person or grouping proposes
going about accomplishing a specific task, approaching a project. Proposed work
plan generally includes an introduction or overview of a project or job, a breakdown
of how individual project-related tasks will be accomplished, a timeline for completion
and cost projections for implementation. The above figure 4.6 shows Gantt chart
of proposed plan work this chart explain the plan of work there are total eight task.
Task 1 is study IEEE paper in 30 days, task 2 signify design of algorithm, task 3 represent
design of GUI, task 4 represent preprocessing, task 5 signify the coding, task
6 represent Implementation it require 60 days to complete a work, task 7 correspond
to Integrating modules and testing and task 8 is documentation.

College Short Form Name, Department of Computer Engineering

 CHAPTER 2

TECHNICAL KEYWORDS
2.1 AREA OF PROJECT

We implemented a smart campus virtual assistant based on SVM algorithm.

The virtual assistant is presented as a chatbot. Considering the popularity of mobile
phones, the chatbot is implemented as an app.

2.2 TECHNICAL KEYWORDS

Please note ACM Keywords can be found : http://www.acm.org/about/class/ccs98-

html

Keywords:
Augmented Reality,
Smart Campus,
Convolutional Neural Network,
Recurrent,
Neural Network,
Emotional Recognition

College Short Form Name, Department of Computer Engineering 2015-16 6

 College Short Form Name, Department of Computer Engineering

CHAPTER 3

INTRODUCTION
3.1 PROJECT IDEA

3.2 MOTIVATION OF THE PROJECT

Motivation of the Project is follow:

Currently different kinds of updates are shared on different platforms and sessions
are conducted for student’s development.
This solution gives a platform where students can receive all kind of
updates/information at a single place.
On top of that it also provides personalized tools that are there in every personality
development training.

• Review of the papers, Description , Mathematical Terms College

College Short Form Name, Department of Computer Engineering 2015-16 7

 3.3 LITERATURE SURVEY

Sr. Name of Paper title Author Advantages Disadvantages

no journal/year of name
publication

1. IEEE/2020 Enabling PO- 1)Voice-activated 1) Less Face Time.

Intelligent SHENG assistance. 2) Personality
Environment by CHIU 2)Skill Enhancing developments
the Design of Activities. tools are not
Emotionally available.
Aware Virtual
Assistant: A
Case of Smart
Campus

2. IEEE/2020 Empathic Sarada 1)Chatbots will have a 1)Multiple sentiments in one

Chatbot: Devaram clear overview of the sentence is complicated for
Emotional patient’s emotional state sentiment annotations.2)The
Intelligence for and respond accuracy may vary when a
Mental Health accordingly. patient changes appearance, or
Well-being 2)Chatbots provide the camera angle is not quite
treatment analysis for a right
patient by analyzing
their responses, whether
the treatment is causing
negative or positive
effects on the patient.

Short Form Name, Department of Computer Engineering

College Short Form Name, Department of Computer Engineering 2015-16 8

Sr. no. Name of Paper title Author Advantages Disadvantages
journal/year of name
publication

3 IEEE/2020 Health Marco 1)sufficient number 1), there is no dataset

Assistant Bot: Polignano of active available with real or
A Personal users .2)Federated synthetic information
Health learning models have that associates the
Assistant for the advantage of patient’s symptoms to
the Italian exploiting her condition.2)e
Language decentralized absence of descriptive
(virtual) databases details of symptoms
without the need of and diseases.
sharing private data
with centralized
servers.

4 IEEE/2020 Retrieval- Liang Zhang 1) Model achieves 1)lacking fluency or

Polished state-of-the-art including grammatical
Response results on the errors
Generation for Douban dialog
Chatbot dataset .

College Short Form Name, Department of Computer Engineering 2015-16 9

 CHAPTER 4
PROBLEM DEFINITION AND SCOPE
4.1 PROBLEM STATEMENT

1. To develop Campus Virtual Assistant with Personalized options. This

system provides a simple voice response interface, without the need for
users to find information in complex web pages or app menus.
2. We implemented a smart campus virtual assistant based on SVM
algorithm.
3. The virtual assistant is presented as a chatbot. Considering the popularity
of mobile phones, the chatbot is implemented as an app.

4.1.1 Goals and objectives

Goal and Objectives:

• To make campus platform interactive.
• To keep student updated with the latest campus affairs.
• To help students to be self aware.
• To guide students to be time efficient.

4.1.2 Statement of scope

• Currently different kinds of updates are shared on different platforms and sessions
are conducted for student’s development.
• This solution gives a platform where students can receive all kind of
updates/information at a single place.
• On top of that it also provides personalized tools that are there in every personality
development training.

4.2 MAJOR CONSTRAINTS

• Any constraints that will impact the manner in which the software is to be
specified, designed, implemented or tested are noted here.

Design Constraints

College Short Form Name, Department of Computer Engineering 2015-16 10

 Apache tomcat and database connectivity.

4.3 METHODOLOGIES OF PROBLEM SOLVING AND EFFICIENCY

ISSUES

Methodologies used.
We are using waterfall model for our project.

1. Requirement gathering and analysis:

In this step of waterfall we identify what are various requirements are need
for our project such are software and hardware required, database, and interfaces.

2. System Design:

In this system design phase we design the system which is easily understood for
end user i.e. user friendly.

We design some UML diagrams and data flow diagram to understand the system
flow and system module and sequence of execution.

College Short Form Name, Department of Computer Engineering 2015-16 11

3. Implementation:

In implementation phase of our project we have implemented various module

required of successfully getting expected outcome at the different module levels.

With inputs from system design, the system is first developed in small programs
called units, which are integrated in the next phase. Each unit is developed and
tested for its functionality which is referred to as Unit Testing.

4. Testing:

The different test cases are performed to test whether the project module are giving
expected outcome in assumed time.

All the units developed in the implementation phase are integrated into a system
after testing of each unit. Post integration the entire system is tested for any faults
and failures.

5. Deployment of System:

Once the functional and non-functional testing is done, the product is

deployed in the customer environment or released into the market.

6. Maintenance:

There are some issues which come up in the client environment. To fix
those issues patches are released. Also to enhance the product some better versions
are released. Maintenance is done to deliver these changes in the customer
environment.

All these phases are cascaded to each other in which progress is seen as
flowing steadily downwards like a waterfall through the phases. The next phase is
started only after the defined set of goals are achieved for previous phase and it is
signed off, so the name "Waterfall Model". In this model phases do not overlap.

College Short Form Name, Department of Computer Engineering 2015-16 12

 4.4 OUTCOME
• To develop Campus Virtual Assistant with Personalized options. This system
provides a simple voice response interface, without the need for users to find
information in complex web pages or app menus.
• We implemented a smart campus virtual assistant based on SVM algorithm.
• The virtual assistant is presented as a chatbot. Considering the popularity of mobile
phones, the chatbot is implemented as an app.

4.5 APPLICATIONS

We can use our application in college,university

4.6 HARDWARE RESOURCES REQUIRED

This section mentions the various hardwares that will be required to develop this project.

1. operating system : Windows 7

2. Processor – Intel i3/i5/i7
3. Speed – 1.1 GHz
4. RAM – 8 GB(min)
5. Hard Disk -500 GB
6. Key Board -Standard Windows Keyboard

4.7 SOFTWARE RESOURCES REQUIRED

Platform :
1.Operating System: Windows 7
2.IDE: Eclipse

3.Programming Language : Java 17

College Short Form Name, Department of Computer Engineering 2015-16 13

 CHAPTER 5

PROJECT PLAN
5.1 PROJECT ESTIMATES

5.1.1 Reconciled Estimates

5.1.1.1 Cost Estimate

The project cost can be found using any one of the model.
COCOMO-1 Model
COCOMO-2 Model
Model -1: The basic COCOMO model computes software development efforts as a
function of program size expressed in estimated lines of code.
Model-2: The intermediate COCOMO model computes software development
efforts as a function of program size and a set of cost drivers that include subjective
assessment of the product, hardware, personnel, project attributes
Model-3: The advanced COCOMO model incorporates all characteristics of the
intermediate version with an assessment of the cost drivers impact on each step of
the software engineering process. Following is the basic COCOMO -2 model.

Software A(b) B(b) C(b) D(b)

Project
Organic 2.4 1.05 2.5 0.38
Semi- 3.0 1.22 2.5 0.35

College Short Form Name, Department of Computer Engineering 2015-16 14

 detached
Embedde 3.6 1.20 2.5 0.32
d

The basic COCOMO -2 model equations take form:

E=A(b)KLOCB(b)
D=C(b)ED(b)
Where E is the effort applied in person months. D is development time in
chronological month. KLOC is estimated number of delivered lines of code for the
project. This project can be classified as Semidetached software project. The rough
estimate of number of lines of this project is 9.072k.Applying the above formula
E=3.0*(9.072)1.22
= 44.20 person- months
D=2.5* 44.35
=
9.40 months
Hence according COCOMO -2 model the time required for completion of the
project is 9 (~9.40) months.

 Cost of Project:
Equation for calculation of cost of project using COCOMO - 2 model is:
C = D * Cp
Where,
C = Cost of project
D = Duration in month
Cp= Cost incurred per person-month, Cp=Rs.5000/- (per person-month) (approx.)
C = 9 * 5000
= 45000/-
Hence according COCOMO - 2 model the cost of project is 45000/-(approx.)

5.1.1.2 Time Estimates

The time estimate of this project is approximate 11 months.

College Short Form Name, Department of Computer Engineering 2015-16 15

 5.1.2 Project Resources

Project resources [People, Hardware, Software, Tools and other resources] based
on Memory Sharing, IPC, and Concurrency derived using appendices to be
referred.

5.2 RISK MANAGEMENT W.R.T. NP HARD ANALYSIS

This section discusses Project risks and the approach to managing them.
1. In appropriate dataset -To overcome this risk we are trying to use well
organized and complete dataset.
2. Security- To overcome and improving security we use multilevel
security like access permissions of user.

5.2.1 Risk Identification

1. Have top software and customer managers formally committed to

support the project?
Ans-Not apllicable.
2. Are end-users enthusiastically committed to the project and the
system/product
to be built?
Ans-Not known at this time.
3. Are requirements fully understood by the software engineering team
and its
customers?
Ans-Yes
4. Have customers been involved fully in the definition of
requirements?
Ans-Not applicable
5. Do end-users have realistic expectations?
Ans-Not applicable
6. Does the software engineering team have the right mix of skills?
Ans-yes
7. Are project requirements stable?
Ans-Not applicable
8. Is the number of people on the project team adequate to do the job?
Ans-Not applicble
9. Do all customer/user constituencies agree on the importance of the
project and

College Short Form Name, Department of Computer Engineering 2015-16 16

on the requirements for the system/product to be built?
Ans-Not applicable

5.2.2 Risk Analysis

The risks for the Project can be analyzed within the constraints of time and quality

Impact
ID Risk Description Probability
Schedule Quality Overall
1 Correctness Low Low High High
2 Availability High Low High High

Table 5.1: Risk Table

Probability Value Description

High Probability of occurrence is > 75%
Medium Probability of occurrence is 26 − 75%
Low Probability of occurrence is < 25%

Table 5.2: Risk Probability definitions [?]

Impact Value Description

Very high > 10% Schedule impact or Unacceptable quality
High 5 − 10% Schedule impact or Some parts of the project have low
quality
Medium < 5% Schedule impact or Barely noticeable degradation in qual-
ity Low Impact on schedule or Quality can be
incorporated

Table 5.3: Risk Impact definitions [?]

5.2.3 Overview of Risk Mitigation, Monitoring, Management

Following are the details for each risk.

1. Risk Mitigation:
If a software team adopts a proactive approach to risk, avoidance is always the best
strategy. This is achieved by developing a plan for risk mitigation. To mitigate this
risk, you would develop a strategy for reducing turnover. Among the possible steps
to be taken are:

College Short Form Name, Department of Computer Engineering 2015-16 17

• Meet with current staff to determine causes for turnover (e.g., poor working
conditions, low pay, competitive job market).
• Mitigate those causes that are under your control before the project starts.
• Once the project commences, assume turnover will occur and develop techniques
to ensure continuity when people leave.
• Organize project teams so that information about each development activity is
widely dispersed.
• Define work product standards and establish mechanisms to be sure that all
models and documents are developed in a timely manner.
• Conduct peer reviews of all work (so that more than one person is “up to speed”).
• Assign a backup staff member for every critical technologist.
2. Risk Monitoring
As the project proceeds, risk-monitoring activities commence. The project manager
monitors factors that may provide an indication of whether the risk is becoming
more or less likely. In the case of high staff turnover, the general attitude of team
members based on project pressures, the degree to which the team has jelled,
interpersonal relationships among team members, potential problems with
compensation and benefits, and the availability of jobs within the company and
outside it are all monitored.

3. Risk Management
Risk management and contingency planning assumes that mitigation efforts have
failed and that the risk has become a reality. Continuing the example, the project is
well under way and a number of people announce that they will be leaving. If the
mitigation strategy has been followed, backup is available, information is
documented, and knowledge has been dispersed across the team. In addition, you
can temporarily refocus resources (and readjust the project schedule) to those
functions that are fully staffed, enabling newcomers who must be added to the team
to “get up to speed.” Those individuals who are leaving are asked to stop all work
and spend their last weeks in “knowledge transfer mode.” This might include
video-based knowledge capture, the development of “commentary documents or
Wikis,” and/or meeting with other team members who will remain on the project.

College Short Form Name, Department of Computer Engineering 2015-16 18

 5.3 PROJECT SCHEDULE

5.3.3 Timeline Chart

The project plan uptil the design phase over the course of 12 weeks is shown in Figure 1.1.
The phases of the project are color coded in the figure. The group formation, domain
submission, title submission, title finalisation and the one page proposal submission was in
done by the sixth week. Later, the Problem Statement and Objectives were finalised in the
next week. The Literature Review with the reference papers and designing the system
architecture was done by the end of the ninth week. After that, the model diagrams were
designed and the report was completed by the end of the twelth week.

Fig. Project

College Short Form Name, Department of Computer Engineering 2015-16 19

Month Phase Name of Work done
Scheduled Group
Members

June-August Topic Topic Searched

searching

August- Topic Topic Selected

September selection

August- Project Project Confirmed

September confirmation

August- Literature Sur- Literature Sur-

September
Vey vey Done

September- Requirement Requirement

October
Analysis Analysis Done

September- Requirement Requirements

October
Gathering Gathered

5.4 TEAM ORGANIZATION

Team consists of 4 members and proper planning mechanism is used
and roles of each member are defined.

College Short Form Name, Department of Computer Engineering 2015-16 20

5.4.1 Team structure
The team structure for the project is identified. There are total 4
members in our team and roles are defined. All members are
contributing in all the phases of project.

November- Designing Architecture

December Design

November- Designing GUI Tested

December Test

November- Database Database

December Creation Tested

January- Coding Coded

February Different
modules

January- Database And Connectivity

February Modules Done
Connectivity

March Testing of Project

project Tested

April Result Result

Analysis Analysis

5.4.2 Management reporting and communication

Well planning mechanisms are used for progress reporting and inter/intra team
communication are identified as per requirements of the project.

College Short Form Name, Department of Computer Engineering 2015-16 21

 CHAPTER 6
SOFTWARE REQUIREMENT
SPECIFICATION
6.1 INTRODUCTION

6.1.1 Purpose and Scope of Document

Most of the current campus platforms are similar to the official website of the
school. There are not many examples presented in the form of chatbot or personal
mobile assistants.
We intend to develop Personalized chatbot combined with the campus student
affairs web page to implement humanized and personalized campus  virtual
assistant. That will not only keep the students updated about campus affairs but will
also work on student’s overall growth.

6.1.2 Overview of responsibilities of Developer

1. To have understanding of the problem statement.

2. To know what are the hardware and software requirements of proposed system.
3. To have understanding of proposed system.
4. To do planning various activities with the help of planner.
5. Designing, programming, testing etc.

6.2 USAGE SCENARIO

This section provides various usage scenarios for the system to be developed.

6.2.1 Use Case View

Use Case Diagram. Example is given below

 Fig 6.2. Use Case Diagram

6.3 DATA MODEL AND DESCRIPTION

6.3.1 Data Description

Data objects that will be managed/manipulated by the software are described in this
section. The database entities or files or data structures required to be described.
For data objects details can be given as below

6.3.2 Data objects and Relationships

Data objects and their major attributes and relationships among data objects are de-
scribed using an ERD- like form.

College Short Form Name, Department of Computer Engineering 2015-16 23

6.4 FUNCTIONAL MODEL AND DESCRIPTION

A description of each major software function, along with data flow (structured
anal- ysis) or class hierarchy (Analysis Class diagram with class description for
object oriented system) is presented.

6.4.1 Data Flow Diagram

6.4.1.1 Level 0 Data Flow Diagram

6.4.1.2 Level 1 Data Flow Diagram

College Short Form Name, Department of Computer Engineering 2015-16 24

6.4.1.3 Level 2 Data Flow Diagram

6.4.2 Activity Diagram:

• The Activity diagram represents the steps taken.

College Short Form Name, Department of Computer Engineering 2015-16 25

6.4.3 Non Functional Requirements:

 Interface Requirements

User Interfaces
User interface of this program is the common windows interface, nothing additional
is required. The Development of “Enabling Intelligent Environment by the Design

College Short Form Name, Department of Computer Engineering 2015-16 26

 of Personalized Virtual Assistant: A Case of Smart” 99.9% of all new users are able
to use this application.

Hardware Interfaces
The hardware should have following specifications:

 Ability to read gallery

 Ability to exchange data over network
 Touch screen for convenience
 Keypad (in case touchpad not available)
 Continuous power supply
 Ability to connect to network
 Ability to take input from user
 Ability to validate user

Software Interfaces
The software interfaces are specific to the target other user’s Development of
“Enabling Intelligent Environment by the Design of Personalized Virtual Assistant:
A Case of Smart Campus” based on Machine Learning Approach software systems.

 Performance Requirements

System can produce results faster on 4GB of RAM.

It may take more time for peak loads at main node.

The system will be available 100% of the time. Once there is a fatal error, the
system will provide understandable feed back to the user.

 Safety Requirements
Only administrators have access to the database of each individual user.

College Short Form Name, Department of Computer Engineering 2015-16 27

 All data will be backed-up every day automatically and also the system
administrator can backup the data as a function for him.
This makes it easier to install and updates new functionality if required.
For the safety purpose backup of the database must be required.

 Software Quality Attributes

The system considers following non-functional requirements to provide better
functionalities and usage of system.

1. Availability: The system shall be available during 24 hours of a day.

2. Usability: The system is designed keeping in mind the usability issues

considering the end-users who are developers/programmers. It provides detailed
help which would lead to better and faster learning. Navigation of system is easy.

3. Consistency: Uniformity in layout, screens, Menus, colors scheme, format.

4. Performance: The performance of the system should be fast and as per user
requirement. From this system we will get expected outcome in less time and less
space since efficiency is higher. Speed is totally depending on the response of the
database and connection type.

5. Extendibility: Prevention in the system should be done in the system by which we

make changes in the system later on.

6. Reusability: Files of any type can be used by the system for any number of times
during transformation.

7. Reliability: Protection of data from malicious attack or unauthorized access.

8. Security: The system provides security to the randomly generated private key by
performing encryption to it for encrypting patient data and thus protects from other
nodes in the network.

The network is free from malicious node and misbehaving node attacks.

College Short Form Name, Department of Computer Engineering 2015-16 28

9. Reliability: Our system can provide user an efficient search each time. So the user
can reliable on the system. Because system can guarantee user to provide his/her
interested data every time in least amount of time.

6.4.4 State Diagram:

6.4.5 Design Constraints

Any design constraints that will impact the subsystem are noted.

Design constraints: Apache tomcat and database connectivity.

6.4.6 Software Interface Description

The software interfaces are specific to the target other user’s Development of
“Enabling Intelligent Environment by the Design of Personalized Virtual Assistant:
A Case of Smart Campus ” based on Machine Learning Approach software systems.

College Short Form Name, Department of Computer Engineering 2015-16 29

 Figure 6.2: State transition diagram

College Short Form Name, Department of Computer Engineering 2015-16 30

 CHAPTER 7
DETAILED DESIGN DOCUMENT USING
APPENDIX A AND B
7.1 INTRODUCTION
Most of the current campus platforms are similar to the official
website of the school. There are not many examples presented in the
form of chatbot or personal mobile assistants.
We intend to develop Personalized chatbot combined with the
campus student affairs web page to implement humanized and
personalized campus  virtual assistant. That will not only keep the
students updated about campus affairs but will also work on
student’s overall growth.

7.2 ARCHITECTURAL DESIGN

A description of the program architecture is presented. Subsystem design or Block

diagram,Package Diagram,Deployment diagram with description is to be presented.

College Short Form Name, Department of Computer Engineering 2015-16 31

 Figure 7.1: Architecture diagram

7.3 DATA DESIGN (USING APPENDICES A AND B)

A description of all data structures including internal, global, and temporary data
structures, database design (tables), file formats.

7.3.1 Internal software data structure

When SQLite/ SQL returns the results of the query sent to it by XML And JAVA,
the results of the query will be passed back to XML using the built in data
structures.
7.3.2 Global data structure

We are not using any global data structures at this time.

7.3.3 Temporary data structure
 We will be using a cookie saved on the users machine to temporarily store the users
query entry. This is so the user can go back to the query page and easily modify
their last query to refine or widen their search as needed.

7.3.4 Database description

A database will be used to store all of the user data. The database is made up of no of
tables.

7.4 COMPOENT DESIGN

7.4.1 Class Diagram

College Short Form Name, Department of Computer Engineering 2015-16 24

College Short Form Name, Department of Computer Engineering 2015-16 33

Figure 7.2: Class Diagram
 CHAPTER 8

PROJECT IMPLEMENTATION
8.1 INTRODUCTION
Most of the current campus platforms are similar to the official website of the
school. There are not many examples presented in the form of chatbot or personal
mobile assistants.
We intend to develop Personalized chatbot combined with the campus student
affairs web page to implement humanized and personalized campus  virtual
assistant. That will not only keep the students updated about campus affairs but will
also work on student’s overall growth.

8.2 TOOLS AND TECHNOLOGIES USED

1. Eclipse:

 Eclipse is an open source community whose projects building tools and frameworks
are used for creating general purpose application. The most popular usage of Eclipse
is as a Java development environment .

 Eclipse is an open source community, whose projects are focused on building an

open development platform comprised of extensible frameworks, tools and runtimes
for building, deploying and managing software across the lifecycle. The Eclipse
Foundation is a not-for-profit, member supported corporation that hosts the Eclipse
projects and helps cultivate both an open source community and an ecosystem of
complementary products and services.
 The Eclipse Project was originally created by IBM in November 2001 and
supported by a consortium of software vendors. The Eclipse Foundation was created
in January 2004 as an independent not-for-profit corporation to act as the steward of
the Eclipse community. The independent not-for-profit corporation was created to
allow a vendor neutral and open, transparent community to be established around
Eclipse. Today, the Eclipse community consists of individuals and organizations
from a cross section of the software industry.

Feature Highlights
JDK 7 
 Project Coin support
 Editor enhancements: Code completion, hints
College Short Form Name, Department of Computer Engineering 2015-16 35
 8.3 METHODOLOGIES/ALGORITHM DETAILS

8.3.1 Algorithm 1/Pseudo Code

Support Vector Machine (SVM)-
• SVM or Support Vector Machine is a linear model for classification and regression
problems. It can solve linear and non-linear problems and work well for many
practical problems.
• The idea of SVM is simple: The algorithm creates a line or a hyperplane which
separates the data into classes.
• They’re accurate in high dimensional spaces; and, they use a subset of training
points in the decision function (called support vectors), so it’s also memory
efficient.

“Support Vector Machine” (SVM) is a supervised machine learning algorithm that

can be used for both classification or regression challenges. However,  it is mostly
used in classification problems. In the SVM algorithm, we plot each data item as a
point in n-dimensional space (where n is a number of features you have) with the
value of each feature being the value of a particular coordinate. Then, we perform
classification by finding the hyper-plane that differentiates the two classes very
well.

Steps of SVM algorithm

Step 1: Import the dataset.
Step 2: Explore the data to figure out what they look like.
Step 3: Pre-process the data.
Step 4: Split the data into attributes and labels.
Step 5:Divide the data into training and testing sets.
Step 6: Train the SVM algorithm.
Step 7: Make some predictions.

8.4 VERIFICATION AND VALIDATION FOR ACCEPTANCE

Verification and validation are independent procedures that are used together for
checking that a product, service, or system meets requirements and specifications
and that it fulfills its intended purpose. These are critical components of a quality
management system such as ISO 9000. The words “verification” and”validation”
are sometimes preceded with”independent”, indicating that the verification and
validation is to be performed by a disinterested third party. ”Independent
verification and validation” can be abbreviated as”IV and V”.
”Validation The assurance that a product, service, or system meets the needs of the
customer and other identified stakeholders. It often involves acceptance and
suitability with external customers. Contrast with verification.”
”Verification The evaluation of whether or not a product, service, or system
complies with a regulation, requirement, specification, or imposed condition. It is
often an internal process. Contrast with validation.”

College Short Form Name, Department of Computer Engineering 2015-16 37

 CHAPTER 9

SOFTWARE TESTING
9.1 TYPE OF TESTING USED
GUI Testing:
Test case Login Screen- Sign up

Objective Click on sign up button then check all required/ mandatory fields
with leaving all fields blank

Expected All required/ mandatory fields should display with symbol “*”.
Result Instruction line “* field(s) are mandatory” should be displayed

Test case Create a Password >>Text Box

Confirm Password >>Text Box

Objective Check the validation message for Password and Confirm Password
field

Expected Correct validation message should be displayed accordingly or

Result “Password and confirm password should be same” in place of
“Password mismatch”.

9.2 TEST CASES AND TEST RESULTS

Test case Display Menu
Objective Click on On Off Button
Expected It will give menu Various Option
Result
Login test case

Test Case ID Test Case Test Case I/P Actual Result Expected Test case
Result criteria(P/F)
001 Enter The Username or Error comes Error Should P
Wrong password come
username or
password
click on
submit button
002 Enter the Accept Accept P
correct Username and
username and password
password
click on
submit button
Registration test case

Test Case ID Test Case Test Case I/P Actual Expected Test case
Result Result criteria(P/F)
001 Enter the Number Error Comes Error Should P
number in Comes
username,
middle name,
last name
field
001 Enter the Character Accept Accept p
character in
username,
middle name,
last name
field
002 Enter the Kkgmail,com Error comes Error Should P
invalid email Comes
id format in
email id field
002 Enter the valid kk@gmail.com Accept Accept P
email id
format in
email id field
003 Enter the 99999 Error comes Error Should P
invalid digit Comes
no in phone
no field
003 Enter the 10 9999999999 Accept Accept P
digit no in
phone no field

College Short Form Name, Department of Computer Engineering 2015-16 39

 CHAPTER 10

RESULTS
10.1 SCREEN SHOTS

Outputs / Snap shots of the results

10.2 OUTPUTS

Outputs / Snap shots of the results

 CHAPTER 11

DEPLOYMENT AND MAINTENANCE

11.1 INSTALLATION AND UN-INSTALLATION
We need to install following software’s to execute our project,
•Eclipse Kepler
•Xampp Control panel
•Jdk 7.1
•Windows 32 bit Windows 7 and on words OS

Eclipse Installation
•Unzip eclipse-SDK-4.3-win32.zip, the file that you just downloaded
and moved.
•Create a shortcut on your desktop to the eclipse.exe file in this eclipse
folder
•Double-click the shortcut to Eclipse that you just created above
•Click OK

1.Steps to create dynamic web project.

Step 1 :Create a Java EE 6 Web Project We start by creating a new Java
EE 6 dynamic web project in Eclipse:
•Open the [New Project] dialog box, e.g. by using File>New>Project...
•Select Web>Dynamic Web Project and click Next.
•Choose a Project Name (e.g. Guestbook).

Step 2: Entity Class and Persistence Unit

College Short Form Name, Department of Computer Engineering 2015-16 41

To store objects in an ObjectDB database using JPA we need to define
an entity class:
•Open the [New Java Class] dialog box, e.g. by right clicking the
project node
(in the [Package Explorer] window) and selecting New>Class.
•Enter guest as the package name use exactly that case sensitive
package name.
•Enter Guest as the class name use exactly that case sensitive class
name.
•Click Finish to create the new class.

Step 3: Add a Servlet Class

In this step we will add a servlet to manage guestbook web requests:
•Open the [Create Servlet] dialog box by right clicking the guest
package node
(in the [Package Explorer] window), selecting
New>Other...>Web>Servlet and clicking Next.
•The Java package name should be guest.
•Enter GuestServlet as the class name use exactly that case sensitive
class name.
•Click Finish to create the new servlet class.
Step 5: Add a JSP Page
In this step we will add the JSP that generates the guest book page
output:–Open the [New JSP File] dialog box by right clicking the
WebCon-
tent node (in the [Package Explorer] window), selecting
New>Other...>Web>JSP File and clicking Next.–Enter guest as the jsp
file name use exactly that case sensitive class name.–Click Finish to
create the new JSP file.
•The Java package name should be guest.
•Enter GuestServlet as the class name use exactly that case sensitive
class name.
•Click Finish to create the new servlet class.

Step 5: Add a JSP Page

In this step we will add the JSP that generates the guestbook page
output–Open the [New JSP File] dialog box by right clicking the
WebContent node (in the [Package Explorer] window), selecting
New>Other...>Web> JSP File and clicking Next.–Enter guest as the jsp
file name use exactly that case sensitive class name.–Click Finish to
create the new JSP file.

Step 6: Run the Java EE 6 Application

You can run the application now by right clicking the GuestServlet node
(in
the [Project Explorer] window) and selecting Run As>Run on
Server>Finish:

MySQL:
MySQL, the most popular Open Source SQL database manage-ment system, is
developed, distributed, and supported by Oracle Corporation.The MySQL Web site
(http://www.mysql.com/) provides the latest information about MySQL software.
1.MySQL is a database management system.
A database is a structured collection of data. It may be anything from a simple
shopping list to a picture gallery or the vast amounts of information in a corporate
network. To add, access, and process data stored in a computer database,you need a
database management system such as MySQL Server. Since computers are very
good at handling large amounts of data, database management systems play a
central role in computing, as standalone utilities, or as parts of
other applications.

College Short Form Name, Department of Computer Engineering 2015-16 43

2.MySQL databases are relational.
A relational database stores data in separate tables rather than putting all the data in
one big storeroom. The database structures are organized into physicalfiles
optimized for speed. The logical model, with objects such as databases,tables,
views, rows, and columns, offers a flexible programming environment.You set up
rules governing the relationships between different data fields, such as one-to-one,
one-to-many, unique, required or optional, and pointers between different tables.
The database enforces these rules, so that with a well-designed database, your
application never sees inconsistent, duplicate, orphan, out of date, or missing data.
The SQL part of MySQL stands for Structured Query Language. SQL is the most
common standardized languageused to access databases. Depending on your
programming environment, you might enter SQL directly (for example, to generate
reports), embed SQL statements into code written in another language, or use a
language-specific API that hides the SQL syntax. SQL is defined by the ANSI/ISO
SQL Standard. The SQL standard has been evolving since 1986 and several
versions exist. In this manual, SQL-92 refers to the standard released in 1992,
SQL:1999 refers
to the standard released in 1999, and SQL:2003 refers to the current version of the
standard. We use the phrase the SQL standard to mean the current version of the
SQL Standard at any time.
3.MySQL software is Open Source.
Open Source means that it is possible for anyone to use and modify the software.
Anybody can download the MySQL software from the Internet and use it without
paying anything. If you wish, you may study the source code and change it to suit
your needs. The MySQL software uses the GPL (GNU General Public License),
http://www.fsf.org/licenses/, to define what you may and may not do with the
software in different situations. If you feel uncomfortable with the GPL or need to
embed MySQL code into a commercial application, you can buy a commercially
licensed version from us.
4.The MySQL Database Server is very fast, reliable, scalable, and easy to use. If
that is what you are looking for, you should give it a try. MySQL Server can run
comfortably on a desktop or laptop, alongside your other applications, web servers,
and so on, requiring little or no attention. If you dedicate an entire machine to
MySQL, you can adjust the settings to take advantage of all the memory, CPU
power, and I/O capacity available. MySQL can also scale up to clusters of
machines, networked together. You can find a performance comparison of MySQL
Server with other database managers on our benchmark page.
MySQL Server was originally developed to handle large databases much faster than
existing solutions and has been successfully used in highly demandingproduction
environments for several years. Although under constant development, MySQL
Server today offers a rich and useful set of functions. Its connectivity, speed, and
security make MySQL Server highly suited for accessingdatabases on the Internet.
5.MySQL Server works in client/server or embedded systems.The MySQL
Database Software is a client/server system that consists of amulti-threaded SQL
server that supports different backends, several different client programs and
libraries, administrative tools, and a wide range of application programming
interfaces (APIs). We also provide MySQL Server as an embedded multi-threaded
library that you can link into your application to geta smaller, faster, easier-to-
manage standalone product. A large amount of contributed MySQL software is
available.MySQL Server has a practical set of features developed in close
cooperation
with our users. It is very likely that your favorite application or language sup-
ports the MySQL Database Server.

College Short Form Name, Department of Computer Engineering 2015-16 45

 CHAPTER 12

CONCLUSION AND FUTURE SCOPE

We have implemented a Personalized smart campus virtual assistant. In this study, we
implemented a smart campus virtual assistant based on Support Vector Machine. This study
can achieve a maximum accuracy of 95.6% in short sentence emotion recognition. With
guided questions and Chinese Word Embedding, Chatbot can correctly answer students’
topics about campus maps, classroom configuration, surrounding dining and basic school
affairs, and can provide basic contextual dialogue based on the user’s emotions. This
research can be applied to AR virtual campus navigation, friendly campus applications, and
advanced school affairs applications.
In the future, combined with a personalized voice assistant, with campus administration,
school affairs and sensors distributed throughout the campus, replacing the official website
or app with a virtual campus assistant will no longer be out of reach.
ANNEXURE A REFERENCES

[1] Y.-B. Lin, L.-K. Chen, M.-Z. Shieh, Y.-W. Lin, and T.-H. Yen, ‘‘CampusTalk:
IoT devices and their interesting features on campus applications,’’ IEEE Access,
vol. 6, pp. 26036–26046, 2018.
[2] eMarketer Mobile Taiwan: A Look at a Highly Mobile Market. Country Has the
Highest Smartphone Penetration in the World. [Online]. Available:
https://www.emarketer.com/Article/Mobile-TaiwanLook-Highly-Mobile-Market/
1014877?ecid=NL1007
[3] X. Xu, D. Li, M. Sun, S. Yang, S. Yu, G. Manogaran, G. Mastorakis, and C. X.
Mavromoustakis, ‘‘Research on key technologies of smart campus teaching
platform based on 5G network,’’ IEEE Access, vol. 7, pp. 20664–20675, 2019. [4]
National Communications Commission. 3G/4G Mobile Communication Market
Statistics. [Online].Available:http://www.ncc.gov.tw/chinese/news.aspx?
site_content_sn=3773&is_history=0
[5] Department of Statistics, Taiwan. [Online]. Available: https://stats.moe. gov.tw/
[6] J. W. P. Ng, N. Azarmi, M. Leida, F. Saffre, A. Afzal, and P. D. Yoo, ‘‘The
intelligent campus (iCampus): End-to-end learning lifecycle of a knowledge
ecosystem,’’ in Proc. 6th Int. Conf. Intell. Environ., Jul. 2010, pp. 332–337.
[7] IBM. (2016). Building a Smarter Campus: How Analytics is Changing the
Academic Landscape. [Online]. Available: https://ftp.software.
ibm.com/la/documents/gb/mx/Building_a_Smarter_Campus.pdf
[8] Forward-Looking Infrastructure Project. [Online]. Available: https://www.
ndc.gov.tw/cp.aspx?n=608FE9340FE6990D&s=F30C1215990A560F
[9] M. W. Sari, P. W. Ciptadi, and R. H. Hardyanto, ‘‘Study of smart campus
development using Internet of Things technology,’’ IOP Conf. Ser., Mater. Sci.
Eng., vol. 190, Apr. 2017, Art. no. 012032.
[10] X. Zhai, Y. Dong, and J. Yuan, ‘‘Investigating Learners’ technology
Engagement—A perspective from ubiquitous game-based learning in smart
campus,’’ IEEE Access, vol. 6, pp. 10279–10287, 2018.
[11] W. Zhang, X. Zhang, and H. Shi, ‘‘MMCSACC: A multi-source multimedia
conference system assisted by cloud computing for smart campus,’’ IEEE Access,
vol. 6, pp. 35879–35889, 2018.
[12] S. I. Popoola, A. A. Atayero, J. A. Badejo, T. M. John, J. A. Odukoya, and D.
O. Omole, ‘‘Learning analytics for smart campus: Data on academic performances
of engineering undergraduates in nigerian private university,’’ Data Brief, vol. 17,
pp. 76–94, Apr. 2018.

College Short Form Name, Department of Computer Engineering 2015-16 47

 ANNEXURE B
PROJECT PLANNER

PERT chart/ Gantt chart

A work plan is a complete accounting of how a person or grouping proposes
going about accomplishing a specific task, approaching a project. Proposed work
plan generally includes an introduction or overview of a project or job, a breakdown
of how individual project-related tasks will be accomplished, a timeline for
completion
and cost projections for implementation. The above figure 4.6 shows Gantt chart
of proposed plan work this chart explain the plan of work there are total eight task.
Task 1 is study IEEE paper in 30 days, task 2 signify design of algorithm, task 3
represent
design of GUI, task 4 represent preprocessing, task 5 signify the coding, task
6 represent Implementation it require 60 days to complete a work, task 7 correspond
to Integrating modules and testing and task 8 is documentation.
College Short Form Name, Department of Computer Engineering 2015-16 49
 ANNEXURE C
REVIEWERS COMMENTS OF PAPER
SUBMITTED
 (At-least one technical paper must be submitted in Term-I on the project design
in the conferences/workshops in IITs, Central Universities or UoP Conferences or

equivalent International Conferences Sponsored by IEEE/ACM) 1. Paper Title: 2. Name

of the Conference/Journal where paper submitted :
3. Paper accepted/rejected :
4. Review comments by reviewer :

5. Corrective actions if any :

 ANNEXURE D

PLAGIARISM REPORT
Plagiarism report
 ANNEXURE E
INFORMATION OF PROJECT GROUP
MEMBERS
one page for each student .

College Short Form Name, Department of Computer Engineering 2015-16

 51

photo.jpg

1. Name :

2. Date of Birth : 3. Gender :

4. Permanent Address :
5. E-Mail :
6. Mobile/Contact No. :
7. Placement Details :
8. Paper Published :

45

College Short Form Name, Department of Computer Engineering 2015-16

 45

College Short Form Name, Department of Computer Engineering 2015-16