Scenario models consumer perspective

In this master data consumer model a limited view of the relevant architectural entities are displayed. Here you see a high level model of register data consumption. Via different application functions data is consumed. For example via user interfaces like reports, portals, geo viewers etc data is directly consumed by various end users. A detailed inventarization of these end users and user interfaces will be modeled.

Version 1.0
Created date 02-05-2021

Register Data Consumption

Abstract architectural entity for the register data consumers, all user interfaces and data integrations are an master data consumer

Author Bert Dingemans
Alias --
Stereotypes ApplicationFunction
Details of Register Data Consumption

Register Data Consumption via Integration

Application and database integration like webservices, file transfer, database links, views etc. In a later phase we will model the various integration methods and model these in detail

Author Bert Dingemans
Alias --
Stereotypes ApplicationFunction
Details of Register Data Consumption via Integration

Register Data Consumption via User Interface

All kinds of user interfaces in which an user can consume data via a (graphical) user interface. Examples of user interfaces are reports, forms, portals graphs, geoviews etc.

Author Bert Dingemans
Alias --
Stereotypes ApplicationFunction
Details of Register Data Consumption via User Interface

Register Data Publication and Integration Service

Logical services that publish the data from the register to various register data consumers

Author Bert Dingemans
Alias --
Stereotypes ApplicationService
Details of Register Data Publication and Integration Service