Software Requirements

Specification
For

“Student Portal”

Version 1.0 approved

Prepared by:

1- Hassan Mehdi
2- Wasiq Karim
3- Shoaib Arif
4- Zehra Ali

PAF-KIET

Dated: 15/2/2019

Copyright © 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
Software Requirements Specification for <Project> Page ii

Table of Contents
Table of Contents...........................................................................................................................ii
Revision History.............................................................................................................................ii
1. Introduction..............................................................................................................................1
1.1 Purpose...........................................................................................................................................1
1.2 Document Conventions..................................................................................................................1
1.3 Intended Audience and Reading Suggestions.................................................................................1
1.4 Product Scope.................................................................................................................................1
1.5 References.......................................................................................................................................1
2. Overall Description..................................................................................................................2
2.1 Product Perspective........................................................................................................................2
2.2 Product Functions...........................................................................................................................2
2.3 User Classes and Characteristics.....................................................................................................2
2.4 Operating Environment...................................................................................................................2
2.5 Design and Implementation Constraints.........................................................................................2
2.6 User Documentation.......................................................................................................................2
2.7 Assumptions and Dependencies......................................................................................................3
3. External Interface Requirements...........................................................................................3
3.1 User Interfaces................................................................................................................................3
3.2 Hardware Interfaces........................................................................................................................3
3.3 Software Interfaces.........................................................................................................................3
3.4 Communications Interfaces............................................................................................................3
4. System Features.......................................................................................................................4
4.1 Login/Register Panel......................................................................................................................4
4.2 Student Profile................................................................................................................................5
4.3 Courses...........................................................................................................................................6
4.4 Library............................................................................................................................................6
4.5 Fee Statement.................................................................................................................................6
4.6 Student Grades................................................................................................................................7
4.7 Student Queries...............................................................................................................................7
4.8 Data integrity & Security................................................................................................................8
5. Other Nonfunctional Requirements.......................................................................................8
5.1 Performance Requirements.............................................................................................................8
5.2 Safety Requirements.......................................................................................................................8
5.3 Security Requirements....................................................................................................................8
5.4 Software Quality Attributes............................................................................................................8

Revision History
Name Date Reason For Changes Version
Software Requirements Specification for <Project> Page 1

1. Introduction

1.1 Purpose
The purpose of this software is to provide student a portal from which they can manage their
courses, fees, files and more. This document covers all the functional and nonfunctional
requirements proposed by our professor.

1.2 Document Conventions

Following are the document conventions:

 Admin: An admin login ID with administrator privileges.

 Student: Intended Students who would like to use the software.
 Database: SQL Server with relational Database.
 Forms: Windows forms for user to interact.

1.3 Intended Audience and Reading Suggestions

This project is prototyped for Students. It would be read by sir Ayub Latif.

1.4 Product Scope

The purpose of this software is to ease students and the admin by providing a convenient way for
them to register their courses, managing their fee statements, keeping their private files, and
some other stuff like book issue e.t.c. The system is based on relational database supporting a
large number of students. Above all, we hope to provide an easy user interface for students and
admin to interact.

1.5 References
 http://lms.pafkiet.edu.pk/
 SRS documentation (IEEE standards)

2. Overall Description

2.1 Product Perspective

 Student portal is a desktop application which will provide students to login to the
database. Student can manage their profile, view and register the courses added by the
admin, Issue and return a book from library, review fee Statements and review fee bill,
submit queries to admin, and review grades.
Software Requirements Specification for <Project> Page 2

 Admin can manage its profile, registered students and assign and add courses to the
department for the students to enroll, manages Student information and reply to the
student queries.

2.2 Product Functions

This program has the following functionalities:

1. Students

 Login
 Manage profile
 Enroll courses
 Access library
 View fee statement
 Submit queries
 View Grades
 Logout
2. Admin
 Login
 Manage profile
 Registered students
 Add, update, delete courses
 Manage student info
 Reply student queries
 Announcements

2.3 User Classes and Characteristics

