PadhaikoAll subjects

Final Project Report Submission

Project II (ENCT 461)

Open in the Padhaiko app

5 Final Project Report Submission

The Final Project Report is the permanent academic record of your two-semester B.E. Major Project (Project I + Project II). Under the ENCT 461 syllabus, the Final Project Report must be submitted 3 weeks before the end of the eighth semester—one full week prior to the Final Defense and Demonstration—so your supervisor, internal committee, and external examiner can thoroughly review your engineering design, test results, and critical analysis before your viva.

Definition

Final Project Report Submission (3 Weeks Before End)

Under the official Institute of Engineering ENCT 461 syllabus, Final Project Report Submission is the formal completion of comprehensive technical documentation in the department-approved standard format, submitted 3 weeks before the end of the eighth semester. It integrates the refined problem formulation and literature survey from Project I with complete Semester-8 design, implementation, systematic testing, performance evaluation, comparative result analysis, and conclusions.

5.1 Submission Timeline and Departmental Format Compliance

Waiting until two days before the deadline to assemble a 60-to-90-page report almost always causes formatting rejections, broken figure numbers, and missing supervisor signatures. Work backward from the End - 3 weeks deadline:

  1. 14 days before report deadline: Freeze all code, datasets, and test numbers; export final high-resolution plots (300 DPI PNG/SVG) and verified benchmark tables.
  2. 10 days before report deadline: Complete full first draft of Chapters 1 through 6 and run automated reference checks (BibTeX/Zotero) and spell/grammar review.
  3. 5–7 days before report deadline: Submit the complete draft to your assigned supervisor for technical and formatting review, and run the department's plagiarism/similarity check.
  4. 2 days before report deadline: Incorporate supervisor corrections, verify page margins, fonts, Roman vs. Arabic page numbering, list of figures/tables, and print/bind or upload PDFs per department rules.

5.2 Standard Structure of the B.E. Final Project Report

While exact subsection names vary slightly by campus template, an Institute of Engineering Computer Engineering Final Project Report follows a clear, logical narrative from problem to verified outcome.

Standard Chapters and Target Focus in the Final Project Report
Report SectionCore PurposeKey Content Evaluators Inspect
Preliminary PagesFormal metadata, approval, and navigationTitle page, Supervisor/HOD Certificate of Approval, Declaration, Acknowledgement, Abstract (200–300 words), ToC, List of Figures/Tables/Abbreviations
Ch. 1: IntroductionDefine why and whatBackground, Problem Statement, Measurable Objectives, Scope & Limitations, Report Organization
Ch. 2: Literature ReviewPosition work against prior artCritical synthesis of academic papers/existing systems (not copy-pasted abstracts), comparative gap table
Ch. 3: System Analysis & Design / MethodologyExplain how it is engineeredArchitecture diagrams, ER/data schemas, algorithm flowcharts, mathematical/ML formulations, hardware schematics, security/UI design
Ch. 4: Implementation & ToolsDocument how it was builtTech stack justification, module descriptions, core algorithmic pseudocode/logic, deployment setup
Ch. 5: Testing, Results & DiscussionProve how well it worksUnit, integration, and UAT test tables; performance benchmarks; baseline/ablation comparisons; critical interpretation of results
Ch. 6: Conclusion & Future WorkClose the loop against ObjectivesSummary of achievements mapped directly to Ch. 1 objectives, honest limitations, concrete future extensions
References & AppendicesAttribution and reproducibilityStandardized IEEE or APA 7 citations; Appendices (API spec, user manual, extended test logs, hardware BOM)
Recommended Chapter & Section Skeleton (Final Report)Text
Preliminary: Cover -> Approval Certificate -> Declaration -> Abstract -> ToC -> Lists
Chapter 1:   Introduction (1.1 Background, 1.2 Problem Statement, 1.3 Objectives,
                           1.4 Scope and Limitations, 1.5 Organization)
Chapter 2:   Literature Review (Thematic survey + Summary Comparison Table)
Chapter 3:   Methodology / System Design (Requirements, Architecture, Schemas, Algorithms)
Chapter 4:   Implementation (Environment, Modules, Integration, Deployment)
Chapter 5:   Testing, Results and Discussion (Unit/Integration/UAT, Benchmarks,
                                              Comparison with Baselines, Failure Analysis)
Chapter 6:   Conclusion and Future Work
References:  IEEE / APA 7 (every citation in text must appear here and vice versa)
Appendices:  User Guide, Sample Outputs, Extended Test Cases, Dataset/BOM Details

5.3 Writing High-Quality Technical Analysis, Figures, and Citations

