sysml-roadmap:system_analysis_workgroup
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
sysml-roadmap:system_analysis_workgroup [2016-04-19 13:48] mbajaj |
sysml-roadmap:system_analysis_workgroup [2017-05-23 14:50] (current) sfriedenthal [Presentations] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | 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 37: | Line 37: | ||
| - | ===== Status Quo ===== | + | ===== Challenges in formulation, representation, and execution of system analyses ===== |
| - | + | The current generation of SysML (1.x) has the following challenges related to formulating, representing, and executing system analyses. | |
| - | * No cross-disciplinary traceability | + | - Analysis is a missing concept in SysML |
| - | * Different (proprietary) data formats | + | - Lack of formal represenation of analysis objectives, subject system, analysis models, results, and decisions |
| - | * Need to capture multi-disciplinary engineering data and relationships in a common data format | + | - Lack of formal representation of design <-> analysis model transformations |
| - | * No standard API to access SysML data | + | - Incomplete definitions of types and units |
| - | * No standard Web API to access SysML data | + | - Lack of formal representation of complex data structures, such as vectors, tensors, and matrices |
| - | * No standard Query API to perform complex queries on SysML data | + | - Lack of formal representation of mathematical operators, such as needed for differentials and integrals |
| - | + | - Lack of formal representation of primitive geometry concepts, as needed for precise representation and verification of requirements | |
| - | + | - Lack of formal representation of visualization concepts, such as mathematical graphs as needed for representing analysis results | |
| - | + | - Lack of a unique identifier system for model elements | |
| - | ===== Limitations of SysML ===== | + | - Lack of element-level version and configuration management |
| - | + | ||
| - | SysML data is currently not available: | + | |
| - | * in a standardized graph-based data format | + | |
| - | * through a standard API | + | |
| - | * through a standard Web API | + | |
| - | * through a standard Query API to perform complex queries | + | |
| - | + | ||
| - | + | ||
| - | ===== Derived Requirements for Interoperability ===== | + | |
| - | + | ||
| - | System Modeling Environment (SME) should support: | + | |
| - | * a data format suitable for describing graphs | + | |
| - | * a non-proprietary data format | + | |
| - | * a widely adopted data format | + | |
| - | * Standard Web API to access SysML data | + | |
| - | * Standard Web API supporting complex queries | + | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | ===== Key Features of New Concepts ===== | + | |
| - | + | ||
| - | * Adoption of data format and data access standards aligned with W3C standards | + | |
| - | * Adoption of data format and data access standards aligned with the larger web community | + | |
| - | * Merging/Linking different systems engineering standards (STEP/OMG/ISO/OSLC) through Linked Data | + | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | ===== Recommended Standards for Interoperability ===== | + | |
| - | * **Data** of the System Modeling Environment (SME) should be available in the W3C standard **[[http://www.w3.org/RDF/Resource Description Framework (RDF)| Resource Description Framework (RDF)]]** | + | |
| - | * **Metadata** (semantics) in the System Modeling Environment (SME) should be defined in RDF vocabularies (W3C standard **[[http://www.w3.org/TR/rdf-schema/| RDF Schema]]**) and shape constraints (W3C standard **[[http://www.w3.org/TR/shacl/| SHACL]]**) | + | |
| - | * **Web API** of the System Modeling Environment (SME) should be RESTful and conform to the W3C standard **[[http://www.w3.org/TR/rdf-schema/| Linked Data Platform]]** | + | |
| - | * **Query API** of the System Modeling Environment (SME) should conform to the W3C standards **[[http://www.w3.org/TR/sparql11-query/| SPARQL]]** and **[[http://www.w3.org/TR/sparql11-protocol/| SPARQL Protocol]]** | + | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | ===== Review Documents ===== | + | |
| - | + | ||
| - | * {{sysml-roadmap:sysml_v2_model_interoperability_requirements_-_axel_reichwein_-_dec_10_2015_v3.pptx|SysML v2 Model Interoperability Requirements - Axel Reichwein - Dec 10 2015}} | + | |
| - | + | ||
| - | + | ||
| - | ===== Prototypes to demonstrate feasibility ===== | + | |
| - | * Open-source OSLC and Linked Data solutions available at [[https://github.com/ld4mbse| GitHub ld4mbse]] | + | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | ===== SME/SysML v2 Service requirements (e.g. functions) to support interoperability ===== | + | |
| - | + | ||
| - | Most services listed in the {{00-SysML v2-Services-2015-11-26.xlsx| spreadsheet}} are useful for supporting data traceability/interoperability. | + | |
| - | + | ||
| - | * Services to create, read, update, and delete links between tools | + | |
| - | * Services to create, read, update, delete, and execute transformations to/from SysML models | + | |
| - | * Services to export and import unstructured and structured data | + | |
| - | * Services to create, update, delete, and execute model elements and patterns | + | |
| - | * Services to create, resd, update, and delete viewpoints | + | |
| - | * Services to create, read, update, delete, and execute model queries to support visualization and analysis | + | |
| - | * Services to generate and manage views | + | |
| - | * Services to create, read, update, delete, and execute model validation rules to validate input data and model | + | |
| - | * Services to create, read, update, delete, and execute analytical models | + | |
| - | * Services to manage model metadata | + | |
| - | * Services to manage changes to model | + | |
| - | * Services to create, read, update, delete, and execute workflows and notifications | + | |
| - | + | ||
| ===== Presentations ===== | ===== Presentations ===== | ||
| + | - {{sysml-roadmap:sysml_v2_analysis_requirements_omg_reston_2017-03-23.zip|SysML 2 Analysis Requirements presentation (zip) at SysML 2 RFP WG mtg at OMG Technical Meeting, Reston (Mar 20-24, 2017) }} | ||
| + | - {{sysml-roadmap:sysml_2_analysis_requirements_2017-02-08_.pdf|SysML 2 Analysis Requirements presentation at SysML 2 RFP webcon (Feb 8, 2017) }} | ||
| + | - {{sysml-roadmap:sysml_2_analysis_wg_2016-11-16.pdf|System Analysis presentation at SysML 2 RFP webcon (Nov 16, 2016) }} | ||
| + | - {{sysml-roadmap:sysml_2_analysis_wg_2016-09-13.pdf|System Analysis presentation at Chicago (Sep 2016) }} | ||
| - {{sysml-roadmap:sysml_v2-analysis_concept-manas_bajaj_intercax-reston-2016-03-16.pdf|System Analysis presentation at Reston (Mar 2016) }} | - {{sysml-roadmap:sysml_v2-analysis_concept-manas_bajaj_intercax-reston-2016-03-16.pdf|System Analysis presentation at Reston (Mar 2016) }} | ||
| - {{sysml-roadmap:05-sysml_v2-system_analysis-bajaj-intercax-_2015-12-08.pdf|System Analysis presentation at La Jolla (Dec 2015)}} | - {{sysml-roadmap:05-sysml_v2-system_analysis-bajaj-intercax-_2015-12-08.pdf|System Analysis presentation at La Jolla (Dec 2015)}} | ||
| + | |||
| ====== System Analysis Workgroup Team ====== | ====== System Analysis Workgroup Team ====== | ||
sysml-roadmap/system_analysis_workgroup.1461088115.txt.gz · Last modified: 2016-04-19 13:48 by mbajaj
Page Tools
