Project

Tracker

To Bridge the Gap between

Industry and Academia

Group Number :-

Project Title:-

Name of Guide

Name of Co-Guide

Department of Electronics & Communication Engineering

GUIDELINES
WHY IS FINAL YEAR PROJECT IMPORTANT?
The final-year project is important for a number of reasons:

 It is the largest single piece of work you will do during your degree course.

 An industry oriented or research based project increases the weightage of

your resume tremendously thereby multiplying your job prospects. Industry
professional always looks out for candidates with excellent project back
grounds.

 A technically sound project increases your higher education admission

prospects.

 It is the part of the curriculum that allows you to specialise in a topic you are
good at or enjoy.

 It is the part of your course that prospective employers will most likely ask
you about at interview;

 It allows you to show off a wide range of the skills and knowledge learned
during your course;

 It encourages integration of subjects learned in different years of

engineering education.

TIMELINE FOR PROJECT

Students should strictly adhere to the timeline given below:

Initial thinking and register project choices: Within one week of

commencement of classes.
Preparing Methodology and Literature review: Last week of August
Framework of the Project/Layout/Component Purchase: November
Writing and Publishing a review Paper: End of Semester
Finalizing and Testing of Project: January-February
Research paper and Final presentation: Last week of March
Report Submission (With Published Paper): Second week of April
External Presentation: As per University
The above timetable applies both to students out on industrial placement or
internships and to those students who are continuing on into the final year.
IMPORTANT INSTRUCTIONS
You can’t just build the project though; you must be able to reflect on why you built
it the way you did. You would therefore review the problem domain and a range of
candidate solutions before proceeding with a design, implementation and
evaluation. Normally there is an identifiable “customer” for the project – someone
who could use the product in the course of their business or other activities. At
each stage, you would be expected to justify your decisions in the context of the
customer’s business or other needs.

The three things that external examiners in recent years have most
frequently criticised projects for is lack of a proper literature review, failure
to adopt an engineering approach and lack of a critical element.

A proper literature review is necessary for you to show that you can place your
work in the wider context of computing and that you have adequately found out
about previous work in the field that may guide your project.

An engineering approach is one where you follow some appropriate process or

methodology that leads from requirements to design to implementation and testing.
By adopting such a process, it is much less likely that you will fail to take some
crucial factor into consideration – an important aspect of professionalism.

The critical element involves showing what you independently (in your
professional judgement) believe to be good and bad about what you’ve read, what
you’ve been taught, what you’ve been asked to do, what you’ve done, what you
haven’t done and the consequences of those. It does not involve blindly accepting
as fact everything that you have been told or seen written down.

GENERAL REQUIREMENTS FOR THE PROJECT

Obviously, it is not sufficient just to have a problem to solve or a question to

answer to form a project. This doesn’t necessarily mean that the problem has
never been solved before but projects that simply set out to repeat someone else’s
work are weak unless they incorporate some new aspect or adopt a different
approach.

A project must be big enough to fill your time for about 10 months (including winter
vacations). On the other hand, it must also be small enough for you to have a
reasonable chance of completing it within that timeframe.

Finally, a project is an individual piece of work, though there is no bar on students

doing related projects (or separate, identifiable parts of a larger project).

2
During the course of a project, you will undoubtedly undertake many different
activities. These will include:

 Defining the objectives of the project;

 Acquiring background information about the problem and its possible

solutions.

 Establishing the criteria by which your solution(s) to the problem will be

judged.

 Determining by what process the work will be carried out.

 Planning the detailed phases of the project.

 Adopting one or more design methodologies.

 Analysing requirements.

 Using (or constructing) tools.

 Construction of one or more artefacts (hardware, software, document).

 Evaluating your solution to the problem;

 Reporting on your work.

Whatever the nature of the problem you set out to solve, the conclusion of
your project should be whether you solved it successfully or not.

PROJECT GUIDE/SUPERVISOR

Every student project must have two Project Guides/supervisors, One Main Guide
and One Co-Guide. The supervisor’s role is to guide you through the project
process and help you if you have problems. The Guide is not there to do the
project for you. Your Project Guide will be seeing you each week to discuss the
progress of your project. Its responsibility of the students to seek guidance from
your supervisor every week. Any failure in doing so would lead to severe penalties
in terms of marks.

3
REPORT WRITING

Project report is a written evidence of tasks, processes and activities that are undertaken and
accomplished by the students while pursuing their projects and implementing it.

