MIZAN TEPI UNIVERSITY

SCHOOL OF COMPUTING AND INFORMATICS

DEPARTMENT OF INFORMATION TECHNOLOGY

C# PROJECT PROPOSAL

TITLE : STUDENT MANAGEMENT SYSTEM

F_NAME L_NAME ID

YIKEBER ADELA MTUUR3365/14

SUBMITTED TO : Mr.Melaw

SUBMISSION DATE :17/01/2017

MTU 1
 Abstraction
Student Management System is an organized computerized system
designed and programmed to deal with day to day operations and
management of student activities. The program can look after student
records, scores, registrations, information. It also maintains student
information such as student id and department administering.In this
project we are going to provide the extra facility to store the report in the
database and make available from anywhere in the world

MTU 2
 Catalog
Abstraction..................................................................................................………... 2
Table of Contents........................................................................................................ 3
List of Tables............................................................................................................... 3
Abbreviations................................................................................................................4
Introduction................................................................................................................ 5
1.1 Background of the University ............…............................................................. 5
1.2 Background of the Project...............................................................................6
1.3 Task and Schedule .........................................................................................7
1.5 Statement of the Problem............................................................................... 8
1.6 Objective of the Project.................................................................................. 8
1.6.1 General Objective ....................................................................................8
1.6.2 Specific Objectives...............................................................................8
1.7 Scope of the Project..........................................................................................8
1.8 Feasibility Study of the Proposed System........................................................ 9
1.8.1 Economic Feasibility .......................................................................10
1.8.2 Technical Feasibility ........................................................................... 10
1.8.3 Operational Feasibility ........................................................................ 10
1.8.4 Behavioral/Political Feasibility ............................................................ 11
1.8.5 Schedule Feasibility ............................................................................. 11
1.9 Significance of the project.................................................................................. 12
1.10 Target Beneficiaries of the System................................................................... 12
1.11 Methodology ..................................................................................................... 12
1.11.1 Data Analysis Methodology ...........................................................13
1.11.2 Data Collection Methodology ......................................................... 13
1.11.3 System Analysis and Design Methodology ........................................14
1.11.4 Implementation Methodology ........................................................... 15
1.12 Limitation of the Project.................................................................................. 16
1.13 System Design…………………………………………………………………16
1.13.1 use case diagram…………………………………………………….16
Conclusion..............................................................................................................17
Reference ...................................................................................................................18
List of Tables
Table 1:1 Task and Schedule...................................................................................7
Table 1:2 Budget of the Project.............................................................................9
Table 1:3 Schedule Feasibility...............................................................................11
Table 1:4 Target beneficiaries of the system......................................................... 12
Table 1:5 Hardware tools required.......................................................................15
Table 1:6 Software tools........................................................................................15

MTU 3
 Abbreviations
MTU=Mizan Tepi University
SMS=Student Management System
UML=Unified Modeling Language
OOSAD=Object Oriented System Analysis and Design
OOA=Object Oriented System Analysis
OOD=Object Oriented System Design

MTU 4
 Introduction

The Student Management System (SMS) is designed to simplify and streamline the
administrative tasks of educational institutions by providing a digital platform for
managing student data. This project aims to develop a software solution that
centralizes the storage, retrieval, and management of student-related information,
reducing the need for manual record-keeping and minimizing errors.

Educational institutions deal with large volumes of data on a daily basis, including
student personal details, academic performance, attendance, and fee management.
Handling such information manually is not only time-consuming but also prone to
inaccuracies. The Student Management System offers a more efficient alternative by
automating routine tasks and providing a unified system for administrators, teachers,
students, and parents to access relevant information.

The key objectives of this project are:

 To automate administrative tasks, including student registration, grade

management, and attendance tracking.
 To create a centralized database that stores all student records, accessible by
authorized users.
 To provide an intuitive and user-friendly interface for managing student
information.
 To improve data accuracy, security, and transparency within the institution.

This project will involve the design and implementation of a web-based application
that allows easy access to real-time data, enhances communication between students,
faculty, and administration, and ensures seamless management of academic and
administrative processes.

1.1 Background of the University

