Professional Documents
Culture Documents
Project Report UG Format Guidelines 2.1 1
Project Report UG Format Guidelines 2.1 1
for
B. Tech. / B.Sc.
Version 2.1
DISCLAIMER
This document covers the general rules of format, appearance, and writing. It is the student’s
responsibility to read and follow the requirements presented here and to submit documents of
the highest quality. The final copies will not be accepted with corrections, insufficient margins,
or if they are of poor quality. It is the responsibility of the students that the final version of the
report must be free from plagiarism, typographical, grammatical and other errors when
submitted as Library Copy. Students must have to consult properly with his/her supervisor for
the same.
Again, the guidelines in this document are a generic. Changes (e.g., skipping some sections
if not applicable or adding more sections etc.) may be considered as per the instructions
from the concerned Supervisor.
Followings are the instructions and structure to be followed in writing the report:
Font size (regular Text): Times New Roman of 12 pts.
Line Spacing : 1.5 line spacing
Chapters : 16 pts bold Centre aligned (Capital Letters)
Sections : 12 pts bold left aligned (Capital Letters)
Subsections : 12 pts bold left aligned (Title case)
Page numbers (Start with Chapters and onwards): Bottom – centered – 12 pts (1, 2, 3…)
Cite the papers/URL/report/other works/texts or figures appropriately whenever used in your
text in any chapter or sections.
Each chapter should be start from new page.
1) Cover Page
2) Inside Cover Page/Title Page
3) Candidate’s Declaration
4) Certificate from the Supervisor
5) Acknowledgement
6) Abstract
7) Table of Contents
8) Chapters
Maximum Number of Chapters are recommended to be six (Chapter one is Introduction,
Problem Statement/Objective(s), Chapter two is Literature Review/Existing Works,
Chapter three is Design Details, Proposed Approaches, Algorithms and System, Chapter
four is Tools and Technologies/Implementation Details, Chapter five is Results and
Discussion, Chapter six is Conclusions and Future Work/Extension).
9) References
Page Numbering:
The preliminary materials consist of the Title Page, Declaration, Certificate,
Acknowledgements, Abstract, Table of Contents, List of Tables, List of Figures and other lists.
Preliminary pages are paginated separately from the rest of the text. The title page is counted,
but it is not numbered. Beginning with the page immediately following the title page, place
page numbers in lowercase Roman numerals centered at the bottom of the preliminary pages
in the mentioned order. The Roman numerals are continued up to the first page of the text.
Title of the Project
A project report
submitted in partial fulfilment of the requirements for the award of the degree of
Bachelor of Science/Technology
in
Computer Science/Engineering
By
NAME OF CANIDATE
B.Tech. Semester
Exam Roll No.: …….
Enrolment No.: ………
Month, 2021
CANDIDATE’S DECLARATION
I, Name of Candidate, hereby certify that the work, which is being presented in the report,
entitled Title of the Report, in partial fulfillment of the requirement for the award of the
Degree of Full Name of Degree and submitted to the institution is an authentic record of my
own work carried out during the period Month-Year to Month-Year under the supervision of
Supervisor Name at the Department of Electronics and Communication, University of
Allahabad. The matter presented in this report has not been submitted elsewhere for the award
of any other degree or diploma from any Institutions.
I declare that I have cited the reference about the text(s) /figure(s) /table(s) /equation(s)
from where they have been taken. I further declare that I have not willfully lifted up some
other’s work, para, text, data, results, etc. reported in the journals, books, magazines, reports,
dissertations, theses, etc., or available at web-sites and included them in this report and cited
as my own work.
This is to certify that the Mr. Candidate Name has carried out this project/dissertation entitled
Title of the Report under my supervision.
This page is used to thank those persons who have been instrumental to the student in
completing the degree requirements. Acknowledgement of grants and special funding or
fellowship received to support the work also may be made on this page.
ABSTRACT
The abstract should provide a succinct, descriptive account of the report including a statement
of problem procedure and method, results and conclusion. It must not include diagrams and
should not include mathematical formulas unless essential. The abstract should be in the range
of 200 to 400 words with 1.5 line spaced. It should adhere to the same style manual as the
report manuscript. A lower-case Roman numeral is used on the abstract page and number of
keywords not more than six.
ABSTRACT...........................................................................................................................v
LIST OF TABLES .................................................................................................................viii
LIST OF FIGURES ...............................................................................................................ix
LIST OF ABBREVIATIONS ................................................................................................x
LIST OF NOTATIONS ..........................................................................................................xi
CHAPTER 1 INTRODUCTION
LIST OF TABLES
1.1 RSA, DL and EC key sizes for equivalent security levels ………… ........................10
2.1 OEF example parameters……………………………………….......... .....................22
2.2 Computational details for inversion in OEFs ............................................................25
2.3 Computational details for inversion in OEFs …………………................................35
2.4 Admissible orders of elliptic curves over F37…………………… ...........................45
3.1 Isomorphism classes of elliptic curves over F5 ………………………….. ..............48
3.1 Operation counts for arithmetic on y2 = x3 −3x +b …………………………. .............49
3.7 Operation counts for arithmetic on y2 +xy = x3 +ax2 +b………………… ..............50
4.1 Point addition cost in sliding versus window NAF methods …………….. ..............51
4.2 Operation counts for computing kP +lQ …………………………………. ..............55
4.4 Operation counts in comb and interleaving methods ……………………................65
5.1 Koblitz curves with almost-prime group order …………………………… .............75
5.2 Expressions for αu (for the Koblitz curve E0) ……………………………. .............85
5.10 Expressions for αu (for the Koblitz curve E1) ……………………………. .............95
5.11 Operation counts for point multiplication (random curve over F2163 )…. ...............110
(Sample)
LIST OF FIGURES
LIST OF ABBREVIATIONS
LIST OF NOTATIONS
INTRODUCTION
This chapter should be 2 to 4 pages according to the text formatting mentioned above.
Section(s) may be omitted as per the project category, consult to the respective supervisor.
Start from general subject to specific topic. Describe some background and motivation for the
particular topic. Why is the particular problem chosen? What is the significance of the work?
State the Problem Definition and objectives. State the methodology being used in very brief.
Give the detailed methodology in Chapter 3.
State the contribution of your work clearly. Contribution can be some innovation applications
or systems or it can be some proposed algorithms or modification of algorithms. It can also be
some comparative study, etc.
Basically, this chapter contains a discussion of the general area of research/problem which you
plan to explore in the report. It should contain a summary of the work you propose to carry out
and the motivations you can cite for performing this work. Describe the general problem that
you are working towards solving and the specific problem that you attempt to solve in the
report.
The chapter should end with a guide to the reader on the structure and contents of the rest of
the thesis, chapter by chapter.
CHAPTER 2
LITERATURE REVIEW/SURVEY
Describe the previous works done by others in this particular area. Consider most relevant
previous works preferably of last five years. Analyze their merits and demerits, and
shortcomings that motivate you to work further in this area. This chapter contains a specialized
overview of that part of a particular field in which you are doing this project. You should make
generous use of illustrative examples and citations to current research/development.
You can categorize or classify the literature or can give some taxonomy. Sections are not
compulsory in this chapter but you can if it is suitable. Consult with your supervisor.
CHAPTER 3
3.1 INTRODUCTION
3.2 REQUIREMENT SPECIFICATIONS
3.3 SYSTEM DESIGN
3.4 METHODOLOGY USED
3.5 ALGORITHM
3.6 PROPOSED APPROACHES
Section(s) may be omitted according to the project category. Consult to the respective
supervisor. Subsections 3.2 and 3.3 are generally used for database or application design
project.
This chapter outlines your proposed solution to the specific problem described in Chapter 1.
The solution may be an extension to, an improvement of, or even a disproof of someone else's
theory / solution / method / ...).
State the particular approach or methodology being used by you in this project. It can be a step-
by-step process or procedure to do this work. It can be the particular algorithm(s) used in the
work. You can also use some flow diagram or any appropriate diagram to demonstrate it.
Proposed Approaches is only for when you are proposing something new work which is not
existing already. The proposed work can be some new techniques or algorithms or modification
of existing.
If you do not have something new to propose, consult with your supervisor. Comparative study
can also be done.
CHAPTER 4
4.1 INTRODUCTION
4.2 DETAILED DESIGN
4.3 SIMULATOR/TOOL/TECHNOLOGY USED
4.4 SIMULATION
4.5 IMPLEMENTATION
Section(s) may be omitted according to the project category. Consult to the respective
supervisor. For database project or some application design project, describe the section 4.2
here. It may not be applicable for all kind of project.
This chapter describes your implementation or formalism. Depending on its length, it may be
combined with Chapter 3. Not every report/thesis requires an implementation. Prototypical
implementations are common and quite often acceptable although the guiding criterion is that
the research problem must be clearer when you've completed your task than it was when you
started!
If the project category is database application or some other application software design then
describe your detailed design respective to the higher-level design in Chapter 3. If you are using
some simulator or tool or some other technology then describe the details.
Describe about the simulation and/or implementation details. For the source code you can add
that as an appendix.
CHAPTER 5
6.1 INTRODUCTION
6.2 TESTING, VERIFICATION, VALIDATION
6.3 COMPARISON OF RESULTS
6.4 DISCUSSIONS
Section(s) may be omitted according to the project category. Consult to the respective
supervisor.
Give the description of testing, verification, validation, and comparison of results. You can
skip some of these or add something more specific according to the project category. For
database or application design project testing, verification and validation is compulsory.
This chapter should present the results of your report/thesis. You should choose criteria by
which to judge your results, for example, the adequacy, coverage, efficiency, productiveness,
effectiveness, elegance, user friendliness, etc., and then clearly, honestly and fairly adjudicate
your results according to fair measures and report those results. You should repeat, whenever
possible, these tests against competing or previous approaches. The competing or previous
approaches you compare against must have been introduced in Chapter 2 (in fact that may be
the only reason they actively appear in Chapter 2) and you should include pointers back to
Chapter 2. Be honest in your evaluations. If you give other approaches the benefit of the doubt
every time, and develop a superior technique, your results will be all the more impressive.
CHAPTER 6
This chapter should summarize the achievements of your work done in this report/thesis and
discuss their impact on the problems/research questions raised in Chapter 1. Use the distinctive
phrasing "An original contribution of this report/thesis is" to identify your original
contributions to research/design. If you solved the specific problem described in Chapter 1,
you should explicitly say so here. If you did not, you should also make this clear. State the
significance of the work in this chapter.
You should indicate open issues and directions for further or future work in this area with your
estimates of relevance to the field, importance and amount of work required.
REFERENCES
Complete references for all cited works. This should not be a bibliography of everything you
have read in your area.
List the references of all the papers, tutorial or any kind of resources used to prepare this report.
Give the numbering as [i], where i=1, 2, 3, … Also cite them in the text of report.
Ensure that ALL reference entries are complete including: authors, title, journal or conference,
volume and number of journals, date of publication and page numbers. Be careful to at least be
consistent in punctuation.
Within the text of the report, a reference with a number of people can be referred to as Lastname
et al. (where et al appears in italics and the al is followed by a period).
URL's are not valid bibliographic references. They and their contents change and they often
contain material that has not been refereed. If necessary you can give URL’s reference with
accessed date.
[1] D. J. Beebe, “Signal conversion (Book style with paper title and editor),” in Biomedical Digital
Signal Processing, W. J. Tompkins, Ed. Englewood Cliffs, NJ: Prentice-Hall, 1993, ch. 3, pp. 61–
74.
[2] M. Akay, Time Frequency and Wavelets in Biomedical Signal Processing (Book style). Piscataway,
NJ: IEEE Press, 1998, pp. 123–135.
[3] G. B. Gentili, V. Tesi, M. Linari, and M. Marsili, “A versatile microwave plethysmograph for the
monitoring of physiological parameters (Periodical style),” IEEE Trans. Biomed. Eng., vol. 49, no.
10, pp. 1204–1210, Oct. 2002.
[4] V. Medina, R. Valdes, J. Azpiroz, and E. Sacristan, “Title of paper if known,” unpublished.
[5] E. H. Miller, “A note on reflector arrays (Periodical style—Accepted for publication),” IEEE Trans.
Antennas Propagat., in press.
[7] J. E. Monzon, “The cultural approach to telemedicine in Latin American homes (Published
Conference Proceedings style),” in Proc. 3rd Conf. Information Technology Applications in
Biomedicine, ITAB´00, Arlington, VA, pp. 50–53.
[8] F. A. Saunders, “Electrotactile sensory aids for the handicapped (Presented Conference Paper
style),” presented at the 4th Annu. Meeting Biomedical Engineering Society, Los Angeles, CA,
1973.
[9] J. R. Boheki, “Adaptive AR model spectral parameters for monitoring neonatal EEG (Thesis or
Dissertation style),” Unpublished Ph.D. dissertation, Biomed. Eng. Program, Univ. Fed. Rio de
Janeiro, Rio de Janeiro, Brazil, 2000.
APPENDICES
Appendices (optional) include technical material (program listings, output, graphical plots of
data, detailed tables of experimental results, detailed proofs, etc.) which would disrupt the flow
of the report/thesis but should be made available to help explain or provide details to the curious
reader.