BTI/B Tech/MBA Tech

Minor Project/Capstone Project

GUIDELINES
AND
REPORT FORMATS

PAGE 1
 Mukesh Patel School of Technology Management and Engineering
SVKMs NMIMS University

Table of contents
Topics Page No.

1. Introduction to the course 3

1.1 Preamble 3

1.2 Course Objective 3

1.3 Prerequisite 3

2. Course Outcomes (CO) and mapping with Program Outcomes (PO) 3

2.1 Course Outcomes (CO) 3

2.2 Program Outcomes (PO) 3

2.3 CO-PO Mapping 4

3. Teaching and evaluation scheme 4

4. Guidelines for the project and review process 5

4.1 Finalization of the project teams and domains 5

4.2 Project guidance and review time lines 6

5. Assessment Policy 6

5.1 Component wise Continuous Evaluation Internal Continuous Assessment (ICA) 6

5.2 Rubrics for fortnightly progress review 7

Annexures 12

A.1 Project registration form 13

A.2 Topic approval form 14

A.3 Evaluation sheet for Review 1: Topic approval and feasibility 16

A.4 Evaluation sheet for Review 2: Midterm review 17

A.5 Evaluation sheet for Review 3: External Panel Member Evaluation 18

A.6 Evaluation sheet for Review 3: Internal Project mentor Evaluation 19

A.7 Log Book format 20

A.8 Report Format 22

PAGE 2
1 Introduction to the Course

1.1 Preamble

The capstone project aims to provide practical design experience to the students. It will also help the students to
acquire the required skill sets in their professional careers. The project guidelines are framed to apprise the
students about the procedures to be followed and the expectations to be met. The project guidelines will help
supervisors and examiners in evaluation of the project work.

1.2 Course objective

The capstone project is designed to consolidate the learning of the final year students with a hands-on experience.
ABET defines a capstone design experience as "a culminating major engineering design experience that 1)
incorporates appropriate engineering standards and multiple constraints, and 2) is based on the knowledge and
skills acquired in earlier course work. The capstone design course is used to assess the ability to identify,
formulate, and solve complex engineering problems, and apply engineering design using ethical and professional
responsibilities in engineering situations and working effectively in a team.

1.3 Pre-requisite

 Knowledge of all core and elective courses completed till 3rd year.

2 Course Outcomes (CO) and mapping with Program Outcomes (PO)

2.1 Course Outcomes

After successful completion of the course, a student will be able to -

1. Select an appropriate problem statement after reviewing the literature and identifying the research gaps.
2. Formulate a feasible design model.
3. Implement the prototype/proof of concept, test and validate the results.
4. Work efficiently in a team environment.
5. Summarize the findings into a technical report.

2.2 Program Outcomes

Engineering Graduates will be able to:

1. Engineering knowledge: Apply the knowledge of mathematics, science, engineering fundamentals, and an
engineering specialization to the solution of complex engineering problems.
2. Problem analysis: Identify, formulate, review research literature, and analyze complex engineering problems
reaching substantiated conclusions using first principles of mathematics, natural sciences, and engineering sciences.
3. Design/development of solutions: Design solutions for complex engineering problems and design system
components or processes that meet the specified needs with appropriate consideration for the public health and safety,
and the cultural, societal, and environmental considerations.
4. Conduct investigations of complex problems: Use research-based knowledge and research methods including design
of experiments, analysis and interpretation of data, and synthesis of the information to provide valid conclusions.
5. Modern tool usage: Create, select, and apply appropriate techniques, resources, and modern engineering and IT
tools including prediction and modelling to complex engineering activities with an understanding of the limitations.
6. The engineer and society: Apply reasoning informed by the contextual knowledge to assess societal, health, safety,
legal and cultural issues and the consequent responsibilities relevant to the professional engineering practice.

