Web Application SRS_010322
Web Application SRS_010322
SEMISTER : II
Group No.07
1.1 PURPOSE
The University offering different courses uses manual process of student registration
which is very tremendous. So, it requires an automated process for student registration called
online student registration.
The university student registration system uses manual process registration. It is unable
to deal with infinite number of telephone calls for inquiries, registration, confirmation etc. So, it
needs an online system which will provide users/students an interface for filling information,
listing the courses available, batch information and other details.
So, the objective of the software is to provide an Online Student Registration System
which will be used to provide an interface for displaying the details of courses available,
department information, registration etc so that it will reduce the burden of the registration team.
1.3 REFERENCES
2.0 OVERALL DESCRIPTION
The online student registration system is completely new system and replacement of current
manual process of registration and inquiry by telephone. Figure x describes the functions
involved in an automated student registration system. The system is expected to provide services
of providing availability of courses, department information, schedule, registration and credit and
debit card authorization.
View course
details
Register for a
course
Student Registrar
Retrieve
registration
report
Fig. 1 Student Registration System
Student Registration
Student Browser System
Student The students from various cities willing to apply for the courses uses this software
for knowing the details of various courses available, batches available, schedules
etc. Students willing to register for a course need not to call in university and
register. He or she will register by online.
Registrar The registrar uses the software for retrieving the registered user’s credentials. He
can use the information for allotting the batches and uploading it.
OE-1 The software must work on Microsoft Internet Explorer 7 and above, Mozilla
Firefox and Google chrome.
OE-2 The software should work on university’s server running on Linux Red Hat and
Apache Web server.
OE-3 The online student registration system should provide an authorized access to
registrar within Intranet.
The system shall provide an online hierarchical and cross-linked help system in HTML
that describes and illustrates all the functions.
Students can register for available courses and batches which are updated on website by a
registrar.
3.0 EXTERNAL INTERFACE REQUIREMENTS
1. The user interface should provide navigation list of available courses and
batches with links provides for other details.
2. The user interface should provide the help link describing how to use each link
on interface.
4. The user interface should display all registered user’s information with all
credentials in a tabular form.
5. The user interface should provide registration form with fields for all necessary
credentials.
I. The online student registration system should transform the registered user
credential into a database.
II. To check the course selected is available.
III. To Show updated information.
IV. To authorize a credit or debit card.
V. To transform the data from database into tabular form and display it.
Software should display the list of available courses and details. It should display
the batches information and schedules arranged.
The registrar is an employee from the university who retrieves and updates
the courses information.
5.1 OTHER NON-FUNCTIONAL REQUIREMENTS
PE-1: The system shall accommodate 400 users during the peak usage time window of
8:00am to 10:00am local time, with estimated average session duration of 8
minutes.
PE-2: All Web pages generated by the system shall be fully downloadable in no more
than 10 seconds over a 40KBps modem connection.
PE-3: Responses to queries shall take no longer than 7 seconds to load onto the screen
after the user submits the query.
PE-4: The system shall display confirmation messages to users within 4 seconds after
the user submits information to the system.
5.2 SAFETY REQUIREMENTS
No safety requirements are identified.
Availability-1: The Cafeteria Ordering System shall be available to users on the corporate
Intranet and to dial-in users 99.9% of the time between 5:00am and midnight
local time and 95% of the time between midnight and 5:00am local time.