1 INTRODUCTION.........................................................................................................2 1.1 Document Purpose..................................................................................................2 1.2 Scope.......................................................................................................................3 1.3 Definitions, Acronyms and Abbreviations.............................................................3 1.4 References...............................................................................................................4 1.5 Overview.................................................................................................................

4 2 Overall Description........................................................................................................4 2.1 Product Perspective.................................................................................................4 2.1.1 System Interfaces.............................................................................................5 2.1.2 User interfaces..................................................................................................7 2.1.3. Hardware interfaces........................................................................................7 2.1.4. Software interfaces..........................................................................................8 2.1.5. Communications interfaces.............................................................................8 2.1.6. Memory...........................................................................................................8 2.2 Product Functions ..................................................................................................8 2.2.1 Admit Student Use Case..............................................................................9 2.2.2 Library Membership Creation......................................................................9 2.2.3 Create Web User .........................................................................................9 2.2.4 Manage Attendance...................................................................................10 2.2.5 Send Warning Mailers...............................................................................10 2.2.6 Issue Books................................................................................................11 2.2.7 Return Book...............................................................................................12 2.2.8 Create Roles...............................................................................................12 2.2.9 Time Table Management...........................................................................12 2.2.10 Student Exam Management.....................................................................13 1|Page

2.3 User characteristics...............................................................................................14 Administrator..........................................................................................................14 Teachers..................................................................................................................14 Student....................................................................................................................14 3 Specific Requirements ...............................................................................................14

1 INTRODUCTION
The project this SRS talks about is a School Management System designed for Spring Dale College in particular but it is the endeavour of the developers to enhance it further to become a Domain Specific Content Management System. Keeping that in mind some of the design and architectural options used by the developers are specifically chosen for future use and development. Following section deals with the overview of the project and gives the reader a birds eye view of the main points in this software. This section may be used to give a brief introduction to possible audience without getting into the detailed parts. It will give you a very good idea about the goals of this development team.

1.1 Document Purpose

Basic purpose of this document is to set goals and boundaries for our software. This document will clearly mention the requirements asked by the user and the enhancements introduced by the developers. This document can be and should be used for design and development. The intended audience of the document are the users and the developers. It is our firm belief that without a proper understanding of the requirements demanded and the requirements delivered it is all but impossible to reach at any contractual obligation and fulfilment. Unless we have concrete benchmarks for measurement, it will be pretty 2|Page

difficult to measure or quantify the completeness and conformance percentage of the product.

1.2 Scope
This software which has been quiet aptly and quiet plainly named as School Management System does exactly what the name says. It has been designed by keeping a particular school in mind but most of the modules have been kept so flexible that it might be easily modified either for some other college or can be enhanced to become a full fledged CMS. This software is designed to automate most of the working of a school. Most of the workings might be a vague term and it encompasses nearly everything. So to be more specific and to the point lets take point by point the modules demanded by the user and some of the modules introduced by the development team. Authentication Authorisation Class Attendance Maintenance Student Record Maintenance Examination Report Generation Library maintenance Time Table Designing Student Profile Teacher Profile 24*7 Online Presence

1.3 Definitions, Acronyms and Abbreviations

SOAP JSON XML HTML HTTP ASPX ASMX Simple Object Access Protocol Javascript Object Notation Extended Markup Language Hypertext Markup Language Hyper Text Transfer Protocol ASP.net Page .net Webservice File 3|Page

CS XSD DLL/DAL BLL UI DLL

C# class file XML Schema Definition Data Logic Layer/Data Access Layer Business Logic Layer User Interface Dynamic Link Library

1.4 References 1.5 Overview

2 Overall Description
2.1 Product Perspective
School Management System or similar products have in vogue for quite some time now therefore it will be erroneous to assume that this product is first in its family. As mentioned earlier the school that I investigated for model and have included the requirements gathered in this document has some form of software already working for them. Firstly the software or softwares working in the school are quite old fashioned and have been written using tools such as DBaseIII and Excel. Thus they are not the most user friendly piece of code nor are they easy to maintain either. Secondly these softwares are independent peaces completely unaware of each other thus they work in isolation. Data migration or sharing becomes a huge problem. Not 4|Page

only that, it is nearly impossible to maintain any sort of control or design any kind of work flow. Every work which is done is quite ad-hoc in nature. The design of my software is such that it can work independently and does not need support of any legacy applications. It brings under one roof all the varied components. This makes data standardisation much easier. The learning curve is cut to halve because operators do not need to learn 3 softwares and get used to the nuisances of each, instead they have one clean standard GUI which can be used to do everything they need from within one application. Data repetition and variance on these legacy applications are a problem. These applications have been designed by three different vendors thus the standards are not the same.

2.1.1 System Interfaces

School Management System is built using .NET framework 4.0. It is a web based application which has been written using the mixture of HTML, Javascript and C#. Database used is SQL Server 2008. This application needs IIS 7.0 and above to function. Every piece of data is stored in the database is kept online for a very specific reason. As mentioned earlier my endeavour is to make it a CMS thus someday this software might need to interface with cloud based Databases therefore the amount of local code related to database should be minimal. To this extent this software strictly follows 3 Layer architecture concept of ASP.NET. In some circles this architecture is also called as Model View Control Architecture. My application has been designed in a way that any changes to database design can be independently achieved without disturbing the business logic layer or the UI layer. This concept may be summarized in the following manner.

5|Page

Three Tier/Layer Architecture Design Components We can separate the three tiers as Data Tier, Business Tier and Presentation Tier.

Data Tier is basically the server which stores all the applications data. Data tier contents Database Tables, XML Files and other means of storing Application Data. Business Tier is mainly working as the bridge between Data Tier and Presentation Tier. All the Data passes through the Business Tier before passing to the presentation Tier. Business Tier is the sum of Business Logic Layer, Data Access Layer and Value Object and other components used to add business logic. Presentation Tier is the tier in which the users interact with an application. Presentation Tier contents Shared UI code, Code Behind and Designers used to represent information to user.

6|Page

2.1.2 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 HTML 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 messages should be highlighted. This software should be made unique by its ability for analysis. Thus each page will gives user the ability to cross reference and a very rich interface will presents the data not in bland table format but in a very modern and easy to understand graphical format.

2.1.3. Hardware interfaces

a. Server Side 7|Page

The web application will be hosted online, with the SQL Server hosted online too. IIS 7 or higher will be used on these hosting servers. There is no restriction on having either shared or dedicated server. The server must support .Net framework 4 or higher. b. Client Side Due to the system being web based, it reduces the system requirement on the clients side to nill. The client is expected to use just a browser; any modern browsers will work perfectly. The client must have a VDU capable of showing web pages with colour. No specific dimension are required. Due to the online nature of the application client must have internet connection for the system to work.

2.1.4. Software interfaces

a. Server Side As mentioned in the previous section this application due to its nature of being webbase requires IIS 7 or higher with .NET 4.0 or higher installed and SQL-Server 2008. Javascript libraries like jQuery may be installed locally or they may be referenced from google public library. b. Client Side An OS is capable of running a modern web browser which supports HTML version 4.0.1 or higher. Cookies and scripting should be enabled.

2.1.5. Communications interfaces

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

2.1.6. Memory
Memory requirement on the client side is minimal as long as it can run an OS it should be enough to run the application.

2.2 Product Functions

This section defines the various functions this software should perform

8|Page

2.2.1 Admit Student Use Case

<<i ude>> ncl

Adm i n

Adm i St t udent

Cr e Li ar M em ber eat br y
<<i ude>> ncl

Cr e W eb U ser eat

Brief Description The Administrator initiates student admission procedure which in turn creates a library membership for the student as well as he/she gets his/her login too.
2.2.2 Library Membership Creation

Adm i n

Cr e Li ar M em ber eat br y

Brief Description The Administrator may create new library members.

2.2.3 Create Web User

Adm i n

Cr e W eb U ser eat

Brief Description The Administrator may create new webuser. 9|Page

2.2.4 Manage Attendance

Teacher

At endance M anagem ent t

Adm i n

Brief Description The Administrator or Teacher can update attendance of any class or student.

2.2.5 Send Warning Mailers

Teacher

send war ng m ai ni l s

Brief Description Based upon any cutoff attendance percentage a teacher or administrator may send warning mails to one or more students.

10 | P a g e

2.2.6 Issue Books

<<i ude>> ncl

Adm i n

Sear chBookO nAut hor

<<i ude>> ncl

Sear chBookO nSubj ect St udent I ssueBook

<<i ude>> ncl

Sear Book O n Til ch te Teacher

<<i ude>> ncl

Sear Book O n I ch SBN

Brief Description Any of the valid library members can issue books, each time they want it the software shall provide them an easy interface to search any book on multiple criteria.

11 | P a g e

2.2.7 Return Book

Adm i n

St udent

R et n Book ur

Teacher

2.2.8 Create Roles

R ol eaton eCr i Adm i n

Brief Description Admin is allowed to create new roles categories for the software.

2.2.9 Time Table Management

<<i ude>> ncl

Adm i n

Ti eTabl M anager m e

Ti e Tabl D esi m e gner

12 | P a g e

Brief Description Admin can create Time Tables, this will be achieved by simple to use drag and drop interface.
2.2.10 Student Exam Management

13 | P a g e

2.3 User characteristics

According to the user requirements the software must have these broad categories or roles. Each roles may have more than one users in it.

Administrator
By far the most powerful and versatile of the Roles, its main aim is to be the power user or if we take the parlance of Linux, this is the root user. Due to the uncertainty in the users mind we have designed this role in such a way that it will have the rights of both the principal and the management, in addition to the web-admin role. During the course of several interviews it was found that the school does not have clearly demarcated duties for Principal, Management and Web-Admin, resulting in overlapping and switching.

Teachers
The next most powerful user is the Teachers they may not have the same level of access yet they can control all the functions of a class and student.

Student
This Role has both the parent and student in it and has the most reduced set of rights yet it is more than enough for the student to be aware of his standing and the parents to be aware of their wards performance.

3 Specific Requirements

14 | P a g e