At the Logical Level, in Scenario diagrams, Solution Alternatives are created, for example as below. Each Solution Alternative is drawn such that it ultimately decomposes (directly or indirectly) to a Component, and where each Component decomposes to a Service.
Generic logical level scenario diagram
Service definitions form parts of Contracts (Conceptual Level) and these relationships are modeled by using definitions rather than diagrammatically using line symbols.
If a particular Service is drawn as a child of particular Component then a relationship between two Components can be determined by virtue of the relationship that exists between the two Services via their relationship within a Contract, this inferred relationship is modeled as a Component Contract between the Components.
The creation of these inferred relationships is automated and invoked by using helpers; a helper becomes available when a Scenario diagram is open.
Using a helper will create an Interaction Model diagram for the selected Solution Alternative onto which the Components that participate in the Solution Alternative are added; inferred Component Contract lines are then also added and defined. Note that should an Interaction Model already exist for the selected Solution Alternative then it will be re-used.
The table below shows the Scenario and Interaction Model diagrams for which helpers are available, note that there must at least one Solution Alternative present in the Scenario diagram for the helper to operate against.
Helpers are invoked from the Tools > IAF menu.
Logical level scenario and interaction diagram helper table
