1. Previous Workshop Summary January 12, 2017

2. Previous Workshop Theme: MBSE & Transverse Verification
What are the benefits of transverse verification ?
What are the contributions of modeling?
Etre capable de vérifier à tous moments avec les différents stakeholders. Sur différents niveaux
Jouer sur les vérifications sur chaque partie de la décomposition.
Summary of Previous Workshop - April 11, 2017

3. Transverse Verification
Capability to verify with all stakeholders at any moment
Manage the verification of each section during decomposition
Optimization of verification efforts
Summary of Previous Workshop - April 11, 2017

4. NEEDS 1. Mastering of Modeling Efforts 2. Completeness of verification
3. Reduction of Overlaps
4. Detection & Anticipation of Problems
5. Verification of Specifications
6. Reuse of Models
7. Coherence between abstraction levels
8. Mastering verification of complex systems
9. Test Automation
10. Collaboration and Exchange Tool
Summary of Previous Workshop - April 11, 2017

5. Fort Impact Faible Fort Faible Effort Nom : Entreprise : 6 9 3
5. Verification of Specifications
Fort 6 9
4. Detection & Anticipation of Problems
3. Reduction of Overlaps
9. Test Automation
7. Coherence between abstraction levels
2. Completeness of verification
10. Collaboration and Exchange Tool 3
6. Reuse of Models
8. Mastering verification of complex systems
Impact
1. Mastering of Modeling Efforts
Faible
Fort
Summary of Previous Workshop - April 11, 2017
Faible
Effort

6. Summary of Previous Workshop - April 11, 2017

7. NEEDS 1. Mastering of Modeling Efforts 2. Completeness of verification
3. Reduction of Overlaps
4. Detection & Anticipation of Problems
5. Verification of Specifications
6. Reuse of Models
7. Coherence between abstraction levels
8. Mastering verification of complex systems
9. Test Automation
10. Collaboration and Exchange Tool
Summary of Previous Workshop - April 11, 2017

8. MAX 21 Votes
Summary of Previous Workshop - April 11, 2017

9. Needs with Lowest Efforts
High priority in MBSE literature
Positive impacts have been shown in case studies
The amount of effort greatly depends on the integration of tools and employee expertise
Summary of Previous Workshop - April 11, 2017

10. Needs with Highest Impacts
Traceability analysis is the most common method for problem detection
Model simulation used to test the Specification
Requirement Management Tool still required
Summary of Previous Workshop - April 11, 2017

11. Needs with Highest Efforts
Area of continued research
Modeling and tracing elements in complex systems is admittingly difficult
The return on investment for model-based activities is not clear
Summary of Previous Workshop - April 11, 2017

12. Verification in the V cycle
Model-Based
Summary of Previous Workshop - April 11, 2017

13. Ex: System Requirements
Activity Code
Type
Description
Model Based?
What is verified? A1
Reqs
Capture formally link between needs and test
Yes
Reqts A3
Trace requiremnts No B3
Capture if needs are coherent, feasible, etc
Needs B6
Design
Client level model of system
Behavior B8
Model executable specification D3
Specification documentation with Word/Visio
Functional Reqts
Summary of Previous Workshop - April 11, 2017