Requirements Engineering with IREB Foundation

Learn the fundamental terminology of requirements engineering, including needs, capabilities, and documented representations, and understand how stakeholders and systems define and manage requirements.

Differentiate functional requirements, quality requirements, and constraints, and explain how each addresses concerns about results, quality, or space. Explore various perspectives on requirements, including business, stakeholder, user, and system requirements.

Adequate requirements engineering adds value by reducing risk and costly changes, enabling early detection of wrong or missing requirements, and providing a basis for effort estimates and testing.

Identify how inadequate requirements engineering causes missing, unclear, or wrong requirements, and explore causes such as schedule pressure, communication gaps among stakeholders, assumed self-evidence, and skill deficits.

Explore how requirements apply to socio technical and cyber physical systems, distinguishing domain requirements, business requirements, stakeholder requirements, user requirements, and system requirements from software requirements by perspective.

Explore the four major requirements engineering tasks—elicitation, documentation, validation, and management—and how tool support aids these core tasks, with elicitation covering analysis, conflict resolution, and tailored processes.

Assume the role of a requirements engineer, eliciting, documenting, validating and managing requirements while bridging the gap between problems and potential solutions in professional work and private life.

Develop requirements engineering skills, blending technical, analytical, and soft skills like listening, moderating, negotiating, and mediating, empathy for stakeholders, and master principles, documenting, elaborating, and engineering processes with tool support.

Explore nine principles of requirements engineering to guide tasks, activities, and practices, highlighting value orientation, stakeholders, shared understanding, context, problem requirement, solution validation, evolution, and disciplined work.

Explore the nine fundamental principles of requirements engineering, including value orientation, stakeholders, shared understanding, context, the intertwined problem-requirement-solution triple, validation, evolution, innovation, and disciplined work.

Explore value-oriented requirements engineering, balancing benefits minus costs to justify elicitation and validation while aligning stakeholder needs through shared understanding and disciplined practices.

Explore typical requirements engineering work products, from user stories to system requirement specifications. Understand representation, storage, and lifespan of work products, with examples like use cases, prototypes, and story maps.

Explore the lifespan of work products, from creation to disposal, and distinguish temporary, evolving, and durable types with metadata, change control, baselining, and release.

Explore how requirements align with abstraction levels from business to system, and how to choose the right level of detail, balancing risk, context, and stakeholder feedback.

Explore how requirements engineering work products cover functional, quality, and constraint requirements within context. Examine structured data, function and flow, and state and behavior, plus domain and external interfaces.

Follow guidelines for creating requirements work products by selecting a fitting work product type, using aligned notation, avoiding redundancy and inconsistencies, applying glossary terms consistently, and structuring with standard structures.

Define work products for each initiative with stakeholders and managers, deciding what requirements are recorded, at which abstraction levels, and how they are represented to enable early planning and maintainability.

Explore expressing requirements with natural language templates and models, noting its expressiveness and readability for almost any conceivable requirements, alongside limitations in precision and rapid ambiguity detection.

learn to write natural language requirements clearly by following proven rules, using a single sentence per requirement, and building well-structured documents with a glossary and hierarchical sections.

Use templates to create well-structured, readable work products in natural language. Learn about phrase, form, and document templates, including customer-specific types, and avoid mechanical use and omissions.

Explore the phrase template for writing user stories, including as a role, I want, the benefit and acceptance criteria, to clarify requirements for stakeholders and prevent misunderstandings.

Apply Alistair Cockburn's form template for use cases. Define an actor's action and the system's response; pair templates with use case diagrams and write requirements in natural language.

Explore how a requirements model provides a conceptual, visual representation of system needs, decomposes complexity, and uses UML diagrams with syntax and semantics to specify, paraphrase, and validate requirements.

Evaluate model-based work products, especially graphical models, for describing system requirements, which reduce cognitive load and ambiguities via restricted syntax, while addressing consistency, stakeholder readability, and cross-model integration.

Select and apply the most suitable models for requirements engineering by modeling the system context and goals early, then analyze functions, processes, data, and behavior.

Learn to model system boundaries and interactions with context models, use case diagrams, class diagrams, activity diagrams, and state diagrams, illustrated by a book ordering system.

Demonstrate building a simple system data model with a Unified Modeling Language class diagram on paper, using the book ordering system class diagram as shown.

Learn to specify a simple system or business process with a UML activity diagram, using a book ordering example, and prepare for the foundation level examination questions about the diagram.

Glossaries establish shared terminology by defining terms, abbreviations, acronyms, and synonyms; mark homonyms, enforce consistency, central governance, stakeholder involvement, mandatory use, and enterprise-level standardization in requirements engineering.

Specification documents create a consistent, maintainable collection of requirements, include a glossary and acceptance criteria, and may align with structures or agile artifacts like product backlog or story map.

Recognize there is no universal requirements structure; tailor it to development process, project type, domain, contract, and document size, using templates to create a consistent, maintainable collection of requirements.

Explore exploratory prototypes for requirements elicitation and validation, using wireframes, mockups, and paper prototypes, and understand evolutionary prototypes that evolve a pilot system through iterations.

Explore quality criteria for requirements in the IREB foundation framework, including verifiable, unambiguous, understandable, adequate, and necessary criteria, and how complete scope and value tie to adequacy and understandability.

Apply the six criteria for work products when handling multiple requirements: ensure consistencies, non-redundant documentation, completeness, modifiable work products, traceable origins, and conformant formatting.

Identify requirements sources and analyze their relevance to the system, guiding iterative elicitation. Repeat search in a recursive process until you deliver a single, consistent, agreed set of understandable requirements.

Identify the three major sources in requirements engineering—stakeholders, documents, and other systems—to ensure complete requirements and a full understanding.

