1 Introduction:

This document is used to define the overall software description or requirements for
"STUDENT RESULT MANAGEMENT SYSTEM". Efforts have been made to define the req.
completely and accurately. The final products will be having only features or function mentioned
in this document and assumption for any additional functionality or feature should not be made
by any of the parties involved in development/testing/implementing or using this product. In case
it is required to have some additional features a formal change request will need to be raised
against and subsequently a new release of this document and/or product will be produced.

1.1 Purpose:

This SRS documents describes the capability that will be provided by the software
application SRMS. It also states the various required constrains by which the system will
abide (follow).the intended audience for this documents are the development team,
testing team and end-users of the product.

1.2 Scope:

• The software product "STUDENT RESULT MANAGEMENT SYSTEM" is an

MIS and reporting application that will be used for result preparation and
management of M-Tech program of a university.
• The application will manage the information about various student enrolled in this
course in different years, subject offered during different semester of the course,
students' choices about opting different subjects, and the marks obtained by
various students in various sub in different semester.
• Printable reports regarding list of students, marks obtained by all student in a
particular semester and performance of students (rankwise, percentage wise,
pass/fail, division wise) will be generated. The system will also generate printable
mark sheet for individual student. The application will greatly simplify and
speedup the result and management process.

1.3 Definition, Acronyms and Abbreviations:

• M.tech-Master of Technology
• IT-Information Technology
• SRMS-Student Result Management System
• MIS-Management Information System
1.4 References:

• University Website:-For info about course structure of M.tech program

 • IEEE Recommended Practice For Software Requirement Specification:-
IEEE Std.830-1993

1.5 Overview:

• The rest of SRS documents describe various system requirement, interfaces,

features & functionality in details.
• The student are offered four theory papers and two Lab papers (practical) during
1st, 2nd and 3rd semesters. The theory papers offered in these semesters are
categorized as either 'core' or 'elective'. Core papers do not have an alternative
subjects, where as elective papers have two other alternative subjects. Thus
student can study any subject out of the 3 choices available for an elective paper.
• In 1st, 2nd and 3rd semesters, 2 core papers and 2 elective papers are offered to
each student. The students are required to submit a team paper/minor project in
2nd and 3rd semester each.
• In 4th semester the students have to give a seminar and submit a dissertation on a
topic/subject area of their interest.
• It is required to develop a system that will manage information about subjects
offered in various semesters, students enrolled in various semesters, students
enrolled in various semesters, elective(s) opted by various students in different
semesters, marks and credit points obtained by students in different semesters.

Summary Report:
o Student Information
o Subject Information
o Semester wise Mark sheet
o Performance of Students
o Printable Mark sheet are generated

2 The Overall Description:

M.Tech. Program is a 4-semester course. The students are offered 4 subjects (theory) and
2 Labs (practical) during first, second and third semesters. Students also have to submit a
term paper/minor project in 2nd and 3rd semesters. The fourth semester consists of a
seminar and dissertation. Each subject/lab/term/paper/seminar/dissertation has credits
associated with it. When a student secures pass marks in a paper he/she also earns all the
credit (s) assigned to that paper.
The “Student Result Management System” will have capability to maintain information
about students enrolled in the course. The subjects offered during different semesters, the
students’ choices for opting different Elective subjects (out of the available ones) and the
marks obtained by students in different subjects in various semesters. The software will
also generate summary reports regarding student information, semester-wise mark lists
and performance reports. Printable mark-sheets of individual students will also be
generated by the application.

2.1 Product Perspective

The application will be a windows based, self content and independent software
product

Frontend client
Application with
Update / Entry / Data-base Backend
Delete / View /
Reporting
facilities

2.1.1 System Interface

None

2.1.2 User interfaces

The application will have a user friendly and a menu based interface
following screens will be provided

login screen:
1. login screen for entering user name and password and
role(Administration, data entry operator, marks entry clerk, co-
coordinator)will be provided. Access to different screen will be
based upon the role of the user.
2. There will be a screen for capturing and displaying information
regarding what all subject are offered during which semester, the
how many credit point are design that subject and whether the
subject is elective or a core paper, a lab paper, a term paper or a
dissertation.
3. There will be a screen for capturing and displaying information
regarding various students enrolled for the course in different
years.
4. There will be a screen for capturing and displaying information
regarding which student is currently enrolled in which semester
and what all elective subject he/she has opted.
 5. There will be a screen for capturing and displaying information
