Software requirement specification

After analysis of requirement, analyst starts to systematically organize the requirement in the form of SRS document. SRS document is toughest of all. It is the contract between the development team and the customer. The SRS document can even be used as a legal document to settle disputes between the customers and developers. Many software engineers consider SRS document as a reference document. If customer agrees with the SRS, development team proceeds to develop the product ensuring that it confirms to all the requirements mentioned in the SRS document.

Users of SRS
Software developers Test engineers User documentation writers Project managers Maintainance engineers

Characteristics of good SRS

Concise Structured Black box view Traceable Response to undesired events verifiable

Categories of SRS document

Functional requirement discuss the functionalities required by the users from the system Nonfunctional requirement - it deals with the characteristics of a system that can not be expressed as functions - non negotiable obligation -includes external interface requirement,performance requirement,constrains,software system attributes Goals of implementation offers some general suggestions regarding developement

Functional requirements
In order to document the functional requirement, it is necessary to first learn to identify the high level functions of the system. High level functions would be split into smaller subrequirement. Each high level requirement typically involves accepting some data from the user,transforming it to the required response and then outputting the system response to the user.

 High level functions usually involves a series of interactions between the system and one or more users. For same high level function, there can be different interaction sequences or scenarios due to users selecting different options. Thus, each high level requirement might consists of several sub requirement.

How to identify the functional requirement

Find out different types of users of the system Identify the different services expected from the software by different types of users. Find out high level functional requirement. Find out input, processing required on input and output of high level function and also for subfunction. Identify scenarios

How to document functional requirement

Write R.1,R.2 likewise for high level functions Then write discription of that function Then write subfunctions in the form of R.1.1,R.1.2 etc Then write state,input,output and processing for each subfunction