What is the European Library of Architecture Principles (ELAP) and its validation?
In this guide, you will find some information about the ELAP and its validation (Interoperability Architecture Solutions Validator). It is presented in the following points:
The European Library of Architecture Principles (ELAP) and its validation are intended to be used by architects (system architects, enterprise architects) involved in IT change programs to guide for making correct design decisions. Furthermore, the use of both solutions will help identify the right sources and allow for proper contextualisation when arriving at decision-making points in architecture and design.
Policymakers are served by the Interoperability Architecture Solutions Validator to ensure that accepted or accepted solutions comply with the recommended frameworks. They are also served by endorsing decisions that further proliferate interoperability between organisations at all levels (Legal, Organisational, Semantical, and Technological) thus the effective and efficient use of resources.
The Interoperability Architecture Solutions Validator is a comprehensive tool developed to address a variety of needs in the design and implementation of interoperability solutions within public institutions in Europe. Stemming from the foundation laid by ELAP, its validation is designed to align with, and further the goals of, interoperability programs, ensuring that systems and solutions are not only compliant with European Frameworks but also efficient and effective. Below are the key purposes of the the Interoperability Architecture Solutions Validator:
- Quality Control:
- Ensures that SATs and Solutions meet the necessary quality standards to implement and support all European Frameworks on interoperability, such as the EIF.
- Guidance and Decision Support:
- Provides guidance for architects involved in IT change programs and aids in proper contextualization at decision-making points in architecture and design.
- Policy Compliance and Endorsement:
- Assists policymakers in ensuring solutions comply with recommended frameworks and supports decisions enhancing interoperability between organizations.
- Automation and Efficiency:
- Offers automated methods for users to self-assess their ongoing work, reducing time investment and adding granularity to validation procedures.
- Support for Interoperability:
- Aligns with the goals of ELAP and European interoperability programs, fulfilling interoperability requirements and ensuring alignment with various frameworks.
- Implementation through ITestBed:
- Utilizes the Interoperability TestBed (ITestBed) for providing automated assessment capabilities.
In essence, the Interoperability Architecture Solutions Validator is a pivotal asset for public institutions in Europe, enabling them to achieve interoperability, comply with frameworks, and make informed design decisions while optimizing resources.
- The library: the access to the library can be done in different ways, there is the library in excel (here), but there is also the its online documentation (which is in the process of being updated) where the user can read the different principles, definitions and rationales as well as context for the solution.
- The library in archimate (Work in progress): the ELAP is available in archimate through the CarTool archiplugin, which allows users to check it and include architecture principles into models.
- The Interoperability TestBed: the validator can be accessed here.
The rules outlined below form the foundation for modelling ELAP principles. They aim to establish a series of assertions with which any model incorporating architecture principles must comply. The ELAP validator is fully aligned with EIRA’s methodologies, ensuring consistency in the use, implementation, and role of architecture principles.
ELAP-000: ArchiMate syntax validation (XSD).
The ArchiMate syntax validation is focused on the basics, this business rule validates if the XML file to be validated is conformant with ArchiMate syntax.
Assertion: Models MUST be conformant with ArchiMate syntax
- Principle Name: ArchiMate syntax validation (XSD).
- Applies to: All.
- Severity: Error
- Message: [ELAP-000] XSD validation errors.
ELAP-001: Completeness principle
The Completeness Principle focus on the fact that all ELAP Architecture Principles need to be modelled when producing a Solution Architecture Template or a Solution.
Adding all ELAP principles in the creation of SATs or Solutions will ensure that outcomes have a comprehensive view and comply with IoP frameworks at all levels: legal, organisational, semantic, and technical.
Assertion: All APs MUST be modelled
- Principle Name: Completeness principle.
- Applies to: All.
- Severity: Error
- Message: [ELAP-001] Architecture principle 'XYZ' must be defined in the model.
ELAP-002: No-orphan elements Principle, Comply or explain principle
In this case, the No-orphan elements, Comply or explain principle pretends to ensure that Architecture Principles included are modelled and used. This means being related to the proper ABBs, or in case that principle is not going to be used, a justification is needed. This fact ensures that, when modelling, users do not miss any principles by design or accident. This business rule is conditioned by the next one, where it is validated if the principle is an “Obligation” or a “Desire”, more details within the next rule "Influence on DPS Lifecycle or Implemented Attribute”.
Assertion: If APs are not modelled, they MUST be commented in the Architecture view together with the reasons why are not included (as ArchiMate ‘note’).
- Principle Name: No-orphan elements principle, Comply or explain principle.
- Applies to: All.
- Severity: Error.
- Message: [ELAP-002] 'XYZ' must be associated with at least one element in the model, not being a 'principle'. If the principle is not used, associate it to a note (Archi “note” element).
ELAP-003: Specific implementation Solution
The DPS Lifecycle or implemented Attribute Principle focus on checking if all principles tagged as "Obligation" in the life-cycle or attributes of Digital Public Services are modelled. The logic behind this principle is that, when a principle is an “Obligation”, which means that is on regulations, it cannot be “not used” and justified.
Assertion: APs as 'Obligation' MUST be modelled.
- Principle Name: Influence on DPS Lifecycle or Implemented Attribute
- Applies to: All.
- Severity: Error.
- Message: [ELAP-003] Element 'XYZ' must be modelled, as it is an it is considered an obligation.
ELAP-004: Salient Alignment Principle
The Salient Alignment Principle is focused on validating the associations between Architecture Principles and Architecture Building Blocks from EIRA©. Users will not receive error messages here, instead, the feedback will be message warnings.
Assertions: APs SHOULD be modelled and associated mainly with the ABBs they are mapped to.
- Principle Name: Salient Alignment Principle.
- Applies to: ALL.
- Severity: Warning.
- Message: [ELAP-004] Architecture principle 'XYZ' must be modelled and related to the correct ABB. Any of the following ABBs can be related to this principle: List of ABBs
Architecture Principles need to be modelled as an Archimate notation. For that purpose, there is the CarTool, which is a plugin that includes amongst other libraries, the ELAP.
However, the latest version of ELAP is not available in CarTool yet, but it will be soon. Additionally, the latest release of CarTool is also unavailable.
By using the CarTool, the user ensures that the principles are included following and reaching the standards from ELAP. Which means: not stereotyping elements and reusing principles’ properties.
The mappings can be checked in the excel, and ttl file, and soon will be available in the CarTool.
Below you will find a few steps on how to use the CarTool provided by the EIRA action:
1. First of all, activate EIRA support to use the CarTool:
2. Access the ELAP through the Cartool navigation panel:
3. The panel will open where all principles are listed:
4. With the ELAP opened, then, the user can select one principle from the list, do right click and select “Architecture Principle To model”
5. Once the user has included the principle in the model, and other ABBs or SBB are already in place, it is time to link them. To be compliant, the elements need to be associated. The relationship to be used is the association, as shown in the following image:
6. After doing the relationship, an optional action is to adjust it, by directing it. To depict the influence from principle to architecture building block. This step is not mandatory for the validation, however, it facilitates the understanding of the model.
The following image is how it would look "basic" relationship to be conformant with the Interoperability Architecture Solutions Validator business rules:
Once the user has finished the model (SAT or Solution) can validate if is following the ELAP logic for modelling principles in the following link.
The model in XML can be exported from the modelling tool Archi® doing the following step:
The validator has the layout shown in the image below:
After selecting the solution "EIRA", to validate your model, select within the "Validate for" the option "ELAP SAT Model":
After selecting the model type to validate, then the user need to upload the model in XML using the following button:
