The Power of Stereotypes

©2014AirbusDefenceandSpace–Allrightsreserved.Thereproduction,distributionandutilizationofthisdocumentaswellasthecommunicationofitscontentstootherswithoutexpressauthorizationis
prohibited.Offenderswillbeheldliableforthepaymentofdamages.Allrightsreservedintheeventofthegrantofapatent,utilitymodelordesign.
EA User Group Conference, London 16th May 2014
1Date
The Power of Stereotypes
Architecture Management for the Border Security Product Line
at AIRBUS Defence & Space
Heather Wallace
Principal Systems Engineer / Architecture Manager

The Power of Stereotypes – Heather Wallace 2
A Little Background
1. Old issues and new challenges
2. A cunning plan
Determination of Stereotypes (and their Use)
3. Metamodel and EA project structure
4. MDG technology implementation
Stereotype Exploitation
5. Document generation
6. DOORS integration
7. Integrity checking
And Finally…
8. Next steps
9. Key messages
Contents

OLD ISSUES AND NEW CHALLENGES
1
A LITTLE BACKGROUND

The border security context
NOV-1 Concept: Border Surveillance and Response Overview

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 Elements
Supporting System Elements
Legend
«SystemElement»
Command & Control
«SystemElement»
Command & Control
«SystemElement»
Surveillance
«SystemElement»
Surveillance
«SystemElement»
Intelligence
«SystemElement»
Intelligence
«SystemElement»
Training & Simulation
«SystemElement»
Training & Simulation

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
REUSE
REUSE REUSE
ROADMAP

Enterprise Features
Stakeholder
Reqs
Lead to
OperationalArchitecture
Description
System L0 Features
System L0
Reqs
Lead to
System Element
Features
System
Element
Reqs
Lead to
Specification to
Subsystems
analysis
SystemArchitecture
DescriptionMainDocument
(SystemBlackBox)
SADDesign
Descriptions
(SystemWhiteBox)
OperationalArchitectureSystemArchitecture
SADSE
Specification
(SEBlackBox)
analysis
analysis
analysis
Contract
Reqs
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

Client Project A – effective but inefficient approach

3-stream
architecture
Inconsistencies
between streams

High traceability
Complex set of
link types

Substantial team
effort
Errors and
misinterpretations

Informative
decompositions
High maintenance
(link-hiding)

Validated L0
system arch /design
Static operational
architecture

Requirements
integration
Late identification
of trace gaps

Effective
documentation
Navigation issues
(order of elements)

Reference Architecture – additional challenges
New team of
20 architects
& analysts
Kit-based
product variants
Multiple client
projects and goals
Commercial considerations
– finding the quality
“sweet-spot”

A CUNNING PLAN
2
A LITTLE BACKGROUND

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)
MDG
Stereotypes
Diagrams
Kit-based product variants
Static 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)

Model conversion and enhancement
Determine
target
metamodel
Convert Client
Project A
local copy
Upload to SQL
Server
Enhance as
reference
architecture
Manage
reference
architecture
Create MDG
technology
Use MDG
technology
Maintain MDG
technology

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

METAMODEL AND EA PROJECT STRUCTURE
3
DETERMINATION OF STEREOTYPES (AND THEIR USE)

Levels of abstraction
NAF Capability View Enterprise capability level – abstracted view of enterprise
needs
NAF 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 analysis
Operational 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 analysis
System element level – black box view of what the system
element must achieve. Basis for derived system element (L1)
requirements
….

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)

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

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»
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

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.

Links and their fundamental roles
Current level of abstraction
Exchanged
Data
Data Model
Entity
Justification
to higher-level
exchanged data
Feature
Higher-level
Feature
Asset
Higher-level
Asset
Requirement
Higher-level
Requirement
Contractual
Requirement
Role
Qualification
Justification
Justification Fulfilment
Qualification
Qualification
Qualification
Justification
Fulfilment
Qualification
Qualification
Design Link
Requirement Link
Justification
Fulfilment
Fulfilment
Justification
Fulfilment
Fulfilment
Qualification

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 stereotypes
NAV-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 Node
Operational QualityOperational Quality
Information ClassInformation ClassInformation Item ConveyedInformation Item Conveyed
Enterprise Use CaseEnterprise Use Case
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 ElementSystem Element
SystemSystem
Integrated ProductIntegrated Product
Integrated Product TypeIntegrated Product Type
Integrated SolutionIntegrated Solution
Element
Element
External SystemExternal System
«trace»
Use(Case)
Association
«trace»
Generalization
Association
«flow»
Information
Item(s)
produce/consumed
by (derived)
Dependency
Dependency
Dependency
«trace»
Dependency
«trace»
Dependency
«trace»
Generalization
Association Association
Associaiton
«trace»
LogicalDataElement(s)
«flow»
Association
Association
«trace»
produced/consumed
by (derived)
Use(Case)
«trace»
Association
produced/consumed
by (derived)
«trace»
«flow»
InformationItem(s)
Control Flow
Association
produce/consumed
by (derived)
Association
«flow»
InformationItems
produced/consumed
by (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/consumed
by (derived)
Association
«trace»
Association
Association
Association

MDG TECHNOLOGY IMPLEMENTATION
4
DETERMINATION OF STEREOTYPES (AND THEIR USE)

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
+ _metatype = SEFunction
+ _sizeX = 160
+ _sizeY = 80
«metaclass»
Component
+ isIndirectlyInstantiated :Boolean = true
SystemElement
+ _metatype = SystemElement
+ _sizeX = 160
+ _sizeY = 80
+ role :SERole = Core A
«metaclass»
Association
+ direction :Direction = Source -> Desti...
BelongsTo
ComponentFunction
+ _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
+ _metatype = CapabilityL1
+ _sizeX = 160
+ _sizeY = 80
+ MeasurableProperty
+ QualitativeProperty
LogicalDataElement
+ _metatype = LogicalDataElement
+ _sizeX = 160
+ _sizeY = 80
OperationalQuality
+ _metatype = OperationalQuality
+ _sizeX = 160
+ _sizeY = 80
+ AvailabilityTarget
+ CoverageTarget
+ TimeTarget
SystemQuality
+ _metatype = SystemQuality
+ _sizeX = 160
+ _sizeY = 80
SysQualityControl
+ _metatype = SysQualityControl
+ _sizeX = 160
+ _sizeY = 80
SEQuality
+ _metatype = SEQuality
+ _sizeX = 160
+ _sizeY = 80
SysUseCase
+ _metatype = SysUseCase
+ _sizeX = 160
+ _sizeY = 90
SEUseCase
+ _metatype = SEUseCase
+ _sizeX = 160
+ _sizeY = 90SEQualityControl
+ _metatype = SEQualityControl
+ _sizeX = 160
+ _sizeY = 80
ComponentQuality
+ _metatype = ComponentQuality
+ _sizeX = 160
+ _sizeY = 80
System
+ _metatype = System
+ _sizeX = 160
+ _sizeY = 80
Component
+ _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
+ _metatype = FeatureGrouping
+ _sizeX = 200
+ _sizeY = 300
AppliesTo
ContributesProduce
Consume Use
Meets
«metaclass»
Port
+ isBehavior :Boolean = false
+ isConjugated :Boolean = false
+ isService :Boolean = true
InformationItem
+ _metatype = InformationItem
+ _sizeX = 160
+ _sizeY = 80
InformationClass
+ _metatype = InformationClass
+ _sizeX = 160
+ _sizeY = 80
LogicalDataClass
+ _metatype = LogicalDataClass
+ _sizeX = 160
+ _sizeY = 80
OperationalActivity
+ _metatype = OperationalActivity
+ _sizeX = 160
+ _sizeY = 80
EnterpriseNode
+ _metatype = EnterpriseNode
+ _sizeX = 160
+ _sizeY = 80
EnterpriseActivity
+ _metatype = EnterpriseActivity
+ _sizeX = 160
+ _sizeY = 80
OperationalRole
+ _metatype = OperationalRole
«metaclas...
Actor
ExternalActor
+ _metatype = ExternalActor
SystemUser
+ _metatype = SystemUser
ContractReq
+ _metatype = ContractReq
«metaclas...
Requirement
ExternalNode
+ _metatype = ExternalNode
+ _sizeX = 160
+ _sizeY = 80
ExternalSystem
+ _metatype = ExternalSystem
+ _sizeX = 160
+ _sizeY = 80
EntUseCase
+ _metatype = EntUseCase
+ _sizeX = 160
+ _sizeY = 90
CapabilityL2
+ _metatype = CapabilityL2
+ _sizeX = 160
+ _sizeY = 80
+ MeasurableProperty
+ QualitativeProperty
Environment
+ _metatype = Environment
+ _sizeX = 160
+ _sizeY = 80
EnterpriseVision
+ _metatype = EnterpriseVision
+ _sizeX = 160
+ _sizeY = 80
EnterpriseGoal
+ _metatype = EnterpriseGoal
+ _sizeX = 160
+ _sizeY = 80
EnterpriseQuality
+ _metatype = EnterpriseQuality
+ _sizeX = 160
+ _sizeY = 80
EntQualityControl
+ _metatype = EntQualityControl
+ _sizeX = 160
+ _sizeY = 80
+ AvailabilityTarget
+ CoverageTarget
+ TimeTarget
IntProductType
+ _metatype = IntProductType
+ _sizeX = 160
+ _sizeY = 80
IntegratedProduct
+ _metatype = IntegratedProduct
+ _sizeX = 160
+ _sizeY = 80
Kit
+ _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
+ _metatype = KitPart
+ _sizeX = 160
+ _sizeY = 80
+ kitPartType :Kit Part Type
IntegratedSolution
+ _metatype = IntegratedSolution
+ _sizeX = 160
+ _sizeY = 80
+ IntSolnType :Integrated Solution Type
IntPConnection
+ _metatype = IntPConnection
+ _sizeX = 15
+ _sizeY = 15
KitConnection
+ _metatype = KitConnection
+ _sizeX = 15
+ _sizeY = 15
KPConnection
+ _metatype = KPConnection
+ _sizeX = 15
+ _sizeY = 15
«enumeration»
Integrated Solution Type
Standard Solution
Project Solution
«enumeration»
Kit Set Type
Formal Set
Constrained Set
KitSet
+ _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
+ _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:
NCV-2.1
Capability
Taxonomy
«metaclass»
Diagram_Logical
+ diagramID = NCV-3 Phasing:
NCV-3
Capability
Phasing
«metaclass»
Diagram_Logical
+ diagramID = NCV-4 Dependencies:
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

MDG activation

MDG use
Also creation of new element in Enterprise
Architect and pre-defined tagged values

DOCUMENT GENERATION
5
STEREOTYPE EXPLOITATION

Formal documents aligned to levels of abstraction
NAV-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
Enterprise-level ActivityEnterprise-level Activity
Operational ActivityOperational Activity
Enterprise NodeEnterprise Node
Operational NodeOperational Node
Operational QualityOperational Quality
Information ClassInformation ClassInformation Item ConveyedInformation Item Conveyed
Enterprise Use CaseEnterprise Use Case
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 ElementSystem Element
SystemSystem
Integrated ProductIntegrated Product
Integrated Product TypeIntegrated Product Type
Integrated SolutionIntegrated Solution
Element
Element
External SystemExternal System
«trace»
Use(Case)
Association
«trace»
Generalization
Association
«flow»
Information
Item(s)
produce/consumed
by (derived)
Dependency
Dependency
Dependency
«trace»
Dependency
«trace»
Dependency
«trace»
Generalization
Association Association
Associaiton
«trace»
LogicalDataElement(s)
«flow»
Association
Association
«trace»
produced/consumed
by (derived)
Use(Case)
«trace»
Association
produced/consumed
by (derived)
«trace»
«flow»
InformationItem(s)
Control Flow
Association
produce/consumed
by (derived)
Association
«flow»
InformationItems
produced/consumed
by (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/consumed
by (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

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)

eaDocX profiles tailor output for each stereotype

DOORS INTEGRATION
6

Requirements
Architecture Elements
& Traces
1. Requirements imported into Enterprise Architect (EA), using DOORS MDG Link
2. Links created directly in EA, between imported requirements and architecture elements
3. 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 elements
5. All requirement-architecture links are available for requirements and architecture specs.
Requirements
Specifications
Synchronisation process
Requirements
KPIs
Architecture
Specification
Architecture
KPIs

INTEGRITY CHECKING
7

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 reflect
element maturity or link maturity
e.g. Operational Design Justification
KPI
KPI
KPI
INDICATOR
INDICATOR
INDICATOR
KPI
INDICATOR
INDICATORINDICATOR
M
ETRIC
M
ETRIC
METRIC
METRIC
METRIC
METRIC
METRIC
METRIC
METRICMETRIC
METRIC
METRIC
METRIC
METRIC
METRICM
ETRIC
M
ETRIC
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)

NEXT STEPS
8
AND FINALLY…

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)

KEY MESSAGES
9
AND FINALLY…

• 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

UESTIONS ?Q

The Power of Stereotypes

Recommended

Recommended

More Related Content

Similar to The Power of Stereotypes

Similar to The Power of Stereotypes (20)

The Power of Stereotypes