1. MBSE Usability Group Bjorn Cole Bjorn.Cole@jpl.nasa.gov
March 1, 2013 MBSE Meeting
MBSE Usability Group
Bjorn Cole

2. MBSE Usability Group – Collaboration Process
Customized Propulsion
Schematic from JPL
Identify & prioritize modeling use cases
Study exemplars for each use case
Emphasize full-scale industrial applications
Span a wide range of usage patterns
Example: Libraries use case exemplars from:
Rockwell Collins, Jet Propulsion Laboratory,
Ford Motor Company, BAE Systems, Honeywell
Synthesize and publish exemplars :
Ex: “Emerging Usability Patterns in the Application of Modeling Libraries” (Submitted to 2013 INCOSE International Symposium)
Ex: Making assertions based upon modeling (Pending in 2013)
Create a document that offers guidance on usability issues
Ex: Developing and Managing Modeling Libraries (Pending in 2013)

3. Recommendations: The User Experience
Understand libraries as a crucial corporate asset.
Make exemplars of correct usage available in templates to streamline training and work (Put the best at people’s fingertips.)
Best Practices / Process examples
Example models
Generic
Domain-Specific
Best of class algorithms
Design the user experience.
Understand your users. (Most users will not be modeling geeks!)
Keep it simple
Support flow
Make it “write once” for the modeler
Create an immersive environment for users
Persistent real time environment for training and model building
As if it was a multi-player game (Because it is!)

4. Recommendations: Supporting Collaboration
Immersive Multi-Modeler Environment
Shared awareness
Supporting spiral of meaning
Dialog about applying modeling during projects
Dialog about library objects
New insights into library components
Emerging architectural & design patterns
Dialog happens inside the modeling environment

5. Usability Group Plan for 2013
Library Guide: Developing and Managing Libraries
Use Case: Supporting Decisions with Assertions based upon MBSE models
On the side: Stand up a user forum

6. The Usability Guide Tailoring a Library Element at Rockwell Collins
Addressing MBSE Adoption with Model Templates
Domain-Specific Customization at JPL
Vehicle Model Architecture at Ford Motor Company
SoS Modeling Framework at Honeywell

7. Questions for the Group
What is our audience?
Sounds like model architects / librarians is one part of this
“Tool vendors” is a little vague – what parts of the tools?
How deep versus how wide?
Work to build an outline collaboratively up to the next meeting
What are people’s areas of interest?
Not just usability, but REusability
Libraries -> Assertions (via analysis)
Connecting to specialized tools
How to control / mark level of fidelity or assumptions?
Estimates of run time during use?
How to add fidelity as needed for a given circumstance?
Decision-making knowledge: e.g., preferred vendors, costs, familiarity
How can people find the library pieces? Central store at Rockwell?
Atego Asset Library? Subversion store?
Moving library assets across modeling tools
How / when do we infuse discipline of interface design?

8. Multi-Disciplinary Integration
Automatic Cruise Control <FAULT>
Thermal/Heat Dissipation: 780°
Ergonomic/Pedal Feedback: 34 ERGS
Hydraulic Pressure: 350 PSI
Sensor MTBF: 3000 hrs
Power Rating: 18 Amps
Hydraulic Fluid: SAE 1340 not-compliant
Multi-Disciplinary Integration
Source: INCOSE MBSE Initiative-Mark Sampson
If we can pull this off we can achieve this ultimate vision for integrated requirements…, visualizing where requirements go and how they interact with various systems… For example, …starting with the car, what are the requirements associated with the front end of this vehicle.
Shows current requirements by graphically clicking on the car…
What about changing a requirement…stopping distance
Show the potential impact of changing stopping distance including…
Thermal/heat problems with brakes
Ergonmic feedback problems with brake pedal
Hydraulic fluid rating violation
Failure modes/MTBF rating problems with sensors
Hydraulic pressure problems
Electrical fault problems
Zooming into the electrical box, highlights a fuse
Clicking into the fuse brings up the schematic and highlights a fuse link
Clicking into the schematic zooms in on the wire harness that has the problem—including the signal for a failed sensor that in this particular failure mode causes the short.
…which allows us to go look at the Failure Modes document and update appropriately.
Updating the software to handle that fault
…and even seeing the impact on our safety rating and insurance costs.
Minimum Turn Radius: 24 ft.
Dry Pavement Braking Distance at 60 MPH : 110 ft. 90 ft
Minimum Turn Radius: 24 ft.
Dry Pavement Braking Distance at 60 MPH : 110 ft. 8

9. Creating Queries
Find all US Capitals from DBPedia (semantic capture of Wikipedia):

10. Questions for the Group
Are there particular questions people have for these system models?
Any exemplars out there already?
Is there interest in doing this in parallel with the guide or should we work in series?
Assertions from models has high experience base in the analytical space; less so in SysML / UML
Libraries tie nicely into this as elements can be deployed for analysis
Insights from libraries may inform the limits / approach to making assertions
Can we separate tools from the larger question of making assertions?

11. Who would like to be the focus of discussion for next time?
Final Discussion
Who would like to be the focus of discussion for next time?
Refine outline for the library guide
Outline can help with bringing in new members
Collect ideas for assertion exemplars / needs
How would you like to see the work of this group impact the larger MBSE community?
Is anyone interested in leading the charge on either of the two topics identified at the IW?