Part 1: Core Concepts (2 Marks)
- Capstone Project: A comprehensive, culminating academic project where students integrate programming, database, networking, and managerial principles to engineer a functioning software system solving a real-world problem.
- TELOS Feasibility Framework: A five-point evaluation model assessing project viability: Technical (available technology/skills), Economic (cost-benefit ROI), Legal (copyright/data privacy), Operational (organizational fit), and Schedule (delivery timeline).
- Problem Statement: A concise, objective articulation of the specific practical deficiency, operational pain point, or market gap that the proposed software system aims to solve.
- Scope Creep: The uncontrolled, unapproved expansion of project scope beyond original boundaries without corresponding adjustments to time, budget, or resources.
Part 2: Structural Frameworks (10 Marks)
Capstone Project Proposal Lifecycle
- Step 1: Brainstorming & Domain Selection (Health, FinTech, Agriculture, EdTech)
- Step 2: Problem Identification & Preliminary Literature Review
- Step 3: TELOS Feasibility Analysis & Technical Feasibility Check
- Step 4: Proposal Formulation: Problem Statement, Scope, Objectives, Gantt Chart
- Step 5: Formal Proposal Defense & Approval by TU Departmental Committee
Part 3: Distinction Tables
| Basis of Comparison | Project Objective | Project Scope |
|---|---|---|
| Core Nature | Specific, measurable goals the software will achieve | Concrete boundaries of what the software will and will not do |
| Format | Action-oriented verbs (e.g., “To automate invoice billing”) | Explicit lists of system features, modules, and exclusions |
| Time Orientation | Ultimate outcome realized upon project completion | Operational guardrails enforced throughout project execution |
| Evaluation Criterion | Tested during final product acceptance | Audited to prevent scope creep during sprints |
Part 4: Worked Problems & Exam Traps
TELOS Feasibility Evaluation for Capstone Proposals
- Technical: “Can our team build this using React and Node.js with existing university lab hardware?”
- Economic: “Are open-source databases (PostgreSQL) sufficient to avoid commercial software licensing fees?”
- Legal: “Does the app comply with the Nepal Electronic Transaction Act 2063 and privacy norms?”
- Operational: “Will non-technical municipal clerks be able to navigate the dashboard?”
- Schedule: “Can all deliverables be implemented and tested within the 16-week semester?”
TU Exam Trap: In the proposal defense, avoid overly ambitious, vague topics (e.g., “Building an AI Operating System”). TU evaluation committees favor well-bounded, complete enterprise software solutions with clear local business relevance in Nepal.