Software Requirements Specification for Online University Admission System

Page 1

Table of Contents
Table of Contents........................................................................................................................... 1 Revision
History............................................................................................................................. 3 1.
Introduction................................ ................................ ................................ ............................. 4

1.1 Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.2 Document Conventions. . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.3
Project Scope. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.4 Abbreviations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1.5
Benefits of System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 1.6 References. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 1.7
Technologies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 1.8
Overview............................................................................................................................... 9

2. Overall Description................................ ................................ ................................ ............... 11

2.1 Product Perspective. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 2.2 Product Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 2.3 User
Classes and Characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . 14 2.4 Design and Implementation
Constraints................................................................................. 15 2.5 User
Documentation........................................................................ ..................................... 15 2.6 Assumptions and
Dependencies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . 15 2.7 Apporting of Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

3. System Requirments and Analysis................................ ................................ ....................... 17

3.1 User Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 3.2 Student View Functiona
lity................................................................................................... 17 3.3 Admission View Functionality. . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 3.4
Tutor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 3.5 System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.........................................................................................
. . . . . 20

4. Supplementary Requirements................................ ................................ .............................. 21

5. Other Nonfunctional Requirements................................ ................................ .................... 22

5.1 Performance Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 5.2 Security
Requirements.......................................................................................................... 22 5.2 Portability Requirements. . .
.........................................................................................
. . . . . . . . . . 23
Software Requirements Specification for Online University Admission System
Page 2

5.2 Maintanability Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 5.2 Reliability Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 5.2 Usability Requirements. . .
.........................................................................................
. . . . . . . . . . . . 23 5.2 Availability Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 5.4 Software System
Attributes................................................................................................... 24

6. Change Management Process............................................................................................... 24 7. Documentation

Approvals................................ ................................ ................................ .... 24 8. Supporting
Information................................ ................................ ................................ ........ 22 Appendix A:
Glossary................................ ................................ ................................ ................. 25 Appendix B: Analysis
Models..................................................................................................... 27

Software Requirements Specification for Online University Admission System

Page 3

Revision History
Name
Date
Reason For Changes
Version
Software Requirements Specification for Online University Admission System
Page 4

1. Introduction
Student admissions are a vital part of any universitys running because students are what keep a University alive. The
student admission is one of the most important activities within a university as one cannot survive without students. A
poor admissions system can mean fewer students being admitted into a university because of mistakes or an overly
slow response time.

The process begins with a potential student completing an application form through the Universities and Colleges
Admissions Service, the first step for students is to apply directly to the university through a custom online form.

The next step is for the Admissions service center has to review the application and ensure that all of the required
information has been provided, from the form itself to the supplementary documentation, such as language and degree
certificates. If any of the required information is missing, it is the secretary for the department to which the application
concerns that contacts the potential student and arranges for the delivery of the outstanding data.
The application in its entirety is then forwarded, complete with a recommendation, to the respective
departments Admissions Tutor, who has the final say as to whether each potential student is

accepted or rejected. Before making a decision, the Admissions Tutor reviews the application and the additional
documentation, comparing the academic credentials to a list of university rankings and previous, similar applications.
1.1P urpo se

The purpose of this SRS document is to specify software requirements of the Online Admission for the university. It is
intended to be a complete specification of what functionality the admission provides. The main purpose of the system is to
automate the task carried out by different peoples in the organization to perform the student admission. Specific design and
implementation details will be specified in a future document.

Online University Admission System

Download this Document for FreePrintMobileCollectionsReport Document

Info and Rating

srs
system requirements specification
university admission system
online admission system
(more tags)
Follow

vignesh