0% found this document useful (0 votes)
9 views9 pages

Project Report Template - CSS - BWU

The document provides a comprehensive format for preparing project and internship reports at Brainware University, detailing the arrangement of contents, general formatting guidelines, and specific chapter structures for application-based and research-based projects. It includes instructions for printing, binding, and submission, as well as a checklist and reference format. Important notes on common mistakes to avoid are also highlighted to ensure adherence to the guidelines.

Uploaded by

xapow49268
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
0% found this document useful (0 votes)
9 views9 pages

Project Report Template - CSS - BWU

The document provides a comprehensive format for preparing project and internship reports at Brainware University, detailing the arrangement of contents, general formatting guidelines, and specific chapter structures for application-based and research-based projects. It includes instructions for printing, binding, and submission, as well as a checklist and reference format. Important notes on common mistakes to avoid are also highlighted to ensure adherence to the guidelines.

Uploaded by

xapow49268
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/ 9

BRAINWARE UNIVERSITY

398, Ramkrishnapur Road, Barasat, North 24 Parganas, Kolkata - 700 125

FORMAT FOR PREPARATION OF PROJECT REPORT / INTERNSHIP REPORT

1. ARRANGEMENT OF CONTENTS:

The sequence in which the project report material should be arranged and bound should be
as follows:

1. Cover Page & Title Page [Refer Appendix 1]


2. Bonafide Certificate [Refer Appendix 2]
3. Acknowledgement (Singed by Students)
4. Abstract
5. Table of Contents [Refer Appendix 3]
6. List of Tables
7. List of Figures
8. List of Symbols, Abbreviations and Nomenclature
9. Chapters [Chapter 1: Introduction, Chapter 2: Literature Review, Chapter 3:
Theory, Methodology, Materials & Methods, Chapter 4: Results, Analysis &
Discussions, Chapter 5: Conclusion, Future Scope, Limitations.]
10. Appendices
11. References [Refer Appendix 4]

The table and figures shall be introduced in the appropriate places.

2. General Formatting Guidelines

• Font: Calibri throughout the document.


• Font Size: 12pt for all content including text in figures, tables, and appendices. Minimum 8pt
may be used in tables/figures if needed.
• Chapter Title: 16pt bold.
• Chapter Number Line: 14pt regular.
• First-Level Headings: 12pt bold with Initial Capitals.
• Second-Level Headings: 12pt bold.
• Third-Level Headings: 12pt bold italic.
Text must be single spaced. Provide one blank line (12pt) after every paragraph. Insert two blank lines
before each chapter title and one blank line before each heading. Do not leave space between a heading
and the following text.

All text in the report must be justified, which means both left and right alignment must be maintained.

Every figure and code snippet included in the report must be accompanied by a caption. Captions for
figures should be placed below the figure, and captions for code should be placed above the code
block. Captions should be numbered consistently (e.g., Figure 3.1, Code 4.2) and briefly describe the
content or purpose.

3. Sequence of Report Content

The report must follow the exact sequence below. Do not modify the order:

1. Cover Page and Title Page (as per Appendix 1 of the template)
2. Bonafide Certificate (as per Appendix 2)
3. Acknowledgement Page (must be placed after the Bonafide Certificate)
4. Abstract
5. Table of Contents (as per Appendix 3)
6. List of Tables
7. List of Figures
8. List of Symbols, Abbreviations, and Nomenclature
9. Chapters (as per project type)
10. Appendices
11. References (as per Appendix 4)

Note:

• The Acknowledgement Page must be hand-signed by all project group members. Each
student must also clearly write their student code next to their signature.
• On the Cover Page and Title Page, students must include the following details: Student
Code, Registration Number, Roll Number, and Student Name.

4. Chapter Structure Based on Project Type

For Application-Based Projects

1. Chapter 1: Introduction
2. Chapter 2: Objective
3. Chapter 3: Planning
4. Chapter 4: Requirement Analysis
5. Chapter 5: System Flow
o This chapter must include relevant diagrams to represent the logical and functional flow
of the system. Diagrams should include:
▪ Context Level Diagram (CLD)
▪ Data Flow Diagrams (DFD) for Level 0, Level 1 (and Level 2 if required)
▪ Use Case Diagram (if applicable)
▪ Activity Diagram (for system behavior)
▪ Sequence Diagram (to show interaction logic)
▪ Flow Chart (for individual module processes)
6. Chapter 6: Proposed Design
7. Chapter 7: Experimental Result
8. Chapter 8: Future Scope
9. Chapter 9: Conclusion

For Research-Based Projects

1. Chapter 1: Introduction
2. Chapter 2: Literature Review
3. Chapter 3: Theory, Methodology, Materials & Methods
4. Chapter 4: Results, Analysis & Discussions
5. Chapter 5: Conclusion, Future Scope, Limitations

Each chapter must begin on a new page. DO NOT change the chapter names or rearrange their order.

5. Printing and Binding Instructions

• Paper Size: A4, good quality bond paper recommended.


• Binding: Hardbound (Thesis binding).
• Cover Colors:
o BCA – Black
o MCA – Sky Blue

The cover must include the BWU logo, student name, year of graduation, degree name (e.g., Bachelor
of Computer Application), and department.

Each group must submit:

• Two hardbound copies for the University.


• One hardbound copy per group member.
Example: For a group of five students, submit six copies in total.

6. Submission Checklist

