How To
Summary
This article demonstrates different approaches to modelling exceptions using UML/SysML activity diagrams.
Both approaches have advantages and disadvantages. Users must decide which approach is most suitable.
Author: Chris Sutton
Document Location
Worldwide
[{"Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSB2MU","label":"IBM Engineering Systems Design Rhapsody"},"ARM Category":[{"code":"a8m50000000CjYLAA0","label":"Rhapsody-\u003EProfiles-\u003ESysML"}],"ARM Case Number":"TS004261240","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)"}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
Modified date:
27 May 2022
UID
ibm16346547