ABSTRACT

University Management System (UMS) deals with the maintenance of university,

college, faculty, student information with in the university. UMS is an automation

system, which is used to store the college, faculty, student, courses and information of a

college.

Starting from registration of a new student in the college, it maintains all the details

regarding the attendance and marks of the students. The project deals with retrieval of

information through an INTRANET based campus wide portal. It collects related

information from all the departments of an organization and maintains files, which are

used to generate reports in various forms to measure individual and overall performance

of the students.

Development process of the system starts with System analysis. System analysis

involves creating a formal model of the problem to be solved by understanding

requirements.

1
 PURPOSE OF THE SYSTEM

UNIVERSITY MANAGEMENT SYSTEM [UMS] deals with the maintenance of

university, college,facultie, student information with in the university. This project of

UMS involved the automation of student information that can be implemented in

different college managements

The project deals with retrieval of information through an INTRANET based

campus wide portal. It collects related information from all the departments of an

organization and maintains files, which are used to generate reports in various forms

to measure individual and overall performance of the students.

2
 EXISTING SYSTEM

The system starts with registration of new staff and students. When the subjects are to be

allocated to the faculty, the Head of the Department should enter everything in the Excel

sheets. Then the staff enters corresponding subject’s attendance and marks of a student

then those must also be entered in the Excel sheets and validations are to be done by the

user itself. So there will be a lot of work to be done and must be more conscious during

the entrance of details. So, more risk is involved.

PROBLEMS IN THE EXISTING SYSTEM:

Storing and accessing the data in the form of Excel sheets and account books is a tedious

work. It requires a lot of laborious work. It may often yield undesired results.

Maintaining these records as piles may turn out to be a costlier task than any other of the

colleges and institutions

Risks involved in existing system:

Present System is time-consuming and also results in lack of getting inefficient results.
Some of the risks involved in the present system are:
• During the entrance of marks and attendance, if any mistake is done at a
point, then this becomes cumulative and leads to adverse consequences

3
 • If there is any need to retrieve results it may seem to be difficult to search.

PROPOSED SYSTEM

UMS (UNIVERSITY MANAGEMENT SYSTEM) makes management to get the most

updated information always by avoiding manual accounting process. This system has the

following functional divisions.

• University Administrator

• College Administrator

• User (Students / Faculties)

University Administrator has the functionality of registering new colleges and courses.

College Administrator has the rights of creating department, allocating courses to

departments, creating faculties, students and allocating subjects to faculties, and

modifications in the data entered by the user can also be done by the college

administrator.

User of this may be faculty or students. Faculty has the facility of entering the marks and

attendance of the students. Students can check their marks and attendance but there is no

chance of modifications.

Reports must be generated for the existing data i.e. for attendance and marks of the
students, which are used to assess the performance of the students. These reports should
be viewed by the in charge and user.

4
 INTRODUCTION

After analyzing the requirements of the task to be performed, the next step is to
analyze the problem and understand its context. The first activity in the phase is studying
the existing system and other is to understand the requirements and domain of the new
system. Both the activities are equally important, but the first activity serves as a basis of
giving the functional specifications and then successful design of the proposed system.
Understanding the properties and requirements of a new system is more difficult and
requires creative thinking and understanding of existing running system is also difficult,
improper understanding of present system can lead diversion from solution.

5
 ANALYSIS MODEL
The model that is basically being followed is the WATER FALL MODEL, which
states that the phases are organized in a linear order. First of all the feasibility study is
done. Once that part is over the requirement analysis and project planning begins. The
design starts after the requirement analysis is complete and the coding begins after the
design is complete. Once the programming is completed, the testing is done. In this
model the sequence of activities performed in a software development project are: -
• Requirement Analysis
• Project Planning
• System design
• Detail design
• Coding
• Unit testing
• System integration & testing

Here the linear ordering of these activities is critical. End of the phase and the
output of one phase is the input of other phase. The output of each phase is to be
consistent with the overall requirement of the system. Some of the qualities of spiral
model are also incorporated like after the people concerned with the project review
completion of each of the phase the work done.
WATER FALL MODEL was being chosen because all requirements were known
beforehand and the objective of our software development is the
computerization/automation of an already existing manual working system.

6
 Changed
Requirements
Communicated
Requirements

Requirements
Specification
Requirements
Engineering

Design
Specification
Design

Executable
Software
Programming Modules Maintenance

Integrated
Software
Process
Integration Product

Delivered
Software
Product Product Delivery Product
Input Output

Fig 2.2: Water Fall Model

7
 FEASIBILITY STUDY

Preliminary investigation examine project feasibility, the likelihood the system will
be useful to the organization. The main objective of the feasibility study is to test the
Technical, Operational and Economical feasibility for adding new modules and
debugging old running system. All system is feasible if they are unlimited resources and
infinite time. There are aspects in the feasibility study portion of the preliminary
investigation:
• Technical Feasibility
• Operational Feasibility
• Economical Feasibility

TECHNICAL FEASIBILITY

Technical Feasibility centers on the existing computer system hardware, software,

etc. and to some extent how it can support the proposed addition. This involves financial
considerations to accommodate technical enhancements. Technical support is also a
reason for the success of the project. The techniques needed for the system should be
available and it must be reasonable to use. Technical Feasibility is mainly concerned
with the study of function, performance, and constraints that may affect the ability to
achieve the system. By conducting an efficient technical feasibility we need to ensure
that the project works to solve the existing problem area.
Since the project is designed with ASP.NET with C# as Front end and SQL Server
2000 as Back end, it is easy to install in all the systems wherever needed. It is more
efficient, easy and user-friendly to understand by almost everyone. Huge amount of data

8
can be handled efficiently using SQL Server as back end. Hence this project has good
technical feasibility

OPERATIONAL FEASIBILITY

People are inherently instant to change and computers have been known to facilitate
change. An estimate should be made to how strong a reaction the user staff is likely to
have towards the development of the computerized system.
The staff is accustomed to computerized systems. These kinds of systems are
becoming more common day by day for evaluation of the software engineers. Hence,this
system is operationally feasible. As this system is technically, economically and
operationally feasible, this system is judged feasible.

ECONOMICAL FEASIBILITY

9
 The role of interface design is to reconcile the differences that prevail among the
software engineer’s design model, the designed system meet the end user requirement
with economical way at minimal cost within the affordable price by encouraging more of
proposed system. Economic feasibility is concerned with comparing the development
cost with the income/benefit derived from the developed system. In this we need to
derive how this project will help the management to take effective decisions.
Economic Feasibility is mainly concerned with the cost incurred in the implementation
of the software. Since this project is developed using ASP.NET with C# and SQL Server
which is more commonly available and even the cost involved in the installation process
is not high.
Similarly it is easy to recruit persons for operating the software since almost all the
people are aware of ASP.NET with C# and SQL Server. Even if we want to train the
persons in these area the cost involved in training is also very less. Hence this project has
good economic feasibility.
The system once developed must be used efficiently. Otherwise there is no
meaning for developing the system. For this a careful study of the existing system and
its drawbacks are needed. The user should be able to distinguish the existing one and
proposed one, so that one must be able to appreciate the characteristics of the proposed
system, the manual one is not highly reliable and also is considerably fast. The proposed
system is efficient, reliable and also quickly responding.

S/w and H/w requirements

1. Environment:
• Servers:
• Operating System Server: - Microsoft Windows 2000 or
Higher
• Data Base Server: Microsoft SQL Server 2000/2005
• Clients : Microsoft Internet Explorer,
• Tools : Microsoft Visual Studio .Net
• User Interface: ASP.NET with AJAX
• Code Behind : VC#.NET

10