The Harmony aMBSE functional analysis of use cases many be done in any of five alternative approaches, each of which is roughly equivalent to the others in their outcome. 

• Flow Based Approach 

  • This uses fully executable activity modeling and is best applied when the use case is dominated by algorithmic or continuous flow behavior​

• System Function-Based Approach​

  • This approach creates incomplete activity diagrams and uses the state machine as the normative specification. It is the most common approach and is best used when the identification and characterization of system functions are the primary concern​

• Interaction-Based (Scenario-based) Approach​

  • This approach starts with sequence diagrams and is best used with either working directly with non-technical stakeholders or when the interaction between the system and its environment is the primary concern​

• State-based approach​

  • This approach is useful when the use case is clearly state- or mode-based and the engineers have strong state machine skills. ​

• Harmony "Classic" (depricated)​

  • This is the older Harmony SE approach and is recommended only when working on a system previous modeled in this way. This approach lacks guidance on addressing data, safety, reliability, and security concerns. ​

​​

These alternatives are detailed in the Harmony aMBSE Deskbook (see the Papers page).