TU BCA Internship Report Writing & Final Viva Defense Guide: Format, Chapters & Examiner FAQ
Author: Bhuban Subedi | Subject: Internship & Project (CAIN404) | Semester: Eighth Semester
In the final semester of the Tribhuvan University (TU) Bachelor of Computer Applications (BCA) program, the Internship Course (CAIN404) serves as the ultimate bridge between academic theories and professional IT workplace practice.
Securing high marks in your internship evaluation requires two key milestones:
1. Submitting an academically rigorous Internship Report adhering strictly to TU FoHSS formatting guidelines.
2. Defending your report before an External University Examiner during the final Viva Voce presentation.
In this master guide, I will outline the exact chapter-by-chapter structure, formatting standards, slide deck preparation rules, and common external examiner questions so you can score an A / A+ grade.
1. Official TU Report Formatting Guidelines
Tribhuvan University Faculty of Humanities and Social Sciences enforces strict typographic and layout standards:
+-------------------+---------------------------------------------------------------+
| Parameter | Mandatory Specification |
+-------------------+---------------------------------------------------------------+
| **Font Family** | Times New Roman (Strictly across all headings and body text). |
+-------------------+---------------------------------------------------------------+
| **Font Sizes** | Major Chapter Heading: **16 pt (Bold, Center)** |
| | Level 1 Subheading: **14 pt (Bold, Left)** |
| | Level 2 Subheading: **12 pt (Bold, Left)** |
| | Body Paragraph Text: **12 pt (Regular, Justified)** |
+-------------------+---------------------------------------------------------------+
| **Line Spacing** | **1.5 Lines** (Single spacing allowed inside tables). |
+-------------------+---------------------------------------------------------------+
| **Page Margins** | **Left (Binding edge): 1.5 inches (3.81 cm)** |
| | Top, Bottom, Right: **1.0 inch (2.54 cm)** |
+-------------------+---------------------------------------------------------------+
| **Page Numbers** | Roman numerals (`i, ii, iii`) for preliminary pages; |
| | Arabic numerals (`1, 2, 3...`) starting from Chapter 1. |
+-------------------+---------------------------------------------------------------+
| **Paper & Binding**| Standard **A4 80 GSM paper**, Hardbound Black/Navy with Gold Foil.|
+-------------------+---------------------------------------------------------------+
2. Standard Document Architecture (Order of Pages)
Your report must be organized in the following sequential order:
PRELIMINARY PAGES (Numbered i, ii, iii...):
1. Outer Cover Page & Inner Title Page
2. Certificate of Recommendation (Supervisor's Signature)
3. Letter of Approval (External Examiner & Department Head)
4. Internship Completion Letter from Sponsoring IT Company
5. Acknowledgments
6. Abstract / Executive Summary (1 page max)
7. Table of Contents
8. List of Tables & List of Figures
9. List of Abbreviations (e.g., API, CRUD, JWT, REST)
CORE REPORT CHAPTERS (Numbered 1, 2, 3...):
├── Chapter 1: Introduction (Background, Objectives, Scope)
├── Chapter 2: Organization Profile (History, Hierarchy, Tech Stack)
├── Chapter 3: Internship Activities & Project Development
├── Chapter 4: System Analysis, Design & Implementation
├── Chapter 5: Key Learnings, Challenges & Problem Solving
└── Chapter 6: Conclusion & Recommendations
APPENDICES & REFERENCES:
├── References / Bibliography (IEEE or APA 7th Edition)
└── Appendix: Sample Code Snippets, UI Screenshots, Weekly Activity Logs
3. Chapter Breakdown & Content Blueprint
Chapter 1: Introduction
- Background of Internship: Why practical exposure is necessary.
- Objectives: What technical and soft skills you aimed to develop.
- Scope & Limitations: Boundaries of the assigned projects.
Chapter 2: Organization Profile
- Corporate background of your internship firm (e.g., Nepali software agency, fintech firm, ISP).
- Organizational chart and department hierarchy.
- Major software products and services offered.
Chapter 3: Internship Tasks & Work Assigned
- Weekly work distribution and timeline (Gantt chart).
- Development environment and tooling (VS Code, Docker, Jira, Git, Postman).
Chapter 4: Core Project Implementation (The Meat of Your Report)
- Real-world system built during the internship.
- Architecture diagrams: DFD Level 0/1, Database ER Diagrams, API Workflow diagrams.
- UI screenshots and technical descriptions of solved engineering challenges.
Chapter 5: Critical Reflection & Analysis
- Gaps identified between college curriculum and industry practice.
- How you resolved unexpected bugs, API rate limits, or deployment errors.
4. Preparing for the Final Viva Voce Defense
The viva presentation lasts approximately 15 to 20 minutes (10 mins presentation + 10 mins Q&A).
+------------------------------------+------------------------------------+
| Recommended Slide Breakdown (12-15 Slides Total) |
+------------------------------------+------------------------------------+
| Slide 1: Title & Student Details | Slide 7-9: Project System Architecture & UI|
| Slide 2: Company Overview | Slide 10: Code Highlights & Innovations|
| Slide 3: Internship Objectives | Slide 11: Challenges Encountered |
| Slide 4: Roles & Tech Stack | Slide 12: Key Learnings & Growth |
| Slide 5-6: Assigned Tasks Timeline | Slide 13: Conclusion & Future Scope|
+------------------------------------+------------------------------------+
5. Top 5 Questions Asked by External Examiners
+---+-----------------------------------------------+-----------------------------------------------+
| # | Question | What the Examiner is Looking For |
+---+-----------------------------------------------+-----------------------------------------------+
| 1 | *"What was your exact individual contribution | Proof that you actually wrote code and weren't|
| | versus the rest of the development team?"* | just a passive bystander on the team. |
+---+-----------------------------------------------+-----------------------------------------------+
| 2 | *"Why did your company choose Stack X over Y | Technical justification (e.g., Node.js vs PHP |
| | (e.g., PostgreSQL instead of MongoDB)?"* | for relational ACID constraints). |
+---+-----------------------------------------------+-----------------------------------------------+
| 3 | *"How did you handle user authentication and | Explanation of JWT tokens, password hashing, |
| | database security?"* | and SQL injection defense. |
+---+-----------------------------------------------+-----------------------------------------------+
| 4 | *"What was the hardest bug you encountered?"* | Evidence of genuine debugging methodology and |
| | | perseverance under pressure. |
+---+-----------------------------------------------+-----------------------------------------------+
| 5 | *"Explain this specific ER relationship from | Verification that you understand relational |
| | your report diagram."* | integrity and database foreign keys. |
+---+-----------------------------------------------+-----------------------------------------------+
Frequently Asked Questions (FAQ)
Q1: What is the minimum duration required for the TU BCA Internship?
Tribhuvan University requires a minimum of 8 to 12 continuous weeks (at least 240 working hours) of documented workplace training at a verified IT company or corporate department.
Q2: What happens if an external examiner spots formatting errors?
Minor typos are noted for correction before final bound submission. However, major structural violations (missing supervisor letters, unformatted citations, plagiarized text) will severely reduce your final grade.