Examiners frequently mark down reports that read like a user manual full of login-screen screenshots rather than an engineering thesis. Elevate your report quality with four habits:

  1. Interpret every table and chart in Chapter 5: Never drop a confusion matrix or latency graph without prose. Explain what the number shows, why your method outperformed or underperformed the baseline, and what trade-off emerged (for example, quantization reduced model size by 68% and latency by 2.4x while dropping macro-F1 by only 0.012).
  2. Use vector/high-DPI diagrams with self-contained captions: Every figure and table must be numbered (Figure 3.2, Table 5.1), referenced explicitly in the preceding text ("As shown in Figure 3.2..."), and readable when printed in grayscale or PDF zoom. Avoid blurry phone photos of whiteboards or raw IDE screenshots.
  3. Maintain strict academic integrity and citation hygiene: Paraphrase and synthesize sources in your own words; cite every dataset, pretrained model, external library, paper, and figure adapted from another source using a single consistent style (IEEE [1] or APA 7 (Author, Year)). Never invent fake references or paste unverified AI-generated citations.
  4. Write the Abstract last: In 200 to 300 words, summarize: (a) the problem, (b) your methodology/system, (c) key quantitative/UAT results achieved, and (d) the main conclusion.
AspectWeak Report WritingThesis-Grade Engineering Writing
Screenshots12 full-page screenshots of Sign Up, Login, and Forgot Password2–3 annotated core workflow screens + architecture, schema, and test metrics
Result Description"Figure 5.2 shows our accuracy graph. Our system is very fast and accurate.""Figure 5.2 compares 5-fold macro-F1 across 3 baselines; our temporal model reaches 0.84 (+0.11 over CNN-only) at 18 ms/clip."
Literature ReviewParagraph-by-paragraph summary of 15 disconnected papersThematic grouping ending with a comparison table showing exact gaps your project solves
Code InclusionPasting 40 pages of boilerplate controller/HTML files in Chapter 4Explaining modular logic with clean pseudocode or 15-line core snippets; full repo linked/archived
Example 5.1

Turning Raw Test Logs into a Rigorous Chapter 5 Results & Discussion Section

A Product-Track group built an Offline-First Cooperative Inventory & Ledger App. They have raw logs: 42 passing pytest unit tests, 14 passing API integration tests, a database query speedup from 510 ms to 24 ms after indexing, and a UAT survey of 12 shopkeepers with an average SUS score of 81.5 (where 2 shopkeepers initially struggled with the offline sync indicator). Show how they should structure Chapter 5 ("Testing, Results and Discussion") rather than merely pasting raw logs.

Organize Chapter 5 into logical subsections with summary tables:

  • 5.1 Unit and Integration Testing: Present a concise 8-row representative test-case table (Test ID, Module, Input/Scenario, Expected, Actual, Status) summarizing the 42 unit and 14 integration tests—covering edge cases like negative stock entry, concurrent invoice sync, and duplicate offline UUID idempotency—and place the full automated test output in Appendix B.
  • 5.2 Performance Benchmarking: Present a before/after latency table comparing unindexed vs. composite-indexed ledger queries across 10,000, 50,000, and 100,000 rows (p50 and p95 ms).

Present User Acceptance Testing (UAT) quantitatively and qualitatively:

  • 5.3 User Evaluation: Report task-completion rates across 5 realistic billing/sync tasks for all 12 shopkeepers plus the mean SUS score (81.5, above the standard 68 usability threshold). Highlight that 2 users missed the tiny top-bar sync icon, describe the UI change made (explicit "Pending Sync: 3 Bills" banner), and note re-test improvement.

Write a critical Discussion subsection (Section 5.4):

Compare the offline-first sync workflow against cloud-only POS apps during simulated 2-hour internet blackouts, showing zero billing downtime while acknowledging conflict-resolution limits when two clerks edit the same product price offline simultaneously.

Answer:

Instead of pasting raw console logs, the group structures Chapter 5 into representative Unit/Integration matrices, scaled p50/p95 indexing benchmarks, 12-user UAT + SUS analysis with documented UI fixes, and a critical Discussion comparing against cloud-only alternatives and stating conflict-resolution limits.

Example 5.2

Executing a Pre-Submission Format, Citation, and Integrity Audit

Ten days before the Final Project Report submission deadline (which is 3 weeks before semester end), a three-member group merges their individually drafted Google Docs/LaTeX chapters into one master document. Identify the five most likely integration defects and show how to resolve them systematically.

Check structural and cross-reference consistency:

  1. Broken figure/table numbering & style clash: When Member A writes Chapter 3 and Member B writes Chapter 5 separately, figure captions often jump (Figure 3.4 -> Figure 5.1 missing Figure 4.x), or diagrams use mismatched fonts/colors. Standardize all diagrams to one color palette and regenerate auto-numbered captions (LaTeX \ref or Word Cross-Reference).
  2. Inconsistent terminology & acronyms: Ensure terms (e.g., "XGBoost" vs. "XG-Boost", "ESP-32" vs. "ESP32", "User" vs. "Client") are unified and every acronym is expanded at first mention and listed in the List of Abbreviations.

