Software Requirements Specification For A Management Information System Part One: Top Level Requirements
Software Requirements Specification For A Management Information System Part One: Top Level Requirements
The system should support management of academic, administrative and other activities in our
institute. These activities are divided into four sections as follows.
• Academic Activities
• Administrative Activities
• Facilities
1. Academic Programme : Applications and Admissions, Enrolling new students, Course registration
(enrollment for desired courses) and Fee payment, Evaluation and Grading, Viewing and printing
grade cards, Teacher evaluation.
3. Training and Placement : Displaying schedules of Campus interviews, Putting up shortlists and
declaring results.
1. Employee Information : Maintaining Employee records, Accessing data and Generating reports as
required.
2. Legal matters : Access to Case reports and Legal suits of the Institute.
1
4. General Administration : File movement Tracking (across departments/administration), Facility to
raise an issue / ticket and track it, Meeting Management, Managing Institute Advertisements.
1. Student account management covering fees, teaching assistantship, scholarships, fines and other
charges
2. Employee Accounts Management: Salaries, Leave management, Income Tax management, Pension
management, TA/DA and PDA.
3. Visibility and transparency of various funds across departments, projects, interest groups, Deans,
Registrar and the Director; Compilation of accounts to enable furnishing details of expenditure to
the funding agencies.
4. Internal Audit.
Facilities include:
1. Stores and Purchases : Indenting and approval, Billing and sales, Inventory management and
stock verification, Common Access System to Library, Stores etc through Smart Card, Interface to
check stock register and status of purchase etc.
1. Deployment
2
System should be locally deployable at , preferably on a Linux platform.
2. Security
Nobody should be allowed to tamper with data; Enhanced Security for sensitive data. It should be
made sure that only users who are given specific rights can access data and all actions are logged,
thus providing an extensive role based authorization.
Note: Password security may not be sufficient. Advanced technologies like use of biometrics is
desirable.
3. Backup
There should be an easy back-up feature for the entire data, to prevent losing any data.
4. Platform/Browser independence
The system should be able to work on any of the modern browsers like Firefox / Explorer / Opera /
Chrome, and any of the common Operating Systems like Linux, Windows and Mac OS.
5. Data migration
(i) There should be an easy way to migrate data from the current system to a new system.
(ii) The system should be able to interface with Microsoft Excel – read from Excel and write to Excel.
Standard file formats such as CSV or XML should also be supported for both import and export.
6. Performance
(i) During Course Registration an estimate of 10,000 students should be able to register over an
interval of 2 days.
(ii) The system should handle the simultaneous usage of almost 1000 users at a time.
7. Flexibility
As many of the institute processes and rules are expected to evolve over time, an important
requirement for the software is customizability. It is desirable to have a system that is flexible enough
3
to allow the administration at to evolve our processes without having to contact the company
every time for any small change. For example, adding new attributes in the registration form. MIS is
expected to be highly configurable to avoid code or database schema level modifications for small
changes. In addition, code and database schema changes for bug fixes and common features that
would be required by most academic institutes should be treated as part of the product patch or
upgrade. Such changes should be rolled into the main product source line and maintained at no extra
cost.
(i) The software should be designed for extensive customizability, even for people who are not used
to computer programming.
(iii) There should be a proper documentation of the system. This document should be so simple yet
precise so that a newly appointed faculty should do all the things on one’s own and distinguish all
the features. This could be given in the form of a ‘help’ menu associated with every activity.
9. Components
It is desirable that the solution must be based on, and runs on open-source infrastructure and
components, such as Linux, Apache Web Server, Tomcat/JBoss, PostgreSQL/MySQL. The solution can
be composed from available open source components and custom developed ones. Any custom
components developed should be made available to in the source format with sufficient
documentation.
4
Part Two: Detailed functional requirements
Academic Programme
Active Users : Applicants (external users, who are not registered users from ), MIS admin.
System should provide online application form for admission to be filled in by the applicant. The
occurrence of errors should be minimized through the use of interactive check-boxes, radio-buttons
and scroll-down menus.
After form submission, applicants should be provided with a unique Application ID, which the MIS
admin will verify, check details and finally register the applicant in the MIS with all the given details. ii.
Activity expected at the beginning of the academic year. MIS admin (from Administration department)
enters names of the new students who joined in the new academic year to the MIS.
Active Users : Students, MIS admin, HoD, Faculty Advisor, Faculty-in-charge of time table.
Activity expected at the beginning of every semester. Student should login into their account using
the username and password provided by the MIS admin, and register/enroll themselves for the
courses of their choice. System should maintain a session of the student when logged in.
There should be a superuser (for each dept) who shall have the rights to float courses offered by the
department. Faculty Advisor, HoD, Faculty in-charge of time table etc should be user statuses
assignable to users in the faculty group.
5
Student can register for courses from the list of courses based on student details – branch, semester,
passing pre-requisite courses, CGPA etc. and also enter their fee details (amount, mode of payment
etc). Student should be allowed to choose electives of his/her choice and Faculty Advisor should be
able to approve this.
A student is allowed to do registration only once for a semester. Any further changes (add/drop etc)
will have to be done by the MIS admin or the Faculty Advisor.
Faculty should be able to assign test and assignment marks, attendance and grading policy (what is
the range of marks that deserve grade A etc) and according to this policy the software should assign
grades S, A, B, C, D, E, F or I to every student. The grades information shall remain hidden till an
appropriate time decided as per the academic time table. There should be one privileged user ‘Class
Committee Chairman’who can see the marks/grades before that.
As of now there are two mid-term tests and a set of assignments. There should be flexibility to add
more tests/assignments if needed. Current possible values of attendance are H (High), N (Normal) and
Low (L). (I corresponds to 'incomplete'). Keep this flexible so that more grades could be included.
It would be good if the faculty is able to able to upload the marks/attendance in a delimited format
(e.g.: comma separate values, tab, semi-colon etc or an excel worksheet) directly, and the system
reads this information and assigns marks correctly.
There must be an option to see a list that shows how many students fall in each grade.
System should provide students who have logged into their accounts, the functionality of viewing
their grade card.
It should also provide MIS admin with the functionality of viewing and printing any student’s grade
card.
6
vi. Teacher evaluation
Active users : Students and Faculty, Dean (UG) and Dean (PG).
Students evaluate the faculty members based on the course they were offered in the last semester.
Individual faculty members should be able to view their own report. Dean (UG) and Dean (PG) can
view all the reports. The anonymity of the individual students should be ensured.
2. Student Information
MIS_admin should be provided with the functionality of entering and updating the necessary
student’s details like Name, Branch, Photograph, Batch, Roll number, Date of Birth, Blood Group etc.
Students should be provided with the functionality of viewing their own records (password
protected), filling up other optional detail fields like contact number, e-mail etc. and reporting to the
MIS_admin in case any discrepancy occurs.
Some of these fields should be available for internal viewing, while others are accessible only for
those with admin status (Faculty, Faculty advisor and HoD). Details about the students currently
enrolled to his/her course should be visible to the faculty. Similarly faculty advisor should have the
same rights on all students under him/her. HoD should be able to view details of the students in the
department.
Active users : T&P in charge uploads the test/interview schedules that include given to each company.
Students can view the schedule any time. ii. Putting up the list of short-
7
T&P in charge uploads the list of shortlisted candidates and later the final results.
1. Employee Information
MIS_admin staff from the administration department should be able to add and update the employee
details (Service book) in an online database.
Employees should be able to view/print their own information and report if there is a discrepancy.
Employees, HoDs, Registrar and Admin should be able to view/print Employee information.
2. Legal matters
A one-point access to the case reports of all the legal suits that the institute has been involved in. The
Registrar/Director should have access to this database.
System should provide online application forms for various positions, for which the advertisements
are available online on the Institute page. With the use of check-boxes, radio buttons and scroll down,
we could reduce the amount of text input from the user.
8
After the submission, applicants should be provided with a unique Application ID which the
MIS_admin (Administrative section) will verify, check details and finally register the applicant for
selection procedure.
A super-user should have the rights to uploads the list of shortlisted candidates and the list of
selected candidates.
4. General Administration
HoDs and Administrative Department should be provided with a fast and secure File movement
Tracking Facility. One should be able to easily check where a given file is now. Support for Electronic
File movement is also expected.
There should be a facility for every employee to raise an issue / ticket when necessary, and track it.
The priority of the ticket shall be escalated and notifications sent to concerned people if there is no
action on the ticket for 3 days (or a given period of time).
Every employee has the facility to check availability of meeting places like Seminar Room, Conference
Hall etc.; Book a meeting place and upload meeting minutes.
The administration shall be able to track the Institute advertisements and their follow-ups.
9
(c) Accounting and Finance
MIS_admin should be able to keep the account of fees, teaching assistantship, scholarships, fines and
other charges of students and update it regularly. Any amount that has been paid should be marked
as paid. Student should be able to view their account and report in case of any discrepancy.
i. Salaries
Active users : MIS_admin (Accounts department), Employees (teaching and non-teaching staff) .
MIS_admin should be able to keep the account of employee’s salaries every month (with
componentwise split, income tax deducted etc.) and when it was paid, and employees should be able
to view the details and report in case of any discrepancy.
Active users : MIS_admin (Registrar), Employees (teaching and non–teaching staff), Heads of the
Departments.
Employees should be provided with the functionality of placing request for leave and to check the
status (approved/rejected/need to submit supporting documents). Leave can be of different types –
Earned Leave, Duty Leave, Casual Leave, Medical Leave or Loss of Pay. Casual Leave and Duty Leave
can be approved by the Head of the Department. Other approvals come from the Registrar.
Active users : MIS_admin (Accounts department), Employees (teaching and non-teaching staff) .
10
Employees should be able to enter details of the investments that they make, Insurance policies,
Housing Loans etc; MIS_admin should be able to keep the account of these investments that each
employee makes, income tax relaxations that each employee is entitled to in each section (like 80C)
and the income tax deductions from salary every month. Employees should be able to view the details
and report in case of any discrepancy.
Similar to Salary management, but only when there is a need to approve TA/DA/PDA to employees.
Salaries, Leave management, Income Tax management, Pension management, TA/DA and PDA.
i. Visibility and transparency of various funds across departments, projects, interest groups, Deans,
Registrar and the Director.
Records should be available online for any such expenditure, and should be easily verifiable.
ii. Compilation of accounts to enable furnishing details of expenditure to the funding agencies.
Faculty and HoD should be able to fill in the details of expenditure for any project that they are part
of, so that this data can be compiled and sent to Funding Agencies for funding a project.
4. Internal Audit
11
(d) Facilities
Departments (HoDs) or institute (Administration Department) make requests for purchases, Dean P &
D approves it.
Administration as well as departments (HoDs) make requests for tenders for selling old goods,
Registrar approves it, and the accounts section keeps the record of the amount that is paid.
Active users : HoDs (Departments), Employees in charge of stock verification, Admin (Registrar).
Entry and verification of machines/tools in laboratories, books in the library, fur ure and other
articles in the institute. Activity expected once every academic year. Admin should be able to view
this.
iv. Common Access System to Library, Stores etc through Smart Card (desired, but not necessary)
Heads of the departments should be able to view the stock register and status of purchases requested
for.
12
Some hostels are reserved for first year students. With such restrictions, hostel/room allocation to
students should be automated, and rooms to be allocated at random to students. The list of students,
the number of hostels, number of rooms in each hostel and capacity of each room will be given as
input.
(This is not a must for now, it can be managed manually).
Warden and Resident Tutors for each hostel should be stored and displayed. Hostel related expenses
like Mess tenders, purchases of vegetables etc should be accounted in a database.
Students and Faculty members should be able to place requests for accommodation in Guesthouse.
Administrative Section approves/rejects these requests as per availability and priority. These details
management
Details of empty Quarters and Apartments are listed. Faculty members place requests for the
quarter/apartment of their preference. Engineering Section (Assistant Engineer) approves/rejects
these requests considering seniority of the faculty member.
Similar to managing the bookings at the guest house. Availability of Institute Seminar Rooms /
Conference Rooms during any given time slot should be available online.
13
Employees should have the functionality of placing complaints about maintenance and malfunctioning
issues in the department buildings, Quarters, Lab machinery etc. and Assistant Engineer allocates
resources to look into these matters and close it when done.
Engineering u people list their requirements viz. Tendering, Placement etc., and it gets approved
from administrative section.
Engineering u people should be able to update the water and electricity bills and the Employees
x. A discussion forum
A discussion forum module where the employees as well as students can login and discuss various
issues of their interest. A newsgroup structure with separate groups for different set of topics is
desirable.
14
Use Case:
15