Last modified on April 13th, 2021
College Management System Project SRS Download
The main objective of our product is to maintain information about students, employees and other activities like attendance, student marks, fee payment, and salary payment, etc. The information is stored for decision making in the future for a business process within an organization. This is a desktop application.
This document describes the software requirements specification (SRS) for the Collage Management System that provides the access and management of information of different modules in a collage-like Students, Guardians, Teachers/Faculty, Finance, Examination, HR. Our project is based on a database, which stores and maintains the information of different modules within the system. The advantage of the management system is to avoid entries in hard copies and it saves the burden of hard copies of data. The system is a Desktop Application and GUI for this system is developed in C#. The Database for this management system is created in SQL. There are two users for this system 1. Admin (have full access to read and write of all modules in management system) 2. Teacher (have access limited to write and manage the student’s marks, attendance, etc.). This is version 1.0 of the software requirements specification.
The purpose of this document is to retrieve and analyze the ideas that define the product and requirements that the user needs. This document describes the details of our product, its parameter, and its goals. This SRS document describes the target, audience, user interface of product and Software/Hardware requirements of our product. This document also describes the problem we have faced during the designing and implementation of the product and also describes how we have solved this problem and make our product more efficient. The management system saves the human power and time cost to perform the same task. The data in the database can be saved for a long time and can be used for different purposes in the future. In management systems, there is a minor chance of losing the data. This document also defines how customers and users see our product and understand the functionality of the product. This document will help the developers/designers in case of maintenance of the software product.
Key Focus and Abbreviations
When writing this SRS for College Management System the following terminologies are used:
- CMS: College Management System.
- C#: Pronounced as C sharp. It is an object-oriented programming language in which reusable components build for a wide variety of applications.
- GUI: Graphical User Interface.
- DBMS: Database Management System.
- SQL: Structured Query Language, used to create the database.
- SQL Server: SQL Server is a database management system in which database is created and manages the database like “update”, “Delete” and insert a new record in the database.
“Manual College systems were paper-based and difficult to maintain, expensive, more manpower required and unable to handle large records, the previous system was not efficient, not effective and there were issues of redundancy and consistency.”
In this project, the system is proposed by understanding the issues in the existing system. In this management system the problems are solved that were in the previous system by shifting on a computerized system of the modern age. The database is used to store the data at the backend of the system.
The graphical interface GUI is developed in C#. In a certain way get the data from the user and store it into the database. Reports of stored data are generated through Crystal reports. The system that is proposed provides consistent and redundancy free data in storage and should be more efficient.
This system provides the security of data by authentication of users and in this project right of users are defined. In this system, admin is the main user of the system who has full rights of all modules within the proposed system and the other user which is an employee of college also can be a teacher within the college has limited access to the system like students attendance and marks of the students are managed by the employee. In this product, different reports can be generated, pay slips of employee salary, fee report of fee payment if students, student details, attendance report, etc.
The main modules which are focused on this project:
- Student management
- Employee management
- Student Fee management
- Employee salary payment
- User registration
- Internal Marks of students
- Attendance of students
- Reports of all modules (Crystal Reports)
As Colleges are growing day by day more and more, and also increasing the complexity of storing information of students and related to the college system, they face many related issues: attendance and fee of students, salary details of employees, etc.
This project is based on the educational institute system where this application gives maximum services in a single software product that is used by teacher and system administration. This project is based on a desktop application that is sharing information on different departments in a college.
In this project that includes C# and SQL. C# is used to design the GUI for the application by which the user can interact with software applications. The SQL Server is used for creating the database in which different information will store. The main focus of this project is to give the best GUI for the users and provide the many modules in a single product. Admin can view all of the information that is stored in the database through application and admin also can modify this information because the admin has full access to the system.
The teacher can view and modify the information related to students, teachers have limited access. This project can adjust any additional module at any time.
Target Audience and Reading Suggestions
This document is to be read by the development team, the project managers, marketing staff, testers, and documentation writers. The software engineer/Developer and project managers need to become intimately familiar with the SRS. Others involved need to review the document.
Testers need an understanding of the system features to develop meaningful test cases and give useful feedback to the developers. The developers need to know the requirements of the software product they need to build.
This document is for general discussions on the implementation decisions regarding the College Management System. The user of the product should have the concepts of RDMS, SQL, interfaces, and classes.
The CMS is expected to be deployed in a real environment to manage the DBMS inside the college. The centralized database is used to store the information. The user only within the college (members of college staff) can use this management system. Users outside form the college cannot access the management system. This application is developed for windows operating system that can be run on Windows XP and above.
The database is used in different departments within a branch of the college. The database used to store the information is the centralized database. The software we have developed will be installed on different computer systems within a college and software will be connected to a centralized database through LAN within a college and then the user can interact with the system and can store the data and other users can get access the stored through a centralized database.
User Types and Authorities
This management system is controlled by the teachers and system administrators. In this system, admin is the main user who has full access to the management system .admin can view and modify all information that is stored in the database.
Admin can view and modify the student’s records like student’s profile, attendance, fee, results, and details of teachers and other employees in college, their personal information and their attendance for their salaries.
Teachers have access to view and modify the student’s information like their attendance, marks of exams to generate the progress report of students. When the teacher “update”s the student’s information then admin can view this information.
Design and Implementation Constraints
During the implementation of the product, different challenges are faced. Choosing the interface for the management system was a paramount issue. Connecting the database with the application was a major problem.
For connecting the database we had to create our account in ORACLE and then we had to download the driver(software). The connection of the database that is created in ORACLE with C# is not very simple as like SQL. So the installation of ORACLE driver(software) is necessary to create a connection between ORACLE and C#. But after installing the required driver it creates a problem in installing and connecting with a server in the oracle server, so we decided to leave the oracle and then we choose the SQL server to create the database.
The SQL Server is easy to install and connect with a server in SQL it is very easy to understand the implementation of the database and also easy to create a new database and connect with the GUI application.
Methodology of Project
We developed our product using the software development life cycle. In the development of our product, we use the Agile model. The Agile model is a model of SDLC which is a combination of two process models incremental and iterative. CMS is developed on the basis of incremental process model of the Agile model which allows the user to divide the large project into different parts/ modules.
In the incremental model the versions/parts of the system are delivered to the user after a regular interval of time, to get feedback from the user that is it cleared or he/she want any more changes in the given module. If the user wants any type of change in the product then it is possible through the incremental model.
After the decided time each new part of the product is developed and delivered to the user and then at the end when all parts are developed, all modules/parts are combined in a way to develop the full product to deliver to the user in the form of finished/complete application as user’s requirements.
Communication between client and developer is an important part of the agile model. The product will fulfill the user’s requirement in the case when there is maximum communication between developer and client so the application will be more accurate. The finished product should accept the changes in the future.