Identify and maintain close relationships with stakeholders to clarify rights, obligations, and needs for the proposed system. Use stakeholder agreements and additional sources to elicit subconscious requirements and ensure clarity.

Maintain a close relationship with stakeholders to clarify rights, obligations, and needs, and use a stakeholder contract to ensure clear expectations, while exploring additional sources and eliciting subconscious requirements.

Explore the Kano model to classify requirements into dividers, satisfiers, and dissatisfiers, emphasizing differentiating features from expressed needs through a customer-centered perspective.

Categorize elicitation techniques into gathering and design approaches; use questioning, collaboration, observation, and artifact methods with brainstorming, prototyping, and storyboards to generate requirements and balance Kano satisfiers with implicit quality.

Select elicitation techniques by weighing quality requirements and constraints with functional requirements, using ISO 25,010 models, and consider technical, legal, organizational, cultural, environmental solution-space restrictions to tailor and combine methods.

Identify and resolve conflicts between requirements and stakeholders during elicitation, using techniques for subject matter, data, interest, value, relationship, and structural conflicts to keep development on track.

Resolve a requirements conflict with a four-step process: identify the conflict, analyze its nature and stakeholders, select and obtain acceptance of a resolution technique, and document the outcome.

Learn to select conflict resolution techniques for requirements, including agreement, compromise, voting, and overruling, and apply decision matrices and variants to evaluate criteria like cost and risk.

Validate coverage of stakeholders’ needs by your documentation and agreement among all stakeholders upfront to ensure requirements quality, then continuously monitor defects to detect root causes in the requirements.

Engage the right stakeholders with appropriate independence to uncover defects, separate defect identification from correction, and validate from multiple views in an interdisciplinary team for repeated validation.

Select validation techniques from static reviews, exploratory dynamics, and sample development, including walkthroughs, inspections, prototyping, and alpha/beta testing, guided by lifecycle maturity, risk, and regulatory needs.

Configure a tailored requirements engineering process using process facets to fit the given situation, enabling iterative, change-friendly handling of time, budget, stakeholders, and system complexity.

Configure a tailored requirements engineering process to fit the development and system context. Elicit, document, validate, and manage requirements within that customized framework.

Explore how to configure a requirements engineering process using three facets—time, purpose, and target—covering linear and iterative time approaches, prescriptive and explorative purposes, and customer- or market-oriented targets.

Explore three configurations of requirements engineering processes—participatory, contractual, and product oriented—and learn when to apply iterative, exploratory, prescriptive, or market-oriented facets in agile, waterfall, and product development contexts.

Define a tailored requirements engineering process using a five-step procedure. Analyze factors, apply facet criteria, select a configuration, define requirements, and choose practices to fit the project and mitigate risk.

Explore participatory, contractual, and product-oriented requirements engineering process configurations across insurance, car manufacturing, and media sectors, with evidence-based guidance on selecting the optimal configuration.

Discover how requirements management identifies, documents, and traces requirements across the system life cycle. See how it operates at the individual requirements, work products, and system levels to enable traceability.

Explore how requirements and their work products evolve through creation, validation, implementation, change, and retirement, with overlapping life cycles and role-driven views.

Track all work products through their evolution with version control, restore earlier versions, and enforce three measures: version identification with numbers and dates, linked change descriptions, and strict version storage.

Define configurations as unchangeable, uniquely identified work products containing requirements, with a single version and date, then establish baselines as stable milestones for go-live or end of the design phase.

Learn how to manage requirements by collecting metadata and defining attributes that reveal planned releases, effort estimates, and priority, tailored to stakeholders' information needs throughout the lifecycle.

Select key requirement attributes at project start, guided by ISO standards for identification, source, priority, rationale, risk, and dependency; store and report this data in documents, spreadsheets, or tools.

Use views to tailor reports for target audiences by filtering and sorting data on work products, delivering relevant information and using selective and projected views with summaries, totals, or averages.

Trace requirements back to origin and forward to downstream work products for verification and impact analysis, with backward traceability (pre requirements specification) crucial in safety critical domains.

Explore implicit traceability through document structures, templates, and naming conventions, and establish explicit traceability by linking work products with unique identifiers to other requirements.

Explore explicit traceability through wiki hyperlinks, a trace graph, and a traceability matrix linking requirements to sources like observations or interviews. Large projects require robust requirements management tooling for versioning.

changes in requirements arise from system context, stakeholder insights, and competitors, presenting risk and opportunity; handle them through decision making, planning, and controlled implementation across linear or iterative processes.

Assess and prioritize requirements using criteria such as business value, urgency, effort, and dependencies to determine which items to implement next and test first.

Define goals and constraints to guide criteria such as business value, urgency, effort, risks, dependencies, and stakeholder preferences. Identify stakeholders, choose a prioritization technique, and apply criteria to selected requirements.

prioritize requirements by applying ad hoc techniques like Moscow and top ten ranking, or analytical methods that weight criteria such as benefit, cost, risk, and time to implement for stakeholders.

Explore tool types for requirements engineering, including management, modeling, testing, documentation, and collaboration tools, and learn how they support life cycle management, version control configurations, tracing, and change management.

Define objectives, context, and requirements before selecting a requirements engineering tool, ensure it supports required artifacts, integrate with the tool chain, and evaluate life-cycle costs via pilots.

Move from theory to practice by preparing for the IREB CPR Foundation exam, focusing on core definitions, exam structure, question types, and test-taking tips through the requirements engineering glossary.

Master exam scoring rules for the IREB foundation level, practice with realistic questions, simulate timed conditions, and apply key terms and negation-aware strategies to maximize scores.

Explore the IREB foundation level practice test for requirements engineering, a 45-question exam lasting 75 minutes that mirrors the real test and includes explanations referencing the CPRE foundation level handbook.