PAGE 3
7. Environment and sustainability: Understand the impact of the professional engineering solutions in societal and
environmental contexts, and demonstrate the knowledge of, and need for sustainable development.
8. Ethics: Apply ethical principles and commit to professional ethics and responsibilities and norms of the engineering
practice.
9. Individual and team work: Function effectively as an individual, and as a member or leader in diverse teams, and
in multidisciplinary settings.
10. Communication: Communicate effectively on complex engineering activities with the engineering community and
with society at large, such as, being able to comprehend and write effective reports and design documentation, make
effective presentations, and give and receive clear instructions.
11. Project management and finance: Demonstrate knowledge and understanding of the engineering and management
principles and apply these to one’s own work, as a member and leader in a team, to manage projects and in
multidisciplinary environments.
12. Life-long learning: Recognize the need for, and have the preparation and ability to engage in independent and life-
long learning in the broadest context of technological change.

2.3 CO-PO mapping

PO1 PO2 PO3 PO4 PO5 PO6 PO7 PO8 PO9 PO10 PO11 PO12

CO1 3 3 1 2 2 2 1 1

CO2 2 3 3 2 2 1 2 2 2 1 2 1

CO3 2 3 3 3 3 1 2 1 2 2 2

CO4 1 1 1 3 1 3

CO5 3 1 3 3

3 Teaching and evaluation scheme

Semester VI for BTI programs

Semester VII for all B Tech Programs except B Tech CSE (Data Science) 311 program

Semester VIII for all MBA Tech Programs

Teaching Scheme Evaluation Scheme

Tutorial Internal Continuous Term End
Lecture Practical
Hours Assessment Examinations
Hours per Hours per Credit
per (ICA) (TEE)
week week
week (Marks -50) (Marks - 50)
Presentation and
Viva
0 8 0 4 Marks Scaled to 50
Marks Scaled to
50

PAGE 4
 4 Guidelines and review process

4.1 Finalization of the project teams and domains

The orientation of the minor project/capstone project, finalizing the project teams and allocation of the mentors is
to be completed in the prior semester i.e. semester V/VI/VII as applicable.

Table 4.1.1: Time line for finalization of Capstone project teams and mentors

Week No Activity Responsibility and roles

 Department project coordinators.
 To introduce the significance, time lines and the
10th week of
expectations of the capstone project as a part of their
prior semester
Project curriculum.
(semester
Orientation-I  Each group will be of maximum 2-3 students.
V/VI/VII as
applicable)  The students should be made aware of the assessment and
evaluation policies and the implications of not following
the same.
 Students to form project group consisting of 2 to 3 students.
 The students to submit the following:
11th week of Submission  Project group details (Interdisciplinary project groups will
prior semester of project be permitted based on the problem statement and scope of
(semester groups and the project with the approval of the dean)
VI/VII as three broad  At least three broad domains in which they intend to work
applicable) domains for their capstone project.
 The submission of the group details and domains to be done as
per the template given in annexure.
12th week of Finalization  Department project coordinators in consultation with the head
prior semester and approval of the department or a committee formed at department level.
(semester of Project
VI/VII as Teams and
applicable) Mentors
13th week of Mentor  Department project coordinators
prior semester Allocation to
(semester be informed
VI/VII as to the
applicable) students
 The project groups to have the first meeting with their
respective mentors.
 Agenda for the meeting:
 Briefing to the students about the capstone project and the
14th week of
expectations and requirements by the mentor.
prior semester Project idea
 Discussion on the broad domain/ideas submitted by the
(semester discussion
students and expected outcomes
VI/VII as with Mentors
applicable)  Action points for the next meeting at the start of the
semester:
 Literature review on the ideas/problem statement.
 Determine research gaps
 Prepare a brief synopsis on the finalized topic.

PAGE 5
 4.2 Project guidance and review time lines

