INCOSE Delegate Report FEAPO Plenary: November 2015 Presented by Richard Martin.

INCOSE Delegate ReportFEAPO Plenary: November 2015

Presented by Richard Martin

About INCOSE – International Council on System Engineering• The International Council on Systems Engineering (INCOSE) is a not-for-profit membership

organization founded to develop and disseminate the interdisciplinary principles and practices that enable the realization of successful systems.

Mission

• Share, promote and advance the best of systems engineering from across the globe for the benefit of humanity and the planet.

Vision

• The world's authority on Systems Engineering.Goals

• To provide a focal point for dissemination of systems engineering knowledge.

• To promote international collaboration in systems engineering practice, education, and research.

• To assure the establishment of competitive, scale-able professional standards in the practice of systems engineering.

• To improve the professional status of all persons engaged in the practice of systems engineering.

• To encourage governmental and industrial support for research and educational programs that will improve the systems engineering process and its practice.

November 2015

The Body of Knowledge and Curriculum to Advance Systems Engineering (BKCASE)• Project includes two closely related products

• Guide to the Systems Engineering Body of Knowledge A living, authoritative guide to the knowledge most relevant and important to the advancement of systems engineering. SEBoK discusses what is included in the discipline, how this knowledge can be structured to facilitate understanding, and what documents are most important to the discipline.

• Graduate Reference Curriculum for Systems Engineering Curriculum guidance for systems engineering master’s program, GRCSE makes reference to sections of the SEBoK to define its core knowledge and suggests broader program outcomes and objectives that reflect aspects of the professional practice of systems engineering as discussed across the SEBoK.

These products are available at www.bkcase.org.

November 2015

http://www.bkcase.org/

http://www.bkcase.org/faq/sebok-sub/

http://www.bkcase.org/faq/grcse-sub/

Certifications for System Engineering• Knowledge examination and experience based• Program began in 2004• Three levels of certification

• ASEP – Examination of knowledge based upon INCOSE SE Handbook content• CSEP - Examination of knowledge based upon INCOSE SE Handbook content, 5

years experience working as SE, technical degree• ESEP – Review of contribution to field of SE, 25 years experience working as

SE, technical degree, 5 years of professional development credit

• About 1,000 of 10,000 members are now certified as ASEP, CSEP or ESEP

(INCOSE SE Handbook aligns with ISO 15288)

November 2015

Educational programs• Annual International Symposium

• Rotates between US, Europe, and Asia• Presentation sessions, panel discussions, tutorials, networking

• Chapters around the world• Meet regularly, some every month• Presentations, discussions, networking

• Monthly webinars on topics of interest – usually new approaches• Website library of past presentations and INCOSE work products• Annual International Workshop

• Working Group meetings• Business meetings

• Monthly INSIGHT news letter and quarterly Systems Engineering JournalNovember 2015

Conceptual modeling for system engineering• V-model and Dual V-model• N2 and Design Structure Matrix• Interpretive Structural Modeling - Warfield• Soft-systems Methodology - Checkland• SysML – OMG• Object-Process Methodology – Dori• ISO 15288 Systems and software engineering – System life cycle processes• ISO/IEC/IEEE 42010 Systems and software engineering – Architecture

description

November 2015

Dual-V Model

November 2015 7

Slide 1 - 11©2005 CSM

Dual Vee Model

S o l u t i o n R e a l i z a t i o n

U s e r a n dS t a k e h o l d e r

R e q u i r e m e n t s



E n t i t yR e q u i r e m e n t s


C o n c e p t &A r c h i t e c t u r e

S e l e c t i o n a n dD e s i g n - t o

S p e c i f i c a t i o n




B u y ,B u i l d ,C o d e


V e r i f i c a t i o n -I n s p e c t i o n


V e r i f i c a t i o n – T e s t ,D e m o n s t r a t i o n ,

A n a l y s i s


A n a l y s i s

V a l i d a t i o nP r e p a r a t i o nV a l i d a t i o n

P r e p a r a t i o n

