Software Requirement Specification

1- INTRODUCTION:
The following subsections of the SRS document provide an overview of the entire SRS. a) Purpose: Main objective of the existing system is to provide a user-friendly interface. The system, which is proposed, now computerizes all the details that are maintained manually. Once the details are fed into the computer there is no need for various persons to deal with separate sections. Only a single person is enough to maintain all the reports. The security can also be given as per the requirement of the user. Large volumes of data can be stored with case. Maintenance of file is flexible. Records stored are updated now and then. Stored data and procedures can be easily edited. Reports can be generated with case. Accurate calculations are made.
Less manpower required.

b) Scope: The website to conduct online School Administration is E-Class. . Online school administration helps to store and manage school information like students records, Students parents information, teachers and staff profiles, examination schedules, time table, attendance records, students performance record, school events etc available over Internet to everyone and manage the administration online with ease.

2- OVERALL DESCRIPTIONS:

2.1 PRODUCT PERSPECTIVE

Block Diagram of the System is below:

2.2 PRODUCT FUNCTION

In e-CLASS System, the administrator can add/update/delete/view all the information. To explain about the product functions, we use Use Case Diagram.

2.3 USER CHARACTERISTICS

In this system there are two users: Administrator User: He/she have knowledge of System. He/she handle the system process. He/she can give rights to others.

Normal User: Normal user have knowledge of System.. He/she have rights to entry the records.

2.4 GENERAL CONSTRAINTS

Thus software provides a secure system to handle records. The general constraints can include: It is not a large scale system. Only limited information provided by this system.

2.5 ASSUMPTIONS AND DEPENDENCIES

Assumptions: In general it has been assumed that the user has complete knowledge of the system that means user is not a nave user. Any data entered by him/her will be valid. To make the

software as user friendly as possible but at the same time keeping in minds user requirements. Server OS should be Windows XP/VISTA/7. Client PC should be Windows XP/VISTA/7with latest service pack. Dependencies: It depends that the one should follow the international standards for the generating the User ID & should fill the related information in the proper format.

3- SPECIFIC REQUIREMENTS
This section describes in detail all the functional requirements.

3.1 FUNCTIONALITY
3.1.1 Logon Capabilities The system shall provide the users with logon capabilities. 3.1.2 Alerts The system can alert the administrator in case of any problems.

3.2 USABILITY
The system shall allow the users to access the system from the Internet using HTML or its 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.

3.3 RELAIBILITY
The system has to be very reliable due to the importance of data and the damages incorrect or incomplete data can do. 3.3.1 Accuracy The accuracy of the system is limited by the accuracy of the speed at which the uses use the system.

3.3.2 Access Reliability

The system shall provide 100% access reliability.

3.4 PERFORMANCE
3.4.1 Response Time
Response time should be minimum as much as possible.

3.4.2 Administrator Response

The system shall take as less time as possible to provide service to the administrator.

3.4.3 Throughput The number of transactions is directly dependent on the number of users. So throughput should be maximum as much as possible.

3.4.4 Capacity The system is capable of handling requirement users (maxi.500 users) at a time.

3.4.5 Resource Utilization The resources are modified according the user requirements.

3.5 SUPPORTABILITY
The system designers shall take in to considerations the following supportability and technical limitations.

3.5.1 Internet Protocols The system shall be comply with the TCP/IP protocol standards and shall be designed accordingly.

3.5.2 Information Security Requirement The system shall support the e-Class information security requirements.

3.5.3 Result System Data Compatibility The result of marks will be calculated correctly and that should be compatible with the data type system and design. 3.5.4 Maintenance The maintenance of the system shall be done as per the maintenance contract.

3.5.5 Standards The coding standards and naming conventions will be as per the American standards.

3.6 DESIGN CONSTRAINTS 3.6.1 Software Language Used The languages that shall be used for coding the e-CLASS System are C#, HTML, JavaScript, and CSS. For working on the coding phase of the e-CLASS System, the Internet Information Services (IIS) Server needs to be installed.

3.6.2 Development Tools Will make use of the available Microsoft Visual Studio Tool for working with C# languages. Also will make use of the online references available for developing programs in HTML.

3.7 ONLINE HELP SYSTEM REQUIREMENTS

Online help is provided for each of the feature available with the e-CLASS System. All the applications provide an on-line help system to assist the user. The nature of these systems is unique to application development as they combine aspects of programming (hyperlinks, etc) with aspects of technical writing (organization, presentation). Online help is provided for each and every feature provided by the system. The User Manual describes the use of the system to Admin and users.

4- INTERFACES

4.1 User Interfaces For Administrator User:

Admin can give permission for access right Admin can generate report according to the demand.

For the Normal User:

User can view his/her account.

User can insert, update and monitor the whole process . User have access right for inserting marks and attendance.

4.2 Hardware Interfaces

Server Side: Operating System: Windows xp/Vista/7 Processor: Intel Processor 2.0 GHz or above RAM: 512 Mb or more Hard Drive: 10 GB or more

Client side: Operating System: Windows 9x or above, MAC or UNIX. Processor: Pentium III or 2.0 GHz or higher. RAM: 512 MB RAM or more. Space:10 GB Hard Disk Drive or more.

4.3 Software Interfaces

Client Side: Web Browser, Windows XP/Vista/7 Web Server: IIS 7.0 4.4 Communications Interfaces The e-CLASS System will be connected to the World Wide Web. 4.5 Site Adaptation Requirements No site adaptation is necessary in this project. Because the e-CLASS is portable. The entire system is transported to wherever it is needed. No external dependancies are in place and operartion of the system will never change due to location.

5- SYSTEM FEATURES 5.1 DATABASE STORAGE

Description and Priority Proposed Database is intended to store, retrieve, update, and manipulate information related to school which include Profile of users Student details Staff details My account Report

Stimulus / Response Sequences

Responses for Administrator: The administrator can Login and Logout. When the Administrator Logs into the e-CLASS system. The system will check for validity of login .If the Login and password are valid, the response to this action is the administrator will be able to modify, view, add, deleting and all other functions that can be performed on the database. User: First of all the user gets a valid identification number . The user can log on with this identification no. and can use the system. After logging in the user can see various options and can choose the option from the menu.

5 FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS:

1. Login User can access the system after successful login. User can login successfully if and if he/she is an authenticated user and authorized user. User prompted for username and password. User gives username and password. If he/she entered wrong username or password then system allow him/her to re-enter it.

2. Insert This operation is used to insert the data into the different tables. First, Data are filled into the form by any user or administrator. Then the filled data are submitted by verifying by internal queries. If the data are inserted correctly then & then it will be inserted into the database otherwise it will give an error to the user or administrator. Inserted data will be stored into the appropriate table.

3. Update
10

Depending on the database that is selected, the user may wish to modify some details under certain parameter(s) for an existing entity.

4. Delete This operation is used to delete the data from the database which are unwanted or duplicate. In this application, basically delete operation is performed by the admin side.

5. Search This operation is used to search the particular entry from the database. As per delete operation, this operation also needs to give an id of particular entry of the table.

6. Reliability Reliability of the system is very important. As it would be accessed several times in a day by different users across the department, it should be entirely robust and reliable.

7. Usability The system shall allow the users to access the system from the Internet using HTML or its 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. 8. Maintainability: The system should be designed to be easily maintainable and get the least Complaints from users, along with minimum downtime.

11

12