1. The students are expected to meet with the faculty mentor every week (semester VI/VII/VIII as applicable)
and update about the work done. Record of the proceeding to be maintained.
2. The faculty mentor is expected to review and evaluate the work done and give suggestions for further work.
3. A google sheet will be maintained by the department project coordinators for recording the status and updates
about the weekly interactions of the project groups and mentors and the grading for every week.
4. Student’s Project Progress would be reviewed three times during the entire semester as per the academic
calendar.
5. A separate schedule for submission for various reports is enclosed (Annexure). The student must strictly
observe the submission date, while sending reports.
6. For all the project reviews, it is the sole responsibility of the student to report to his faculty mentor, and to
make a presentation regarding the project progress in front of the panel of faculty members, which includes
the project guide.
7. During all reviews students should represent all technical specification and data of the project. The
presentation should be complete in all respect as per the templates given in Annexure to grade it.
8. Any deviation/noncompliance should be reported by the mentor in time to the HoD/Dean.

Table 4.2.1: Minor Project/Capstone project review timelines

Sr. No. Review Timeline

1st review Topic approval and feasibility 2nd week of semester VI/VII/VIII for BTI/B
Tech/MBA Tech
2nd review Midterm review 7th week of the semester (after midterm test 1)
3rd review Final presentation and viva Last week of the semester

5 Assessment Policy

5.1 Component wise Continuous Evaluation Internal Continuous Assessment (ICA)

ICA (50 Marks) Final Presentation and Viva

Assessment (Internal + External)

Component
1st review 2nd review Fortnight progress review (3rd review)

Weightage 10% 25% 15% 50%

Marks 10 25 15 (Fortnightly graded out 50

of 10. Scaled to 15 at the
end of the semester.)

PAGE 6
5.2 Progress review

All the project team members must meet the faculty mentor regularly and update them about the progress. An
individual team member’s contribution will be ascertained using different tools.

Continuous assessment of the project work will be carried out based on the fortnightly performance, discussions
and reporting to the faculty mentor.
 Log book format will be given to students to maintain a record of work carried out every week and discuss
with faculty mentor and get signature of faculty mentor on it. Reporting date and comments will be written
on weekly basis in this log book.
 Log book submission to be done by students during the midterm and final presentation.
 Any student not completing the requirements to be reported to the HoD/Dean in time.
The faculty mentors will evaluate the project team fortnightly on the basis of the rubric shown in table 5.2.1.

Table 5.2.1: Rubrics for fortnightly progress review

Below
Far Exceeds Exceeds Met Expectations
Parameter Expectation (5) Expectation(4) Expectations(3) (2)
Fortnightly project The student reports The student The student The student is
discussion with to the project mentor reports to the reports to the irregular and
A Mentor (5) regularly and project mentor project mentor inconsistent in
consistent in work often but not but lacks work
very consistent Consistency
Completion of the The student has The student has The student has The student
tasks as discussed completed all the completed most completed some has not
B in previous meeting tasks and has shown of the tasks and of the tasks and completed
(5) the updates has shown the has shown the any the tasks.
updates updates.
TOTAL MARKS= (A+B)=10 per week

1st Review Criteria

The student would be evaluated for the first phase of the capstone project as per the time line given in the table
4.2.1. The Student has to make the presentation in front of the panel of faculty members that also includes the
faculty mentor. It is expected that by this time the project groups have discussed and finalized the topic and the
feasibility of the implementation. Following are the guidelines for the 1st Review.

• Each project group to briefly describe the project definition, objectives and the scope of the project.
• The tools and technology which would be used for the design and development of the project to be
discussed.
• The students are expected to present the project engagement schedule and the project development time
line for the entire semester (Gantt Chart) to be prepared.

• The topic approval will be done based on the rubric shown in table 5.2.2.

PAGE 7
 Table 5.2.2 Rubrics for 1st review

Far Exceeds Expectation Exceeds Below