Audit citation integrity and objective alignment:

  1. Dangling or mixed citations: Merge all references into one BibTeX/Zotero library so [12] in text matches [12] in References under one consistent standard (IEEE or APA 7), and verify every URL/DOI actually resolves.
  2. Objective-to-Conclusion mismatch: Compare Chapter 1 Objectives line-by-line against Chapter 5 Results and Chapter 6 Conclusion; remove or revise any promise in Chapter 1 that was later moved to Limitations/Future Work.

Verify similarity score and supervisor sign-off:

  1. Unintentional high similarity: Run the similarity check early (never on the final morning), rewrite overly close paraphrases from literature surveys in original synthesis, properly quote/cite standard definitions, and send the clean compiled PDF to the supervisor with 5–7 days left for review.
Answer:

The group audits five merger defects—caption/diagram mismatches, inconsistent terminology, dangling/mixed citations, Chapter 1-to-6 objective drift, and similarity spikes—with enough buffer time for supervisor review before the End - 3 weeks deadline.

Viva-Style Questions: Final Project Report Submission

Question 1

When is the Final Project Report submitted under the ENCT 461 syllabus, and why is it due before rather than after the Final Defense?

Official deadline: The Final Project Report must be submitted 3 weeks before the end of the eighth semester, whereas Final Defense and Demonstration take place 2 weeks before the end of the eighth semester.

Purpose of the 1-week reading window: Submitting the report one week ahead gives the internal committee and external examiner time to read the architecture, methodology, test evidence, and results beforehand so they can inspect system depth and ask targeted technical questions during the defense.

Answer:

It is due 3 weeks before the end of the eighth semester—one week prior to Final Defense—so internal and external examiners can review the full technical documentation before evaluating the live demo and viva.

Question 2

How does an Abstract differ from Chapter 1 (Introduction) and Chapter 6 (Conclusion) in a B.E. Final Project Report?

Distinct roles of each section:

  • Abstract (200–300 words): A standalone executive summary placed in the preliminary pages covering the entire project at a glance—problem, approach, key quantitative/UAT results, and overall takeaway.
  • Chapter 1 (Introduction): Sets context, details the problem statement, states measurable objectives, and defines scope/limitations before presenting the methodology.
  • Chapter 6 (Conclusion): Reflects backward on completed evidence from Chapter 5, explicitly confirms how each objective was met, notes remaining limitations, and proposes concrete future work.
Answer:

The Abstract is a concise standalone summary of the problem, method, and headline results; Chapter 1 frames motivation, objectives, and scope; Chapter 6 evaluates completed objectives against Chapter 5 findings and outlines future work.

Question 3

Why is pasting dozens of pages of source code in Chapter 4 or dozens of login/UI screenshots in Chapter 5 discouraged in Institute of Engineering project reports?

Engineering focus over bulk filler: Examiners evaluate design reasoning, algorithmic trade-offs, and test validation—not page count inflated by auto-generated boilerplate code or trivial authentication screens.

Better documentation practice: In Chapter 4, explain modular interactions, data flow, and brief pseudocode or critical 10–20 line algorithmic snippets (linking the full codebase repository or placing brief user guides in an Appendix). In Chapter 5, show structured test matrices, benchmark charts, baseline comparisons, and critical result interpretation.

Answer:

Raw boilerplate code and trivial UI screenshots add bulk without engineering insight; Chapter 4 should explain architecture and core algorithms concisely, while Chapter 5 should present test matrices, benchmarks, and analytical discussion.

Question 4

What should be included in Chapter 5 (Results and Discussion) for a Research-Track project versus a Product-Track project?

Research-Track Chapter 5: Dataset statistics and split protocol, baseline vs. proposed method comparison tables, ablation study results, statistical variance/confusion matrices, failure case analysis, and computational cost (training/inference latency).

Product-Track Chapter 5: Unit and integration test summaries, system performance benchmarks (response latency, throughput, power/memory on hardware), User Acceptance Testing (UAT/SUS) outcomes, security/edge-case validation, and comparison against existing manual or commercial alternatives.

Answer:

Research Track emphasizes fair baseline comparisons, ablations, confusion/error analysis, and compute cost; Product Track emphasizes unit/integration test matrices, system latency/resource benchmarks, UAT/SUS scores, and comparison with existing workflows.

Question 5

If your group used an open-source pretrained model, public dataset, or adapted helper library in Project II, how must that be handled in the Final Project Report?

Explicit attribution and boundary clarity: Cite the original paper, repository, or dataset license accurately in both the body text (Chapters 2, 3, or 4) and the References list.

Distinguish reused vs. original engineering work: State clearly what the third-party component provided (e.g., pretrained backbone weights or MQTT broker) versus what your team designed, fine-tuned, integrated, or evaluated—transparency builds examiner trust and avoids plagiarism flags.

Answer:

Cite every external dataset, pretrained model, and library properly in the text and References, and explicitly distinguish reused components from your group's original design, integration, and evaluation work.

← Progress Report Submission and Presentation IIFinal Defense and Demonstration →