This presentation covers Requirements Documentation for IT Projects

1. www.qbi.in

2. www.qbi.in

3. www.qbi.in

4. www.qbi.in

5. www.qbi.in

6. www.qbi.in

7. www.qbi.in

8. – Company wide same document structure is followed
– Easy to Read
– Easy to do Quality Checks
– Suits your requirements
www.qbi.in

9. – Different Readers the document is aimed at
– Specific Sections of interest to a particular audience
– Document Dependencies
– Technical background if any to suit the requirements
www.qbi.in

10. – Glossaries are integral to Requirement Documents
– You can prepare a common glossary for your domain and
utilize it after making suitable amendments for the project
www.qbi.in

11. – Standard Notations allow you to remain consistent
– Examples: UML 2.0 , BPMN 2.0
www.qbi.in

12. www.qbi.in

13. www.qbi.in

14. www.qbi.in

15. www.qbi.in

16. www.qbi.in

17. www.qbi.in

18. 1. Correct 6. Verifiable
2. Unambiguous 7. Modifiable
3. Complete 8. Traceable
4. Consistent
5. Ranked for
importance
and/or stability
www.qbi.in

19. • Correct: every requirement given in SRS is a
requirement of the software
• Unambiguous: every requirement has exactly one
interpretation
• Complete: includes all functional, performance,
design, external interface requirements;
definition of the response of the software to all
inputs (valid and invalid)
• Consistent: internal consistency
www.qbi.in

20. • Ranked importance: essential vs. desirable
• Verifiable: for each requirement there must be a
“finite cost-effective” method to verify process
with which a person or machine can check that
the software product meets the requirement.”
• Modifiable: SRS must be structured to permit
effective modifications (e.g. don’t be redundant,
keep requirements separate)
• Traceable: origin of each requirement is clear.
www.qbi.in

21. • Introduction
– Purpose
• delineate purpose of SRS
• intended audience for SRS
– Scope
• identify software to be produced by name
• explain what sw will (not) do
• describe application of sw (benefits, objectives)
www.qbi.in

22. • Introduction (continued)
– Definitions/acronyms/abbreviations
– References
• list documents referenced by name and source
– Overview
• brief description of rest of SRS
• organization of SRS
www.qbi.in

23. • Overall description
– Product perspective (related products?)
• block diagram
• constraints
– system interfaces
» identify functionality that fulfills each system
requirement
– user interfaces
– hardware interfaces
– software interfaces
» how sw interacts with supporting software (purpose,
message content and format) www.qbi.in

24. • Overall description (continued)
– Product perspective
• constraints
– communications interfaces
» network protocols
– memory
» requirements/limits on primary and secondary memory
– operations
» modes of operation
» interactive vs. unattended operation
» backup & recovery
– site adaptation requirement
www.qbi.in

25. • Overall description (continued)
– Product functions
• summary of major functions sw will perform
– Intended user characteristics
• educational level
• experience
• technical expertise
www.qbi.in

26. • Overall description (continued)
– Constraints (limitations of developer options)
• regulatory policies
• hardware limitations interfaces to other
applications
• parallel operation
• audit functions
• reliability requirements
• criticality of the application
• safety and security considerations
www.qbi.in

27. • Overall description (continued)
– Assumptions and dependencies
• e.g. specific OS available on HW
– Apportioning of requirements
• requirements that may be delayed to future versions
www.qbi.in

28. • Specific requirements
– External interfaces
– Functions
– Performance requirements
– Logical database requirements
– Design constraints
• Standards compliance
www.qbi.in

29. • Specific requirements (continued)
– Software system attributes
• Reliability
• Availability
• Security
• Maintainability
• Portability
www.qbi.in

30. • Specific requirements (continued)
– Organizing the specific requirements
• System mode
• User class
• Objects
• Feature
• Stimulus
• Response
• Functional hierarchy
– Additional comments
www.qbi.in

31. • Supporting Information
– Table of contents
– Index
– Appendixes
www.qbi.in

32. www.qbi.in