TEAM NO:

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

PROJECT WORK DIARY

ACADEMIC YEAR
2024 - 2025

PROJECT TITLE

PROJECT GROUP MEMBERS

SL
USN NAME MOBILE EMAIL
No.
1

PROJECT GUIDE(S)

GUIDE NAME
DESIGNATION MOB
& EMAIL

CO-GUIDE NAME
DESIGNATIONMOB
& EMAIL

1
 About Final Year Project (FYP) diary

This final year project (FYP) diary will record the progress of the students, from the

commencement of project until completion of the project.

The project guide(s) and students are required to retain diary and record each meeting

proceedings regarding the progress of project.

The FYP diary is an official record of contacts between the students and the guide(s). It must

be produced at the end of each phase of project presentations as proof of work done and must

be available for review at any stage during the semester.

IMPORTANT NOTICE TO STUDENTS

i. The Project work diary must be submitted to the Guide (or Co-Guide) for verification

ONCE AWEEK.

ii. The Project work diary must be brought along on every meeting with Guide, Co-

Guide or anyrelated person for verification (signature).

iii. The Project work diary belongs to the faculty. It must be submitted together with

PROJECT REPORT for evaluation purposes by the Guide.

iv. In Project work diary students are required to record the date, time, Guide‟s or Co-Guide„s

signature and meeting place related to the Project completion process.

v. In Project Progress Summary section, remarks of the discussion should be stated.

2
FYP commencement date

FYP completion date

PROJECT WORK GANTT CHART (PHASE I)

(Initial Project Title: )

Month Sep – Oct Oct – Nov Nov – Dec Dec – Jan

Sl. Project  2023 2021 2023 2023-24
No. Activities Week
 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

1
2

3
4
5
6

7
Sl. Month Jan – Feb Feb – Mar Mar – Apr May – Jun
Project  2024 2024 2024 2024
No. Activities Week
17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32

9
10
11

12
13

14

15
16
17

18

(Final Project Title: )

3
Project Work diary writing procedures:

 Record the date on each page. Start each day on a new page. Keep a record of the time
you spend on each step of your project. One easy way to do this is to note the time
you started and the time you finished each activity in your dairy.
 Label each entry and record this in a table of contents (reserve 3-4 pages at start).
 Use ink. Do not erase. Delete an entry by neatly drawing a single line through it.
 Do not remove pages, and do not skip pages.
 Avoid backfilling. If you realize later that you left something out, or just want to
summarize something, go ahead and write it in, noting that it‟s after-the-fact.
 Include everything that contributes to the progress of the Project tasks… good, bad,
and ugly.
 If new information/source are in the form of loose sheets/paper/notes, paste them
inside the dairy and record the date properly on the pages. If the source is larger, fold
and paste neatly into the dairy page.

Tips for diary entry:

If you just finished… Ask yourself…
A meeting  What were the main outcomes of the meeting?
 Was the meeting productive, and why?
 What are your personal action items before the next
meeting?
 Is the project heading in the right direction?
Brainstorming  Which ideas seem most feasible, and why?
 Are there enough good ideas?
 How could better ideas be developed based on this
session?
Engineering Analysis  What were the governing equations?
 What were the most important findings?
 What do the results mean and how should they be
applied?
Visualization  What are the major features/discoveries and why are
(by hand or from visual these significant?
source)  What was learned about the problem or solution
possibilities?
 What problems were resolved and what still needs to
be addressed?
 How does this piece integrate with the whole?
An internet search  What key information did I find? How does it help
achieve the project objectives?
 Are there other sources that should be pursued?
 What new questions were generated?

4
GUIDELINES FOR THE PREPARATION OF B.E./B. Tech. PROJECT REPORTS

1. Project reports should be typed neatly only on one side of the paper with 1.5 or double line spacing on a A4
size bond paper (210 x 297 mm). The margins should be: Left – 1.25”, Right – 1”, Top and Bottom – 0.75”.
2. The total number of reports to be prepared are
 One copy to the department, One copy to the concerned guide(s), Two copies to the sponsoring agency,
One copy to the candidate.
3. Before taking the final printout, the approval of the concerned guide(s) is mandatory and suggested
corrections, if any, must be incorporated.
4. For making copies dry tone Photocopy is suggested.
5. Every copy of the report must contain
 Inner title page (White)
 Outer title page with a plastic cover
 Certificate in the format enclosed both from the college and the organization where the project is
