This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
sysml-roadmap:model_visualization_working_group [2016-03-15 07:42] cschreiber |
sysml-roadmap:model_visualization_working_group [2017-02-22 10:39] (current) cschreiber [The Model Visualization Focus Area Team] |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Model Construction Focus Area ====== | + | ====== Model Visualization Focus Area ====== |
- | Back to [[http://www.omgwiki.org/OMGSysML/doku.php?id=sysml-roadmap:sysml_assessment_and_roadmap_working_group| System Modeling Assessment and Roadmap Working Group]] | + | Back to [[http://www.omgwiki.org/OMGSysML/doku.php?id=sysml-roadmap:sysml_assessment_and_roadmap_working_group| SysML v2 RFP Working Group]] |
Line 20: | Line 20: | ||
===== Summary Documents ===== | ===== Summary Documents ===== | ||
- | Presentations - | + | == Presentations == |
- | + | * {{ :sysml-roadmap:visualization_requirements_for_sysml_2.0_02222017.pptx |Visualization_requirements_for_sysml_2.0_02222017}} Visualization Requirements (from SysML 2.0 Working Group Call, Feb. 22, 2017)\\ | |
- | {{sysml-roadmap:sysml_v2_model_visualization_12-8-15.pptx|}} Further Refined Visualization Concept (from La Jolla December 2015)\\ | + | * {{ :sysml-roadmap:visualization_considerations_for_sysml_2_0_-_coronado_-_20161207_-_r2.pptx |Visualization and Concrete Syntax Considerations for SysML 2 0 - Coronado - 20161207 - r2}} |
- | {{sysml-roadmap:sysml_v2_model_visualization_9-24-15.pptx|}} Initial Model Visualization Concept (from Cambridge September 2015)\\ | + | * {{sysml-roadmap:sysml_v2_model_visualization_12-8-15.pptx|}} Further Refined Visualization Concept (from La Jolla December 2015)\\ |
+ | * {{sysml-roadmap:sysml_v2_model_visualization_9-24-15.pptx|}} Initial Model Visualization Concept (from Cambridge September 2015)\\ | ||
Line 96: | Line 97: | ||
* Standards support (e.g., diagram definition) | * Standards support (e.g., diagram definition) | ||
+ | {{ :sysml-roadmap:visualization_graphic_v2.1.pdf |}} | ||
Line 125: | Line 126: | ||
- **Model Construction** views are used day-to-day to build and otherwise work with the model. They conform to the guidelines for diagramming in the UML and SysML specifications. But, we anticipate intelligent interactive features to be laid on top of these diagrams. Some of these features might include: | - **Model Construction** views are used day-to-day to build and otherwise work with the model. They conform to the guidelines for diagramming in the UML and SysML specifications. But, we anticipate intelligent interactive features to be laid on top of these diagrams. Some of these features might include: | ||
- | - Easy expand and collapse of nested nodes | + | * Easy expand and collapse of nested nodes |
- | - Hide and show of nodes and edges by filtering (e.g. meta class, stereotype, or other criteria) | + | * Hide and show of nodes and edges by filtering (e.g. meta class, stereotype, or other criteria) |
- | - Color or otherwise highlight based on repeatable rules (e.g. meta class, stereotype, or other criteria) | + | * Color or otherwise highlight based on repeatable rules (e.g. meta class, stereotype, or other criteria) |
- | - Creation of //meta edges// to show nested connections when a node is collapsed | + | * Creation of //meta edges// to show nested connections when a node is collapsed |
- | - Focus in on one node and those things that connect to it (e.g. show neighborhood) | + | * Focus in on one node and those things that connect to it (e.g. show neighborhood) |
- | - Show related nodes according to model-aware queries (e.g. for a chosen block on a BDD, show other blocks that transitively contribute to the definition of that block by either generalization or composition) | + | * Show related nodes according to model-aware queries (e.g. for a chosen block on a BDD, show other blocks that transitively contribute to the definition of that block by either generalization or composition) |
- | - Allows editing of model | + | * Allows editing of model |
- **Domain Specific** views are those used to address the Concerns of a Stakeholder in the sense of ISO 42010. | - **Domain Specific** views are those used to address the Concerns of a Stakeholder in the sense of ISO 42010. | ||
- | - These diagrams are free to conform to any display rules -- they do not need to be valid UML/SysML diagrams | + | * These diagrams are free to conform to any display rules -- they do not need to be valid UML/SysML diagrams |
- | - They may conform to any existing diagrammatic standard or convention, or to //ad hoc// rules | + | * They may conform to any existing diagrammatic standard or convention, or to //ad hoc// rules |
- | - They must be based on rules and rigorous transformations of the model so that they are repeatable | + | * They must be based on rules and rigorous transformations of the model so that they are repeatable |
- | - May or may not allow editing of model | + | * May or may not allow editing of model |
- **Version and Configuration Management** views are **Domain Specific** views that address stakeholder concerns regarding managing changes to the model | - **Version and Configuration Management** views are **Domain Specific** views that address stakeholder concerns regarding managing changes to the model | ||
- | - We feel this is a common, and very important, use case that merits its own discussion | + | * We feel this is a common, and very important, use case that merits its own discussion |
- | - Many version control systems for software provide such diagrammatic views | + | * Many version control systems for software provide such diagrammatic views |
- | - These typically show the history and relations of versions and merges over time, or line-by-line comparison of files | + | * These typically show the history and relations of versions and merges over time, or line-by-line comparison of files |
- | - Comparison of of models is significantly more complex than comparison of source code in text files | + | * Comparison of of models is significantly more complex than comparison of source code in text files |
- | - Important to compare the underlying model content, and present the differences both diagrammatically and in text form | + | * Important to compare the underlying model content, and present the differences both diagrammatically and in text form |
- **Interactive vs. Static** | - **Interactive vs. Static** | ||
- | - All of the above use cases can be implemented either as static diagram, or interactive user interfaces | + | * All of the above use cases can be implemented either as static diagram, or interactive user interfaces |
Line 202: | Line 203: | ||
^ Name ^ Organization ^ email ^ | ^ Name ^ Organization ^ email ^ | ||
| Chris Schreiber | Lockheed Martin Space Systems Company | <[email protected]> | | | Chris Schreiber | Lockheed Martin Space Systems Company | <[email protected]> | | ||
- | | Josh Feingold | Tom Sawyer Software | | | + | | Josh Feingold | Tom Sawyer Software | <[email protected]> | |
| Marc Sarrel | NASA Jet Propulsion Lab | <[email protected]> | | | Marc Sarrel | NASA Jet Propulsion Lab | <[email protected]> | | ||
| Elyse Fosse | NASA Jet Propulsion Lab | | | | Elyse Fosse | NASA Jet Propulsion Lab | | | ||
+ | | Ahsan Qamar | Ford Motor Company | <[email protected]> | | ||