Skip to content
BoKSA

Technical Requirements Analysis

Technical Requirements Analysis

Requirements decide what gets built and how you'll know it succeeded. Business, user, and system requirements are different things, and so are functional and non-functional requirements — mixing them up is one of the most common causes of rework later in a project. Writing requirements as clear, testable statements ("The system shall…"), backed by use cases (actors, main flow, alternative flows) and acceptance criteria, gives you and your stakeholders a shared, checkable definition of "done".

Starting Points

  • SWEBOK Guide — "Software Requirements" chapter (IEEE Computer Society).
  • Wiegers, K. E., & Hokanson, C. (2023). Software Requirements Essentials. Addison-Wesley.

Key Points

  • You identify stakeholders and derive functional and non-functional requirements for a web application.
  • You translate informal stakeholder wishes into clear, structured requirement statements.
  • You describe use cases (actors, main flow) with matching acceptance criteria.
  • You review a set of requirements for ambiguity, missing information, and testability, and propose concrete improvements.
  • You explain how your requirements link to acceptance tests.