IAI SP1 study guide
IAI SP1 · Work through your exam, one topic at a time.
SP1 (Systems Practice 1) is a certification offered by the International Association for Innovation (IAI) for people who apply systems engineering and systems thinking in practice, whether as systems engineers, requirements analysts, architects, integrators or technical leads moving into a systems role. It tests judgement as much as recall: how you frame a problem, bound a system, engage stakeholders, turn needs into verifiable requirements, shape a conceptual design, evaluate trade-offs, and carry a system through integration, verification, validation and lifecycle governance. The IAI SP1 study guide has 9 sections and about 2,628 words.
01Systems Practice Foundations and the SP1 Framework
Domain 1 tests whether you can explain what systems engineering is for, how the SP1 framework organizes practice, and why a lifecycle perspective changes technical decisions. Expect questions on process purpose, the systems engineer's role, and the distinction between performing systems engineering and completing templates.
368 words, about 2 min02Systems Thinking and Holistic Analysis
Domain 2 tests holistic analysis: setting system boundaries, recognizing emergence, and reasoning about feedback instead of decomposing a problem into isolated parts and assuming the parts explain the whole. A system is a set of interacting elements organized to achieve one or more stated purposes.
310 words, about 2 min03Stakeholder Engagement and Contextual Inquiry
Domain 3 tests stakeholder engagement and contextual inquiry: identifying who matters, separating needs from wants, and understanding how the context of use shapes requirements. Stakeholders include users, operators, maintainers, acquirers, regulators, and affected parties-not only the paying customer.
286 words, about 1 min04Requirements Elicitation, Analysis and Specification
Domain 4 tests requirements elicitation, analysis, and specification: producing statements that are necessary, unambiguous, complete, and verifiable, and tracing them to sources and evidence. A requirement is a statement that translates or expresses a need and its associated constraints and conditions.
286 words, about 1 min05System Architecture and Conceptual Design
Domain 5 tests system architecture and conceptual design: partitioning a system, defining interfaces, allocating requirements, and making structure explicit before detailed design commits cost. Architecture is the fundamental organization of a system embodied in its elements, their relationships to each other and to the environment, and the principles guiding its design and evolution.
292 words, about 1 min06Systems Modelling, Analysis and Trade-off Evaluation
Domain 6 tests modeling, analysis, and trade-off evaluation: selecting a model for the question, validating it for use, and comparing alternatives against explicit criteria and uncertainty. A model is an abstraction for a purpose.
288 words, about 1 min07Integration, Verification and Validation
Domain 7 tests integration, verification, and validation: assembling elements into a system, proving compliance, and proving fitness for use in the operational context. Integration combines elements according to an integration plan.
274 words, about 1 min08Lifecycle Management
Domain 8 tests lifecycle management: planning across stages, using decision gates, controlling configuration, and transitioning the system into operation and support. ISO/IEC/IEEE 15288 describes life cycle stages from concept through retirement.
258 words, about 1 min09Governance and Professional Practice
Domain 9 tests governance and professional practice: decision rights, accountability, ethics, regulation, and the systems engineer's responsibility to the public and the profession. Governance sets decision rights, accountability, and oversight.
266 words, about 1 min