At the time of the final evaluation, the following must be submitted:

• Project Report (in prescribed format)


• Final Presentation (PPT format)
• Project Code: Upload code in shared drive (as per instructor’s guidance)

Note: There is no requirement to print the entire source code within the project report.

• For Research-Based Projects, only relevant algorithms or pseudo-code necessary to understand


the methodology should be included.
• For Application-Based Projects, include only the key or representative code segments for each
important module. This may include controller logic, algorithm implementation, database
interaction, or other significant parts that explain system behavior.
7. Reference Format

References must be listed alphabetically by the surname of the first author. The following format
should be used:

Author(s) (Year) ‘Title of the Work’, Journal/Conference Name, Volume(Issue), Page Numbers.

Example: Aritikula, S. and Nandi, S. (1994) ‘Transport Phonomena of Sm Sel – X Asx’, Pramana –
Journal of Physics, Vol.42, No.1, pp.421-425.

The citation style to be used in the report is author-date format (e.g., Sharma, 2022). Each in-text
citation must correspond to a full reference listed in the References section at the end of the report.

For online sources, include the full URL and the date you accessed the website.

Example: Author(s) (Year) ‘Title of the Web Page’, Website Name. Available at:
https://www.example.com/examplepage.html (Accessed: 28 March 2025).

Detailed examples are available in Appendix 4 of the official project report template

8. Important Notes and Common Mistakes

• Do not alter the structure or chapter titles from the template.


• Maintain consistent formatting and justification throughout.
• Include a duly signed Bonafide Certificate.
• Add an Acknowledgement Page immediately after the Bonafide Certificate.
• The Acknowledgement Page must be signed by all group members along with their student
codes.
• Ensure all content including tables, figures, and references are properly formatted and labeled.
• Every figure and code segment must have an appropriate caption.
• Do not include complete code listings; focus on what is essential to understand the design and
implementation.
• Do not list only the domain name for any website in references. Always provide the full URL
and access date.

For any clarification, students are advised to contact their project supervisor or the departmental project
coordinator.
APPENDIX 1[cover page]
TITLE OF PROJECT REPORT
<Font Size 18><1.5 line spacing>

A PROJECT REPORT
<Font Size 14>

Submitted by
<Font Size 14><Italic>

NAME OF THE CANDIDATE(S)


<Font Size 16>

in partial fulfillment for the award of the degree


of
<Font Size 14><1.5 line spacing><Italic>

NAME OF THE DEGREE


<Font Size 16>

IN

BRANCH OF STUDY
<Font Size 14>

NAME OF THE UNIVERSITY

Address
<Font Size 14>
[Title page]

MONTH & YEAR

NAME OF THE PROJECT

Submitted by

[Name]

in partial fulfillment for the award of the degree

of

BACHELOR OF TECHNOLOGY

in

[Department]

BRAINWARE UNIVERSITY
398, Ramkrishnapur Road, Barasat, North 24 Parganas, Kolkata - 700 125
APPENDIX 2
Bonafide Certificate – The Bonafide Certificate shall be in double line spacing using Font Style
Calibri and Font Size 14. The certificate shall carry the supervisor’s signature and shall be followed
by the supervisor’s name, academic designation (not any other responsibilities of administrative
nature), department and full address of the institution where the supervisor has guided the
student.

The term ‘SUPERVISOR’ must be typed in capital letters between the supervisor’s name and
academic designation.

[A specimen of the BONAFIDE CERTIFICATE]

BRAINWARE UNIVERSITY
398, Ramkrishnapur Road, Barasat, North 24 Parganas, Kolkata - 700 125

[DEPARTMENT NAME]

BONAFIDE CERTIFICATE

Certified that this project report “……….TITLE OF THE PROJECT……………..” is the bonafide work of
“…………..NAME OF THE CANDIDATE(S).…………” who carried out the project work under my
supervision.

<<Signature of the Head of the Department>> <<Signature of the Supervisor>>


SIGNATURE SIGNATURE

<<Name>> <<Name>>
HEAD OF THE DEPARTMENT SUPERVISOR
<<Academic Designation>>
<<Department>> <<Department>>
<<Full address of the Dept & College >>
APPENDIX 3
TABLE OF CONTENTS
Chapter Title Page No.
ABSTRACT iii
LIST OF TABLE xvi
LIST OF FIGURES xviii
LIST OF SYMBOLS xxvii
1. INTRODUCTION 1
1.1 GENERAL 1
1.2 . . . . . . . . . . . . . 2
1.2.1 General
1.2.2 ……………..
APPENDIX 4

List of References –The reference material should be listed in the alphabetical order of the first
author. The name of the author/authors should be immediately followed by the year and other
details.

A typical illustrative list given below relates to the citation example quoted above.

REFERENCES

1. Aritikula, S. and Nandi, S. (1994) ‘Transport Phonomena of Sm Sel – X Asx’, Pramana – Journal of
Physics Vol.42, No.1, pp.421-425.

2. Bernard, R.W. and Keiger, C. (1980) ‘Applications of Convolution Theory Operators to Problems
in Univalent Function Theory’, Michigan Mach, J., Vol.27, pp.81–94.

3. Shaw, K.G. and Mckay, N.D. (1984) ‘Open Loop Maximum Time Control of Mechanical Motoring
and its Applications’, Proc.Amer.Contr.Conf., San Diego, CA, pp. 1231-1236.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy