Upload
heather-wallace
View
61
Download
0
Embed Size (px)
Citation preview
© 2
014
Airb
us D
efen
ce a
nd S
pace
– A
ll rig
hts
rese
rved
. The
repr
oduc
tion,
dis
tribu
tion
and
utili
zatio
n of
this
doc
umen
t as
wel
l as
the
com
mun
icat
ion
of it
s co
nten
ts to
oth
ers
with
out e
xpre
ss a
utho
rizat
ion
is p
rohi
bite
d. O
ffend
ers
will
be
held
liab
le fo
r the
pay
men
t of d
amag
es. A
ll rig
hts
rese
rved
in th
e ev
ent o
f the
gra
nt o
f a p
aten
t, ut
ility
mod
el o
r des
ign.
EA User Group Conference, London 16th May 2014
1Date
The Power of StereotypesArchitecture Management for the Border Security Product Line at AIRBUS Defence & Space
Heather WallacePrincipal Systems Engineer / Architecture Manager
© 2
014
Airb
us D
efen
ce a
nd S
pace
– A
ll rig
hts
rese
rved
. The
repr
oduc
tion,
dis
tribu
tion
and
utili
zatio
n of
this
doc
umen
t as
wel
l as
the
com
mun
icat
ion
of it
s co
nten
ts to
oth
ers
with
out e
xpre
ss a
utho
rizat
ion
is p
rohi
bite
d. O
ffend
ers
will
be
held
liab
le fo
r the
pay
men
t of d
amag
es. A
ll rig
hts
rese
rved
in th
e ev
ent o
f the
gra
nt o
f a p
aten
t, ut
ility
mod
el o
r des
ign.
The Power of Stereotypes – Heather Wallace 2
EA User Group Conference, London 16th May 2014
A Little Background1. Old issues and new challenges2. A cunning plan
Determination of Stereotypes (and their Use)3. Metamodel and EA project structure4. MDG technology implementation
Stereotype Exploitation5. Document generation6. DOORS integration7. Integrity checking
And Finally…8. Next steps9. Key messages
Contents
© 2
014
Airb
us D
efen
ce a
nd S
pace
– A
ll rig
hts
rese
rved
. The
repr
oduc
tion,
dis
tribu
tion
and
utili
zatio
n of
this
doc
umen
t as
wel
l as
the
com
mun
icat
ion
of it
s co
nten
ts to
oth
ers
with
out e
xpre
ss a
utho
rizat
ion
is p
rohi
bite
d. O
ffend
ers
will
be
held
liab
le fo
r the
pay
men
t of d
amag
es. A
ll rig
hts
rese
rved
in th
e ev
ent o
f the
gra
nt o
f a p
aten
t, ut
ility
mod
el o
r des
ign.
EA User Group Conference, London 16th May 2014
OLD ISSUES AND NEW CHALLENGES1
A LITTLE BACKGROUND
© 2
014
Airb
us D
efen
ce a
nd S
pace
– A
ll rig
hts
rese
rved
. The
repr
oduc
tion,
dis
tribu
tion
and
utili
zatio
n of
this
doc
umen
t as
wel
l as
the
com
mun
icat
ion
of it
s co
nten
ts to
oth
ers
with
out e
xpre
ss a
utho
rizat
ion
is p
rohi
bite
d. O
ffend
ers
will
be
held
liab
le fo
r the
pay
men
t of d
amag
es. A
ll rig
hts
rese
rved
in th
e ev
ent o
f the
gra
nt o
f a p
aten
t, ut
ility
mod
el o
r des
ign.
The Power of Stereotypes – Heather Wallace 4
EA User Group Conference, London 16th May 2014
The border security contextNOV-1 Concept: Border Surveillance and Response Overview
© 2
014
Airb
us D
efen
ce a
nd S
pace
– A
ll rig
hts
rese
rved
. The
repr
oduc
tion,
dis
tribu
tion
and
utili
zatio
n of
this
doc
umen
t as
wel
l as
the
com
mun
icat
ion
of it
s co
nten
ts to
oth
ers
with
out e
xpre
ss a
utho
rizat
ion
is p
rohi
bite
d. O
ffend
ers
will
be
held
liab
le fo
r the
pay
men
t of d
amag
es. A
ll rig
hts
rese
rved
in th
e ev
ent o
f the
gra
nt o
f a p
aten
t, ut
ility
mod
el o
r des
ign.
The Power of Stereotypes – Heather Wallace 5
EA User Group Conference, London 16th May 2014
Border security as a system of systemsNSV-1.1 System Decomposition: Border Security System Decomposition
«System»Border Security System
A
«System»Border Security System
A
«SystemElement»Communication Infrastructure
«SystemElement»Communication Infrastructure
«SystemElement»IT & Shared Services
«SystemElement»IT & Shared Services
«SystemElement»Physical Infrastructure
«SystemElement»Physical Infrastructure
Core Functional System ElementsSupporting System Elements
Legend
«SystemElement»Command & Control«SystemElement»
Command & Control«SystemElement»
Surveillance«SystemElement»
Surveillance«SystemElement»
Intelligence«SystemElement»
Intelligence
«SystemElement»Training & Simulation
«SystemElement»Training & Simulation
© 2
014
Airb
us D
efen
ce a
nd S
pace
– A
ll rig
hts
rese
rved
. The
repr
oduc
tion,
dis
tribu
tion
and
utili
zatio
n of
this
doc
umen
t as
wel
l as
the
com
mun
icat
ion
of it
s co
nten
ts to
oth
ers
with
out e
xpre
ss a
utho
rizat
ion
is p
rohi
bite
d. O
ffend
ers
will
be
held
liab
le fo
r the
pay
men
t of d
amag
es. A
ll rig
hts
rese
rved
in th
e ev
ent o
f the
gra
nt o
f a p
aten
t, ut
ility
mod
el o
r des
ign.
The Power of Stereotypes – Heather Wallace 6
EA User Group Conference, London 16th May 2014
Client Project A (border security) as source of EA-based architecture, software assets and integration knowledge.
Reuse as both driver and context
Reference Solution, extending border security capabilities, enhancing non-functional characteristics.
Delivering modular product “kits” against roadmap
Client Project C configuring, deploying and maintaining
standard products.
Client Bid B costing based on standard
products
Business Development planning and marketing
based on standard products
REUSE
REUSEREUSE REUSE
ROADMAP
© 2
014
Airb
us D
efen
ce a
nd S
pace
– A
ll rig
hts
rese
rved
. The
repr
oduc
tion,
dis
tribu
tion
and
utili
zatio
n of
this
doc
umen
t as
wel
l as
the
com
mun
icat
ion
of it
s co
nten
ts to
oth
ers
with
out e
xpre
ss a
utho
rizat
ion
is p
rohi
bite
d. O
ffend
ers
will
be
held
liab
le fo
r the
pay
men
t of d
amag
es. A
ll rig
hts
rese
rved
in th
e ev
ent o
f the
gra
nt o
f a p
aten
t, ut
ility
mod
el o
r des
ign.
The Power of Stereotypes – Heather Wallace 7
EA User Group Conference, London 16th May 2014
Enterprise Features Stakeholder ReqsLead to
Ope
ratio
nal A
rchi
tect
ure
Des
crip
tion
System L0 Features System L0 ReqsLead to
System Element Features
System Element
ReqsLead to
Specification to Subsystems
analy
sis
Sys
tem
Arc
hite
ctur
e D
escr
iptio
n M
ain
Doc
umen
t (S
yste
m B
lack
Box
)
SA
D D
esig
n D
escr
iptio
ns
(Sys
tem
Whi
te B
ox)
Ope
ratio
nal A
rchi
tect
ure
Syst
em A
rchi
tect
ure
SA
D S
E
Spe
cific
atio
n (S
E B
lack
Box
)
analy
sis
analysis
analysis
ContractReqs
Inform
inform
inform
validation
verification
factory acceptance test
•Principles: – All requirements derived (by architects) from
architecture at specific levels of abstraction
– Three streams of features drive requirements:– Functional– Deployment– Non-functional (including all interfaces)
– Single repository, international access– All architectural features presented in review
documentation with their driving and derived requirements, plus key element links
•Methodology and techniques:– DoDAF views, logical and UML diagrams– Stereotypes defined as UML types– Selectable styles (pre-set colours)– Diagrams and link types from standard plug-ins– eaDocX for document generation– DOORS integration via MDG Link and eaXL
Client Project A – pragmatic but principled approach
© 2
014
Airb
us D
efen
ce a
nd S
pace
– A
ll rig
hts
rese
rved
. The
repr
oduc
tion,
dis
tribu
tion
and
utili
zatio
n of
this
doc
umen
t as
wel
l as
the
com
mun
icat
ion
of it
s co
nten
ts to
oth
ers
with
out e
xpre
ss a
utho
rizat
ion
is p
rohi
bite
d. O
ffend
ers
will
be
held
liab
le fo
r the
pay
men
t of d
amag
es. A
ll rig
hts
rese
rved
in th
e ev
ent o
f the
gra
nt o
f a p
aten
t, ut
ility
mod
el o
r des
ign.
The Power of Stereotypes – Heather Wallace 8
EA User Group Conference, London 16th May 2014
Client Project A – effective but inefficient approach
3-stream architecture
Inconsistenciesbetween streams
High traceability
Complex set of link types
Substantial team effort
Errors and misinterpretations
Informative decompositions
High maintenance(link-hiding)
Validated L0system arch /design
Static operationalarchitecture
Requirements integration
Late identification of trace gaps
Effective documentation
Navigation issues(order of elements)
© 2
014
Airb
us D
efen
ce a
nd S
pace
– A
ll rig
hts
rese
rved
. The
repr
oduc
tion,
dis
tribu
tion
and
utili
zatio
n of
this
doc
umen
t as
wel
l as
the
com
mun
icat
ion
of it
s co
nten
ts to
oth
ers
with
out e
xpre
ss a
utho
rizat
ion
is p
rohi
bite
d. O
ffend
ers
will
be
held
liab
le fo
r the
pay
men
t of d
amag
es. A
ll rig
hts
rese
rved
in th
e ev
ent o
f the
gra
nt o
f a p
aten
t, ut
ility
mod
el o
r des
ign.
The Power of Stereotypes – Heather Wallace 9
EA User Group Conference, London 16th May 2014
Reference Architecture – additional challenges
New team of 20 architects & analysts
Kit-basedproduct variants
Multiple client projects and goals
Commercial considerations – finding the quality “sweet-spot”
© 2
014
Airb
us D
efen
ce a
nd S
pace
– A
ll rig
hts
rese
rved
. The
repr
oduc
tion,
dis
tribu
tion
and
utili
zatio
n of
this
doc
umen
t as
wel
l as
the
com
mun
icat
ion
of it
s co
nten
ts to
oth
ers
with
out e
xpre
ss a
utho
rizat
ion
is p
rohi
bite
d. O
ffend
ers
will
be
held
liab
le fo
r the
pay
men
t of d
amag
es. A
ll rig
hts
rese
rved
in th
e ev
ent o
f the
gra
nt o
f a p
aten
t, ut
ility
mod
el o
r des
ign.
EA User Group Conference, London 16th May 2014
A CUNNING PLAN2
A LITTLE BACKGROUND
© 2
014
Airb
us D
efen
ce a
nd S
pace
– A
ll rig
hts
rese
rved
. The
repr
oduc
tion,
dis
tribu
tion
and
utili
zatio
n of
this
doc
umen
t as
wel
l as
the
com
mun
icat
ion
of it
s co
nten
ts to
oth
ers
with
out e
xpre
ss a
utho
rizat
ion
is p
rohi
bite
d. O
ffend
ers
will
be
held
liab
le fo
r the
pay
men
t of d
amag
es. A
ll rig
hts
rese
rved
in th
e ev
ent o
f the
gra
nt o
f a p
aten
t, ut
ility
mod
el o
r des
ign.
The Power of Stereotypes – Heather Wallace 11
EA User Group Conference, London 16th May 2014
Significant new features of target approach
Inconsistencies between streams
Complex set of link types
Qualities focus
Enhanced Metamodel
Capture of client drivers and operations (generic)
MDGStereotypes Diagrams
Kit-based product variantsStatic operational architecture
Rapid learning curve / consistent approach
Addressing identified issues:
Addressing identified issues:
Errors and misinterpretations
High maintenance (link-hiding)
Navigation issues (order of elements)
© 2
014
Airb
us D
efen
ce a
nd S
pace
– A
ll rig
hts
rese
rved
. The
repr
oduc
tion,
dis
tribu
tion
and
utili
zatio
n of
this
doc
umen
t as
wel
l as
the
com
mun
icat
ion
of it
s co
nten
ts to
oth
ers
with
out e
xpre
ss a
utho
rizat
ion
is p
rohi
bite
d. O
ffend
ers
will
be
held
liab
le fo
r the
pay
men
t of d
amag
es. A
ll rig
hts
rese
rved
in th
e ev
ent o
f the
gra
nt o
f a p
aten
t, ut
ility
mod
el o
r des
ign.
The Power of Stereotypes – Heather Wallace 12
EA User Group Conference, London 16th May 2014
Model conversion and enhancement
Determine target
metamodel
Convert Client Project A local copy
Upload to SQL Server
Enhance as reference
architecture
Manage reference
architectureCreate MDG technology
Use MDG technology
Maintain MDG technology
© 2
014
Airb
us D
efen
ce a
nd S
pace
– A
ll rig
hts
rese
rved
. The
repr
oduc
tion,
dis
tribu
tion
and
utili
zatio
n of
this
doc
umen
t as
wel
l as
the
com
mun
icat
ion
of it
s co
nten
ts to
oth
ers
with
out e
xpre
ss a
utho
rizat
ion
is p
rohi
bite
d. O
ffend
ers
will
be
held
liab
le fo
r the
pay
men
t of d
amag
es. A
ll rig
hts
rese
rved
in th
e ev
ent o
f the
gra
nt o
f a p
aten
t, ut
ility
mod
el o
r des
ign.
The Power of Stereotypes – Heather Wallace 13
EA User Group Conference, London 16th May 2014
Types and stereotypes• eaXL: stereotype updates• MS Access: update queries • MS Access: filter and replace• Manual: model missing layers
Diagram types• Manual: Change diagram type• Manual: Create new diagrams• MS Access: query for old types
New rules• eaXL: Update descriptions
Conversion – assisted by database updates
© 2
014
Airb
us D
efen
ce a
nd S
pace
– A
ll rig
hts
rese
rved
. The
repr
oduc
tion,
dis
tribu
tion
and
utili
zatio
n of
this
doc
umen
t as
wel
l as
the
com
mun
icat
ion
of it
s co
nten
ts to
oth
ers
with
out e
xpre
ss a
utho
rizat
ion
is p
rohi
bite
d. O
ffend
ers
will
be
held
liab
le fo
r the
pay
men
t of d
amag
es. A
ll rig
hts
rese
rved
in th
e ev
ent o
f the
gra
nt o
f a p
aten
t, ut
ility
mod
el o
r des
ign.
EA User Group Conference, London 16th May 2014
METAMODEL AND EA PROJECT STRUCTURE3
DETERMINATION OF STEREOTYPES (AND THEIR USE)
© 2
014
Airb
us D
efen
ce a
nd S
pace
– A
ll rig
hts
rese
rved
. The
repr
oduc
tion,
dis
tribu
tion
and
utili
zatio
n of
this
doc
umen
t as
wel
l as
the
com
mun
icat
ion
of it
s co
nten
ts to
oth
ers
with
out e
xpre
ss a
utho
rizat
ion
is p
rohi
bite
d. O
ffend
ers
will
be
held
liab
le fo
r the
pay
men
t of d
amag
es. A
ll rig
hts
rese
rved
in th
e ev
ent o
f the
gra
nt o
f a p
aten
t, ut
ility
mod
el o
r des
ign.
The Power of Stereotypes – Heather Wallace 15
EA User Group Conference, London 16th May 2014
Levels of abstractionNAF Capability View Enterprise capability level – abstracted view of enterprise
needsNAF Operational View Enterprise level – black box view of what the enterprise must
achieve. Basis for derived stakeholder requirements.Enterprise enabling level – contextual breakdown of black box enterprise into sub-features for white box analysisOperational level – white box view of enterprise and its operational activities, nodes and qualities. Informs system architecture
NAF System View
System level – black box view of what the system must achieve. Basis for derived system L0 requirements.System enabling level – contextual breakdown of black box system features for white box analysisSystem element level – black box view of what the system element must achieve. Basis for derived system element (L1) requirements….
© 2
014
Airb
us D
efen
ce a
nd S
pace
– A
ll rig
hts
rese
rved
. The
repr
oduc
tion,
dis
tribu
tion
and
utili
zatio
n of
this
doc
umen
t as
wel
l as
the
com
mun
icat
ion
of it
s co
nten
ts to
oth
ers
with
out e
xpre
ss a
utho
rizat
ion
is p
rohi
bite
d. O
ffend
ers
will
be
held
liab
le fo
r the
pay
men
t of d
amag
es. A
ll rig
hts
rese
rved
in th
e ev
ent o
f the
gra
nt o
f a p
aten
t, ut
ility
mod
el o
r des
ign.
The Power of Stereotypes – Heather Wallace 16
EA User Group Conference, London 16th May 2014
To be expanded in Enterprise Architect
Some additional information on the selection of NAF sub-views is available in the backup slides
Package structure (NAF views)
© 2
014
Airb
us D
efen
ce a
nd S
pace
– A
ll rig
hts
rese
rved
. The
repr
oduc
tion,
dis
tribu
tion
and
utili
zatio
n of
this
doc
umen
t as
wel
l as
the
com
mun
icat
ion
of it
s co
nten
ts to
oth
ers
with
out e
xpre
ss a
utho
rizat
ion
is p
rohi
bite
d. O
ffend
ers
will
be
held
liab
le fo
r the
pay
men
t of d
amag
es. A
ll rig
hts
rese
rved
in th
e ev
ent o
f the
gra
nt o
f a p
aten
t, ut
ility
mod
el o
r des
ign.
The Power of Stereotypes – Heather Wallace 17
EA User Group Conference, London 16th May 2014
Model element types
Drivers Describe strategic factors that drive the definition of capabilities and guide or constrain the operational architecture
Features Describe functionality, non-functional qualities or (conceptual/logical deployment) node types at a specific level of abstraction
Roles Describe the main human actors that interact with the features at a specific level of abstraction
Data Represents data inputs to and outputs from functional features.
Assets Represent the system deliverables (System Breakdown Structure) at a specific level of abstraction
© 2
014
Airb
us D
efen
ce a
nd S
pace
– A
ll rig
hts
rese
rved
. The
repr
oduc
tion,
dis
tribu
tion
and
utili
zatio
n of
this
doc
umen
t as
wel
l as
the
com
mun
icat
ion
of it
s co
nten
ts to
oth
ers
with
out e
xpre
ss a
utho
rizat
ion
is p
rohi
bite
d. O
ffend
ers
will
be
held
liab
le fo
r the
pay
men
t of d
amag
es. A
ll rig
hts
rese
rved
in th
e ev
ent o
f the
gra
nt o
f a p
aten
t, ut
ility
mod
el o
r des
ign.
The Power of Stereotypes – Heather Wallace 18
EA User Group Conference, London 16th May 2014
To be viewed in Enterprise Architect
Note that stereotypes have been defined down to component level (not shown), but these are not yet tested or validated through use.
Model elements (stereotypes)NAV-2 Metamodel: Architecture Metamodel Elements
Requirements
Model Structure
Data
Collaborators
Information
Assets
System Roles
Features
CLAS Model Elements
«CapabilityL1»Level 1 Capability
«CapabilityL1»Level 1 Capability
«CapabilityL2»Level 2 Capability
«CapabilityL2»Level 2 Capability
«EnterpriseGoal»Enterprise Goal
«EnterpriseGoal»Enterprise Goal
«EnterpriseVision»Enterprise Vision
«EnterpriseVision»Enterprise Vision
«Environment»Environment
«Environment»Environment
«EnterpriseActivity»Enterprise-level Activity
«EnterpriseActivity»Enterprise-level Activity
«EnterpriseNode»Enterprise Node
«EnterpriseNode»Enterprise Node
«EnterpriseQuality»Enterprise Quality«EnterpriseQuality»Enterprise Quality
«EntUseCase»
Enterprise Use Case
«EntUseCase»
Enterprise Use Case
«EntQualityControl»Enterprise Quality Control
«EntQualityControl»Enterprise Quality Control
«OperationalActivity»Operational Activity
«OperationalActivity»Operational Activity
«OperationalNode»Operational Node
«OperationalNode»Operational Node
«OperationalQuality»Operational Quality
«OperationalQuality»Operational Quality
«InformationClass»Information Class
«InformationClass»Information Class
Information Item Conveyed
Information Item Conveyed
«SystemFunction»System Function
«SystemFunction»System Function
«SystemQuality»System Quality«SystemQuality»System Quality
«System»System
«System»System
«SysUseCase»
System Use Case
«SysUseCase»
System Use Case
«SysQualityControl»System Quality Control
«SysQualityControl»System Quality Control
«SEFunction»System Element Function
«SEFunction»System Element Function
«SEQuality»System Element Quality
«SEQuality»System Element Quality
«SystemElement»System Element «SystemElement»System Element
«OperationalRole»Operational Role
«ExternalNode»External Node
«ExternalNode»External Node
«ExternalSystem»External System«ExternalSystem»External System
«LogicalDataClass»Logical Data Class
«LogicalDataClass»Logical Data Class
«LogicalDataElement»Exchanged Logical Data
Element
«LogicalDataElement»Exchanged Logical Data
Element
Package
«FeatureGrouping»Feature Grouping
«FeatureGrouping»Feature Grouping
Contract Requirement Stakeholder Requirement System Requirement System Element Requirement
«IntegratedProduct»Integrated Product«IntegratedProduct»Integrated Product
«IntProductType»Integrated Product Type
«IntProductType»Integrated Product Type
«Kit»Kit
«Kit»Kit
«KitSet»Kit Set
«KitSet»Kit Set
«KitPart»Kit Part
«KitPart»Kit Part
«IntegratedSolution»Integrated Solution«IntegratedSolution»Integrated Solution
«EntSubNode»Enterprise Sub-node
«EntSubNode»Enterprise Sub-node
«GenOpRole»Generic Operational
Role
«SystemUser»System User
«BusScenario»
Business Scenario
«BusScenario»
Business Scenario
«EnterpriseRole»Enterprise Role
© 2
014
Airb
us D
efen
ce a
nd S
pace
– A
ll rig
hts
rese
rved
. The
repr
oduc
tion,
dis
tribu
tion
and
utili
zatio
n of
this
doc
umen
t as
wel
l as
the
com
mun
icat
ion
of it
s co
nten
ts to
oth
ers
with
out e
xpre
ss a
utho
rizat
ion
is p
rohi
bite
d. O
ffend
ers
will
be
held
liab
le fo
r the
pay
men
t of d
amag
es. A
ll rig
hts
rese
rved
in th
e ev
ent o
f the
gra
nt o
f a p
aten
t, ut
ility
mod
el o
r des
ign.
The Power of Stereotypes – Heather Wallace 19
EA User Group Conference, London 16th May 2014
Link reasons
Example
Justification A system element function is justified through its contribution to a system use case
Fulfilment An enterprise quality control is fulfilled by one or more system qualities
Qualification An enterprise use case is constrained by one or more enterprise quality controls
Integrity An external flow from an activity is represented on a needline between the corresponding internal and external nodes.
Requirement Link An integrated product informs 1 or more system L0 deployment requirements.
Design Link A stakeholder functional requirement is informed by a single enterprise use case.
© 2
014
Airb
us D
efen
ce a
nd S
pace
– A
ll rig
hts
rese
rved
. The
repr
oduc
tion,
dis
tribu
tion
and
utili
zatio
n of
this
doc
umen
t as
wel
l as
the
com
mun
icat
ion
of it
s co
nten
ts to
oth
ers
with
out e
xpre
ss a
utho
rizat
ion
is p
rohi
bite
d. O
ffend
ers
will
be
held
liab
le fo
r the
pay
men
t of d
amag
es. A
ll rig
hts
rese
rved
in th
e ev
ent o
f the
gra
nt o
f a p
aten
t, ut
ility
mod
el o
r des
ign.
The Power of Stereotypes – Heather Wallace 20
EA User Group Conference, London 16th May 2014
Links and their fundamental roles
Current level of abstraction
ExchangedData
Data Model Entity
Justificationto higher-level exchanged data
Feature
Higher-levelFeature
Asset
Higher-level Asset
Requirement
Higher-levelRequirement
ContractualRequirement
Role
Qualification
Justification
Justification Fulfilment
Qualification
Qualification
Qualification
Justification
Fulfilment
Qualification
Qualification
Design Link
Requirement Link
Justification
Fulfilment
Fulfilment
JustificationFulfilment
Fulfilment
Qualification
© 2
014
Airb
us D
efen
ce a
nd S
pace
– A
ll rig
hts
rese
rved
. The
repr
oduc
tion,
dis
tribu
tion
and
utili
zatio
n of
this
doc
umen
t as
wel
l as
the
com
mun
icat
ion
of it
s co
nten
ts to
oth
ers
with
out e
xpre
ss a
utho
rizat
ion
is p
rohi
bite
d. O
ffend
ers
will
be
held
liab
le fo
r the
pay
men
t of d
amag
es. A
ll rig
hts
rese
rved
in th
e ev
ent o
f the
gra
nt o
f a p
aten
t, ut
ility
mod
el o
r des
ign.
The Power of Stereotypes – Heather Wallace 21
EA User Group Conference, London 16th May 2014
To be viewed in Enterprise Architect
This is by no means ALL of the model. With the exception of the requirement links that are not shown, this represents the meta model for our first significant technical review, the System Requirements Review.
Elements and links in red were de-prioritised.
Supported links between stereotypesNAV-2 Metamodel: Architecture Metamodel: SRR only
Operational View (NOV) - OAD Annexes
System Architection (NSV) SAD Main Document
Operational View (NOV) - OAD Main Document
Capability View (NCV) - OAD Main Document
Level 1 CapabilityLevel 1 Capability
Enterprise-level ActivityEnterprise-level Activity
Operational ActivityOperational Activity
Enterprise NodeEnterprise Node
Operational NodeOperational NodeOperational QualityOperational Quality
Information ClassInformation ClassInformation Item ConveyedInformation Item Conveyed
Enterprise Use CaseEnterprise Use Case
Level 2 CapabilityLevel 2 Capability
Enterprise GoalEnterprise GoalEnterprise VisionEnterprise Vision
Enterprise Quality ControlEnterprise Quality Control
Enterprise QualityEnterprise Quality
EnvironmentEnvironment
«OperationalRole»Operational Role
«GenOpRole»Generic Operational
Role
Enterprise Sub-nodeEnterprise Sub-node
Business ScenarioBusiness Scenario
«EnterpriseRole»Enterprise Role
System FunctionSystem Function System QualitySystem Quality
System Element System Element
SystemSystem
Integrated ProductIntegrated Product
Integrated Product TypeIntegrated Product Type
Integrated SolutionIntegrated Solution Exchanged Logical Data Element
Exchanged Logical Data Element
External SystemExternal System
«trace»
Use(Case)
Association
«trace»
Generalization
Association
«flow»InformationItem(s)
produce/consumedby (derived)
Dependency
Dependency
Dependency
«trace»
Dependency«trace»
Dependency
«trace»
Generalization
Association Association
Associaiton
«trace»
LogicalDataElement(s)«flow»
Association
Association
«trace»
produced/consumedby (derived)
Use(Case)
«trace»
Association
produced/consumedby (derived)
«trace»
«flow»InformationItem(s)
Control Flow
Association
produce/consumedby (derived)
Association
«flow»InformationItems
produced/consumedby (derived)
«trace»
Control Flow
Use(Case)
«trace»«trace»
Use(Case)
«trace»
«trace»
«trace»
Use(Case)
«trace»
«trace»
Dependency
Nesting
«trace»
«trace»
«flow»InformationItems(s)
produced/consumedby (derived)
Association
«trace»
Association
Association
Association
© 2
014
Airb
us D
efen
ce a
nd S
pace
– A
ll rig
hts
rese
rved
. The
repr
oduc
tion,
dis
tribu
tion
and
utili
zatio
n of
this
doc
umen
t as
wel
l as
the
com
mun
icat
ion
of it
s co
nten
ts to
oth
ers
with
out e
xpre
ss a
utho
rizat
ion
is p
rohi
bite
d. O
ffend
ers
will
be
held
liab
le fo
r the
pay
men
t of d
amag
es. A
ll rig
hts
rese
rved
in th
e ev
ent o
f the
gra
nt o
f a p
aten
t, ut
ility
mod
el o
r des
ign.
EA User Group Conference, London 16th May 2014
MDG TECHNOLOGY IMPLEMENTATION4
DETERMINATION OF STEREOTYPES (AND THEIR USE)
© 2
014
Airb
us D
efen
ce a
nd S
pace
– A
ll rig
hts
rese
rved
. The
repr
oduc
tion,
dis
tribu
tion
and
utili
zatio
n of
this
doc
umen
t as
wel
l as
the
com
mun
icat
ion
of it
s co
nten
ts to
oth
ers
with
out e
xpre
ss a
utho
rizat
ion
is p
rohi
bite
d. O
ffend
ers
will
be
held
liab
le fo
r the
pay
men
t of d
amag
es. A
ll rig
hts
rese
rved
in th
e ev
ent o
f the
gra
nt o
f a p
aten
t, ut
ility
mod
el o
r des
ign.
The Power of Stereotypes – Heather Wallace 23
EA User Group Conference, London 16th May 2014
To be expanded in Enterprise Architect
MDG scope & structure
Stereotypes & their styles Enumerations
Diagram types
Diagram toolboxes
class CLAS Profile
SystemFunction
+ _image = <Image type="EA...+ _metatype = SystemFunction+ _sizeX = 160+ _sizeY = 80
«metaclass»Activity
+ isReadOnly :Boolean = false+ isSingleExecution :Boolean+ parameterName :String+ postcondition :String+ precondition :String
SEFunction
+ _image = <Image type="EA...+ _metatype = SEFunction+ _sizeX = 160+ _sizeY = 80
«metaclass»Component
+ isIndirectlyInstantiated :Boolean = true
SystemElement
+ _image = <Image type="EA...+ _metatype = SystemElement+ _sizeX = 160+ _sizeY = 80+ role :SERole = Core A
«metaclass»Association
+ direction :Direction = Source -> Desti...
BelongsTo
ComponentFunction
+ _image = <Image type="EA...+ _metatype = ComponentFunction+ _sizeX = 160+ _sizeY = 80
«metaclass»Class
+ isActive :Boolean
«metaclass»Node
+ _defaultDiagramType :string = CLAS NSV Diagra...+ isExecutionEnvironment :Boolean = false
«metaclass»UseCase
+ _defaultDiagramType :string = CLAS NSV Diagra...
CapabilityL1
+ _image = <Image type="EA...+ _metatype = CapabilityL1+ _sizeX = 160+ _sizeY = 80+ MeasurableProperty+ QualitativeProperty
LogicalDataElement
+ _image = <Image type="EA...+ _metatype = LogicalDataElement+ _sizeX = 160+ _sizeY = 80
OperationalQuality
+ _image = <Image type="EA...+ _metatype = OperationalQuality+ _sizeX = 160+ _sizeY = 80+ AvailabilityTarget+ CoverageTarget+ TimeTarget
SystemQuality
+ _image = <Image type="EA...+ _metatype = SystemQuality+ _sizeX = 160+ _sizeY = 80
SysQualityControl
+ _image = <Image type="EA...+ _metatype = SysQualityControl+ _sizeX = 160+ _sizeY = 80
SEQuality
+ _image = <Image type="EA...+ _metatype = SEQuality+ _sizeX = 160+ _sizeY = 80
SysUseCase
+ _image = <Image type="EA...+ _metatype = SysUseCase+ _sizeX = 160+ _sizeY = 90
SEUseCase
+ _image = <Image type="EA...+ _metatype = SEUseCase+ _sizeX = 160+ _sizeY = 90SEQualityControl
+ _image = <Image type="EA...+ _metatype = SEQualityControl+ _sizeX = 160+ _sizeY = 80
ComponentQuality
+ _image = <Image type="EA...+ _metatype = ComponentQuality+ _sizeX = 160+ _sizeY = 80
System
+ _image = <Image type="EA...+ _metatype = System+ _sizeX = 160+ _sizeY = 80
Component
+ _image = <Image type="EA...+ _metatype = Component+ _sizeX = 160+ _sizeY = 80+ role :ComponentRole = Core
OperationalNode
- _image = <Image type="EA...- _metatype = OperationalNode+ _sizeX = 160+ _sizeY = 80
«metaclass»Dependency
+ direction :Direction = Source -> Desti...
FeatureGrouping
+ _image = <Image type="EA...+ _metatype = FeatureGrouping+ _sizeX = 200+ _sizeY = 300
AppliesTo
ContributesProduce
Consume Use
Meets
«metaclass»Port
+ isBehavior :Boolean = false+ isConjugated :Boolean = false+ isService :Boolean = true
InformationItem
+ _image = <Image type="EA...+ _metatype = InformationItem+ _sizeX = 160+ _sizeY = 80
InformationClass
+ _image = <Image type="EA...+ _metatype = InformationClass+ _sizeX = 160+ _sizeY = 80
LogicalDataClass
+ _image = <Image type="EA...+ _metatype = LogicalDataClass+ _sizeX = 160+ _sizeY = 80
OperationalActivity
+ _image = <Image type="EA...+ _metatype = OperationalActivity+ _sizeX = 160+ _sizeY = 80
EnterpriseNode
+ _image = <Image type="EA...+ _metatype = EnterpriseNode+ _sizeX = 160+ _sizeY = 80
EnterpriseActivity
+ _image = <Image type="EA...+ _metatype = EnterpriseActivity+ _sizeX = 160+ _sizeY = 80
OperationalRole
+ _metatype = OperationalRole
«metaclas...Actor
ExternalActor
+ _metatype = ExternalActor
SystemUser
+ _metatype = SystemUser
ContractReq
+ _metatype = ContractReq
«metaclas...Requirement
ExternalNode
+ _image = <Image type="EA...+ _metatype = ExternalNode+ _sizeX = 160+ _sizeY = 80
ExternalSystem
+ _image = <Image type="EA...+ _metatype = ExternalSystem+ _sizeX = 160+ _sizeY = 80
EntUseCase
+ _image = <Image type="EA...+ _metatype = EntUseCase+ _sizeX = 160+ _sizeY = 90
CapabilityL2
+ _image = <Image type="EA...+ _metatype = CapabilityL2+ _sizeX = 160+ _sizeY = 80+ MeasurableProperty+ QualitativeProperty
Environment
+ _image = <Image type="EA...+ _metatype = Environment+ _sizeX = 160+ _sizeY = 80
EnterpriseVision
+ _image = <Image type="EA...+ _metatype = EnterpriseVision+ _sizeX = 160+ _sizeY = 80
EnterpriseGoal
+ _image = <Image type="EA...+ _metatype = EnterpriseGoal+ _sizeX = 160+ _sizeY = 80
EnterpriseQuality
+ _image = <Image type="EA...+ _metatype = EnterpriseQuality+ _sizeX = 160+ _sizeY = 80
EntQualityControl
+ _image = <Image type="EA...+ _metatype = EntQualityControl+ _sizeX = 160+ _sizeY = 80+ AvailabilityTarget+ CoverageTarget+ TimeTarget
IntProductType
+ _image = <Image type="EA...+ _metatype = IntProductType+ _sizeX = 160+ _sizeY = 80
IntegratedProduct
+ _image = <Image type="EA...+ _metatype = IntegratedProduct+ _sizeX = 160+ _sizeY = 80
Kit
+ _image = <Image type="EA...+ _metatype = Kit+ _sizeX = 160+ _sizeY = 80+ kitType :Kit Type
«enumeration»Kit Type
Site Kit Platform Interface Kit Base Kit Modification Kit Mission Kit Protection Kit Comms Kit Service Kit
«enumeration»Kit Part Type
CFE COTS OEM Product Asset Other Part Type
KitPart
+ _image = <Image type="EA...+ _metatype = KitPart+ _sizeX = 160+ _sizeY = 80+ kitPartType :Kit Part Type
IntegratedSolution
+ _image = <Image type="EA...+ _metatype = IntegratedSolution+ _sizeX = 160+ _sizeY = 80+ IntSolnType :Integrated Solution Type
IntPConnection
+ _image = <Image type="EA...+ _metatype = IntPConnection+ _sizeX = 15+ _sizeY = 15
KitConnection
+ _image = <Image type="EA...+ _metatype = KitConnection+ _sizeX = 15+ _sizeY = 15
KPConnection
+ _image = <Image type="EA...+ _metatype = KPConnection+ _sizeX = 15+ _sizeY = 15
«enumeration»Integrated Solution Type
Standard Solution Project Solution
«enumeration»Kit Set Type
Formal Set Constrained Set
KitSet
+ _image = <Image type="EA...+ _metatype = KitSet+ _sizeX = 160+ _sizeY = 80+ kitSetType :Kit Set Type
EntSubNode
- _image = <Image type="EA...- _metatype = EntSubNode+ _sizeX = 160+ _sizeY = 80
GenOpRole
+ _metatype = GenOpRole
BusScenario
+ _image = <Image type="EA...+ _metatype = BusinessScenario+ _sizeX = 160+ _sizeY = 90
EnterpriseRole
+ _metatype = EnterpriseRole
class CLAS NCV Diagram Types
«metaclass»Diagram_Logical
+ diagramID = NCV-1 Vision:+ frameString = #DGMID# #DGMNAME#+ pdata = HideAtts=1;Hide...+ styleex = HideQuals=1;NoF...+ toolbox = NCV-1 Capabilit...
NCV-1 Capability
Vision
«metaclass»Diagram_Logical
+ diagramID = NCV-2.Taxonomy:+ frameString = #DGMID# #DGMNAME#+ pdata = HideAtts=1;Hide...+ styleex = HideQuals=1;NoF...+ toolbox = NCV-2 Capabilit...
NCV-2.1 Capability Taxonomy
«metaclass»Diagram_Logical
+ diagramID = NCV-3 Phasing:+ frameString = #DGMID# #DGMNAME#+ pdata = HideAtts=1;Hide...+ styleex = HideQuals=1;NoF...+ toolbox = NCV-3 Capabilit...
NCV-3 Capability Phasing
«metaclass»Diagram_Logical
+ diagramID = NCV-4 Dependencies:+ frameString = #DGMID# #DGMNAME#+ pdata = HideAtts=1;Hide...+ styleex = HideQuals=1;NoF...+ toolbox = NCV-4 Capabilit...
NCV-4 Capability Dependencies
class NCV-1 Capability Vision Toolbox
NCV-1 Vision Tools
+ CLAS Profile::EnterpriseGoal(UML::Class) = Enterprise Goal+ CLAS Profile::EnterpriseVision(UML::Class) = Enterprise Vision+ CLAS Profile::FeatureGrouping(UML::Class) = Feature Grouping+ UML::TraceLink = Trace (goal->vision)
«metaclass»ToolboxPage
© 2
014
Airb
us D
efen
ce a
nd S
pace
– A
ll rig
hts
rese
rved
. The
repr
oduc
tion,
dis
tribu
tion
and
utili
zatio
n of
this
doc
umen
t as
wel
l as
the
com
mun
icat
ion
of it
s co
nten
ts to
oth
ers
with
out e
xpre
ss a
utho
rizat
ion
is p
rohi
bite
d. O
ffend
ers
will
be
held
liab
le fo
r the
pay
men
t of d
amag
es. A
ll rig
hts
rese
rved
in th
e ev
ent o
f the
gra
nt o
f a p
aten
t, ut
ility
mod
el o
r des
ign.
The Power of Stereotypes – Heather Wallace 24
EA User Group Conference, London 16th May 2014
MDG activation
© 2
014
Airb
us D
efen
ce a
nd S
pace
– A
ll rig
hts
rese
rved
. The
repr
oduc
tion,
dis
tribu
tion
and
utili
zatio
n of
this
doc
umen
t as
wel
l as
the
com
mun
icat
ion
of it
s co
nten
ts to
oth
ers
with
out e
xpre
ss a
utho
rizat
ion
is p
rohi
bite
d. O
ffend
ers
will
be
held
liab
le fo
r the
pay
men
t of d
amag
es. A
ll rig
hts
rese
rved
in th
e ev
ent o
f the
gra
nt o
f a p
aten
t, ut
ility
mod
el o
r des
ign.
The Power of Stereotypes – Heather Wallace 25
EA User Group Conference, London 16th May 2014
MDG use
Also creation of new element in Enterprise Architect and pre-defined tagged values
© 2
014
Airb
us D
efen
ce a
nd S
pace
– A
ll rig
hts
rese
rved
. The
repr
oduc
tion,
dis
tribu
tion
and
utili
zatio
n of
this
doc
umen
t as
wel
l as
the
com
mun
icat
ion
of it
s co
nten
ts to
oth
ers
with
out e
xpre
ss a
utho
rizat
ion
is p
rohi
bite
d. O
ffend
ers
will
be
held
liab
le fo
r the
pay
men
t of d
amag
es. A
ll rig
hts
rese
rved
in th
e ev
ent o
f the
gra
nt o
f a p
aten
t, ut
ility
mod
el o
r des
ign.
EA User Group Conference, London 16th May 2014
DOCUMENT GENERATION5
STEREOTYPE EXPLOITATION
© 2
014
Airb
us D
efen
ce a
nd S
pace
– A
ll rig
hts
rese
rved
. The
repr
oduc
tion,
dis
tribu
tion
and
utili
zatio
n of
this
doc
umen
t as
wel
l as
the
com
mun
icat
ion
of it
s co
nten
ts to
oth
ers
with
out e
xpre
ss a
utho
rizat
ion
is p
rohi
bite
d. O
ffend
ers
will
be
held
liab
le fo
r the
pay
men
t of d
amag
es. A
ll rig
hts
rese
rved
in th
e ev
ent o
f the
gra
nt o
f a p
aten
t, ut
ility
mod
el o
r des
ign.
The Power of Stereotypes – Heather Wallace 27
EA User Group Conference, London 16th May 2014
Formal documents aligned to levels of abstractionNAV-2 Metamodel: Architecture Metamodel: SRR only
Operational View (NOV) - OAD Annexes
System Architection (NSV) SAD Main Document
Operational View (NOV) - OAD Main Document
Capability View (NCV) - OAD Main Document
Level 1 CapabilityLevel 1 Capability
Enterprise-level ActivityEnterprise-level Activity
Operational ActivityOperational Activity
Enterprise NodeEnterprise Node
Operational NodeOperational NodeOperational QualityOperational Quality
Information ClassInformation ClassInformation Item ConveyedInformation Item Conveyed
Enterprise Use CaseEnterprise Use Case
Level 2 CapabilityLevel 2 Capability
Enterprise GoalEnterprise GoalEnterprise VisionEnterprise Vision
Enterprise Quality ControlEnterprise Quality Control
Enterprise QualityEnterprise Quality
EnvironmentEnvironment
«OperationalRole»Operational Role
«GenOpRole»Generic Operational
Role
Enterprise Sub-nodeEnterprise Sub-node
Business ScenarioBusiness Scenario
«EnterpriseRole»Enterprise Role
System FunctionSystem Function System QualitySystem Quality
System Element System Element
SystemSystem
Integrated ProductIntegrated Product
Integrated Product TypeIntegrated Product Type
Integrated SolutionIntegrated Solution Exchanged Logical Data Element
Exchanged Logical Data Element
External SystemExternal System
«trace»
Use(Case)
Association
«trace»
Generalization
Association
«flow»InformationItem(s)
produce/consumedby (derived)
Dependency
Dependency
Dependency
«trace»
Dependency«trace»
Dependency
«trace»
Generalization
Association Association
Associaiton
«trace»
LogicalDataElement(s)«flow»
Association
Association
«trace»
produced/consumedby (derived)
Use(Case)
«trace»
Association
produced/consumedby (derived)
«trace»
«flow»InformationItem(s)
Control Flow
Association
produce/consumedby (derived)
Association
«flow»InformationItems
produced/consumedby (derived)
«trace»
Control Flow
Use(Case)
«trace»«trace»
Use(Case)
«trace»
«trace»
«trace»
Use(Case)
«trace»
«trace»
Dependency
Nesting
«trace»
«trace»
«flow»InformationItems(s)
produced/consumedby (derived)
Association
«trace»
Association
Association
Association
Operational Architecture Description
Operational Design Description (OAD Annexes)• Operational Activity Design• Operational Deployment Design• Operational Quality Design
System Architecture Description
© 2
014
Airb
us D
efen
ce a
nd S
pace
– A
ll rig
hts
rese
rved
. The
repr
oduc
tion,
dis
tribu
tion
and
utili
zatio
n of
this
doc
umen
t as
wel
l as
the
com
mun
icat
ion
of it
s co
nten
ts to
oth
ers
with
out e
xpre
ss a
utho
rizat
ion
is p
rohi
bite
d. O
ffend
ers
will
be
held
liab
le fo
r the
pay
men
t of d
amag
es. A
ll rig
hts
rese
rved
in th
e ev
ent o
f the
gra
nt o
f a p
aten
t, ut
ility
mod
el o
r des
ign.
The Power of Stereotypes – Heather Wallace 28
EA User Group Conference, London 16th May 2014
eaDocX templates structure
•Minimum number of templates– OAD main document TEMPLATE– OAD annex TEMPLATE– SAD TEMPLATE– ..to be extended for SAD annexes
•Standard / alternative introductions
•95%+ model driven content– Package-driven core content– Element reports for traceability sections
To be expanded in Enterprise Architect (if time)
© 2
014
Airb
us D
efen
ce a
nd S
pace
– A
ll rig
hts
rese
rved
. The
repr
oduc
tion,
dis
tribu
tion
and
utili
zatio
n of
this
doc
umen
t as
wel
l as
the
com
mun
icat
ion
of it
s co
nten
ts to
oth
ers
with
out e
xpre
ss a
utho
rizat
ion
is p
rohi
bite
d. O
ffend
ers
will
be
held
liab
le fo
r the
pay
men
t of d
amag
es. A
ll rig
hts
rese
rved
in th
e ev
ent o
f the
gra
nt o
f a p
aten
t, ut
ility
mod
el o
r des
ign.
The Power of Stereotypes – Heather Wallace 29
EA User Group Conference, London 16th May 2014
eaDocX profiles tailor output for each stereotype
© 2
014
Airb
us D
efen
ce a
nd S
pace
– A
ll rig
hts
rese
rved
. The
repr
oduc
tion,
dis
tribu
tion
and
utili
zatio
n of
this
doc
umen
t as
wel
l as
the
com
mun
icat
ion
of it
s co
nten
ts to
oth
ers
with
out e
xpre
ss a
utho
rizat
ion
is p
rohi
bite
d. O
ffend
ers
will
be
held
liab
le fo
r the
pay
men
t of d
amag
es. A
ll rig
hts
rese
rved
in th
e ev
ent o
f the
gra
nt o
f a p
aten
t, ut
ility
mod
el o
r des
ign.
EA User Group Conference, London 16th May 2014
DOORS INTEGRATION6
STEREOTYPE EXPLOITATION
© 2
014
Airb
us D
efen
ce a
nd S
pace
– A
ll rig
hts
rese
rved
. The
repr
oduc
tion,
dis
tribu
tion
and
utili
zatio
n of
this
doc
umen
t as
wel
l as
the
com
mun
icat
ion
of it
s co
nten
ts to
oth
ers
with
out e
xpre
ss a
utho
rizat
ion
is p
rohi
bite
d. O
ffend
ers
will
be
held
liab
le fo
r the
pay
men
t of d
amag
es. A
ll rig
hts
rese
rved
in th
e ev
ent o
f the
gra
nt o
f a p
aten
t, ut
ility
mod
el o
r des
ign.
The Power of Stereotypes – Heather Wallace 31
EA User Group Conference, London 16th May 2014
DOORS sync Enterprise Architect
Requirements
Architecture Elements& Traces
1. Requirements imported into Enterprise Architect (EA), using DOORS MDG Link2. Links created directly in EA, between imported requirements and architecture elements3. Architecture elements of specific stereotypes exported back to DOORS via eaXL, including
requirement links.4. The links are replicated automatically (by DXL scripts) inside DOORS, between requirements
– requirements and requirements – architecture elements5. All requirement-architecture links are available for requirements and architecture specs.
Requirements Specifications
Synchronisation process
Requirements KPIs
Architecture Specification
Architecture KPIs
© 2
014
Airb
us D
efen
ce a
nd S
pace
– A
ll rig
hts
rese
rved
. The
repr
oduc
tion,
dis
tribu
tion
and
utili
zatio
n of
this
doc
umen
t as
wel
l as
the
com
mun
icat
ion
of it
s co
nten
ts to
oth
ers
with
out e
xpre
ss a
utho
rizat
ion
is p
rohi
bite
d. O
ffend
ers
will
be
held
liab
le fo
r the
pay
men
t of d
amag
es. A
ll rig
hts
rese
rved
in th
e ev
ent o
f the
gra
nt o
f a p
aten
t, ut
ility
mod
el o
r des
ign.
EA User Group Conference, London 16th May 2014
INTEGRITY CHECKING7
STEREOTYPE EXPLOITATION
© 2
014
Airb
us D
efen
ce a
nd S
pace
– A
ll rig
hts
rese
rved
. The
repr
oduc
tion,
dis
tribu
tion
and
utili
zatio
n of
this
doc
umen
t as
wel
l as
the
com
mun
icat
ion
of it
s co
nten
ts to
oth
ers
with
out e
xpre
ss a
utho
rizat
ion
is p
rohi
bite
d. O
ffend
ers
will
be
held
liab
le fo
r the
pay
men
t of d
amag
es. A
ll rig
hts
rese
rved
in th
e ev
ent o
f the
gra
nt o
f a p
aten
t, ut
ility
mod
el o
r des
ign.
The Power of Stereotypes – Heather Wallace 33
EA User Group Conference, London 16th May 2014
KPIs are major measures of maturity applied to a whole NAF view or level of abstraction.
e.g. Operational Design KPI
Indicators present a significant aspect of the maturity within a KPI. They reflectelement maturity or link maturity
e.g. Operational Design Justification KPI
KPI
KPIINDICATOR
INDICATOR
INDICATORKPIINDICATOR
INDICATORINDICATOR
METRIC
METRIC
METRIC
METRIC
METRIC
METRIC
METRIC
METRIC
METRICMETRIC
METRIC
METRIC
METRIC
METRIC
METRICMETRICMETRIC
Metrics represent specific measurements (usually based on counts) that contribute to an indicator. Metrics are specific to a stereotype or a link between a pair of stereotypes e.g. System functions elaborated as system use cases (fulfilment metric)
Measuring maturity (currently eaXL)
© 2
014
Airb
us D
efen
ce a
nd S
pace
– A
ll rig
hts
rese
rved
. The
repr
oduc
tion,
dis
tribu
tion
and
utili
zatio
n of
this
doc
umen
t as
wel
l as
the
com
mun
icat
ion
of it
s co
nten
ts to
oth
ers
with
out e
xpre
ss a
utho
rizat
ion
is p
rohi
bite
d. O
ffend
ers
will
be
held
liab
le fo
r the
pay
men
t of d
amag
es. A
ll rig
hts
rese
rved
in th
e ev
ent o
f the
gra
nt o
f a p
aten
t, ut
ility
mod
el o
r des
ign.
EA User Group Conference, London 16th May 2014
NEXT STEPS8
AND FINALLY…
© 2
014
Airb
us D
efen
ce a
nd S
pace
– A
ll rig
hts
rese
rved
. The
repr
oduc
tion,
dis
tribu
tion
and
utili
zatio
n of
this
doc
umen
t as
wel
l as
the
com
mun
icat
ion
of it
s co
nten
ts to
oth
ers
with
out e
xpre
ss a
utho
rizat
ion
is p
rohi
bite
d. O
ffend
ers
will
be
held
liab
le fo
r the
pay
men
t of d
amag
es. A
ll rig
hts
rese
rved
in th
e ev
ent o
f the
gra
nt o
f a p
aten
t, ut
ility
mod
el o
r des
ign.
The Power of Stereotypes – Heather Wallace 35
EA User Group Conference, London 16th May 2014
Architecture meta-model• Validate system element level meta-model through continued enhancement of Client Project
A model to achieve reference solution architecture and system element requirements (L1).
• Consider extent to which the approach can be flowed down another level to component architecture and (L2) requirements.
• Revisit system breakdown to better reflect system of systems (Meta-system as top level?)
Process enhancement• Shape scripts to enhance deployment model
• Improve efficiency around integrity checking through some mechanism of automation. (Requires investigation of options.)
• Determine and incorporate optimum solution for variant management (architecture and associated requirements)
Next steps (wish list)
© 2
014
Airb
us D
efen
ce a
nd S
pace
– A
ll rig
hts
rese
rved
. The
repr
oduc
tion,
dis
tribu
tion
and
utili
zatio
n of
this
doc
umen
t as
wel
l as
the
com
mun
icat
ion
of it
s co
nten
ts to
oth
ers
with
out e
xpre
ss a
utho
rizat
ion
is p
rohi
bite
d. O
ffend
ers
will
be
held
liab
le fo
r the
pay
men
t of d
amag
es. A
ll rig
hts
rese
rved
in th
e ev
ent o
f the
gra
nt o
f a p
aten
t, ut
ility
mod
el o
r des
ign.
EA User Group Conference, London 16th May 2014
KEY MESSAGES9
AND FINALLY…
© 2
014
Airb
us D
efen
ce a
nd S
pace
– A
ll rig
hts
rese
rved
. The
repr
oduc
tion,
dis
tribu
tion
and
utili
zatio
n of
this
doc
umen
t as
wel
l as
the
com
mun
icat
ion
of it
s co
nten
ts to
oth
ers
with
out e
xpre
ss a
utho
rizat
ion
is p
rohi
bite
d. O
ffend
ers
will
be
held
liab
le fo
r the
pay
men
t of d
amag
es. A
ll rig
hts
rese
rved
in th
e ev
ent o
f the
gra
nt o
f a p
aten
t, ut
ility
mod
el o
r des
ign.
The Power of Stereotypes – Heather Wallace 37
EA User Group Conference, London 16th May 2014
• Stereotypes provide a valuable mechanism for verifying the integrity of your model, particularly with respect to appropriate tracing of requirements.
• Stereotypes (coupled with eaDocX), allow for great flexibility of output, tailored for specific audiences.
• MDG technologies help modellers apply the right stereotypes in the right contexts. Rapid learning curve.
• MDG technologies can be created as simple UML profile extensions with no need for coding skills.
• MDG technologies need to be maintained as best practice is updated to reflect lessons learned. This requires a high level of discipline to ensure all impacts of each change are fully reflected.
• Based on the comparison of Client project A and the current project, significant productivity gains can be achieved through MDG-based stereotype application.
Key Messages
© 2
014
Airb
us D
efen
ce a
nd S
pace
– A
ll rig
hts
rese
rved
. The
repr
oduc
tion,
dis
tribu
tion
and
utili
zatio
n of
this
doc
umen
t as
wel
l as
the
com
mun
icat
ion
of it
s co
nten
ts to
oth
ers
with
out e
xpre
ss a
utho
rizat
ion
is p
rohi
bite
d. O
ffend
ers
will
be
held
liab
le fo
r the
pay
men
t of d
amag
es. A
ll rig
hts
rese
rved
in th
e ev
ent o
f the
gra
nt o
f a p
aten
t, ut
ility
mod
el o
r des
ign.
EA User Group Conference, London 16th May 2014
UESTIONS ?Q