Established in 2006, the Mizan Tepi University is a non-profit public higher education
institution located in the large town of Mizan (population range of 10,000-49,999
inhabitants), South West region. This institution also has a branch campus in Tepi and
Aman. Officially recognized by the Ministry of Education of Ethiopia, Mizan Tepi
University (MTU) is a coeducational Ethiopian higher education institution. Mizan
Tepi University (MTU) offers courses and programs leading to officially recognized
higher education degrees such as bachelor's degrees in several areas of study.
International applicants are eligible to apply for enrollment. MTU also provides
several academic and non-academic facilities and services to students including a
library, as well as administrative services.

MTU 5
1.2 Background of the Project

In educational institutions, managing student data has traditionally involved extensive

paperwork, manual processes, and siloed systems, leading to inefficiencies in
administrative tasks and communication gaps between students, teachers, and parents.
As the student population grows and academic institutions evolve, the need for an
organized and streamlined system to handle vast amounts of data becomes
increasingly critical.

Over the years, educational institutions have transitioned towards digital tools to
manage various administrative functions such as enrollment, attendance tracking, and
performance assessment. However, many schools and universities still rely on
fragmented systems or partially automated processes, leading to challenges such as:

 Data Redundancy: Storing the same data across multiple platforms often
leads to duplication and inconsistency.
 Time-Consuming Tasks: Manual data entry for student records, attendance,
and grading takes significant time and effort, diverting focus from core
educational objectives.
 Limited Accessibility: In many institutions, accessing student records
requires physical paperwork or navigating multiple software platforms,
causing delays in decision-making.
 Errors and Inaccuracy: Manual record-keeping introduces the risk of human
errors, impacting data accuracy and reporting.

Recognizing these challenges, the concept of a Student Management System (SMS)

emerged as a solution to provide a more efficient, reliable, and scalable method of
managing student information. This system offers an integrated platform that
centralizes data, automates tasks, and ensures accessibility for authorized users. The
SMS addresses key areas such as student registration, academic performance,
attendance, fee management, and communication, all while ensuring data security and
compliance with regulatory standards.

MTU 6
 1.4 Task and Schedule

Phase Method Start Date Stop Date Compilation

Time(hr/day)

Data Gathering Interview Feb-15 Mar-03 2hr

observation 4hr

Document 2days
Analysis

Data analysis analysis Mar-10 Mar-20 10days

Documentation Mar-21 Apr-03 8days

and design

implementation Apr-04 May-15 9days

testing White Testing May-16 May-25 5days

Black Testing May-26 May-30 2days

Table 1:1 Task and Schedule

MTU 7
 1.5 Statement of the Problem
Design and implementation of student management system is desktop application that
will solve the student information problem facing patient and other stakeholders in
MTU student management system.
The basic problem facing (manual) student monitoring is:
1. Lack of immediate retrievals: -
The information is very difficult to retrieve and to find particular information like- E.g.
- To find out about the student’s history, the user has to go through various registers.
This results in inconvenience and wastage of time.
2. Lack of immediate information storage:
- The information generated by various transactions takes time and efforts to be stored
at right place.
3. Lack of prompt updating: - Various changes to information like student details
are difficult to make as paper work is involved.
4. Error prone manual calculation: -
Manual calculations are error prone and take a lot of time this may result in incorrect
information.
For example calculation of student’s bill based on various registration.
5. Preparation of accurate and prompt reports: -
This becomes a difficult task as information is difficult to collect from various register.

1.6 Objective of the Project

1.6.1 General Objective

The General objective of this project is to design and implement web based student
management system.
1.6.2 Specific Objectives
To achieve the general objective, we shall be guided by the following specific
objectives:
 Collect data requirement for the system.
 To evaluate the existing paper-based information of student management system.
 To analyze and organize student information in such a way that it will be used to
design the new system.
 Design the system using necessary tools.
 To design and implement a database for proper implementation of the student
management system.
 Implement the proposed system.
 Test the performance of the proposed system.

1.7 Scope of the Project

This study covers the procedure for managing student information's in MTU students .
Online student management system is too wide in its scope but, this project is done
the following points only according to time are:
 Record new students information and existing students
 Generating record of students in printable format.

MTU 8
 Searching and retrieving students data.
 Generate and view report and allows users to record students data accurately.
 Registering, Updating, and searching students information by the the appropriate
