week 3 summary

Gergő Pintér, PhD

gergo.pinter@uni-corvinus.hu

steps of requirement analysis

based on [1]

functional and non-functional requirements

  • functional requirements define
    what a system is supposed to do
  • non-functional requirements define
    how a system is supposed to operate
    • e.g., legal requirements (GDPR)

minimum viable product

based on Making sense of MVP (Minimum Viable Product) by Henrik Kniberg

what is a user story?

  • a popular tool in requirements analysis, particularly in agile software development methodologies
  • simple description of a software feature
    • from the perspective of the end user or customer
  • and are often accompanied by acceptance criteria (BDD),
    • which define the conditions that must be met to be considered complete

as a [type of user], I want to [action/function] in order to [benefit/value]

behaviour-driven development

  • BDD starts from a user story and
    focuses on adding acceptance criteria
  • extends user stories how the software should react in some with scenarios (conditions)
Title (one line describing the story)

Narrative:
As a [role]
I want [feature]
So that [benefit]

Acceptance Criteria:
(presented as Scenarios)

Scenario 1: Title
Given [context]
  And [some more context]...
When  [event]
Then  [outcome]
  And [another outcome]...

Scenario 2: ...

user story mapping

  • performed in workshops including
    • users,
    • (UI) designers,
    • developers,
    • testers,
    • and stakeholders
  • build a shared understanding of the product and a common language
  • living document

user story mapping mistakes

more from Jeff Patton: 5 story mapping mistakes

references

[1]
A. Krysik, “SDLC guide: Requirement analysis in software engineering.” https://stratoflow.com/requirements-analysis , 24-Nov-2023.