↓ Ir para o conteúdo principal

← todas as notas

📎 Webclip

The Hardest thing about Engineering is Requirements

The post argues that the hardest part of engineering is not building the system but communicating what should be built. Requirements fail when they do not match stakeholder needs or the market, and the author treats this as a communication problem across technical disciplines and jargon-heavy domains.

Reading notes
#

  • Gathering requirements is presented as one of the hardest parts of being a software architect.
  • The root problem is framed as communication, since engineers have to express abstract ideas across different disciplines and domain languages.
  • “The product shall” lists are easy to add but can encourage feature creep and conflicting requirements.
  • User stories improve on shalls by forcing a discussion of who wants the feature and why, but they work best when stakeholders stay close to the development team.
  • User stories are too vague to serve as a solid agreement, since one sentence can be interpreted in several ways.
  • Use cases add step-by-step detail and error paths, which helps development teams, but stakeholders often find them tedious and hard to review.
  • The author proposes “user cases” as a mix of user stories and use cases, with the story as the title and the use cases as the detailed expansion.
  • This approach aims to keep stakeholders engaged while giving developers enough detail to reduce disputes over interpretation.
  • Rapid prototyping is presented as another promising way to capture requirements because it helps stakeholders feel how the product will work.
  • The author suggests prototyping may soon take less time than fully documenting requirements.