How to document the Operational Analysis

Arcadia
1

Hi everyone,

I was wondering how you usually document your Operational Analysis for external reviewers or stakeholders who are not familiar with Arcadia, Capella, or MBSE in general.

I’m less interested in the specific software setup or implementation itself, and more in the overall structure, methodology, and way the Operational Analysis is presented and documented.

Thanks a lot!

Cheers,
Olli

2

Hello,

You may read chapter 5 of Jean-Luc Voirin.

Best

3

How deep do you want to explain your Operational Analysis to stakeholders who are not familiar with MBSE methods? What do you want to achieve with them?

What about a structure like this:

1. Introduction / Scope

  • Problem, goal, mission

2. Operational Context

  • Main actors

  • Main operational entities

3. Key Capabilities

  • List

  • Explanation + overview diagram

4. Scenarios / Operational Activities

  • Explain key scenarios step by step

5. Key Insights / Assumptions

  • Focus on the main points

Overall recommendation:
Follow a clear storyline: context → capabilities → scenarios
And make sure to explain everything in simple terms.

4

One thing that helped me when documenting Operational Analysis in Capella was keeping the Operational Entities and Operational Activities pretty lightweight at first, then refining the interactions later. It’s easy to over-model too early. Also, using scenarios/use cases as a starting point made the Operational Capabilities much clearer for me.

5

Thanks everyone, this already helps a lot!

I’m still quite new to all of this, so I always appreciate getting input from more experienced users.

Thanks!