+ All Categories
Home > Documents > INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf ·...

INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf ·...

Date post: 10-Mar-2018
Category:
Upload: dothuan
View: 215 times
Download: 1 times
Share this document with a friend
55
INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future Professor Philip John, Cranfield University [email protected]
Transcript
Page 1: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

INCOSE UK ChapterAutumn Assembly 2001

Systems Engineering :Past, Present & Future

Professor Philip John, Cranfield [email protected]

Page 2: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

Technical Requirement Specifications• System TRS• Subsystem TRSs

Interface Control Documents

Design Reviews

Multidisciplinary teams

System Proving

System Design methodologiesand supporting tools

Configuration Management

What is SE ?

Concurrent Engineering

Availability Reliability & MaintainabilityHuman Factors Logistics Support Analysis

Safety

Performance

Requirements Management Requirements Engineering

System Integration

Simulation & ModellingTrials

Standards

Functional ArchitecturePhysical Architecture

System Test, Evaluation & Acceptance

Verification & ValidationSystem Installation

Training

Page 3: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

A Basic View of SE Process

User Requirements

System Design

Subsystem Testing

Integration Tests

Acceptance Tests

System Requirements

Sub-system Reqts

Sub-system Development & Build

System Tests

Page 4: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

A Basic View of SE Process

User Requirements

System Design

Subsystem Testing

Integration Tests

Acceptance Tests

System Requirements

Sub-system Reqts

Sub-system Development & Build

System TestsUnderstanding the problem

Formulating anacceptable solution

Implementing the solution

Proving the solution

Page 5: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

Process Improvements

Page 6: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

Process Improvements

* Systematic, disciplined systems process

Page 7: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

Process Improvements

* Systematic, disciplined systems process* Objective : balancing performance, cost & time

Page 8: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

Process Improvements

* Systematic, disciplined systems process* Objective : balancing performance, cost & time* Need to avoid expensive, late surprises … early decisions

crucial

Page 9: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

Process Improvements

* Systematic, disciplined systems process* Objective : balancing performance, cost & time* Need to avoid expensive, late surprises … early decisions

crucial* Focus on …

> identifying decision drivers & evaluating options> increased rigour through formal methods, scenarios, use cases etc> through life approach … making trade-offs> use of simulation, prototyping etc> multidisciplinary teams> information sharing, justification, traceability

Page 10: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

Process Improvements

* Systematic, disciplined systems process* Objective : balancing performance, cost & time* Need to avoid expensive, late surprises … early decisions

crucial* Focus on …

> identifying decision drivers & evaluating options> increased rigour through formal methods, scenarios, use cases etc> through life approach … making trade-offs> use of simulation, prototyping etc> multidisciplinary teams> information sharing, justification, traceability

* Not much focus on the nature of systems themselves

Page 11: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

Are process improvements enough ?

User Requirements

System Design

Subsystem Testing

Integration Tests

Acceptance Tests

System Requirements

Sub-system Reqts

Sub-system Development & Build

System TestsUnderstanding the problem

Formulating anacceptable solution

Implementing the solution

Proving the solution?

??

Page 12: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

Understanding the problem

Page 13: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

Automobile technology about 1890

Early Systems developmentsdrew heavily on previous experience

Page 14: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

Automobile technology about 1890

Early Systems developmentsdrew heavily on previous experience

• Expectations centred on performance• Fundamental architecture based on years of evolution• Fundamental interactions and influences in the environment well precedented e.g. ‘we know who the stakeholders are’• … the problem to be tackled was clear

Page 15: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

SE formalised in US defence & aerospace (e.g. B47 Stratojet)

Formalised Systems Engineeringdealt with similarly clear problems

… problem was fairly clear … aircraft & their operations were well understood … users & stakeholders were ‘obvious’

Page 16: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

The Systems challengeis becoming more complex

Page 17: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

The Systems challengeis becoming more complex

* Customer / Enterprise expectations> Constraints (performance, time, cost .. including through life cost etc)> Customers want Benefits achieved, not features for their own sake> We need to decide what is relevant to achieve those benefits> Customers want customisation & adaptability

Page 18: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

The Systems challengeis becoming more complex

* Customer / Enterprise expectations> Constraints (performance, time, cost .. including through life cost etc)> Customers want Benefits achieved, not features for their own sake> We need to decide what is relevant to achieve those benefits> Customers want customisation & adaptability

* Enterprise environment> extended, global … organisations, team dynamics & decisions are complex

Page 19: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

The Systems challengeis becoming more complex

* Customer / Enterprise expectations> Constraints (performance, time, cost .. including through life cost etc)> Customers want Benefits achieved, not features for their own sake> We need to decide what is relevant to achieve those benefits> Customers want customisation & adaptability

* Enterprise environment> extended, global … organisations, team dynamics & decisions are complex

* Highly integrated with environment & other systems> stronger, wider influences & interrelationships

Page 20: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

The Systems challengeis becoming more complex

