Software Requirement Specification

For

Web Portal for Student Information System of E.C.A

Version 1.0

GOVT. ENGINEERING COLLEGE, AJMER

M.C.A BATCH 2009-12

Prepared by: Kirti Kumar Valiya(09MCA23) Vijay Sharma(09MCA58) ChandraShekhar Garg(09MCA11)

Guided by:Mr. Sanjay Singh

DATE: 28/MARCH/2011

Software Requirements Specification for Web Portal of Student Information System

Page ii

Table of Contents

Table of Contents ...................................................................................................................... ii 1. Introduction......................................................................................................................... 1

1.1 1.2 1.3 1.4 1.5 2.1 2.2 2.3 2.4 2.5 2.7 3.1 3.2 3.3 3.4 Purpose ....................................................................................................................................... 1 Document Conventions ............................................................................................................... 1 Intended Audience and Reading Suggestions ............................................................................... 1 Product Scope ............................................................................................................................. 2 References .................................................................................................................................. 2 Product Perspective ..................................................................................................................... 2 Product Functions ....................................................................................................................... 4 User Classes and Characteristics................................................................................................ 11 Operating Environment ............................................................................................................. 11 Design and Implementation Constraints..................................................................................... 12 Assumptions and Dependencies................................................................................................. 12 User Interfaces .......................................................................................................................... 12 Hardware Interfaces .................................................................................................................. 16 Software Interfaces ................................................................................................................... 16 Communications Interfaces ....................................................................................................... 16

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

3. External Interface Requirements ..................................................................................... 12

4. System Features ................................................................................................................ 17

4.1 Manage Information .................................................................................................................. 17

5. Other Nonfunctional Requirements ................................................................................. 18

5.1 5.2 5.3 5.4 Performance Requirements ........................................................................................................ 18 Safety Requirements ................................................................................................................. 18 Security Requirements .............................................................................................................. 18 Software Quality Attributes ....................................................................................................... 18

Appendix A: Glossary ............................................................................................................. 20

Software Requirements Specification for Web Portal of Student Information System

Page 1

1. Introduction
1.1 Purpose
This SRS document contains the complete software requirement for the Student Information System (SIS) and describes its design and architecture. The main objective of this web portal is to provide a self service environment for students, faculty members and academic staff of the college , this information environment system provides reporting, data extraction and information analysis of students for all levels of faculty and academic staff. This is a web application to manage student data. Student Information System provide capabilities for entering student personal information, test and other assessment scores, building student schedules, tracking student attendance, online fee submission and managing many other students related data needs in ECA. The mission of Student Information System project is to create an integrated information technology environment for students, HOD, faculty, staff and administration. Our goal is to focus reducing the paper work and time consumption. Student Information System accepts, process and generate academic reports accurately and any point of time any user can get the student information.

1.2 Document Conventions

There are no standard document requirements for this document.

1.3 Intended Audience and Reading Suggestions

This document is intended for any individual user, developer, tester, project manager or documentation writer that needs to understand the basic system architecture and its specifications. y Developer: The developer who wants to read, change, modify or add new requirements into the existing program, must firstly consult this document and update the requirements with appropriate manner so as to not destroy the actual meaning of them and pass the information correctly to the next phases of the development process. User: The user of this web portal reviews the diagrams and the specifications presented in this document and determines if the web portal has all the suitable requirements and if the web portal developer has implemented all of them. Tester: The tester needs this document to validate that the initial requirements of this web portal actually corresponds to the executable code correctly.

For each one of the reader types to better understand this document, here is a suggestion of the chapters to read in this document: Developer: (1.1, 1.3, 2.2, 2.3, 2.5, 2.7, 3, 4, 5 and rest)

Software Requirements Specification for Web Portal of Student Information System

Page 2

User: (1, 2.1, 2.2, 2.3, 3.1, 5.5) Tester: (1.1, 2, 3, 4, 5)

1.4 Product Scope

Student Information System (SIS) is a web-based application for students, faculty, academic staff and parents who wants to get and retrieve students whole information instantly via internet. The major benefit of this web portal is to store the students information at one place (like SERVER) and it can be accessed via online interaction. The SIS web portal is to replace the old and traditional file(paper work) storing process. Instead of tedious paper work, students will be able to submit required information electronically, and the departments will be able to evaluate the submissions with a much quicker turnaround. Benefits and Goals for using SIS web portal y Quick and full information retrieval y Time saving process y High security level of data y Multiuser environment y Global access of data y No repetition of data

1.5 References
1. Get Real Website http://getreal.ous.edu 2. Requirement Specifications Documentation http://www.scribd.com 3. Software Engineering Text- Roger Pressmen 4. Software Engineering Text- Summerville

2. Overall Description

2.1 Product Perspective

The SIS web portal is a sub system of a large system (WEB SITE OF ENG. COLLEGE, AJMER ). That is functionally relates to E.C.A web site for providing the facilities of retrieving overall academic information of students. Relationship and Linking of SIS web portal sub system with Large System (ECA Web site)

Software Requirements Specification for Web Portal of Student Information System

Page 3

Fig: 2.1 SIS Web Linking Interface: CLIENT (User) LOCAL NETWORK

Application

LOCAL SERVER

SQL SERVER

Software Requirements Specification for Web Portal of Student Information System

Page 4

Fig: 2.2 Interface Design

2.2 Product Functions

MODULE-ONE :- LOGIN AS ADMINISTRATOR In this module when the administrator will enter his/her user name and password, then he/she will enter in to the administrator page and this page consists of two following sub modules. y SUBMODULE-ONE: ADD AND UPDATE DATA IN WEB PORTAL When the administrator clicks this link then a data add form will appear. In this form the administrator of ECA will uploads the results, attendance, notices etc and also can modify the existing academic information of student.

SUBMODULE-TWO: DELETE STUDENT The administrator can delete the whole student information by clicking this link. By providing the user id of the student, the student information can be deleted.

MODULE-TWO: LOGIN AS STUDENT In this module when a user enters his student id and password, then he can visit all the following pages. y Profile: When the student clicks on this link he/she will get his/her information like student id, student name, password, father name, date of birth, nationality, city, address, country, phone number, mobile number, email. If he/she wants then he/she can change the profile. Notice: When the student clicks on this link, he can see latest notices released by the administrator. Attendance: When the student clicks on this one, the student can get his overall attendance percentage (present and absent). Internal Results: When the student clicks on this, he/she will get the internals result in all the subjects. How much grade point he/she secure out of 20 he/she can know. Time Table: When the student clicks on this link then he/she get all the information that on which day which room which class will be held at which time. Fee: When the student clicks this link he/she can get all the fees structure semester wise and annual fee.

Software Requirements Specification for Web Portal of Student Information System

Page 5

The Student Helpdesk: This helpdesk is staffed by faculty who are there to help you. You may contact on (faculty phone no.). Possible reasons you would contact the student helpdesk
y y y y

Something wrong with the computer you are using Learn how to use computer devices You have forgotten your username or password Problem regarding to any software package

General Use Case Diagram: This use case diagram shows overall functionality of this web portal.

Authentication and Validation

Registration

Student/Admin

Major Functions

Get Information

Fig: 2.3 General Use Case

Software Requirements Specification for Web Portal of Student Information System

Page 6

Student Use Case Diagram: This use case diagram shows all functions performed by the user (student) of this web portal.
Student Login

Notices

Attendance

Profile

Student
Internal Result

Data Base

Time Table

Fee

Logout

Fig: 2.4 Student Use Case

Administrator Use Case Diagram: This use case diagram shows all functions and authorization of this web portal.
Admin Login

Add Student Admin Data Base Delete Student

Update Student Record

Fig: 2.5 Admin Use Case

Software Requirements Specification for Web Portal of Student Information System

Page 7

Activity Diagram of SIS:

Fig: 2.6 Activity Diagram

Software Requirements Specification for Web Portal of Student Information System

Page 8

Data Flow Diagram of SIS:

0-LEVEL DFD of SIS

Fig: 2.7 0-Level DFD

Software Requirements Specification for Web Portal of Student Information System

Page 9

1-LEVEL DFD of SIS

Fig: 2.8 1-Level DFD

Software Requirements Specification for Web Portal of Student Information System

Page 10

Integrated DFD of SIS

Fig: 2.7 DFD of SIS

Software Requirements Specification for Web Portal of Student Information System

Page 11

2.3 User Classes and Characteristics

User class Student This section is for students of ECA Student Registration Form: Student can be register on the system and fill in all detail. Change Detail: Student can change detail if information is incorrect such as telephone number. Change Password: Student can change his login password at any time for security reason. Forget Password: Student can request his password if he/she forgotten the password.

1. 2. 3. 4.

User class Academic Staff All staff can view the details of any student. User class System Administrator 1. List Student: System Administrator can list all students in different period of different group to check any error. 2. Change Password: System Administrator can reset the students password if required. User Characteristics: y y y y Every user must have basic knowledge of English. He should be able to work with computer. All users must have his/her unique login name and password for join web portal. The user should know the details (meaning) of the operation.

2.4 Operating Environment

This program will operate in the following operating environment for the client and the server. GUI: The SIS designed to operate at full capacity on the following systems: Windows XP, Vista & 7: Internet Explorer, Firefox, Safari, Opera, Google Chrome, LunaScape, Lynx Ubuntu (Linux) : Firefox

Software Requirements Specification for Web Portal of Student Information System

Page 12

2.5 Design and Implementation Constraints

The system need to design base on the existed code and database using JAVA 1.6, JSP, SERVLET, HTML and SQL 2005. So a minimum PC having at least 256mb of RAM and CPU over PENTIUM4 is required to run the program with good speed. Also the program uses at least 40gigabytes of hard disk space to store the program libraries.

2.6 Assumptions and Dependencies

Although basic password authentication and role based security mechanisms will be used to protect SIS from unauthorized access; functionality such as inserting, deleting and updating are assumed to be sufficiently protected under the existing security policies applied by the SIS developing team. The correct functioning of SIS will partly be dependent on the correctness of the data stored and managed as a part of ECA website. For creating this web portal and setting up the core program JAVA framework and classes will be used that offers a complete set of tools for developing this project. For better understanding the know-what to do rather than the know-how to do it we assume that the reader is not interested for knowing how to create and design web portal and how the program is coded.

