Software Requirement Specification definition Types of requirement Functional Requirement Non-Functional Requirement SRS Document Structure Importance of SRS

2. OVERVIEW
 SoftwareRequirementSpecificationdefinition
 Typesofrequirement
 FunctionalRequirement
 Non-FunctionalRequirement
 SRSDocumentStructure
 ImportanceofSRS

3. SOFTWAREREQUIREMENTSPECIFICATIONDEFINITION(SRS)
 Structured document setting out detailed description of the system services written
as a contract between client and contractor
 Important characteristics-
Characteristics Conditions
Correct If and only if every requirement stated is one that the
software shall meet
Unambiguous If and only if every requirement stated has one
interpretation
Complete If includes all significant requirements full labels and
references to all figures and diagram
Consistent Doesn’t conflict with other requirements
Verifiable Can be tested cost effectively
Traceable Origin of each requirement can be found
Modifiable Structure and style are not changed when
requirements are modified

4. II. TYPESOFREQUIREMENT
Functional
Requirement
Non-Functional
Requirement
User
Requirement
System
Requirement

5. III. FUNCTIONALREQUIREMENT
 Statement that the system should provide
 Statements for how system should react to particular
input
 Statements for how system should behave in particular
situation
 Specifies what product must do in order to satisfy the
basic reason for its existence

6. IV. NON-FUNCTIONALREQUIREMENTS
 Statements that tell how a system should behave
 A constraint upon the system’s behavior
 Includes all requirements not covered by functional requirement
 Places restriction on the product being developed
 Examples include-
o Safety
o Security
o Usability
o reliability
 Includes most important requirements

7. V. SRSDOCUMENTSTRUCTURE
1. Introduction
Purpose
Scope
Definition, acronyms and abbreviations
References
Overview
2. General Description
Product perspective
Product functions
User characteristics
General constraints
Assumptions and dependencies
3. Specific Requirements
Functional Requirement
Non-Functional Requirement
Interface Requirement
4. Appendices
5. Index

8. VI. IMPORTANCEOFSRS
 Formal and official document
 Resolves conflict between user and developer
 Based on SRS, further development of the system takes place

9. CONCLUSION:
SRS- an important part in Software Development Process
→ Requirements analysis for a good quality product…

10. THANK YOU . . .