SE311 · Chapter 7 · Annotated SlidesRequirements Specification
Original
Overview

Requirements Specification

What the SRS is and who reads it, labeling requirements (sequence numbers, hierarchical numbering, hierarchical textual tags), handling TBDs, user interfaces in the SRS, readability tips and best practices.

How to read this page

Every original slide is shown unchanged. Yellow marks on a slide point to a numbered note: hover or tap a mark to jump to its note, and hover a note to see its marks. Questions tagged Past exam appeared on a real paper; Prediction questions are likely angles, not confirmed. Pick an answer to each question: a wrong pick tells you why it is wrong, so you can try again.

All 23 slides
  1. 1 Slide 1
  2. 2 RE Process
  3. 3 Requirements Specification
  4. 4 Requirements Specification
  5. 5 SRS
  6. 6 If a desired capability or quality doesn’t appear
  7. 7 SRS Audience
  8. 8 Labeling Requirements
  9. 9 Requirements Labeling Methods – Sequence Number
  10. 10 Requirements Labeling Methods – Sequence Number
  11. 11 Requirements Labeling Methods – Hierarchical Numbering
  12. 12 Requirements Labeling Methods – Hierarchical Numbering
  13. 13 Requirements Labeling Methods – Hierarchical Numbering
  14. 14 Requirements Labeling Methods – Hierarchical Textual Tags
  15. 15 Requirements Labeling Methods – Hierarchical Textual Tags
  16. 16 Requirements Labeling Methods – Hierarchical Textual Tags
  17. 17 TBDs won’t resolve themselves
  18. 18 User Interfaces and the SRS
  19. 19 Screen layouts don’t replace functional requirements
  20. 20 SRS – Readability Tips
  21. 21 SRS – Readability Tips
  22. 22 Requirements Specification Best Practices
  23. 23 Requirement Shell
Slide 1 / 23

Slide 1

Slide 1: Slide 1
Slide 2 / 23

RE Process

Slide 2: RE Process
Slide 3 / 23

Requirements Specification

Slide 3: Requirements Specification
Slide 4 / 23

Requirements Specification

Slide 4: Requirements Specification
Slide 5 / 23

SRS

Slide 5: SRS

Notes

  1. SRS: functional and non-functional requirements the system must satisfy; the basis for design, testing, planning and contracts.

Slide 6 / 23

If a desired capability or quality doesn’t appear

Slide 6: If a desired capability or quality doesn’t appear
Slide 7 / 23

SRS Audience

Slide 7: SRS Audience

Notes

  1. Audience: customers, marketing, project managers, developers, testers, maintainers, documentation writers, legal.

Slide 8 / 23

Labeling Requirements

Slide 8: Labeling Requirements
Slide 9 / 23

Requirements Labeling Methods – Sequence Number

Slide 9: Requirements Labeling Methods – Sequence Number

Notes

  1. Labeling methods: sequence numbers (UR-9), hierarchical numbering (3.2.4.1, breaks when edited), hierarchical textual tags (Print.ConfirmCopies).

Exam angle

PredictionQ1

Which labeling method is most stable when requirements are inserted or deleted?

Slide 10 / 23

Requirements Labeling Methods – Sequence Number

Slide 10: Requirements Labeling Methods – Sequence Number
Slide 11 / 23

Requirements Labeling Methods – Hierarchical Numbering

Slide 11: Requirements Labeling Methods – Hierarchical Numbering
Slide 12 / 23

Requirements Labeling Methods – Hierarchical Numbering

Slide 12: Requirements Labeling Methods – Hierarchical Numbering
Slide 13 / 23

Requirements Labeling Methods – Hierarchical Numbering

Slide 13: Requirements Labeling Methods – Hierarchical Numbering
Slide 14 / 23

Requirements Labeling Methods – Hierarchical Textual Tags

Slide 14: Requirements Labeling Methods – Hierarchical Textual Tags
Slide 15 / 23

Requirements Labeling Methods – Hierarchical Textual Tags

Slide 15: Requirements Labeling Methods – Hierarchical Textual Tags
Slide 16 / 23

Requirements Labeling Methods – Hierarchical Textual Tags

Slide 16: Requirements Labeling Methods – Hierarchical Textual Tags
Slide 17 / 23

TBDs won’t resolve themselves

Slide 17: TBDs won’t resolve themselves

Notes

  1. TBD ("to be determined") marks gaps: give each an owner and a date, and resolve them before building.

Slide 18 / 23

User Interfaces and the SRS

Slide 18: User Interfaces and the SRS
Slide 19 / 23

Screen layouts don’t replace functional requirements

Slide 19: Screen layouts don’t replace functional requirements

Notes

  1. Screen layouts don’t replace functional requirements; keep UI design details out of the SRS (or in an appendix).

Slide 20 / 23

SRS – Readability Tips

Slide 20: SRS – Readability Tips
Slide 21 / 23

SRS – Readability Tips

Slide 21: SRS – Readability Tips
Slide 22 / 23

Requirements Specification Best Practices

Slide 22: Requirements Specification Best Practices

Notes

  1. Best practices: use a template (e.g. IEEE 830 / ISO 29148), label requirements, keep it current, review it.

Slide 23 / 23

Requirement Shell

Slide 23: Requirement Shell