3. External Interface Requirements

3.1 User Interfaces

All pages of the system will follow a consistent theme and clear structure. Each level of user will have its own interface and privilege to mange and modify the project information such as administrator able to monitor/manage his/her student progress and make comment on it, student can change his/her detail, view the progress. The System should provide a feedback form for all users to give comments. It will provide a platform to minimize the workload of system administrator.

Software Requirements Specification for Web Portal of Student Information System

Page 13

This figure shows login interface

Fig: 3.1 Login Interface

Software Requirements Specification for Web Portal of Student Information System

Page 14

Interface for adding student Information

Fig: 3.2 Student Info Entry Form

Software Requirements Specification for Web Portal of Student Information System

Page 15

Interface for showing student information

Fig: 3.3 Student Profile Form

Software Requirements Specification for Web Portal of Student Information System

Page 16

3.2 Hardware Interfaces

y Server Side The web application will be hosted on one of the web servers and connecting to Database server also. y Client Side The system is a web based application; clients are requiring using a modern web browser such as Mozilla Firebox 1.5, Internet Explorer 6 and Enable Cookies. The computer must have an Internet connection in order to be able to access the system. And TCP protocol for the client to connect to the server in online mode.

3.3 Software Interfaces

Back End : Front End : User Side : MS SQL Server2005 JAVA1.6, J2EE Framework(Servlet, Jsp,Html) Appropriate Web Browser

3.4 Communications Interfaces

Setting up the server into server mode requires that there will be open ports for accepting connections from the clients. The connection between the client and the server uses Connection oriented communication, via TCP/IPTransfer Control Protocol/Internet Protocol, implements reliable delivery of messages. Connection-oriented communication makes programming easier because the protocol includes mechanisms for detecting and handling errors and an acknowledgment mechanism between client and service. Again we assume that the reader is not interested of how that is implemented into the program at this phase so there will be no more details of this now.

Software Requirements Specification for Web Portal of Student Information System

Page 17

4. System Features

4.1 Manage Information

a. Description and Priority The administrator can create, modify, view and remove student info. This is of high priority because it is the starting point of the context process. b. Stimulus/Response Sequences When any student wants to register on SIS web portal, then administrator will provide unique login id and password to student. The administrator will then view the progress of all students as needed, modify students information and can remove them as needed. c. Functional Requirements 4.1.c.1 The administrator can also add student information to SIS and the student information will be stored in the database. If a student has already been entered, an error message will be displayed and nothing changed in the system. 4.1.c.2 The administrator will be able to modify student information. When modifications are made, the new information will be set in the database. 4.1.c.3 The administrator will be able to view the progress of all students. The administrator will select student to view their information, including attendance, test marks and feedback. 4.1.c.4 The administrator will be able to remove student from the system. This will remove student, its all academic information.

Software Requirements Specification for Web Portal of Student Information System

Page 18

5. Other Nonfunctional Requirements

Here we specify some nonfunctional constraints that the program satisfies in order to be more concrete and stable.

5.1 Performance Requirements

Performance: checking the fact that the system must perform as what every user expects .So in every action-response of the system, there are no immediate delays. In case of opening web forms, of popping error messages and saving the settings or sessions there is delay much below 2 seconds, In case of opening databases, sorting questions and computing there are no delays and the operation is performed in less than 2 seconds for opening, sorting, computing > 95% of the files. Also when connecting to the server the delay is based on the distance of the 2 systems and the configuration between them so there is high probability that there will be or not a successful connection in less than 20 seconds.

5.2 Safety Requirements Consistency: checking the fact that all clients must be attachable to one server, so there would be appropriate control of the test statistics and information. Also in case of a potential loss of connection between the client and the server the clients test progress so far is lost. When the client finishes its test (by pressing the finish button) then its progress is sent to the server and be logged. In case of a potential server breakdown only the so far finished tests are saved to the log file. 5.3 Security Requirements This program uses object oriented mechanisms to protect its data passed using methods also there is no currently a security schema of this program. Thus the log files that are being created are readable using a simple text reader. 5.4 Software Quality Attributes Availability: Checking that the system always has something to function and always pop up error messages in case of component failure. In that case the error messages appear when something goes wrong so to prevail availability problems. Usability: Checking that the system is easy to handle and navigates in the most expected way with no delays. In that case the system program reacts accordingly and transverses quickly between its states.

Software Requirements Specification for Web Portal of Student Information System

Page 19

Functionality: Checking that the system provide the right tools for editing question databases, creating session tests and analyzing the test sessions. In that case the tools that the Database editor provide are the ones that provide that attribute.

Appendix A: Glossary
Here we list all the terminology that is used throughout the document: SRS: Software Requirements Specification SIS: Student Information System Connects: Links this requirement with another Includes: Has the appropriate constraint in it Extends: Shows or cancels a constraint effect if the conditions are met.