the problematic situation aspect of conceptual design
DESCRIPTION
Describes what system conceptual designers must Know? Preface to (subsequent presentation) describing what they must Do and Be.TRANSCRIPT
The Problematic Situation-- a key aspect of Conceptual Design –
MBCD Workshop11/12/2013
by
Jack RingFellow, INCOSE
Educe LLC
Learning, Creating and Using KnowledgeNovak, J. Ph.D., Earlbaum, 2nd Edition, 2009
Theory
Principles
Propositions
Situation Invariant
Relationships form
ConceptsSalient discontinuities
in a semantic space
Relationships form
Instance
Observation
Interpretation
Knowledge Claims
Acknowledgement
expressed as
Agenda
To excel at MBCD --- • What must you know?• Why must you know?• When must you know?• Where must you know?• Who must know?• How can you know, for
sure?
11/10/13
OntoPilot LLC 4
Checkpoint Protocol
Not clear. Cognitive overload.
Disagree. (Strongly disagree can be a subset)
Makes sense.
This is key.we can do this!
11/4/2013
KK Kfalse DK
Ktrue
What must you Know: Classes
KK = know you knowKDK = know what you don’t knowDKDK = don’t know that you don’t knowDKK = don’t know you know (e.g.,subconscious)
Our fallibility stems not from what we do not know but from what we do know --- that ‘ain’t so.’
KDK
DKDK
DKK
not to
scale
11/10/13
What must you know: Types
©Xplane: Wired Magazine, 2/2001
As Is (see graphic)May become, growMay become, morph
State-determinedErgodicNon-deterministic
Stakeholder Perspective• Significance• Urgency• Intent• Concerns11/10/13
Why must you know: To Conceive π1. Problematic Situation 2. Systemics
Problem System
Stakeholders
Users
Beneficiaries
Losers
Generators
Techno-logies
InteropSystems
11/10/13
π
Why must you know: To Conceive π1. Problematic Situation 2. Systemics
Problem System
Stakeholders
Users
Beneficiaries
Losers
Generators
Techno-logies
InteropSystems
E V AHighMediumLow
E = ExtentV = VarietyA = Ambiguity
= MBSE 2
= MBSE 1= TSE
11/10/13
π
Q = QualityP = ParsimonyB = Beauty
π
Why must you know: Else
• Unintended Consequences• Schedule slips• Overruns• etc.
11/10/13
System of Systems
When must you know?
Case 1
Concept Design Time and Cost
Case 2
Case 310 %
100%
11/10/13
Where must you know it
• As close to the action as possible, persistently.• Then when system usage starts: POSIWID
11/10/13
Art: Jamcracker
It is not about Requirements Management
Who must know
The Concept designers and
The Problematic Situation Representative(s). (creative tension).
Both Accountable for subsequent surprises.
11/10/13
How can you know, for sure?
• The ConOps: Concept of Operations. A prescriptive model of intended usage, or two or three. Clearly communicates intended and unacceptable
behaviors (emergent characteristics and properties. States Top Ten Measures of System Effect-iveness States Standards of Acceptance (if various modalities
and usage domains). Source of T&E scenarios. Not to be confused with Operations Concept (the
owner’s/operator’s manual) Not to be confused with Use Cases.
• Must be accepted by Concept Design staff (performing incoming inspection and risk assessment).
11/10/13
A fresh look at the problematic situation inspired this conceptual design
11/10/13
Gird Thy Loins!
Beware CHANGE ---There is nothing as difficult to handle, more dubious in outcome or more dangerous to organise.
It creates enemies of all those content with the status quo, and can only muster lukewarm support from those who would benefit from the change.
Niccolo Machiavelli 1513
G’day