In order to fulfil the transforming process from JBAR to ALFABET, clear and unambiguous definitions are needed. The link to the current valid definitions, proposed future definitions and the approach chosen for this project can be find in the glossary (section 8). As mentioned in the glossary, the distinction between application, component, platform, etc. will be defined in the execution phase of the project. At the same time, the project has to map each data object to the new data model. A case-by-case examination of objects is needed because of poor data quality in JBAR. The current data model of JBAR defines all data objects as application. A distinction is made by a type definition. Table 1 shows the data objects and object types in JBAR as constituted on 11th of October 2018.