* Customer / Enterprise expectations> Constraints (performance, time, cost .. including through life cost etc)> Customers want Benefits achieved, not features for their own sake> We need to decide what is relevant to achieve those benefits> Customers want customisation & adaptability

* Enterprise environment> extended, global … organisations, team dynamics & decisions are complex

* Highly integrated with environment & other systems> stronger, wider influences & interrelationships

* Increasing rate of change … & uncertainty> need to establish through life robustness … through life influences

Page 21: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

The Systems challengeis becoming more complex

* Customer / Enterprise expectations> Constraints (performance, time, cost .. including through life cost etc)> Customers want Benefits achieved, not features for their own sake> We need to decide what is relevant to achieve those benefits> Customers want customisation & adaptability

* Enterprise environment> extended, global … organisations, team dynamics & decisions are complex

* Highly integrated with environment & other systems> stronger, wider influences & interrelationships

* Increasing rate of change … & uncertainty> need to establish through life robustness … through life influences

* Situations are becoming increasingly varied & unprecedented

Page 22: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

The Systems challengeis becoming more complex

* Customer / Enterprise expectations> Constraints (performance, time, cost .. including through life cost etc)> Customers want Benefits achieved, not features for their own sake> We need to decide what is relevant to achieve those benefits> Customers want customisation & adaptability

* Enterprise environment> extended, global … organisations, team dynamics & decisions are complex

* Highly integrated with environment & other systems> stronger, wider influences & interrelationships

* Increasing rate of change … & uncertainty> need to establish through life robustness … through life influences

* Situations are becoming increasingly varied & unprecedented….. We, as systems engineers, must decide what is relevant and

critical and highest priority more explicitly than ever before

Page 23: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

The Systems challengeis becoming more complex

* Customer / Enterprise expectations> Constraints (performance, time, cost .. including through life cost etc)> Customers want Benefits achieved, not features for their own sake> We need to decide what is relevant to achieve those benefits> Customers want customisation & adaptability

* Enterprise environment> extended, global … organisations, team dynamics & decisions are complex

* Highly integrated with environment & other systems> stronger, wider influences & interrelationships

* Increasing rate of change … & uncertainty> need to establish through life robustness … through life influences

* Situations are becoming increasingly varied & unprecedented….. We, as systems engineers, must decide what is relevant and

critical and highest priority more explicitly than ever before…. we face open problems rather than closed problems

Page 24: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

EmergentCapability

Influences (time, cost etc)

Related Systems

Wider environment /situation

Influences & Interactions

System

Page 25: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

Implications for Systems Engineering

Page 26: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

Implications for Systems Engineering

*We must establish a clear, common understanding of our view of the problem across stakeholders, the SE team etc

Page 27: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

Implications for Systems Engineering

*We must establish a clear, common understanding of our view of the problem across stakeholders, the SE team etc*We cannot rely on previous precedents

Page 28: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

Implications for Systems Engineering

*We must establish a clear, common understanding of our view of the problem across stakeholders, the SE team etc*We cannot rely on previous precedents* … this system context and associated decisions must be established and communicated explicitly

Page 29: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

Implications for Systems Engineering

*We must establish a clear, common understanding of our view of the problem across stakeholders, the SE team etc*We cannot rely on previous precedents* … this system context and associated decisions must be established and communicated explicitly*Soft methods are essential in progressing such ‘open’ problems towards a tangible systems engineering programme

Page 30: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

Formulating an acceptable solution

Page 31: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

Systems solutions arebecoming more complex

Page 32: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

Systems solutions arebecoming more complex

* An increasing number of subsystem options (choices) are available to us

Page 33: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

Systems solutions arebecoming more complex

* An increasing number of subsystem options (choices) are available to us

* Systems are more highly integrated than ever> enabled by IT and communications technologies> moving away from the historical role of the human operator as the primary

system integrator and embedding more decisions in the system design

Page 34: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

Systems solutions arebecoming more complex

* An increasing number of subsystem options (choices) are available to us

* Systems are more highly integrated than ever> enabled by IT and communications technologies> moving away from the historical role of the human operator as the primary

system integrator and embedding more decisions in the system design

* We are no longer constrained by historical system architectures> we need to develop more sophisticated architectural design approaches> many system architectures are unprecedented

Page 35: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

Systems solutions arebecoming more complex

* An increasing number of subsystem options (choices) are available to us

* Systems are more highly integrated than ever> enabled by IT and communications technologies> moving away from the historical role of the human operator as the primary

system integrator and embedding more decisions in the system design

* We are no longer constrained by historical system architectures> we need to develop more sophisticated architectural design approaches> many system architectures are unprecedented

* The relationship between Function & Form is changing significantly

Page 36: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

System Architecture

Page 37: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

System Architecture

SYSTEM

Function

Subsystem

Function

Subsystem

Function

Subsystem

Page 38: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

System Architecture

SYSTEM

Function

Subsystem

Function

Subsystem

Function

Subsystem

….‘DETAIL Complexity’Senge (1990)

