Adopting MBSE at Kongsberg Defence & Aerospace Your ...
Transcript of Adopting MBSE at Kongsberg Defence & Aerospace Your ...
KONGSBERG PROPRIETARY: This document contains KONGSBERG information which is proprietary and confidential. Any disclosure, copying, distribution or use is prohibited if not otherwise explicitly agreed with KONGSBERG in writing. Any authorised reproduction in whole or in part, must include this legend. © 2015 KONGSBERG – All rights reserved.
Your Presentation Title
Goes Here
Adopting MBSE at Kongsberg
Defence & Aerospace – Joint Strike
Missile project
June 9th 2015
Svein-Erik Soegaard
Kongsberg Defence & Aerospace
KONGSBERG PROPRIETARY: This document contains KONGSBERG information which is proprietary and confidential. Any disclosure, copying, distribution or use is prohibited if not otherwise explicitly agreed with KONGSBERG in writing. Any authorised reproduction in whole or in part, must include this legend. © 2015 KONGSBERG – All rights reserved.
MBSE using SysML Adopting MBSE in the Joint Strike Missile (JSM)
Svein-Erik Soegaard
Kongsberg Defence and Aerospace
About Presenter
Svein Erik Søgård
Senior System Engineer in JSM
10.06.2015 WORLD CLASS - through people, technology and dedication Page 3
• Svein Erik Søgård, MSc
– Principal Engineer, Missile Systems
• Engaged since 1995 at the Missile Division in
Kongsberg Defence & Aerospace (KDA)
• Background from SW development, system
integration and test in NSM (Naval Strike Missile)
• Current work (since 2010) : System Architect in JSM
and responsible for adopting MBSE using SysML
Joint Strike Missile (JSM)
• Next Generation Cruise Missile from
Kongsberg Defence and Aerospace
– Based on technology from current
generation Naval Strike Missile (NSM)
• To be integrated on the F-35 Joint Strike
Fighter (block 4)
• Contracts with the Royal Norwegian Air
Force (development) and Lockheed Martin
(aircraft integration)
10.06.2015 WORLD CLASS - through people, technology and dedication Page 4
start of develop
ment 2009
first test
F-16 platform
2015 verified 2018 deployed 2020
JSM – some key characteristics
• Many different technologies to be integrated (multi disciplinary):
– Passive Infrared Imaging Target Seeker
– multi-sensor Navigation System
– Jet Engine and bank-to-turn flight control
– In-flight radio communication (Weapon Data Link)
– on-board Flight Route Planning based on situation awareness
– programmable Fuze/Warhead
– Multicore Computing Platform
– ……
• SW intensive
– >60% of the system requirements affects SW
• >30 years product lifecycle, mid life updates
10.06.2015 5
How do we manage
this?
MBSE in the JSM Project – Initial objectives
• Establish System Architecture Model (SAM) – “The Big Picture”
– Consistent model ensuring successful functional/logical integration of
discipline components
– fulfil system requirements by tracing
– Navigation ONLY through diagrams to READ information
• Both structural drill-down and between views
– Information available outside tool -> publishing to web and some type
of docs (Requirement Specs)
– Linking related/detailed information (docs, other models etc) scoped
by the nodes in the system architecture
• Life cycle focus – System Architecture understandable for maintenance,
mid-life update, new product variants
10.06.2015 Page 7 WORLD CLASS - through people, technology and dedication
Validation
JSM Modeling scope
Define customer needs
Analyse requirements
Define concept & behaviour
Identify sub functions
Implement
Integrate
Verify system
Validate system
Verification
Establish SAM - Focus in first stage
Customer requirements,
operational concepts and
JSM System
Requirements in DOORS
Not modeling alternative
concepts and analysis in
SysML, done in separate
tools
System Architecture Framework - Views
10.06.2015 Page 9 WORLD CLASS - through people, technology and dedication
Physical
Design
• Functional - Given concept, HOW shall the
system work?
- Activity Diagrams with dataflow
• Logical - Given functional design, HOW shall
the system be constructed?
- Interfaces
- Block Diagrams
- Sequence Diagrams
• Physical - Mechanical design, 3D DMU in
Catia®
- HOW is the product assembled
(MBOM)?
Specification - WHAT shall the system do?
- Context/interfaces
- Requirements and Behavior
Views as key to
document archive
KDA Missile Reference Model
• Developed reference model – «KDA Missile Reference Model»
– Stripped down unclassified version of JSM product
• Purposes
– Define how we shall organize the model, define the Architecture
Framework
– Define which subset of SysML that should be used for which view
– Cover all modeling aspects/principles in the real product
– Basis for training and presentations
– Basis for developing customizations (validation rules, plugins etc)
• Evolved in parallel with product development
10.06.2015 WORLD CLASS - through people, technology and dedication Page 10
Navigable model: Top –level index
10.06.2015 WORLD CLASS - through people, technology and dedication Page 11
Functional System - index
10.06.2015 WORLD CLASS - through people, technology and dedication Page 12
Functional System:
Manage complexity,
context for further
functional decomposition
and functional IT&V
Functional Architecture
10.06.2015 WORLD CLASS - through people, technology and dedication Page 14
Example from Missile Reference Model
Requirements
10.06.2015 WORLD CLASS - through people, technology and dedication Page 15
Example from Missile Reference Model
Functional view
10.06.2015 WORLD CLASS - through people, technology and dedication Page 16
Example from Missile Reference Model
Navigation plugin,
Link to diagram under type
Contextualization:
Document describing
algorithm linked to function
Allocation annotation by
plugin (allocation derived
from owner of activity)
Logical design view - Functional Structure
10.06.2015 WORLD CLASS - through people, technology and dedication Page 17
Example from Missile Reference Model.
Functional System:
Manage complexity,
context for further
functional decomposition
and functional IT&V
Show logical components
in their functional context
Navigation plugin,
Link to diagram for Port
Type
Defining Behavior
10.06.2015 Page 18 WORLD CLASS - through people, technology and dedication
State and Activity
Diagrams shows external
visible behavior for
System and Components
Logical Architecture
10.06.2015 Page 19 WORLD CLASS - through people, technology and dedication
• Functional Systems • Functional breakdown
• Requirement
development and tracing
• Logical view
• Component Specifications • Information interfaces
• Allocated Requirements
• Allocated Functions
• Behavior
• Logical Architecture • Realization oriented
• Modules integrating components to a
product
• Modules have block diagrams for
different layers: information, protocol,
electrical, cabling
• Design constraints and Physical
Requirements
Missile – Logical architecture structure
10.06.2015 WORLD CLASS - through people, technology and dedication Page 20
Example from Missile Reference Model.
Logical Architecture – layers
10.06.2015 Page 21 WORLD CLASS - through people, technology and dedication
Electrical Signal view Power distribution view
Information view
Cabling view
Tracing (allocation) of
connectors between
different layers
Logical modules may have
different layers depending
on technology
Logical Architecture (Realization)
Port Allocation
10.06.2015 Page 22 WORLD CLASS - through people, technology and dedication
Example from Missile Reference Model
10.06.2015 WORLD CLASS - through people, technology and dedication Page 23
From System Design to Software Design
SW Component Specification – Flight Controller
10.06.2015 WORLD CLASS - through people, technology and dedication Page 24
Requirements
Black – Box
(Ports/Interfaces)
Behavior
(states, activitites)
Documents
(A3s, algoritms,
models etc..) Linked Non-SysML
Information
Example from Missile Reference Model
Missile – Logical architecture structure
10.06.2015 WORLD CLASS - through people, technology and dedication Page 25
Example from Missile Reference Model
Software Logical Architecture
10.06.2015 WORLD CLASS - through people, technology and dedication Page 26
Example from Missile Reference Model
Adapters to HW Adapters to HW
Realization of Logical
Components
10.06.2015 WORLD CLASS - through people, technology and dedication Page 27
Example from Missile Reference Model
Software Logical Architecture
Inheriting logical black-
boxes from the System
Architecture Model
Software Physical Architecture
10.06.2015 WORLD CLASS - through people, technology and dedication Page 28
Example from Missile Reference Model
Software: Code generation from model
10.06.2015 WORLD CLASS - through people, technology and dedication Page 29
UML
Interfaces
Generated
IDL
UML Logical
Architecture Generated
XML
(CCM
compliant) UML Physical
Architecture
Generated
C++
Interfaces
Generated
C++
Component
Configuration
Hand Coded
C++
Functional
Code
Executable Code
UML
Component
Design
Generated
C++ State
Machine
skeletons
Summary (System to SW)
• Smooth and consistent transition to SW design
– Inheriting Component black boxes with ports/Interface
• Chosen UML interfaces for information interfaces at sysML
– Tracing to other model elements (requirements, state machines,
activities)
• Challenges
– Requires frequent iterations between system and SW
– Where is the border between System and SW?
• Ground rule: Define course grained SW components at system
level, one component for a function that plays a role in its
functional system
10.06.2015 WORLD CLASS - through people, technology and dedication Page 31
Lessons learned Experiences and recommendations
Experiences and Recommendations #1
• Adopting a MBSE solution is a long journey
– It’s about learning new methodology, new architecture framework and a new
language/tool in parallel
• In JSM it took several years to get the Architecture Framework mature
– 10 Workshops and trainings (2-3 days), extensive mentoring
– MBSE test bed – tested in student project
• Many people are in general not motivated to spend much time on learning
tools, MagicDraw is not a tool for everyone
– Invest in training and mentoring, Establish core team(s) and mentor(s)
• Keeping the model update and consistent is mandatory
– Do not put too much details into the model
– Throw away duplicated/obsoleted information
– (sub)Model ownership mandatory
• SysML very expressive and powerful, but complex
– Define a language subset and a strict guideline to develop large models ->
Establish a reference model expressing which subset of sysML to use for
which purpose
10.06.2015 WORLD CLASS - through people, technology and dedication Page 32
Experiences and Recommendations #2
• Systems Engineering terminology is overloaded
– Functional versus logical versus physical? What is a system?
– Clear terminology is essential in communicating the model -> define!
– Communicate terminology with examples
• Complex System Models require well managed abstractions
– abstractions are not popular at the first glance for many
• «abstractions hiding the details that is important»
• «the information become fragmented by applying separate views»
– Framework and abstractions need to be teached frequently
• It is a challenge to develop methodology and guidelines in parallel with
product development
– Start small: Establish methodology and Architecture Framework on pilot
projects or small products/small parts of a product
– Documenting existing products components – good way to learn and establish
methodology & framework, «sandwich» process – meet in the middle
– Roll out stuff that works!
10.06.2015 WORLD CLASS - through people, technology and dedication Page 33
The recipe for success 1)
think BIG start SMALL
and EVOLVE
10.06.2015 WORLD CLASS - through people, technology and dedication Page 34
1) From presentation by Darius Silingas, No Magic
Is MBSE in JSM a success story?
We have made a good foundation
– Established SAM expressing R,F, L and P of the JSM
• > 25 systems, > 80 components, > 4000 diagrams
• 20-30 persons contributed to modeling the SAM (R,F,L)
– Precise specifications for component development, especially for SW
• Smooth transition to SW component design
• Generating code for interfaces defined in SAM
– Commitment from Management
Success so far! But we still need to improve and evolve…...
– Integration, test and verification of the next JSM product increments must be
successful
– «everyone» has to understand the model
– new employees should efficiently maintain the product
– model (elements) should be reused from JSM in other product variants
– the modeling culture must be sustainable
10.06.2015 WORLD CLASS - through people, technology and dedication Page 35
Test and verification
10.06.2015 Page 37 WORLD CLASS - through people, technology and dedication
• Add more requirements/capabilities for test and verification
• «extracted» from functional design and behavior
• Hooks for test and verification
• Define Test Specifications/Test Cases
Enovia
Enterprise
Enovia MBSE
(R F L P )
MagicDraw
Doors
Sw dev
suite Catia
Allegro
Specifications
B
O
M
Production
documents
Informal technical
documents (A3)
RFL
R
P
Executables
Future state of KDA Integrated Development Platform:
10.06.2015 WORLD CLASS - through people, technology and dedication
38
R = Requirements
F = Functional
L = Logical
P = Physical
Data originating from multiple sources are
integrated in a joint database. Using
Enovia/Catia, the data is contextualized.
Knowledge is related to the system
element(s) to which it refers
• Multi-disciplinary process
• Cross-disciplinary platform
• Model-based knowledge management