Parameter Met Expectations (3)
(5) Expectation (4) Expectations (2)
Detailed and extensive
No great
Identification of explanation of the project Good explanation Average explanation
explanation of the
Problem statement, idea, purpose, need of the of the project idea, of the project idea,
A project idea,
Purpose and need of project, novelty of the idea purpose and need purpose and need of
purpose and need
the project (5) and clearly defined of the project the project;
of the project
objectives
Feasibility has been done Has idea about the Feasibility has yet to
Not considered
Feasibility of the taking into accounts all the constraints and be considered. Has
B constraints and
implementation (5) constraints and explained considered Knowledge about
feasibility
well explained feasibility constraints

TOTAL MARKS= (A+B)=10

2nd Review Criteria

The Student would be evaluated for the second phase of the capstone project during the 2nd Review as per the time
line given in table 4.2.1. The Student has to give the presentation in front of the panel of faculty members that also
includes the faculty mentor. Following are the guidelines for the 2nd Review.

• Student has to make a presentation covering the Project Progress till date. Student can include the proposed
features of the system, the Analysis and design documents as well as the problems related to the system
design, tools and technology. Individual contribution to be presented.
• The current progress would be compared with the project engagement schedule and the project
development plan, which was submitted during the 1st Review.

After the 2nd review, the Internal Facilitator/Internal Project Reviewer would evaluate the regularity of the student,
his knowledge as well as the approach and methodology adopted by him to design and develop the system. His
documentation and presentation skills would also be evaluated. If the faculty finds the project progress very slow
mentor will be required to to report to the PC/HoD. Student has to demonstrate the working modules of the project
in front of the panel of faculty members which includes the faculty mentor.

The second review will be for 20 marks. The components for the evaluation of 2nd review are shown in table 5.2.3.

PAGE 8
 Table 5.2.3 Rubrics for 2nd review

Far Exceeds Expectation Exceeds Below

Parameter (5) Expectation(4) Met Expectations(3) Expectations (2)
The student has a good
The student has complete understanding of the The student has
Literature understanding of the existing conducted a very narrow No remarkable
A Review/Market existing research/products research/products and research on existing literature/market
Survey(5) and debates relevant to the debates relevant to the systems/methodologies/p survey conducted
project topic or area of study project topic or area of roducts.
study
The student has identified
The problem statement The problem
Clarity of the the problem statement after
The student stated the needs some improvement statement is not
B problem statement identifying research gaps
objectives well. and the objectives need to clear. Need to be
(5) and stated the objectives
be refined. reworked.
well.
The system
The system design is very The system architecture architecture is not
The system architecture
well drawn and gives designed gives a good drawn and there is
designed moderately
Design/ System complete understanding of understanding of the no complete
depicts the proposed
C level the proposed model/ proposed model/ understanding of
model/ Algorithms to be
representation(5) Algorithms to be Algorithms to be the proposed
implemented are
implemented are clearly implemented are well model or
moderately explained
stated stated Algorithms to be
implemented.
The student has The student has started
The student has The student has
implemented the the implementation of the
implemented the not yet started
model/algorithms and model/algorithms and
model/algorithms and implementation.
Implementation/ completed more than 50% completed less than 40%
D completed up to 40% of Results are not
Results (5) of the work of the work
the work satisfactorily
The results are very well Some preliminary results
The results are shown in shown in the
documented and shown in are shown in the
the presentation presentation
the presentation. presentation
Complete explanation Not a great
Complete explanation of the of the key concepts but Incomplete explanation of explanation of the
key concepts and strong in-sufficient description the key concepts and in- key concepts and
description of the technical of the technical sufficient description of in-sufficient
E Interim Report (5)
requirements of the project requirements of the the technical description of the
and Future extensions in the project Future requirements of the technical
project are well specified extensions in the project project requirements of
are specified the project

Total (A+B+C+D+E) = 25 marks

3rd review (Final Presentation and Viva)

