Dave Camm and Dave Evans

advertisement
UK UNCLASSIFIED
© Crown Copyright 2012
Architectures for Decision Makers
Integrated-EA 2012
David Camm
DepHd Engineering – SEIG
DESSESEIG-Eng-DepHd@mod.uk
Tel +44 117 91 37810
Mob +44 7974 224358
David Evans
Chief Architect - Niteworks
David.Evans@niteworks.net
Tel +44 1252 385130
Mob +44 7776 215 623
UK UNCLASSIFIED
© Crown Copyright 2012
Architectures for Decision Makers
•  The MOD architecture journey
–  A potted history of EA in UK
Defence
–  Successes and lessons learnt
•  A partner view
–  Changing attitudes to EA
–  Different applications and
styles
•  Where next for EA in Defence?
UK UNCLASSIFIED
© Crown Copyright 2012
MOD ARCHITECTURE JOURNEY
UK UNCLASSIFIED
© Crown Copyright 2012
MOD Architecture Journey
Integ
ra
Focu tion
sed
ent
m
e
r
i
u
Req
d
Focuse
System of System
Focused
• Enterprise and Programme
orientated
• Pan DLOD
•  System orientated
•  IS Interoperability
•  Project orientated
•  Traceability
UK UNCLASSIFIED
© Crown Copyright 2012
The Story So Far.......
IA Arch
Modelling
(MODAR)
EA Initiatives
SOSA
ISRA
JSP906
NTA
DTSI
Logs NEC
GVA
DSTO - SOS
DOD - SOSE
MODAF v1.1
MODAF v1
DODAF
Frameworks v1
DODAF v1.5
NAF v1
Geo
DIRM
NAF v3.1
GBA
ISSE
E3
LOSA
MODAF v1.2
DODAF v2
DNDAF v1.7
UPDM v1.0
UPDM v2.0
2004
MODEM
2012
EA WG
SOSA CF
NTA
C-IED
Organisation/
Major
Projects
IDA
Meds
GII
MALE UAS
SUCCESSOR
CEPP
Pride
LOGNEC
UK UNCLASSIFIED
© Crown Copyright 2012
The IA / SEIG Architecture Journey
•  Architecture modelling
focus
–  Dedicated modelling lab
–  Capacity for 78 desks
–  ‘Drop in Centre’
•  Modelling
‘achievements’
–  400 Systems
–  24,000 diagrams
•  Only 1600 had any form of
history
–  300,000 nodes
–  9000 Man Days
UK UNCLASSIFIED
© Crown Copyright 2012
UK UNCLASSIFIED
© Crown Copyright 2012
Lessons Identified (and Learned?)
•  Focus on architecture modelling
–  Not architecture understanding
•  Focussed on Gate submissions
–  Used to support Assurance function
–  Investment model wrong – project focussed
–  Too little too late
–  Not maintained
•  Products not owned or valued by Delivery Teams
–  Done to them not with them
•  Architectural outputs
–  Policy produced stating what views required to support which gates
–  Complexity & detail viewed as good
•  Limited grasp of Enterprise Architecture (EA) concept
–  EA was composite Architecture of the Enterprise
•  Repository was being built piece-meal
–  Did not know what you did not know
UK UNCLASSIFIED
© Crown Copyright 2012
SOSA – System of Systems Approach
80/20
Rule
“Enabling enhanced capability through achieving
commonality, reuse and the interoperability of
independently procured systems”
Collaboration
Re-use
Interoperability
Evolutionary
SOSA
Rulebook
Controlled
Innovation
Incremental
Agility
Principles
Rulebook
Standardisation
Value for
Money
Operating Model
SOSA Community
!!#!~
Bas
el i
Pl an
ned
ENVI RO
Ar chi t ect ur e
FE@
???
NM
C4
C4
!!#!~
Tar g
et
ENT
R
PL AT F O
RM
SYSTEM
CO
M
PO
NENT
Logs
Training
Solution Support
ISTAR
Domain ...
Self Help
Rulebook
Basel i
ne
Pl anne
d
ENVI RO
Ar chi t ect ur e
FE@
SOSA Front
Door
NM
Ta r ge t
ENT
R
PL AT F O
RM
SYSTEM
CO
?
M
PO
NENT
?
Project 1
Project 1
Project 1
Industry
Delivery Teams
Project 2
Project 2
UK UNCLASSIFIED
© Crown Copyright 2012
Current Approach – System of Systems
•  Enterprise split into federated domains
–  Domain - defined logical area of Defence for which control and
coherence is required at an Enterprise level
•  Enterprise view
–  Capability, Technical, Operational
–  Domain Authority - organisation with authority to cohere and control one
or more SOSA Domains
–  Domain Map - relationship between domains
•  Domains develop & maintain necessary Body of Knowledge
(artefacts)
–  Artefact framework
•  Supported by more abstract concepts – Patterns, Services, ….
–  Issue based development
•  Support of domain experts provided throughout life of project
–  Systems Engineering Lifecycle - Shaping, Control, Release
–  Supports DE&S engineering strategy
•  Design Reviews
UK UNCLASSIFIED
© Crown Copyright 2012
Knowledge Based Systems Engineering
•  Developing, maintaining &
using knowledge ‘about’
the system
Coherent Knowledge Base
FE@R
Cap
Groups
System
Safety
–  Working from System of
Systems Perspective
Mission
Threads
...
•  Two overarching models
Doctrine
Domains
HF
–  Reference model
–  Process model
•  Creating coherent,
consistent requirement set
constraining the system
–  Context for the system
UK UNCLASSIFIED
© Crown Copyright 2012
Scavenger Case Study
• 
Purpose
–  Support development of Scavenger
context
–  Develop constraints and
interoperability requirements
• 
Approach
–  Use CONEMP, DSG 08, HLOC,
FASOC 2009 and Allied Joint Doctrine
for Air and Space Operations (AJP
3.3A), and is consistent with the
concepts espoused in the FMOC,
FLOC and FEMOC
–  Synthesise
•  Coherent Context
–  Validate with stakeholders
•  Corner Case Mission Threads
Benefit – Complete and coherent requirements
specification developed from a through life perspective
enabling SoS integration during
delivery not operations
UK UNCLASSIFIED
© Crown Copyright 2012
A PARTNER PERSECTIVE
UK UNCLASSIFIED
© Crown Copyright 2012
Niteworks - then and now
2003
2012
{  Focus on traditional
warfighting experimentation
and the NEC domain. Long
duration providing high level of
evidence.
{  Trend towards shorter term
projects taking rapid,
pragmatic view of a problem.
Often followed by more indepth investigation.
Single ‘experimentation’ Focus
Dedicated Architect
Enduring Role
Plan Development
Multiple foci
Arch Principles more prevalent
Multiple Roles
Rapid Development
UK UNCLASSIFIED
© Crown Copyright 2012
Recent Architecture Work In Support Of......
Current Operations
Urban &
Rear
PWAS
Tac C4
ISTAR
Capability Planning &
Delivery
DPD CI
MSII
DSF SSFI
QL
Visualising Complex
Scenarios
DSF Cap Vis
QL
Tac C4
ISTAR
CTC Cap Vis
QL
Option Analysis
Future
Maritime
Fires (FMF)
HIRA
Solution Support
JSP 604
IP Multi Cast
Integration & Coherency
SOSA
Community
Forum
Architecture Management
ISTAR
Domain
Architecture
Library
HIRA
Tac Bases
Voice
Cyber
TT CCD
MSII
Land Weapons
Integration
Feasibility Study
Acquisition
Tools &
Methods
DLIMS
NEADS
TT CCD
LE TAC CIS
ECM
Blueprint
UK UNCLASSIFIED
© Crown Copyright 2012
The approach is based on the systems engineering ‘V-model’
All capability definition outputs support the evaluation stage
Capability definition
Assessment
5 MCGs
Solution
performance
against system
requirements
Option definition
20 Munitions 3 Platforms
Cost model
Solutions
Key
Requirement
modelling
Option
definition
Operational
analysis
Capability
modelling
Solution
differentiators
‘Soft’ factors
URD
Solution options
Solution
performance
against user
requirement
Validation
Validation (beyond
Niteworks
Execution Phase)
URD score
Operational
effectiveness
through time
Concept
User
Requirements
Through-time
Validation
System
Requirements
Solutions
Capability
performance
Validation
Cost Model
CONEMP
CRD
Capability
Requirements
(Effects)
Performance models
Engagements
Definition
Architecture
models
Target set
Option evaluation
Cost
modelling
UK UNCLASSIFIED
© Crown Copyright 2012
The Changes In EA Adoption
• 
Decision focused
–  Used in support of decisions rather than done for the sake
of the architecture
• 
Good is good enough
–  Rapid development and very focused
• 
Increased awareness
–  Higher level of stakeholder involvement, understanding and
buy-in
–  Within the community an EA mentality and behaviours is
more recognisable if not the architect
• 
The role of the architect
–  Emerging understanding on the different architect roles
• 
Architecture by stealth
–  Architectural Principles more important than the
architecture model
UK UNCLASSIFIED
© Crown Copyright 2012
The Changes In EA Adoption
• 
Service Approach
–  Service based approach/thinking more common
• 
Visualisation is key
–  Greater focus on visualization of complex data rather than
architecture design
• 
Diversity in tooling
–  Best tool for the job (PowerPoint, EA , MOOD, SA)
–  Drive to integrate EA tooling with MI systems
• 
Appreciation of reuse
–  Partial reuse but limited based on domain, purpose and
currency
–  Understanding model shelf life and maintenance overhead
UK UNCLASSIFIED
© Crown Copyright 2012
UK UNCLASSIFIED
© Crown Copyright 2012
WHERE NEXT FOR EA IN DEFENCE?
UK UNCLASSIFIED
© Crown Copyright 2012
•  Part of the
acquisition mindset
•  Never fully meet
early promises
•  Disjointed
messages
The Ugly
•  MODAF
internationally
recognised
The Bad
The Good
The Good, the Bad and the Ugly
•  At times lost focus
of the value to the
war fighter
•  Distracted by the
complexity of the
problem
•  Significant project
successes
•  Continuing to
develop
UK UNCLASSIFIED
© Crown Copyright 2012
Challenges for Next 5 Years
•  MOD Industry relationship
–  White Paper – OTS and SME
–  Shared architecture development
•  Tools maturity
–  Niche – all do some things well – limited interoperability
–  Integration into MI / Business tools
•  Framework maturity and simplification
–  MODAF, NAF, DODAF, ……
•  Put single information source at heart of project development
–  MBSE
•  Establish ‘business as normal’ governance
–  Ownership and authority
–  Architecture validation and verification
UK UNCLASSIFIED
© Crown Copyright 2012
The Key Challenge – Institutionalisation
•  Corporate and cultural challenge
–  Architecture still seen (by some) as overhead
•  Long haul – no silver bullet
–  Post reform organisation
•  Architectural roles / responsibilities
–  Embed into mature organisational processes
•  Understanding value
–  Value of Coherence – Pan DLOD and whole life
–  Configuration understanding and sharing architectural
information
•  Professionalization
–  Skills recognition / skills development
–  Ways of working, style to enable reuse
•  Common lexicons
UK UNCLASSIFIED
© Crown Copyright 2012
The Journey So Far
•  Joint journey by MOD
and Industry
•  Significant successes
but..
•  ...continue to reinforce
way of thinking and good
practices
UK UNCLASSIFIED
© Crown Copyright 2012
QUESTIONS?
UK UNCLASSIFIED
© Crown Copyright 2012
Download