Jahziah.
العربية

STUDY GUIDE · GKU 4

Requirements analysis and specification study guide (Software Engineering)

A requirement states what a system must do or how well it must do it, in terms a stakeholder can agree to and a tester can check. This guide follows the requirements engineering process: the kinds of requirement and where they come from, analysis with its models, negotiation and prioritisation, elicitation techniques and when each works, writing requirements that are unambiguous and verifiable, user stories with acceptance criteria for agile work, validation with reviews, prototypes and early acceptance-test planning, and finally traceability and the control of change.

Continue in the app

Structured by the official ETEC subject standard for this topic: every listed topic and learning outcome, with formulas, figures and worked examples. The full sections are available to members in the app.

SKU 4.1 · Fundamentals of systems requirements

  1. The requirements engineering process and types of requirements

    The activities of requirements engineering and how they repeat, the levels from business need to system requirement, and the split into functional requirements, non-functional requirements and constraints.

  2. Requirements analysis, negotiation, prioritisation and tools

    What analysis does to raw needs, the attributes every requirement carries, the tools that hold them, and two prioritisation methods: MoSCoW and the cost-value ratio, with a budget check that does not trust a greedy ranking.

  3. Requirements elicitation techniques

    Finding the stakeholders, the main elicitation techniques with what each is good and bad at, the problem of tacit knowledge, and how to combine techniques for a given project.

  4. Writing requirements: quality, templates and the specification document

    What makes a single requirement and a whole specification good, sentence templates that prevent ambiguity, quality-attribute scenarios that make non-functional requirements measurable, and the structure of a software requirements specification.

  5. Iterative and agile requirements: use cases, user stories and acceptance criteria

    Use cases and user stories as two ways of capturing user goals, the INVEST test for a good story, acceptance criteria in Given-When-Then form, and how a backlog refines requirements one iteration at a time.

  6. Requirements validation, prototyping and early test planning

    The checks a requirements set must pass, the techniques that perform them — reviews, prototypes, models and test-case design — and how acceptance tests are planned from the requirements before any code exists.

  7. Traceability and requirements change management

    Forward and backward traceability, the traceability matrix and the coverage it reports, baselines, the change-control process with impact analysis, and the volatility measure that tells a manager how unstable the requirements are.

MORE SOFTWARE ENGINEERING GUIDES

All study guides

Read the full guide beside your practice questions.

Open the app