Student will demonstrate the working modules of the project in front of the external expert and a panel of faculty
members formed by the department which includes the faculty mentor. The students shall demonstrate details of
the testing, implementation and technical documentation including the outcomes and conclusion. The students
should present the overview of all aspects of the project completed including the design/testing/implementation
and documentation details.

There will be two components for the final presentation and viva.

1. Faculty mentor evaluation (20 marks)

2. External panel member evaluation (30 marks)
PAGE 9
 The evaluation for the final presentation and viva will be done based on the rubric shown in table 5.2.4 and
5.2.5

Table 5.2.4 Rubrics for external panel member for final Presentation and Viva (3rd review)

Sr. Far Exceeds Exceeds Below Expectations

No. Parameter Expectation (5) Expectation(4) Met Expectations(3) (2)
The student has identified The problem statement
Literature review
the problem statement needs some The problem statement
and clarity of the The student stated the
A after identifying research improvement and the is not clear. Need to be
problem statement objectives well.
gaps and stated the objectives need to be reworked.
(5)
objectives well. refined.
The system
The system design is very The system architecture
The system architecture architecture is not
well drawn and gives designed gives a good
designed moderately drawn and there is no
Design/ System complete understanding understanding of the
depicts the proposed complete
B level of the proposed model/ proposed model/
model/ Algorithms to understanding of the
representation(5) Algorithms to be Algorithms to be
be implemented are proposed model or
implemented are clearly implemented are well
moderately explained Algorithms to be
stated stated
implemented.

Algorithms/techniques
Implementation are well stated/modules No algorithms/
Algorithms/techniques Algorithms/techniques
and results, of project are well techniques specific to
are well stated/ are not proper/Modules
C attainment of integrated and system the projects are stated
Integration of all of project are not
defined working is accurate. and Modules of project
modules is not done properly integrated
objectives(5) Defined objectives are are not integrated
attained.

Complete explanation
Complete explanation of Not a great
of the key concepts but Incomplete explanation
the key concepts and explanation of the key
in-sufficient description of the key concepts and
strong description of the concepts and in-
of the technical in-sufficient description
D Report (5) technical requirements of sufficient description
requirements of the of the technical
the project and Future of the technical
project Future requirements of the
extensions in the project requirements of the
extensions in the project
are well specified project
project are specified

The project team falters

The project team fails to The student fail to
around to answer few
Contents of presentations answer many questions. answer questions. The
questions but The
E Presentation (5) are appropriate and well The student has no great student has no
student has thorough
delivered technical insights into idea/technical insights
knowledge about the
the project into projects
project

The student falters

The student is able to The student fails to The student fails to
around to answer few
answer the questions answer many questions. answer questions. The
questions but The
F Viva (5) effectively. The student The student has no great student has no
student has thorough
has thorough knowledge technical insights into idea/technical insights
knowledge about the
about the project the project into projects
project

Total (A+B+C+D+E+F) = 30 marks

PAGE 10
 Table 5.2.5 Rubrics for faculty mentor for final Presentation and Viva (3rd review)

Sr. Far Exceeds Exceeds Below

No. Parameter Expectation (5) Expectation(4) Met Expectations(3) Expectations (2)
Complete
explanation of the Complete explanation Not a great
key concepts and of the key concepts but explanation of the
strong description in-sufficient Incomplete explanation of the key key concepts and
of the technical description of the concepts and in-sufficient in-sufficient
A Report (10)
requirements of the technical requirements description of the technical description of the
project and Future of the project Future requirements of the project technical
extensions in the extensions in the requirements of
project are well project are specified the project
specified

The students fail

The project team
to answer
Contents of falters around to The project team fails to answer
questions. The
presentations are answer few questions many questions. The student has no
C Presentation (5) student has no
appropriate and but The student has great technical insights into the
idea/technical
well delivered thorough knowledge project
insights into
about the project
projects

The project team is