V a l i d a t i o nV a l i d a t i o n

B u i l d - t oa n d

C o d e - t oA r t i f a c t s





















A n a l y s i s


A n a l y s i s

V a l i d a t i o nP r e p a r a t i o n

























A n a l y s i s


A n a l y s i s


























A n a l y s i s


A n a l y s i s

V a l i d a t i o nP r e p a r a t i o nV a l i d a t i o n

P r e p a r a t i o n
























A n a l y s i s


A n a l y s i s


























A n a l y s i s


A n a l y s i s


























A n a l y s i s


A n a l y s i s








Depicts architecture baseline evolution. Vertical dimension is architecture decomposition. Horizontal dimension is system realization. Third and normal dimension is quantity of entities and their interfaces.

Architecture Vee for architecture management

Depicts entity baseline elaboration. Vertical dimension is entity detail.Horizontal dimension is entity realization.

Entity Veefor entity management

System RealizationSystem Realization

Arch

itectu

re D

eco

mpositio

n

& D

efinitio

n

Arch

itectu

re D

eco

mpositio

n

& D

efinitio

n

Arc

hit

ect

ure

Inte

gra

tion &

Veri

fica

tion

Arc

hit

ect

ure

Inte

gra

tion &

Veri

fica

tion

SystemDevelopment

SystemDevelopment

SubsystemRealizationSubsystemRealizationSubsystemRealizationSubsystemRealization

SystemRealization

SystemRealization

SystemRealization

SystemRealization

LCILowest

Configuration Item Development

LCILowest

Configuration Item Development

SubsystemDevelopment Subsystem

Development Subsystem

Development Subsystem

Development

LCILowest

Configuration Item Realization

LCILowest

Configuration Item Realization

The vertical dimension of the Architecture Vee is decomposition into levels of architecture entities which is based on the Product Breakdown Structure. Only three of the INCOSE seven levels of decomposition are illustrated.

The vertical dimension of the Entity Vee is extent of elaboration detail at the decomposition level of interest such as Subsystem or Lowest Configuration Item. The elaboration includes the baselines of concept, architecture, design-to, build-to, code-to, as-built, etc.

FEAPO Plenary

Managing Resource to Create Enterprise Value

November 2015 8FEAPO Plenary

3 Kinds of Enterprise Capability

November 2015 FEAPO Plenary 9


Anti-terrorism WG Charter• Purpose

– Demonstrate that systems engineering principles, techniques, and practices can offer a path to policy and technical solutions that reduce and mitigate the consequences of terrorism and natural disaster events.

• Goal– Create INCOSE-wide product(s), which apply systems engineering principles,

techniques, and practices to recommend policy and technical solutions that reduce and mitigate the consequences of terrorism and natural disaster events.

• Scope– Solutions, tools, analysis to support public policy decisions, discussion forums

(e.g., panels) through volunteers within and without INCOSE

• Planned work– Develop a proposal for a book chapter on applying systems engineering to public

policy surrounding the threat to cyber-dependent infrastructure– Develop a student challenge problem that uses SE to establish understanding of

complex systems

11November 2015 FEAPO Plenary

• Purpose• Expand the practice of Architecture in Systems Engineering and advance the body

of knowledge …

• Goals• Advance and evolve the architecture body of knowledge.• Promote the use and practice of architecture principles.• Develop and share best practices for the use of architecture.• Engage in architecture related standards and specifications.

• Scope• The domain of Systems and Systems of Systems (SoS) Architecture as it relates to

Systems Engineering and (SoS) Engineering.

• Planned work• Continued collaboration with FEAPO, SEBoK• Define a framework for architect competencies

IW: International Workshop AWG: Architecture Working Group 12

Architecture WG Charter

November 2015 FEAPO Plenary

SysSciWG – IFSR: Systems Praxis Framework


ISO/WD1 42020 Architecture processes


Architecting information flow


ISO/IEC/CD 42030 Architecture evaluation


Complex Systems WG Charter• We operate at enlarging the intersection of Complex Systems Science and Systems

