Jahziah.
العربية

STUDY GUIDE · GKU 7

System paradigms: requirements, modelling and acceptance study guide (Information Technology)

A system is only as good as the agreement about what it should do. This unit covers that agreement from first conversation to signed acceptance: how requirements are elicited, analysed, specified and validated; how models (use cases, class diagrams, data-flow and sequence diagrams) make the agreement precise; how functional requirements differ from non-functional ones and why an unmeasurable quality is not a requirement; how to write and analyse use cases with their main flow, alternatives and relationships; the testing standards that set levels, entry and exit criteria; and user acceptance testing, where the customer decides against pre-agreed criteria.

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 7.1 · Requirements engineering

  1. Fundamentals of requirements engineering

    Eliciting, analysing, specifying, validating and managing requirements; who the stakeholders are; what makes a requirement good (clear, complete, consistent, verifiable, traceable); and how the requirements document is used through the project.

  2. Modelling techniques

    What each model is for: use-case, class, data-flow, sequence, state and activity diagrams; which question each answers; how multiplicity and relationships are read; and why one model never shows everything.

  3. Functional and non-functional requirements

    Telling what the system does from how well it must do it: functional requirements, quality attributes (performance, availability, security, usability, maintainability), constraints, and how to make a non-functional requirement measurable and testable.

  4. Creating and analysing use cases

    Actors, goals, the system boundary, the main success scenario, alternative and exception flows, pre- and postconditions, and the include, extend and generalisation relationships, with traceability from a use case to the functional requirements it realizes.

SKU 7.2 · Testing and quality assurance

  1. System testing standards

    The test levels (unit, integration, system, acceptance), the V-model that pairs each with a specification, ISO/IEC/IEEE 29119's process and its entry/exit criteria, independent testing, and how a test plan makes coverage and stopping rules explicit.

  2. User acceptance testing

    UAT as the customer's decision against pre-agreed criteria: participants and business scenarios, environment and data, execution and defect triage, the acceptance types (contract, regulatory, operational, alpha/beta), and how a pass rate is judged.

MORE INFORMATION TECHNOLOGY GUIDES

All study guides

Read the full guide beside your practice questions.

Open the app