Presentation is loading. Please wait.

Presentation is loading. Please wait.

Interfacing Risk and Systems Engineering – Left Shift Risk Management

Similar presentations


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 Conference 9th November 2007 Val Jonas

2 Agenda Basics of Systems Engineering The concept of “Left Shift”
Application to three stages of Systems Engineering Conclusions

3 Systems Engineering Systems 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 need Operational use Capability requirements Acceptance tests User requirements User tests Customer Supplier System specification System tests Customer Supplier Subsystem specifications Subsystem tests

5 Traceability and Compliance
Statement of need Operational use satisfies validating the User verifying the system qualifying the subsystems qualifying components Capability requirements Acceptance tests User requirements User tests System specification System tests 2. 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 specifications Subsystem tests

6 Tackled as potential problems
<Left Shift Cost of Recovery Emergence as problems No. of Problem causes Established Tackled as potential problems

7 Left shift during 3 stages
Understand context Create the baseline requirements acceptance criteria Manage change

8 Stage 1 - Understand context
Portfolio Analysis Economic, environment, market influences Strategic Risks (threats & opportunities) Operational use User requirements System specification Subsystem specification User tests System tests Subsystem tests Acceptance tests Capability requirements Statement of need Options considerations Business benefits

9 Case study: Rail industry Requirement: increased passenger capacity
Portfolio analysis Overlap with Technical Upgrade Programme Economic, environment, market influences GDP Investment / financing environment Evolving stakeholder expectations Competitors Change of London Mayor Options analysis Benefits case 1. More seats (added safety requirements) 2. Longer trains (longer platforms) 3. Double-decker trains (taller tunnels) 4. High speed trains (upgraded track) Options comparison Schedule, budget, resources Procurement strategy Lease value and life Reputation / image

10 Stage 2 – Create the baseline
Requirements & Acceptance Criteria Identify risks against requirements & develop mitigation strategies Operational use User requirements System specification Subsystem specification User tests System tests Subsystem tests Acceptance tests Capability requirements Statement of need Identify risks to achieving compliance Risk and Action Register Identify sub-system requirements risk (in lower level risk registers) Supplier 1 Risk Register Supplier 2 Risk Register

11 Case study: Utilities Requirement: National infrastructure upgrade
High level risks to achieving requirements Acceptance risks Difficulty gaining stakeholder agreement Long-winded ministerial approval process Need for public consultations Change of government / general election New health & safety legislation Related disaster Influence of regulatory review New leases non-compliant Sub-system Acceptance risks Low level risks to achieving requirements System platform incompatibility Obsolete technology Failure to reach reliability targets Insufficient trials New technology unavailable Failure to achieve wayleave consent Raw materials not availabie Legacy platform restricts design options

12 Stage 3 – Manage Change Case study: UK MoD
Manage scope creep Write requirements in sufficient detail Enforce rigorous change and configuration control Evaluate potential change in advance Traceability (Doors) Risk assessment (Predict! and ARM) & risk analysis (Predict!) Beware of opportunities – they can bite!

13 Tackled as potential problems
= Risk Management <Left Shift Cost of Recovery Emergence as problems No. of Problem causes Established Tackled as potential problems

14 Thank you


Download ppt "Interfacing Risk and Systems Engineering – Left Shift Risk Management"

Similar presentations


Ads by Google