Request by Mads Hjorth: In the context of MS pilot with Denmark, it was requested to create an Archi model of the EIRA. He also made the following comments on the release of EIRA v0.8.3
- EIRA does not always well align with ArchiMate model concepts. Metadata management service is a “Service” in EIRA, but a “Business Service” in ArchiMate.
- The relation between Citizen and User are un-qualified. It is a simple association, but might be better as an assignment-releation
- The Relation-type between Public Service and Service Delivery model is not allowed. In EIRA an assignment is used and Archi only allows association between the two.
- Legal view is using technology elements. The use of green artifacts as types for legal elements might be confusing. An improvement could be to actually make a “regulation extension” to the Archimate language. It should be coordinated with the core legal vocabulary under development…
Draft resolution:
We have produced a first experimental version of the EIRA in Archi. This model introduces considerable changes compared to release v0.8.3 of the EIRA. This version can serve as a basis for future work on the Archi/EIRA and future EIRA releases. This work is by no means an official release of EIRA v0.8.3
Download model (right-click -> save link as) : ArchiMate® | PNG
Modeling this in Archi has triggered some issues on types of concepts to use from ArchiMate® and used relations. To overcome these, following changes have been implemented.
Legal layer, public policy : public policy, is designed as a principle that is influences by legal constraints and requirements as well as approaches, resources, and mandates. This enable the public policy concept to 'realize' that principle. The principle concept was chosen in the spirit of ArchiMate 2.1 definition of principle : Principles are normative guidelines that guide the design of all possible solutions in a given context.
Following that idea, and for consitency, other policy building blocks are also principles.
Application Function and Service: inspired by the ArchiMate meta-model, the Trans-European System has now a function concept assigned that realizes an application function. For example, the STORK system has two main functions : get user identity and get user attributes function, that realizes the STORK application STOCK C-PEPS/S-PEPS service. It is through that function that it access data.
Groups: some groups (organisational enablers, infrastructure enablers, ....) have been replaced by superclasses of their individual elements. This allows to have complete structural chain from public policy to infrastructure services and to use the superclass as first class building block rather than a group.
Interoperability Agreement: the three interoperability agreements within the EIRA have been replaced by one that can be signed between service providers or between a service provider and a user of the public service.
User: User now have only 1 concept specialized in citizen , businesses and public administration assigned to a location : sub-national, national, or europe.
(ArchiMate® is a registered trademark of the Open Group)
Component
Miscellaneous
Category
task
Comments
Hi all,
we have developed a first one-to-one mapping of the current v0.8.3 beta EIRA version. There are some difference that we have to explain. Two main difference are that
1. strong relations had to be replaced by weaker association on some place when Archi did not accept the relation the way it was presented in the visio
2. Some groups (organisational, legal views) have been replaced by concept and the elements within the group changed to subclasses. The reason is that Archi does not accept relationships to groups.
Colors have the same meaning than the Visio version (green = passive, yellow = behavioura, and blue = active.
We have added the attributes defined within the CarTool Template Excel into the Archi file. However, it requires improvement and agreement on how to present attributes in the Archi.
We believe this version is suitable for your modeling needs of the pilots (SAT), please do send us feedback, we will improve where necessary.
Please find the files here (Archi | Architemplate | PDF ). Please use right-click "Save as..."
Thanks Zakaria, that is gonna save some of us a lot of work...
I will use this forum to capture any issues moving along. And hope you understand that I really appricate your work and I know how much work has been put into this work.
Nevertheless here is my first issue.
In the model exist quite a few ducplicates of items. Pressing the backspace key only delete an element from the view. To delete from the model you need to right click and choose remove from model.
For next version I would suggest going through the (expanded) model and remove any un-used elements (names in italic).
Thanks again for some great usefull work
Hi Mads, indeed I discovered it a bit late. It is solved. I have removed all duplicated and added attributes the same way you did for your ePrescription.