Following user classes are identified:

1. Student:
 Will be using this portal to manage their activities.
2. Admin
 Admin will be reviewing student activities.
3. Courses
 This will be assigned by Admin and enrolled by Students.
4. Library
 Admin will add books and students will issue them.
5. Department
 A department will be assigned to students.
6. Fee Statement
 Student can review fee statement and generate fee bill.
7. Queries
 Student will submit queries and admin will resolve them.
8. Marks
 Admin will be generating student grades.
Software Requirements Specification for <Project> Page 3

Operating Environment
Operating environment for the Student portal is listed below.
1. Windows based OS (7 or later)
2. SQL Server database (2008 or later)
3. Platform: Visual Studio (C#, Winforms)

2.4 Design and Implementation Constraints

There is no such constraints except for some of the few listed.

 Windows 7 or later
 Ram: 512MB or more
 System: Core2duo (2.0ghz) or above
 Database: SQL Server 2008 or later
 A working internet connection

2.5 User Documentation

The software will be an easy to use application, there would be no manual required to operate.

2.6 Assumptions and Dependencies

The dependencies required are:

 Microsoft Visual Studio 2015

 Microsoft SQL Server (Database)

3. External Interface Requirements

3.1 User Interfaces

This is a desktop application. The GUI will be user friendly. The user will be able to add, update
any info in a list or a textbox format for their ease. A back and Home button will be there at every
form. The User interface will be needed at every information exchange with the Student and other
entity classes.

3.2 Hardware Interfaces

The minimum hardware requirements are as follows:
 RAM: 512 MB
 Processor: Core2duo (2.0ghz)
 HDD: 10 GB
 Network: Ethernet or WIFI
 OS: Windows 7 or above
 .Net Framework 4.5 or above
Software Requirements Specification for <Project> Page 4

3.3 Software Interfaces

 Database: MS SQL Server
 Application: DotNet Framework 4.5 or above for Windows Forms

3.4 Communications Interfaces

Executable file will be opened through a Windows OS. The need for dotnet 4.5 or above is
needed as the software will be compiled on it. A network connection will be needed for Student
portal to access the database on the server.

4. System Features

4.1 Login/Register Panel

4.1.1 Description and Priority

A login panel comprises of two types of login. Student and the admin login. Only
one admin but multiple Students.
4.1.2 Stimulus/Response Sequences
 Admin can login through the panel.
 Admin will create Student ID and its profile.
 Students can then login to their portal.
4.1.3 Functional Requirements

 Login page:
This page will consist of 2 textboxes named Username and Password and a Submit
button. The Student or the Admin fills in the page and if typed correctly they will be
redirected to the dashboard.

 Register page:
Admin will login to the system and will register the Student. Page will comprise of
Register button along with several fields. ID, Name, Father name, Gender, DOB,
NIC, Mobile, Residence, Nationality, Email, Religion, Department. The admin fills in
the information and registers the Student.

4.2 Student Profile

4.2.1 Description and Priority

A profile page where Student can manage its information.
4.2.2 Stimulus/Response Sequences
 Student logs in.
 Student clicks on profile
 A form is showed containing Student information.
4.2.3 Functional Requirements
Software Requirements Specification for <Project> Page 5

 Profile page:
This page will consist of several read only and some editable fields. Read only
fields: ID, Name, Father Name, Gender, NIC, DOB, and Department. Editable
fields: Mobile, Residence, Nationality, Religion, Email.

 Student can update profile:

Student can update the editable fields only. Read only fields are just to be viewed
by the student.

4.3 Courses

4.3.1 Description and Priority

Courses panel for admin as well as students. Admin can add courses while
students will enroll them.
4.3.2 Stimulus/Response Sequences
 Admin add courses within a department.
 Student can enroll the course.
 Admin can also edit and delete course.
4.3.3 Functional Requirements

 Add a course:
Admin can only add a course by logging in and then going to the course panel. The
fields required for adding a course: ID, Name, Cr Hours, Fee, Days, Time and
Department.

 Delete a course:
Admin can delete a course from the panel. Selecting a course from dropdown and
then removing the course. The course should also be removed from Student’s
enrolled courses.

 Enroll a course:
Student can enroll a course by going to the courses panel. The courses which are
being offered by the admin for the department will only be viewed by students of the
specific department. Student can then enroll the course by selecting it and clicking
on enroll button.

 Drop a course:
After Selecting an enrolled course. Student can drop the course from the list by
selecting it and clicking on drop.

4.4 Library

4.4.1 Description and Priority

Students can issue a book and then return later on. A library will be managed by
the administrator.
4.4.2 Stimulus/Response Sequences
Software Requirements Specification for <Project> Page 6

 Admin adds a book

 Student issues the book
 Student returns it later.
 Book is then again added to be issued.
4.4.3 Functional Requirements

 Add a book:
Admin can add a book to the library. The required fields are: ID, Name, Author,
Edition and Category.

 Remove a book:
Admin can remove a book from the library. The book must not be issued by anyone
while it’s deleted.

 Issue a book:
Students can issue a book which is available. The student has to return a book
within 7 days of time else they would be charged a fee.

 Return a book:
Issued book by the student will have to be returned within 7 days. Student can
return the book issued. If the book is not returned within the due time, a charge of
20 r.s per day will be fined.

4.5 Fee Statement

4.5.1 Description and Priority

Students will be reviewing the fee statement from the panel.
4.5.2 Stimulus/Response Sequences
 Student can generate fee bill of the courses.
 Student can view fee statement.
 Student can pay the fee.
 Admin can monitor the statement.
4.5.3 Functional Requirements

 Generate fee bill:

Student can generate the fee bill after selecting a course from the course panel.
The fee of the course will be added to the bill. The result will be reflected in fee
statement once the bill has been generated.

 Pay fee bill:

Student can pay the fee bill after generating it. He/she has to enter the amount
equal to the fee bill in order to continue. Once the fees have been paid, Statement
is updated under fee statement.

 View fee statement:

Student can review the transaction and the statement of the fees anytime he/she
wants.
Software Requirements Specification for <Project> Page 7

4.6 Student Grades

4.6.1 Description and Priority

Registered courses of the students will be having final marks after the course
completion. A grade will be added.
4.6.2 Stimulus/Response Sequences
 Student enroll course.
 Admin enter marks.
 Grade is assigned by system.
 Student can view grade sheet.
4.6.3 Functional Requirements
 Add course marks:
Admin will be adding student marks according to the course.

 View grade sheet:

Student can view grade sheet. Grade will be assigned to the course when the
admin enters the marks.

4.7 Student Queries

4.7.1 Description and Priority

A query panel for students will allow them to write queries for admin to resolve.
4.7.2 Stimulus/Response Sequences
 Student adds a query
 Admin view and replies it.
4.7.3 Functional Requirements

 Add a query:
Student will type a query in text format and submit it to the admin.

 Add a reply:
Admin can reply to the query.
Software Requirements Specification for <Project> Page 8

4.8 Data Validation & Integrity

4.8.1 Description and Priority

Every field will be containing data validation and verification along with data integrity
to make sure the program is error and bug free.
4.8.2 Functional Requirements

 User input validation:

Each user input will be validated on its data type. The error will be showed instantly
if the user enters data in an incorrect format.

 Data integrity:
The system will make sure if the program is stuck at any time. There will be no loss
of data.

5. Other Nonfunctional Requirements

5.1 Performance Requirements

The software (if met with the minimum requirements) should perform fast enough without any
uncertainty. The response time of the software will be in milliseconds.

5.2 Safety Requirements

At any time, the software can be stuck. Therefore, data integrity will be added along with some
data backups.

5.3 Security Requirements

The required software will be as a desktop application along with SQL server therefore the
queries and the inputs will be protected from SQL injection and other exploits.

5.4 Software Quality Attributes

The software will be easy to use so there would be no such manual or need of any help. The
interfaces will be user friendly.