H_BUC_05_Subproc_Specification | Lexipedia

APPROVED

EESSI Business Use Case

H_BUC_05_Subprocess Exchange of PINs

Table of Contents

6.1. Issues 12

Document Control Information

Settings

Value

Document Title:

Business Use Case

H_BUC_05_Subprocess-Exchange of PINs

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:

31/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

13/07/2016

Anda Mirita

Initial Draft

v0.99.0

27/09/2016

Anda Mirita

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.

- Adapted reference to BUC confluence page in Configuration Management

v1.0.2

03/11/2017

Heidi Warson

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

v4.1.0

31/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 Exchange of PINs. 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 Exchange of PINs 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 Exchange of PINs business process.

Chapter 4 describes in detail the Exchange of PINs business process based on the RUP use case template, as well as the relationship to other use cases.

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

Description

Business Scenario

H_BUC_05_Subprocess is a sub process that is used to exchange Personal Identification Numbers (PIN) described in Article 2 (2) and Article 52 (1) (a) of Regulation (EC) No 987/2009, within an existing sectorial Case.

Legal Base

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

Implementing Regulation (EC) No 987/2009 Article 2 (2)

Implementing Regulation (EC) No 987/2009 Article 52(1) (a)

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.

SED

Implementing Regulation

2 (2)

52(1)(a)

H061

H062

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_05_Subprocess

Use Case Name:

Exchange of PINs

Created By:

Anda Mirita

Last Updated By:

Novella Bacelli

Date Created:

13/07/2016

Last Revision Date:

31/08/2018

Actors:

Triggering Participant

Other Participant(s)

Description:

Trigger:

An Institution sends the Exchange of/Request for confirmation of Personal Identification Number to other Participant(s).

Preconditions:

A case exists and triggers this BUC.

Post conditions:

The identification of the person is confirmed or could not be confirmed.

The identification PIN's for the purpose of social security administration has been provided or could not be provided.

Main Scenario:

The Triggering Participant fills in a Notification/Request of Personal Identification Number (H061) by entering all required information;

The Triggering Participant sends the H061 to all other Participant(s);

Each other Participant (s) receives the Notification/Request of Personal Identification Number (H061);

Each other Participant (s) fills in a Confirmation/Reply to Request of Personal Identification Number (H062) by entering all required information;

Each other Participant (s) sends the H062 to all participants.

The Triggering Participant and all other Participant(s) receive H062.

The use case ends here

Alternative Scenarios:

The Following Branches Determine the use of Administrative Processes

within this Business Process

Branch 1: at any step after step [2] the Triggering Participant chooses to advise all recipients of their H061 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 Notification/Request of Personal Identification Number (H061) by entering all required data;

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

[This Branch] Ends.

Branch 2: at any step after step [5], the other Participant(s) chooses to advise all recipients of their H062 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 Confirmation/Reply to Request of Personal Identification Number (H062) by entering all required data;

Optionally, the other Participant sends the H062, including any attachments, to all participants;

[This Branch] Ends.

Branch 3: at any step after step [2] the Triggering Participant chooses to send an updated version of H061

The Case Owner executes business use case AD_BUC_10-Subprocess -

Update_SED;

[This Branch] Ends.

Branch 4: at any step after step [5] the other Participant(s) chooses to send an updated version of H062

1. The Counterparty executes business use case AD_BUC_10-Subprocess -

Update_SED;

2. [This Branch] Ends.

Exceptions:

Includes:

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

Special Requirements:

SR1: H061 can be sent only once (even though updates can be created for this SED).

SR2: Rules about the invoking of Branches:

[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:

- H062 has multiple destination recipients, the Triggering Participant + all other Participant(s) and it is sent only as reply of H061.

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)

H061

H062

Attachments Allowed

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

SED

Attachments

H061

Allowed

H062

Allowed

Artefacts used

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

Artefact name

Artefact type

H061

SED

H062

SED

Business Processes

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

Appendices

Issues

Issue date

Description

Replies

Action/Resolution

Close date