1 / 16

SysML v2 Usability Working Session

SysML v2 Usability Working Session. OMG Meeting Reston, VA March 21, 2017. Sanford Friedenthal safriedenthal@gmail.com. Topics. Usability Introduction & Session Overview – Sanford Friedenthal Ideas on Usability Layering - Bertil Muth Break User Centered Design Approach - Tricia Lagoon

sanglin
Télécharger la présentation

SysML v2 Usability Working Session

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SysML v2 Usability Working Session OMG Meeting Reston, VA March 21, 2017 Sanford Friedenthal safriedenthal@gmail.com

  2. Topics • Usability Introduction & Session Overview – Sanford Friedenthal • Ideas on Usability Layering -BertilMuth Break • User Centered Design Approach - Tricia Lagoon • Facilitated Discussion on SysML v2 Usability Requirements

  3. Session Objectives & Approach • Objectives • Define minimal usability requirements/criteria and supporting assessment methods for SysML v2 RFP • Increase awareness of usability concerns and approaches • Approach • Elicit inputs from modeling end users with a range of experience levels and modeling tool vendors

  4. User Classes • New modelers • Early career and experienced systems engineers learning SysML • Seasoned modelers • System engineers with experience in modeling, comfortable with using SysML and modeling tools • Consumers of model data • Other engineering disciplines who do not use SysML modeling tools, but need to understand and interpret model information Needs vary across lifecycle, disciplines, and application domains

  5. Wikipediahttps://en.wikipedia.org/wiki/Usability • Usability is the ease of use and learnability of a human-made object such as a tool or device.[1] In software engineering, usability is the degree to which a software can be used by specified consumers to achieve quantified objectives with effectiveness, efficiency, and satisfaction in a quantified context of use.[2]

  6. Usability Criteria

  7. MBSE Learning Obstacles • MBSE is a more rigorous/formal approach to address the inherent complexity of systems and SE methods • System complexity (e.g, layered interfaces, complex state behaviors, complex structures with assemblies and subsystems) • SE Methods must address multiple stakeholder viewpoints that span multiple requirements, multiple levels of design, across disciplines, and full lifecycle

  8. SysML Language/ToolUsability Issues • Learning obstacles • Definition/Usage (e.g., part vs block, action vs activity, ..) • Maintaining consistency across views • different kinds of behavior, structure, parametrics, requirements • Model containment tree vs product structure • Unfamiliar terminology from UML legacy and SysML (e.g., proxy port) • Functional vs geometric concepts (enclosed by versus external to) • Lack of engaging/intuitive domain-specific visualizations (i.e., boxology) • Inability to express informal ideas and refine • Ability to abstract • Productivity obstacles in model construction • Complexity of user interface • Create/update one element at a time (too many clicks) • Manual diagram layout

  9. SysML v2 Usability Focus • Model Visualization Concept • Model Construction Concepts • Language Concepts and Formalisms

  10. Browser-Based Data Presentations Visualization Concept Model Data User System Modeler Heavy Model User • Model Organization & Development • Pattern & Model Library Definitions • Model Customizations Source: C. Schreiber, J. Feingold, M. Sarrel Light Model User Model Data Contributor • Model Updates • Report Generation • Model Execution Reviewer/Consumer • Model Review & Comment • Predefined Reports • User-defined Views

  11. Model Construction Concept Source: R. Williamson Model Construction Workflow Example Execute Analysis [login] Note: Iterative steps not shown Import Requirements Reference Library Analyze Requirements Component Library Batch Import & Transformation Select Reference Architecture Variant Execute Analysis • Supports different classes of collaborative users (e.g., expertise, domain, life cycle) • Driven by iterative / agile workflow • Batch import, transformation & export • Broad application of patterns & reuse libraries • Textual, graphical and tabular model create, update and delete • Model ownership, baseline & version management via Model Management • Black Box/White Box Representations via Model Management • Model views & usability via Model Visualization • Requirements/Design Analysis via Model Analysis Integrate & Configure Component Designs Evaluate Architecture Designs Apply Patterns Update Baseline Commit to Server

  12. Other Usability Concepts • Simple hierarchical lists with cross connections • Mind maps • Wiki’s

  13. SysML v2 Usability Expecations • Should SysML v2 be simple (how does this contrast  with mechanical and electrical design tools and languages) • What are examples of user friendly languages (MATLAB, Simulink,. …) and user friendly interfaces (Apple/Iphone) • How much of the usability is allocated to SysML v2 vs the tool vs the method • How can customization address  the usability needs (e.g., jargon/aliases, visuzliations, domain specific symbology, …)

  14. Usability Requirements

  15. Backup

  16. Requirement • How quickly can a modeler find what they are looking for • Level of assistance when stuck

More Related