body which are responsible for the appropriate task.
 Enable communication among members of the stockholders in MTU.

1.8 Feasibility Study of the Proposed System

Feasibility is the measure of how scheduled, beneficial or practical the development

of the system will be for the organization. To start with our project first, we have to
clearly analyses the feasibility of the system that we are going to do. So, we have
looked at some feasibility: -

1.8.1 Economic Feasibility

System to be developed is economically feasible and it is designed to gain high
benefit that can out weight the cost. Since this project will help computerize and
mobilize the existing system that the organization uses there will be a decrease of cost
for materials used in manual operation which means it becomes beneficiary to the
organization in each and every way, and also in order for the project team to
complete/reach the final result of this project. Our work won’t be economically
extravagant we will be able to use medium amount of resources to make the
documentation and to finish the implementation so what we have conducted is this
project will be economically feasible.
Tangible benefits
The system has tangible benefits such as:
 There is no cost wastage for pen, papers and more.
 Problem that was occurring on billing is strictly avoided.
 There is no time wasted by customers and by the employee as previously wasted
on different processes.
Intangible benefits
The system has intangible benefits such as:
 Security.
 Increase accuracy.
 Increase information processing efficiency.
 Reliability and trust.
Cost of the project
To complete our project starting from the beginning up to the end of this project we
planned the following cost list.

Material Measurement Quantity Single Total

no Price(birr) Price(birr)

1 flash Byte 16GB 340 340

2 printing Number 70 sheets 2 140

3 laptop Number 1 30,000 30,000

Total Cost 30,480

MTU 9
Table 1:2 Budget of the Project

1.8.2 Technical Feasibility

It is about how the organization accesses the developed system. It is also the measure
of practicality of the specific technical solution and the availability of technical
resources (like hardware and software) and know-how the proposed system is also
simple to manage and maintain.
The system is going to be developed by technological development technique such as
C# language with the XAMP Server and visual studio code editor, MYSQL database
to store files, Microsoft word for writing document. The system that we are going to
develop is familiar with new technologies and easy to understand by the system users.
This system will provide an easy access to the users. The work for the project is done
with the current equipment and existing software technology. The proposed system
can be easily maintained and repaired without requiring high experts or technical
assistance. Therefore, the new system is technically feasible.

1.8.3 Operational Feasibility

The Proposed systems are beneficial only if they can be turned out into information
system and user friendly that meets the organization’s operating requirements.
Operational feasibility aspects of the project are to be taken as an important part of the
project implementation. Some of the important issues raised are to test the operational
feasibility of a project includes the following:
 Is the new system being easy for access and acceptable by the users?
 Will the system be used and work properly without failure if it is being developed
and implemented?
 Will there be any resistance from the user that will undermine the possible
application benefits?
This system is targeted to be in accordance with the above-mentioned issues. In
advance the management issues and user requirements have been taken into
consideration. So, there is no question of resistance from the users that can undermine
the possible application benefits.
We will propose the system which is operationally feasible and the project will be:
 More efficient
 User friendly
 Reduce information redundancy which is a major problem in existed
system .

1.8.4 Behavioral/Political Feasibility

The project team members built the system without violating rules and regulations of
the governments as well as the organization. The system being built is for the
importance of productivity of the organization, so that the project is behavioral
feasible. Behavioral feasibility determines whether the proposed system conflicts with
the legal requirement or not.

MTU 10
1.8.5 Schedule Feasibility

The proposed system can be implemented in an acceptable time frame give below.
Project manager is responsible for monitoring and controlling the project development
based on the schedule shown below.

Gantt Chart Project Schedule

S.No Phases 1 st 2 nd 3 rd 4 th 5 th 6 th
Quarter Quarter Quarter Quarter Quarter Quarter

20th 4th 21th 4th 16th 1th

Seb-3th Oct- Nev- Dece- Janua- March-
Oct 20th 3th 15th 30th 15th
Nev Dece Janua Febru March
1 Project
Proposal

2 Requirement
Analysis

3 Design

4 Coding And
Implementati
on

5 Installation
Testing

6 Project
Closure

MTU 11
Table 1:3 Schedule Feasibility

