H_BUC_01_Subproc_Specification | Lexipedia

APPROVED

EESSI Business Use Case

H_BUC_01_Subprocess Adhoc Exchange of Information

Table of Contents

1. Introduction 4

1.1. Purpose 4

1.2. Scope 4

1.3. Definitions, Acronyms and Abbreviations 4

1.4. References 5

1.5. Overview 5

2. Description 6

2.1 Business Scenario 6

2.2 Legal Base 6

3. Actors & Roles 7

4. Use Case 8

4.1. RUP Table Representation 8

4.2. Request – Reply SEDs 10

4.3. Attachments Allowed 10

4.4. Artefacts used 10

5. Business Processes 11

6. Appendices 12

6.1. Issues 12

Document Control Information

Settings

Value

Document Title:

Business Use Case

H_BUC_01_Subprocess-Adhoc Exchange of Information

Project Title:

EESSI (Electronic Exchange of Social Security Information) Project

Document Author:

European Commission, DG EMPL F5

System Owner:

European Commission, DG EMPL D2

Doc. Version:

v4.1.0

Sensitivity:

Public

Date:

24/08/2018

Document history:

The Document Author is authorized to make the following types of changes to the document without requiring that the document be re- approved:

Editorial, formatting, and spelling

Clarification

To request a change to this document, contact the Document Author or Owner.

Revision

Date

Created by

Short Description of Changes

v0.1.0

10/04/2015

Phil Cummings

Initial Draft

v0.2.0

11/07/2016

Anda Mirita

Updated Table of Contents

Added EESSI Project Glossary link

Update Section 4.1

Added Sections 4.2, 4.3, 4.4.

v0.99.0

27/09/2016

Anda Mirita

No comments received

Submitted for AC Approval

v1.0.0

21/10/2016

Anda Mirita

AC Approved Version

v1.0.1

30/06/2017

Dragos Gorjan

Updated BPMN diagram in "Section 5. Business Processes" to correspond to the described process. Included the diagram of the BPMN version used.

-Replaced the reference to the BUC on Confluence.

v1.0.2

03/11/2017

Heidi Warson

Updated section 4.1 RUP Table Representation: branches 3 and 4 to align invalidate wording to the standard wording.

v4.1.0

24/08/2018

Novella Bacelli

- Section 4.4 merged 2 tables (for SED & for Subprocesses) into 1 BUC Artefact table."

- Version adaptations to release 4.1.0

Introduction

Purpose

The purpose of this document is to construct an external view of, part of, the 'EESSI business system' as described in EC Regulations 883/2004 and 987/2009. The ‘EESSI Business System’ describes the business and expected business processes without consideration as to which part(s) may be realized by an IT System (i.e. the proposed EESSI IT System).

The external view comprises of models and descriptions of business use cases, the services of a business system offered to business actors: customers, business partners, or other business systems.

A business use case is described from an actor's perspective; it describes the interaction between an actor and the business system, meaning it describes the behaviours of the business system that the actor utilizes. The Business Use Case includes Use Case Diagrams and Business Process Models.

Use case diagrams show actors, business use cases, and their relationships. Use case diagrams do not describe procedures. Alternative scenarios also remain hidden. These diagrams give a good overview of the behaviours of the EESSI business system which will direct and govern part of the expected behaviours and functionality delivered by the EESSI IT System.

Scope

This document is limited to the external view on the horizontal sector process Adhoc Exchange of Information. The different elements like use case description, actors, and business process as well as supporting UML diagrams and BPMN models pertaining to the ending of a process.

Definitions, Acronyms and Abbreviations

Please see the EESSI Project Glossary.

References

Description

EC Regulation 883/2004

Regulation EC No 883- 2004.pdf

EC Regulation 987/2009

Regulation EC No 987-2009.pdf

UML 2.x

http://www.omg.org/spec/UML/

BPMN 2.0

http://www.omg.org/spec/BPMN/index.htm

UML 2.0 In Action

Henriette Baumann, Patrick Grassle & Philippe Baumann, 2005, ISBN 1904811558

RUP@EC standard 5.0

http://www.cc.cec/RUPatEC_Standard/

RUP op maat

http://www.rupopmaat.nl/

Overview

Chapter 1 introduces the external view on the business system under review and lists the elements of this specification.

Chapter 2 introduces us to the Adhoc Exchange of Information business process. The chapter gives a short and detailed description as well as a reference to business process´ legal base.

Chapter 3 lists the actors involved in the Adhoc Exchange of Information business process.

Chapter 4 describes in detail the Adhoc Exchange of Information business process based on the RUP use case template, as well as the

relationship to other use cases.

Chapter 5 describes the Adhoc Exchange of Information business process using business process modelling notation (BPMN).

Description

2.1 Business Scenario

H_BUC_01_Subprocess is a subprocess that is used to request, or communicates, information based on the general cooperation requirements described in Article 76 of the basic Regulation (EC) No 883/2004 within an existing sectorial Case.

2.2 Legal Base

This Business Use Case document's legal base is described in the following Regulations:

basic Regulation (EC) No 883/2004