Engineering, focusing on knowledge that is not addressed in current systems engineering documentation such as standards, handbooks, and textbooks. Applicable sciences include chaos, complexity, complex adaptive systems, nonlinear dynamics, network/graph theory, social science, neuroscience, evolutionary biology, ecology, and others.

• We will develop useful products that will help INCOSE members and their organizations perform systems engineering better, based on knowledge from these sciences.

• Although analysis is important, the goal is to make a difference in synthesis (creation of new systems) as well.

Planned work• Expand on Mat French MBSE in Complexity Contexts work begun in 2014• Expand on selected Primer topics; evolve into wiki to facilitate evolution and access;

develop annotated complexity bibliography• Begin development of a Maturity Model for the Complex SE capability of an organization or

endeavor


Decision Analysis WG Charter

• Purpose– Advance the state of the practices, education and theory of Decision Analysis

and its relationship to other systems engineering disciplines.

• Goal– Expand and promote the body of knowledge of Decision Analysis and its benefits

within the Systems Engineering community.

• Scope– This technical working group will cover activities that are generically applicable to

current and future Decision Analysis practices thru the product development and project life cycle for any and all domains and industries.

• Planned work– Write Book to address top 5 CAB need on making effective trade studies.– Author Tutorial on Decision Analysis and Trade Studies


19

Model-Based Conceptual Design Working Group

http://www.incose.org/about/organization/pdf/MBCE_WG_Charter.pdf http://www.sesa.org.au/model-based-conceptual-design-working-group

MBCD WG Vision – Develop best practice for model-based conceptual designMBCD WG Mission

• Enhance the practise of problem definition and identifying capability needs • Develop modelling practise in support of Exploratory Research and

Concept Stage•Planned work -

SETE2015 Plenary/WorkshopMBSE Symposium/Workshop @ ASEW 2015Workshop at the INCOSE IS2015

• Pain Points Survey Team • MBCD Case Study / Best Practice Guide Team• Return On Investment (ROI) for MBCD – Identify a research question and

look to sponsor a PhD investigation


http://www.incose.org/about/organization/pdf/MBCE_WG_Charter.pdf

http://www.sesa.org.au/model-based-conceptual-design-working-group

20

MBSE Patterns Challenge Team

• S*Patterns are re-usable, configurable, S*Models.• S*Models are MBSE models satisfying the S*Metamodel.• S*Metamodel: The smallest set of elements necessary for system life cycle purposes of

engineering and science (ISO 15288 or otherwise).• Modeling language independent: use SysML, IDEF, or your personal favorite language

—but cover the S*Metamodel elements.• Tools independent: mapped to multiple third party COTS modeling tools, PLM systems,

and databases.• Planned work

Agile Systems Engineering Life Cycle Pattern (Joint with Agile WG)SE Community Social Network PatternINCOSE Summary of PBSE MethodologyThe Case for a Stronger Foundation Metamodel for MBSE: Part 3

Metamodel forModel-Based Systems Engineering (MBSE)

Pattern Hierarchy for Pattern-Based Systems

Engineering (PBSE)

Pattern Class Hierarchy

Individual Product or System Configurations

Product Lines orSystem Families

General System Pattern

State

Input/Output

Interface

Functional Interaction

(Interaction)System

System of Access

attribute

Technical Requirement

Statement

Stakeholder Feature

attribute

Design Component

attribute

(physical system)

(logical system)

FunctionalRole

attribute

“A” Matrix Couplings

“B” MatrixCouplings

StakeholderWorld

Language

High LevelRequirements

TechnicalWorld

Language

attribute

Design Constraint Statement

attribute

StakeholderRequirement

Statement

BB

WBDetail Level

Requirements

High LevelDesign

Pattern-Based Systems Engineering (PBSE)

Processes

Pattern Management Process

Pattern Configuration Process

(Projects, Applications)

Pattern

s

Learn

ings

Configure,Specialize

Pattern

Improve Pattern

S*Metamodel Summary


Product Line Engineering WG Charter

• Purpose– To promote PLE and related SE best practices

