BIT Project Work

Nature of Project

The project work should include development of an application/system software. Students are highly recommended to implement relevant algorithms, theories and concepts that they have learned. The project should be practiced by following analysis, design, implementation and testing phases. The project can be done in group with at most three members in each group. For the implementation of the project, students can choose appropriate language technologies as per comfort and skills. While implementing the project, students should be able to write their own program modules rather than relying on predefined APIs or plugins except in some unavoidable circumstances.

Phases of Project

1. Proposal Submission and Presentation: Students must submit and present project proposal on 3rd to 4th week of start of the seventh semester.
2. Mid-Term: Students must submit progress report and defend midterm progress of their project work on the 10th to 11th week of the seventh semester.
3. Final Submission: Students must submit and defend the project work during the last week of the seventh semester but before the final board examination. The final defense will include a viva voce followed by a demonstration of the project. The final defense will be conducted by an evaluation committee with an external from the university. Students must submit the project final report to their respective department of college/campus at least 10 days before the final defense date. The report should be submitted in the standard prescribed format. A hard/soft copy of the report should be made available to the external examiner a week before the presentation date.

Provision of Supervision

The supervisor should be a regular faculty of the campus/college. The role of the supervisor is to provide appropriate guidance to the students throughout the project. A supervisor can supervise at most three groups of the project in a section. The supervisor should rigorously supervise, monitor, provide feedback, and evaluate the project groups under his/her supervision.

Evaluation Scheme

1. Proposal Defense – 10% of 100 Marks (2 Marks Head/Program Coordinator + 6 Marks Supervisor + 2 Marks Internal Examiner)
2. Midterm – 20% of 100 Marks (3 Marks Head/Program Coordinator + 14 Marks Supervisor + 3 Marks Internal Examiner)
3. Final Defense – 70% of 100 Marks (5 Marks Head/Program Coordinator + 40 Marks Supervisor + 5 Marks Internal Examiner + 20 Marks External Examiner)

a. Evaluation Committee

• HOD/Coordinator of the campus/college
• Project Supervisor (Regular faculty of the campus/college)
• Internal Examiner (Regular faculty of the campus/college)
• External Examiner (Allocated from university at the final defense)

b. Marks Allocation

Of the total 100 marks, 80 are considered internal marks and 20 are considered final external marks. Students must pass both separately, scoring at least 32 and 8 marks respectively.

c. Focus of the Evaluation

• Presentation Skills
• Level of Work and Understanding (Level of Analysis, Design, Implementation, Testing, Result Analysis done for the project)
• Project Report
• Viva/Question Answer
• Demonstration of the project
• Teamwork and Contribution

Roles and Responsibilities

• HOD/Coordinator: Coordinates with the supervisor, internal examiner, external examiner, and students. Monitors students' project progress in coordination with the respective supervisors. Responsible for arranging the proposal defense, midterm, and final defense, and participates in and evaluates each of these.
• Project Supervisor: Supervises students' project throughout the semester. Should rigorously provide feedback and guidance, monitor project progress, and participate in and evaluate the proposal defense, midterm, and final defense.
• Internal Examiner: Evaluates the students' project during the different evaluation phases, participating in and evaluating the proposal defense, midterm, and final defense.
• External Examiner: Evaluates the students' project during the final defense, participating in and evaluating the viva voce, presentation, and demonstration session.
• Student: Responsible for development of the project, project report preparation, and defending the project work at each evaluation phase. Despite being group work, each student should have equal role and responsibilities in the project, as each student is evaluated individually and should be able to demonstrate their individual contribution. Students should maintain a log of visits with their supervisors at different dates during their work, including technical feedback received.

Report Contents

1. Prescribed Content Flow for the Project Proposal

1. Introduction
2. Problem Statement
3. Objectives
4. Methodology
   • a. Requirement Identification
     • i. Study of Existing System / Literature Review
     • ii. Requirement Analysis
   • b. Feasibility Study
     • i. Technical
     • ii. Operational
     • iii. Economic
     • iv. Schedule (Gantt chart showing the project timeline)
   • c. High Level Design of System (Methodology of the proposed system / Flow Charts / Working Mechanism of Proposed System / Description of Algorithms)
5. Expected Outcome
6. References

2. Prescribed Content Flow for the Project Report

