ISE · Introduction to Software Engineering

Chapter 05 · Requirement Engineering

10 questions

Open the slides
The answers are not shown on this page. Use the questions to revise, then check yourself with the self-check quiz at the end of the slide deck.

  1. Question 1

    Which of these is a non-functional requirement for ITC Club Hub?

    • A student can cancel a registration.
    • Check-in confirms within 1 second for 95 % of scans.
    • An administrator approves or rejects a club.
    • The system rejects a second registration for the same event.

  2. Question 2

    What mainly distinguishes a user requirement from a system requirement?

    • The user requirement is written in natural language for stakeholders; the system requirement is precise and detailed for developers and testers.
    • User requirements are always non-functional.
    • System requirements are written after the code is finished.
    • User requirements cannot be changed once written.

  3. Question 3

    An organiser forgets to mention that walk-ins are admitted when seats remain. Which technique is most likely to reveal this?

    • A questionnaire sent to all students
    • Reading the SRS template
    • Observing check-in at a real club event
    • A MoSCoW vote in the team

  4. Question 4

    Applied: "As a developer I want a CSV repository class so that data is stored." Which INVEST quality is most clearly missing?

    • Independent
    • Estimable
    • Small
    • Valuable

  5. Question 5

    In a Given/When/Then acceptance criterion, what must the Then step contain?

    • The name of the C++ class that implements the story
    • An observable result that can be checked to pass or fail
    • The story points of the story
    • The role and the benefit of the story

  6. Question 6

    Applied: in the textual use case UC-02, a student who is already registered selects Register again. Where is this handled?

    • Main success scenario, step 5
    • The precondition
    • Alternative flow 3a
    • The postcondition

  7. Question 7

    In an SRS following ISO/IEC/IEEE 29148, where does NFR-01 (check-in within 1 s for 95 % of scans) belong?

    • 1 Introduction · Scope
    • 2 References
    • 3 Specific requirements · Performance
    • 5 Appendices · Glossary

  8. Question 8

    Applied: which requirement is testable as written?

    • The app shall be user-friendly.
    • The system shall respond quickly.
    • The system shall handle many events.
    • 4 of 5 first-time students register for an event in under 60 s without help.

  9. Question 9

    Applied: a backlog has 60 story points of Must, Should and Could stories; the Must stories add up to 45 points. What do you conclude?

    • Must share 25 %, well balanced
    • Must share 45 %, within the guideline
    • Must share 75 %, above the 60 % guideline: renegotiate some Musts
    • Must share 60 %, exactly at the guideline

  10. Question 10

    A change request moves the cancellation deadline from 24 h to 48 h. What does the traceability matrix give you?

    • The stories, design elements and tests linked to FR-06 that must be updated
    • The number of story points the team completed last sprint
    • The list of stakeholders to interview next
    • Nothing: matrices are only used for audits