• Coordinate activities around PLE at INCOSE level and share results

• Goals– Help our members acquire Know‐How

• Compare to the State‐of‐Art• Share concerns, experiences, good practices and traps to avoid

– Provide guidelines to setup and evolve PLE in organizations

• Scope– All types of Systems, Markets & Organizations– All the SE Processes (needs, requirements, architecture, integration and tests …)– All maturity levels of PLE, from opportunistic to completely Integrated and anticipated strategies

• Planned work– Guideline on “Model-Based Product Line Systems Engineering”– PLE meta-model or ontology– Building product lines from legacy assets (research)– Extended work on ISO2655x standards for a bigger impact


Risk Management WG Charter• Purpose

Advance knowledge, common understanding, and quality of practice of risk and opportunity management in the systems engineering community worldwide. Our mission is to develop value-added technical products and participative activities which help INCOSE members effectively and efficiently implement risk & opportunity mgmt.

• GoalProvide a forum for INCOSE risk management practitioners to present research and analysis results, discuss problems , and put forth improvement ideas.

• ScopeRisk and Opportunity Management process, methods and tools as they relate to Risk Management within the context of Systems Engineering (SE) throughout the life-cycle. NOTE: This framing definition excludes Opportunity Management that would apply to business enterprise or service activities pursued outside the context of Risk Management, and Risk and Opportunity Management outside the context of Systems Engineering (SE).

• Planned work• Support update of ISO/IEC 16085, Systems and software engineering – Life cycle processes – Risk

management• Consider the opportunity to support the development and management of risk management related

parts of the INCOSE SEBoK (evaluate capability to support)• Continue liaison work with the Healthcare WG and the Biomed MBSE Team regarding Safety

Assurance Cases and Risk Mgmt., including conference activities and publications.


SEQual Project CharterWG Purpose: Zero-fault systems. The SEQual Project intends to foster and foment ethos and action toward Zero-Fault systems thereby revitalizing the aspect of system engineering that ensures operational system fitness for purpose.

WG Goals: 1)Foster and foment a Fault-free ethos throughout the INCOSE membership and their beneficiaries.

2)Show how to achieve system operational availability in deployed systems equivalent to that demonstrated in Acceptance Tests.

3)Disband when exemplary operational systems are the norm rather than the current experience of ‘less than 50% of those attempted.’

WG Scope:

Compressing SE cycle times to 1/3 current practice despite system problematique increasing in Extent, Variety and Ambiguity; Including autonomous systems for non-deterministic problem situations while handling increasing kinds and quantity of threats from cyberspace. Understanding and applying new technologies that enable a order of magnitude leap in a system’s ownership value throughout its life cycle.

Planned work:• Examine Fit For Purpose Assessment provisions in Standards, Handbooks, Guides, Guide to SEBoK and in

the foci and products of INCOSE initiatives and WG’s.• Produce ConOps for “Fault detection and removal from Day 2 of a system project through Year N of a system

useful life.”


Very Small Entities WG Charter• Purpose

• Systems Engineering concepts have been adopted and adapted by most industries in various domains (Aeronautics, Defense, Space, Transportation, Telecom, Information Systems, Bio Medical…) for development of product and services.

• In the context of very small and micro enterprises and small projects (VSEs), these concepts can be used or tailored to improve:

• Product development efficiency (including costs and delays)• Product Quality

• Goal• To improve and make product development within VSEs more efficient by using Systems Engineering

and Systems Thinking concepts• Elaborate tailored guidance to apply, in the context of either a prime or subcontractor role to small

projects• To contribute to standardization in the context of Systems Engineering and Systems Thinking

• Planned work• SEBoK – Develop and coordinate SEBoK content• Develop VSE Use Cases• Review Project Manager’s Guide to SE Measurement for Project Success


INCOSE Delegate Report FEAPO Plenary: November 2015 Presented by Richard Martin.

Documents

systems engineering

systems engineering

best of systems engineering

systems engineering

core knowledge

esep incose se handbook

field of se

international collaboration