regarding which student has scored how many marks(internal +
external evaluation)in each subject(in a particular semester).credits
in each subjects will be calculating depending upon marks
obtained in that subject.
6. There will be a screen for capturing and displaying information
regarding which all user account exists in the system does showing
who all can access the system

The following report will be generated;

1. Students’ list report: Printable report will be generated to show
the list of students (enrolled in a particular batch year.
2. Students’ subject choices list report: For first, second and third
semester, there will be printable reports showing the different
elective subject opted by various students enrolled in a particular
batch year) of the corresponding semester.
3. Marks list report: for each semester there will be a printable
report showing the subject wise marks details of all the student of
that semester.
4. Rank wise list report: For each semester there will be a printable
report showing a percentagewise and rank wise list of the students
along with the division secured.
5. Mark sheet: For each student of each semester a printable mark
sheet will be generated, showing the subject wise marks details,
total marks, total credits, percentage, pass/fail status for that
student.

2.1.3 Hardware interface:

1. Support for printer (Dot-matrix/Inkjet/Laser etc any will do) i.e.
appropriate drivers are installed and connected printer will be
required for printing for reports and mark sheet.
2. Screen resolution of at least normal category is required for proper
and complete viewing of the entire screen. Higher resolution would
not the problem.
3. Stand alone system or network based-not a concern as it will be
possible to run the application of any of these.

2.1.4 Software interface:

1. Any windows base operating system
(windows95/98/2000/xp/vista/nt/7/8).
 2. Crystal reports 8-for generating and viewing reports.
3. Visual Basic 6-for coding/developing the s/w.
4. Ms access2000 as the DBMS-for back end database. Future release
for the application will aim at upgrading to oracle8i as dbms.

2.1.5 Communication Interface:

None

2.1.6 Memory Constrains:

256 Mb RAM & 2 GB space on hard disk will be required for running the
application.

2.1.7 Operation:
This product release will not covered any automated housekeeping aspects
of the database. The DBA at the client site (that is university) will be
responsible for manually deleting/non required data. Database backup &
recovery will also have to handle by the DBA.
However system will provide “reset system” Function that will delete
(upon confirmation from administrator) all the existing info from the
database.

2.1.8 Site Adaption Requirements:

The terminal at client site will have to support hardware &software
interfaces specified above selection.

2.2 Product Function:

• The system will allow access to authorized user with specific roles
(Administrator, Coordinator, Data Entry Operator, Marks Entry
Clerk).Depending upon user’s role; he/she will be able to access only specific
modules of the system.
• A summary of the major function that system will performed:
1. Login facility for enabling only authorized access to the system.
2. User (with role data entry operator) will be able add/modified/delete
info about different student that are enrolled for the course in different
years.
3. User (with role data entry operator) about different sub that are offered
in a particular semester. The semester wise the list of sub along with
 their credits & typed (i.e. elective, a core paper, a lab paper, a term
paper or a dissertation) will also be displayed.
4. User (with role data entry operator) will be able add/modified/delete
info about the elective sub opted by different student in different
semesters.
5. User (with role marks entry clerk) will be able add/modified/delete
info regarding marks obtain by different students in different
semesters.
6. User (with role marks entry clerk) will also be able to print mark sheet
of student.
7. User (with role coordinator) will be able to generate printable report.(
as mentioned in session 2.1.2 above. )
8. User (with role administrator) will be able to reset the system leading
to deletion of all existing information the backend database.
9. User (with role administrator) will be able to create /modified /delete
new existing user accounts.

2.3 User characteristics:

 Educational level:
 At list graduate should be comfortable with English
language.
 Experience:
 Should be well-versed/informed about the course structure
of MTACH program of university.
 Entry of marks for their modification can be done only by
user who is authorized for this job by result preparation
committee of University.
 Technical expertise:
 Should be comfortable using general purpose application
on a computer.

2.4 Constraints:

• Since the dbms being used is MS ACCESS 2000 which is not a very powerful
dbms, it will not be able to store a very huge number of records.
• Due to limited features of dbms being used performance tuning features will
not be applied to the quarries and does the system may become slow with the
increases in number of records being stored.
• Due to limited features of dbms database auditing will also not be provided.
 • Users at university will have to implement a security policy to safe guard the
marks related information from being modified by unauthorized users (by
means of gaining access to the backend database).

2.5 Assumptions And Dependencies:

• The number of subjects to be taken up by a student in each semester does not

change.
• The subject types (i.e. elective, core, lab, term-paper and dissertation) do not
change.
• The number of semesters in M.TECH program does not change.

2.6 Apportioning of Requirements:

None.

3. Specific Requirements

This section contains the software requirements to a level of detail sufficient to enable designers
to design the system, and testers to test that system.

3.1 External Interface Requirements

3.1.1 User Interfaces

The following screens will be provided:

Login Screen:
This will be the first screen that will be displayed. It will allow user to access different screens
based upon the user’s role. Various fields available on this screen will be

(i). User ID: Alphanumeric of length upto 10 characters

(ii). Password: Alphanumeric of length upto 8 characters.
(iii). Role: Will have the following values:
Administrator, Marks Entry Clerk, Coordinator, Data Entry Operator

Subject Info Parameters Screen:

This screen will be accessible only to user with role Administrator. It will allow the user to enter
the semester number for which the user wants to access the subject information.

Subject Information Screen:

This screen will be accessible only to user with role Administrator. It will allow user to
add/modify/delete information about new/existing subject(s) for the semester that was selected in
the ‘Subject Info Parameters’ screen. The list of available subjects for that semester, will also be
displayed.

(i). Subject Code: of the format IT-### (# represents a digit)

(ii). Subject Name: Alphanumeric, of length upto 50 characters.
(iii). Category/Type: Will have any of the following values:

Elective 1/Elective 2/Core/Lab/Term Paper/Seminar/Dissertation

(iv). Credits: Numeric, will have any value from 0 to 20.

Student Info Parameters Screen:

This screen will be accessible only to user with role Administrator. It will allow user to enter the
Batch Year for which the user wants to access the student information.

Student Information Screen:

This screen will be accessible only to user with role Administrator. It will allow user to
add/modify/delete information about new/existing student(s) for a particular Batch Year, Batch
Year-wise list of students will also be displayed. Various fields available on these screens will
be:

(i). Student Information: of the format ##M.Tech. (IT)/YYYY (# represents a digit

and YYYY represents the batch year)
(ii). Student Name: will have only alphabetic letters and length upto 40 characters.
 (iii). Batch Year: of the format YYYY(representing the year in which the student
enrolled for the course)

Students’ Subject Choice Parameters Screen:

This screen will be accessible only to user with role Administrator. It will allow user to enter the
Batch Year and the semester number for which the user wants to access the students’ subject
choice information.

Students’ Subject Choice Information Screen:

This screen will be accessible only to user with role Administrator. It will allow user to
add/modify/delete students’ choices for elective subjects of the semester and batch year selected
in “Students’ Subject Choice Parameters” screen. For the selected semester it will display the list
of available choices for Elective I and for Elective II. The screen will display the list of students
enrolled during the selected batch year and currently studying in the selected semester and the
user will be able to view/add/modify delete the subject choices for each student in the list.

Marks Entry Parameters Screen:

This screen will be accessible only to user with role Marks Entry Clerk. It will allow the user to
enter the Batch Year, the semester number and the Subject for which the user wants to access the
marks information.

Marks entry Screen:

This screen will be accessible only to user with role Marks Entry Clerk. It will allow user to
add/modify/delete information about marks obtained in the selected subjects by different
students of that semester who were enrolled in the Batch Year selected in the ‘Marks Entry
Parameters Screen’. The screen will display the selected subject in the selected semester and the
user will be able to view/add/modify/delete the marks for each student in the list. Various fields
available on these screens will be:

(i). Student Enrollment No: will display the enrollment numbers of all students of the
selected Batch Year studying the selected subject in the selected semester.
(ii). Student Name: will display the name of the student.
(iii). Internal Marks: between 0 and 40
(iv). External Marks: between 0 and 60
(v). Total Marks: sum of Internal Marks and External Marks

Mark-sheet Parameters Screen:

