--%>
Assignment Help - homework help

  Contents of SRS

Contents of SRS

A SRS template should be selected or defined at the start of the requirements so that the contents of the documents evolve and build up as the requirements elicitation and analysis activates progress. This document must be clear and concise. For this   it is essential to  organize documents as sections  and subsections; so that each SRS will follow a certain format  which  will be  easier to understand and use additionally  they  are also  required so that the analyst does  not forget any property.

Most organizations usually have a template with some tailoring guidelines, which allow every project to modify and use the template. A many organizations and projects have used the IEEE 8301993 standard; IEEE standard suggests the followings structure for requirements documents as shown if table 3.2.

Section 1. Introduction

The introduction section sets the tone of the document it contains the purpose of the documents scope of the document and an overview of the requirement. It also contains the references cited in the document and any definitions that are used.

Section 2. General Description

This general description section describes the general information regarding the factors that affect the product and its requirements. In this section, the specific requirements are not mentioned, but a general overview is presented to make the understanding of the specific requirements easier.

Product perspective describes the connection between the various products. It defines whether the product is independent in itself or a component of a large product and which interfaces it requires. A general abstract description of the products function is provided.  Diagram can also be used to show the various functions and their relationship. Additionally, the characteristics of the user general constraints imposed on software product and any assumptions made in the SRS or implicit dependences are also specified.

Section 3. Specific Requirements

Specific requirements section describes all the details that the software developer needs to know for designing and developing the system. This is the most important, largest and substantial part of the document. This section includes the functional external interface and performance requirements to describe system functionality and performance. It also includes the design constraints and system attributes. This section includes four separate table of contents referred in the IEEE software engineering standards as specific requirements. They are given below one by one. 

In the functional requirement section the function capabilities of the system are described. First the purpose of each functional requirement is described, and then the required inputs processing requirements and desired output will have to be specified. For   the inputs the source of the input their format units of measure, valid ranges etc. Are specified. To specify the processing, all operations that need to be performed on the input data, unambiguous and precise language to write the process and any intermediate data produced should be specified. No algorithms are generally specified in it only the relationship between the inputs and   the output is specified. For outputs the destination of outputs, their format, range of valid inputs, error messages and exception messages etc.  Have to be specified.

The  External interface  Requirements Section :  specifies all the  interfaces  of the  software  people  other  software hardware and other  systems. User interface are specified for user friendliness, human computer interaction, its screen formats, contents of menus and command structure. Hardware interfaces are used to describe all characteristics required to interface the software product and hardware. In software interfaces, all other software with, their interfaces are specified to run this software. And the communication interfaces are described if the software communicates with other entities in other machines.

Performance Requirements Section should specify both static and dynamic performance requirements. State requirements are like the number of terminals to be supported, the number of simultaneous users to be supported, the number of files that the system has to process and their sizes etc. Whereas dynamic requirements involve the number of transactions that must be processed per unit time. What is the response time of a particular command etc?

The design constraints section specifies all the constraints imposed on design. It includes environmental hardware limitations, security fault tolerance etc. The attributes section specifies some of the overall attributes that a system should have.

Latest technology based Software Engineering Online Tutoring Assistance

Tutors, at the www.tutorsglobe.com, take pledge to provide full satisfaction and assurance in Contents of SRS homework help via online tutoring. Students are getting 100% satisfaction by online tutors across the globe. Here you can get homework help for Contents of SRS, project ideas and tutorials. We provide email based Contents of SRS homework help. You can join us to ask queries 24x7 with live, experienced and qualified online tutors specialized in Contents of SRS. Through Online Tutoring, you would be able to complete your homework or assignments at your home. Tutors at the TutorsGlobe are committed to provide the best quality online tutoring assistance for Software Engineering homework help and assignment help services. They use their experience, as they have solved thousands of the software engineering assignments, which may help you to solve your complex issues of Contents of SRS. TutorsGlobe assure for the best quality compliance to your homework. Compromise with quality is not in our dictionary. If we feel that we are not able to provide the homework help as per the deadline or given instruction by the student, we refund the money of the student without any delay.