Software Requirements Specification

Requirement Engineering Process

Software Requirements Specification(SRS):

The s/w requirement and specification focuses on what the system will do, not how the system will be implemented. It is produced as the culmination of the s/w requirements analysis task in the lifecycle model. You must analyze the information domain, the function, performance and behavior and interface requirement of the system. Software requirements can be specified in the following ways.

representation format and content should be relevant to the problem
information contain within the specification should be nested.
Representations should be revisable.

s/w requirements specification produced at the culmination of the analysis task. This also states the goal and objectives of the s/w.

information description provides a detailed description of the problem that the s/w must solve.

Functional description is a description of each function required to the solve the problem.

Behavioral description section of the specification examines the operation of the s/w as a consequence of external events and internally generated control characteristics.

Validation criteria is the most important and ironically the most often neglected section of requirements specification.

Functional vs. non functional requirements

functional requirements: statements of services the systems should provide, how the system should react to particular inputs and how the systems should behave in particular situations.

Non functional requirements: constraints on the services or functions offered by the system such as timing constraints, constrains on the development process, standards etc.,

2.1.1Requirement engineering process:

Requirement engineering provides the appropriate mechanism for understanding what the customer wants, analyzing need accessing feasibility, negotiating a reasonable solution, specifying the solution unambiguously, validating the specification and managing the requirements as they are transformed into an operational system. The requirement engineering process can be described in five distinct steps.

requirement elicitation
requirement analysis and negotiation
requirement specification
system modeling

requirement validation
requirement management

Source: http://www.snscourseware.org/snsct/files/CW_5952206c764dd/Req%20engineering.doc

Web site to visit: http://www.snscourseware.org/

Author of the text: indicated on the source document of the above text

If you are the author of the text above and you not agree to share your knowledge for teaching, research, scholarship (for fair use as indicated in the United States copyrigh low) please send us an e-mail and we will remove your text quickly. Fair use is a limitation and exception to the exclusive right granted by copyright law to the author of a creative work. In United States copyright law, fair use is a doctrine that permits limited use of copyrighted material without acquiring permission from the rights holders. Examples of fair use include commentary, search engines, criticism, news reporting, research, teaching, library archiving and scholarship. It provides for the legal, unlicensed citation or incorporation of copyrighted material in another author's work under a four-factor balancing test. (source: http://en.wikipedia.org/wiki/Fair_use)

The information of medicine and health contained in the site are of a general nature and purpose which is purely informative and for this reason may not replace in any case, the council of a doctor or a qualified entity legally to the profession.

Software Requirements Specification

The texts are the property of their respective authors and we thank them for giving us the opportunity to share for free to students, teachers and users of the Web their texts will used only for illustrative educational and scientific purposes only.

All the information in our site are given for nonprofit educational purposes