1. Quick orientation for MBSE Usability Group
Usability Team

2. Definitions
Usability = The extent to which a product can be used by specified users to achieve specified goals with effectiveness, efficiency, and satisfaction in a specified context of use or a quality attribute that assesses how easy user interfaces are perceived to be to use. Also refers to methods for improving ease-of-use during the design process.
Task = activity performed by a single person that has a distinct beginning and end
Function = a related set of tasks, some of which may be automated (i.e., performed by a computer). May consist of multiple people performing cooperative or collaborative tasks

3. Measurable Usability Dimensions
Ease of Learning
Efficiency of Use (routine)
Efficiency of Use (non-routine)
Error Tolerance
Subjective

4. The current arc for the team started in 2011 at the INCOSE IS
Started by collecting many high-level use cases for systems engineers to do modeling
Creating libraries
Generating consequences from the current design
Working requirements
Etc.
Creating libraries was highest prioritized use cases at the IS

5. First product: Library Exemplars
The first product, finished roughly August 2012, was a paper that combined five exemplars of making library information more accessible
Using a common data bus for simulation (Judy Che, Ford)
Applying in-domain icons (Bjorn Cole, JPL)
Library curation and employment use cases (David Lempia, Rockwell)
Making user templates to ease adoption (George Sawyer)
Coordinating contributed simulations (Ron Llleyls, Honeywell)

6. So far, only have a draft of the above
Follow on
Team looked for a larger, more encompassing product – a library builders’ guide
How to build a SysML library
Good practices for embedding information
Good practices for making information apparent
Challenges imposed by SysML
So far, only have a draft of the above
~40 pages, mostly on the “how to build”

7. Highlights of Paper
Main section under work is about capturing systems engineering information for downstream users
Separates “in-domain” versus “out-of-domain” knowledge capture and support
Looks at standards for reusable software and how they might apply to systems models
Discusses various attributes of SE problems to capture
Identifies the vital nature of capturing context with library to know where to use it

8. Would like to move forward to greatest profit
Looking forward
Would like to move forward to greatest profit
Different situation than in 2011:
MBSE moving from very early prototypes to initial adoption
Many more practitioners and attempted practitioners
Strategy still key, but more practitioners demands more considerations for tactical and day-to-day experiences related to MBSE

9. Agenda for this Session
01:00-01:10
Introductions
01:10-01:30
Review current effort - Bjorn
01:30-02:30
SysML Usability Issues Brainstorm Session
02:30-03:30
Paper / Guide Outline Development
03:30-04:30
Next steps
04:30-05:00
Wrap-up and closing