Scribd
Upload
53 views5 pages

BIT Report Format

IEEE standard report format for IT and computer engineering student

Uploaded by

kulrajkhanal4
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
53 views5 pages

BIT Report Format

IEEE standard report format for IT and computer engineering student

Uploaded by

kulrajkhanal4
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

Report structure for BIT

Cover page
Note that the cover page should not show a page number.
Approval certificate
Acknowledgements
It is normal to thank those who have given help and support (typically your supervisor). Keep
acknowledgements short and business-like.

Abstract
This should be not more than one page in length. The abstract should allow the reader who is
unfamiliar with the work to gain a swift and accurate impression of what the project is about,
how it arose and what has been achieved.

List of Tables/Figures
If the report contains figures or tables a list of these should be provided. The list should give
the table or figure number, the title of the table or figure and the page number. If only a few
tables and figures are present, they may be treated on one page. Remember that all figures
and tables used must be referred to in the text. For example “The class diagram shown in
Figure 2.1 ....”

List of Abbreviation
Table of Content
Approval certificate
Acknowledgements
Abstract
List of Figures
List of Tables
List of Abbreviation
Chapter 1: Introduction
1.1 Background
1.2 Problem Statement
1.3 Project objective
1.3.1 General objectives
1.3.2 Specific objectives
1.4 Project scope
1.5 Project limitation

Chapter 2: Literature Review


2.1 Background
2.2 Research based on similar project
2.3 Functional and non-functional requirement
2.4 Feasibility study

Chapter 3: System Design & Methodology


3.1 Software Development life cycle
3.1.1 Used model
3.2 Context Diagram
3.3 Data flow Diagram
3.4 Entity-Relation Diagram
3.5 Use case Diagram
3.6 Sequence Diagram
3.7 Activity Diagram
Chapter 4: Implementation
4.1 Software and hardware requirement
4.1.1 Language used
4.2 Testing
4.2.1 Test cases for testing method [Unit testing, System testing, so on]
Chapter 5: Analysis and Evaluation
5.1 Analysis of output obtained
[on the basis predefined objectives]
5.2 Schedule analysis: Gantt chart
Chapter 6: Conclusion & Future recommendation
5.1 Problem faced and their implementation with limitation of the project
5.2 Conclusion
5.3 Future recommendation

(The conclusion chapter should state briefly the achievements of the project, the conclusions
and suggestions for further work.)

References
There should always be a list of all books, articles and technical resources consulted. The use
of all source material should be explicit in the report. This means that normally ever item in
the reference list will be referred to in the report and every item mentioned in the report will
have an entry in the reference list.
Use IEEE citation style for references
[1] J. K. Author, “Title of paper,” Abbrev. Title of Journal, vol. x, no. x, pp. xxx-xxx,
Abbrev. Month, year.

For example:
[1] J. H. Smith and K. W. Tang, “Efficient algorithms for sorting and synchronization,” IEEE
Trans. Computers, vol. 50, no. 3, pp. 274-285, Mar. 2001.

In this example:
• J. H. Smith and K. W. Tang are the authors.
• "Efficient algorithms for sorting and synchronization" is the title of the paper.
• IEEE Trans. Computers is the abbreviated title of the journal.
• Volume 50, Number 3, pages 274 to 285 are the details of the journal.
• March 2001 is the publication date.
Appendices /Annex
List screenshots of the project.
Note: Screenshots should have figure number and name.
Report Format Standards:

A. Page Number
• The pages from certificate page to the list of
tables/figures/abbreviations/approvals should be numbered in roman starting
from i.
• The pages from chapter 1 onwards should be numbered in numeric starting
from 1. The page number should be inserted at bottom, aligned center.
B. Page Size and Margin
• The paper size must be a page size corresponding to A4.
• The margins must be set as
• Top = 1 in (2.54 cm)
• Bottom = 1 in (2.54 cm)
• Left = 1.25 in (3.17 cm)
• Right = 1 in (2.54 cm)
C. Paragraph Style
• All paragraphs must be justified and have spacing of 1.5.
D. Text Font of Document
• The contents in the document should be in Times New Roman font
• The font size in the paragraphs of document should be 12
E. Section Headings
• Font size for the headings should be 16 for chapter headings, 14 for section
headings, 12 for sub-section headings.
• All the headings should be bold faced.
F. Figures and Tables
• Position of figures and tables should be aligned center.
• The figure caption should be centered below the figure and table captions
should be centered above the table.
• All the captions should be of bold face with 9 font size & font face italic.
Notes:
• Start new chapter from new page.
• Save document in pdf format before print.
Presentation format for Final defence
Introduction to your group member [Name of project and members]
Introduction of the project
Problem statement
Objective
Scope of the project
Used SDLC model
Feasibility analysis
Context Diagram
DFD
E-R Diagram
.
.
Use case Diagram
Gantt Chart
Final outcome
Conclusion
Reference

Guideline For Effective Slide:


• One Main Topic Per Slide: Each slide should focus on one main point or idea. Keep it
simple, don't overload slides with too much information.
• Clear Headings: Use clear and concise headings to tell what each slide is about.
Headings should summarize the main point of the slide.
• Use Simple Transition: Stick to simple transitions that complement your presentation
without being overwhelming.
• Use Bullet Points: Instead of long sentences or paragraphs, use bullet points to list key
ideas. Keep each bullet point short and to the point.
• Big Fonts: Make sure the text on your slides is big enough to read from a distance. Use a
simple font like Arial or Calibri, and make the font size at least 24pt.
• Pictures Speak Louder: Use pictures or images to show what you're talking about. A
picture can often explain things better than words. This doesn’t mean totally overwhelm
your slide with pictures. In general, try to maintain a ratio of 70% text & 30% image.
• Consistent Design: Keep the design of your slides consistent. Use the same colors, fonts,
and layout throughout your presentation.

You might also like