Part 1: Core Concepts (2 Marks)
- BITM Internship Practicum: A mandatory 3-credit professional attachment (minimum 8-12 consecutive weeks) requiring students to apply theoretical knowledge in real-world IT and business management environments under industry supervision.
- Tripartite Governance Model: The collaborative operational framework binding the Academic Institution (Faculty Supervisor), Host Industry Organization (Workplace Mentor), and Student Intern through a structured learning contract.
- Memorandum of Understanding (MoU): A formal bilateral agreement establishing the institutional terms of the internship attachment, defining working hours, resource access, IP rights, and student welfare provisions.
- Non-Disclosure Agreement (NDA): A legally binding contract requiring the intern to maintain absolute secrecy regarding proprietary source code, trade secrets, financial records, customer databases, and operational blueprints encountered during attachment.
- Workplace Code of Conduct: An organization’s formal policy governing professional integrity, punctuality, anti-harassment, data handling, and acceptable use of enterprise computing assets.
Part 2: Structural Frameworks (10 Marks)
1. The Tripartite Governance and Lifecycle Architecture
- | TRIBHUVAN UNIVERSITY / |
- | COLLEGE ADMINISTRATION |
- | (Faculty Supervisor Oversight)|
- Academic Regulations | Evaluation Guidelines
- | MEMORANDUM OF UNDERSTANDING |
- | HOST INDUSTRY ORGANIZATION | | STUDENT INTERN |
- | (Software Company / Bank / | | (Applies Theory to Real Tasks |
- | Fintech / ISP in Nepal) | | Maintains Daily Logbook, |
- | Workplace Mentor Assigned | | Adheres to Code of Conduct) |
2. Four Pillars of Professional IT Ethics (ACM/IEEE Code of Ethics)
- Public Interest: Software engineers and IT professionals shall act consistently with the public interest, prioritizing safety, privacy, and public welfare over short-term employer profits.
- Client and Employer: Act in a manner that is in the best interest of the client and employer, consistent with the public interest and legal frameworks.
- Product Integrity: Ensure that software products and modifications meet the highest professional standards possible (thorough testing, code reviews, security validation).
- Professionalism and Growth: Maintain lifelong learning, advance an ethical approach to the profession, and credit intellectual property accurately.
Part 3: Distinction Tables
| Basis of Comparison | Academic Capstone Project (ITM 448) | Professional Internship Attachment (ITM 498) |
|---|---|---|
| Operational Environment | University lab / Academic classroom | Professional corporate office or IT enterprise |
| Supervision Structure | Guided exclusively by Academic Faculty Supervisor | Co-supervised by Industry Mentor and Faculty Supervisor |
| Scope of Work | End-to-end development of an isolated standalone project | Contributing to large-scale production codebases or enterprise IT ops |
| Evaluation Focus | Academic rigor, architecture diagrams, and thesis defense | Professional work ethic, punctuality, industry contribution, and report |
| Confidentiality Scope | Open academic submission (public defense) | Bound by enterprise NDAs; proprietary secrets redacted from report |
| Timeline Constraints | Flexible academic term deadlines | Strict commercial client sprint deadlines and daily operational standups |
Part 4: Worked Problems & Exam Traps
Problem Archetype: Managing Intellectual Property and NDA Boundaries in Internship Reports
Question: An intern working at a major Nepalese payment gateway implements a novel fraud detection microservice. The company prohibits exposing its proprietary fraud scoring weights and production API endpoints. How must the intern structure the formal TU academic internship report without violating the NDA or failing academic evaluation? Solution:
- Legal & Academic Reconciliation:
- Academic reviewers require evidence of technical problem-solving, architectural competence, and engineering methodologies, not proprietary trade secrets.
- Report Structuring Protocol:
- Obtain Written Clearance: Submit draft report to the Industry Mentor for formal NDA redaction review before academic submission.
- Architectural Abstraction: Replace proprietary internal API endpoints and server IP addresses with RFC 5737 documentation addresses (
192.0.2.1) and generic placeholders (api.example.com/v1/fraud-check). - Algorithm Conceptualization: Explain algorithmic methodology (e.g., Random Forest classifier with SMOTE oversampling for imbalanced data) rather than publishing production model weights or actual customer database schemas.
- Data Sanitization: Mask all real customer identifiers, account numbers, and monetary figures using synthetic sample records.
TU Exam Trap: Students frequently paste raw production database connection strings, client API keys, or unredacted proprietary customer tables into the appendix of their internship report. If discovered during the external viva defense, this constitutes a severe breach of contract resulting in immediate legal action by the host employer and disqualification of the internship submission! Always sanitize and verify NDA clearance.