From universal principles to global business practices

Stuart Arnold QinetiQJonathan Earthy Lloyd’s Register

INCOSE UK Autumn Assembly 2002

2

INCOSE UK Autumn Assembly 11.11.2002

The changing system engineering paradigm• De-emphasis of systems engineers in system development

making all the system decisions - we all do system engineering

• Life cycle thinking - don’t throw problems and cost over the wall

• Simplistic sequence gives way to more realistic life cycle representations - linearity maps into hierarchy

• Enterprise, project and engineering all influence a system - systems placed in an organisational context

• Bounding the problem - system of interest, system elements, enabling systems

• Life cycle management - synonymous with risk management and control

ISO/IEC 15288 has been six years in the

making.

4

INCOSE UK Autumn Assembly 11.11.2002

SystemsEngineering

Mil-std-499

SoftwareEngineering

1969 Mil-Std-499A

1974Mil-Std-

499B

1994EIA /IS

632

1994EIA 632

1999 ISO15288

2002

IEEEP1220

1994

IEEE1220

1999

ISO12207 Amd 1

1995

Perry halts DoD solutions,US favour civil standards

Standard for Application and Management of the Systems Engineering Process

Process for Engineering a System

Systems EngineeringSystem Life Cycle

Processes

ISO12207

2002

Life Cycle ManagementSoftware Life Cycle Processes

Life Cycle ManagementSoftware Life Cycle Processes

A brief history of Systems Engineering process standards

5

INCOSE UK Autumn Assembly 11.11.2002

ISO/IEC 15288 Active participants

• Australia

• Brazil

• Canada

• Czech Republic

• China

• Denmark

• France

• Germany

• Israel

• Italy

• Japan

• Korea

Up to 35 around the tableOverall cost: ~ $10M

• Russia

• South Africa

• Sweden

• Spain

• UK

• USA

6

INCOSE UK Autumn Assembly 11.11.2002

ISO/IEC 15288 Milestones

• Jun ‘94: Study group on software-system relationship

• Mar ‘95: US ANSI New Work Item proposal

• Apr ‘96: ISO/IEC JTC1 approval of the project

• May ‘96: Work started

• July ‘99: CD 1(766 comments)

• Feb & Nov ‘00: CD 2 (1589 comments)

• May ‘01: CD 3 (673 comments)

• Nov ’01: FCD (715 comments, mostly TL/E)

• Feb ’02: FDIS

• July ‘02 International Standard approval

• Nov ’02 ISO Publication

7

INCOSE UK Autumn Assembly 11.11.2002

Systems engineering is described as a key part of an organisation’s business practices.

9

INCOSE UK Autumn Assembly 11.11.2002

SystemsEngineers

ProjectManagers

BusinessManagers

SpecialistEngineers

EnterpriseProcesses

Project Processes

SystemTechnical

Processes

Implementation Technology Processes

Scope and profile of business processes

10

INCOSE UK Autumn Assembly 11.11.2002

Enterprise Processes

Project Processes

SystemTechnical

Processes

SystemsEngineers

ProjectManagers

BusinessManagers

SpecialistEngineers

Implementation Technology Processes

Profile of ISO/IEC 15288

11

INCOSE UK Autumn Assembly 11.11.2002

Business Processes

Organizational Capability Professional Competence

Business Excellence

Why processes are key to defining and applying Systems Engineering

12

INCOSE UK Autumn Assembly 11.11.2002

CMM2

SystemsEngineering

SoftwareEngineering

EIA/IS731

ISOTR15504

EIA 632

1999 ISO15288

200x

1998

1997

Systems Engineering Capability

Process for Engineering a System

System Life Cycle Processes

SW CMM

CMMI

EIA /IS632

1994

ISO15504

2002

2002A very short history of Capability Assessment

13

INCOSE UK Autumn Assembly 11.11.2002

System Engineering to specialist disciplines• JTC SC7

– ISO/IEC 15288 Systems engineering - System life cycle process

– ISO/IEC 12207 AMD1 Information Technology - Software life cycle process

– ISO/IEC 15504 Process assessment