The students fail
able to answer the The project team
to answer
questions falters around to The project team fails to answer
questions. The
effectively. The answer few questions many questions. The student has no
D Viva (5) student has no
student has but The student has great technical insights into the
idea/technical
thorough thorough knowledge project
insights into
knowledge about about the project
projects
the project

Total (A+B+C+D) = 20 marks

PAGE 11
Annexures

PAGE 12
 A.1 Project registration form

Mukesh Patel School of Technology Management

& Engineering

Project registration form

Department:
Program:
Semester:

Project Team details

S No SAP ID Roll No Name Signature
1
2
3

Three broad domains in which the project team intends to work

S No Domain Project idea in brief
1
2
3

PAGE 13
 A.2 Topic approval form

Mukesh Patel School of Technology Management & Engineering

Topic approval form
Department :
Program :
Semester :
Project Team details
S No SAP ID Roll No Name Signature
1
2
3

Type of Project (Tick any one)

Type of project
Application
Product
Research

Project details
Project Title
Project Objectives

PAGE 14
Domain
Motivation

Expected outcomes

Latest References
S No Publication (Author, “Title”, Journal/Book/Conference, Date, Page, Volume, year)
1
2
3
4
5

Status of the project after Review 1

Comments/Remarks

Name and Signature of the guide

Name and signature of panel

members for review 1
Signature of HoD

If any change in project title after review 1 presentation as per comments received
from panel and areas of concern to be noted here

PAGE 15
 A.3 Evaluation sheet for Review 1: Topic approval and feasibility

Mukesh Patel School of Technology Management & Engineering

Evaluation sheet for Review 1: Topic approval and feasibility

S No SAP ID Roll No Student Identification Feasibility of Total

Name of Problem the
statement, implementation (10 marks)
Purpose and (5 marks)
need of the
project

(5 marks)

Name & Signature of the Project mentor

(with Date)

Name & Signature of the panel members

(with Date)

PAGE 16
 A.4 Evaluation sheet for Review 2: Midterm review

Mukesh Patel School of Technology Management & Engineering

Evaluation sheet for Review 2: Midterm review

S SAP Roll Student Literature Clarity of Design/ Implement Interim Total

No ID No Name Review/Mark the problem System level ation/ Report
et Survey statement representation Results (25
(5 marks) marks)
(5 marks) (5 marks) (5 marks) (5 marks)

Name & Signature of the Project mentor

(with Date)

Name & Signature of the panel members

(with Date)

PAGE 17
A.5 Evaluation sheet for Review 3: External Panel Member Evaluation

Mukesh Patel School of Technology Management & Engineering

Evaluation sheet for Review 3: External Panel Member Evaluation
S No SAP Roll Student Literature Design/ Implementat Report Presentation Viva Total
ID No Name review and System ion and
clarity of level results (5 marks) (5 marks) (5 (30
the representat marks) marks)
problem ion (5 marks)
statement
(5 marks)
(5 marks)

Name & Signature of the External Panel Member

(with Date)

PAGE 18
 A.6 Evaluation sheet for Review 3: Internal Project mentor Evaluation

Mukesh Patel School of Technology Management & Engineering

Evaluation sheet for Review 3: Internal Project mentor Evaluation

S No SAP ID Roll Student Report Presentation Viva Total

No Name
(10 marks) (5 marks) (5 marks) (25 marks)

Name & Signature of the Project mentor

(with Date)

PAGE 19
 A.7 Log Book for Capstone Project

Mukesh Patel School of Technology Management & Engineering

Log Book for Capstone Project

Department :
Program :
Semester :
TITLE OF THE PROJECT :

Name of the Faculty Mentor:

STUDENT DETAILS

NAME ROLL NO. CONTACT

Student 1

Student 2

Student 3

Student 4

Name of group members:

Roll No. Name Sign(Students) Grades(By Faculty

Mentor)

PAGE 20
Date of Reporting:

Work Carried out in Week No.

From : (DD/MM/YYYY to DD/MM/YYYY):

