mod architectural framework (modaf): recent...
TRANSCRIPT
modaf© Crown Copyright 2007Published and used by INCOSE with permission
MOD Architectural Framework (MODAF):Recent Developments
MODAF Enablers TeamPeter Bryant (LogicaCMG)
Mike Phipps (LogicaCMG UK)Paul King (Vega Group plc)Ian Bailey (Model Futures)
Adrian Pearson (MOD Integration Authority)
modaf
Agenda
• MODAF – historical perspective & status
• Summary of recent changes
• Special topics
– Enterprise phases & capability
– Humans in MODAF
– Nodes & requirements
• Future of MODAF
modaf© Crown Copyright 2007Published and used by INCOSE with permission
MODAF – historical perspective& status
modaf
Why does MOD need to do Architecting?
• Network Enabled Capability (NEC)
Interconnection
Integration
Synchronization
• System-of-systems
• Joined-up thinking
• Common understanding
modaf
What MODAF is NOT
SV-9: Systems Technology Forecast
SV-10a: System Rules ModelSV-10b: Systems StateTransition Description
SV-10c: Systems Event Trace Description
SV-11: Physical Schema
AcV-1: System of SystemAcquisition Clusters AcV-2: System of System
Acquisition Programmes
A lot of disconnected views
modaf
What MODAF IS
• An Architecture Framework
• For the MOD Enterprise
• Views as expressions of a model
• Underpinned by a MODAF Meta-Model (M3)
• Evolution of DoDAF
modaf
Historical Perspective
DoDAF M3
ArmyActivityModel
MODBusinessModelling
MOD Business Modelling Activities
Architecture Frameworks
IA frameworkMODAF v1
MDAUML2XMI
SysML
Object Management Group (OMG) activities
ISSE Meta Model
modaf
On Line Documentation
Documentation has recentlybeen published at www.modaf.org.uk
modaf
MODAF Viewpoints
All
Vie
ws
Te
ch
nic
al
Sta
nd
ard
sV
iew
s System Views
Operational Views
Ac
qu
isitio
nV
iew
s
New viewpoint(two new views)
New viewpoint(six new views)
Strategic Views
One modified view (AV-2)
Two new views(OV-1b and OV-1c)and one modified view (OV-2)
Two new views (SV-2a and SV-2b)and two modified views (SV-1 and SV-2c)One modified view (TV-1)
modaf
OPERATIONAL VIEWPOINT
SYSTEM VIEWPOINT
OV-2 OV-3 OV-4
OV-5 OV-7
SV-7 SV-8 SV-9 SV-11
STRATEGIC VIEWPOINT
StV-1 StV-2 StV-3 StV-4 StV-5 StV-6
SV-1 SV-3 SV-4 SV-5 SV-6
STANDARDS VIEWPOINT
TV-1 TV-2
ACQUISITION VIEWPOINT
AcV-1 AcV-2
ALL VIEWS
AV-1 AV-2
OV-1cOV-1bOV-1a
OV-6cOV-6bOV-6a
SV-2cSV-2bSV-2a
SV-10cSV-10bSV-10a
OV-1a: High LevelOperational Concept Graphic
OV-2: Operational NodeRelationship Description
OV-5: Operational Activity ModelSV-1: Systems Interface Description
SV-3: Systems-Systems Matrix
SV-10c: Systems EventTrace DescriptionAcV-2: System of System
Acquisition Programmes
MODAF standardprovides guidanceon views
The Framework of Views
modaf
Alternative Perspective on Views
SV-3SV-5
StV-3StV-5StV-6
Mapping
SV-4SV-10aSV-10bSV-10c
OV-5OV-6aOV-6bOV-6c
Behavioural
AcV-1
SV-1SV-2aSV-2bSV-2cSV-11
OV-2OV-4OV-7
StV-4
Structural
AcV-2AcquisitionViews
TV-1TV-2
TechnicalStandardsViews
SV-8SV-6SV-7SV-9
System Views
OV-1aOV-1bOV-1cOV-3
OperationalViews
StV-2StV-1StrategicViews
AV-2AV-1All Views
TimelinePictorialOntologyTabularCategory
Viewpoint
modaf
MODAF Meta-Model (M3)
operational architecture
Project
required to deliver
delivers
Capability Increment
has milestones
system architecture
Fielded Capability
hasconfiguration
deployed architecture ?
strategicarchitecture
StandardStandardStandard
Ontology & Information
MODAF Ontology Local Taxonomy (AV-2)
Logical Information Model (OV-7)
Physical Data Model (SV-11)
MetaData
(AV-1)
Capability Configuration
Physical Asset
System
hosted on
deployed to
Competence
has
to conduct
is realised as
performs
fulfils
realises
from to
FunctionData
System Connection
carries
Org Resource
RoleRole
interaction
composedof
Whole-Life Enterprise
Enterprise Vision
contributes to depends on
Enterprise Goalhas goals
Enterprise Phase
vision for phase
Enterprise Phase Enduring Task
tasks
contributes to
Capability Metrics
StandardOperational Activity
contributesto
OperationalActivity
Node
conducts
Needline
from to
Information
carries
requiredcapability
specialisatonof Strategic Architecture
Operational Architecture
System Architecture
Programmatics
Ontology & Information
Standards
Deployed Architecture
modaf
DependenciesOntology
StrategicArchitecture
StandardActivities
Capabilities
OrganisationsInformation
OperationalArchitecture
OperationalActivities
Nodes
2020
OperatorsData
SystemArchitecture
Systems Functions
Option B
Vert
ica
lIn
tegra
tio
n
Layering of Views (Structural)
SV
OV
StV
InformationFlows
Information
OperationalArchitecture
OperationalActivities
Nodes
InteractionsData
SystemArchitecture
Resources Functions
2010
Option A
modaf
Layering of Views (Temporal)
StV
DependenciesOntology
StrategicArchitecture
StandardActivities
Capabilities
Phase 2
Phasing
Phase 1
Organisations
ProjectArchitecture
Milestones AcV
Projects
modaf
Putting it all together
All
Vie
ws
(Me
tad
ata
)
Te
ch
nic
al
Sta
nd
ard
s
OperatorsData
SystemArchitecture
Resources Functions
Option D
OperatorsData
SystemArchitecture
Resources Functions
Option C
OperatorsData
SystemArchitecture
Resources Functions
Option B
OperatorsData
SystemArchitecture
Resources Functions
OrganisationsInformation
OperationalArchitecture
OperationalActivities
Nodes
2020
OrganisationsInformation
OperationalArchitecture
OperationalActivities
Nodes
Org
an
isa
tio
ns
Pro
jec
tsP
roje
ct
Arc
hit
ec
ture
Mil
es
ton
es
Wo
rks
tre
am
sO
rga
nis
ati
on
sP
roje
cts
Pro
jec
tA
rch
ite
ctu
reM
iles
ton
es
Wo
rks
tre
am
sO
rga
nis
ati
on
sP
roje
cts
Pro
jec
tA
rch
ite
ctu
reM
iles
ton
es
DependenciesOntology
StrategicArchitecture
StandardActivities
Capabilities
modaf© Crown Copyright 2007Published and used by INCOSE with permission
Recent changes
modaf
Drivers for Change
• Capability-based procurement– Need models of the business context for a capability that do
not prejudge how organisational resources are involved
• Enterprise Architecture– Need models with a strategic time dimension
• Operational planning– Moving towards SOA support
• Increasing alignment with SysML
modaf
Summary of Changes (post Aug 2005)
• Viewpoint integration
• Changes to names to a number of views tobetter reflect their purpose
• Views, changes to content of
– AV-1, StV-1, StV-2, StV-3, StV-5, StV-6
– OV-2, OV-4, SV-1, SV-4, AcV-2
modaf
Viewpoint Linkage Between Layers
Why? How?
Why?
What?
How?
Who?Where?
When?
Who?Where?
System
Operational
Strategic
NB this reflects the perspective of a URD author
modaf
Key MODAF Concepts
• Enterprise Phases
• Capability & Capability Configuration
• Treatment of Organisational Resources
• Operational Node & Problem Domain
modaf
cd StV-2 PB1
«WholeLifeEnterprise»
Ground Manoeuv re
«EnterprisePhase»
Ground Manoeuv re 2005-2015«EnterprisePhase»
Ground Manoeuv re 2015-2025
Enterprise Phasing
modaf
cd StV2-PB2
«WholeLifeEnterprise»
Ground Manoeuv re
«EnterprisePhase»
Ground Manoeuv re 2005-2015
«Capabil ity»
Ground Manoeuvre
2005-2015::Light Armour
Recovery - Desert
+ recoveryTime: 8 hours
«Capabili ty»
Ground Manoeuv re
2005-2015::Light Armour
Recov ery - Road
+ recoveryTime: 4 hours
«Environment»
Desert - Any
Conditions
«Environment»
Roadside - Any
Conditions
«Capabil ity»
Light Armour Recov ery
«Capabili ty»
Vehicle Recovery
«Capabili ty»
Heav y Armour Recovery
«Environment»
In Theatre under Fire
«Capabili ty»
Ground Manoeuv re
2005-2015::Light
Armour Recov ery -
Under Fire
+ recoveryTime: 1 hour
«Capabili ty»
Ground Manoeuv re::Infantry Mobility &
Protection
«EnvironmentalConditions»«EnvironmentalConditions»«EnvironmentalConditions»
Capabilities
modaf
Capability Configuration
CapabilityConfigurationCapability
Configuration
PhysicalAsset
PhysicalAsset
OrganisationalResource
OrganisationalResource
configured with
hosted on
SystemSystem
owns
configured with
deployed to
FunctionFunctionhas
RoleRole
is assigned
operates
modaf
«CapabilityConfiguration»
FRED Armour Recov ery Configuration
«PhysicalAsset»
FRED Platform
«System»
:Bowman
PRCxxx
«PostType»
:FRED Commander
«Role»
:Radio Operator
«Role»
:Commander
«ResourceInteraction»
Capability Configuration
modaf
cd SV-1 Example
«ResourceStructureModel»
FRED Resource Interactions
«Capabil i tyConfiguration»
FRED Armour Recovery Configuration «OrganisationType»
Light Aid Detachment
«PhysicalAsset»
FRED Platform
«System»
:Bowman
PRCxxx
«PostType»
:FRED Commander
«Role»
:Radio Operator
«PostType»
:FRED Driv er
«Role»
:Driver
«Role»
:Commander
«System»
:FRED Control System
«PostType»
:FRED Crane Operator
«Role»
:Crane Operator
«System»
:FRED Crane
System
«PostType»
:LAD Commander
«PostType»
:LAD Comms Officer
«Role»
:Fleet Controller
«Role»
:Command
«System»
:Bowman
HCDR
«System»
Bowman WAN
«R
eso
urce
Inte
ractio
n»
«R
eso
urce
Inte
ractio
n»
«R
eso
urce
Inte
ractio
n»
«ResourceInteraction»
«ResourceInteraction»
«ResourceInteraction»
«ResourceInteraction»
«ResourceInteraction»
«R
eso
urce
Inte
ractio
n»
modaf
cd OV-2 Example ISTAR
«NodeRelationshipDescription»
ISTAR Example with Activ ities
«Node»
Intelligence Node
«Node»
Target Acquisition Constellation
«Node»
STAR Node
«Node»
Command Node
«Node»
Strike Node
«Needline»
7 - Authorisation
«Needline»
1 - Target Observation
«Needline»
6 - Target Data
«Needline»
5 - Target Data
«Needline»
4 - Target Collateral
«Needline»
2 - Target Collateral
«Needline»
3 - Target Collateral
OV-2 (logical)
modaf
cd OV-2 Generic Example with Flows
«NodeRelationshipDescription»
OV-2 Example 1
«ProblemDomain»
My Problem Domain
«Node»
External Node
«Node»
Node1
«Node»
Node2
«NodeConnector»
Materiel Supply
«Needline»
2
«NodeConnector»
Movement of Personnel
«Needline»
1
«NodeConnector»
Electricity Supply
OV-2 (physical flows)
modaf
cd OV-2 With Capabilities
«NodeRelationshipDescription»
Armour Recovery Logical Architecture
«ProblemDomain»
Repair & Recov ery Problem Domain
«Node»
Repair & Recov ery
Control Node
«Node»
Recovery Node
«Node»
Command Node
«Node»
Stranded Vehicle
Light Armour Recovery
«Capabili ty»
Ground Manoeuv re
2005-2015::Light Armour
Recov ery - Road
+ recoveryTime: 4 hours
«Environment»
Roadside - Any
Conditions
«LocationType»
Public Road
«Environment»
Desert - Any Conditions
«LocationType»
Desert
Light Armour Recovery
«Capabil i ty»
Ground Manoeuv re 2005-
2015::Light Armour
Recov ery - Desert
+ recoveryTime: 8 hours
Needlines:
1 - Request for Aid2 - Order for Aid
3 - Recovery Tasking Order
«EnvironmentalConditions»
«EnvironmentalConditions»
«Needline»
1
«Needline»
2
«Capabil i tyForNode»
«Capabil ityForNode»
«Needline»
3
Capability need fulfilment
modaf
Resources
modaf
Context for Trade Offs
modaf© Crown Copyright 2007Published and used by INCOSE with permission
Where is MODAF going?
modaf
Future Drivers (post v1.1)
• SOA for procurement within a System of Systems– Need models to support governance
– How to specify an equipment capability within an SOAenvironment
• Better integration with specialist engineeringdisciplines– Security, Human Factors…
• Architectural Design Patterns– MODAF could provide a template for pattern definition
• Future support for BPMN (post OMG rationalisation)
modaf
The Future?
DoDAF M3
ArmyActivityModel
MODBusinessModelling
MOD Business Modelling Activities
Architecture Frameworks
IA frameworkMODAF v1
MDAUML2XMI
SysML
Object Management Group (OMG) activities
(BPMN)
FutureMil ArchStandard(UPDM?)
FutureMOD EA
FutureMODAF
(MODAF Ontology)
NAF
?
svcs
MODAFv1.1
?
ISSE Meta Model
modaf
QUESTIONS?
Documentation available atwww.modaf.org.uk