This report is an official document that reflects precise and concrete information about the
different aspects of the project ranging from the overview, requirements, practical aspects,
theoretical considerations, tasks furnished, outcomes gained, objectives listed, reports attached,
abstracts, experiments and results, conclusions and recommendations to the implementation and
scope of the project.

Thus, a project report provides complete information about the project to the reader, and
therefore, it is a mandatory document that must be submitted to as per follows

1. Project Guide,

2. Department( to be kept for future reference)

3. University Copy.

More often than not such a valuable project report is poorly drafted and presented, and
therefore fails to attract the attention of the departmental authorities who usually conduct
exams. Apart from this, such a poorly drafted report not even gets proper attention from
its readers as well. Eventually, it leads to poor impression, and the possessor of such a
report usually scores low marks in projects.

4
 ABES Engineering College
Ghaziabad
Department of
Electronics and Communication Engineering

GENERAL INFORMATION
PROJECT NAME GUIDE CO- GUIDE

PROJECT ABSTRACT

GROUP MEMBERS DETAILS

NAME ROLL NO CONTACT NO E-MAIL ID HOSTLER/DAYSCHOLAR

CONCLUSIONS/RECOMMENDATIONS BY GUIDE (AT THE TIME OF SUBMISSION)

 ABES Engineering College,
Ghaziabad
Department of
Electronics and Communication Engineering

PROJECT STATUS REPORT

GUIDE –STUDENT MEETING SCHEDULER

SL DATE % WORK DONE NEXT DUE DATE COMMENTS GUIDE SIGNATURE

NO
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.

CONCLUSIONS/RECOMMENDATIONS (AT THE TIME OF SUBMISSION)

6
Student- Guide Meeting

Date :- Meeting No:-

Objective of Meeting:-

Task Completed:-

New Task Assigned:-

Date of Completion of new Task:-

Review:

Conclusions:

Signature of the student Signature of Guide/Co-Guide

Student- Guide Meeting

Date :- Meeting No:-

Objective of Meeting:-

Task Completed:-

New Task Assigned:-

Date of Completion of new Task:-

Review:

Conclusions:

Signature of the student Signature of Guide/Co-Guide

2
Student- Guide Meeting

Date :- Meeting No:-

Objective of Meeting:-

Task Completed:-

New Task Assigned:-

Date of Completion of new Task:-

Review:

Conclusions:

Signature of the student Signature of Guide/Co-Guide

3
Student- Guide Meeting

Date :- Meeting No:-

Objective of Meeting:-

Task Completed:-

New Task Assigned:-

Date of Completion of new Task:-

Review:

Conclusions:

Signature of the student Signature of Guide/Co-Guide

4
Student- Guide Meeting

Date :- Meeting No:-

Objective of Meeting:-

Task Completed:-

New Task Assigned:-

Date of Completion of new Task:-

Review:

Conclusions:

Signature of the student Signature of Guide/Co-Guide

5
Student- Guide Meeting

Date :- Meeting No:-

Objective of Meeting:-

Task Completed:-

New Task Assigned:-

Date of Completion of new Task:-

Review:

Conclusions:

Signature of the student Signature of Guide/Co-Guide

6
Student- Guide Meeting

Date :- Meeting No:-

Objective of Meeting:-

Task Completed:-

New Task Assigned:-

Date of Completion of new Task:-

Review:

Conclusions:

Signature of the student Signature of Guide/Co-Guide

7
Student- Guide Meeting

Date :- Meeting No:-

Objective of Meeting:-

Task Completed:-

New Task Assigned:-

Date of Completion of new Task:-

Review:

Conclusions:

Signature of the student Signature of Guide/Co-Guide

8
Student- Guide Meeting

Date :- Meeting No:-

Objective of Meeting:-

Task Completed:-

New Task Assigned:-

Date of Completion of new Task:-

Review:

Conclusions:

Signature of the student Signature of Guide/Co-Guide

9
Student- Guide Meeting

Date :- Meeting No:-

Objective of Meeting:-

Task Completed:-

New Task Assigned:-

Date of Completion of new Task:-

Review:

Conclusions:

Signature of the student Signature of Guide/Co-Guide

10
Student- Guide Meeting

Date :- Meeting No:-

Objective of Meeting:-

Task Completed:-

New Task Assigned:-

Date of Completion of new Task:-

Review:

Conclusions:

Signature of the student Signature of Guide/Co-Guide

11
Student- Guide Meeting

