The L2 Logical Scenario (Fit for Purpose) viewpoint of NAF v4 is a diagram upon which you can model Roles and the OperationalExchanges between Roles. A Role is the relationship created between an OperationalPerformer and an OperationalActivity – PerformsInContext (Role) – in DM2 (which UAF’s DMM is based on) this was called ActivityPerformedbyPerformer – alias Role.
You may manually create OperationalExchanges between Roles, or use System Architect’s automation to create OperationalExchanges by selecting Tools > NAF 4 Utilities > Generate Operational Exchanges.
Automatically-generated OperationalExchanges have their SA-controlled property set to T (True) and their Valid property set to T (True). If you manually draw an OperationalExchange, its SA-Controlled and Valid properties default to F (False). You may change them in the OperationalExchange definition.
▪SA-Controlled: An OperationalExchange with its SA-controlled property set to F will not be overridden if someone runs the auto-generation utility.
▪Valid: An OperationalExchange whose Valid property is set to T (True) means that the OperationalExchange has a from and to Role (PerformsInContext) that each relates an OperationalPerformer and OperationalActivity, and there is an OperationalActivityEdge between the two involved OperationalActivities.
