Software Requirement Specification

Roll No Name
Group
Members

.
DEPARTMENT OF INFORMATION SCIENCES
MULTAN CAMPUS
UNIVERSITY OF EDUCATION
LAHORE

2021-2025
 SRS Title
(Specimen case study)
Software Requirements Specifications
1. Introduction
Asadssjdjda (Ariel, 12 Font)
1.1 Purpose
Assasdad (Ariel, 12 Font)
1.2 Need/Motivation
Sfsdfsdfds (Ariel, 12 Font)
2. Problem Statement
Sdsfsdfdsf (Ariel, 12 Font)
3. Requirements
Dsfdsggfdgfd (Ariel, 12 Font)
3.1 Functional Requirements

No Requirement Description

FR1 Create Semester The Academic Manager can create a new

semester for offering. The semester is
automatically offered to students when the
Semester Registration Start Date is
reached. The following information will be
needed:
● Year
● Type (Spring, Summer, Fall)
● Semester Start Date
● Semester End Date
● Semester Registration Start Date
● Semester Registration End Date
● Course Registration Start Date
● Add Course Last Date
● Drop Course Last Date
● Withdraw Course Last Date
● Classes Start Date
● Classes End Date
FR2 Offer Course The Academic Manager can offer a
previously created course in the semester.
The information provided will be:
● Course (Title + Code)
● CGPA Requirement
● Registration Type
(Primary Sections/Open)

Depends on FR1.
FR3 Create Section Sections have to be created when a
course is offered to students. The
 Academic Course Coordinator enters the
following information must be provided:
● Instructor
● Registration Last Date
● Add Last Date
● Drop Last Date
● Withdraw Last Date
● Class Timings
● Registration Type (Batch-wise/Open)
● Seats Distribution (if Batch-
wise registration)

Depends on FR1 and FR2.

FR4 Semester The student can register in the current
semester. This includes a transaction equal
Registration Request to the Registration Fees in his account.

A student can register in one semester at a

time.

FR5 Add Student to Course When a student’s requests to add a course,

the system will check the number courses
that the student is already registered in and
student’s GPA against the requirement of
the course. For BS and MS, maximum limit
of courses in a semester is 5. The system
will then check for clashes between the
registered courses and the new course.

If a student wants to take 6 courses, the

advisor will have to approve this. A student
with CGPA below 2 also needs approval
from the advisor. The advisor ‘s approval
should be received within 2 days of the
registration, if registration does not close
within those days.

Both BS and MS students must have

successfully cleared all pre-requisites of the
courses that he/she is taking. The student
must have cleared all previous dues to
register for the new semester. The system
will check the number of seats available.

BS students can take MS courses and vice

versa, if they are offered to them. However,
BS students require the course instructor’s
approval for taking a MS course. MS
students require the approval of their
advisor/coordinator for taking any course.
If all checks are validated the students is
registered in the course.
 If the advisor’s approval is required, then
the student has 2 days for getting the
approval (if the last date of registration is
not in those 2 days) and a further 2 days (if
the last date of registration is not in those 2
days) to submit his fees and get his name
finally registered, else his name will be
automatically removed.

If seats are filled he/she is added to the

waiting queue. The student can be added in
3 courses for the waiting list at a time.

FR6 Drop Course The student can request to drop from any
course he is registered in until the add/drop
date. If there are students in the waiting list
for the course, the next student is notified
automatically. The students of the batch to
who this course was offered are given
priority.

The new student has 2 days to confirm this

registration by paying his dues, else his
name is dropped from the waiting list, the
list is updated and the next person is
notified.

Students with CGPA below 2 cannot drop a

course without approval from the advisor.

Depends on FR7.
FR7 Withdraw Course The student can request to withdraw from
any course he is registered in until the
withdraw date. The status is changed to ‘W’
(withdraw) to appear on the transcript.
Students with CGPA below 2 cannot
withdraw from a course without approval
from the advisor.
MS students cannot withdraw from a
course. Depends on FR7.

FR8 View reports The various types of reports that the users
(depending on their access level and role)
can view are:
● Course-wise Registration (specifying
sections)
 ● Student-wise Registration
(specifying sections)
● Waiting List of that Course
(specifying sections)
● Date-wise Add/Drop status of each
student
– This report will be delivered after the
rest of the system, by 15th January 2002.
FR9 Semester Freeze A student can freeze his next or previous
semester by paying the required amount to
Accounts. The fee has to be paid for each
semester (maximum 2) that is to be frozen.
The current semester cannot be frozen if a
student is taking courses.

FR1 Clear Accounts Status The Accounts Officer can clear the status of
0 a student when he pays his dues.
When the student pays his dues or submits
the financial aid/installments application, the
Accounts Officer clears his financial status
so that the student’s seat can be confirmed.
When the student pays his semester freeze
dues the Accounts Officer does the same.

3.2 Non-Functional Requirements

No Requirement Description

NFR Security ● All access to the system will be logged.

1 ● Only an administrator shall be able to create
users.
● Only authorized and authenticated users shall
be able to access the system i.e. a user with
valid username and password and the right
post/domain.
● System operators shall not have access to the
data that they do not need
● Database shall be accessed indirectly using
predefined queries so that there is no direct SQL
injection attack i.e. the user information that may
affect the queries generated for the system or
corrupt database
● Illegal operations may lead to termination of
program. Error handling and exceptions will stop
any illegal operations.
NF User Interface Internet explorer 6.0+ will work as the client application
R2 on Windows.

NF Platform The system will be independent of a single platform

R3 Independen and commercial software.
ce
NF Extensibility The system will be extensible and modular to integrate
R4 with other automated systems as they are developed

NF Performance The system will be able to handle multiple requests

R5 over the Intranet of 50 users at the maximum.
When the applicant submits his information, the
maximum delay before getting a response shall not
exceed 3 minutes
The availability of the application form shall be 24
hours a day during the dates it is uploaded on the
site.
The response time experienced by the administrator
while editing or uploading the application form shall
not be more than 30 seconds.
Accuracy of up to 4 decimal places shall be provided
while generating reports
The software shall produce reports on the data saved
in the database. Therefore, the software has the
capacity to generate reports of any size that is within
the database limits.
After a training of 1 hour of an experienced computer
user, the average number of mistakes made by any
system operator shall not exceed 1 per day
NF User Online help shall be made available for:
R6 Documentati a) The applicants to help them in following the
on application procedure.
b) The candidates giving the test to guide them
through the instructions at the start of the test.
● Reference manual shall be provided for all
system operators defining user interfaces and
functionalities provided by each interface to
assist them in making use of the functionalities
provided.
● Installation manual shall be provided to the
system users.
● Recovery manual shall also be provided to
assist them in case of system failures.
3.3 Hardware Requirements
(Ariel, 12 Font)
3.4 Software Requirements
(Ariel, 12 Font)
3.5 Suggested Model and Why
(Ariel, 12 Font)
3.6 Feasibility Study
(Ariel, 12 Font)
3.6.1 Financial Feasibility
(Ariel, 12 Font)
3.6.2 Technical Feasibility
(Ariel, 12 Font)
3.6.3 Operational Feasibility
(Ariel, 12 Font)