Академический Документы
Профессиональный Документы
Культура Документы
Interface Definitions
Request to proceed
Trade-off Analysis
Power-up
Report Status
Initiate Taxi
2013 Atego. All rights reserved. - May 2013 - M Hause - How to fail at MBSE
2
Model-Based Engineering
MCE (CRC)
MCE (CRC)
AWACS
LINK 16
LINK 16
AM DPCS
FAAD C3I
LINK 16
LINK 16
Patriot ICC
E-2C
AWACS ABM OC Subsystem
F/A-18 Voice Com m
Operator Interface Power
Hardware Power Generati on Hardware includes
and Distributi on M SE
Power
RIVET JOINT Data Processing Power
M CE T erm inal Power T CIM
JT IDS
Hardware
T erm inal
Software Power
Architecture Models
Power Generati on OP 5.1.1 Comm Op Info
Hardware includes support data fusion composite Host CEP Yes Binary IAW IDD Secret xx secs/xx secs xx % Table 3-3 and
Engagements
and Distributi on M SE tracking Host reqmts
IFF measurements to support
Provide SA/Support
Power OP 5.1.1 Comm Op Info data fusion and composite Host CEP Yes Binary IAW IDD Secret xx secs/xx secs xx %
Data Processing Engagements
tracking
T erm inal T CIM IFF interrogation requests to
Voice & T ADIL-B Data Provide SA/Support Respond w hen
Hardware Power OP 5.1.1 Comm Op Info support data fusion and Host CEP Yes Binary IAW IDD Secret xx secs/xx secs xx %
JT IDS Engagements requested
DDG-51 A EGIS Destroyer composite tracking
T erm inal Provide SA/Support ID Changes to support data
CG Software OP 5.1.1 Comm Op Info Host CEP Yes Binary IAW IDD Secret xx secs/xx secs xx %
Engagements fusion and composite tracking
Network Pl an Network Interface T rack Management Module Correlation Module T rack File HIC
<TITLE>System Design<TITLE>
Modul e
Network
CID Criteria
T rack Data
Attempt to
Correlate wi th
T rack Data
Request
Possible
BMDS T rack
<META http-equiv="REFRESH"
BMDS T rack
Network Track Data Receive Network Track Data
Track File
Network T rack MSG
Fil e Matches
T rack File Request
Session Activated
<!--CSSDATA:966533483-->
11 Correlate Track
Fil es
Correlated Track T rack Data Send T rack
Fil e Data
/ initiali ze
<SCRIPT src="/virtual/2000/code
Systems Models
12
<LINK rel="stylesheet" href="/
Correlation Com pl ete ( Correl ation
Manage B MDS BMDS T rack Data Correlate T racks BMDS T rack Data Results ) [ set not nul l ] / Send Results Idl e Network T rack File Received ( Fil e Data ) [ number tracks
BMDS Track
JDN Track File Data > 0 ] / Input Network T rack
Correlation S /W
Modul e 13
Veri fy CID,
Correlation, and
Assoicated T rack
Correlation Results
yes
Update T rack
Correlating T racks
Receiving Network T rack Fil e
<SCRIPT language="javascript"
Fil e Data On entry / match state vectors Data
Data
Network Do / corr state vectors
Correlation no
Interface S /W Do / corr LPE On entry / receive fil e data
Possible
Do / corr P IP Do / store track data
Create New
Do / corr RCS On exit / request matchi ng data
BMDS T rack
Do / corr CID
On exit / corr BMDS T rack #
Track Mangement S/W Modul e HIC corr fai l / i s new BMDS T rack
corr success / is corr BMDS T rack
Monitor
BMDS T rack Di spl ay Correlation
Process BMDS T rack Fil e Request Sent ( Request
) / Pull BMDS T rack Files
BMDS T rack Data BMDS T rack Fil e Data
Received ( Fi le Data ) /
T rack MSG Data
Correlate T racks
Send BMDS Receiving BMDS T rack Fil e
T rack Data to Data
JDN
Prepared T rack MSG
On entry / receive fil e data
Do / store track data
Component Models
Versi on_Number [PK1] Power
owning element T SS _E ntry_Number [PK1]
<<deri ved>> /associated data
Received Date-T i me
traces to /hi story Non-Key Attri butes A2C2 S ubsystem
local track number
Operator Interface Power
Wi ndows_Version Voice Comm
create ()
T SS _Description Hardware Power Power Generati on
recei ve ()
update ()
Hardware includes
store ()
update () destroy () and Distributi on MSE
send () retrieve ()
EPLRS or SINGARS
T erm inal
Power
Force Level Power
Control System PLGR
(GPS )
Power
2013 Atego. All rights reserved. - May 2013 - M Hause - How to fail at MBSE
4
Modeling Language for these Multiple Levels of the System
2013 Atego. All rights reserved. - May 2013 - M Hause - How to fail at MBSE
5
System Modeling with SysML
Mass
Properties
System Model Model
Efficiency
Model
Safety
Model
Cost
Engine Transmission Drive Shafts Model
2013 Atego. All rights reserved. - May 2013 - M Hause - How to fail at MBSE
11
Adopting MBSE can be hard
2013 Atego. All rights reserved. - May 2013 - M Hause - How to fail at MBSE
12
Things NOT to do when adopting MBSE
2013 Atego. All rights reserved. - May 2013 - M Hause - How to fail at MBSE
13
Dont Neglect Training and Mentoring
2013 Atego. All rights reserved. - May 2013 - M Hause - How to fail at MBSE
14
Encourage Collaboration
2013 Atego. All rights reserved. - May 2013 - M Hause - How to fail at MBSE
16
Dont Adopt an External Process Wholesale
2013 Atego. All rights reserved. - May 2013 - M Hause - How to fail at MBSE
18
Dont Look at MBSE as Duplicate Work
2013 Atego. All rights reserved. - May 2013 - M Hause - How to fail at MBSE
23
Dont Abuse Lean and Agile Development
2013 Atego. All rights reserved. - May 2013 - M Hause - How to fail at MBSE
24
Optimize Your Process
2013 Atego. All rights reserved. - May 2013 - M Hause - How to fail at MBSE
25
Dont Model Too Much, Too Early
2013 Atego. All rights reserved. - May 2013 - M Hause - How to fail at MBSE
28
Adopt a Standard Notation
The Problem: Companies buy tools first and then use them in the
same way as the existing paper-based process
This gets the least out of tools, not the most
The Solution: Paper-based and model-based processes are different
The inventors of the car did not start by inventing an electric horse
Work practices need to adapt to the paradigm shift
Processes need to adapt to make better use of tools
Project documents
Originally large paper documents, then electronic documents
Next, electronic documents with cut and paste diagrams
Need to shift to automated document generation
Requirements traceability
Originally large sheets of graph paper, then spreadsheets
Next, Requirements Management (RM) tools
Then, traceability links between RM tools and models
Need to shift toward models integrated with reqts.
2013 Atego. All rights reserved. - May 2013 - M Hause - How to fail at MBSE
30
Dont Start by Buying a Tool (Any Tool)
The Problem: Projects often buy the cheapest tool to minimize costs
Models then expand to the point where converting to a different
tool is too expensive
Projects have no choice but to carry on
Buying cheap can be very expensive
The Solution: People Process Tools
The GAO and DoD CIO found the DoD spends 40% of its RDT&T
budget on software
FY 2003 $21B, FY 2006 $30B
40% was attributed to rework efforts ($8.4B and $12B)
Recommendations included:
Increase awareness of software problems, technology, and
opportunities
Develop real incentives to share specifications, interfaces,
models, and software (e.g. ARCI program)
Apply emerging software engineering tools to appropriate
problems
Deploy system engineering methods that enable specification,
implementation, and testing to evolve together
Model driven tools can stimulate and enforce iterative systems
engineering
Description You Me
:Attendee :Speaker
{Speech Time}
1 loop while open questions exist
1.1 Question
Question
1.1.1 Answer
Answer
end loop
2013 Atego. All rights reserved. - May 2013 - M Hause - How to fail at MBSE
43