This screen will be accessible only to user with role Marks Entry Clerk. It will allow user to
enter the Enrollment Number and the semester number of the student for whom the user wants to
view/print the mark-sheet.
Students’ List Report Parameters Screen:

This screen will be accessible only to user with role Coordinator. It will allow user to enter the
Batch Year for which the user wants to view/print the students’ list report.

Marks List Report Parameters Screen:

This screen will be accessible only to user with role Coordinator. It will allow user to enter the
Batch Year and the semester for which the user wants to view/print the marks list report.

Rank-wise List Report Parameters Screen:

This screen will be accessible only to user with role Coordinator. It will allow user to enter the
Batch Year and the semester for which the user wants to view/print the rank-wise list report.

Students’ Subject Choices List Report Parameters Screen:

This screen will be accessible only to user with role Coordinator. It will allow user to enter the
Batch Year and the semester for which the user wants to view/print the students’ subject choices
list report.

3.1.2 Hardware Interfaces

As stated in Section 2.1.3.

3.1.3 Software Interfaces

As stated in Section 2.1.4.

3.1.4 Communication Interfaces

None

3.2 System Features

3.2.1 Subject Information Maintenance

Description

The system will maintain information about various subjects being offered during different
semesters of the course. The following information would be maintained for each subject:

Subject code, Subject name, Subject Type (Core/Elective1/Elective 2/Lab1/Lab 2/Term Paper/
Minor Project/Dissertation/Se minar), Semester, Credits.

The system will allow creation/modification/deletion of new/existing subjects and also have the
ability to list all the available subjects for a particular semester.
Validity Checks

(i). Only user with role Data Entry Operator will be authorized to access the Subject
Information Maintenance module.
(ii). Ist, IInd and IIIrd semesters will have 2 core papers, 2 Elective Papers, 2 lab papers
and 1 term paper/Minor Project.
(iii). Ist, IInd and IIIrd semesters will have 3 choices(subjects) each of type Elective1 and
of type Elective 2.
(iv). IVth semester will have only 1 dissertation and 1 seminar.
(v). No two semesters will have the same subject i.e., A subject will be offered only in
a particular semester.
(vi). Subject code will be unique for every subject.
(vii). Subject code cannot be blank.
(viii). Subject name cannot be blank.
(ix). Credits cannot be blank.
(x). Credits can have value only between 0 and 20.
(xi). Subject Type cannot be blank.
(xii). Semester cannot be blank.

Sequencing Information

Subject Info for a particular semester will have to be entered in the system before any
student/marks information for that semester can be entered.

Error Handling/Response to Abnormal Situations

If any of the above validations/sequencing flow does not hold true, appropriate error messages
will be prompted to the user for doing the needful.

3.2.2 Student Information Maintenance

Description

The system will maintain information about various students enrolled in the M.Tech(IT) course
in different years. The following information would be maintained for each student :

Student Enrollment Number, Student Name, Year of Enrollment.

The system will allow creation/modification/deletion of new/existing students and also

have the ability to list all the students enrolled in a particular year.
Validity Checks.

(i). Only user with role Data Entry Operator will be authorized to access the Student
Information Maintenance module.
(ii). Every student will have a unique Enrollment Number.
(iii). Enrollment Number cannot be blank.
(iv). Student name cannot be blank.
(v). Enrollment Year cannot be blank.

Sequencing Information

Student Info for a particular student will have to be entered in the system before any marks
information can be entered for that student.

Error Handling/Response to Abnormal Situations

If any of the above validations/sequencing flow does not hold true, appropriate error messages
will be prompted to the user for doing the needful.

3.2.3 Students’ Subject Choices Information Maintenance

Description

The system will maintain information about choice of different Elective subjects opted by
various students of different enrollment years in different semesters. The following information
would be maintained:

Student Enrollment Number, Semester, Student’s Choice for Elective 1 subject, Student’s
Choice for Elective 2 subject.

The system will allow creation/modification/deletion of students’ subject choices and

also have the ability to list all the available students’ subject choices for a particular semester.

Validity Checks

(i). Only user with role Data Entry Operator will be authorized to access the Students’
Subject Choices Information Maintenance module.
(ii). The subject choice for Elective 1 and Elective 2 can be made only from the list of
available choices for that semester.

