{"id":9992,"date":"2023-08-30T09:42:33","date_gmt":"2023-08-30T09:42:33","guid":{"rendered":"https:\/\/incose.nl\/workshop-2023\/9990-2\/"},"modified":"2023-09-06T13:23:50","modified_gmt":"2023-09-06T13:23:50","slug":"mathworks","status":"publish","type":"page","link":"https:\/\/incose.nl\/en\/workshop-2023\/mathworks\/","title":{"rendered":"MathWorks MBSE"},"content":{"rendered":"
\"INCOSE-NL<\/a><\/div><\/div><\/div><\/div><\/div><\/section>
\"Stephan<\/div><\/div>

Stephan van Beek<\/span><\/span>\u00a0<\/span><\/h2>\n<\/div><\/div>

Principal<\/span> Application Engineer<\/span><\/span> ,
\nMathworks<\/span><\/em><\/p>\n<\/div><\/div>

\"Tadele<\/div><\/div>

Tadele Shiferaw<\/span><\/span>\u00a0<\/span><\/h2>\n<\/div><\/div>

Senior Application Engineer<\/span><\/span>,
\nMathworks<\/span><\/em><\/p>\n<\/div><\/div><\/div><\/div>

Workshop: MBSE and sustainable cooling systems: a case study in engineering a greener future<\/h2>\n

14:30 – 16:00<\/p>\n<\/div><\/div>

<\/div>

Abstract<\/strong>
\nIn the early phase of a project, stakeholders, requirements engineers and system architects collaborate to derive system requirements from stakeholder needs. This is a collaborative process which requires a lot of communication. In this presentation I will explain how models help improve communication and thus increase the quality and utility of system requirements.<\/span>\u00a0<\/span><\/p>\n

You can consider authoring requirements models at 3 levels of precision:<\/span>\u00a0<\/span>
\nDescriptive requirements models<\/span><\/b> are a step forward compared to the traditional natural language requirements as they provide a structured, graphical representation of the requirement which improves the collaboration between the teams involved. A good example of such representation would be a sequence diagram.<\/span>\u00a0<\/span><\/p>\n

However, descriptive requirements models are still firmly in the engineering domain, whereas <\/span>Simulatable requirements models<\/span><\/b> can yield observations and insights in the system domain allowing stakeholders to get a direct understanding of the requirement in their domain. A good example of an executable formalism is a state chart.<\/span><\/p>\n

Although these are simulation techniques that provide good coverage of system behaviours, typically simulation is targeted at key scenarios to support collaborative work. <\/span><\/b>Formal requirements models<\/span><\/b> on the other hand contain formalisms that enable a more systematic assessment of the model\u2019s quality.\u00a0 One such formalism is a requirements table that can be used to formally prove the consistency and completeness of a set of requirements.<\/span>\u00a0<\/span><\/p>\n

Formal requirements models provide a good starting point for downstream teams both because the quality of the requirements is higher, and because elements of the requirements model can be re-used during design and verification.<\/span>\u00a0<\/span><\/p>\n

During this hands-on workshop we will apply these techniques to improve a cooling system to become more sustainable.<\/span>\u00a0<\/span><\/p>\n

What will you learn? Hands-on experience in:<\/span><\/b>\u00a0<\/span><\/p>\n