Requirements Engineering (IREB / ISO/IEC/IEEE 29148)

Explore the requirements engineering process, from defining a need and decomposing goals to assessing constraints, measures of effectiveness, verification and validation, and life cycle concepts.

Identify stakeholders' needs and goals to define market gaps and capabilities, then decompose into missions, phases, scenarios, and use cases that drive requirements and specifications while avoiding premature solutions.

Identify and draft the mission need statement (mns) to define the current problem, its impact on stakeholders and their missions, and the desired solution, guiding top-down requirements and goal generation.

Identify and manage project constraints, including technical, resource, regulatory, and market limits, using interviews, swot, pestle, and trade studies to guide requirements decisions and trade-offs.

Learn how the requirements engineering process translates needs and goals into a mission domain of scenarios, use cases, and user stories, bridging stakeholders and engineers through elicitation and detailed requirements.

Describe how scenarios capture mission contexts and stakeholder needs as a structured bridge from goals to requirements, outlining environments, actors, preconditions, and potential failure points, without dictating solutions.

Explore the types of scenarios, including sunny day and rainy day missions, abstract and detailed scopes, and use cases, to shape robust, testable system requirements.

Explore the elements of scenario content, including actors, rules, goals, resources, preconditions, postconditions, operational environment, main scenario, alternatives, and exceptions, showing how requirements derive from these factors in drone missions.

Explore the three common scenario formats: narration, numbered lists, and tables. Narration supports stakeholders, while tables and numbered lists structure steps with inputs and outputs across academia and industry.

Explore template-based scenario elicitation, linking goals, actors, and requirements through unique identifiers, versions, and conditions, with steps and references to derived functions, in a table-driven life-cycle approach.

Apply ten rules of thumb for scenario creation, transforming narratives into numbered steps and ensuring present tense, active voice, subject-verb-object format, third-person perspective, explicit actors, and sunny-day mission focus.

Explore the agile method, sprints, and backlog, and learn how user stories guide requirements and prioritization. Apply the six invest rules—independent, negotiable, valuable, estimable, small, and testable—to craft deliverable features.

Learn how use case analysis refines system requirements by detailing actors, goals, preconditions, guarantees, triggers, and the main course of events, with extensions and alternative paths.

Master requirements elicitation by identifying diverse sources and applying techniques like questioning, collaboration, observation, and research to uncover stakeholder needs for the system.

Review how to translate the problem space into a need, mission, and goals, decompose into scenarios and use cases, identify stakeholders, sources, and artifacts, and establish acceptance criteria.

Learn to elicit requirements through interviews, using open or closed questions with individuals or groups. Prepare goals, select stakeholders, avoid bias, capture responses, and analyze feedback to shape product requirements.

Discover how workshops provide a structured, collaborative elicitation method for capturing requirements, guided by a neutral moderator and clear goals, with documented decisions and artifacts like context diagrams.

Learn how questionnaires serve as a scalable elicitation technique to gather targeted stakeholder input for requirements, including design, formats, benefits, limitations, and analysis for improving existing products.

Master document analysis as a cost-effective elicitation technique in requirements engineering, extracting data from specifications, manuals, policies, and standards to define robust requirements across life cycle contexts.

Observe how users interact with systems to elicit requirements, using controlled or uncontrolled observation setups, mitigate Hawthorne effect with consent and transparency, and use recording methods to produce actionable requirements.

Explore how working groups elicit requirements from diverse stakeholders, covering planning, roles, rules of conduct, and artifact creation, with model-based systems engineering for complex projects like a Mars research facility.

Harness brainstorming during requirements elicitation to generate ideas and foster collaborative stakeholder input. Combine brainstorming with cx method and mind mapping to identify needs and prioritize requirements.

Apply the Cage method, an affinity diagram approach using sticky notes or cards to organize unstructured ideas collaboratively, iteratively group and label categories, prioritize requirements, and document outcomes.

Visualize mind maps that organize requirements elicitation by showing a central idea with branching concepts, helping stakeholders identify gaps, redundancies, dependencies, and collaborate on planning and decision making.

Explore prototyping as a tool for eliciting requirements by creating tangible models to test usability and functionality, align with stakeholders' feedback, and reduce later rework.

Learn to write clear requirements that define the product’s functions, behavior, and design, fostering shared understanding, reducing rework, and ensuring compliance with standards and regulations.