Date :- Meeting No:-

Objective of Meeting:-

Task Completed:-

New Task Assigned:-

Date of Completion of new Task:-

Review:

Conclusions:

Signature of the student Signature of Guide/Co-Guide

12
Student- Guide Meeting

Date :- Meeting No:-

Objective of Meeting:-

Task Completed:-

New Task Assigned:-

Date of Completion of new Task:-

Review:

Conclusions:

Signature of the student Signature of Guide/Co-Guide

13
Student- Guide Meeting

Date :- Meeting No:-

Objective of Meeting:-

Task Completed:-

New Task Assigned:-

Date of Completion of new Task:-

Review:

Conclusions:

Signature of the student Signature of Guide/Co-Guide

14
Student- Guide Meeting

Date :- Meeting No:-

Objective of Meeting:-

Task Completed:-

New Task Assigned:-

Date of Completion of new Task:-

Review:

Conclusions:

Signature of the student Signature of Guide/Co-Guide

15
Student- Guide Meeting

Date :- Meeting No:-

Objective of Meeting:-

Task Completed:-

New Task Assigned:-

Date of Completion of new Task:-

Review:

Conclusions:

Signature of the student Signature of Guide/Co-Guide

16
Student- Guide Meeting

Date :- Meeting No:-

Objective of Meeting:-

Task Completed:-

New Task Assigned:-

Date of Completion of new Task:-

Review:

Conclusions:

Signature of the student Signature of Guide/Co-Guide

17
Student- Guide Meeting

Date :- Meeting No:-

Objective of Meeting:-

Task Completed:-

New Task Assigned:-

Date of Completion of new Task:-

Review:

Conclusions:

Signature of the student Signature of Guide/Co-Guide

18
Student- Guide Meeting

Date :- Meeting No:-

Objective of Meeting:-

Task Completed:-

New Task Assigned:-

Date of Completion of new Task:-

Review:

Conclusions:

Signature of the student Signature of Guide/Co-Guide

19
Student- Guide Meeting

Objective of Meeting:-

Task Completed:-

New Task Assigned:-

Date of Completion of new Task:-

Review:

Conclusions:

Signature of the student Signature of Guide/Co-Guide

20
 Evaluation

1. The evaluation of students would be according to following Rubrix, which is designed separately for VIIth
and VIIIth Semester. The evaluation Rubrix has to be filled by faculty Guide.

2. Faculty Guide should maintain all 6 Rubrix sheets for each student in the group separately as per his/her
performance and should be submitted to the office after completion of evaluation.

3. Final marks statement has to be maintained separately for all students in the group and should be
submitted in the department on completion of evaluation.
 Rubric # R1-B.Tech Project (7th Semester)
Statement: Project proposal evaluation: An ability to propose a project which is relevant to subject of engineering after
detailed literature survey and technical feasibility

Expectation:-->
Exceeds expectations Adequately meets expectations Minimally Meets expectation Fails to meet expectation
Expectations Point:4 Expectations Point:3 Expectations Point:2 Expectations Point:1 Score
Criteria

C1: Identification of a Identification of a project proposal with Identification of a project proposal

Identification of a project proposal with
project proposal which is complete clarity without any ambiguity with incomplete discussions on its Project identification with no idea
adequate and light discussions on its
relevant to the subject of with a through discussions on its relevance, need and purpose. Not about its relevance, need, purpose
relevance, purpose and need on the basis of fully aware of available
engineering and its relevance, purpose and need on the basis and available information.
readily available information. information.
purpose and need. of all available information.

Prepared a fair literature review

C2:Literature review Prepared an excellent literature review Prepared a good literature review pertaining
pertaining to the field of project No literature review provided.
pertaining to the field of project proposal. to the field of project proposal.
proposal.

C3:Specifications of
Identified and discussed major
project, analysis of Identified and discussed all constraints, Fails to identify the constraints
Identified and discussed major constraints, constraints, criteria, and
technical feasibility, criteria, and assumptions and constructed and assumptions. Did not
criteria, and assumptions and constructed assumptions and constructed an
criteria, constraints and complete specifications of the project identify the specifications of the
broad specifications of the project proposal outline of specifications of the
assumptions: proposal project proposal.
project proposal

C4: Cost analysis: Poor cost analysis and

Excellent cost analysis done with due Very good cost analysis supported with
Estimated cost of Good cost analysis approximate cost mentioned with
diligence and supported with discussions. discussions.
completing the project no basis given.

