Advertisement

Towards a Cross-Border Reference Architecture for the Once-Only Principle in Europe: An Enterprise Modelling Approach

  • Jaak TepandiEmail author
  • Eric Grandry
  • Sander Fieten
  • Carmen Rotuna
  • Giovanni Paolo Sellitto
  • Dimitris Zeginis
  • Dirk Draheim
  • Gunnar Piho
  • Efthimios Tambouris
  • Konstantinos Tarabanis
Conference paper
Part of the Lecture Notes in Business Information Processing book series (LNBIP, volume 369)

Abstract

The Once-Only Principle states that citizens and businesses provide data only once in contact with public administrations. So far, many European countries have started to implement the Once-Only Principle at national level, but its cross-border implementation is still fragmented and limited. This paper presents the development of a Reference Architecture for the Once-Only Principle in Europe. The case study, stemming from the EU-funded Once-Only Principle project (TOOP) highlights the challenges faced by the architecture team when developing the Reference Architecture that tackles the Once-Only Principle across different countries and policy domains. The architecture is not built from scratch, but re-uses and enhances already available building blocks in order to seamlessly preserve interoperability and to comply with regulations and existing technical standards, leaving at the same time enough space for vendors and open source developers to propose their compliant solutions, whatever is their business model.

Keywords

Once-Only Principle EU Single Digital Gateway Reference Architecture TOOP EU Building Blocks TOOPRA 

Notes

Acknowledgements

This work was supported by the European Union Horizon 2020 research and innovation program (The Once-Only Principle Project, grant agreement no 737460). The authors would like to thank the three anonymous reviewers for their suggestions and comments.

References

  1. 1.
    Akkaya, C., Krcmar, H.: Towards the implementation of the EU-wide “once-only principle”: perceptions of citizens in the DACH-region. In: Parycek, P., et al. (eds.) EGOV 2018. LNCS, vol. 11020, pp. 155–166. Springer, Cham (2018).  https://doi.org/10.1007/978-3-319-98690-6_14CrossRefGoogle Scholar
  2. 2.
    Cloutier, R., Muller, G., Verma, D., Nilchiani, R., Hole, E., Bone, M.: The concept of reference architectures. Syst. Eng. 13(1), 14–27 (2010)Google Scholar
  3. 3.
    Dobrica, L., Ovaska, E.: A survey on software architecture analysis methods. IEEE Trans. Softw. Eng. 28, 638–653 (2002).  https://doi.org/10.1109/TSE.2002.1019479CrossRefGoogle Scholar
  4. 4.
    EC: European Interoperability Framework - Implementation Strategy. Communication from the Commission to the European Parliament, the Council, the European Economic and Social Committee and the Committee of the Regions, no. COM (2017) 134 final:9Google Scholar
  5. 5.
    EC: EU eGovernment Action Plan 2016–2020 - Accelerating the Digital Transformation of Government. Communication from the Commission to the European Parliament, the Council, the European Economic and Social Committee and the Committee of the Regions 2016, no. 179, pp. 1–11 (2016)Google Scholar
  6. 6.
    EC: European Interoperability Reference Architecture (EIRA) release v3.0.0 (2019)Google Scholar
  7. 7.
    Grandry, E., et al.: Generic Federated OOP Architecture (3rd version). Deliverable D2.3 of the TOOP project. European Commission (2018)Google Scholar
  8. 8.
    ISO/IEC/IEEE: ISO/IEC/IEEE 42010:2011. Systems and Software Engineering - Architecture Description. International Organization for Standardization (2011)Google Scholar
  9. 9.
    Krimmer, R., Kalvet, T., Toots, M., Cepilovs, A., Tambouris, E.: Exploring and demonstrating the once-only principle: a European perspective. In: Proceedings of dg.o 2017, pp. 546–551. ACM, New York (2017).  https://doi.org/10.1145/3085228.3085235
  10. 10.
    Proper, H.A., Lankhorst, M.M.: Enterprise architecture - towards essential sensemaking. Enterp. Model. Inf. Syst. Architect. 9, 5–21 (2014) CrossRefGoogle Scholar
  11. 11.
    Shanmugapriya, P., Suresh, R.M.: Software architecture evaluation methods – a survey. Int. J. Comput. Appl. 49, 19–26 (2012). https://www.ijcaonline.org/archives/volume49/number16/7711-1107Google Scholar
  12. 12.
    Sommerville, I.: Software Engineering, 9th edn. Addison-Wesley Publishing Company, Boston (2010)zbMATHGoogle Scholar
  13. 13.
    Tepandi, J., et al.: Generic Federated OOP Architecture (1st version). Deliverable D2.1 of the TOOP project. European Commission (2017)Google Scholar
  14. 14.
    The Open Group Architecture Forum: TOGAF Version 9.2. The Open Group (2018)Google Scholar
  15. 15.
    Urbaczewski, L., Mrdalj, S.: A comparison of enterprise architecture frameworks. Issues Inf. Syst. 7(2), 18–23 (2006)Google Scholar
  16. 16.
    Wimmer, M.A., Tambouris, E., Krimmer, R., Gil-Garcia, J.R., Chatfield, A.T.: Once only principle: benefits, barriers and next steps. In: Proceedings of dg.o 2017, pp. 602–603. ACM, New York (2017).  https://doi.org/10.1145/3085228.3085296
  17. 17.
    Woods, E.: Industrial architectural assessment using TARA. J. Syst. Softw. 85 (2011).  https://doi.org/10.1109/WICSA.2011.17

Copyright information

© IFIP International Federation for Information Processing 2019

Authors and Affiliations

  • Jaak Tepandi
    • 1
    Email author
  • Eric Grandry
    • 2
    • 3
  • Sander Fieten
    • 4
  • Carmen Rotuna
    • 5
  • Giovanni Paolo Sellitto
    • 6
  • Dimitris Zeginis
    • 7
    • 8
  • Dirk Draheim
    • 1
  • Gunnar Piho
    • 1
  • Efthimios Tambouris
    • 7
    • 8
  • Konstantinos Tarabanis
    • 7
    • 8
  1. 1.Information Systems GroupTallinn University of TechnologyTallinnEstonia
  2. 2.Luxembourg Institute of Science and TechnologyLuxembourg CityLuxembourg
  3. 3.Ministry of Mobility and Public WorksLuxembourg CityLuxembourg
  4. 4.Holodeck B2BLeidenThe Netherlands
  5. 5.ICI BucharestBucharestRomania
  6. 6.ANACRomeItaly
  7. 7.Centre for Research and Technology HellasThessalonikiGreece
  8. 8.University of MacedoniaThessalonikiGreece

Personalised recommendations