Software Requirement Specification

Student Registration System

 Table of Content
1. Introduction………………………………………………………………………………………………....03
1.1 Purpose and Scope…………………………………………………………………………….......03
1.2 References…………………………………………………………………………………………....05
1.3 Overview……………………………………………………………………………………………..05
2. Functional Requirements…………………………………………………………………………………..06
2.1 Use case diagram…………………………………………………………………………..............06
2.1.1 Use case for Super user…………………………………………..................................06
2.1.2 Use case for Administrator………………………………………….............................07
2.1.3 Use case for Student………………………………………….......................................08
2.1.4 Use case for Guest…………………………………………..........................................08
2.2 Use cases……………………………………………………………………………………………..09
Use Case 1 : Login into the system…………………………………………………………….09
Use Case 2 : Manage users………………………………………………………….10
Use Case 3 : Add users………………………………………………………………….………11
Use Case 4 : Remove users……………………………………………………………………..12
Use Case 5 : Manage users……………………………………………………………............13
Use Case 6 : Edit profile information………………………………………………………….14
Use Case 7 : Remove selected subjects from student's selections………………………..15
Use Case 8 : Create new subjects……………………………………………………………...16
Use Case 9 : Edit existing subjects………………………………………………………….…17
Use Case 10 : Delete subjects………………………………………………………………….18
Use Case 11 : Create new subject lists………………………………………………………..19
Use Case 12 : Make adjustment of credits per subject……………………………………...20
 Introduction

1.1 Purpose and Scope

The purpose of this System Requirements Specification is to outline the

functional, nonfunctional and business requirements of the “Student Registration
System” of Rajarata University of Sri Lanka. The document provides a detailed
overview of the software product, its parameters and goals.

The main objective of the Student Registration System is to allow internal

students of the university to register for a new semester via internet. The
system will maintain 3 categories of user accounts in performing the tasks.
They are namely “Super user”, “Administrator” and “Student”.
1.2 References

 UML A beginner’s guide- Jason T Roff

 UML DeMYSTiFieD- Paul Kimmel

1.6 Overview of the Document

The next chapter of the document is on functional requirements of the system. It covers
required features of the software product and the services it provides in detail using Activity
diagrams, use case diagrams.

The 3rd chapter of the SRS is on non-functional requirements. This includes the
emergent system properties and constraints on the system such as reliability, portability,
response time.

The 4th chapter includes Entity relationship diagram and class diagram.

The Final chapter includes the verification and validation methods.

2. Functional Requirements
2.1 Use Case Diagram for SuperUser
 2.2 Use Case Diagram for Student

2.3 Use Case Diagram for Guest