MBSE Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== MBSE Usability ======

===== Purpose ===== 
ISO defines usability as "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.“

Our purpose is to identify how systems engineering languages such as SysML, processes, and supporting tools can be made easier to learn and use and to promote usability improvements.


Our definition of the Model Based Systems Engineering (MBSE) Environment is that it consists of:

  - The Language  in which people express models, (for now, predominantly SysML)
  - The Tools that people use to build and manipulate models
  - The Methods - that people follow to build models
  - Synthesis - Transcends single category

===== Measure of Success ===== 
  - Identify usability levels to focus discussions
  - Paper 1 - {{:mbse:combined_usability_exemplars_paper_mbse_usability_group.docx|2012 Usability Exemplars; 5 cases}}
  - Paper 2 - [[https://docs.google.com/document/d/1EVZNqtEumypuqymV8l3ENP5hFTLErSLjDwpsKnPtjt4/edit?usp=sharing|Library Guidelines and Usability Challenges (Focus on Meta data)]] Focused Scope on Jan 2014 IW
  - Paper 3 - [[https://docs.google.com/document/d/12BIvPKiQxdExC0UoPt87Ucb0AK2wUXB740eHCYL7EtE/edit?usp=sharing|SysML Usability Challenges (Usability Study)]] New as of Jan 2014 IW

===== Schedule ===== 

^Date^Milestone^Status^Point of Contact^
|Jan 2011|Develop Usability Use Cases|Ongoing|David Lempia|
|Nov 2012|Complete Library Exemplar Document Published|Submitted for INCOSE 2013 IS|Scott Workinger|
|Feb 2013|Condense Library Exemplar Paper to 15 pages|Ron Lyles & David Lempia|
|June 2013|Library Best Practices|Working Group Sessions at IS|Bjorn Cole|
|Jan 2014|Re-focus the Library Paper|Ready for IW|Bjorn Cole|
|Nov 2014|Complete Paper 2 & 3 for the IS 2015|Ready for IW|Bjorn Cole|

===== Team Members ===== 

^Name^Organization^Contact Information^
|Armin Mueller|ScopeSET GmbH|arminus@gmail.com |
|Dick Welling | | |
|Jen Narkevic | | |
|Lynn Baroff |NASA Engineering & Safety Center |lynnbaroff@verizon.net |
|Patricia Collins | | |
|Peter Campbell | | |
|Quoc Do | | |
|Ron Lyells |Honeywell Inc. |ron.lyells@honeywell.com |
|Scott Workinger | | |
|Tim Tritsch | | |
|Werner Altmann| | |
|Bjorn Cole| Jet Propulsion Laboratory | bjorn.cole@jpl.nasa.gov |

====== Materials ======

  * {{:mbse:emerging_usability_patterns_in_the_application_of_modeling_libraries.pdf|Emerging Usability Patterns in the application of modeling libraries, Published Feb 2013}}
  * **Emerging Usability Patterns in the Application of Modeling Libraries Abstract**: This paper summarizes the conclusions of the MBSE Usability Group for 2012. Five perspectives are offered with each perspective grounded by an exemplar from the authors’ practice using Model Based Systems Engineering Environments. These exemplars range from very detailed step-by-step descriptions with identification of fine-grained usability issues to system of systems simulations developed by geographically dispersed operations in a global company. Discussion of each exemplar within the Usability Group led to significant lessons learned for the team. This paper summarized the chief lessons learned during this process. Today, the process continues. In the words of Ron Lyells, “Usability is an emergent quality.”
  * {{:mbse:mbse_usability_working_group_use_cases_jan_31_2011_v3.doc|Usability Use Cases collected January 31, 2011}}

====== Usability Dimensions ======

A presentation on {{:mbse:what_is_usability.pptx|What is usability?}}

The usability dimensions describe key aspects of usability that are measurable during experiments. The four usability dimensions are:
  * Ease of Learning
  * Efficiency of Use (routine, non-routine)
  * Error Tolerance
  * Subjective (Satisfaction)

====== Scope ======

The scope of the usability groups work includes:
  * Process
  * Language / models (representational capabilities)
  * Tools

====== Usability Use Cases ======


Use cases will be collected that describe how a systems engineer creates engineering artifacts for a specific customer during a specific systems engineering process step. The type of information we will collect for use cases include:
  * **Goal** - What is the goal of the use case? (Focus on the produced engineering artifacts and the needs of the customer)
  * **Actors** – Who are the actors involved in this use case? Who is the customer?
  * **Usability Hypothesis** – What are the expected usability issues that may be encountered in this use case?
  * What systems engineering **process** is supported?
  * **Pre-condition** – What is the state of the tools and engineering artifacts before the use case begins. What are the inputs needed to start this use case.
  * **Post-condition** – What is the state of the tools and engineering artifacts after the use case finishes. What are the outputs from this use case.
  * **Sequence of tasks** - What are the tool independent tasks the primary actor does (Starts with a verb) (What SysML element(s) and/or diagram(s) is used?)
  * **MBSE Value Added** - What is the value added to this use case because I used MBSE as opposed to traditional methods?

**Goal - Assemble components and associated behaviors from a library of primitives to meet the mission need**
    - Actors - Architect, systems engineers/component designers, librarian, interface designer, Change Control Board
    - Process - Collaboration, Analysis & simulation, Configuration Management Tools
    - Pre-condition - Mission needs understood, Library of components, each meeting criteria for reuse
    - Post condition - Architect and collection of components, meeting the proposed mission need
    - Sequence of tasks
      - SE searches repository for components, based on criteria/desired function
      - SE selects and connects component abstractions in system model
      - SE/integrator initiates performance analysis, simulation to verify behavior
      - SE reconfigures components as necessary
**Goal - Conduct a Design Review using MBSD Environment**
    - Actors - SE, Architect/Designer, Customer, PM, Eng Mgmt, Peers
    - Process - Collect changed artifacts and supporting artifacts into a form that can be commonly sharable, i.e. document or html form. Highlight all changed items.
    - Pre-condition - Change Complete, Completed design review checklist
    - Post condition - All issues adjudicated, Ready for re-baseline
    - Sequence of tasks
      - Identify modeling artifacts and external artifacts that have changed or support the change
      - Create review artifact that is sharable across all reviewers. Artifact should highlight all changed items, both textual changes, changes to a diagrams/tables and any model element properties, including logical/physical elements, requirements, relationships, etc. 
      - Distribute review artifact and initiate review process
      - Collect issues, resolve  and capture resolution
      - Review adjudication with reviewers
      - Merge changes and re-baseline
**Goal - Make assertions on current design**
    - Actors - Accountable engineer makes assertions, reviewers evaluate
    - Process - Cross-cutting – focused on constraints
    - Pre-condition - Assertions are made, simulations and analysis run
    - Post condition - Reviews have concurred or not concurred that assertions are properly validated/tested
    - Sequence of tasks - 
**Goal - Define system architecture and conduct architectural analysis**
    - Actors - Systems engineer performing architecting function
    - Process - Many candidate methodologies for sys arch, UML/SysML diagram tips: Pkg diagrams, BDDs, Class diagrams
    - Pre-condition - Architectural approach/methodology adopted, Modeling languages and tool(s) selected, Profiles exist and have been imported
    - Post condition - System architecture (logical/conceptual) captured in system model and validated
    - Sequence of tasks - 
      - Specify architectural properties and constraints/drivers
      - Consider arch alternatives
      - Describe architecture (use views/view points)
      - Refine requirements and design
      - Develop scenarios===== Reference Links ===== 

===== Documents and Presentations ===== 
=== 2013 International Symposium ===
  * {{:mbse:mbse_usability_is_plenary_2013.pptx|MBSE Usability Plenary Slides 2013}}
  * {{:mbse:usability_group_session_1_v7.pptx|MBSE Usability Work Group Slides 2013}}

=== 2011 International Symposium ===
  * {{:mbse:2011_is_mbse_usability_collaboration_v1.ppt|Collaboration, 2011}}
  * {{:mbse:mbse_-_usability_is2011.pptx|}}
  * {{:mbse:incose_is_2011_mbse_presentation.ppt | Practical SysML Applications: A Method to Describe the Problem Space}}

=== 2011 International Workshop===
  * {{:mbse:mbse_usability_working_group_use_cases_jan_31_2011_v3.doc|Usability Use Cases collected January 31, 2011}}
  * {{:mbse:2011_iw_mbse_usability_outbrief_v2.ppt|Working Group Outbrief presented January 31, 2011}}
  * {{:mbse:incose_usability_workshop_kickoff_2011_v9.ppt|Incose Usability Kickoff 2011}}
  * {{:mbse:incose_usability_workshop_workshop_2011_v2.pptx|Incose Usability Workshop 2011}}
  * {{:mbse:mbse_usability_working_group_GroupInfo_v2.docx|Group Information Form}}
  * {{:mbse:MBSE Usability Working Group_UseCaseForm_v2.docx|Use Case Form}}
  * {{:mbse:MBSE Usability Working Group_UseCaseForm Examples.docx|Use Case Examples}}
  * {{:mbse:MBSE Usability Working Group Ending Questions.docx|Group Ending Questions}}

=== Use Case Analysis ===
  * {{:mbse:mbse-usecases_working.doc|Use Cases from 2011 International Workshop with Page Numbers}}
  * {{:mbse:usecaseanalysis032711.docx|Snapshot of Dialog:  Use Case Analysis}}
  * {{:mbse:usecaseanalysis.xlsx|Analysis of Preliminary Use Cases from 2011 International Workshop}}

=== MBSE Usability Collaboration Issues & Path Forward - May, 2011 ===
  * {{:mbse:mbse-cop-workingsmarter.docx|Working Paper: Collaborating on MBSE Usability - Supporting the MBSE Community of Practice}}
  * {{:mbse:mbse-cop052511_handout.pdf|MBSE Community of Practice:  The Path Forward (Meeting 5/25/11)}}

=== Usability Reference Materials ===

  * [[http://handle.dtic.mil/100.2/ADA433320|Agent Based Modeling and Behavior Representation (AMBR)]] - Kevin A. Gluck Sept 2004
  * [[http://www.usability.gov/methods/index.html|Government web site on usability]]
  * {{:mbse:Usability+Assessment+and+Conops+15+Oct.pdf|Usability Assessment and Conops}} - Ron Lyells
  * {{:mbse:miker_cser_usc_15_april_2011v5-handouts.pdf|NASA Systems Engineering Challenges (MBSE) - Dr. Michael Ryschkewitsch (Conference on SE Research 2011)}}

==== Library and Reuse Materials ====
  * [[http://www.omg.org/spec/RAS/2.2/PDF|Reusable Asset Specification V2.2]]
  * [[https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&ved=0CC8QFjAA&url=http%3A%2F%2Fwww.infosys.com%2FIT-services%2Fapplication-services%2Fwhite-papers%2FDocuments%2Fasset-reuse-model.pdf&ei=GyfMUdaqN6LI0QGX2IDgCQ&usg=AFQjCNF4Fh0jSaW5RoFwEXFONMdsJyxRQQ&sig2=yeHjiT2djH-B_HyN4-V7jA&bvm=bv.48340889,d.dmQ|A Model for Effective Asset Re-use in Software Projects]]
  * [[https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&ved=0CE4QFjAA&url=http%3A%2F%2Fwww.cs.clemson.edu%2F~johnmc%2Fconferences%2Fsymposium%2Ftutorial.pdf&ei=VifMUb2HGqi20QHl04CwAg&usg=AFQjCNHuc_m9f-E_fx25cu7alAhlW0TI8w&sig2=6DsjPXQ6SVOITGPHu1fOdA&bvm=bv.48340889,d.dmQ|Building resuable testing assets for a product line]]
  * [[https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&ved=0CDQQFjAA&url=http%3A%2F%2Fwww.inf.puc-rio.br%2Fwer02%2Fzip%2FMetamodeling_reuse(6).pdf&ei=kyfMUe2jKabH0QGX94C4Cg&usg=AFQjCNF_RvtVv3DEi0LIBkCueqXv9EvaHg&sig2=vM3NsZzBU9I7tUA2894vzg&bvm=bv.48340889,d.dmQ|Metamodeling for Requirements Reuse]]
  * [[https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&ved=0CC8QFjAA&url=http%3A%2F%2Fpdf.aminer.org%2F000%2F361%2F375%2Fproduct_line_architectures_aspects_and_reuse_tutorial_session.pdf&ei=3SfMUbyqIa3W0gHfqIHYAw&usg=AFQjCNENO4dqOh_l4410cyu23meGvoEZMg&sig2=21lskMx0vUDffDkUO4HtnQ&bvm=bv.48340889,d.dmQ|Evolution and Composition of Reusable Assets in
Product-Line Architectures: A Case Study]]


=== Candidate Usability Use Cases ===

  * {{:mbse:MBSEUsabilityIssuesFriedenthal032110.pdf|Usability Issues}} - Friedenthal

=== Usability Exemplars from Industry ===
  * {{:mbse:combined_usability_exemplars_paper_mbse_usability_group.docx|2012 Usability Exemplars; 5 cases}}

==== INCOSE Links ==== 

==== OMG Links ====
  * [[mbse:UsabilityTeamExemplars|Usability Team Exemplars]]
  * [[mbse:UsabilityTeamWorkspace|Usability Team Workspace]]

==== External Links ====
 
  * [[http://code.google.com/p/mbse-usability/|Prototype collaboration environment]] - Google Code
  * [[http://groups.google.com/group/mbse-usability|Discussion Group]] - Google Discussions
  * [[https://docs.google.com/document/d/1y90pkhLYeZmnH_G-E3sO16BawYXIxq11VfWfThIwVjY/edit|Using Exemplars to Improve the Usability of Modeling Methods, Languages, and Tools]] - Google Document White Paper in Draft State


==== Cross Team Links ====
MBSE Wiki

User Tools

Site Tools

Page Tools
