Progress Report and Presentation I
Open in the Padhaiko app1 Progress Report and Presentation I
Project II (ENCT 461) is the eighth-semester continuation and completion phase of the B.E. Computer Engineering Major Project (4 credits; 100 marks internal evaluation and 50 marks external evaluation). Whereas Project I (ENCT 413) established the problem statement, literature survey, architecture, and an initial Proof of Concept (PoC), Project II demands full-scale implementation, systematic testing, quantitative and user validation, comparative analysis, and final thesis-grade documentation. Its very first formal checkpoint—Progress Report and Presentation I—occurs two weeks after the commencement of the eighth semester.
Progress Report and Presentation I (Week-2 Checkpoint)
Under the official Institute of Engineering ENCT 461 syllabus, Progress Report and Presentation I is the mandatory Phase-II kick-off evaluation held two weeks after the start of the eighth semester. Every group continues its approved Project I topic and selected track (Product, Research, or Internship-based), demonstrates how evaluators' Project I feedback has been incorporated, and presents a concrete, week-by-week execution plan to move from a seventh-semester Proof of Concept to a complete, evaluated final system.
1.1 Transitioning from Project I to Project II
The two weeks between the start of the eighth semester and Presentation I are not meant for starting a new topic from scratch; they are for closing the gap between where Project I ended and where full-scale development begins.
- Preserve topic and track continuity: The approved problem statement, core objectives, and track from Project I remain unchanged. Major pivots are permitted only in exceptional cases with formal supervisor and departmental approval.
- Audit Project I evaluation feedback: Collect every comment raised by your supervisor and the Project I panel—such as missing baselines, weak database normalization, unvalidated sensor calibration, narrow dataset diversity, or security gaps—and convert each comment into a concrete Semester-8 action item.
- Separate "PoC shortcuts" from "Project II engineering": Seventh-semester prototypes often rely on hardcoded paths, small sample datasets, manual scripts, or unstyled screens. Identify every shortcut that must be replaced by clean, maintainable, testable components in Semester 8.
- Lock environment and resource readiness: Confirm that datasets, cloud or local GPU access, embedded hardware spares, and (for internship-based groups) host mentor approvals and anonymized test environments are fully ready before Month 1 slips away.
| Aspect | Project I Final Review (Sem 7) | Project II Presentation I (Sem 8, Week 2) |
|---|---|---|
| Core Purpose | Prove the idea is feasible via a working Proof of Concept (PoC) | Prove the team is ready to execute full-scale build, testing, and evaluation |
| System State | Partial prototype, baseline script, or simulated module | Refined architecture incorporating Project I panel feedback plus post-Sem-7 progress |
| Focus of Panel Questions | Problem validity, literature gap, and PoC viability | Technical bottlenecks, missing modules, test/validation metrics, and realistic timeline |
| Key Deliverable | Project I final progress report | Project II Progress Report I + updated Semester-8 execution roadmap |
1.2 Structure of Progress Report I
Because Presentation I happens only two weeks into the semester, Progress Report I is a focused, high-density engineering status document (typically 8 to 15 pages, formatted in your department's approved template) rather than a full thesis draft.
| Section | Core Content to Include | Common Mistake to Avoid |
|---|---|---|
| 1. Project Identity & Recap | Title, group members, supervisor (and industry mentor if internship track), track, and 1-paragraph approved problem & objectives | Copy-pasting 10 pages of Chapter 1/2 prose from Project I |
| 2. Project I Feedback & Refinements | Traceability table listing each Project I panel comment and the exact design/scope refinement made | Ignoring panel critiques or offering vague promises |
| 3. Current System / Research Status | Honest inventory of completed modules, PoC baseline metrics, dataset/hardware readiness, and known limitations | Claiming "80% done" when only UI mockups exist |
| 4. Refined Architecture / Methodology | Updated system block diagram, database schema, API contracts, or experimental/ablation pipeline for Sem 8 | Showing outdated diagrams that no longer match the codebase |
| 5. Testing & Evaluation Plan | Concrete unit, integration, user-testing, or research benchmark metrics that will prove success | Writing "we will test the system thoroughly" without metrics |
| 6. Sem-8 Work Plan & Division | Week-by-week Gantt schedule (aligned to Month 2, Week N-3, Week N-2) and member-wise task ownership | Assigning one member solely to "documentation" |
+----+-------------------------------+-----------------------------------+-----------------------+
| ID | Project I Evaluator Feedback | Concrete Sem-8 Action / Change | Owner & Target Week |
+----+-------------------------------+-----------------------------------+-----------------------+
| F1 | Dataset lacks low-light cases | Collect 600 dusk/indoor images + | Member A (Weeks 1-4) |
| | | add gamma/noise augmentation | |
+----+-------------------------------+-----------------------------------+-----------------------+
| F2 | No offline fallback on edge | Add local SQLite queue with auto | Member B (Weeks 3-5) |
| | node when Wi-Fi drops | retry sync on reconnect | |
+----+-------------------------------+-----------------------------------+-----------------------+
| F3 | Evaluation used accuracy only | Add macro-F1, confusion matrix, | Member C (Weeks 6-8) |
| | on imbalanced classes | and per-class inference latency | |
+----+-------------------------------+-----------------------------------+-----------------------+1.3 Preparing and Delivering Presentation I
Presentation I is typically a 10-to-12-minute talk followed by 5 to 10 minutes of technical Q&A. A crisp, well-paced deck demonstrates control over the project before heavy coding and experimentation consume the middle of the semester.
| Track | What Evaluators Want to See at Week 2 | Live / Visual Evidence to Bring |
|---|---|---|
| Product Track | Clean modular architecture, API/DB design, clear list of remaining features, and realistic deployment + UAT plan | Short demo of the Project I PoC plus any new backend/UI scaffolding completed over the break |
| Research Track | Verified baseline numbers, refined hypothesis, dataset split hygiene (no data leakage), and planned ablation/comparison experiments | Baseline metric table/plot, sample failure cases, and experimental pipeline diagram |
| Internship-Based Track | Clear boundary between host company's existing system and the team's original Sem-8 engineering contribution, plus NDA-safe demo plan | Architecture showing your module's interfaces, anonymized sample logs, and mentor sign-off confirmation |
Converting Project I Feedback into Progress Report I (Product Track)
A three-member Product-Track group built a Project I Proof of Concept for a Campus Lost-and-Found & Asset Tracking Portal using basic keyword search and local JSON storage. During the Project I final presentation, evaluators pointed out three weaknesses: (1) keyword search fails when students describe items differently, (2) there is no role-based verification to stop false ownership claims, and (3) local JSON storage cannot support concurrent users. Outline how the group should structure Progress Report I and Presentation I two weeks into the eighth semester.
Convert each Project I critique into a concrete Semester-8 engineering task:
- Feedback 1 (Weak search): Replace plain keyword matching with hybrid search combining PostgreSQL full-text search and sentence-embedding similarity for short item descriptions.
- Feedback 2 (No claim verification): Add campus-email OTP verification, an admin/security-desk moderation queue, and an encrypted verification-question workflow before releasing an item.
- Feedback 3 (Local JSON storage): Migrate persistence to a normalized PostgreSQL schema with proper foreign keys, audit logs, and transactional claim locking.
Document Week 1–2 progress honestly:
In Progress Report I, the group includes the finalized 6-table ER diagram, the Dockerized PostgreSQL migration script completed in Week 1, and a benchmark table showing that their prototype embedding search runs in under 40 ms on 1,000 sample listings.
Align Presentation I slides and Month-2 target:
- Slides 1–2: 90-second recap of problem, objectives, and Project I PoC.
- Slides 3–4: Feedback Traceability Matrix and updated 3-tier system architecture.
- Slides 5–6: Live demo of the migrated database + early hybrid search endpoint.
- Slides 7–8: Work division across the 3 members, unit/integration/UAT plan (25 campus testers), and the Month-2 feature-complete target for Presentation II.
The group translates all three Project I critiques into database migration, hybrid search, and claim-verification deliverables, shows early Week 1–2 schema and latency progress in Progress Report I, and structures Presentation I around the updated architecture, live endpoint check, and Month-2 milestone targets.
Preparing Presentation I for a Research-Track Project
A two-member Research-Track group is working on Automated Nepali Sign-Language Gesture Recognition from Video. In Project I, they trained a baseline MobileNetV2 frame classifier on 800 self-recorded clips (10 gesture classes) and got 78% accuracy, but evaluators warned that (1) random frame splitting leaked frames from the same signer across train and test sets, and (2) frame-only classification ignores temporal motion. Show how the group should organize Progress Report I and Presentation I.
Fix methodological flaws before scaling up:
The group restructures the dataset using signer-independent (leave-one-group-out) splitting so no signer appears in both training and test sets, and re-runs the baseline MobileNetV2 to establish an honest, leak-free baseline (e.g., 64.5% macro-F1).
Define the Semester-8 research methodology and ablation plan: To capture temporal dynamics without heavy compute, the group proposes a two-stage pipeline: MediaPipe hand/pose landmark extraction followed by a lightweight sequence model (BiLSTM vs. 1D-TCN vs. ST-GCN comparison), plus an ablation study comparing RGB-only frames, skeletal keypoints, and fused features.
Structure Progress Report I and Presentation I deliverables: Progress Report I documents the corrected signer-independent split protocol, the honest re-evaluated baseline confusion matrix, a data collection schedule to expand from 10 to 25 classes with 12 distinct signers, and quantitative target metrics (macro-F1, top-1 accuracy, and inference FPS on CPU).
The group fixes train/test signer leakage first to record an honest baseline, specifies a temporal sequence and ablation roadmap in Progress Report I, and uses Presentation I to justify the dataset expansion and comparative experiments scheduled before Month 2.
Viva-Style Questions: Progress Report and Presentation I
When is Progress Report and Presentation I scheduled in ENCT 461, and why is it placed so early in the eighth semester?
Official schedule: Under the ENCT 461 syllabus, Progress Report and Presentation I must be submitted and presented two weeks after the commencement of the eighth semester.
Engineering rationale: Because Project II continues the approved Project I topic rather than starting fresh, an early Week-2 gate ensures groups immediately convert Project I evaluator feedback into concrete Semester-8 tasks, verify hardware/dataset readiness, and lock a realistic schedule before the Month-2 midterm checkpoint.
It takes place two weeks after the eighth semester begins so teams transition immediately from Project I's PoC to full-scale implementation, address prior panel feedback early, and commit to a realistic schedule toward Month 2 and final defense.
Can a group change its entire project topic at Progress Report and Presentation I if they feel bored with their Project I work? Explain the syllabus rule and practical consequences.
Official syllabus rule: The ENCT 461 general procedures explicitly state that students continue their approved major project from Project I based on the selected track, keeping the scope and topic the same while incorporating refinements from prior evaluations.
Practical consequences: Switching to an unrelated topic in Semester 8 forfeits the literature review, design, and PoC work completed in Project I and leaves insufficient time for full implementation, systematic testing, and final report writing (due 3 weeks before semester end). Only supervisor-approved scope refinements—not arbitrary topic abandonment—are expected.
No. Students must continue their approved Project I topic and track, applying refinements from prior evaluations rather than switching topics without formal departmental intervention.
What essential sections must appear in Progress Report I, and how does it differ from the Project I Final Progress Report?
Key sections of Progress Report I:
- Concise project identity and approved objectives recap.
- Feedback traceability matrix showing how Project I panel comments were resolved.
- Current implementation/experiment status and PoC baseline inventory.
- Refined architecture, database/hardware design, or experimental pipeline.
- Explicit testing/validation metrics and Sem-8 Gantt schedule with member-wise ownership.
Difference from Project I Final Report: The Project I report summarized past background study and initial PoC results; Progress Report I is forward-looking, focusing on refinements made since Project I and the execution blueprint for completing and validating the full system in Semester 8.
Progress Report I focuses on a Project I feedback traceability matrix, refined architecture/methodology, concrete testing metrics, and a Semester-8 execution schedule—unlike the Project I report, which documented initial background study and PoC creation.
Suppose during Project I an evaluator criticized your group's Product-Track project for "having no clear evaluation criteria beyond screenshots." How should you address this in Progress Report and Presentation I?
Replace subjective claims with measurable engineering metrics: Define quantitative system metrics (e.g., API response time under 200 ms at 50 concurrent requests, offline sync recovery rate, crash-free session rate) alongside structured User Acceptance Testing (UAT) criteria (e.g., task completion rate and System Usability Scale score across 15–20 target users).
Embed the metrics into the Sem-8 timeline: Present a test plan table in Progress Report I showing which test runs in which week, who owns the test harness, and what pass/fail threshold must be met before Presentation II (Month 2) and final submission.
Address the critique by defining quantitative system benchmarks (latency, reliability, resource use) and a structured User Acceptance Testing protocol with target pass thresholds and scheduled test weeks in Progress Report I.
What extra checks must an Internship-Based Track group include in Progress Report and Presentation I compared to a campus Product-Track group?
Boundary of original academic work: The group must clearly distinguish the host organization's pre-existing proprietary codebase or infrastructure from the specific modules designed and implemented by the students for ENCT 461.
Confidentiality and mentor alignment: They must confirm written alignment with their prospective industry mentor on using anonymized/synthetic datasets and sanitized architecture diagrams so that Month-2 demos, the final bound report, and the external defense can proceed smoothly without NDA violations.
An Internship-Based Track group must explicitly separate its original Sem-8 engineering deliverables from the host company's existing system and document NDA-compliant demo/data arrangements approved by both the industry mentor and department supervisor.