IAI SP1 study plan

Define the SP1 role and its boundaries relative to business analysis, project management and enterprise architecture, writing a one-page comparison

Explain the systems engineering lifecycle stages and map each SP1 competency area to at least one lifecycle stage

Distinguish hard systems, soft systems and socio-technical perspectives and identify which framing suits three sample problem statements

Construct a system boundary diagram for a familiar organisation, labelling inputs, outputs, environment and interfaces

List the core systems thinking concepts (emergence, feedback, holism, suboptimisation) and give one worked example of each

Apply causal loop and influence diagramming to represent at least two feedback structures in a worked scenario

Analyse a system for emergent behaviour by identifying interactions that produce outcomes no single component produces

Draft a stakeholder-neutral problem statement and convert it into three measurable system-level objectives

Practise elicitation techniques (interview, workshop, observation, document analysis) and record when each is most appropriate

Classify a sample set of requirements as functional, non-functional, constraint or assumption

Write requirements that pass a quality checklist for unambiguous, verifiable, singular and traceable statements

Build a requirements traceability matrix linking stakeholder needs to system requirements to acceptance criteria

Produce a stakeholder map with power, interest, influence and attitude dimensions, and derive an engagement approach for each quadrant

Design a contextual inquiry session plan including observation protocol, interview questions and consent considerations

Identify conflicting stakeholder needs and document the trade-off and resolution rationale

Derive a functional architecture by decomposing system functions and allocating them to logical components

Compare at least three candidate architectures against weighted criteria and justify the selection

Build a SysML-style block definition and internal block structure for the chosen design, describing interfaces and flows

Select appropriate modelling viewpoints (functional, structural, behavioural) for a given analysis question

Document key architectural decisions with context, alternatives considered and consequences

Perform a trade-off evaluation using a documented method and test its sensitivity to changed weightings

Model system behaviour with state or sequence representations and check consistency against the functional architecture

Identify interface risks and specify interface requirements for at least four system boundaries

Evaluate a design against non-functional requirements such as performance, safety, security and maintainability

Critique a peer-style architecture description for gaps, ambiguities and unstated assumptions

Distinguish verification from validation and write a testable criterion for each requirement in a sample set

Construct a verification matrix mapping requirements to methods (inspection, analysis, demonstration, test)

Design an integration strategy (bottom-up, top-down or incremental) and justify the choice for a given architecture

Plan a validation activity with real users or representatives and define acceptance evidence

Define defect reporting and regression handling for a verification campaign

Map governance mechanisms (review gates, baselines, change control boards) to lifecycle stages

Describe configuration and change management for requirements and architecture artefacts, including baseline and version control

Evaluate professional and ethical obligations in two scenarios involving safety, data or conflicting instructions

Compare lifecycle models (waterfall, incremental, iterative) and select one for a stated project context with justification

Identify how SP1 practice integrates with risk management and assurance activities

Consolidate all eight domains into a single revision map showing links between competencies and artefacts

Complete timed practice questions across all domains and analyse errors by domain and reasoning type

Rehearse explaining trade-off and verification decisions aloud in exam-style structured answers

Close remaining knowledge gaps identified in the error analysis with targeted re-study

Confirm readiness by scoring consistently above a self-set threshold on mixed practice sets