User Tools

Site Tools


sysml-roadmap:mbse_workflow_and_collaboration_working_group

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
sysml-roadmap:mbse_workflow_and_collaboration_working_group [2016-04-20 07:58]
happerly
sysml-roadmap:mbse_workflow_and_collaboration_working_group [2016-12-25 10:44] (current)
sfriedenthal
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]]
  
 ====== MBSW Workflow and Collaboration Workgroup ====== ====== MBSW Workflow and Collaboration Workgroup ======
Line 7: Line 7:
 ===== Project Overview ===== ===== Project Overview =====
 The MBSE Workflow and Collaboration project will define the concepts, requirements,​ and metrics for an effective systems engineering workflow, its practices and collaboration that support the next generation system modeling language (SysML v2).  The MBSE Workflow and Collaboration project will define the concepts, requirements,​ and metrics for an effective systems engineering workflow, its practices and collaboration that support the next generation system modeling language (SysML v2). 
 +
 +
  
  
Line 14: Line 16:
 ===== Driving Requirements ===== ===== Driving Requirements =====
  
-  - The next-generation modeling language must be accompanied by a set of reccomended, preferred processes+  - The next-generation modeling language must be accompanied by a set of recommended, preferred processes
   - The next-generation practice repository must provide services for modifying, creating and implementing a preferred processes for model-based systems engineering  ​   - The next-generation practice repository must provide services for modifying, creating and implementing a preferred processes for model-based systems engineering  ​
   - Rather than only standardizing a modeling language and logical systems modeling environment (SME) process advice (based on industry norms) must also be provided   - Rather than only standardizing a modeling language and logical systems modeling environment (SME) process advice (based on industry norms) must also be provided
-  - More streamlined and efficient model-based systems engineering processes ​willreduce ​the time and effort taken to build and maintain models and systems+  - More streamlined and efficient model-based systems engineering processes ​will reduce ​the time and effort taken to build and maintain models and systems
   - Reduced learning curve when embarking on model-based systems engineering   - Reduced learning curve when embarking on model-based systems engineering
 +  - Apply Software & Systems Process Engineering Metamodel™ specification (SPEM™) and BPMN
 +
  
  
Line 45: Line 49:
  
 4.  Focus on language ignores tool environment concerns, such as collaboration ​ 4.  Focus on language ignores tool environment concerns, such as collaboration ​
 +
 +
  
  
Line 77: Line 83:
       Peer review, design review workshop, brainstorming,​ storyboarding       Peer review, design review workshop, brainstorming,​ storyboarding
 5.  SME Service (how) 5.  SME Service (how)
-      Automated design review, system model simulation, functional animation+      Automated design review, system model simulation, functional animation, m-2-m transformation (based on rules)
 6.  PR Roles with Skills (who) 6.  PR Roles with Skills (who)
       System Design Reviewer with skills & competencies in MBSE       System Design Reviewer with skills & competencies in MBSE
Line 85: Line 91:
       Systems modeling tool (generic, then site specific)       Systems modeling tool (generic, then site specific)
 9.  PR & SME Deliverables (i.e. SME data subset, Work Product, Deliverable,​ Outputs, Input) 9.  PR & SME Deliverables (i.e. SME data subset, Work Product, Deliverable,​ Outputs, Input)
 +      This will typically be diagrams, groups of diagrams, viewpoints and states of all three
       Design review report, list of proposed improvements,​ improved model       Design review report, list of proposed improvements,​ improved model
 10.  PR Values or Benefits provided (why) 10.  PR Values or Benefits provided (why)
Line 214: Line 221:
     c. Capture Metrics     c. Capture Metrics
     d. Repot on progress and Metrics     d. Repot on progress and Metrics
 +
  
  
Line 226: Line 234:
 ===== Current Open Action Items ===== ===== Current Open Action Items =====
  
-  - Document Use Cases +  - Align with SPEM and add terms to Glossary
-  - Practice Repository Meta-model+
   - HSUV Examples   - HSUV Examples
-  - Plans for prototypes & actual prototypes ​ 
   - Open question; should practice repository be part of the SME?   - Open question; should practice repository be part of the SME?
-  - Review high-level service list +  - Add Requirements ​to master spreadsheet
-  - Consider links to all services (e.g. model creation) during workflow (practices)+
  
  
Line 254: Line 259:
     Response; Wiki created     Response; Wiki created
  
 +
 +
 +===== Review Material =====
 +  *{{ :​sysml-roadmap:​workflow_and_collaboration_concept_and_proposed_requirements-draft_v3_.pptx |SysML v2 Workflow and Collaboration Concept and Proposed Requirements-draft v3 Dec 08, 2016)}}
 ===== Team ===== ===== Team =====
 ^ Name ^ Organization ^ email ^ ^ Name ^ Organization ^ email ^
 | Hedley Apperly | [[http://​www.ptc.com/​| PTC]] | <​[email protected]>​ | | Hedley Apperly | [[http://​www.ptc.com/​| PTC]] | <​[email protected]>​ |
-| Ron Williamson |   |+| Ron Williamson | [[http://​raytheon.com/​Raytheon]] | <​[email protected]> ​|
  
 +Others tbd on request
  
  
 Last updated April 11, 2016 Last updated April 11, 2016
sysml-roadmap/mbse_workflow_and_collaboration_working_group.1461153511.txt.gz · Last modified: 2016-04-20 07:58 by happerly