Presentation on theme: "Interfacing Risk and Systems Engineering – Left Shift Risk Management"— Presentation transcript:
1 Interfacing Risk and Systems Engineering – Left Shift Risk Management Incose Conference9th November 2007Val Jonas
2 Agenda Basics of Systems Engineering The concept of “Left Shift” Application to three stages of Systems EngineeringConclusions
3 Systems EngineeringSystems Engineering consists of the technical and management processes used to transform operational needs, concepts, and policies into a system configuration that optimises the total system design to meet cost, schedule and technical performance objectives.
4 Requirements process Customer Supplier Customer Supplier Statement of needOperational useCapability requirementsAcceptance testsUser requirementsUser testsCustomerSupplierSystem specificationSystem testsCustomerSupplierSubsystem specificationsSubsystem tests
5 Traceability and Compliance Statement of needOperational usesatisfiesvalidating the Userverifying the systemqualifying the subsystemsqualifying componentsCapability requirementsAcceptance testsUser requirementsUser testsSystem specificationSystem tests2. An important part of the requirements management discipline is to ensure traceability.Individual requirements are traced back to the requirements they are designed to satisfy.Individual tests are traced back to the requirements they are designed to verify.2. One of the main purposes of tracing requirements is to be able to perform impact analysis when things change.If a high-level requirement is subject to change, tracing can be used to determine the potential impact of that change.Subsystem specificationsSubsystem tests
6 Tackled as potential problems <Left ShiftCost of RecoveryEmergence as problemsNo. ofProblem causesEstablishedTackled as potential problems
7 Left shift during 3 stages Understand contextCreate the baselinerequirementsacceptance criteriaManage change
11 Case study: Utilities Requirement: National infrastructure upgrade High level risks to achieving requirementsAcceptance risksDifficulty gaining stakeholder agreementLong-winded ministerial approval processNeed for public consultationsChange of government / general electionNew health & safety legislationRelated disasterInfluence of regulatory reviewNew leases non-compliantSub-system Acceptance risksLow level risks to achieving requirementsSystem platform incompatibilityObsolete technologyFailure to reach reliability targetsInsufficient trialsNew technology unavailableFailure to achieve wayleave consentRaw materials not availabieLegacy platform restricts design options
12 Stage 3 – Manage Change Case study: UK MoD Manage scope creepWrite requirements in sufficient detailEnforce rigorous change and configuration controlEvaluate potential change in advanceTraceability (Doors)Risk assessment (Predict! and ARM) & risk analysis (Predict!)Beware of opportunities – they can bite!
13 Tackled as potential problems = Risk Management<Left ShiftCost of RecoveryEmergence as problemsNo. ofProblem causesEstablishedTackled as potential problems