Students Information Sharing System The Real-time System…

Ansan Jose

1/4/2013

2

SOFTWARE REQUIREMENTS SPECIFICATION (SRS) FOR

STUDENTS INFORMATION SHARING SYSTEM

INTRODUCTION

PURPOSE

This SRS Document contains the complete software requirements for the Student

Information Sharing System (SISS) and describes the design decisions, architectural design and

the detailed design needed to implement the system. It provides the visibility in the design and

provides information needed for software support.New reliable and fast school management

software with the great customers support. It'll help you with your daily school management

routines and deliver you from your paperwork.

SCOPE

Students Information Sharing System is developing for Universities / colleges and used to

replace old paper work system and PUMS. OSIMS is to build upon the existing information

system PUMS in order to efficiently provide student information to teachers and school

administration. This increase in efficiency of result making, provide result to parents, give

feedback to student, finally, publication and email student result. It provides a mechanism to edit

the student information form which makes the system flexible.

DEFINITIONS, ACRONYMS AND ABBREVIATIONS

SISS Students Information Sharing System

PUMS Project Units Management System

SRS Software Requirements Specification

J2EE Java 2 Platform Enterprise Edition

OS Operating System

3

OVERALL DESCRIPTION

PRODUCT PERSPECTIVE

This section provides a detailed description of the problem that the software must solve.

Information content flow and structure is documented.

USER INTERFACES

All pages of the system are following a consistent theme and clear structure. The

occurrence of errors should be minimized through the use of checkboxes, radio buttons and

scroll down in order to reduce the amount of text input from user. JavaScript implement in PHP

in order to provide a Data Check before submission. HTML Tables to display information to

give a clear structure that easy to understand by user. Error message should be located beside the

error input which clearly highlight and tell user how to solve it. If system error, it should provide

the contact methods. The page should display the project process in different colour to clearly

reflect the various states that student done. Each level of user will have its own interface and

privilege to mange and modify the project information such as supervisor able to

monitor/manage his student progress and make comment on it, student can change his detail,

view the progress, submit project idea. The System should provide a feedback form for all users

to give comments or asking questions.

HARDWARE INTERFACES

Server Side :

The web application will be hosted on one of the department’s servers and connecting to

one of the school SQL Database server. The web server is listening on the web standard port.

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.

4

SOFTWARE INTERFACES

Server Side :

The required software to host a PHP web application. An Apache Web server will accept

all requests from the client and forward SUMS specific requests to Tomcat 5.5 Servlet Container.

A development database will be hosted locally (using MySQL); the production database is

hosted centrally (using Oracle).

Client Side :

An OS is capable of running a modern web browser which supports HTML version 3.2 or

higher.

COMMUNICATION INTERFACES

The HTTP protocol will be used to facilitate communications between the client and

server.

EXISTING SYSTEM & PROPOSED SYSTEM

Existing system :

The existing system uses different software to perform specific task like admission

management, faculty management, attendance tracking, etc. that are entered manually by user.

There are no common frameworks or seamless integration exists between these systems which

results in maintaining the same set of student information separately for each software module.

Proposed system :

The proposed system provides an integrated solution with a consistent interface and

common database. Because all components of a school management system will share a single

data repository, and user only need to enter information once and it becomes immediately

available to everyone with appropriate need and security access.

Web-based solution combined with seamless application integration, enables students, parents,

teachers, and administrators to participate in increasing student achievement by means of

centralized data repository. And easy-to-use communication tools enable students, parents,

teachers, and administrators to work together to improve student achievement without creating

more administrative overhead. Online access to grades, attendance information, and events

makes it easy for teachers and parents to stay in closer contact on student progress.

5

PRODUCT FUNCTIONS

Students Information Sharing System this software is used to maintain and manage the

information of the student .This software help the user to easy access the information of students.

This software is also helpful for the administrator because he can easily bring changes to the

records of the student.

USER CHARACTERISTICS

The users of the system are students, teachers and the administrators who maintain the

system. The users are assumed to have basic knowledge of the computers and Internet browsing.

The administrators of the system to have more knowledge of the internals of the system and is

able to rectify the small problems that may arise due to disk crashes, power failures and other

catastrophes to maintain the system. The proper user interface, users manual, online help and the

guide to install and maintain the system must be sufficient to educate the users on how to use the

system without any problems.

CONSTRAINTS

The information of all the users must be stored in a database that is accessible by the

Online Student Information Sharing System.

The university information security system must be compatible with the Internet applications.

The Online Student Information Sharing System is connected to the university computer and is

running all 24 hours a day.

The users must have their correct usernames and passwords to enter into the Online Student

Information Sharing System.

ASSUMPTIONS AND DEPENDENCIES

The users have sufficient knowledge of computers.

The University computer should have Internet connection and Internet server

capabilities.

The users know the English language, as the user interface will be provided in

English

The product can access the university student database

6

SPECIFIC REQUIREMENTS

DFD (Level-0)

A Data Flow Diagram (DFD) is a graphical representation of the “flow” of Student

Information System. A data flow diagram can also be used for the visualization of Data

Processing. It is common practice for a designer to draw a context-level DFD first which shows

the interaction between the system and outside entities. This context-level DFD is then

“exploded” to show more detail of the system being modelled.

7

USE CASE DIAGRAM

8

Student Admission & Allotment Management

Application Forms will be available for the candidates online in the institutional

website which will be linked internally to the software application. The applied list of

candidates are sorted out using various parameters such as mark/percentage of marks,

reservation category etc. This filtering generates a set of eligible candidates. They are

converted as selected candidates for interview, then through manual selection procedures

the students are asked to join the institution. During the joining procedure these

candidates become allocated students or set of new admissions.

Faculty Management

Depending upon the availability of the modules the faculty management begins

with the direct/selected enrollment of the faculties. For direct enrollment the details of the

teaching staff is registered through a registration form. The enrolled teaching staff is

made available for the further allocation. The allocations are made against the subjects

for each class. The unallocated/allocated staff list will be helpful for the substitution and

other job assignments.

9

Time Table Management

Rule definers are used to collect some dynamic data from the user such as the

number of working days per week, number of periods available for a day, restriction of

the teaching staff:- maximum number for periods per day, total number of periods for a

week etc. there should be a default value for each of these rules specified above in case

the user did not set any of the values the scheduler should take these default values.

Subject to the above defined values the scheduler will automatically generate a timetable

set for each of the class against the data available from the faculty allocation. The

abstraction of these of these se allows viewing the timetable as faculty time table and

class timetable.

The timetable set shall be manually edited according to the user’s desire.

Academics

Examinations:- Name of the examinations and the scheduled timetable for specified academic

year is created in the examinations procedure. The timetables of the exams available for

the students are visible.

Result & Grading:-

Marks and grades are entered by the concerned staff for each student in

class/batch against the examination names for the current academic year. The report card

is generated for the individual students and mark list for the whole class/batch.

Attendance Markup:-

Attendance markup is done against the list of students in class/batch for the

selected dates. The holidays are detected form the calendar for the attendance marking.

Event Management

Every holidays available for the current academic year is defined here with

reason, these days are automatically blocked from marking the attendance and is set to

the holidays status.

Institutional events and the class/batch events can be declared with two markup options :-

1) Events with automatically setting the attendance as available/present status.

2) Events which needs mark up procedures for setting the attendance status.

10

SOFTWARE SYSTEM ATTRIBUTES

FUNCTIONALITY

Logon Capabilities :

The system shall provide the users with logon capabilities.

Alerts :

The system can alert the administrator in case of any problems.

USABILITY

The system shall allow the users to access the system from the Internet using HTML

or it’s derivative technologies. The system uses a web browser as an interface.

Since all users are familiar with the general usage of browsers, no specific training is

required.

The system is user friendly and self-explanatory.

RELIABILITY

The system has to be very reliable due to the importance of data and the damages

incorrect or incomplete data can do.

AVAILABILITY

The system is available 100% for the user and is used 24 hrs a day and 365 days a year.

The system shall be operational 24 hours a day and 7 days a week.