SE201 · Chapter 5.1 · Annotated SlidesRequirements Engineering
Original
Overview

Requirements Engineering

User vs. system requirements and their readers, stakeholders, functional, non-functional and domain requirements, the requirements engineering process (elicitation, specification, validation), user stories and scenarios, natural-language specification, the requirements document, and management.

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 47 slides
  1. 1 Software Engineering
  2. 2 Topics covered:
  3. 3 The Requirements Process
  4. 4 Requirements engineering
  5. 5 Types of Requirements
  6. 6 User and System Requirements
  7. 7 Readers of different types of requirements specification
  8. 8 System Stakeholders
  9. 9 Example: Stakeholders in the Mentcare system
  10. 10 Slide 10
  11. 11 Functional and Non-Functional Requirements
  12. 12 Functional and Non-Functional Requirements
  13. 13 Functional Requirements
  14. 14 Functional Requirements Example
  15. 15 Non-functional Requirements
  16. 16 Types of Non-functional Requirement
  17. 17 Non-Functional Requirements Example
  18. 18 Slide 18
  19. 19 Requirements Engineering Processes
  20. 20 Requirements elicitation and analysis
  21. 21 Problems of Requirements Elicitation
  22. 22 Requirements elicitation
  23. 23 Process activities
  24. 24 Requirements Elicitation (or discovery)
  25. 25 Requirements elicitation techniques
  26. 26 Slide 26
  27. 27 Agile methods and requirements
  28. 28 Stories and scenarios
  29. 29 A user Story: Photo sharing in the classroom (iLearn)
  30. 30 Scenarios
  31. 31 Scenario: Uploading photos (iLearn)
  32. 32 Uploading photos (iLearn) (2)
  33. 33 h
  34. 34 Ways of writing a system requirements specification
  35. 35 Natural language specification
  36. 36 Guidelines for writing requirements
  37. 37 Problems with natural language
  38. 38 Example requirements for the insulin pump software system
  39. 39 The software requirements document
  40. 40 Slide 40
  41. 41 Requirements validation
  42. 42 Requirements checking
  43. 43 Requirements validation techniques
  44. 44 Requirements reviews
  45. 45 Requirements management
  46. 46 Key points
  47. 47 Key points
Slide 1 / 47

Software Engineering

Slide 1: Software Engineering
Slide 2 / 47

Topics covered:

Slide 2: Topics covered:
Slide 3 / 47

The Requirements Process

Slide 3: The Requirements Process
Slide 4 / 47

Requirements engineering

Slide 4: Requirements engineering
Slide 5 / 47

Types of Requirements

Slide 5: Types of Requirements
Slide 6 / 47

User and System Requirements

Slide 6: User and System Requirements

Notes

  1. User requirements: natural language + diagrams for customers. System requirements: detailed, structured, for developers and contracts.

Slide 7 / 47

Readers of different types of requirements specification

Slide 7: Readers of different types of requirements specification
Slide 8 / 47

System Stakeholders

Slide 8: System Stakeholders
Slide 9 / 47

Example: Stakeholders in the Mentcare system

Slide 9: Example: Stakeholders in the Mentcare system
Slide 10 / 47

Slide 10

Slide 10: Slide 10

Notes

  1. Functional: what the system should DO (services). Non-functional: constraints on HOW (performance, security, usability, reliability). Domain: from the application domain.

  2. Memory trick If it says "the system shall <do something>", it is functional; if it talks about speed, availability, platform, it is non-functional.

Exam angle

PredictionQ1

"The system shall be available 99.9% of the time" is a:

PredictionQ2

"A user shall be able to search the appointment list" is a:

Slide 11 / 47

Functional and Non-Functional Requirements

Slide 11: Functional and Non-Functional Requirements
Slide 12 / 47

Functional and Non-Functional Requirements

Slide 12: Functional and Non-Functional Requirements
Slide 13 / 47

Functional Requirements

Slide 13: Functional Requirements
Slide 14 / 47

Functional Requirements Example

Slide 14: Functional Requirements Example
Slide 15 / 47

Non-functional Requirements

Slide 15: Non-functional Requirements
Slide 16 / 47

Types of Non-functional Requirement

Slide 16: Types of Non-functional Requirement
Slide 17 / 47

Non-Functional Requirements Example

Slide 17: Non-Functional Requirements Example
Slide 18 / 47

Slide 18

Slide 18: Slide 18

Notes

  1. RE process: elicitation and analysis → specification → validation, iterated (spiral).

Slide 19 / 47

Requirements Engineering Processes

Slide 19: Requirements Engineering Processes
Slide 20 / 47

Requirements elicitation and analysis

Slide 20: Requirements elicitation and analysis
Slide 21 / 47

Problems of Requirements Elicitation

Slide 21: Problems of Requirements Elicitation

Notes

  1. Elicitation problems: stakeholders don’t know what they want, use their own terms, conflict, change their minds; politics.

Slide 22 / 47

Requirements elicitation

Slide 22: Requirements elicitation
Slide 23 / 47

Process activities

Slide 23: Process activities
Slide 24 / 47

Requirements Elicitation (or discovery)

Slide 24: Requirements Elicitation (or discovery)
Slide 25 / 47

Requirements elicitation techniques

Slide 25: Requirements elicitation techniques

Notes

  1. Techniques: interviews (closed/open), ethnography (observation), scenarios, use cases, stories.

Slide 26 / 47

Slide 26

Slide 26: Slide 26
Slide 27 / 47

Agile methods and requirements

Slide 27: Agile methods and requirements
Slide 28 / 47

Stories and scenarios

Slide 28: Stories and scenarios

Notes

  1. User story: "As a <role>, I want <goal> so that <benefit>." Scenarios describe a real interaction in more detail.

Slide 29 / 47

A user Story: Photo sharing in the classroom (iLearn)

Slide 29: A user Story: Photo sharing in the classroom (iLearn)
Slide 30 / 47

Scenarios

Slide 30: Scenarios
Slide 31 / 47

Scenario: Uploading photos (iLearn)

Slide 31: Scenario: Uploading photos (iLearn)
Slide 32 / 47

Uploading photos (iLearn) (2)

Slide 32: Uploading photos (iLearn) (2)
Slide 33 / 47

h

Slide 33: h
Slide 34 / 47

Ways of writing a system requirements specification

Slide 34: Ways of writing a system requirements specification
Slide 35 / 47

Natural language specification

Slide 35: Natural language specification
Slide 36 / 47

Guidelines for writing requirements

Slide 36: Guidelines for writing requirements
Slide 37 / 47

Problems with natural language

Slide 37: Problems with natural language
Slide 38 / 47

Example requirements for the insulin pump software system

Slide 38: Example requirements for the insulin pump software system
Slide 39 / 47

The software requirements document

Slide 39: The software requirements document
Slide 40 / 47

Slide 40

Slide 40: Slide 40
Slide 41 / 47

Requirements validation

Slide 41: Requirements validation

Notes

  1. Validation checks: validity, consistency, completeness, realism, verifiability.

Exam angle

PredictionQ1

Checking that requirements do not contradict each other is a check for:

Slide 42 / 47

Requirements checking

Slide 42: Requirements checking
Slide 43 / 47

Requirements validation techniques

Slide 43: Requirements validation techniques
Slide 44 / 47

Requirements reviews

Slide 44: Requirements reviews
Slide 45 / 47

Requirements management

Slide 45: Requirements management
Slide 46 / 47

Key points

Slide 46: Key points
Slide 47 / 47

Key points

Slide 47: Key points