finse, finish chapter of incose, 26 th may 2005, helsinki, s.arnold standard systems engineering in...
TRANSCRIPT
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Standard Systems Engineering in the Business Environment
Stuart ArnoldQinetiQFort HalsteadSevenoaksKent TN14 7BP
+44 1959 514961+44 7770 [email protected]
A Thought…
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Definition 1………..
Definition 2………..
………..
Standard
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
………..
………..
………..
A device or emblem used as a rallying point in times of conflict or battle
Standard
A Changing View of Systems Engineering
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
In the early 90’s new views of systems engineering were emerging
- driven largely by the business environment and international trade
A reassessment of Systems Engineering was occurring
exactly what it is, why we do it, how we do it who does it
when do we do it …..
……and can we all agree on it ?
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Systems Engineering - Everyone has their own model
SystemsEngineering
Product
ServiceSystem
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Increasing business challenge in systems
Additional complexity in systems– multiple technologies
– multiple contributing enterprises
Coordinated cooperation
More capability + less budget– Need for international customers
– Need for international supplier collaborations
International trade
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
The changing systems engineering paradigm
De-emphasis of systems engineers in development making all the system decisions - we all do systems engineering.
Life cycle thinking - don’t throw problems and costs over the wall.
Simplistic sequence gives way to more realistic life cycle representations - linearity maps into hierarchy
Enterprises, projects and technologies influence a system’s architecture.
Life cycle management - synonymous with risk management.
Cooperation between contributors - softening the traditional boundaries of multiple trading enterprises.
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Systems Engineering – A Key Component of the Organization’s Business
Management System
ISO (trade and commerce) and IEC (technical integrity and safety) recognised that a shift in the definition of business processes was occuring – setting systems engineering in terms of both technical and management actions.
Organisations needed a common, internationally-endorsed approach to their management of system complexity.
ISO and IEC jointly decided to act as the forum for the international definition and codification of systems engineering.
In the foreseeable future, the approaches defined in this International Standard are expected to be an aspect of standard business practice.
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Systems Engineering – A Key Component of the Organization’s
Business Management System
ISO/IEC International Standard to:
Codify a widely accepted model for international cooperative action
Designate common concepts for clarity of international communication
Establish common understanding to underpin agreement and consent
Permit actions and responsibilities to be cited in formal or informal acquirer/supplier transactions
Support the determination of organisational capability
Contribute to a framework for developing individual competence
Process Descriptions of Systems Engineering
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Systems Engineering - Everyone has their own model
SystemsEngineering
Product
ServiceSystem
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
People (in organizations) act on systems by performing processes throughout the life cycle.
Process is the most effective basis for a common model
Product
Service
System
Process
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Mil-std-499
1969
Mil-Std-499A
1974
Mil-Std-499B
1994
EIA IS 632
1994
IEEEP1220
1994
DoD solutions halted,
US favour civil standards
Early codification of systems engineering
Emphasis of systems engineers in development making all the system decisions.
Simplistic sequence describes system lifetime
Limited life cycle thinking threw problems and costs ‘over the wall’
Defence/aerospace view
Big acquirer/big supplier perspective
US culture view
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
SystemsEngineering
A Brief History of Systems Engineering Process Standards
Mil-std-499
SoftwareEngineering
1969 Mil-Std-499A
1974Mil-Std-
499B
1994EIA /IS
632
1994
ISO15288
IEEEP1220
1994
1995
DoD solutions halted,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
Life Cycle ManagementSoftware Life Cycle Processes
DERA Systems Engineering
Reference Model
1997
ESA PS-05Software Engineering
Standard
1993
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
SystemsEngineering
A Brief History of Systems Engineering Process Standards
Mil-std-499
SoftwareEngineering
1969 Mil-Std-499A
1974Mil-Std-
499B
1994EIA /IS
632
1994EIA 632
1999
ISO15288
IEEEP1220
1994
IEEE1220
1999
ISO12207 Amd 1
1995
DoD solutions halted,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
DERA Systems Engineering
Reference Model
1997
ESA PS-05Software Engineering
Standard
1993
2001
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
SystemsEngineering
A Brief History of Systems Engineering Process Standards
Mil-std-499
SoftwareEngineering
1969 Mil-Std-499A
1974Mil-Std-
499B
1994EIA /IS
632
1994EIA 632
1999
ISO/IEC15288
IEEEP1220
1994
IEEE1220
1999
ISO/IEC12207 Amd 1
1995
DoD solutions halted,US favour civil standards
Standard for Application and Management of the Systems Engineering Process
Process for Engineering a System
Systems EngineeringSystem Life Cycle
Processes
ISO/IEC12207
2002
Life Cycle ManagementSoftware Life Cycle Processes
Life Cycle ManagementSoftware Life Cycle Processes
DERA Systems Engineering
Reference Model
1996
ESA PS-05Software Engineering
Standard
1993
2001
200X
EIA 632
IEEE1220
ISO/IEC12207
200X
A Challenging Journey
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Active ISO/IEC 15288 participants
Australia Brazil Canada China Czech Republic Denmark France Germany Israel
Italy Japan Korea Norway Russia Sweden Spain UK USA
Up to 40 around the table
Final cost $9.5M
INCOSE
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
ISO/IEC 15288 Milestones
Jun ‘94: ISO Study Group on software-system relationship
Mar ‘95: USA New Work Item proposal
Apr ‘96: ISO/IEC JTC1 approval of the project
May ‘96: Work started
July ‘99: CD 1(766 comments)
Feb ‘00: CD 2 (1450 comments)
Nov ‘00: CD 2 rev (300 comments)
May ‘01: CD 3 (680 comments)
Nov ’01: FCD (274 Comments)
Jan ’02: FDIS
June ’02: Unanimous ratification of International Standard
Nov ’02: Publication
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Keep in mind
ISO/IEC 15288 only a model, like any model it has problems of representing the complexity of reality and has limits to its range of validity.
It is a top-level model that will need to be supported by detail in other standards.
Reviewers and users all want to see themselves in the model ISO/IEC 15288
Most people come to 15288 preconditioned by models in other systems engineering standards.
It is not intended to be a idealized model; it has to be used in practice.
ISO/IEC 15288 is therefore a workable compromise.
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Also keep in mind
ISO/IEC 15288 is principally implemented using language
– linear sequence of words - trying to capture an iterative, recursive, dynamic reality
– most of the good words have been used in other models with different meaning - misconceptions
– unambiguous translation into French, Russian and also Spanish, Japanese, Swedish, Portuguese etc. introduces constraints -
Graphical/schematic representations may be rich but they imply notations and conventions which have to be interpreted.
In varying detail, the users of ISO/IEC 15288 are all functions in the organisation – one story, many actors, many discipline-specific terms.
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
And a few more challenges?
It was a requirement that it can be cited in contract.
Many concepts were muddled in preceding standards (Verification and
Validation, Process and Life Cycle Stage, Products and Services, Systems and
Components, Iteration and Recursion)
The decision to write a Guide (ISO Technical Report) was made half
way through.
It was a requirement that it could be used for maturity assessment.
Size matters!
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Were we successful?
Published Nov 2002 Links to implementation
technology standards Links to assessment
standards
From a business perspective it…..
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Business Outcomes of Complying with ISO/IEC 15288
Provides a tailorable, multi-domain, system-driven profile of business processes.
Can be applied bi-laterally, contributes to consistency across a trading boundary; applied multi-laterally, contributes to supply chains.
Lets customer satisfaction drive technology opportunities and the supplier chain.
Influences inter-and intra-organisational accountability and structure.
Defines system-oriented managerial outcomes that are directed toward customer satisfaction.
Builds the essential relationship between product creation and the provision and management of services.
Assists development of a service (capability)-driven culture
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Application in the Defence Industry
Acquisition Management System
ISO/IEC 15288 is the basis of UK MOD’s Acquisition Policy and Process Framework
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Application in the Rail Industry
From the EPT Final Report
“During the development phase [of ERTMS] a robust System Engineering Process and Quality Management System will be required. The scope of this work would include the production and approval of necessary processes, procedures and standards based on ISO/IEC 15288 and CENELEC EN 50126, and the achievement of ISO 9000 certification”.
From the EPT Year 1 Progress Report 2003
“…the EPT has established a Quality Management System. It is based on IEC 15288 but has been focused on the specific needs of the programme. It concentrates on staff competencies, configuration management, change control, document review and requirement management, and is underpinned by a programme of internal audits…”.
Establishing the Business Context
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
ProjectManagers
BusinessManagers
SpecialistEngineers
Enterprise Processes
Project Processes
Implementation Technology Processes
Mind The Gap
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
ProjectManagers
BusinessManagers
SpecialistEngineers
Enterprise Processes
Project Processes
Implementation Technology Processes
Same Gap – Multiple Views
Project View of Systems Implementation
Discipline View of Systems
Described in Project
Management Practices/Body of
Knowledge
Described in Discipline Standards/Practices
e.g. Software Practices, Human Centred Practices
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
SystemsEngineers
ProjectManagers
BusinessManagers
SpecialistEngineers
Enterprise Processes
Project Processes
SystemTechnical
Processes
Implementation Technology Processes
A Common, Profiled View Set in a Management Context
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Context for Systems Engineering
SOCIAL ENVIRONMENT
ENTERPRISE ENVIRONMENT
PROJECT ENVIRONMENT
SYSTEMS ENGINEERING DOMAIN
IMPLEMENTATION TECHNOLOGYENVIRONMENT
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Organization
ENTERPRISEPROCESSES
PROJECT PROCESSES
TECHNICALPROCESSES
enterprisemanagement
projectmanagement
technicalmanagement
Organisational Structure
enterprisethat part of an organization with responsibility to acquire and to supply products and/or services according to agreementsNOTE An organization may be involved in several enterprises and an enterprise may involve one or more organizations.
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
AGREEMENTPROCESSES
Organization A Organization C
ENTERPRISEPROCESSES
PROJECT PROCESSES
TECHNICALPROCESSES
enterprisemanagement
projectmanagement
technicalmanagement
ENTERPRISEPROCESSES
PROJECT PROCESSES
TECHNICALPROCESSES
enterprisemanagement
projectmanagement
technicalmanagement
Organisational trading
agreementthe mutual acknowledgement of terms and conditions under which a working relationship is conducted
acquirerthe stakeholder that acquires or procures a product or service from a supplierNOTE Other terms commonly used for an acquirer are buyer, customer, purchaser. The acquirer may at the same time be the owner, user or operating organization.
supplieran organization or an individual that enters into an agreement with the acquirer for the supply of a product or service
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
AGREEMENTPROCESSES
Organization A
Organization B
Organization C
AGREEMENTPROCESSES
ENTERPRISEPROCESSES
PROJECT PROCESSES
TECHNICALPROCESSES
enterprisemanagement
projectmanagement
technicalmanagement
ENTERPRISEPROCESSES
PROJECT PROCESSES
TECHNICALPROCESSES
enterprisemanagement
projectmanagement
technicalmanagement
ENTERPRISEPROCESSES
PROJECT PROCESSES
TECHNICALPROCESSES
enterprisemanagement
projectmanagement
technicalmanagement
Organisational trading Acquirer/supplier chains
Structure, Architecture, Hierarchy and Recursion
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Aircraft System
Defining a Systemsystema combination of interacting elements organized to achieve one or more stated purposesNOTE 1 A system may be considered as a product or as the services it provides.NOTE 2 In practice, the interpretation of its meaning is frequently clarified by the use of an associative noun, e.g. aircraft system. Alternatively the word system may be substituted simply by a context dependent synonym, e.g. aircraft, though this may then obscure a system principles perspective.
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
System
System element
System element
System element
is completely composed of
A system
a set of interacting
system elements
System Compositionsystema combination of interacting elements organized to achieve one or more stated purposesNOTE 1 A system may be considered as a product or as the services it provides.NOTE 2 In practice, the interpretation of its meaning is frequently clarified by the use of an associative noun, e.g. aircraft system. Alternatively the word system may be substituted simply by a context dependent synonym, e.g. aircraft, though this may then obscure a system principles perspective.
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Aircraft SystemAirframesystem
Propulsionsystem
Air Crew
Life support system
Flight controlsystem
Navigationsystem
Global positioningreceiver system
Displaysystem Navigation
System
Recursion gives us Hierarchy
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Air trafficcontrol system
Air Transport System
Fueldistribution
system
Airportsystem
Ticketingsystem
GroundTransportation
System
MaritimeTransportSystem
Aircraft SystemAirframesystem
Propulsionsystem
Air Crew
Life support system
Flight controlsystem
Navigationsystem
Global positioningreceiver system
Displaysystem Navigation
System
Recursion gives us Hierarchy
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Establishing One’s Bearings in Recursion
PRODUCT
SUBASSEMBLY
PART
ASSEMBLY
1:N
1:N
1:NX
Real world - absolute
SYSTEM-OF-INTEREST
SYSTEM
SYSTEM ELEMENT
SYSTEM
1:NX
1:N
1:N
Abstract - absolute
SYSTEM
SYSTEM
SYSTEM
SYSTEM
1:N
1:N
1:N
Abstract - relative
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
System element
System-of-interest
System element
System element
System element
Architecture Assists the Management of Complexity
system-of-interestthe system whose life cycle is under consideration in the context of this International Standard
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
System element
System-of-interest
System element
System element
System elementSystem
System element
System element
System element
System
System element
System element
System element
Architecture Assists the Management of Complexity
system elementa member of a set of elements that constitutes a systemNOTE A system element is a discrete part of a system that can be implemented to fulfil specified requirements
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
System element
System-of-interest
System element
System element
System elementSystem
System element
System element
System element
System
System element
System element
System element
System
System element
System element
System element
System
System element
System element
System
System element
System element
Architecture Assists the Management of Complexity
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
System element
System-of-interest
System element
System element
System elementSystem
System element
System element
System element
System
System element
System element
System element
System
System element
System element
System elementSystem
System element
System element
System
System element
System element
System
System element
System element System
System element
System element
System element
Architecture Assists the Management of Complexity
Project Focus
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
System-of-interest
System
System element
Project
(Subordinate) Project
1:many
1:many
Isresponsible
for
Isresponsible
for
System
1:many
Acquisition
Supply
ISO/IEC 15288’s Project Centred View
projectan endeavour with defined start and finish dates undertaken to create a product or service in accordance with specified resources and requirementsNOTE 1 Adapted from ISO 9000: 2000 and the PMBOK Guide(2000).NOTE 2 A project may be viewed as a unique process comprising co-ordinated and controlled activities and may be composed of activities from the Project Processes and Technical Processes defined in this International Standard..
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Systems Engineering is Conducted in Projects
Project Planning Process
Project Assessment Process
Project Control Process
Decision-makingProcess
Risk ManagementProcess
Configuration Management ProcessAgreement Processes
Information Management Process
Enterprise Processes Technical ProcessesProjectProcesses
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
And Project Are Created by Enterprise Management in Organisations
Project Planning Process
Project Assessment Process
Project Control Process
Decision-makingProcess
Risk ManagementProcess
Configuration Management ProcessAgreement Processes
Acquisition Process
Supply Process
Information Management Process
Enterprise Environment Management Process
Investment Management Process
System Life Cycle Management Process
Resource ManagementProcess
Quality ManagementProcess
Enterprise Processes Technical ProcessesProjectProcesses
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
And Project Execute Technical Processesto Create Products and Deliver Services
Project Planning Process
Project Assessment Process
Project Control Process
Decision-makingProcess
Risk ManagementProcess
Configuration Management ProcessAgreement Processes
Acquisition Process
Supply Process
Information Management Process
Enterprise Environment Management Process
Investment Management Process
System Life Cycle Management Process
Resource ManagementProcess
Quality ManagementProcess
Enterprise ProcessesStakeholder Requirements
Definition Process
Requirements AnalysisProcess
Architectural DesignProcess
Implementation Process
Maintenance Process
Disposal Process
Operation Process
Validation Process
Verification Process
Transition Process
Integration Process
Technical ProcessesProjectProcesses
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
System Creation
“Local” requirements & constraints
Requirementsanalysis
Requirementsanalysis
Requirementsanalysis
Architecturaldesign
Architecturaldesign
Architecturaldesign
Integratedsystem
Integratedsubsystem
Integration &verification
Integratedsubsystem
Reporting, metrics &management control
Reporting, metrics &management control
Suppliedsubsystems
“Local” requirements & constraints
“Local” requirements & constraints
Proposedcharacteristics
Verification
Verification
Derivedrequirements
Proposedcharacteristics
Derivedrequirements
Suppliedsubsystems
VerificationIntegration
Integration
Integration
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
System Creation
“Local” requirements & constraints
Stakeholderrequirements
definition
Requirementsanalysis
Requirementsanalysis
Requirementsanalysis
Architecturaldesign
Architecturaldesign
Architecturaldesign
Integratedsystem
Integratedsubsystem
Integration &verification
ValidationOperational capability
Integratedsubsystem
Reporting, metrics &management control
Reporting, metrics &management control
Suppliedsubsystems
Reporting, metrics &management control
“Local” requirements & constraints
“Local” requirements & constraints
Proposedcharacteristics
Verification
Verification
Derivedrequirements
Proposedcharacteristics
Derivedrequirements
Proposedcharacteristics
Suppliedsubsystems
Suppliedsystem
Transition
VerificationIntegration
Integration
Integration
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
System element
verification
System Creation
“Local” requirements & constraints
Stakeholderrequirements
definition
Requirementsanalysis
Requirementsanalysis
Requirementsanalysis
Architecturaldesign
Architecturaldesign
Architecturaldesign
Integratedsystem
Integratedsubsystem
System element
requirements
System element design
System element
fabrication
System Element
Integration &verification
ValidationOperational capability
Integratedsubsystem
Reporting, metrics &management control
Reporting, metrics &management control
Reporting, metrics&Management control
Suppliedsubsystems
Suppliedcomponents
Reporting, metrics &management control
“Local” requirements & constraints
“Local” requirements & constraints
“Local” requirements & constraints
Proposedcharacteristics
Verification
Verification
a1
Derivedrequirements
Proposedcharacteristics
Derivedrequirements
Proposedcharacteristics
ProposedcharacteristicsDerived
requirements
Suppliedsubsystems
Suppliedsystem
Transition
VerificationIntegration
Integration
Integration
Process Concurrency
Implementation Technologies
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Mec
hani
cal
Eng
inee
ring
Hu
ma
nF
act
ors
Ele
ctro
nic
E
ng
inee
rin
g
….
So
ftwa
reE
ngi
nee
ring
Engineering across the Organisation
ImplementationTechnologies
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Mec
hani
cal
Eng
inee
ring
Hu
ma
nF
act
ors
Ele
ctro
nic
E
ng
inee
rin
g
….
So
ftwa
reE
ngi
nee
ring
ImplementationTechnologies
Systems Engineering
Engineering across the Organisation
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold x8
SOI User
requirementsdefinition
SOIInstallation
Operational System
Proposedcharacteristics
Software element
implementation
System Elements
Deliveredcomponents
Integratedsystem
Allocatedrequirements
Proposedcharacteristics
Derivedrequirements
Proposedcharacteristics
Suppliedsubsystems
Proposedcharacteristics
IntegratedElements
Suppliedsubsystems
Engineering at an implementation -independentlevel of abstraction
Engineering at an implementation technology level
Derivedrequirements
SystemRequirement
sDefinition
SystemArchitectural
Design
SystemIntegration
SystemVerificatio
n
SOIValidation
SoftwareRequirement
sDefinition
SoftwareDetailedDesign
SoftwareIntegration
SoftwareVerificatio
n
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Business Process Profile of ISO/IEC 15288
Enterprise Processes
Project Processes
SystemTechnical Processes
Implementation Technology Processes
SystemsEngineers
ProjectManagers
BusinessManagers
SpecialistEngineers
10
7
5 1
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Characteristically Different System Element Implementation Media
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Humans and Systems
Operators
System-of-interest
operatoran individual who, or an organization that, contributes to the functionality of a system and draws on knowledge, skills and procedures to contribute the function NOTE 1 The role of operator and the role of user may be vested, simultaneously or sequentially, in the same individual or organization.NOTE 2 An individual operator combined with knowledge, skills and procedures may be considered as an element of the system.
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Operators
Operators are not stakeholders
Stakeholders
stakeholder
a party having a right, share or claim in a system or in its possession of characteristics that meet that party’s needs and expectations
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Role rather than person
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Humans and Systems
Systems in operational environment
System-of-interest
Users(& stakeholders)
Operators
userindividual who or group that benefits from a system during its utilizationNOTE The role of user and the role of operator may be vested, simultaneously or sequentially, in the same individual or organization.
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Humans and Systems
Systems in operational environment
System-of-interest
Users(& stakeholders)
Stakeholders
SocietyOperators
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
System-of-interest Interactions throughout the Life Cycle
Systems in operational environment
Enabling systems
Production system
Maintenance system
System-of-interest
Stages through the Life Cycle
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
System Life Cycle Stages
Fu
nctio
nal
Vie
ws
System Life Cycle Processes
People (in organizations) act on systems by performing common processes
throughout the life cycle
life cycle modela framework of processes and activities concerned with the life cycle, which also acts as a common reference for communication and understanding
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
A Hierarchy of Processes
Process
Process
Process
Process
Process
Stage
Life cycle
Activity
1:n
1:n
1:n
Generic
Patterns
Unique
t2-t1
large
‘instantaneous’
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Compatibility,Feasibility
Compatibility,Feasibility
Compatibility,Feasibility
Compatibility,Feasibility
Compatibility,Feasibility
Compatibility,Feasibility
Compatibility,Feasibility
Compatibility,Feasibility
Compatibility,Feasibility
Compatibility,Feasibility
Compatibility,Feasibility
Compatibility,Feasibility
Compatibility,Feasibility
Compatibility,Feasibility
Compatibility,Feasibility
Consistency,Viability
Consistency,Viability
Consistency,Viability
Consistency,Viability
Consistency,Viability
Consistency,Viability
Consistency,Viability
Consistency,Viability
Consistency,Viability
Consistency,Viability
Consistency,Viability
Consistency,Viability
Consistency,Viability
Consistency,Viability
Consistency,Viability
Needs,Concepts,Feasibility
Engineering,Solutions,Practicability
Fabrication,Assembly,Verification
Operation,Usage,Validation
Reuse,Archiving,Destruction
Installation,Maintenance,Logistics
LIFE CYCLE STAGES
OR
GA
NIZ
AT
ION
AL
FU
NC
TIO
NS
Contribute to
Personnel
CONCEIVERS
DEVELOPERS
PRODUCERS
USERS
SUPPORTERS
RETIRERS
Whole life thinking
from each contributing function
DEVELOPMENT
PRODUCTION
UTILIZATION
SUPPORT
RETIREMENT
CONCEPTION
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Compatibility,Feasibility
Compatibility,Feasibility
Compatibility,Feasibility
Compatibility,Feasibility
Compatibility,Feasibility
Compatibility,Feasibility
Compatibility,Feasibility
Compatibility,Feasibility
Compatibility,Feasibility
Compatibility,Feasibility
Compatibility,Feasibility
Compatibility,Feasibility
Compatibility,Feasibility
Compatibility,Feasibility
Compatibility,Feasibility
Consistency,Viability
Consistency,Viability
Consistency,Viability
Consistency,Viability
Consistency,Viability
Consistency,Viability
Consistency,Viability
Consistency,Viability
Consistency,Viability
Consistency,Viability
Consistency,Viability
Consistency,Viability
Consistency,Viability
Consistency,Viability
Consistency,Viability
Needs,Concepts,Feasibility
Engineering,Solutions,Practicability
Fabrication,Assembly,Verification
Operation,Usage,Validation
Reuse,Archiving,Destruction
Installation,Maintenance,Logistics
OR
GA
NIZ
AT
ION
AL
FU
NC
TIO
NS
Contribute to
Personnel
DEVELOPMENT PRODUCTION UTILIZATION SUPPORT RETIREMENT
CONCEIVERS
DEVELOPERS
PRODUCERS
USERS
SUPPORTERS
RETIRERS
CONCEPTION
Integrated Project Teams
DEVELOPMENTLIFE CYCLE
STAGE
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Compatibility,Feasibility
Compatibility,Feasibility
Compatibility,Feasibility
Compatibility,Feasibility
Compatibility,Feasibility
Compatibility,Feasibility
Compatibility,Feasibility
Compatibility,Feasibility
Compatibility,Feasibility
Compatibility,Feasibility
Compatibility,Feasibility
Compatibility,Feasibility
Compatibility,Feasibility
Compatibility,Feasibility
Compatibility,Feasibility
Consistency,Viability
Consistency,Viability
Consistency,Viability
Consistency,Viability
Consistency,Viability
Consistency,Viability
Consistency,Viability
Consistency,Viability
Consistency,Viability
Consistency,Viability
Consistency,Viability
Consistency,Viability
Consistency,Viability
Consistency,Viability
Consistency,Viability
Needs,Concepts,Feasibility
Engineering,Solutions,Practicability
Fabrication,Assembly,Verification
Operation,Usage,Validation
Reuse,Archiving,Destruction
Installation,Maintenance,Logistics
LIFE CYCLE STAGES
OR
GA
NIZ
AT
ION
AL
FU
NC
TIO
NS
Contribute to
Personnel
DEVELOPMENT PRODUCTION UTILIZATION SUPPORT RETIREMENT
CONCEIVERS
DEVELOPERS
PRODUCERS
USERS
SUPPORTERS
RETIRERS
CONCEPTION
A Matrix of Responsibilities
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
System Life Cycle Stages
15288 LIFE CYCLE
STAGES PURPOSE DECISION GATES
CONCEPT
Identify stakeholders’ needs
Explore concepts
Propose viable solutions
DEVELOPMENT
Refine system requirements
Create solution description
Build system
Verify and validate system
PRODUCTIONMass produce system
Inspect and test
UTILIZATION Operate system to satisfy users’ needs
SUPPORT Provide sustained system capability
RETIREMENT Store, archive or dispose the system
-
-
-
-
-
Execute next stage
Continue this stage
Go to previous stage
Hold project activity
Terminate project
Decision Options:
CONCEPT
UK MODSmart Acquisition
Stages
ASSESSMENT
DEMONSTRATION
MANUFACTURE
IN-SERVICE
DISPOSAL
DoD Phases5000.2
CONCEPTREFINEMENT
TECHNOLOGYDEVELOPMENT
SYSTEM
DEVELOPMENT &
DEMONSTRATIONPRODUCTION
&
DEPLOYMENT
OPERATIONS&
SUPPORT
stagea period within the life cycle of a system that relates to the state of the system description or the system itselfNOTE 1 Stages relate to major progress and achievement milestones of the system through its life cycle.NOTE 2 Stages may be overlapping.
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
System Life Cycle Stages
15288 LIFE CYCLE
STAGES PURPOSE DECISION GATES
CONCEPT
Identify stakeholders’ needs
Explore concepts
Propose viable solutions
DEVELOPMENT
Refine system requirements
Create solution description
Build system
Verify and validate system
PRODUCTIONMass produce system
Inspect and test
UTILIZATION Operate system to satisfy users’ needs
SUPPORT Provide sustained system capability
RETIREMENT Store, archive or dispose the system
-
-
-
-
-
Execute next stage
Continue this stage
Go to previous stage
Hold project activity
Terminate project
Decision Options:
CONCEPT
UK MODSmart Acquisition
Stages
ASSESSMENT
DEMONSTRATION
MANUFACTURE
IN-SERVICE
DISPOSAL
DoD Phases5000.2
CONCEPTREFINEMENT
TECHNOLOGYDEVELOPMENT
SYSTEM
DEVELOPMENT &
DEMONSTRATIONPRODUCTION
&
DEPLOYMENT
OPERATIONS&
SUPPORT
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Systemof Interest
Enabling System C
System A in Operational
Environment
System B in Operational
Environment
System C inOperational Environment
Enabling System B
Enabling System AInteraction with systems comprising the operational environment
Interactionwith enabling systems
enabling systema system that complements a system-of-interest during its life cycle stages but does not necessarily contribute directly to its function during operationNOTE 1 For example, when a system-of-interest enters the production stage, an enabling production system is required.NOTE 2 Each enabling system has a life cycle of its own. This International Standard is applicable to each enabling system when, in its own right, it is treated as a system-of-interest.
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Production Utilization Support RetirementDevelopment
System-of-Interest
NEED FOR SERVICESFROM A
SYSTEM-OF-INTEREST
NEED FOR SERVICESFROM A
SYSTEM-OF-INTEREST
SYSTEM-OF-INTERESTSERVICES TO ITSOPERATIONAL ENVIRONMENT
SYSTEM-OF-INTERESTSERVICES TO ITSOPERATIONAL ENVIRONMENT
Concept
Enabling Systems through the Life Cycle
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Production Utilization Support RetirementDevelopment
System-of-Interest
Production Utilization Support RetirementDevelopmentConcept
Concept System
The Enabling System servicesdelivered to the System-of-Interest
The System-of-Interest requirementsfor enabling services
NEED FOR SERVICESFROM A
SYSTEM-OF-INTEREST
NEED FOR SERVICESFROM A
SYSTEM-OF-INTEREST
SYSTEM-OF-INTERESTSERVICES TO ITSOPERATIONAL ENVIRONMENT
SYSTEM-OF-INTERESTSERVICES TO ITSOPERATIONAL ENVIRONMENT
Concept
Enabling Systems through the Life Cycle
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Production Utilization Support RetirementDevelopment
System-of-Interest
Production Utilization Support RetirementDevelopmentConcept
Concept System
Production Utilization Support RetirementDevelopment Concept
Development System
The Enabling System servicesdelivered to the System-of-Interest
The System-of-Interest requirementsfor enabling services
NEED FOR SERVICESFROM A
SYSTEM-OF-INTEREST
NEED FOR SERVICESFROM A
SYSTEM-OF-INTEREST
SYSTEM-OF-INTERESTSERVICES TO ITSOPERATIONAL ENVIRONMENT
SYSTEM-OF-INTERESTSERVICES TO ITSOPERATIONAL ENVIRONMENT
Concept
Enabling Systems through the Life Cycle
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Production Utilization Support RetirementDevelopment Concept
Support System
Production Utilization Support RetirementDevelopment
System-of-Interest
Production Utilization Support RetirementDevelopmentConcept
Concept System
Production Utilization Support RetirementDevelopment Concept
Development System
Production Utilization Support RetirementDevelopment Concept
Production System
Production Utilization Support RetirementDevelopment Concept
Retirement System
The Enabling System servicesdelivered to the System-of-Interest
The System-of-Interest requirementsfor enabling services
NEED FOR SERVICESFROM A
SYSTEM-OF-INTEREST
NEED FOR SERVICESFROM A
SYSTEM-OF-INTEREST
SYSTEM-OF-INTERESTSERVICES TO ITSOPERATIONAL ENVIRONMENT
SYSTEM-OF-INTERESTSERVICES TO ITSOPERATIONAL ENVIRONMENT
Concept
Enabling Systems through the Life Cycle
The Next Steps
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Processes are essential; alone, they are not sufficient
Processes are essential but not a Recipe
Competence and Capability
Processes need to be practiced
– by competent professionals
– in a compatible environment of methods and
tools
– operating within appropriate organisational
resource and responsibility structures
Business Processes
Organizational Capability Professional Competence
Business Excellence
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Standardising Systems Engineering Capability
An influence on organizations’ systems engineering policies, practices and procedures
A driver for process implementation - method, tools, resources
Basis for measurement and continuous improvement
Yardstick for performance evaluation of an organization,
Establishes a common approach for determining supplier acceptability
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
SystemsEngineering
A Simplified History of Capability Assessment
SoftwareEngineering
EIA/IS731
ISOTR15504
EIA 632
1999 ISO15288
2003
1998
1997
Systems Engineering Capability
Process for Engineering a System
System Life Cycle Processes
SW CMM
CMMI
EIA /IS632
1994
ISO15504
2002
2002
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
ISO/IEC15504 Process Assessment
A structured approach to software process assessment for use by, or on behalf of an organization, with the objective of:
– understanding the state of its own processes for process improvement;
– determining the suitability of its own processes for a particular requirement or class of
requirements;
– determining the suitability of another organization's processes for a particular contract or
class of contracts.
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Process MaturityProcesses
Capability Levels
1 - Performed Informally
4 - Quantitatively Controlled
2 - Planned and Tracked
3 - Well Defined
5 - Continuously Improving
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
ISO 18152
Stages + enabling systems
Enterprise/ project processes
Technical
processes
HS.4.1 Human resources strategy
HS.4.2 Define standard competencies and gaps
HS.4.3 Design manpower solution and delivery plan
HS.4.4 Evaluate system solutions
HS.1.1 HS issues in conceptionHS.1.2 HS issues in developmentHS.1.3 HS issues in production
and 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
Humanresources
Life cycle involvement
Human factorsintegration
ISO/IEC 15288
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Standardising Systems Engineering Competence
Encourage Proficiency and Professionalism
Establish performance criteria, permitting demonstration of competence
Imply codes of professional conduct and approach
Prescribe social responsibilities, e.g. safety, environment
Profile training and education schemes
Lead toward norms of attainment and qualification
Career development decisions
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Systems Engineering ability of an individual (or group) draws on four principal constituents
Aptitude - inherent qualities of the individual Knowledge - information gathered from others by
the individual Experience - direct personal participation by the
individual Skills - learned practical execution by the
individual
HUMANS
Systems Engineering CompetenceSystem Life Cycle
PROCESSESABILITYTo
PerformDevelop
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Systems Engineering CompetenceSystem Life Cycle
PROCESSESABILITYHUMANS SYSTEMS
METHODS
TOOLS
SKILLS
KNOWLEDGE
APTITUDE
EXPERIENCE
To Perform
To Act onDevelop
Learn
Possess
Interpreted to provide
Automate
Build up
Train to Acquire
Facilitate
Evolves
Enables
Make practical
Structure
Leverage
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Att
ainm
ent
Enterprise Processes
Project Processes
SystemTechnical
Processes
Implementation Technology Processes
Knowledge
Aptitude Experience
Skill
System Life Cycle Processes
Basic
Understanding
Competent
Advice
Professional
Guidance
Recognized
Authority
Working
Knowledge
Basic Elements of a Systems Engineering Competence Framework
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Enterprise Processes
Project Processes
SystemTechnical
Processes
Implementation Technology Processes
PMBOK/Association of Project Managers Body of Knowledge
BCS Professional Development SchemeLe
vels
of
atta
inm
ent
A Better Structure for Future Competence
IEE/INCOSEIndustry
Basic
Understanding
Competent
Advice
Professional
Guidance
Recognized
Authority
Working
Knowledge
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Individual’s development of competence profile focus, attainment levels and career progression
Att
ainm
ent
InfrastructureDevelopment
ProjectMonitoring
StakeholdersRequirementsDefinition
Human FactorsIntegration
Enterprise ProcessesProject
ProcessesSystem
Technical Processes
Implementation Technology Processes
System Life Cycle Processes
Basic
Understanding
Competent
Advice
Professional
Guidance
Recognized
Authority
Working
Knowledge
SystemInstallation
Profilefocus
Attainmentlevel
Career direction
FINSE, Finish Chapter of INCOSE, 26th May 2005, Helsinki, S.Arnold
Thank You& Questions
Stuart ArnoldQinetiQFort HalsteadSevenoaksKent TN14 7BP
+44 1959 514961+44 7770 [email protected]