common language for systems practitioners: why not!?
DESCRIPTION
Common Language for Systems Practitioners: Why not!?. Panel Moderator: Hillary Sillitto. Panel Agenda and Cast. Hillary Sillitto, THALES, UK Setting the stage frame the problem with Jack Ring’s slides Janet Singer, ISSS Systems Praxis Framework; James Martin, Aerospace Corp, USA - PowerPoint PPT PresentationTRANSCRIPT
![Page 1: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/1.jpg)
Common Language for Systems Practitioners: Why not!?
Panel Moderator:Hillary Sillitto
23rd Annual INCOSE International Symposium - Philadelphia, PA – 24-27 June, 2013
![Page 2: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/2.jpg)
Panel Agenda and Cast•Hillary Sillitto, THALES, UK
Setting the stage frame the problem with Jack Ring’s slides •Janet Singer, ISSS
Systems Praxis Framework; •James Martin, Aerospace Corp, USA
Four universal thought patterns – this is all you need!•Bud Lawson, Lawson Konsult, Sweden
We need multiple paradigms, not just a “language” based upon a sterile ontology•Duane Hybertson, MITRE, USA
Understand what is common and what is different – “models, patterns and views”•Richard Martin, Tinwisle Corp, USA
As the problem space scales up, an increasing emphasis upon praxis derived from system sciences is needed to provide sufficient capability to effectively interoperate
•Joe Kasser, National University of SingaporeGet real, panelists – this is a waste of time and effort! Lessons learned from similar projects indicate that this effort will be about as effective as flogging a dead horse to get it to pull a cart.
•Janet Singer, ISSSInitial considerations – shared models to bridge multiple incommensurable worldviews
23rd Annual INCOSE International Symposium - Philadelphia, PA – 24-27 June, 2013
![Page 3: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/3.jpg)
Panel Agenda•Setting the context
•Debate
•Q&A
•CONCLUSIONS
23rd Annual INCOSE International Symposium - Philadelphia, PA – 24-27 June, 2013
![Page 4: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/4.jpg)
Panel GoalsDiscuss the following dilemmas:
– the scope of “systems practice” is not agreed upon or even obvious– the many systems communities are “divided by a common
language”: same words --- different concepts
Present the “systems praxis framework” (SPF): a contribution to unificationExpand the community that can benefit from this work and
take it forward.
NOTE: a paper on the Common Language for Systems Praxis project will be presented tomorrow: 10.00, Systems Thinking track
23rd Annual INCOSE International Symposium - Philadelphia, PA – 24-27 June, 2013
![Page 5: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/5.jpg)
The chairman’s challenge
• (SPF): correct field of discourse?
• motivation to communicate > motivation to obfuscate?
• Is it feasible and useful to agree a finite set of terms to describe an infinitely complex set of subjects and situations?
23rd Annual INCOSE International Symposium - Philadelphia, PA – 24-27 June, 2013
![Page 6: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/6.jpg)
Common Language(s) for Systems
Practitioners: Why not?
Jack RingIS2013 Panelist in absentia
Fellow, INCOSEJune 24, 2013
![Page 7: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/7.jpg)
Why Bother?
2) Market Demand
Extent , Variety , Ambiguity
1) SE Capacity
Baby Boomers
3) 10X higher - level unified SE language - diversity of participants
4) # participants < Starkermann limit 5) Persistent system integrity
assessment.
6) Else – System of Systems?
NOW is the time.
![Page 8: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/8.jpg)
Praxis Framework
• Rationalizes 15288, SEH, SEBoK
• Does not express a praxis• Does not unify language(s)• Good start
![Page 9: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/9.jpg)
Language(s)• Devised or adopted to express outcomes of thinking: i.e., linear,
relational, lateral, Janusian, Hegelian, quantum, etc.• Devised or adopted to convey presence of emotions.• Convey the dynamics of emergence.• Examples: music, kinesics, natural (> 173), algebra, plots, directed
graphs, video, pheromones.• Necessary, sufficient and efficient in Knowledge Exchange and Choice-
making across human activity systems that initialize User systems: .
Common Unified 4 factor schema, e.g., 50 kinds of process ≈ 200 item formal ontology
![Page 10: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/10.jpg)
Quo Vadis?PRAXIS
System Engineering In Action
Multi-levelMeta-model
Continuously co-evolving knowledge exchange and choice-making
Execution Engine
![Page 11: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/11.jpg)
The Systems Praxis FrameworkThe outcome of the collaboration that started at
the Linz “Conversation”. Aims to: (1) map out the whole universe of discourse of systems
practice, systems thinking and systems science; (2) show how theory could support practice and how
practice can improve theory; (3) provide a properly grounded basis for a unifying set
of concepts; (4) enable development of a common language for the
systems community.
23rd Annual INCOSE International Symposium - Philadelphia, PA – 24-27 June, 2013
![Page 12: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/12.jpg)
JANET SINGER INTERNATIONAL SOCIETY FOR THE SYSTEMS SCIENCES
![Page 13: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/13.jpg)
23rd Annual INCOSE International Symposium - Philadelphia, PA – 24-27 June, 2013
![Page 14: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/14.jpg)
23rd Annual INCOSE International Symposium - Philadelphia, PA – 24-27 June, 2013
![Page 15: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/15.jpg)
23rd Annual INCOSE International Symposium - Philadelphia, PA – 24-27 June, 2013
![Page 16: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/16.jpg)
23rd Annual INCOSE International Symposium - Philadelphia, PA – 24-27 June, 2013
![Page 17: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/17.jpg)
23rd Annual INCOSE International Symposium - Philadelphia, PA – 24-27 June, 2013
![Page 18: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/18.jpg)
JAMES MARTINAEROSPACE CORPORATION, USA
23rd Annual INCOSE International Symposium - Philadelphia, PA – 24-27 June, 2013
![Page 19: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/19.jpg)
Information Transfer
23rd Annual INCOSE International Symposium - Philadelphia, PA – 24-27 June, 2013
Signs (eg, Words &
Symbols)
Signs (eg, Words &
Symbols)
Concepts Concepts
Unified Glossary of Terms
?
![Page 20: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/20.jpg)
Unification through Frameworks
23rd Annual INCOSE International Symposium - Philadelphia, PA – 24-27 June, 2013
Signs (eg, Words &
Symbols)
Concepts
Signs (eg, Words &
Symbols)
Concepts
Conceptual Frameworks
![Page 21: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/21.jpg)
Conceptual Frameworks (i.e. Universal Thought Patterns)
• Better than a Universal “Language”…– PICARD Theory
– 7 Samurai Framework
– PMTE Paradigm
– Knowledge Pyramid
23rd Annual INCOSE International Symposium - Philadelphia, PA – 24-27 June, 2013
![Page 22: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/22.jpg)
PICARD Theory of Systems
Parts InteractionsContextActionsRelationshipsDestiny
Holistic Image ofSystem =
From the Point of View of an Observer
![Page 23: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/23.jpg)
Context System (S1)
Realization System (S3)
Intervention System (S2)
Competing System (S7)
Modified Context System (S1’)
Deployed System (S4)
Sustainment System (S6)
Problem (P1)
Problem (P2)
may cause
Collaborating System (S5)
collaborates with
intended to address
becomes
may address
competes with
becomes
sustains
may need to develop or
modify
needs to understand
needs to understand
The 7 Samurai
![Page 24: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/24.jpg)
PMTE Paradigm
PROCESS
METHODS
TOOLS
ENVIRONMENT
supported by
supported by
supported by
support
support
supports
![Page 25: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/25.jpg)
Signals
Data …1001010011…
Information Meanings & Messages
Knowledge Beliefs & Convictions
The Knowledge Pyramid
Wisdom Ideals & Insights
![Page 26: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/26.jpg)
BUD LAWSONLAWSON KONSULT, SWEDEN
23rd Annual INCOSE International Symposium - Philadelphia, PA – 24-27 June, 2013
![Page 27: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/27.jpg)
23rd Annual INCOSE International Symposium - Philadelphia, PA – 24-27 June, 2013
Paradigms to UnifyThinking and Acting in Terms of Systems• ”a scientific revolution is defined by the appearance of new
conceptual schemes or “paradigms.” These bring to the fore aspects which previously were not seen or perceived, or even suppressed in “normal” science, i.e., science generally accepted and practiced at the time.” – T.S. Kuhn -1962
• “personal mastery, mental models, shared vision and team learning based upon systems thinking that are routes to improvement.” – Peter Senge – 1990
• “A Journey Through the Systems Landscape” provides paradigms in the form of models that can be and have been shared to improve thinking and acting.
![Page 28: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/28.jpg)
23rd Annual INCOSE International Symposium - Philadelphia, PA – 24-27 June, 2013
System Coupling Diagram
• A collectively guided, disciplined inquiry • exploring issues of social significance,• engaged by scholarly practitioners in self-organized teams,• who select a theme for their conversation,• initiated in the course of a preparation phase,• that leads to an intensive learning phase. • (Banathy, 1997)
![Page 29: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/29.jpg)
23rd Annual INCOSE International Symposium - Philadelphia, PA – 24-27 June, 2013
OODA – PDCA –Foundation of Change
• A collectively guided, disciplined inquiry • exploring issues of social significance,• engaged by scholarly practitioners in self-organized teams,• who select a theme for their conversation,• initiated in the course of a preparation phase,• that leads to an intensive learning phase. • (Banathy, 1997)
![Page 30: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/30.jpg)
23rd Annual INCOSE International Symposium - Philadelphia, PA – 24-27 June, 2013
Generic Life Cycle Transformations
• A collectively guided, disciplined inquiry • exploring issues of social significance,• engaged by scholarly practitioners in self-organized teams,• who select a theme for their conversation,• initiated in the course of a preparation phase,• that leads to an intensive learning phase. • (Banathy, 1997)
![Page 31: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/31.jpg)
23rd Annual INCOSE International Symposium - Philadelphia, PA – 24-27 June, 2013
Common Data/Information Structure
Life Cycle of x
Defintion
User Needs
Stakeholder
Requirments
Validation
Requirments
SpecificationsVerification
Requirements
Architecural
Design
Viewpoint Models
Views
Production
Implementation Suppliers
Integration Configurations
Utilization
Transition Training
Operation Log
Maintenance
Trouble Reports
Preventive Maintenance
Retirement Disposal
Disassembly
Lessons Learned
![Page 32: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/32.jpg)
DUANE HYBERTSON, MITRE
23rd Annual INCOSE International Symposium - Philadelphia, PA – 24-27 June, 2013
![Page 33: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/33.jpg)
Basic Position (Duane Hybertson, MITRE)
Is language unification possible in the systems community?• If unification = a common language: No.
– Systems praxis is fundamentally multi-language and multi-discipline
• If unification = shared understanding of systems: ~Yes.– A substantial degree of shared understanding about systems
can be achieved across the entire systems community, which is useful to the systems approaches to practice such as SE, and is based on foundations, theories, and representations of integrative systems science.
23rd Annual INCOSE International Symposium - Philadelphia, PA – 24-27 June, 2013
![Page 34: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/34.jpg)
How to work toward shared understanding?
• What are the most useful aspects to understand?– Characteristics of processes of systems praxis? (e.g.,
steps to engineer a new system, or to conduct integrative systems science)
– Characteristics of systems? (e.g., system categories, types, properties, performance, reliability, structure, behavior, functions)
• Based on examination of other disciplines, it is more useful to understand characteristics of systems than processes of systems praxis
23rd Annual INCOSE International Symposium - Philadelphia, PA – 24-27 June, 2013
![Page 35: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/35.jpg)
How to share understanding of systems?
• Focus on what is common among systems, and distinguish what varies across systems– Integrative Systems Science helps identify what is
common, and dimensions or factors of variability– Commonality can be observed at the level of all
systems, and within identified categories of systems• How do we express and share commonality and
variability?– System models, patterns, views: Discovered and
formulated by Integrative SS, applied/tailored by SE
23rd Annual INCOSE International Symposium - Philadelphia, PA – 24-27 June, 2013
![Page 36: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/36.jpg)
Example: System Composition Hierarchy
• IEEE 1220 focuses on differences at each composition level• Holarchy model focuses on similarities across all levels• SE needs combination of both
23rd Annual INCOSE International Symposium - Philadelphia, PA – 24-27 June, 2013
![Page 37: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/37.jpg)
RICHARD MARTIN TINWISLE CORPORATION
23rd Annual INCOSE International Symposium - Philadelphia, PA – 24-27 June, 2013
![Page 38: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/38.jpg)
a SYSTEM for everyone
23rd Annual INCOSE International Symposium - Philadelphia, PA – 24-27 June, 2013
synset links from WordNet Search 3.1
Princeton University "About WordNet." WordNet. Princeton University. 2010. <http://wordnet.princeton.edu>
physical entity
object relation
state
attribute
part of
unitsituation
environment
abstract entity
entity
context
discourse
system
matter
group
part
artifact
regularity
thing
whole
bodypart
naturalobject
instrumentation
body
livebody
quality cognition(noesis)
orderliness
ability
structure
know-how
psychologicalfeature
methodplan
idea
content
location
region
geographicarea
environment
![Page 39: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/39.jpg)
SS SYSTEM for many
23rd Annual INCOSE International Symposium - Philadelphia, PA – 24-27 June, 2013
synset links from WordNet Search 3.1
Princeton University "About WordNet." WordNet. Princeton University. 2010. <http://wordnet.princeton.edu>
physical entity
object relation
state
attribute
part of
unitsituation
environment
abstract entity
entity
context
discourse
system
matter
group
part
artifact
regularity
thing
whole
bodypart
naturalobject
instrumentation
body
livebody
quality cognition(noesis)
orderliness
ability
structure
know-how
psychologicalfeature
methodplan
idea
content
location
region
geographicarea
environment
![Page 40: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/40.jpg)
SE SYSTEM for many
23rd Annual INCOSE International Symposium - Philadelphia, PA – 24-27 June, 2013
synset links from WordNet Search 3.1
Princeton University "About WordNet." WordNet. Princeton University. 2010. <http://wordnet.princeton.edu>
physical entity
object relation
state
attribute
part of
unitsituation
environment
abstract entity
entity
context
discourse
system
matter
group
part
artifact
regularity
thing
whole
bodypart
naturalobject
instrumentation
body
livebody
quality cognition(noesis)
orderliness
ability
structure
know-how
psychologicalfeature
methodplan
idea
content
location
region
geographicarea
environment
![Page 41: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/41.jpg)
SE SYSTEM for everyone
23rd Annual INCOSE International Symposium - Philadelphia, PA – 24-27 June, 2013
synset links from WordNet Search 3.1
Princeton University "About WordNet." WordNet. Princeton University. 2010. <http://wordnet.princeton.edu>
physical entity
object relation
state
attribute
part of
unitsituation
environment
abstract entity
entity
context
discourse
system
matter
group
part
artifact
regularity
thing
whole
bodypart
naturalobject
instrumentation
body
livebody
quality cognition(noesis)
orderliness
ability
structure
know-how
psychologicalfeature
methodplan
idea
content
location
region
geographicarea
environment
![Page 42: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/42.jpg)
SS SYSTEM for everyone
23rd Annual INCOSE International Symposium - Philadelphia, PA – 24-27 June, 2013
synset links from WordNet Search 3.1
Princeton University "About WordNet." WordNet. Princeton University. 2010. <http://wordnet.princeton.edu>
physical entity
object relation
state
attribute
part of
unitsituation
environment
abstract entity
entity
context
discourse
system
matter
group
part
artifact
regularity
thing
whole
bodypart
naturalobject
instrumentation
body
livebody
quality cognition(noesis)
orderliness
ability
structure
know-how
psychologicalfeature
methodplan
idea
content
location
region
geographicarea
environment
![Page 43: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/43.jpg)
Interoperation mechanisms
23rd Annual INCOSE International Symposium - Philadelphia, PA – 24-27 June, 2013
Integration – common model for information exchange• Formally correct by construction• Established protocols, e.g. STEP, IEEE 802.x• Same syntax and semantics for each party• Strict controls and model adherence in implementation – i’s dotted, t’s
crossed, commas, quotes and brackets correctly placed Unification – common meta-model (language)
• Reference for mapping existing model syntax and semantics• Depends upon notions of semantic equivalence• Often use heuristics rather than formality• Information loss resulting from different extensions or instantiations
Federation – no common model or meta-model• Different terminology and methodology• Use a priori knowledge and negotiating agents• Inconsistencies resolved by manual intervention• Business as usual – try it, break it, fix it
![Page 44: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/44.jpg)
Scaling up interoperation
23rd Annual INCOSE International Symposium - Philadelphia, PA – 24-27 June, 2013
simple complicated complexproblematic situation
federation
unification
integration
inte
rope
ratio
n ap
proa
ch
Common model &
terms
Common meta-model - mapping of syntax & semantics
Little in common a priori -agent discovery, manual intervention, error prone
limit of integration
limit of unification
limit of ??
![Page 45: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/45.jpg)
Scaling up interoperation
23rd Annual INCOSE International Symposium - Philadelphia, PA – 24-27 June, 2013
simple complicated complexproblematic situation
federation
unification
integration
inte
rope
ratio
n ap
proa
ch
Common model &
terms
Common meta-model - mapping of syntax & semantics
Little in common a priori -agent discovery, manual intervention, error prone
![Page 46: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/46.jpg)
Standardization, no way!Are you sure?
Joseph KasserNational University of Singapore
![Page 47: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/47.jpg)
Problem-solving: Temporal perspective
Undesirable situation (t0)
Future conceptual feasible desirable
situation (t0)
Problem
Remedial action
(problem solving)
SolutionActual situation
(t1)
Still undesirable?
No
Yes or partial
End
Undesirable situation (t2)
5-47
![Page 48: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/48.jpg)
Situation
• Undesirable situation– Terminology exists but is ignored– New terms invented for almost identical
existing terms• Humpty Dumpty
– Partitioning is different in different publications• Desirable situation
– A common language using well defined terms
![Page 49: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/49.jpg)
The Hitchins-Kasser-Massie Framework (HKMF) for understanding systems
engineering*
* Kasser and Massie, 2001
![Page 50: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/50.jpg)
Implementation strategy
• Who has similar problems of defining new words– Hebrew, French, etc.– IEEE-610 software standard for terminology
• Solution– Build on Systems Engineering Glossary
project (SECOE) at UniSA – Create INCOSE Terminology of Systems
Engineering Rationalization working group
![Page 51: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/51.jpg)
Problem classification matrix*
ComplexWicked
Here be dragons(there are no solutions)Ill-structured
Well-structured Simple Complicated
Easy Medium Ugly HardNon-complex Level of difficulty
Learning and experience * Kasser J.E. , Complex solutions for complex problems, Third International Engineering Systems Symposium (CESUN), Delft, Holland, 2012
5-51
![Page 52: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/52.jpg)
Problem solving methodologies
• Many in the literature• Which one to use?• Flood and Jackson suggested TSI• Going beyond systems thinking to holistic
thinking– Developing a methodology for selecting
problem solving methodologies based on HKMF
![Page 53: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/53.jpg)
Implementation• Create dictionary (ISO/INCOSE 2014-04-01) by
IW 2014– Select meanings from standards– Post in INCOSE public web site for wide access
• Negotiate agreement with non-native English language organizations to comply with dictionary as of IS 2014
• Submissions to Systems Engineering Journal, Insight, IS and all INCOSE web sites will be required to comply with dictionary as of IS 2015
![Page 54: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/54.jpg)
JANET SINGER INTERNATIONAL SOCIETY FOR THE SYSTEMS SCIENCES
![Page 55: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/55.jpg)
Language unification cannot be achieved from within any one systems worldview:
• there are fundamental incommensurabilities that mean one cannot “get to” elements of one from another.
• collapsing dimensions to achieve commonality – yields a degenerate or trivial result, – does not do justice to the depth and breadth of concerns present
in the incommensurable originals.
This is why previous language unification efforts have not been successful.
23rd Annual INCOSE International Symposium - Philadelphia, PA – 24-27 June, 2013
![Page 56: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/56.jpg)
Technologies
Enterprise processes
Institutions and cultural
norms
Self-interested
agenttransactions
How many aspects of complex socio-technical systems?
Organizationaldynamics Hermeneutics
and sense-making
Population dynamics
Resourceflows, etc., …
INCOMMENSURABILITIES
![Page 57: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/57.jpg)
Shared models are keyThe use of language within pragmatic systems modeling
activities is the common context the actors share, • no matter which systems communities are present.Standardization of the entire systems praxis context • may seem like the “great circle route” to understanding
the features of systems models and systems language• but it is an approach that will eventually pay offSimplifications and partial solutions will continue to fail.
23rd Annual INCOSE International Symposium - Philadelphia, PA – 24-27 June, 2013
![Page 58: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/58.jpg)
Example:
Integrate models for anti-pandemic system design – not necessarily commensurable!
H. Deguchi, 2010
![Page 59: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/59.jpg)
Integrating social science models?
“Social science commensurability gaps
are becomingmore serious
for drawingour intellectual map
for the global society.”Prof. H. Deguchi, 2010
Tokyo Institute of TechnologyDirector of Center for Agent Based
Social Systems Sciences)
![Page 60: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/60.jpg)
If it is possible, it is inevitable?
Need a pragmatic meta-perspective that appreciates both • what the various systems worldviews have in common • the full scope of what is unique to each.
If common language approached from a pragmatic meta-perspective is possible
• it is only a matter of time before it will occur!
23rd Annual INCOSE International Symposium - Philadelphia, PA – 24-27 June, 2013
![Page 61: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/61.jpg)
SO WHAT DO YOU THINK?COMMENTS AND QUESTIONS PLEASE
Has the “systems praxis framework” (SPF) mapped out the correct field of discourse?In that field of discourse, does motivation to communicate exceed motivation to obfuscate?Is it feasible and useful to agree a finite set of terms to describe an infinitely complex set of subjects and situations?
23rd Annual INCOSE International Symposium - Philadelphia, PA – 24-27 June, 2013
![Page 62: Common Language for Systems Practitioners: Why not!?](https://reader035.vdocuments.us/reader035/viewer/2022062323/56815dd8550346895dcc02f8/html5/thumbnails/62.jpg)
Survey
Please take the time to rate this presentation by submitting the web survey found at:
www.incose.org/symp2013/survey
23rd Annual INCOSE International Symposium - Philadelphia, PA – 24-27 June, 2013