Page 39: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

System Architecture

SYSTEM

Function

Subsystem

Function

Subsystem

Function

Subsystem

….‘DETAIL Complexity’Senge (1990)

….‘DYNAMIC Complexity’

SYSTEM

Function

Subsystem

Function

Subsystem

Function

Subsystem

Page 40: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

System Architecture

SYSTEM

Function

Subsystem

Function

Subsystem

Function

Subsystem

….‘DETAIL Complexity’Senge (1990)

….‘DYNAMIC Complexity’

SYSTEM

Function

Subsystem

Function

Subsystem

Function

Subsystem

This change in system characteristics has far

reaching implications for SE

Page 41: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

Implications for Systems Engineering

Page 42: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

Implications for Systems Engineering

* System Architectures must be designed with little or no precedent

> we must be more explicit and careful in our architectural designfrom the outset> we need to understand system interactions more explicitly … they are no longer ‘obvious’ … they must be explored and communicated

Page 43: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

Implications for Systems Engineering

* System Architectures must be designed with little or no precedent

> we must be more explicit and careful in our architectural designfrom the outset> we need to understand system interactions more explicitly … they are no longer ‘obvious’ … they must be explored and communicated

* Organisational and contractual barriers are increasingly likely to cut through critical system relationships

Page 44: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

Implications for Systems Engineering

* System Architectures must be designed with little or no precedent

> we must be more explicit and careful in our architectural designfrom the outset> we need to understand system interactions more explicitly … they are no longer ‘obvious’ … they must be explored and communicated

* Organisational and contractual barriers are increasingly likely to cut through critical system relationships* System evaluation …gaining confidence in our system ... is increasingly difficult

Page 45: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

Proving the solution

Page 46: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

Implications of increasing complexity

Page 47: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

Implications of increasing complexity* The increased complexity of the external systems challenge :

> how do we assess the validity of our analysis of the important influences and interactions when they are unprecedented ? … how do we judge criticality ? … how do we judge if we’ve thought of everything ? … more difficult to identify all the stakeholders

Page 48: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

Implications of increasing complexity* The increased complexity of the external systems challenge :

> how do we assess the validity of our analysis of the important influences and interactions when they are unprecedented ? … how do we judge criticality ? … how do we judge if we’ve thought of everything ? … more difficult to identify all the stakeholders

* The move from Detail Complexity to Dynamic Complexity in System design :> system interdependencies more difficult to identify … most are indirect …

again, many are unprecedented> system behaviour more difficult to predict with confidence … how do we

judge if we’ve done enough testing / simulation / scenarios / use cases ?> Historical techniques such as Failure Mode & Effects Analysis need to be re-

thought

Page 49: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

Implications of increasing complexity* The increased complexity of the external systems challenge :

> how do we assess the validity of our analysis of the important influences and interactions when they are unprecedented ? … how do we judge criticality ? … how do we judge if we’ve thought of everything ? … more difficult to identify all the stakeholders

* The move from Detail Complexity to Dynamic Complexity in System design :> system interdependencies more difficult to identify … most are indirect …

again, many are unprecedented> system behaviour more difficult to predict with confidence … how do we

judge if we’ve done enough testing / simulation / scenarios / use cases ?> Historical techniques such as Failure Mode & Effects Analysis need to be re-

thought

* “Given system complexity, multiple & unexpected interactions of failures are inevitable” Normal Accidents, Perrow

Page 50: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

Summary

Page 51: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

Summary

* We face increased integration (internal and external to our system) and this has profound implications for Systems Engineering

Page 52: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

Summary

* We face increased integration (internal and external to our system) and this has profound implications for Systems Engineering* These cannot be addressed by process improvements alone … it is crucial that systems engineers understand systems & their implications

Page 53: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

Summary

* We face increased integration (internal and external to our system) and this has profound implications for Systems Engineering* These cannot be addressed by process improvements alone … it is crucial that systems engineers understand systems & their implications* “Soft” and “Hard” approaches must both be a fundamental part of the systems engineer’s skills

Page 54: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

Summary

* We face increased integration (internal and external to our system) and this has profound implications for Systems Engineering* These cannot be addressed by process improvements alone … it is crucial that systems engineers understand systems & their implications* “Soft” and “Hard” approaches must both be a fundamental part of the systems engineer’s skills* Fundamental historical practices must be reassessed & progressed with increasing care and with explicit decisions and communication :

> e.g. problem closure, architecture design, FMECA, system evaluation

Page 55: INCOSE UK Chapter Autumn Assembly 2001 - LAAS-CNRShomepages.laas.fr/kader/SE_PPF_Cranfield.pdf · INCOSE UK Chapter Autumn Assembly 2001 Systems Engineering : Past, Present & Future

Systems Engineeringin the 21st Century

Understanding &Dealing withSYSTEMS

Process Discipline

Hard & Soft approaches,methods & tools

• Systems Engineering Body of Knowledge

• SE competencies

• Training & Education

• Continuing Professional Development


Recommended