Sequencing Information
Students’ Subject Choices Info for a particular student can be entered in the system only after
Subject Info has been entered in the system for the given semester and the Student Info for that
student has been entered in the system.

Students’ Subject Choices Info for a particular student will have to be entered in the
system before any marks info can be entered for that student in the given semester.

Error Handling/Response to Abnormal Situations

If any of the above validations/sequencing flow does not hold true, appropriate error messages
will be prompted to the user for doing the needful.

3.2.4 Marks Information Maintenance

Description

The system will maintain information about marks obtained by various students of different
enrollment years in different semesters. The following information would be maintained:

Student Enrollment Number, Semester, Student’s Code, Internal Marks, External Marks,
Total Marks and Credits.

The system will allow creation/modification/deletion of marks information and also have
the ability to list all the available marks information for all students for a particular subject in the
given semester.

Validity Checks

(i). Only user with role Marks Entry Clerk will be authorized to access the Marks
Information Maintenance module.
(ii). Internal Marks for any subject cannot be less than 0 and greater than 40.
(iii). External Marks for any subject will be calculated as: Internal Marks in that
subject + External Marks in that subject.
(iv). If the total Marks in a subject are >= 50, all the credit points associated with that
subject will be given to the student, else the credit points earned by the student
will be 0 for that subject.

Sequencing Information

Marks Info for a particular student can be entered in the system only after Subject Info has been
entered in the system for the given semester, the Student Info for that student has been entered in
the system, and the Students’ Subject Choice Info has been entered in the system for that student
in the given semester.
 Marks Info for a particular student will have to be entered in the system before any that
student’s mark-sheet can be generated.

Error Handling/Response to Abnormal Situations

If any of the above validations/sequencing flow does not hold true, appropriate error messages
will be prompted to the user for doing the needful.

3.2.5 Mark-sheet Generation

Description

The system will generate mark-sheet for every student in different semesters.

Mark-sheet will have the following format:

There will be a ‘Print’ icon at the top of mark sheet for printing the mark-sheet.

Validity Checks

(i). Only user with role Marks Entry Clerk will be authorized to access the Mark-
sheet Generation module.

Sequencing Information
Mark-sheet for a particular student can be generated by the system only after Subject Info has
been entered in the system for the given semester, the Student Info for that student has been
entered in the system, the Students’ Subject Choice Info has been entered in the system for that
student in the given semester, and the Marks Info has been entered in the system for the given
semester.

Error Handling/Response to Abnormal Situations

If any of the above validations/sequencing flow does not hold true, appropriate error messages
will be prompted to the user for doing the needful.

3.2.6 Report Generation

Student List Reports

For each year a report will be generated containing the list of students enrolled in that batch year.

Report Format:

Students’ Subject Choices List Reports

For each batch year a report will be generated containing the list of students and their choices for
Elective subjects in the selected semester. For Ist, IInd and IIIrd semesters the list will contain the
names of elective subjects opted by each student. For IVth semester the list will contain the
topic/subject area of dissertation for each student.

Report Format (for Ist, IInd and IIIrd Semesters):

Report Format (for IVth Semester):

Semester-wise Mark Lists

For each semester a mark list will be generated that will have the total marks (internal + external
) of all students (enrolled in the selected Batch Year) of that semester in all subjects.

Report Format:
Rank-wise List Report

This report will be generated for each semester of every Batch Year. It will show the Grand Total
Marks, Percentage, Rank and Division secured of all students of that semester. The report will be
stored in increasing order of Percentage/Rank.

Report Format:

3.2.7 User Accounts Information Maintenance

Description

The system will maintain information about various users who will be able to access the system.
The following information would be maintained:

User Name, User ID, Password and Role.

Validity Checks
 (i). Only user with role Administrator will be authorized to access the User Accounts
Information Maintenance module.
(ii). User ID cannot be blank.
(iii). User ID should be unique for every user.
(iv). Password cannot be blank.
(v). Role cannot be blank.

Sequencing Information

User Account for a particular user has to be created in order for the system to be accessible to
that user. At the startup, only a default user account for ‘Administrator’ would be present in the
system.

Error Handling/Response to Abnormal Situations

If any of the above validations/sequencing flow does not hold true, appropriate error messages
will be prompted to the user for doing the needful.