1.9 Significance of the project

The current system is not using computerized data processing System so making the
system online will give many benefits. System can be developed successfully and
need to be tested.
Making sure it is user friendly, and has required option, which can be utilized by the
user to perform the desired operations.
The goals must be achieved by the system such as
 instant access
 optimum utilization of resources
 efficient management of records
 less processing time getting required information.
 user friendly.
 portable and flexible for further enhancement.
 It deals with the collection of Student’s information

1.10 Target Beneficiaries of the System

Target Group Benefit

MTU Reduce the work load time load waste to

store and search different student
information
Various Department Reduce the work load whoever concerned
with different departments in MTU
Student Reduce work load and time waste to
register and see their history

Table 1:4 Target Beneficiaries of the System

1.11 Methodology

A methodology is a set of methods, processes and practices that are repeatedly carried
out to deliver the project. Prototyping used for getting clear requirements and re-use
the software components to accelerate the development time lines. This part deals
about the method of data collection, source of data, and how the data organized and
analyzed.
System development methodology refers to the frame work that is used to structure
plan and control the flow of developing an information system there are different
system development methodologies that are suitable for different projects based on

MTU 12
the values technical organizational project and team consideration. For this project the
team used object-oriented software development methodology
The reason why we selected object-oriented system development is because it has the
following advantages.
 In an object-oriented environment,
 Object-oriented systems development is a way to develop software by building
self-contained modules or objects that can be easily replaced, modified, and reused.
 Software is a collection of discrete objects that encapsulate their data as Well as
the functionality to model real-world objects.
 Each object has attributes (data) and methods (functions).
 Objects are grouped into classes; in object-oriented terms, we discover and
describe the classes involved in the problem
 Encourages re-use not only modules but also entire design.

1.11.1 Data Analysis Methodology

After gathering different information from stakeholders the project team has analyzed
requirements by using Unified Modeling Language models like use case diagram,
activity
diagram and class diagram. Since:-
 UML is a modeling language widely used to visualize the object oriented designs.
 UML makes it easy to visualize the software design.
 UML diagrams can be easily decoded and converted into most of the popular
object-oriented programming languages.

1.11.2 Data Collection Methodology

Data collection is the most important part of our project to find the main required
information to system and to understand how the system works. We used the
following methods to collect relevant data required to our project.
 Interview: we gathered information by interviewing the internship advisor about
the existing system. We have prepared some questions to internship advisor to get
the necessary information about the existing system.
 Observation: The project team observed May things using this method; it allowed
us on participating and watching a person perform activities to help us learn about
the current situation or system. This is use full when the validity of data collection
is in question or when the complexity of certain aspect of the system prevents a
clear explanation by the system. We have also followed different methods to get the
overview of the existing system, understanding the overall work flow and how
everything is handled.
 Document Analysis: - We used this method to try to discover Forms, documents
rules, constraints and regulations which the existing system currently uses, also to
find written documents and others written materials about the organizations
structure, business rule, and to know all about the student management
mission, vision, function and overall of their work .

MTU 13
1.11.3 System Analysis and Design Methodology

The advantage of system design and analysis phase is to provide the basic overview
of the system that we are going to develop. As a result, we have used object-
oriented system analysis and design methodology (OOSAD) to develop our system,
because it has the following advantages.
 Encourages data Encapsulation: Since everything within OOA and OOD
revolves around the concept of objects one of the biggest advantages of OOA and
OOD is that it encourages planning and development of systems that are truly
independent of one another.
 Reduced Maintenance: The primary goal of object-oriented development is the
assurance that the system will enjoy a longer life while having far smaller
maintenance costs. Because most of the processes within the system are
encapsulated, the behaviors may be reused and incorporated into new behaviors.
 Real-World Modeling: Object-oriented system tends to model the real world in
a more complete fashion than do traditional methods. Objects are organized into
classes of objects, and objects are associated with behaviors. The model is based on
objects, rather than on data and processing.
 Improved Reliability and Flexibility: Object-oriented system promise to be far
more reliable than traditional systems, primarily because new behaviors can be built
from existing objects. Because objects can be dynamically called and accessed, new
objects may be created at any time. The new objects may inherit data attributes from
one, or many other objects. Behaviors may be inherited from super-classes, and novel
behaviors may be added without effecting existing systems functions.
 High Code Re usability: When a new object is created, it will automatically
