H_BUC_07_Subproc_Specification | Lexipedia

APPROVED

EESSI Business Use Case

H_BUC_07_Subprocess Notification of Death

Table of Contents

6.1. Issues 12

Document Control Information

Settings

Value

Document Title:

Business Use Case

H_BUC_07_Subprocess-Notification of Death

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

21/10/2015

Eric Briffoz

Initial Draft

v0.2.0

11/07/2016

Anda Mirita

Added EESSI Project Glossary link

Update Section 4.1 Main Scenario

Added Section 4.2, 4.3, 4.4

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

22/11/2017

Heidi Warson

Updated section 4.1 RUP Table Representation: branch 1 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 Notification of Death. 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 Notification of Death 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 Notification of Death business process.

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

Chapter 5 describes the Notification of Death business process using business process modelling notation (BPMN).

Description

Business Scenario

H_BUC_07_Subprocess is a sub process that is used to notify the death of an insured person, information based on the general cooperation requirements described in Article 76 of the basic Regulation (EC) No 883/2004 within an existing sectorial Case.

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

H070

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_07_Subprocess

Use Case Name:

Notification of Death

Created By:

Eric Briffoz

Last Updated By:

Novella Bacelli

Date Created:

21/10/2015

Last Revision Date:

31/08/2018

Actors:

Triggering Participant

Other Participant(s)

Description:

Trigger:

An Institution wishes to communicate the Notification of Death to other participant(s).

Preconditions:

A case exists and triggers this BUC.

Post conditions:

The Triggering Participant has communicated the Notification of Death.

Main Scenario:

The Triggering Participant fills in a Notification of Death (H070) by entering all the required Information;

The Triggering Participant sends the H070, attaching, if necessary, any other document proving the death of person concerned, to all other Participants ;

Each Other Participant(s) receive(s) and views H070, and attachments;

Each Other Participant(s) process(es) the H070;

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 may choose to advise all recipients of their H070 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 of Death (H070) by entering all the required data;

Optionally, the Triggering Participant sends the H070, including any attachments, to all other Participants;

[This Branch] Ends.

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

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

[This Branch] Ends.

Exceptions:

Includes:

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

Special Requirements:

SR1: H070 can be sent only once.

SR2: Rules about the invoking of Branches:

[Branch 1] – May be invoked more than once (Provided a new SED H070 has been created after invalidation)

[Branch 2] – May be invoked more than once

SR3: Rules about the destination for each SED Type:

H070 – Must be sent to all other Participant(s)

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)

Attachments Allowed

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

SED

Attachments

H070

Allowed

Artefacts used

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

Artefact name

Artefact type

H070

SED

Business Processes

The following model describes the Business Use Case Notification of Death subprocess using BPMN 2.0.

Appendices

Issues

Issue date

Description

Replies

Action/Resolution

Close date