• TC159– ISO 13407 Human-centred design for interactive systems

– ISO TR 18529 Human-centred life cycle process descriptions

– PAS xxxxx Process assessment of human-system issues

• TC176– ISO 9001 Quality Management System

• IEC SC65 Functional safety– IEC 621508 Functional Safety- safety related systems.

14

INCOSE UK Autumn Assembly 11.11.2002

Stages + enabling systems

Enterprise/Project processes

Technical processes

HS.4.1 Human resources strategyHS.4.2 Define standard competencies and gapsHS.4.3 Design manpower solution and delivery planHS.4.4 Evaluate system solutions

HS.1.1 HS issues in conceptionHS.1.2 HS issues in developmentHS.1.3 HS issues in productionand utilizationHS.1.4 HS issues in utilization and supportHS.1.5 HS issues in retirement

HS.3.1 Context of useHS.3.2 User requirementsHS.3.3 Produce design solutionsHS.3.4 Evaluation of use

HS.2.1 HS issues in business strategy HS.2.2 HS issues in quality mgmt.HS.2.3 HS issues in authorisation and control HS.2.4 Management of HS issuesHS.2.5 HF data in trade-off and risk mitigationHS.2.6 User involvementHS.2.7 Human system integrationHS.2.8 Develop and re-use HF data

Human-centreddesign

Human resources

Life cycle involvement

Human factorsintegration

ISO/IEC 15288

Process Assessment

A view of systems engineering has evolved – one that is more relevant to present day commerce.

16

INCOSE UK Autumn Assembly 11.11.2002

Use so far (WG7 meeting review 2002-11-4)• NB should not be using it at all yet - use is by people

who have been involved in the development.

• Defence - UK(AMS), SWE (FMV), Canada (DND), France (DGA)

• Organisations - Lockheed Martin, Northrop Grummen, QinetiQ

• Professional Bodies - IEE, IEEE , INCOSE

• Very different profile from 12207.

17

INCOSE UK Autumn Assembly 11.11.2002

The Marine Sector• ships carry 96% of goods transport

• as few as 12 people in charge of 440,000 tons, value $70M (with cargo of a similar value)

• 380 metres long, propulsion power 37MW

• recycling everything except fuel (uses 150 tons of oil a day)

• Design life 25-30 years, some still in operation after 70 years

• can move, stay still, and work in temperatures from -35 to +45C and severe storms

• vast, inter-linked set of sub-systems

• all delivered to minimum tender

• built in a year

18

INCOSE UK Autumn Assembly 11.11.2002

Unintended Complexity

• computers used for economy - functionality for market differentiation

• closed systems and “glue code” interfaces - no detailed specification

• compliance culture - third party safety

• ships are not designed systems

• ship control systems are not designed to control the ship

19

INCOSE UK Autumn Assembly 11.11.2002

Process Risk Assessment

• EC ATOMOS IV project, process risk assessment on a 4.3Meuro research SCC retrofit project

• two-part assessment. 1999 - 15504, 13407 and IEC 61508, 2002 - 15288 and HS model

• used: Quality Management, Architectural Design, Validation, Implementation, Verification, Supply, Stakeholder Requirements Definition

• usability and utility of processes

20

INCOSE UK Autumn Assembly 11.11.2002

Dependable Systems Review

• new premium process improvement service for owners with complex ships

• based on the concepts of 15288 and principles of ISO 17894

• “walk through” a project with the client identifying barriers to achieving technical processes

• use workshops, audits and training as appropriate

• findings so far

21

INCOSE UK Autumn Assembly 11.11.2002

Conclusions

• management of system life cycles is key to organisational well-being

• by placing system engineering in a business context the story is more relevant

• initial finding that 15288 life cycle processes work well for assessment and for process improvement

• analyse enterprise and project barriers to technical achievement

• 15288 will give systems engineering the recognition it deserves

• systems engineering is on the business map

22

INCOSE UK Autumn Assembly 11.11.2002

Thank you

• Stuart Arnold QinetiQ

• Jonathan Earthy Lloyd’s Register