Application Services - Revision history

Ictu mavi.cristache at 09:41, 11 June 2021

2021-06-11T09:41:18Z

2021-06-09T09:59:35Z

2021-06-09T09:59:03Z

2021-06-09T09:47:01Z

2021-03-23T12:52:07Z

2021-03-23T12:51:10Z

2021-03-22T11:44:39Z

2021-03-22T11:43:49Z

2021-03-22T11:38:09Z

2021-03-22T11:37:58Z

@@ Line 72: / Line 72: @@
 |Inter, USI
 |Generic. Both DC and DP verify/validate eSignatures supported by this service. Shares the functionality of the verification of documents that are signed electronically. An ‘electronic signature’ means data in electronic form which is attached to or logically associated with other data in electronic form and which is used by the signatory to sign. ‘validation’ means the process of verifying and confirming that an electronic signature is valid.
-|[[Trust Service Provisioning Component]]
+|[[Trust Service Provisioning]]
 |-
 ![[Alternative Channel]]

@@ Line 157: / Line 157: @@
 |Inter, USI, VC
 |Generic. User Interface for entering credentials, e.g. user/password, to be used for authentication purposes.
-|[[Identity Management Component]]
+|[[Identity Management]]
 |-
 ![[Identity/Record Matching]]

@@ Line 97: / Line 97: @@
 |Inter, USI, VC
 |Generic. The DC asks the user to authenticate him/herself. This service initiates the authentication process.
-|[[Identity Management Component]]
+|[[Identity Management]]
 |-
 ![[Procedural Requirements Determination]]

@@ Line 87: / Line 87: @@
 |Inter, USI
 |Generic. Shares the functionality that enables the secure exchange of messages, records, forms and other kinds of data between different ICT systems. This includes data routing, except endpoint discovery
-|[[Data Exchange Component]]
+|[[Data Exchange]]
 |-
 ![[eProcedure Confirmation]]

@@ Line 47: / Line 47: @@
 |Inter, USI, VC
 |Generic. "Saving the (public) service request to continue at a later point in time is handled by this service. This is an important service making the user’s life easier. An eProcedure application form usually requires the user to provide several inputs, wait for evidence transfers and/or upload documents themselves. The save and resume function allows them to complete the form over several days (up to some limit), saving changes e.g. an SLA timeout on the exchange of evidence, and editing the form again as needed before submitting the final application. Beside this voluntarily choice there is also the case that things go wrong: a timeout on the exchange of evidence, a system that is down, network errors etc. The save and resume functionality also supports to recover from some error situations preventing that the user must start all over again.
-|[[Session Management]]
+|[[Procedure Management]]
 |-
 ![[eProcedure Submission]]

@@ Line 32: / Line 32: @@
 |Inter, USI
 |Generic. The user must make an explicit request for OOP transfer of evidence. This service handles the request.
-|[[Online Procedure Portal Front-end|eProcedure Portal Front-end]]
+|[[eProcedure Portal Front-end]]
 |-
 ![[Persistent URL Generation]]

@@ Line 22: / Line 22: @@
 |Inter, USI
 |Generic. The DC must match required evidence cross-border. This service bundles UI and logic to support this process.
-|[[Evidence type translator]]
+|[[Evidence Type Translator]]
 |-
 ![[Evidence Exception UI]]

← Older revision		Revision as of 11:38, 22 March 2021
Line 1:		Line 1:
−	''An application service represents an explicitly defined exposed application behaviour. An application service exposes the functionality of components to their environment. This functionality is accessed through one or more application interfaces.'' ([ArchiMate® Standard, Version 3.1, The Open Group)	+	''An application service represents an explicitly defined exposed application behaviour. An application service exposes the functionality of components to their environment. This functionality is accessed through one or more application interfaces.'' (ArchiMate® Standard, Version 3.1, The Open Group)

	The Application Service is the linking-pin between the Business Process and the Application Component. These application services are identified in the context of the business process realization viewpoint.		The Application Service is the linking-pin between the Business Process and the Application Component. These application services are identified in the context of the business process realization viewpoint.

← Older revision		Revision as of 11:37, 22 March 2021
Line 1:		Line 1:
−	~~== intro text ==~~	+	''An application service represents an explicitly defined exposed application behaviour. An application service exposes the functionality of components to their environment. This functionality is accessed through one or more application interfaces.'' ([ArchiMate® Standard, Version 3.1, The Open Group)
		+
		+	The Application Service is the linking-pin between the Business Process and the Application Component. These application services are identified in the context of the business process realization viewpoint.
		+
		+	In DE4A, Application Service will also be used to provide a functional classification of application behaviour that can be consumed by different business processes. This classification is based on EIRA and TOOP and will be compiled and refined in the context of next task. It will provide the structure of the catalogue of SBBs, which realize this kind of service.

−	~~Lorem ipsum...~~

	== DE4A solution overview ==		== DE4A solution overview ==