1. Cover & Title Page
2. Certificate Page
   • i. Supervisor Recommendation
   • ii. Head / Program Coordinator, Supervisor, Internal and External Examiners' Approval Letter
3. Acknowledgement
4. Abstract Page
5. Table of Contents
6. List of Abbreviations, List of Figures, List of Tables
7. Main Report
8. References
9. Bibliography (if any)
10. Appendices (Screenshots + Snippets of major source code components + Log of visits to supervisor)

3. Prescribed Chapters in the Main Report

Chapter 1: Introduction

• 1.1. Introduction
• 1.2. Problem Statement
• 1.3. Objectives
• 1.4. Scope and Limitation
• 1.5. Development Methodology
• 1.6. Report Organization

Chapter 2: Background Study and Literature Review

• 2.1. Background Study (Description of fundamental theories, general concepts and terminologies related to the project)
• 2.2. Literature Review (Review of the similar/relevant projects, theories and results by other researchers)

Chapter 3: System Analysis

• 3.1. System Analysis
  • 3.1.1. Requirement Analysis
    • i. Functional Requirements (Illustrated using use case diagram/use case descriptions)
    • ii. Non-Functional Requirements
  • 3.1.2. Feasibility Analysis
    • i. Technical
    • ii. Operational
    • iii. Economic
    • iv. Schedule
  • 3.1.3. Analysis (May be Structured or Object Oriented)
    • If structured approach: Data modelling using ER Diagrams; Process modelling using DFD
    • If object oriented approach: Object modelling using Class and Object Diagrams; Dynamic modelling using State and Sequence Diagrams; Process modelling using Activity Diagrams

Chapter 4: System Design

• 4.1. Design (May be Structured or Object Oriented as per the approach followed in the analysis chapter)
  • If structured approach: Database Design (Transformation of ER to relations and normalizations); Forms and Report Design; Interface and Dialogue Design
  • If object oriented approach: Refinement of Class, Object, State, Sequence and Activity diagrams; Component Diagrams; Deployment Diagrams
• 4.2. Algorithm Details

Chapter 5: Implementation and Testing

• 5.1. Implementation
  • 5.1.1. Tools Used (CASE tools, Programming languages, Database platforms)
  • 5.1.2. Implementation Details of Modules (Description of classes/procedures/functions/methods/algorithms)
• 5.2. Testing
  • 5.2.1. Test Cases for Unit Testing
  • 5.2.2. Test Cases for System Testing
• 5.3. Result Analysis

Chapter 6: Conclusion and Future Recommendations

• 6.1. Conclusion
• 6.2. Future Recommendations

References

While writing the above chapters, students should avoid basic definitions. They should relate and contextualize the above-mentioned concepts with their project work.

Citation and Referencing

The listing of references should be listed in the references section. The references contain the list of articles, books, URLs, etc. that are cited in the document. The books, articles, and others that were studied but are not cited in the document can be listed in the bibliography section. The citation and referencing standard should be the IEEE referencing standard. The text inside the document should be cited in IEEE style. The IEEE referencing standard can be found on the web.

Report Format Standards

A. Page Number

The pages from the certificate page to the list of tables/figures/abbreviations/approvals should be numbered in roman starting from i. The pages from Chapter 1 onwards should be numbered in numeric starting from 1. The page number should be inserted at the bottom, aligned center.

B. Page Size and Margin

The paper size must correspond to A4. The margins must be set as:

• Top = 1 in (2.54 cm)
• Bottom = 1 in (2.54 cm)
• Left = 1.25 in (3.17 cm)
• Right = 1 in (2.54 cm)

C. Paragraph Style

All paragraphs must be justified and have spacing of 1.5.

D. Text Font of Document

• The contents in the document should be in Times New Roman font.
• The font size in the paragraphs of the document should be 12.

E. Section Headings

Font size for the headings should be 16 for chapter headings, 14 for section headings, and 12 for sub-section headings. All headings should be bold-faced.

F. Figures and Tables

Position of figures and tables should be aligned center. The figure caption should be centered below the figure, and table captions should be centered above the table. All captions should be bold-faced with 12 font size.

Final Report Binding and Submission

• No. of Copies: 3 (College Library + Self + Dean Office)
• Look and Feel: Golden Embracing with Black Binding
• A final approved signed copy of the report should be submitted to the Dean Office, Exam Section, Institute of Science and Technology, Tribhuvan University.