Professional Documents
Culture Documents
Documenting The Requirements: SRS Lecture 12
Documenting The Requirements: SRS Lecture 12
requirements
SRS lecture 12
Outline
• Users of SRS
• Labeling requirements
• Sequence number
• Hierarchical numbering
• SRS template
Users of SRS
• Training personnel.
• Legal staff.
• Word processor
• Software Tool
How many SRS for a project?
• 1?
• Many?
• Versions?
Labeling requirements
• Number or bullets?
Sequence number
• 3.2
• 3.2.1
• 3.2.1.1
• Incorporating user interface designs in the SRS has both benefits and drawbacks.
• Include user interface in design constraints, if you do not want to implement certain
functionality with specific UI controls and screen.
• If the SRS is specifying an enhancement to an existing
system.
2. Overall description
4. Data requirements
6. Quality attributes
8. Other requirements
9. Appendices
1. Introduction
1.1 Purpose of the requirements document
1.2 Document Conventions
1.3 Scope of the product
1.4 References
18
1. Introduction
Release number
Types of readers
1. Introduction
1.4 references
• List documents
• Hyperlinks
• Uer interfaces style guides
• Contracts
• Title, author, version number, date, source, storage location,or url
2. Overall description
Spell check
3.x.1 Description
4.3 reports
• Characteristics of reports
• Layouts
• Sort sequence
4. Data requirements contd..
6.1 usability
6.2Performance
6.3Security
6.4Safety
6.xOthers
• Legal, regulatory,
• Financial compliance
• Product installation
• Configuration
• Monitoring, logging
Appendix A: Glossary
• Sequence diagrams
• etc
Summary