Proposal Report Submission and Presentation
Open in the Padhaiko app5.1 Preparation of brief project proposal including objective and methodology
Once the Week-2 Concept Note passes initial screening, the group prepares a formal Project Proposal due within three weeks of semester start. While the concept note answered "Is this topic worth pursuing?", the proposal answers "Exactly how will you design, engineer, schedule, and verify this project across Project I and Project II?"
Major Project Proposal
A project proposal is a structured engineering blueprint (typically 8 to 15 pages in department-approved format) submitted before full development begins. It expands the approved concept note into formal background and literature synthesis, measurable objectives, clear scope, detailed methodology and architecture, justified software/hardware stack selection, a Gantt work plan, expected deliverables, and verified references.
5.1.1 Standard Proposal Structure and Section Purposes
Departments provide an official formatting template (cover page, margins, font, citation style—usually IEEE). Never improvise headings when an official template is issued; map your content cleanly into these standard sections:
| Proposal Section | Key Contents Required | Quality Check |
|---|---|---|
| Title Page & Declaration | Course code (ENCT 413), project title, track, up to 3 member names/roll numbers, supervisor (and industry mentor if internship) | Matches department cover template exactly |
| 1. Introduction & Background | Domain context, problem statement, motivation, and operational/research urgency | Grounded in evidence, free of vague hype |
| 2. Objectives & Scope | 1 general objective + 3–4 SMART specific objectives; explicit Project I vs. Project II scope and out-of-scope exclusions | Every objective is testable at defence |
| 3. Literature Review & Existing Systems | Thematic synthesis of 12–20 papers + comparison table of existing products/workflows + isolated gap | Clearly links prior work to chosen baseline |
| 4. Methodology | End-to-end system block diagram, pipeline/workflow, core algorithms/models, data flow, and testing/evaluation plan | Concrete enough that another engineer could follow the pipeline |
| 5. Tools, Technologies & Resources | Justified selection of languages, frameworks, databases, hardware/sensors, datasets, and cost estimate | Justifies why each tool fits constraints |
| 6. Work Plan (Gantt Chart) | Week-by-week schedule for Semester 7 (and high-level Semester 8 roadmap) with task ownership | Leaves buffer before Week 13/14 final report |
| 7. Expected Outcomes & References | Measurable Project I PoC + Project II deliverables, plus IEEE/APA bibliography | Every in-text citation matches reference list |
5.1.2 Writing Rigorous Objectives and Methodology
- General vs. Specific Objectives: Write one overarching general objective stating the system/study goal, followed by 3–4 specific objectives using verifiable action verbs (curate, design, implement, integrate, benchmark, evaluate). Each specific objective should correspond to a deliverable you can demonstrate or measure.
- Methodology that goes beyond buzzwords: Break your methodology into four concrete sub-parts:
- System Architecture / Block Diagram: Show data sources, preprocessing, core logic/model, storage, and client/output interfaces.
- Dataset or Requirement Gathering Plan: Specify sample size, labeling method, ethical/privacy handling, or field-study protocol.
- Core Algorithmic / Engineering Logic: Name the exact model architecture, routing/scheduling algorithm, encryption scheme, or API pattern, plus inputs and outputs.
- Validation & Evaluation Plan: Define how you prove it works—unit/integration tests, latency targets, confusion matrix, macro-F1, BLEU, or user acceptance testing.
Task / Milestone | W1-2 | W3 | W4-5 | W6-7 | W8-9 | W10-11 | W12 | W13-14
-------------------------------+------+----+------+------+------+--------+-----+-------
1. Group, Track & Concept Note | [##] | | | | | | |
2. Proposal & Defence | | [#]| | | | | |
3. Data / Env & Design Docs | | | [##] | | | | |
4. Core Methodology / Baseline | | | | [##] | [##] | | |
5. PoC Integration & Testing | | | | | | [##] | [#] |
6. Progress Report (2 wks pre) | | | | | | | [#] |
7. Final Project I Presentation| | | | | | | | [##]5.2 Selection of software tools, technologies, and resources (programming languages, frameworks, databases, etc)
In a proposal viva, examiners rarely penalize you for choosing PostgreSQL over MongoDB or PyTorch over TensorFlow—unless you cannot explain why. Section 5.2 requires justified engineering selection based on workload requirements, team skill, hardware constraints, licensing, and deployment cost.
Engineering Technology & Resource Selection
Technology and resource selection is the documented decision process of matching project requirements (data structure, concurrency, latency, offline capability, embedded memory, budget) to specific programming languages, frameworks, databases, hardware components, compute platforms, and datasets—explicitly comparing viable alternatives and stating why the chosen stack is optimal.
| Stack Layer | Common Options | Key Decision Factor to State in Proposal |
|---|---|---|
| Programming Language | Python, C/C++, Java, TypeScript/JS, Rust, Go | ML/data ecosystem (Python), bare-metal/RTOS timing (C/C++), cross-platform mobile/web (TS/Dart), type safety & concurrency |
| Backend / Web / Mobile Framework | FastAPI, Django, Express/NestJS, Spring Boot, React/Next.js, Flutter | API throughput, async support, built-in auth/ORM speed, offline mobile capability (Flutter/React Native) |
| Database & Storage | PostgreSQL, MySQL, SQLite, MongoDB, Redis, TimescaleDB | Relational ACID integrity & joins (PostgreSQL), embedded local offline storage (SQLite), time-series telemetry (TimescaleDB), unstructured docs (MongoDB) |
| ML / Vision / NLP Stack | PyTorch, scikit-learn, ONNX Runtime, TensorFlow Lite, OpenCV, Hugging Face | Training flexibility (PyTorch), classical tabular speed (scikit-learn), mobile/edge quantization (ONNX/TFLite) |
| Hardware & Compute Resources | ESP32, STM32, Raspberry Pi, sensors, campus GPU / Colab / cloud free tier | Pin/ADC needs, power consumption, RAM for edge inference, total BOM cost in NPR, backup compute plan |
Justifying a Technology Stack for an Offline-First Rural Clinic Record & Triage App
A Product Track team is building a tablet-based Offline-First Patient Record and Primary Triage System for rural health posts with intermittent electricity and 3G connectivity. Show how they should justify their software, database, and sync choices in Section 5.2 rather than just listing logos.
Analyze the controlling constraints: The clinic tablet loses internet for hours daily, must store structured patient visit histories reliably with zero silent data loss, and must sync safely to a district server once connectivity returns.
Justify each stack layer against alternatives:
- Mobile Client (Flutter vs. Web-only PWA): Selected Flutter because native Android compilation provides reliable background sync queues, direct local file/SQLite access, and predictable offline UI performance on budget Android tablets.
- Local Storage (SQLite vs. JSON files): Selected SQLite (via Drift/sqflite) for ACID transactions, indexed patient lookup in milliseconds, and structured conflict-flag columns.
- Central Backend & DB (FastAPI + PostgreSQL vs. NoSQL): Selected FastAPI (lightweight async REST endpoints, automatic OpenAPI schemas) with PostgreSQL because patient records, prescriptions, and audit logs require strict relational integrity and foreign-key constraints.
- Sync Mechanism: Timestamped delta sync with idempotent UUID primary keys so flaky 3G retries never create duplicate patient visits.
By tying Flutter to reliable Android offline storage, SQLite to local ACID transactions, FastAPI + PostgreSQL to relational medical integrity, and UUID delta sync to flaky 3G resilience, the team transforms a bare tool list into a defensible engineering justification.
5.3 Proposal report submission, presentation in department approved format within 3 weeks after the commencement of seventh semester
Under ENCT 413, the Proposal Report must be submitted and presented in the department-approved format within three weeks after the commencement of the seventh semester. Because Week 2 was the Concept Note, you have roughly one week between Concept Note feedback and Proposal submission—meaning drafting literature, methodology, and slides must start in parallel during Week 2.
Proposal Submission and Defence Presentation
Proposal Report Submission and Presentation is the formal Week-3 milestone where each group submits the formatted proposal document (approved by its supervisor, and prospective mentor for internships) and delivers a timed oral slide presentation + Q&A defence before the Department Project Evaluation Committee.
5.3.1 Structuring a Crisp 8–10 Minute Proposal Presentation
Most Institute of Engineering department proposal defences allocate 8 to 10 minutes for presentation followed by 5 to 10 minutes of Q&A. Do not read paragraphs off dense slides. Aim for 10 to 12 clean visual slides:
| Slide # | Slide Title | What to Show (Keep Text Minimal) | Target Time |
|---|---|---|---|
| 1 | Title & Team | Project title, track badge, member names/rolls, supervisor (and mentor) | 20 sec |
| 2 | Problem Statement & Motivation | 3 bullet pain points + 1 photo, chart, or field evidence | 60 sec |
| 3 | Objectives & Phased Scope | 1 general + 3–4 SMART objectives; clear Sem 7 vs. Sem 8 split | 60 sec |
| 4 | Literature & Existing Systems | Clean comparison matrix (4–6 rows) highlighting the exact gap | 75 sec |
| 5–6 | Proposed Methodology & Architecture | Large readable block/pipeline diagram + explanation of core algorithm/logic | 120 sec |
| 7 | Tools, Dataset & Resources | Compact stack table + confirmed dataset/hardware proof | 45 sec |
| 8 | Expected PoC & Evaluation Metrics | Exact Project I demo target + metrics you will measure | 45 sec |
| 9 | Work Plan (Gantt Chart) | 14-week timeline with named member leads | 30 sec |
| 10 | Risks & Mitigation (Optional/Backup) | Top 2–3 risks (data, hardware) and fallback plans | 20 sec |
| 11 | References & Thank You | Key 5–8 references in IEEE format | — |
5.4 Approval of project proposal by the department
Following the presentation and committee review, the department issues its formal approval decision on the project proposal. This approval acts as the official green light to execute the Initial Project Development Phase (Chapter 6).
Departmental Approval of Project Proposal
Proposal Approval is the official academic clearance granted by the Department Project Committee confirming that the group's objectives, literature grounding, engineering methodology, resource plan, and Gantt schedule meet B.E. Project I standards. Approval may be Unconditional, Conditional (with required revisions), or Deferred/Re-defend.
| Decision Outcome | Meaning | Immediate Action Required |
|---|---|---|
| Approved | Proposal accepted as presented | Save signed approval sheet; lock baseline scope and start Chapter 6 setup immediately |
| Approved with Minor Revisions | Core idea sound, but committee requested clearer metrics, narrowed scope, or updated diagram/Gantt | Incorporate every panel comment into the proposal PDF, get supervisor sign-off, and resubmit within the given deadline (usually 3–5 days) |
| Major Revision / Re-Presentation | Methodology flawed, missing data feasibility, insufficient engineering complexity, or unclear member roles | Meet supervisor urgently, overhaul methodology or problem scope, validate data/prototype early, and appear for re-defence |
Handling Tough Panel Questions and Securing Proposal Approval
During a Week-3 Proposal Presentation for a Network Intrusion Detection System (Research Track), an examiner challenges the group: "Public datasets like KDD99 and NSL-KDD are twenty years old. Why should we approve another classifier trained on outdated traffic?" Outline how the group should answer live in the viva and update its proposal if conditional approval is granted.
Acknowledge the examiner's technical point directly: Do not argue defensively that KDD99 is fine—the examiner is completely right that 1999 DARPA traffic lacks modern TLS, IoT, and HTTP/2 attack patterns.
Pivot to a modern dataset and realistic experimental design:
Explain live: "We agree KDD99 is obsolete. While we used NSL-KDD only to verify our baseline pipeline, our primary experiments use CIC-IDS2017 / CSE-CIC-IDS2018 (or UNSW-NB15 / a small captured local campus lab traffic trace using Scapy/Zeek) containing modern DoS, brute-force, and encrypted flow features, evaluated with time-aware / session-grouped splits so there is no flow leakage."
Log the revision cleanly for final proposal approval: Update Section 4 (Methodology) and Section 5 (Dataset & Tools) of the proposal report to replace KDD99 with UNSW-NB15 / CIC-IDS2017 + local Zeek flow extraction, include session-split validation to prevent data leakage, obtain supervisor confirmation, and submit the revised proposal for final approval.
The team concedes that KDD99 is outdated, proposes modern UNSW-NB15 / CIC-IDS2017 flow benchmarks plus local Zeek packet captures with leak-free session splits, and documents the dataset upgrade in the revised proposal to secure committee approval.
Viva-Style Questions: Proposal Report and Presentation
What is the official syllabus deadline for submitting and presenting the Project Proposal Report in ENCT 413, and what must happen before you submit it?
Official deadline: Section 5.3 mandates proposal report submission and presentation in the department-approved format within 3 weeks after the commencement of the seventh semester.
Prerequisites before submission:
- The Week-2 Concept Note must be screened/approved (incorporating any committee feedback).
- The proposal must follow the exact department template (cover, headings, citation format).
- The assigned supervisor (and prospective industry mentor for the internship track) must review and endorse the proposal prior to committee submission.
The proposal must be submitted and presented within 3 weeks of the seventh semester starting, formatted in the department-approved template and reviewed/approved by the supervisor (plus prospective mentor if on the internship track).
During a proposal defence, an examiner asks: "Why did you choose PostgreSQL and FastAPI instead of MongoDB and Node.js?" What constitutes a strong engineering answer vs. a weak answer?
Weak answer: Saying "Because we already know Python" or "Because FastAPI is trending on GitHub" shows personal convenience rather than engineering analysis.
Strong engineering answer: Tie each choice directly to system constraints: "Our domain has strict relational entities (users, devices, audit transactions) requiring ACID guarantees and complex joins, which PostgreSQL enforces natively without schema drift. FastAPI gives native async I/O, Pydantic request validation, and direct integration with our Python PyTorch/NumPy inference pipeline without inter-language IPC overhead."
A weak answer cites personal familiarity or hype; a strong engineering answer maps workload requirements (ACID integrity, joins, ML pipeline integration, schema validation, latency) to the chosen tools and explains why alternatives fit less well.
What are the four essential components of a strong Methodology section in a Project I proposal?
Four methodology pillars:
- System Architecture / Pipeline Diagram: Visual block diagram showing inputs, processing modules, storage, and outputs.
- Data or Requirement Acquisition Plan: Dataset sources, sampling/collection protocol, annotation rules, or user requirement study.
- Core Algorithmic / Design Logic: Specific models, protocols, hardware circuits, or software patterns transforming inputs into outputs.
- Verification & Evaluation Plan: Exact quantitative metrics, test scenarios, and baseline comparisons proving objectives are met.
A complete methodology covers: (1) system block/architecture diagram, (2) data or requirement acquisition plan, (3) specific algorithms/models/design logic, and (4) verification and evaluation metrics.
Why should a Project I Gantt chart never schedule "Testing & Report Writing" solely in the final week before submission? Give a realistic allocation for a 14-week semester.
Risk of back-loading testing and writing: Integration bugs, model convergence failures, hardware defects, and supervisor formatting reviews always take longer than optimistic estimates. Leaving testing and report writing to the last week guarantees rushed code, unverified claims, and missed the Week-12 Progress Report deadline (two weeks before semester end).
Realistic allocation:
- Weeks 1–3: Group formation, literature scan, Concept Note (Week 2), Proposal & Defence (Week 3).
- Weeks 4–6: Dataset/environment setup and System Analysis & Design.
- Weeks 7–10: Core methodology/algorithm implementation and iterative testing.
- Weeks 11–12: Proof-of-concept integration, benchmarking, and Progress Report submission (2 weeks before semester end).
- Weeks 13–14: Slide refinement, live demo verification, and Final Presentation.
Because ENCT 413 requires the Progress Report two weeks prior to semester end, testing and writing must run continuously alongside development from Weeks 7–12 rather than in the final week, leaving buffer time for supervisor review and demo hardening.
What should a group do if its proposal receives "Conditional Approval" after the Week-3 presentation?
Log and address every panel comment: Immediately write down all committee remarks (scope cuts, dataset changes, diagram clarifications, metric additions) right after the defence while feedback is fresh.
Revise and confirm sign-off: Consult the supervisor within 1–2 days, update the affected proposal sections (e.g., Methodology, Scope, Gantt chart), highlight the changes, and submit the corrected proposal for formal departmental sign-off before proceeding with full implementation.
Record all committee feedback immediately, revise the proposal sections with the supervisor's guidance within the stated deadline, and submit the updated document for formal sign-off before locking the design.