DBA UC1 definition - Revision history

Ictu mavi.cristache at 15:32, 12 April 2021

2021-04-12T15:32:43Z

Ictu mavi.cristache at 14:36, 12 April 2021

2021-04-12T14:36:33Z

Ictu mavi.cristache at 14:34, 12 April 2021

2021-04-12T14:34:53Z

Ivar.Vennekens at 09:23, 2 April 2021

2021-04-02T09:23:20Z

Ivar.Vennekens: Created page with "== Scope == == Milestones == == Planning =="

2021-04-02T09:19:11Z

Created page with "== Scope == == Milestones == == Planning =="

New page

== Scope ==

== Milestones ==

== Planning ==

← Older revision		Revision as of 15:32, 12 April 2021
Line 1:		Line 1:
		+	''Back to [[Use_Case_"Starting_a_Business_in_Another_Member_State"_(DBA_UC1)\|main DBA UC1 page]]''
	== Scope ==		== Scope ==
	[[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.		[[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.

← Older revision		Revision as of 14:36, 12 April 2021
Line 1:		Line 1:
	== Scope ==		== Scope ==
−	[[File:Use case to interaction pattern mapping.png\|thumb]]The ~~first use case~~ 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.	+	[[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.

← Older revision		Revision as of 14:34, 12 April 2021
Line 1:		Line 1:
	== Scope ==		== Scope ==
−	The first use case 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.	+	[[File:Use case to interaction pattern mapping.png\|thumb]]The first use case 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.
−	~~[[File:Use case to interaction pattern mapping.png\|thumb]]~~

@@ Line 1: / Line 1: @@
 == Scope ==
+The first use case 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.
-== Milestones ==
+[[File:Use case to interaction pattern mapping.png|thumb]]