TRIBHUVAN UNIVERSITY
Faculty of Institute of Science and Technology
BHAKTAPUR MULTIPLE CAMPUS
Dudhpati-01, Bhaktapur, Nepal
A Project Report On
“Student Information System”
For
Net Centric Computing (CSC 367)
6th semester Project Report submitted in the partial fulfillment of the
requirement for the degree of Bachelor of Science in Computer Science and
Information Technology
Under the supervision of
Ramesh Kharbuja
Submitted By:
Tushar Kunwar
[T.U. Exam Roll No:28346/078]
Submitted To:
Department of Computer Science and Information Technology
TABLE OF CONTENTS
ACKNOWLEDGEMENT ........................................................................................................................1
ABSTRACT..........................................................................................................................................2
INTRODUCTION .................................................................................................................................3
1.1 Background ......................................................................................................................................... 3
1.2 Objectives ........................................................................................................................................... 3
SYSTEM REQUIREMENTS ....................................................................................................................4
2.1 Software Requirements: ...................................................................................................................... 4
2.2 Hardware Requirements...................................................................................................................... 4
TECHNOLOGIES USED .........................................................................................................................5
3.1 Front-End ............................................................................................................................................ 5
3.2 Back-End............................................................................................................................................. 5
3.3 Data Handling ..................................................................................................................................... 5
3.4 Development Tools ............................................................................................................................. 5
SYSTEM DESIGN .................................................................................................................................6
4.1 MVC Architecture Overview .............................................................................................................. 6
4.2 Data Flow:........................................................................................................................................... 6
MODULES DESCRIPTION .....................................................................................................................7
FUTURE ENHANCEMENTS & CONCLUSION ........................................................................................ 10
6.1 Future Enhancements ........................................................................................................................ 10
6.2 Conclusion ........................................................................................................................................ 10
REFERENCES .................................................................................................................................... 11
APPENDIX ........................................................................................................................................ 12
Screenshots ............................................................................................................................................ 12
TABLE OF FIGURES
Figure 1:Details Page................................................................................................................................... 12
Figure 2: Add Details ................................................................................................................................... 12
Figure 3: Edit Details ................................................................................................................................... 13
Figure 4: After Editing Details ..................................................................................................................... 13
Figure 5: Delete Page .................................................................................................................................. 14
Figure 6: After deletion ............................................................................................................................... 14
Figure 7: Mobile View with Bootstrap Responsive Design ......................................................................... 15
ACKNOWLEDGEMENT
I would like to express my deepest gratitude to Mr. Ramesh Kharbuja, my project supervisor at
Bhaktapur Multiple Campus, for his invaluable guidance, unwavering support, and expert advice
throughout this project. His insightful feedback and encouragement were pivotal in shaping the
direction and quality of this work.
My sincere thanks to Mr. Sushant Poudel, CSIT Coordinator, for fostering an excellent
academic environment and providing the resources necessary for this project’s success.
I am also grateful to my peers for their constructive discussions and motivation, which enriched
my perspective and problem-solving approach.
Finally, I acknowledge everyone who contributed directly or indirectly to this project. Their
support made this journey both rewarding and enlightening.
1
ABSTRACT
In the era of digital transformation, academic institutions are increasingly relying on
automated systems for efficient data management. This project presents a web-based
Student Information System developed using [Link] Core MVC, designed to
streamline the management of student data such as exam roll numbers, TU
registration numbers, semesters, and gender categorization.
The system follows the Model-View-Controller architectural pattern, ensuring a
clean separation of concerns, maintainability, and scalability. With an easy-to-use
interface and efficient backend powered by SQL Server, the system allows
administrative users to perform CRUD operations on student records effectively.
Though the current system focuses solely on basic information management, it lays
a strong foundation for future enhancements such as result publication, attendance
tracking, and integrated analytics.
2
INTRODUCTION
1.1 Background
Managing student information in educational institutions is a critical task that directly impacts
administrative efficiency, academic planning, and decision-making processes. Traditionally,
institutions maintained student records manually, which often led to issues such as data
duplication, inconsistency, and difficulty in retrieval. As the volume of data increases with student
enrollment, manual systems become more prone to errors and time-consuming tasks.
To address these challenges, this project proposes the development of a Student Information
System (SIS) using [Link] Core MVC, a modern web development framework by Microsoft.
The system provides a centralized platform for managing student data such as exam roll numbers,
Tribhuvan University (TU) registration numbers, semester tracking, and gender categorization. It
enables administrative users to add, view, update, and delete student records with ease, while
ensuring data consistency and security.
This web-based system aims to reduce manual work, enhance data accuracy, and improve overall
workflow in academic administration.
1.2 Objectives
The main objectives of the Student Information System project are:
• To create a user-friendly web application for managing student records in a structured and
efficient way.
• To enable administrative staff to perform CRUD (Create, Read, Update, Delete) operations
securely.
• To store and retrieve student information using unique identifiers like roll number and TU
registration number.
• To implement the project using modern web development tools and best practices such as
the MVC architecture.
• To provide a base system that can be extended with additional features like result
management, attendance tracking, and student login in the future.
3
SYSTEM REQUIREMENTS
2.1 Software Requirements:
Component Specification
Operating System Windows 10 or later
IDE/Editor Visual Studio 2022 (Community/Professional)
Framework [Link] Core (.NET 6 or later)
Programming Language C#
Front-End Technology HTML, CSS, Bootstrap, JavaScript
Database Microsoft SQL Server
Web Browser Chrome, Edge, Firefox (latest versions)
2.2 Hardware Requirements
Component Minimum Requirement
Processor Intel Core i3 or equivalent
RAM 4 GB (8 GB recommended)
Storage 500 MB of free disk space for installation
Display 1366×768 resolution or higher
Network Stable internet connection (for hosting/testing)
2.2 Dependencies:
• [Link] Core Libraries – Includes runtime and core libraries for MVC, routing, and
dependency injection.
• Razor Runtime Compilation – Allows real-time rendering of views without rebuilding
the project.
• Bootstrap CDN or Local Files – To apply responsive and consistent UI styling across
all pages.
4
TECHNOLOGIES USED
3.1 Front-End
• HTML5 & CSS3 – Used for structuring and styling the web pages.
• Bootstrap 5 – Provides responsive layout and pre-designed UI components.
• Razor Views – Enables embedding of C# code into HTML for dynamic content
rendering.
3.2 Back-End
• [Link] Core MVC (C#) – Main framework used for application development
following the MVC pattern.
• Controllers & Models – Handle the flow of data and define the logic and structure of
contact entities.
• DataAnnotations – Used for form validation and enforcing rules on user input.
3.3 Data Handling
• In-Memory List – Temporarily stores contact data during runtime (no database used).
• LINQ (Language Integrated Query) – Enables efficient searching and filtering of
contact data.
3.4 Development Tools
• Visual Studio / Visual Studio Code – IDEs used to write, build, and debug the
application.
• Web Browsers (Chrome, Edge, Firefox) – Used to run and test the web application
interface.
5
SYSTEM DESIGN
4.1 MVC Architecture Overview
The system follows a layered MVC architecture:
• Model: Contains classes and validation logic.
• View: Razor views render UI and accept input.
• Controller: Handles logic and routes between model and view.
4.2 Data Flow:
The data flow in the application follows the typical MVC pattern where user interactions are
routed through controllers, processed with models, and rendered in views. Here's a simplified
view of the flow:
User → Razor View → Controller → Model → In-Memory Data → View
6
MODULES DESCRIPTION
The Student Information System is divided into several functional modules, each responsible for
specific tasks. These modules interact seamlessly to provide a smooth and efficient user
experience.
1. Student Management Module
This is the core module of the system. It allows administrators to manage student records through
CRUD operations.
Features:
• Add new student details
• Edit existing student records
• Delete student information
• View list of all students
Data Fields Managed:
• Full Name
• Exam Roll Number
• TU Registration Number
• Semester
• Gender (Male, Female, Other)
2. User Interface (UI) Module
This module handles the presentation layer. It provides an intuitive and responsive interface using
Razor views and Bootstrap for styling.
Features:
• Forms for adding and editing students
• Dynamic tables for displaying student lists
• Input validation and error handling messages
• Responsive design compatible with multiple devices
7
3. Controller Logic Module
This module acts as the bridge between the UI and data handling. It processes input from the user,
performs logic, and controls the flow of data.
Main Controller:
• StudentController
o Handles all HTTP requests (GET, POST) related to student operations
o Manages routing to appropriate views and actions
4. Data Access Module
Responsible for communication with the database using Entity Framework Core.
Features:
• Maps Student model to database table
• Automates CRUD operations
• Uses LINQ queries for efficient data manipulation
• Ensures secure and optimized data access
Key Concepts Implemented:
1. Model-View-Controller (MVC) Architecture
• Clean separation of concerns for better structure, readability, and maintainability.
2. Entity Framework Core (EF Core)
• ORM (Object-Relational Mapping) for interacting with SQL Server using C# classes and
LINQ.
3. CRUD Operations
• Full implementation of Create, Read, Update, and Delete functionalities for student
records.
4. Razor View Engine
• Used for dynamic content rendering in Views with C# and HTML.
8
5. Dependency Injection
• Built-in support in [Link] Core for injecting services like DbContext.
6. SQL Server Database Integration
• Persistent storage of student information using structured schema via EF Core migrations.
9
FUTURE ENHANCEMENTS & CONCLUSION
6.1 Future Enhancements
While the current version of the Student Information System provides essential functionalities
for student data management, several features can be added to enhance its usefulness and
scalability in the future:
1. User Authentication and Role Management
Add login and role-based access control so that only authorized users (e.g., Admin,
Teacher) can access or modify student data.
2. Search and Filter Functionality
Allow users to search students by roll number, registration number, or semester for faster
access to records.
3. Result and Grade Management
Extend the system to include academic performance tracking and result generation.
4. Export and Report Generation
Enable export of student data to PDF, Excel, or CSV formats for documentation and
reporting.
5. Attendance Tracking System
Integrate attendance features to track daily presence and generate summaries.
6. Notification System
Send automated email or SMS notifications for important updates or deadlines.
7. Mobile App Integration
Develop a mobile version or integrate with an existing student portal for increased
accessibility.
6.2 Conclusion
The Student Information System developed using [Link] Core MVC successfully demonstrates
how web technologies can be used to manage academic data efficiently. By following the MVC
architecture, the system ensures a clean separation of responsibilities, scalability, and
maintainability.
This project not only reduces the manual workload of administrative staff but also minimizes the
chances of data errors and improves accessibility to student records. The database-driven approach
combined with a responsive front-end provides a reliable foundation for building more complex
academic management systems in the future.
In conclusion, this system is a practical and scalable solution that fulfills the core requirement of
student information management and opens up possibilities for further development and
integration.
10
REFERENCES
[1] Microsoft, "[Link] Core MVC," Microsoft Docs, [Online]. Available:
[Link]
[Accessed: Apr. 24, 2025].
[2] Microsoft, "Entity Framework Core," Microsoft Docs, [Online]. Available:
[Link]
[Accessed: Apr. 24, 2025].
11
APPENDIX
Screenshots
i. Home Page
Figure 1:Details Page
ii. Create Page
Figure 2: Add Details
12
iii. Edit Page
Figure 3: Edit Details
Figure 4: After Editing Details
13
iv. Delete Page
Figure 5: Delete Page
Figure 6: After deletion
14
v. Responsiveness
Figure 7: Mobile View with Bootstrap Responsive Design
15