1

1.

Introduction
1.1 Purpose 1.2 Scope 1.3 Definitions, Acronyms and Abbreviations 1.4 References 1.5 Overview

3 3 3 3 4 4 5 5 5 5 6 6 7 7 7 7 8 8 8 8 9 9 10 10 10 10

2. Overall Description 2.1 Product Perspective 2.2 Product Functions 2.3 User Characteristics 2.4 Constraints 2.5 Assumptions and Dependencies
3. Specific Requirements 3.1 External Interface Requirements 3.1.1 User Interfaces

3.1.2

Hardware Interfaces

3.1.3 Software Interfaces 3.1.4 Communication Interfaces 3.2 System Features 3.2.1 Reliability 3.2.2 Availability 3.2.3 Security

3.3 Performance Requirements 3.3.1 3.3.2 Operational Requirements Exception Handling

3.4 Design Constraints

3.4.1 3.4.2

Software Constraints Network Constraints

10 11 11 11 11 11 11

3.5 Software System Attributes 3.5.1 3.5.2 3.5.3 Reliability Availability Security

3.6 Other Requirements

1. Introduction

1.1Purpose:
The purpose of this document is to present a detailed description of BE project management system. It will explain the purpose and features of the system, the interfaces of the system, what the system will do and the constraints under which it must operate. This document is intended for both the jury and the developers of the system.

1.2 Scope:
This system will help the students as well as teachers to automate the process of managing BE projects in the college. The students can submit their documents including their mathematical models, documents, UML diagrams and the code part. The students will be assigned a userid and password by their respected project guide and every student group will have only 1 user id.

1.3 Definitions, acronyms, and abbreviations:

HTML (Hyper Text Markup Language): It is used to create static web pages. JSP (Java Server Pages): It is used to create dynamic web content. J2EE (Java 2 Enterprise Edition): It is a programming platform, belonging to the Java platform, which is used for developing and running distributed java applications. J2ME (Java 2 Micro Edition): is a Java platform designed for embedded systems (mobile devices are one kind of such systems). Target devices range from industrial controls to mobile phones (especially feature phones) and set-top boxes. HTTP (Hyper Text Transfer Protocol): It is a transaction oriented client/ server protocol between a web browser and a web server. XML (Extensible Markup Language): It is a markup language that was designed to transport and store data. MySQL: It is a database server which will be used for data management.

Web 2.0: It is commonly associated with web applications which facilitate interactive information sharing, interoperability, user-centered design and collaboration on the World Wide Web.

1.4 References:
1. http://en.wikipedia.org/wiki/Software_Requirements_Specification 2. http://www.outsourcingsoft.com/srs/srs_20.htm

1.5 Overview:
The SRS will include two sections, namely: OVERALL DESCRIPTION: This section will describe major components of the system, interconnections, and external interfaces. SPECIFIC REQUIREMENTS: This section will describe the functions of actors, their roles in the system and the constraints faced by the system.

2. Overall description

2.1 Product perspective:

The proposed BE project management system is an online portal for teachers as well as students. The system will provide optimal features like submit documents, view marks to the students and assign marks to the teacher. This system is independent and self-contained. The system provides a user interface that is easy to use and simple to understand. No major additional hardware is required. The system will be fully controlled by the teachers i.e. they have the right to suspend any activity whenever they want.

2.2 Product functions:

Provide a better approach to the administrator to manage the inventory. Provide an automated way to manage BE projects in any college. Provide users the authority to view their marks. Provide student groups ability to submit their documents. Provide Teachers with the facility to analyze the performance of every group. Teacher will be able to assign marks. Enable the students to perform their operation from anywhere.

2.3 User characteristics:

Users may register themselves to perform purchasing operations, select different available garments, look upon different materials available in the online shop, etc. These users are the customers of the shop. The users are the teachers as well as the students of a college. Every project group is assigned a unique username and password by their respected project guide. The teachers also have a userid that they can login with.

2.4 Constraints:

Hardware constraints:

A database is required for the storage of data. This database will be at the server side. Also the server machine should be accessible.

Software constraints:

The development of the system will be constrained by the availability of required software such as web servers, database and development tools. The availability of most recent versions of software development tools may prove to be a constraint.

Design Constraints: The system must be designed to allow web usability. That is, the system must be designed in such a way that it will be easy to use by customer as well as the administrator and accessible on most of the common browsers.

2.5 Assumptions and dependencies:

It is assumed that the students are allotted the userid and password by their teachers. It is assumed that every teacher has a unique id that she/he can login with.

3. Specific requirements

3.1 External interface requirements: 3.1.1 User interfaces: Top Menu:

Home Select Student group Teacher

Side Menu for student group

View marks Submit documents

Side Menu for teachers

Group number 1 Group number 2

3.1.2 Hardware interfaces:

There are no specific hardware interfaces for BE project Management system. All hardware interface functionality shall be handled by the operating system.

3.1.3 Software interfaces:

BE project management system works for Windows or Linux operating system. There must be a browser in order to open the website and to do the operations.

3.1.4 Communications interfaces:

BE project management system shall be able to connect to the Internet. The website can only be retrieved and all operations on the website can be done only if it is connected to internet.

3.2 System features: 3.2.1 Authentication: 3.2.1.1 Introduction/Purpose of feature:

The first feature provided by the online BE project management system is login. Same login is provided for the user and the administrator.

3.2.1.2 Stimulus/Response sequence:

The user cannot create his own userid and password. Password and userid can only be allotted by a teacher guide.

3.2.1.3 Associated functional requirements:

3.2.1.3.1 Administrator can add any new registration details i.e. any new student group.

3.2.2 Adding Documents 3.2.2.1 Introduction/Purpose of feature:

The students can add any new documents that will help the teacher analyze his performance. The students can also submit any other additional information.

3.2.2.2 Stimulus/Response sequence:

After the administrator changes the inventory status, all the data related to the inventory must me updated successfully to maintain the consistency. After the students submits the documents the teacher guide should be informed that something has been submitted related to the project.

3.2.2.3 Associated functional requirements:

3.2.2.3.1 Students should also have the right to view his marks.

3.2.3 Analyze progress report. 3.2.3.1 Introduction/Purpose of feature:

The teacher guiding a particular project can view the documents that have been submitted by the project groups. The time of submission is compared with the scheduled date. If it is late late remark is added and accordingly the students are given marks based on their performance.

3.2.3.2 Stimulus/Response sequence:

When the teacher assigns marks, the updated marks are shown on the students page.

3.2.3.3 Associated functional requirements:

3.2.3.3.1 Teacher should be able to suspend or reject any project topic.

3.3 Performance requirements: 3.3.1 Operational Requirements

The system must support multiple users at the same time. On an average 10 users must be supported during normal work conditions and

10

25 users must be supported during the peak hours like the last date of submission. The students can be allotted marks only by their respective project guides. Only the respected project guide should be given authority or access to the students documents. The server must have more than 50GB hard disk for the database storage requirements since it need to save information of many project groups. If the server fails due to any reason data recovery should take place.

3.3.2 Exception Handling:

Upon detection of an error condition, the system shall generate a suitable error message that shall be displayed to the user. Error conditions may occur due to invalid username, username already in use, invalid password. If internet connection is lost the product may terminate prematurely.

3.4 Design constraints: 3.4.1 Software Constraints:

3.4.1.1 The front-end will be designed using HTML, CSS and JavaScript. 3.4.1.2 The back-end will be implemented using SQL Plus. 3.4.1.3 The database connectivity will be implemented using Java.

3.4.2 Network Constraints:

A continuous Internet connection is required for proper functioning of the system.

3.5 Software system attributes:

The software attributes for BE project management system are stated below:-

11

3.5.1 Reliability: The system should be reliable especially during the peak hours.

3.5.2 Availability: The system should be available all the hours of the day.

3.5.2 Security: Since the users information is kept in the database required security must be provided

3.6 Other requirements:

The response time of the system must be high so that user should get a high interactive session with the system. Once any updation takes place on the teachers side or the students side the other side should be notified immediately.