carried out.
 An abstract (synopsis) not exceeding 100 words, indicating salient features of the work. (NB: four
copies of the abstract are to be submitted to the Department on the date of submission separately)
6. The organization of the report should be as follows

1. Inner title page

2. Abstract or Synopsis
3. Acknowledgments Usually numbered in roman
4. Table of Contents
5. List of table & figures (optional)

 Chapters - (to be numbered in Arabic) containing Introduction-, which usually specifies the scope of
work and its importance and relation to previous work and the present developments, Main body of the
report divided appropriately into chapters, sections and subsections.
 The chapters, sections and subsections may be numbered in the decimal form for e.g. Chapter 2,
sections as 2.1, 2.2 etc., and subsections as 2.2.3, 2.5.1 etc.
 The chapter must be left or right justified (font size 16). Followed by the title of chapter centered (font
size 18), section/subsection numbers along with their headings must be left justified with section
number and its heading in font size 16 and subsection and its heading in font size 14. The body or the
text of the report should have font size 12. The figures and tables must be numbered chapter wise for
e.g.: Fig. 2.1 Block diagram of a serial binary adder, Table 3.1 Primitive flow table, etc. The last
chapter should contain the summary of the work carried, contributions if any, their utility along with
the scope for further work.
 Reference or Bibliography: The references should be numbered serially in the order of their
occurrence in the text and their numbers should be indicated within square brackets for e.g. [3]. The
section on references should list them in serial order in the following format.
 For textbooks – A.V. Oppenheim and R.W. Schafer, Digital Signal Processing, Englewood, N.J.,
Prentice Hall, 3 Edition, 1975.
 For papers – Devid, Insulation design to combat pollution problem, Proc of IEEE, PAS, Vol 71,
Aug 1981, pp 1901-1907.
 Only SI units are to be used in the report. Important equations must be numbered in decimal form for
e.g. V = IZ (3.2)
 All equation numbers should be right justified.
 The project report should be brief and include descriptions of work carried out by others only to the
minimum extent necessary. Verbatim reproduction of material available elsewhere should be strictly
avoided. Where short excerpts from published work are desired to be included, they should be within
quotation marks appropriately referenced.
 Proper attention is to be paid not only to the technical contents but also to the organization of the report
and clarity of the expression. Due care should be taken to avoid spelling and typing errors. The
student should note that report-write-up forms the important component in the overall evaluation of the
project
 Hardware projects must include: the component layout, complete circuit with the component list
containing the name of the component, numbers used, etc. and the main component data sheets as
Appendix. At the time of report submissions, the students must hand over a copy of these details to the
project coordinator and see that they are entered in proper registers maintained in the department.

5
 GUIDELINES FOR THE PREPARATION OF B.E./B. Tech. PROJECT REPORTS
 Software projects must include a virus free disc, containing the software developed by them along with
the read me file. Read me file should contain the details of the variables used, salient features of the
software and procedure of using them: compiling procedure, details of the computer hardware/software
requirements to run the same, etc. If the developed software uses any public domain software
downloaded from some site, then the address of the site along with the module name etc. must be
included on a separate sheet. It must be properly acknowledged in the acknowledgments.
 Sponsored Projects must also satisfy the above requirements along with statement of accounts, bills for
the same dully attested by the concerned guides to process further, they must also produce NOC from
the concerned guide before taking the internal viva examination.
 The reports submitted to the department/guide(s) must be hard bounded, with a plastic covering.
 Separator sheets, used if any, between chapters, should be of thin paper

COLOUR OF THE OUTER COVER/FRONT PAGE OF UG DISSERTATION / PROJECT REPORT

CSE/ISE Color of the outer cover/frontpage of the report

CREAM

OBJECTIVES OF THE PROJECT

6
 Project Diary

Week No. Activities carried out during Activities planned Signature of

(Period) the week for next week guide(s) with date

From:

To :

From:

To :

From:

To :

From:

To :

7
 Week No. Activities carried out during the Activities planned Signature of
(Period) week for next week guide(s) with date

From:

To :

From:

To :

From:

To :

From:

To :

8
 Week No. Activities carried out during the Activities planned Signature of
(Period) week for next week guide(s) with date

From:

To :

10

From:

To :

11

From:

To :

12

From:

To :

9
 Week No. Activities carried out during the Activities planned Signature of
(Period) week for next week guide(s) with date

13

From:

To :

14

From:

To :

15

From:

To :

16

From:

To :

10
NOTES

11