Explore the requirements engineering process, including needs definition, constraints, requirements derivation and writing, and the role of life cycle concepts, Mose, and use cases.

Master how to write clear, verifiable requirement statements using a subject-verb-object structure, positive priority, and glossary terms, illustrated with an ATM example, covering feasibility, measurability, and traceability.

Derive, decompose, and flow down requirements to turn high-level needs into verifiable, traceable components for the tree seed drone and align with stakeholders.

Use measures of effectiveness in requirements engineering to evaluate how well a system meets stakeholder goals, and decompose Moz into lower level measures of performance (mops) to guide improvements.

Differentiate functional, performance, quality, constraint, and interface requirements and derive performance-based, thresholded targets for a tree seed drone, with verification, validation, and regulatory considerations.

Define software requirements as functional and non-functional characteristics that a system must possess to meet stakeholder needs. Highlight how they differ from hardware and guide design, testing, and maintenance.

Explore the structured software development process, from requirements gathering and analysis to design, implementation, testing, deployment, and maintenance, with project management, requirements management, quality assurance, and configuration management.

Identify software requirements through interviews, surveys, workshops, observation, and prototyping, and apply best practices for stakeholder involvement, traceability, and user-centered design.

Analyze software requirements by applying traceability, functional decomposition, prototyping, use-case analysis, and peer reviews to ensure complete, correct, and testable requirements.

Validate software requirements through peer reviews, tracing, and testing to ensure accuracy, completeness, and stakeholder alignment, using automation, traceability, and regression testing.

Master software requirements management by capturing, documenting, validating, and prioritizing stakeholder needs, while tracking changes, maintaining traceability, and applying collaborative reviews and agile practices.

Prioritize requirements by defining evaluation criteria, engaging stakeholders, and applying scoring or pairwise comparison to allocate resources and focus on high-impact needs.

Track TPMs over time against design specifications with thresholds, objectives, and CTPS to ensure requirements are met and decisions guided through top-down, bottom-up, and historical data analysis.

Learn how requirements verification ensures each component, subsystem, and the full system meet specs through analysis, inspection, demonstration, and testing, with traceability and validation planning.

Evaluate and validate the system to ensure it meets stakeholder requirements, performs in its intended environment, and passes go/no go criteria for deployment.

Translate stakeholder goals and capabilities into formal requirements and specifications to guide design. Examine stakeholder and system requirements specifications, templates, formats, and model-based architectures to consolidate documentation and support baselining.

Identify stakeholder and system requirements specifications, link business case and ROI to lifecycle outcomes, and translate stakeholder needs into verifiable, solution-agnostic system requirements for design and validation.

Adhere to standards and guidelines to craft complete, consistent, and flexible specifications. Replace placeholders with actual numbers and cover rainy day scenarios to ensure clarity and modularity.

Learn to use mil standard 961 echo and IEEE 1223/830 templates to capture specifications, organize sections, and apply metadata for automated requirements management.

Modeling supports requirements engineering by creating visual representations, such as diagrams, use case diagrams, and sequence diagrams, to spot issues early. Refine requirements, identify gaps, and validate stakeholder needs.

Explore how requirements modeling tools support elicitation, analysis, test and evaluation, traceability, version control, and collaboration across the requirements lifecycle, with examples from Sparx EA and Catia magic.

Master entity-relationship diagrams to model requirements, using entities, relationships, and attributes to show system elements, roles, and interactions, with multiplicities, composition, and generalization.

Explore how class diagrams depict system elements at various abstraction levels, show relationships, and organize attributes and operations for software and requirements engineering.

Model how data moves between system functions with data flow diagrams, using a top-down, hierarchically decomposed data flow model that includes sources, sinks, data stores, and data flows.

Describe how activity diagrams map participants and messages to actions with object flows and swim lanes, and how start and end nodes, decompositions, and interfaces guide system behavior.

Explore how UML sequence diagrams communicate interactions between actors and systems using lifelines and messages, including synchronous and asynchronous types, translating user requirements into design for implementation.

Explore state machine diagrams by mapping states, transitions, and entry, do, and end activities, using nested and parallel states and time or change events.

Explore block definition diagrams and internal block diagrams to model system structure, hierarchies, and interfaces, and convert these elements into requirement shall statements for an ATM.

Link requirements to system model elements with SysML to enable rigorous traceability. Capture requirements as elements with id and description, using graphical and tabular diagram relationships for verification and derivation.