Total Score
 Rubric #R 2-B.Tech Project (7th semester)

Statement: Project design: An ability to design the system components and process and identify the engineering tools
required with due consideration of assumptions and constraints and societal considerations

Expectation:-->
Adequately meets Minimally Meets Fails to meet expectation
Exceeds expectations expectations expectation
Expectations Point:4 Score
Expectations Point:3 Expectations Point:2 Expectations Point:1
Criteria

C1: Methodology
proposed for project
design,
implementation
strategy and
engineering tools
required
C2:Technical
knowledge and
awareness about
the project

C3:Communication
skills (Written, oral
and presentation
skills)

Total Score
 Rubric #R 3-B.Tech Project (8th semester)
Statement: First project review: An ability to use management skills and implement the project, manage problems
encountered, work as a team member and present the work progress

Expectation:-->
Adequately meets Fails to meet expectation
Exceeds expectations Minimally Meets expectation
expectations
Expectations Point:4 Expectations Point:2 Score
Expectations Point:3 Expectations Point:1
Criteria

C1:Review of
design
methodology
used

C2: Project
management
skills

C3:
Demonstration
and
presentation

C4:Individual
and team work

Total Score
 Rubric # R4-B.Tech Project (8th Semester)
Statement: Final project review and evaluation: An ability to appreciate suggestions made in the first review, make informed review and
manage resources within the constraints

Expectation:-->
Adequately meets Fails to meet expectation
Exceeds expectations Minimally Meets expectation
expectations
Expectations Point:4 Expectations Point:2 Score
Expectations Point:3 Expectations Point:1
Criteria

C1:
Incorporation
of suggestions

C2:Project
Demonstration

C3: Analysis of
problems
encountered
and remedial
actions taken

C4: Impact on
society and
environment

Total Score
 Rubric # R5-B.Tech Project
Statement: Project report review: Able to prepare a Project report which is consistent with standard technical report writing procedures.

Expectation:--> Adequately meets Fails to meet expectation

Exceeds expectations Minimally Meets expectation
expectations
Expectations Point:4 Expectations Point:2 Score
Expectations Point:3 Expectations Point:1
Criteria

C1:Organizatio
n of report

C2:Figures,
formatting,
diagrams,
graphs, tables
and
mathematics
C3:Description
of concepts and
technical
details
C4: Discussions
and
Conclusions

C5:
Bibliography

C6:Originality
and plagiarism

Total Score
 Rubric # R6-B.Tech Project
Statement: Review by the Guide: Ability to work as a team and contribute effectively with positive attitude

Expectation:-->
Adequately meets Fails to meet expectation
Exceeds expectations Minimally Meets expectation
expectations
Expectations Point:4 Expectations Point:2 Score
Expectations Point:3 Expectations Point:1
Criteria

C1:Positive
attitude,
commitment,
team work and
contribution

C2:Technical
knowledge,
awareness
related to
project

C3:Regularity
and attendance

Total Score
 Rubrics for B.Tech Final year project

Rubric # Statement/Purpose No of Semester

criteria
R1 Project proposal evaluation: An ability to propose a project which is relevant to subject of engineering after detailed 4 VII
literature survey and technical feasibility
R2 Project design: An ability to design the system components and process and identify the engineering tools required 3 VII
with due consideration of assumptions and constraints and societal considerations
R3 First project review: An ability to use management skills and implement the project, manage problems encountered, 4 VIII
work as a team and present the work progress
R4 Final project review and evaluation: An ability to appreciate suggestions made in the first review and manage 4 VIII
resources with the constraints and present the final version of the project.
R5 Project report review: Able to prepare a Project report which is consistent with standard technical report writing 6 VIII
procedures.
R6 Review by the Guide: Ability to work as a team and contribute effectively with positive attitude. 3 VIIIh
Total 24

Semester No. of Rubrics No. of criteria Total points Student’s MM of sessional Sessional marks awarded to the
of Rubrics score in marks students(based on % score in Rubrics)
Rubrics

VII 2 7 28 50
VIII 4 17 68 100
Final Year Project 6 24 96
Group Number:-

Project Name:-

Findings:-

Final Outcome:-

Future Scope:-

Details of the paper Published(DOI/ISSN No):-

Details of the Company(If Applicable):-

Technical Innovation/Novelty of work(To be filled by Guide):-

Remarks(Guide):-

Signature Signature
Guide/Co-Guide Head of Department