Difference between revisions of "DBA UC1 definition"
m |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| + | ''Back to [[Use_Case_"Starting_a_Business_in_Another_Member_State"_(DBA_UC1)|main DBA UC1 page]]'' | ||
== Scope == | == Scope == | ||
| − | The | + | [[File:Use case to interaction pattern mapping.png|thumb]]The [[Use Case "Starting a Business in Another Member State" (DBA UC1)]] ends with a subscription to receive notifications of business events of the company involved. From a logical process point of view, this is strongly intertwined with the company registration: subscribing to notifications follows directly after registration of the company at the eProcedure portal, before the process ends. Hence it is an integrated part of the first use case. From an [[Reference Interaction Patterns|interaction pattern perspective]], the subscription to notifications does not belong to the [[Intermediation Pattern|intermediation pattern]] but to the [[Subscription and Notification Pattern|subscription & notification pattern]]. The first part of the [[Subscription and Notification Pattern|subscription and notification pattern]] deals with managing subscriptions, the second part with sending notifications once a business event took place. So, the first use case spans two interaction patterns. |
| − | |||
Latest revision as of 16:32, 12 April 2021
Back to main DBA UC1 page
Scope
The Use Case "Starting a Business in Another Member State" (DBA UC1) ends with a subscription to receive notifications of business events of the company involved. From a logical process point of view, this is strongly intertwined with the company registration: subscribing to notifications follows directly after registration of the company at the eProcedure portal, before the process ends. Hence it is an integrated part of the first use case. From an interaction pattern perspective, the subscription to notifications does not belong to the intermediation pattern but to the subscription & notification pattern. The first part of the subscription and notification pattern deals with managing subscriptions, the second part with sending notifications once a business event took place. So, the first use case spans two interaction patterns.