Online Srs

Embed Size (px)

Citation preview

SOFTWARE REQUIREMENTS SPECIFICATION OF ONLINE COUNSELING SYSTEM

Table of Contents1). Introduction1.1 Purpose of this document1.2 Scope of this Document1.3 Intended Audience1.4 Document Overview2). Overall description2.1 Product Perspective2.2 Product Functions2.3 Design and Implementation Constraints2.4 Assumptions and Dependencies3). External Interface Requirements3.1 User Interfaces3.2 Hardware Interfaces3.3 Software Interfaces4). Functional Requirement Specifications 4.1 System Features4.2 Functional Requirements5). Non Functional Requirements5.1 Performance Requirements5.2 Security Requirements5.3 Portability Requirements5.4 Maintainability5.5 Reliability

1) INTRODUCTION1.1 Purpose of this document The purpose of this SRS document is to specify software requirements of the Online Counseling System 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.

1.2 Scope of this Document This projects aim is to automate the system, pre-checking the inclusion of all required material and automatically ranking each students application based on a number of criteria. These criteria include the ranking of their university, their grade at said university and their language grade Certificate. The data used by the system is stored in a database that will be the centre of all information held about students and the base for the remainder of the process after the initial application has been made. This enables things to be simplified and considerably quickened, making the jobs of the people involved easier. It supports the current process but centralizes it and makes it possible for decisions to be made earlier and easier way.

1.3 Intended Audience Administrator Students University staff

1.4 Document OverviewThis Online Counseling System aims to make the admission process easier through this online system. This document helps us to understand and sort out the Product Function, User Interface, Design and Implementation Constrains and Assumption and Dependencies of Online Counseling System.

2. OVERALL DESCRIPTION2.1 Product PerspectiveThis software can help the students to get details about the availability of courses in each college with the eligibility criteria through online. The university can maintain all the details of the students in a better way through the computerized systems.

2.2 Product FunctionsIntended Users of the Online Counseling System are Administrator Students University Staff

Administrator Login -Admin enters his own username and password. -It should be unique Add/Update/Maintain Student Record Database Add/Update/Maintain College Information Rank Generation/Publishing Students

Students Login View College Details Apply For Counseling Select the college through counseling process

University Staff Login Allot the selected college to the particular student Generate Admission Report

2.3 User CharacteristicsAdministrator Maintain the student record database Maintain College information like Department, Number of Seats available, Cutoff marks will be maintained by the administrator Updating the student information, college information Maintain the user accounts of the system

Students Register to the system Update the Academic, Personal information View rank, Counseling date Queries the college information database

University Staff Register to the system Allocate students to the colleges Generate the reports for the admitted student

2.4 Design and implementation constraints Some of the design and implementation constraints identified are listed below: Student is not allowed to register for more than three courses. Student not has any rights to edit any data in the system. Student pays the application fees in VPP or DD or MO to register for Course. Online Payment facility may be restricted if the university not want this facility for some reasons. This system is not support distributed database Facility. System is limited to HTTP/HTTPS Protocols.

2.5 Assumptions and Dependencies

Courses are already created and informations available for use. Roles and responsibilities are already established. Administrator is already created.

SARAVANAN.S110081101041YOUSUF IBRAHIM.G110081101064JIM JOSEPH0908010

3. EXTERNAL INTERFACE REQUIREMENTS 3.1 User Interface Front end requirement: web browsers Chrome, Mozilla Firefox. Back end requirement: MS SQL Server Management Studio 2008.

3.2 Hardware Interface Operating System: Windows 7. System Memory: 2GB or higher. Processor: Pentium dual core or higher version.

3.3 Software InterfaceFront end: Net Beans IDE 7.0.1. Back end: JDK 7, JRE 7.

4. FUNCTIONAL REQUIREMENT SPECIFICATION4.1 System Features Students can easily get the details about the each college with its eligibility criteria. Students can be easily classified according to the marks obtained in the HSC examination. University can easily maintain the students record easily. Make rank generation process and admission process easier. 4.2 Functional Requirements 4.2.1 Front end Requirements Login Registration Counseling date and Rank publishing Status Checking Counseling Panel Admission Report Generation4.2.2 Back end Requirements Login Rank Generation Counseling date scheduling Counseling Status Updating

5. NONFUNCTIONAL REQUIREMENTS

5.1 Performance Requirements

Some Performance requirements identified is listed below:

The database shall be able to accommodate a minimum of 10,000 records of students.

The software shall support use of multiple users at a time. There are no other specific performance requirements that will affect development.

5.2 Security Requirements

Some of the factors that are identified to protect the software from accidental or malicious access, use, modification, destruction, or disclosure are described below. Specific requirements in this area could include the need to:

Utilize certain cryptographic techniquesKeep specific log or history data setsAssign certain functions to different modulesRestrict communications between some areas of the programCheck data integrity for critical variablesLater version of the software will incorporate encryption techniques in the user/license authentication process.The software will include an error tracking log that will help the user understand what error occurred when the application crashed along with suggestions on how to prevent the error from occurring again.Communication needs to be restricted when the application is validating the user or license.(i.e., using https)

5.3 Portability Requirements

Some of the attributes of software that relate to the ease of porting the software to other host machines and/or operating systems.

5.4 Maintainability

The user will be able to reset all options and all stored user variables to default settings.

5.5 Reliability

Some of the attributes identified for the reliability is listed below:

All data storage for user variables will be committed to the database at the time of entry. Data corruption is prevented by applying the possible backup procedures and techniques.