Remarks:

Sign of Faculty Mentor (With Date):

PAGE 21
 A.8 Project Report Format

Project Report Format

(This page is only for reference and should not be included in the
final report)

Follow the given instructions while preparing the report:

1. Font Times New Roman.

2 Line spacing 1.5".

3. Margins (left) 1.5”

4. Remaining all margins 1”

5. Header Right corner Academic Year

6. Header Left corner Project Title

7. Footer: Right Corner Page Number

8. Chapter Title Font size 18 and bold.

9. Section titles Font size 14 and bold

10. Subsection titles Font size 12 and bold

11. Figure name (below the figures) Times new roman , font size
10

12. Table name (above the table) Times new roman, font size
10

13. Report text Font size 12

PAGE 22
14. Appendix will include:

 Specifictions of components
 Pin diagram
 Source code
 Sample codes
 Raw experimental observations etc.
 which shall be numbered in Roman Capitals (e.g. “Appendix IV”).

15. The report (two copies) should be Hard Bound- Black Book

16. The report must be verified and signed by the respective mentors before the
final

Presentation / examination.

17.Refer to the following table of contents for the format.

18.Page numbers in Table of Contents for List of Figures, List of Tables

and Abbreviations has to be in Roman numbers.

19. Page numbers from Chapter 1. Introduction, onward should be in decimal

format.

20. Every chapter should have introduction paragraph and summary lines.

21. Conclusion will be only one, which will be written at the end of report.

PAGE 23
 Project Title

Project Report submitted in the partial fulfilment

of

(Name of the Program)

In
(Name of the stream)

by

Names (Roll No.)

Under the supervision of

Name of Faculty Mentor

(Designation, Name of the department, MPSTME)

PAGE 24
 SVKM’s NMIMS University
(Deemed-to-be University)

MUKESH PATEL SCHOOL OF TECHNOLOGY

MANAGEMENT & ENGINEERING (MPSTME)

Vile Parle (W), Mumbai-56

(Academic year)

CERTIFICATE

This is to certify that the project entitled (“Title”), has been done by Ms/Mr ( name) under
my guidance and supervision & has been submitted in partial fulfilment of the degree of
(name of the program) in (name of the stream) of MPSTME, SVKM’s NMIMS (Deemed-to-be
University), Mumbai, India.

_______________ ______________
Project mentor (name and Signature) Examiner ( name and Signature)
(Intenal Guide)
Date

Place: Mumbai _______________

(HoD) (name and Signature)

PAGE 25
 ACKNOWLEDGEMENT

Student Names
NAME ROLL NO. SAP ID

PAGE 26
 ABSTRACT

Approximately one page in which problem shall be defined and outline of proposed work in relation
to title of the report shall be given (Times New Roman 12, 1.5 spacing)

What is Abstract?

The abstract for a project is simple, short and can be seen as an overview. It is also like a summary
that defines the core of your work. Whether it is literature or science, all papers need some kind of
abstract. It will also help the reader understand what you are talking about. Looking at an abstract as
a summary will not just make your work easy but also help you write a good one. Always remember
that an abstract is not just a summary of the whole paper but also something that could be seen as
contributions/conclusions of the work done. To make the abstract more readable thing, make sure to
use precise and easily understandable language.

PAGE 27
 Table of Contents

Topics Page

List of Figures i

List of Tables xvi

Abbreviations xix

Chapter 1 Introduction

1.1

1.2

Chapter 2 Literature survey

2.1

2.2

2.3

Chapter 3 Methodology and Implementation

3.1

3.2

Chapter 4 Result and Analysis

4.1

4.2

Chapter 5 Advantages, Limitations and Applications

5.1 Advantages

5.2 Limitations

5.3 Applications

PAGE 28
Conclusion and Future Scope

References

Appendix A: Soft Code Flowcharts

Appendix B: Data Sheets

Appendix C: List of Components