implementing Regulation (EC) No 987/2009

The following matrix specifies the SEDs that are used in this Business Use Case and documents the articles that provide the legal basis for each SED.

Basic Reg (883/04)

SED

Article 76

H001

H002

Table 1: SED – Legal base relationship matrix

Actors & Roles

This chapter captures details of the actors which are important to understanding the different types of system users. An actor is anyone or anything that exchanges data with the business system. An actor can be a user, external hardware, or another system.

The overarching description of each actor described in this Business Use Case can be found in the Glossary. Below you will find a short description which provides further clarity of this actor within the context of this Business Use Case.

Actor name

Description

Triggering Participant

The Triggering Participant is an active participant in the main process who triggers this BUC. This will be an Institution where the main process permits their role to do so

Other Participant(s)

Other Participant(s) represents all other active participants in the main process. This will be one or more Institutions as determined by the main process.

Table 2: Actors & Roles

Use Case

RUP Table Representation

Use Case ID:

H_BUC_01_Subprocess

Use Case Name:

Adhoc Exchange of Information

Created By:

Phil Cummings

Last Updated By:

Heidi Warson

Date Created:

21/04/2014

Last Revision Date:

03/11/2017

Actors:

Triggering Participant

Other Participant(s)

Description:

H_BUC_01_Subprocess is a sub-process that is used to request, or communicates, information based on the general cooperation requirements described in Article 76 of the basic Regulation (EC) No 883/2004 within an existing sectorial Case.

Trigger:

An Institution wishes to request, or communicate information, with another Institution.

Preconditions:

A case exists and triggers this BUC.

Post conditions:

The Triggering Participant received the information or communicated the information to other Participant(s).

Main Scenario:

The Triggering Participant fills in a Request For Additional Information (H001) by entering all the required information;

The Triggering Participant sends the H001, including any attachments, to all Other Participant(s);

Each Other Participant(s) receives and reviews the H001;

Each Other Participant(s)optionally may choose to fill in a Reply To Request For Information (H002) by entering all the required information;

Each Other Participant(s)y who filled in a H002 sends their H002, including any attachments, to the Triggering Participant and any Other Participant(s)

Triggering Participant (and Other Participant(s)) receive the H002;

The use case ends here.

Alternative Scenarios:

The Following Branches determine the use of Administrative Defined Processes within this Business Process

Branch 1: at any step after [step 2] the Triggering Participant may choose to send an updated version of H001

The Case Owner executes business use case AD_BUC_10-Subprocess - Update_SED

[This Branch] Ends.

Branch 2: at any step after [step 4] one of the other Participant(s) may choose to send an updated version of H002

The Case Owner executes business use case AD_BUC_10-Subprocess - Update_SED

[This Branch] Ends.

Branch 3: At any step after [step 2], the Triggering Participant may choose to advise all recipients of their H001 that it is Invalid under Art

5 of 987/09

The Triggering Participant executes business use case AD_BUC_06_ subProcess Invalidate SED;

Optionally, the Triggering Participant fills in a Request For Additional Information (H001) by entering all the required data;

Optionally, the Triggering Participant sends the H001, including any attachments, to all other Participant(s);

[This Branch] Ends.

Branch 4: At any step after [step 4], one of the other Participant(s) may choose to advise all recipients of their H002 that it is Invalid under Art

5 of 987/09

The other Participant executes business use case AD_BUC_06_ subProcess Invalidate SED;

Optionally, the other Participant fills in a Reply To Request For Information (H002) by entering all the required data;

Optionally, the other Participant sends the H002, including any attachments, to the Triggering Participant and any Other Participant(s);

[This Branch] Ends.

Exceptions:

Includes:

This BUC is exclusively used as an <<include>> in other sectorial business processes.

Special Requirements:

SR1: H001 can be used to request/notify information;

H002 can only be sent after receiving an H001;

SR2: Rules about the invoking of Branches:

The Main Scenario can be invoked more than once by the Triggering

Participant

[Branch 1] may be invoked more than once;

[Branch 2] may be invoked more than once;

[Branch 3] – May be invoked more than once;

[Branch 4] – May be invoked more than once;

SR3: Rules about the destination for each SED type;

H001 must be sent to all other Participant (s);

H002 may be sent to one or more Active Participants;

SR4: The term "Send/Sent to All Active Participants" does not include sending it himself (i.e. to then senders institution);

Assumptions:

Notes and Issues:

Request – Reply SEDs

The following table specifies the SED that have a logical pairing to one another, usually this is known as a request-reply pair.

REQUEST SED

REPLY SED(s)

H001

H002

Attachments Allowed

The following table specifies whether attachments are permitted to be included when sending a SED type.

SED

Attachments

H001

Allowed

H002

Allowed

Artefacts used

The following table specifies the artefacts that are used in this Business Use Case.

Artefact name

Artefact type

H001

SED

H002

SED

Business Processes

The following model describes the Business Use Case Adhoc Exchange of Information subprocess using BPMN 2.0.

Appendices

Issues

Issue date

Description

Replies

Action/Resolution

Close date