CHAPTER 7 Software Requirement Specification

CHAPTER 7

7.1 Overview

The software requirement specification (SRS) is very important part of the software building process, which describes the actual user level requirement from technical point of view. i.e. what the user exactly wants ?or for what purpose we are making every thing The objective of preparing the software requirement specification is to represent the requirements of the software in such a manner that ultimately leads to successful software implementation. It is the result of the analysis process of the software development. It should contain all the data the software is going to process, the function it will provide, and the behavior it will exhibit. This Software Requirements Specifications (SRS) is defined in IEEE Std. 830-1993, IEEE Recommended Practice for Software Requirements Specifications. The document is organized in the following structure:

Ø Introduction

Ø Information Description

Ø Functional Description

Ø Behavior Description

Ø Validation Criteria

Ø Bibliography

Ø Appendix

7.1.1 Introduction

The introduction section describes the goals and objective the software under going development in context of computer based system. It mainly deals with the software scope. i.e. it will bind the software application domain.

7.1.2 Information Description

This section of the SRS provides a detailed of the problem that the software must solve. It should describe the core of the software – i.e. The Data. The data or information the software is going to work on is the most basic part of the software. The description of each data or information entity is described here. It also gives details of the relationships between the data elements of the software. The information description helps the software designers in their designing purpose.

7.1.3 Functional Description

This section of the SRS describes the each functions required to solve the problem. It emphasizes on the core of the software on which the data will be processed – i.e. The Function. It also includes the process specification of each function, design constraints, and performance characteristics. The DFD or any other graphical diagram can also be added to describe the functionality of the system.

7.1.4 Behavioral Description

This section of the SRS describes the behavior of the software will exhibit. It is based on definition of the events and the operations that it will perform because of events.

7.1.5 Validation Criteria

This section of the SRS contains the details of the tests that should be performed to validate functions, performance, and behavior of the software. It is one of the most important aspect of the software which decides how much robust our software is.

7.1.6 Bibliography

This section contains references to all the related documents related with the software. This may include any technical document, standards document or software engineering paper.

7.1.7 Appendix

This section is supplementary and can include the matters that are important for the software development. It may include the statistical data, graphs or algorithm details.

7.1.8 SRS Document

Software Requirements Specification Document

Author : NEHA KHAN

7.2.1 Introduction

This is a Software Requirement Specification for “ “TRANS SERVICE NET” While this document will be in reasonable detail, it will be a good base for expansion of detail to be easily updated in the future.

7.2.2 Audience

TRANS SERVICE NET for all is apart of the web site so audiences are the person around the glob who uses the Internet to retrieve information from the site whether they are an independent end user or related to an institute whose data is customized to use with the institution assigned user id and password an updated copy of SRS is always available on the site.

7.2.3 Purpose

The purpose of this Software Requirement Specification document is to define the requirements, which will enable the development of a win application “ with the facility provided by the embedded approach in the software titled TRANS SERVICE NET” using software engineering approach.

7.2.4 Scope

This document will form the basis for validating the final uploading of the site with the facility provided by the education for all. Any changes made to the requirements in future will have to go through a formal change approval process. The developer is responsible for asking for clarifications, where necessary, and will not make any alterations without the permission of the client.

7.2.5 Case Study

“TRANS SERVICE NET

Introduction:

Software Scope of Proposed software: the website get request from audience around the globe and act accordingly with that, login information, login dependent data transaction. Major task of the software is to build a robust flexible sustainable site, which fulfills all the criteria of an Ogr. With the facility of advertising package, match making and much more (the later are not the part of the project).

Information Description:

The most basic element of any software system is the information items that the system accepts, processes, and outputs. This is also called the information domain of the software. Our software consists of various types of entity sets, which are nothing but the set, the attributes (or information). The grouping of information items helps in logical mapping of the software. The following chart describes the different kinds of entities and the attributes that are the intrinsic part of the software.

Product sell and purchase-

This part of the site is still to be developed as a better option to get better items at low cost.

Behavioral Description

In our context, the proposed system should fully automate the education system; automation to improve the work efficiency by using Internet technologies will benefit the masses. As the proposed system is based on internet technologies (client server model) right to maintain the database and functionality which are strictly confidential within the control of administrator master and partially with the client master. Therefore, as per the need this is a unique and a new approach with the centralized database system in the field of online education. And needs more input and better improvement on every upload.

Validation Constraints

As our project is a database dependent for the information extraction and input so for such a project a minute error in the database will be drastic. So validation constraints has very important role here, because putting any wrong value in the database or in any fields on the form can give tremendous error. So, each field on the form level is validated before saving it into the database. We are and have maintained the validation checks using constraints to maintain the referential integrity at database level too.