Appendix D: List of Paper Presented and Published.

List of the figures

Fig No Name of the figure Page No

List of tables

Table No Name of the Table Page No

Abbreviations

Table No Name of the Table Page

No

Note: Each table should be included on separate page.

PAGE 29
 Chapter 1

Introduction

Introduction (of the project, and the flow of different chapters)

1.1 Background of the project topic

1.2 Motivation and scope of the report
1.3 Problem statement
1.4 Salient contribution
1.5 Organization of report

Note:

1. Please include the citations for the papers refered and also include it in the
references at the same numbered location as in the text.
2. Include the IEEE standards followed for designing the project at
appropriate places in the text.
3. Minimum number of pages for the report has to compulsprily be

PAGE 30
 Chapter 2

Literature survey

Discussion and comparison of literature survey.

2.1 Introduction to overall topic (generate background for literature survey with
reference to minimum 15 references)

2.2 Exhaustive literature survey of atleast 10 good journal or conference papers

related to topic preferably starting from reference 1 to 15 given in the
reference section serially. Literature survey should lead finally to identifying
the gap in the research area and hence definition of problem statement.

Note:

1. Please include the citations for the papers referred

2. Include it in the reference list at the same location as the number in the
text.
What is a literature review?
A literature review summarizes and synthesizes the existing scholarly research on a particular
topic. Literature reviews are a form of academic writing commonly used in the sciences, social
sciences, and humanities. However, unlike research papers, which establish new arguments and
make original contributions, literature reviews organize and present existing research. As a
student, you might produce a literature review as a standalone paper or as a portion of a larger
research project.
Literature Review should be written in paragraph pattern in report and in comparative form in
presentation.

PAGE 31
 Chapter 3

Methodology and Implementation

4.1 Block diagram

4.2 Hardware description

4.3 Software description, flowchart / algorithm

This chapter can comprise of actual implementation photos and their

description.

PAGE 32
 Chapter 4

Results and Analysis

This shall include a thorough evaluation and investigation carried out. It should also bring out your
contributions from the study. The discussion shall logically lead to inferences and conclusions as well
as scope for possible further future work.

Note:

Include the IEEE or any other standards that you have adhered to test
the validity of the results.
Link for IEEE standards

https://www.ieee.org/content/ieee-org/en/standards/index.html/

PAGE 33
 Chapter 5

Advantages, Limitations and Applications

PAGE 34
 Chapter 6

Conclusion and Future Scope

 A brief report of the work carried out, conclusions derived from logical analysis presented in
the Results and Discussions chapter.
 Scope for future work should be stated lucidly in this chapter.

References

 Number all the references.

 Use a chronological bibliography.
 Each listed reference in the bibliography must be cited in the text of the
report.
 For a book give the name(s) of author(s), title of book, edition, chapter
number, and page numbers, publisher, location and year of publication.

 Example:
[25] Jones, C.D., A.B. Smith, and E.F. Roberts, Efficient Real-Time
Fine-Grained Concurrency, 2nd Ed., Ch. 3, pp. 145-7, Tata McGraw-
Hill, New Delhi, 1994.

 For a journal/conference paper, give the name(s) of authors, title of

paper, name of journal/ conference, volume and issue number (for
journal), page numbers, and month and year of publication.
 Example:
[23] Prasad, A.B., Kumar, C.D., Jones, E.F., and Frost, P.: “Cable
Television Broadband Architectures”, IEEE Comm. Magazine, vol. 39,
pp. 134-141, June 1991.

PAGE 35
Appendix A: Soft Code Flowcharts

PAGE 36
Appendix B: Data Sheets

PAGE 37
Appendix C: List of Components

PAGE 38
 Appendix D: List of Paper Presented and Published

 List of papers on the topic of the report published by the candidates.

 This may also be included in the contents.
 The candidates may also include reprints of his/her publications after the literature citation.

PAGE 39