inherit the data attributes and characteristics of the class from which it was spawned.
The new object will also inherit the data and behaviors from all super classes in which
it participates.
 Easy to Understand: Since OOA and D principles are fundamentally based on
real world objects, it’s quite easy for everyone on the team to quickly understand what
an object name means or how a particular behavior, well, behaves. This makes the
overall development life cycle a much smoother process, particularly if your team
needs to frequently interact with customers or other non-technical users about the
objects and components in the system.
This OOSAD has two phases.
 Object Oriented Analysis (OOA): -This phase concerns with determining and
understanding the system requirements, find and identify the business objects,
organize the objects and build a use-case model. A use-case is a scenario to describe
the interaction between user and computer system. This model represents the user
needs or user view of system.
It also includes identifying the classes and their relationships to the other classes in
the problem domain that make up an application.
 Object Oriented Design (OOD): -The objective of this phase is to design and
refine the classes, attributes, methods, and structures that are identified during the
analysis phase, user interface, and data access. This phase also identifies and defines

MTU 14
the additional classes or objects that support implementation of the requirement and
behavior that support the use case scenario, and finally update object model.
The outputs of OOAD activities are analysis models (for OOA) and design models
(for OOD) respectively. The intention is for these to be continuously refined and
evolved, driven by key factors like risks and business value.

1.11.4 Implementation Methodology

Tools Activities
Personal computer(PC) Almost all tasks of this project are
performed on computer.
Flash disk required for data movement and store

Disk (PC) necessary for the store of relevant data and

for backup
paper used for write different question and
resource

Table 1:5 Hardware tools required

Software tools required

Software Tools: - This project uses the following system development tools for
different activities.

Tools Activities

Visual studio code editor For coding C# language

MySql Back end (Server side coding)

Xamp Server For storing complaint information

permanently

Ms office word 2016 For documentation

Ms office PowerPoint 2016 For Presentation

Edrawmax To draw UML Diagram and for designs

MTU 15
Table 1:6 Software tools

1.12 Limitation of the Project

This defines what the proposed system is not going to perform or what is not
including in the proposed system according to time and resources.
Most universities are still facing several challenges with student Management System
because some of them are still using manual processes, while those who are using
computerized method are also facing the challenge of adjusting to it. Like:
The limitations of our software product is listed below
 It does not give online assistant.
 It does not work offline or without Ethernet connection.
 The proposed system cannot access with local language.
 Only literate persons can use this system.

1.13 System Design

1.13.1 use case diagram

MTU 16
 Conclusion

Working on the project was an excellent experience. It helped us to understand the

importance of planning, designing and implementation so far we have learnt in our
theory books. It helped us unleashing our creativity while working in a team. It also
realized the importance of team working, communication as a part of this project. The
project was successfully completed after a lot of efforts and work hours. This project
underwent number of compiling, debugging, removing errors, making it bug free,
adding more facilities in Student Management System and interactivity making it
more reliable and useful. This project focused that scheduling a project and adhering
to that schedule creates a hard sense of time- management. It has also let us known
that co operative teamwork always produce effective results. The entire project has
been developed and deployed as per the requirements stated by the user. It is found to
be bug free as
per the testing standards that are implemented. Finally, we like to conclude that we
put all our efforts throughout the development of our project and tried to fulfill most
of the requirements of the user.

MTU 17
 Reference

https://www.officetimeline.com/make-gantt-chart/excel.
R.S Pressman, Software Engineering: A Practitioner’s Approach, Mc-Graw-Hill,
Edition-7 (2010).
P. Jalote, an Integrated Approach to Software Engineering, Narosa publication house,
Edition -3 (2011).
https://mscw.ac.in/NAAC/Criteria1/Samples-of-
ProjectWork_Fieldwork/Computer_Science/software_Engineering/Software%20Engi
neering/Student%20Managment%20Project%20SE-converted.pdf.
https://m.mu.edu.sa/sites/default/files/content/2018/11/MAJD.pdf.
chatgpt
https://www.4icu.org/reviews/15536.htm.

MTU 18