Systems Software and Services

Process Improvement 28th European

Conference EuroSPI 2021 Krems
Austria September 1 3 2021
Proceedings 1st Edition Murat Yilmaz
Visit to download the full and correct content document:
https://ebookmeta.com/product/systems-software-and-services-process-improvement
-28th-european-conference-eurospi-2021-krems-austria-september-1-3-2021-procee
dings-1st-edition-murat-yilmaz/
More products digital (pdf, epub, mobi) instant
download maybe you interests ...

Computer Vision Systems 13th International Conference

ICVS 2021 Virtual Event September 22 24 2021
Proceedings 1st Edition Markus Vincze

https://ebookmeta.com/product/computer-vision-systems-13th-
international-conference-icvs-2021-virtual-event-
september-22-24-2021-proceedings-1st-edition-markus-vincze/

Towards Autonomous Robotic Systems: 22nd Annual

Conference, TAROS 2021, Lincoln, UK, September 8–10,
2021, Proceedings 1st Edition Charles Fox

https://ebookmeta.com/product/towards-autonomous-robotic-
systems-22nd-annual-conference-taros-2021-lincoln-uk-
september-8-10-2021-proceedings-1st-edition-charles-fox/

Advances in Databases and Information Systems 25th

European Conference ADBIS 2021 Tartu Estonia August 24
26 2021 Proceedings 1st Edition Ladjel Bellatreche

https://ebookmeta.com/product/advances-in-databases-and-
information-systems-25th-european-conference-adbis-2021-tartu-
estonia-august-24-26-2021-proceedings-1st-edition-ladjel-
bellatreche/

Mobile and Ubiquitous Systems Computing Networking and

Services 18th EAI International Conference MobiQuitous
2021 Virtual Event November 8 11 2021 Proceedings
Takahiro Hara
https://ebookmeta.com/product/mobile-and-ubiquitous-systems-
computing-networking-and-services-18th-eai-international-
conference-mobiquitous-2021-virtual-event-
Computational Logistics 12th International Conference
ICCL 2021 Enschede The Netherlands September 27 29 2021
Proceedings Martijn Mes (Editor)

https://ebookmeta.com/product/computational-logistics-12th-
international-conference-iccl-2021-enschede-the-netherlands-
september-27-29-2021-proceedings-martijn-mes-editor/

Parallel Computing Technologies 16th International

Conference PaCT 2021 Kaliningrad Russia September 13 18
2021 Proceedings Victor Malyshkin (Editor)

https://ebookmeta.com/product/parallel-computing-
technologies-16th-international-conference-pact-2021-kaliningrad-
russia-september-13-18-2021-proceedings-victor-malyshkin-editor/

Flexible Query Answering Systems 14th International

Conference FQAS 2021 Bratislava Slovakia September 19
24 2021 Proceedings Lecture Notes in Artificial
Intelligence Troels Andreasen (Editor)
https://ebookmeta.com/product/flexible-query-answering-
systems-14th-international-conference-fqas-2021-bratislava-
slovakia-september-19-24-2021-proceedings-lecture-notes-in-
artificial-intelligence-troels-andreasen-editor/

Big Data Analytics and Knowledge Discovery: 23rd

International Conference, DaWaK 2021, Virtual Event,
September 27–30, 2021, Proceedings 1st Edition
Golfarelli
https://ebookmeta.com/product/big-data-analytics-and-knowledge-
discovery-23rd-international-conference-dawak-2021-virtual-event-
september-27-30-2021-proceedings-1st-edition-golfarelli/

Software Engineering and Formal Methods: 19th

International Conference, SEFM 2021, Virtual Event,
December 6–10, 2021, Proceedings 1st Edition Calinescu

https://ebookmeta.com/product/software-engineering-and-formal-
methods-19th-international-conference-sefm-2021-virtual-event-
december-6-10-2021-proceedings-1st-edition-calinescu/
Volume 1442

Communications in Computer and

Information Science

Editorial Board
Joaquim Filipe
Polytechnic Institute of Setúbal, Setúbal, Portugal

Ashish Ghosh
Indian Statistical Institute, Kolkata, India

Raquel Oliveira Prates

Federal University of Minas Gerais (UFMG), Belo Horizonte, Brazil

Lizhu Zhou
Tsinghua University, Beijing, China

More information about this series at http://​www.​springer.​com/​

series/​7899
Editors
Murat Yilmaz, Paul Clarke, Richard Messnarz and Michael Reiner

Systems, Software and Services Process

Improvement
28th European Conference, EuroSPI 2021, Krems,
Austria, September 1–3, 2021, Proceedings
1st ed. 2021
Editors
Murat Yilmaz
Gazi University, Ankara, Turkey

Paul Clarke
Dublin City University, Dublin, Ireland

Richard Messnarz
I.S.C.N. GesmbH, Graz, Austria

Michael Reiner
IMC University of Applied Sciences Krems, Krems, Austria

ISSN 1865-0929 e-ISSN 1865-0937

Communications in Computer and Information Science
ISBN 978-3-030-85520-8 e-ISBN 978-3-030-85521-5
https://doi.org/10.1007/978-3-030-85521-5

© Springer Nature Switzerland AG 2021

This work is subject to copyright. All rights are reserved by the

Publisher, whether the whole or part of the material is concerned,
specifically the rights of translation, reprinting, reuse of illustrations,
recitation, broadcasting, reproduction on microfilms or in any other
physical way, and transmission or information storage and retrieval,
electronic adaptation, computer software, or by similar or dissimilar
methodology now known or hereafter developed.

The use of general descriptive names, registered names, trademarks,

service marks, etc. in this publication does not imply, even in the
absence of a specific statement, that such names are exempt from the
relevant protective laws and regulations and therefore free for general
use.
The publisher, the authors and the editors are safe to assume that the
advice and information in this book are believed to be true and accurate
at the date of publication. Neither the publisher nor the authors or the
editors give a warranty, expressed or implied, with respect to the
material contained herein or for any errors or omissions that may have
been made. The publisher remains neutral with regard to jurisdictional
claims in published maps and institutional affiliations.

This Springer imprint is published by the registered company Springer

Nature Switzerland AG
The registered company address is: Gewerbestrasse 11, 6330 Cham,
Switzerland
Preface
This volume comprises the proceedings of the 28th Systems, Software
and Services Process Improvement (EuroSPI) Conference, held during
September 1–3, 2021 in Krems, Austria.
Conferences have so far been held in Dublin (Ireland) in 1994, in
Vienna (Austria) in 1995, in Budapest (Hungary) in 1997, in
Gothenburg (Sweden) in 1998, in Pori (Finland) in 1999, in
Copenhagen (Denmark) in 2000, in Limerick (Ireland) in 2001, in
Nuremberg (Germany) in 2002, in Graz (Austria) in 2003, in Trondheim
(Norway) in 2004, in Budapest (Hungary) in 2005, in Joensuu (Finland)
in 2006, in Potsdam (Germany) in 2007, in Dublin (Ireland) in 2008, in
Alcala (Spain) in 2009, in Grenoble (France) in 2010, in Roskilde
(Denmark) in 2011, in Vienna (Austria) in 2012, in Dundalk (Ireland) in
2013, in Luxembourg in 2014, in Ankara (Turkey) 2015, in Graz
(Austria) in 2016, in Ostrava (Czech Republic) in 2017, in Bilboa
(Spain) in 2018, in Edinburgh (UK) in 2019, in Dü sseldorf (Germany) in
2020, and in Krems (Austria) in 2021.
EuroSPI is an initiative with the following major goals http://​www.​
eurospi.​net:
Establishing an annual EuroSPI conference supported by software
process improvement networks from different EU countries.
Establishing a social media strategy with groups in LinkedIn,
Facebook, Twitter and online statements, speeches, and keynotes on
YouTube, and a set of proceedings and recommended books.
Establishing an effective team of national representatives (from each
EU- country), which should grow step by step to include more
countries of Europe.
Establishing a European Qualification Framework for a pool of
professions working with SPI and management. This is supported by
European certificates and examination systems.
EuroSPI has a cooperation agreement with the EU Blueprint for
Automotive project DRIVES (2018–2021), where leading automotive
organizations discuss and present skills for the Europe 2030 strategy in
the automotive sector.
 EuroSPI also has a cooperation agreement with the EU Blueprint for
Battery Systems ALBATTS (2020–2023), where leading industrial
organizations discuss and present skills for the creation of battery
production in Europe for cars, ships, planes, industry plants, etc.
In addition, EuroSPI has established the SPI Manifesto (SPI =
Systems, Software and Services Process Improvement), a set of social
media groups including a selection of presentations and keynotes freely
available on YouTube, and access to job role-based qualification
through the European Certification and Qualification Association
(www.​ecqa.​org).
From 2013 onwards, new communities (cybersecurity, Internet of
Things, Agile) joined EuroSPI² and the meaning of the letter S was
extended to System, Software, Service, Safety, and Security and the
meaning of the letter I was extended to Improvement, Innovation, and
Infrastructure (Internet of Things).
In memory of our dear friend and long term EuroSPI Conference
Series Editor, Prof. Rory O’Connor of Dublin City University and Lero –
the Science Foundation Ireland Research Centre for Software, the
committee has in collaboration with ISCN, ASQ, and Lero, established
the Rory O’Connor Award for Research Excellence. On an annual basis,
the individual presenting the highest quality work to the conference
audience, especially in areas of major importance to our field, is
awarded this honor.
A typical characterization of EuroSPI is reflected in a statement
made by a company: “... the biggest value of EuroSPI lies in its function
as a European knowledge and experience exchange mechanism for SPI
and innovation.”
Since its beginning in 1994 in Dublin, the EuroSPI initiative has
outlined that there is not a single silver bullet with which to solve SPI
issues, but that you need to understand a combination of different SPI
methods and approaches to achieve concrete benefits. Therefore, each
proceedings volume covers a variety of different topics, and at the
conference we discuss potential synergies and the combined use of
such methods and approaches.
These proceedings contain 15 selected research papers and 36
industry contributions under nine core themes:
I: SPI and Emerging Software and Systems Engineering Paradigms
 II: SPI and Team Skills and Diversity
III: SPI and Recent Innovations
IV: SPI and Agile
V: SPI and Standards and Safety and Security Norms
VI: SPI and Good and Bad Practices
VII: SPI and Digitalization of Industry, Infrastructure, and E-Mobility
VIII: SPI and Good/Bad SPI Practices in Improvement
IX: Virtual Reality (VR)
Of the core research contributions, only the highest quality research
submissions were accepted. Theme I presents two papers related to SPI
and emerging software and system engineering paradigms. Theme II
presents a single paper related to team skills and diversity. Theme III
presents two papers exploring SPI and recent innovations, while Theme
IV contains two papers focused on Agile software development and SPI.
Theme V includes two further papers concerned with standards and
safety in software development, with Theme VI presenting four
contributions on the topic of good and bad SPI practices. Theme VII
contains a single paper on cybersecurity, and Theme VIII presents a
further paper focused on digitalization, infrastructure, and e-mobility.
Industry contributions are presented separately to the core
research contributions in these proceedings. Theme I presents five
papers related to SPI and emerging software and system engineering
paradigms. Theme II presents three papers exploring SPI and recent
innovations, while Theme III contains three papers focused on Agile
software development and SPI. Theme IV includes four additional
industrial workshop contributions concerned with standards and
safety in software development, with Theme V presenting two further
contributions on the topic of good and bad SPI practices. Theme VI
contains six papers on cybersecurity, and Theme VII presents eight
further contributions focused on digitalization, infrastructure, and e-
mobility. Finally, Theme VIII contains five industry contributions
focused on virtual reality.
To encourage synergy between best academic and industrial
practices, the various core research and industrial contributions to this
conference are presented side by side at the conference under the nine
key themes identified for this EuroSPI edition.
Murat Yilmaz
 Paul Clarke
Richard Messnarz
Michael Reiner
September 2021
Recommended Further Reading
In [1] the proceedings of three EuroSPI conferences were integrated
into a single book, which was edited by 30 experts in Europe. The
proceedings of EuroSPI 2005 to 2020 inclusive have been published by
Springer in [2–17], respectively.

References
1. Messnarz, R., Tully, C. (eds.): Better Software Practice for Business
Benefit – Principles and Experience, 409 pages. IEEE Computer Society
Press, Los Alamitos (1999)
2. Richardson, I., Abrahamsson, P., Messnarz, R. (eds.): Software
Process Improvement. LNCS, vol. 3792, p. 213. Springer, Heidelberg
(2005)
3. Richardson, I., Runeson, P., Messnarz, R. (eds.): Software Process
Improvement. LNCS, vol. 4257, pp. 11–13. Springer, Heidelberg (2006)
4. Abrahamsson, P., Baddoo, N., Margaria, T., Messnarz, R. (eds.):
Software Process Improvement. LNCS, vol. 4764, pp. 1–6. Springer,
Heidelberg (2007)
5. O’Connor, R.V., Baddoo, N., Smolander, K., Messnarz, R. (eds):
Software Process Improvement.CCIS, vol. 16, Springer, Heidelberg
(2008).
6. O’Connor, R.V., Baddoo, N., Gallego C., Rejas Muslera R., Smolander,
K., Messnarz, R. (eds): Software Process Improvement. CCIS, vol. 42,
Springer, Heidelberg (2009).
7. Riel A., O’Connor, R.V. Tichkiewitch S., Messnarz, R. (eds):
Software, System, and Service Process Improvement. CCIS, vol. 99,
Springer, Heidelberg (2010).
8. O’Connor, R., Pries-Heje, J. and Messnarz R., Systems, Software
and Services Process Improvement, CCIS Vol. 172, Springer-Verlag,
(2011).
9. Winkler, D., O’Connor, R.V. and Messnarz R. (Eds), Systems,
Software and Services Process Improvement, CCIS 301, Springer-Verlag,
(2012).
10. McCaffery, F., O’Connor, R.V. and Messnarz R. (Eds), Systems,
Software and Services Process Improvement, CCIS 364, Springer-Verlag,
(2013).
11. Barafort, B., O’Connor, R.V. and Messnarz R. (Eds), Systems,
Software and Services Process Improvement, CCIS 425, Springer-Verlag,
(2014).
12. O’Connor, R.V. Akkaya, M., Kemaneci K., Yilmaz, M., Poth, A. and
Messnarz R. (Eds), Systems, Software and Services Process
Improvement, CCIS 543, Springer-Verlag, (2015).
13. Kreiner, C., Poth., A., O’Connor, R.V., and Messnarz R. (Eds),
Systems, Software and Services Process Improvement, CCIS 633,
Springer-Verlag, (2016).
14. Stolfa, J, Stolfa, S., O’Connor, R.V., and Messnarz R. (Eds), Systems,
Software and Services Process Improvement, CCIS 633, Springer-Verlag,
(2017).
15. Larrucea, X., Santamaria, I., O’Connor, R.V., Messnarz, R. (Eds),
Systems, Software and Services Process Improvement, CCIS Vol. 896,
Springer-Verlag, (2018)
16. Walker A., O’Connor, R.V., Messnarz, R. (Eds), Systems, Software
and Services Process Improvement, CCIS Vol. 1060, Springer-Verlag,
(2019)
17. Yilmaz M, Niemann, J., Clarke, P., Messnarz, R. (Eds.) Systems,
Software and Services Process Improvement, CCIS Vol. 1251, Springer-
Verlag, (2020)
Acknowledgments
Some contributions published in this book have been funded with
support from the European Commission. European projects
(supporting ECQA and EuroSPI) contributed to this Springer book
including DRIVES – BLUEPRINT Project (591988-EPP-1-2017-1-CZ-
EPPKA2-SSA-B), OpenInnotrain (H2020-MSCA-RISE-2018, exchange of
researchers), ProHeritage (785211 – Pro Heritage – H2020-EE-2016-
2017), ALBATTS – BLUEPRINT Project (612675-EPP-1-2019-1-SE-
EPPKA2-SSA-B), ECEPE Erasmus+ Project (2019-1-CZ01-KA203-
061430), and CyberENG (Cybersecurity Engineer and Manager –
Automotive Sector, Agreement No. 078494).

In this case the publications reflect the views only of the author(s), and
the Commission cannot be held responsible for any use, which may be
made of the information contained therein.
This work was supported, in part, by Science Foundation Ireland grant
13/RC/2094_2 and co-funded under the European Regional
Development Fund through the Southern & Eastern Regional
Operational Programme to Lero - the Science Foundation Ireland
Research Centre for Software (www.​lero.​ie).

In this case the publications reflect the views only of the author(s), and
the Science Foundation Ireland and Lero cannot be held responsible for
any use, which may be made of the information contained therein.
Organization

General Chair and Workshop Chair

Richard Messnarz ISCN GesmbH, Graz, Austria

General Co-chair
Micheal Mac an Airchinnigh ISCN, Ireland

Scientific Chairs
Murat Yilmaz Gazi University, Turkey
Paul Clarke Dublin City University, Ireland

Organization Chairs
Richard Messnarz ISCN GesmbH, Graz, Austria
Andreas Riel Grenoble INP, France
Damjan Ekert ISCN GesmbH, Austria
Tobias Zehetner ISCN GesmbH, Austria
Laura Aschbacher ISCN GesmbH, Austria

Local Organization Chairs

Richard Messnarz ISCN GesmbH, Austria
Michael Reiner IMC FH Krems, University of Applied Sciences, Austria

Emerging and Multidisciplinary Approaches to

Software Engineering Co-chairs
Murat Yilmaz Gazi University, Turkey
Paul Carke Dublin City University, Ireland
Ricardo Colomo-Palacios Ostfold University College, Norway
Richard Messnarz
ISCN GesmbH, Graz, Austria
Mirna Munoz CIMAT, Mexico

Recent Innovations Co-chairs

Bruno Wöran Merinova, Finland
Georg Macher TU Graz, Austria
Tom Peisl Hochschule Munich, Germany
Samer Sameh VALEO, Egypt
Gabriele Sauberer ECQA and TermNet, Austria
Joanne Hyland rInnovationGroup, USA
Richard Messnarz ISCN GesmbH, Austria
Laura Aschbacher ISCN GesmbH, Austria

Experiences with Agile and Lean Co-chairs

Alexander Poth Volkswagen AG, Germany
Susumu Sasabe JUSE, Japan
Khaled Badr VALEO, Egypt
Antonia Mas University of the Balearic Islands, Spain

Standards and Assessment Models Co-chairs

Gerhard Griessnig AVL, Austria
Klaudia Dussa Zieger IMBUS, Germany
Samer Sameh VALEO, Egypt

Good and Bad Practices in Improvement Co-chairs

Elli Goergiadou Middlesex University, UK
Eva Breske Robert Bosch Engineering, Germany
Tomas Schweigert ExpleoGroup, Germany
Kerstin Siakas International Hellenic University, Greece, and Vaasa
University, Finland
Mirna Munoz CIMAT, Mexico

Functional Safety and Cybersecurity Co-chairs

Alexander Much Elektrobit, Germany
Miklos Biro SCCH, Austria
Richard Messnarz ISCN GesmbH, Austria

Digitalization of Industry, Infrastructure, and E-

Mobility Co-chairs
Peter Dolejsi ACEA, the European Automobile Manufacturers
Association
Jakub Stolfa VSB Ostrava, Czech Republic
Svatopluk Stolfa VSB Ostrava, Czech Republic
Andreas Riel Grenoble INP, France
Michael Reiner University of Applied Sciences Krems, Austria
Georg Macher TU Graz, Austria
Richard Messnarz ISCN GesmbH, Austria

Virtual Reality Co-chairs

Michael Reiner University of Applied Sciences Krems, Austria
Jörg Niemann University of Applied Sciences Dü sseldorf, Germany
Christian Reimann University of Applied Sciences Dortmund,
Germany
Philip Wogart VR/AR Association and Miami Ad School Europe
Hamburg, Germany

Board Members
EuroSPI Board Members represent centers or networks of SPI
excellence having extensive experience with SPI. The board members
collaborate with different European SPINS (Software Process
Improvement Networks). The following have been members of the
conference board for a significant period:
Richard Messnarz, ISCN GesmbH, Austria
Micheal Mac an Airchinnigh, ISCN, Contact Point for Ireland
Paul Clarke, Dublin City University, Ireland
Gabriele Sauberer, TermNet, Austria
Jö rg Niemann, University of Applied Sciences Dü sseldorf, Germany
Andreas Riel, Grenoble Institute of Technology, France
Mikló s Biró , Software Competence Center Hagenberg GmbH,
Johannes Kepler Universitä t Linz, Austria
Ricardo Colomo-Palacios, Ostfold University, Norway
Georg Macher, Graz University of Technology, Austria
Michael Reiner, IMC FH Krems, University of Applied Sciences,
Austria
Murat Yilmaz, Gazi University, Turkey
Jakub Stolfa, VSB Ostrava, Czech Republic

EuroSPI Scientific and Industry Program

Committee
EuroSPI established an international committee of selected well-known
experts in SPI who are willing to be mentioned in the program and to
review a set of papers each year. The list below represents the Research
and Industry Program Committee members. EuroSPI also has a
separate Industrial Program Committee responsible for the
industry/experience contributions.

Scientific Program Committee

Biro, Miklos John von Neumann Computer Society, Hungary
Calvo-Manzano Villalon, Jose A. Polytechnic University of Madrid
(UPM), Spain
Clarke, Paul Dublin City University, Ireland
Colomo-Palacios, Ricardo Ostfold University College, Norway
Dobaj, Jürgen Graz University of Technology, Austria
Fussenecker, Claudia
University of Applied Sciences Dü sseldorf, Germany
Georgiadou, Elli UK
Gokalp, Ebru Hacettepe University, Turkey
Gomez Alvarez, Maria Clara Universidad de Medellin, Colombia
Gulec, Ulas TED University, Turkey
Hirz, Mario Graz University of Technology, Austria
Krisper, Michael Graz University of Technology, Austria
Macher, Georg Graz University of Technology, Austria
Macmahon, Silvana Togneri Dublin City University, Ireland
Makkar, Samer VALEO Egypt, Egypt
Martins, Paula University of the Algarve, Portugal
Matthies, Christoph Hasso Plattner Institute, Germany
Mas, Antonia University of the Balearic Islands, UIB, Spain
Mayer, Nicolas Luxembourg Institute of Science and Technology
(LIST), Luxembourg
Mesquida Calafat, Antoni Lluís University of the Balearic Islands, UIB,
Spain
Munoz, Mirna CIMAT- Unidad Zacatecas, Mexico
Niemann, Jörg University of Applied Sciences Dü sseldorf, Germany
Paul, Alexander University of Applied Sciences Dü sseldorf, Germany
Regan, Gilbert Dundalk Institute of Technology, Ireland
Riel, Andreas Grenoble INP, France
Rodic, Miran University of Maribor, Slovenia
San Feliu, Tomas Polytechnic University of Madrid (UPM), Spain
Sechser, Bernhard Process Fellows, Germany
Stolfa, Jakub VSB Ostrava, Czech Republic
Stolfa, Svatopluk VSB Ostrava, Czech Republic
Treacy, Ceara Dundalk Institute of Technology, Ireland
Winkler, Dietmar University of Technology Vienna, Austria
Wolski, Marcin Poznan University of Technology, Poland
Yilmaz, Murat Gazi University, Turkey

Industrial Program Committee

Barafort, Beatrix Luxembourg Institute of Science and Technology
(LIST), Luxembourg
Breske, Eva Bosch Engineering GmbH, Germany
Daughtrey, Taz American Society for Quality, USA
Dreves, Rainer Continental Corporation, Germany
Dussa-Zieger, Klaudia imbus AG, Germany
Ekert, Damjan ISCN GesmbH (Slovenia), Slovenia
Fehlmann, Thomas Euro Project Office AG, Switzerland
Griessnig, Gerhard AVL List GmbH, Austria
Ito, Masao Nil Software Corp., Japan
Johansen, Jorn Whitebox, Denmark
Kaynak, Onur ASELSAN, Turkey
Keskin Kaynak, Ilgi ASELSAN, Turkey
Larrucea, Uriarte Xabier Tecnalia, Spain
Lindermuth, Peter Magna Powertrain, Austria
Mayer, Nicolas Luxembourg Institute of Science and Technology
(LIST), Luxembourg
Mandic, Irenka Magna Powertrain, Austria
Messnarz, Richard ISCN (Austria), Austria
Morgenstern, Jens Germany
Much, Alexander Elektrobit Automotive GmbH, Germany
Nevalainen, Risto Falconleader, Finland
Norimatsu, So JASPIC, Japan
Peisl, Tom University of Applied Sciences Munich, Germany
Poth, Alexander Volkswagen AG, Germany
Reiner, Michael IMC Krems, Austria
Sasabe, Susumu JUSE, Japan
Sauberer, Gabriele TermNet, Austria
Schweigert, Tomas ExpleoGroup, Germany
Sechser, Bernhard Process Fellows GmbH, Germany
Spork, Gunther Magna Powertrain, Austria
Stefanova Pavlova, Maria CITT Global, Bulgaria
Steger, Bernhardt ISCN GesmbH, Austria
Varkoi, Timo Spinet, Finland
Wegner, Thomas ZF Friedrichshafen AG, Germany
Contents
Core Research Contributions: SPI and Emerging Software and
Systems Engineering Paradigms
A Blockchain-Enabled Framework for Requirements Traceability
Selina Demi, Mary Sá nchez-Gordó n and Ricardo Colomo-Palacios
To Work from Home (WFH) or Not to Work from Home?​Lessons
Learned by Software Engineers During the COVID-19 Pandemic
Aifric Nolan, Rachel White, Mahjabeen Soomro,
Boluwatife Comfort Dopamu, Murat Yilmaz, David Solan and
Paul Clarke
Core Research Contributions: SPI and Team Skills and Diversity
The Influence of Specialised University Degrees on Employee’s
Performance
Bahadur Shah, Eren Aykanat, Raphael Edlmann, Ehson Shah and
Thomas Peisl
Core Research Contributions: SPI and Recent Innovations
Linking Innovation and eLearning – The Case for an Embedded
Design
Alexander Ziegler, Thomas Peisl and Patrick Harte
The Need of an Innovation Agent:​Requirements and Competencies
of the Human Dimension in Innovation Management
Anja Del Fabbro, Alexander Niklas and Thomas Peisl
Core Research Contributions: SPI and Agile
Towards a Guide for Risk Management Integration in Agile
Software Projects
Jean Carlo Rossa Hauck and Marcel Vieira
Orchestrating Agile IT Quality Management for Complex Solution
Development Through Topic-Specific Partnerships in Large
Enterprises – An Example on the EFIS Framework
Alexander Poth, Mario Kottke and Andreas Riel
Core Research Contributions: SPI and Standards and Safety and
Security Norms
Towards a Process-Based Approach to Compliance with GDPR
Stéphane Cortina, Michel Picard, Samuel Renault and
Philippe Valoggia
Impact of the New A-SPICE Appendix for Cybersecurity on the
Implementation of ISO26262 for Functional Safety
Noha Moselhy and Yasser Ali
Core Research Contributions: SPI and Good/Bad SPI Practices in
Improvement
Symptom-Based Improvement Advice:​A New Relevant-Focused
Problem-Based Framework
Jan Pries-Heje, Jørn Johansen and Morten Korsaa
Passively Acquiring Information Must End
Hermann Maurer, Bilal Zaka and Sonja Eisenberger
Towards a Multidimensional​Self-assessment for Software Process
Improvement:​A Pilot Tool
Elli Georgiadou, Eleni Berki, Kerstin Siakas, Samer Sameh,
John Estdale, Harjinder Rahanu, Margaret Ross, Richard Messnarz
and Juri Petri Valtanen
A Multidimensional​Review and Extension of the SPI Manifesto
Using STEEPLED Analysis:​An Expert Validation
Elli Georgiadou, Kerstin Siakas, Eleni Berki, John Estdale,
Harjinder Rahanu, Margaret Ross and Richard Messnarz
Core Research Contributions: SPI and Functional Safety and
Cybersecurity
Automotive Cybersecurity - Training the Future
Christoph Schmittner, Abdelkader Shaaban, Svatopluk Stolfa,
Jakub Stolfa, Jan Plucar, Marek Spanyik, Alen Salamun,
Richard Messnarz, Damjan Ekert, Georg Macher and
Alexander Much
Core Research Contributions: Digitalisation of Industry,
Infrastructure and E-Mobility
The Impact of Train Station Topologies on Operation of
Autonomous People Movers
Walter Sebron, Elaheh Gol-Hashem, Peter Krebs and Hans Tschü rtz
Selected Industrial Contributions: SPI and Emerging Software and
Systems Engineering Paradigms
Gamification Principles to Decrease SPI Change Resistance
Gloria Piedad Gasca-Hurtado, María Clara Gó mez-Á lvarez,
Mirna Muñ oz and Jezreel Mejía
Towards Reducing Communication Gaps in Multicultural and
Global Requirements Elicitation
Errikos Siakas, Harjinder Rahanu, Elli Georgiadou and
Kerstin Siakas
Gamification Framework in Automotive SW Development
Environment to Increase Teams Engagement
Mourad Mounir, Khaled Badr and Samer Sameh
Introduction to Text Classification:​Impact of Stemming and
Comparing TF-IDF and Count Vectorization as Feature Extraction
Technique
André Wendland, Marco Zenere and Jö rg Niemann
Digital Transformation and the Role of Dynamic Tooling in
Extracting Microservices from Existing Software Systems
Neil Lapuz, Paul Clarke and Yalemisew Abgaz
Selected Industrial Contributions: SPI and Recent Innovations
Innovation Agents – Moving from Process Driven to Human
Centred Intelligence Driven Approaches
Thomas Peisl, Joanne Hyland, Richard Messnarz, Bruno Wö ran,
Samer Sameh, Georg Macher, Jü rgen Dobaj, Laura Aschbacher and
Detlev Aust
Balancing Exploration and Exploitation Through Open Innovation
in the Automotive Domain – Focus on SMEs
Georg Macher and Omar Veledar
A Professional Career with Autism:​Findings from a Literature
Review in the Software Engineering Domain
 Emma Costello, Sara Kilbride, Zoe Milne, Paul Clarke, Murat Yilmaz
and Silvana Togneri MacMahon
Selected Industrial Contributions: SPI and Agile
Knowledge Sharing in Agile Settings:​State of the Practice of
Organizational Training
Sabrina Gutiérrez, Valeria Henriquez and Ana M. Moreno
ART for Agile:​Autonomous Real-Time Testing in the Product
Development Cycle
Thomas Fehlmann and Eberhard Kranich
Building the Bridge Between Automotive SPICE® and Agile
Development
Claudia Salazar Dorn and Christian L. Knü vener
Selected Industrial Contributions: SPI and Standards and Safety
and Security Norms
The Cybersecurity Extension for ASPICE - A View from ASPICE
Assessors
Christian Schlager and Georg Macher
Post Pandemic Era:​Future of the Automotive Online Assessments
Samer Sameh, Ahmed Alborae, Selina Meza, Damjan Ekert,
Ibrahim Sobh and Ahmed Seddik
An Exploratory Analysis of the Perception of the Utility of Proven
Practices of the Software Basic Profile of ISO/​IEC 29110 by a Set of
VSEs in Mexico
Mirna Muñ oz, Jezreel Mejia, Adriana Peñ a, Claude Laporte,
Gloria Piedad Gasca-Hurtado and Maria Clara Gó mez-Á lvarez
Speed-Up Testing by Application of Semiformal Notations and
Automation
Martin Ringdorfer and Gerhard Griessnig
Selected Industrial Contributions: SPI and Good/Bad SPI Practices
in Improvement
Monitoring the Adoption of SPI-Related Best Practices.​An
Experience Report
 Bartosz Walter, Branko Marović, Ivan Garnizov, Marcin Wolski and
Andrijana Todosijevic
Cultural Diversity – Building up a Network of Standarised Expert’s
Skills for Cultural Heritage of the European Union
Gerald Wagenhofer, Reinhold Sahl and Bernhardt Steger
Selected Industrial Contributions: SPI and Functional Safety and
Cybersecurity
A Proposal for the Tailoring of AUTOSAR Coding Guidelines C++ to
ISO 26262-6:​2018
Ricardo Eito-Brun
Dealing with Privacy for Protecting Information
Xabier Larrucea and Izaskun Santamaria
First Experiences with the Automotive SPICE for Cybersecurity
Assessment Model
Richard Messnarz, So Norimatsu, Jü rgen Dobaj, Damjan Ekert,
Georg Macher, Tobias Zehetner and Laura Aschbacher
Asset Driven ISO/​SAE 21434 Compliant Automotive Cybersecurity
Analysis with ThreatGet
Christoph Schmittner, Bernhard Schrammel and Sandra Kö nig
A-SPICE for Cybersecurity:​Analysis and Enriched Practices
Esraa Magdy
FMEA Integration in Requirements Management as a Basis for an
Automotive SPICE© Level 3 Project
Ovi Bachmann and Bernhardt Steger
Selected Industrial Contributions: Digitalisation of Industry,
Infrastructure and E-Mobility
Ethical Issues Invoked by Industry 4.​0
Harjinder Rahanu, Elli Georgiadou, Kerstin Siakas, Margaret Ross
and Eleni Berki
How to Train the Future European Service Engineer?​
Jö rg Niemann, Claudia Fussenecker, Alexander Paul,
Marius Schö ning, Martin Schlö sser and Dominik Kretschmar
SOTIF Process and Methods in Combination with Functional Safety
Dietmar Kinalzyk
Challenges in Transition of System Engineering Oriented
Organization to a Service Management Perspective
Ayşegü l Ü nal, Onur Kaynak and Taner Ö zdemir
The European CHAISE Initiative to Shape the Future of Blockchain
Skill Qualification and Certification
Dionysios Solomos, Nikos Tsianos, Parisa Ghodous and Andreas Riel
Normative Documents for Electric Vehicles and Possibilities for
Their Application in the Education of E-Powertrain Engineers
Nikolay Pavlov, Boyko Gigov and Maria Stefanova-Pavlova
Steering Drivers of Change:​Maximising Benefits of Trustworthy
IoT
Omar Veledar, Eric Armengaud, Leo Happ Botler,
Violeta Damjanovic-Behrendt, Christian Derler, Stefan Jaksic,
Lukas Krammer, Christian Lettner, Georg Macher,
Stefan Marksteiner, Andreas Martin, Martin Matschnig, Peter Priller,
Sebastian Ramacher, Kay Rö mer, Christoph Schmittner,
Christina Tiefnig, Heribert Vallant, Heinz Weiskirchner and
Mario Drobics
Electric Powertrain Engineer Skills Needs and Pilot Course
Implementation
Svatopluk Stolfa, Jakub Stolfa, Petr Š imoník, Richard Messnarz,
Damjan Ekert, Georg Macher, Eugen Brenner, Nikolay Pavlov,
Boyko Gigov, Maria Stefanova-Pavlova, Marius Schoening,
Alexander Paul, Jö rg Niemann and Claudia Fussenecker
Selected Industrial Contributions: Virtual Reality
PlaySAFe:​Results from a Virtual Reality Study Using Digital Game-
Based Learning for SAFe Agile Software Development
Emer O’Farrell, Murat Yilmaz, Ulas Gulec and Paul Clarke
Usability and Task Load of Applications in Augmented and Virtual
Reality:​How Applicable are the Technologies in Corporate
Settings?​
 Helena Lovasz-Bukvova, Marvin Hö lzl, Gerhard Kormann-Hainzl,
Thomas Moser, Tanja Zigart and Sebastian Schlund
Virtual Reality Applications for Experiential Tourism - Curator
Application for Museum Visitors
Sandra Pfiel, Helena Lovasz-Bukvova, Florian Tiefenbacher,
Matej Hopp, René Schuster, Michael Reiner and Deepak Dhungana
Virtual Reality as a Tool for Education and Training in Intensive
Care
Sarah Horwitz
Agile Development of Cross-University Digital Education
Ecosystems
Carsten Wolff, Christian Reimann, Olha Mikhieieva and
Ekaterina Mikhaylova
Author Index
Core Research Contributions: SPI and
Emerging Software and Systems
Engineering Paradigms
© Springer Nature Switzerland AG 2021
M. Yilmaz et al. (eds.), Systems, Software and Services Process Improvement,
Communications in Computer and Information Science 1442
https://doi.org/10.1007/978-3-030-85521-5_1

A Blockchain-Enabled Framework for

Requirements Traceability
Selina Demi1 , Mary Sá nchez-Gordó n1 and Ricardo Colomo-
Palacios1
(1) Østfold University College, Halden, Norway

Selina Demi
Email: selina.demi@hiof.no

Mary Sánchez-Gordón (Corresponding author)

Email: mary.sanchez-gordon@hiof.no

Ricardo Colomo-Palacios
Email: ricardo.colomo-palacios@hiof.no

Abstract
Requirements traceability has been broadly recognized by researchers
as an important quality of any software development process. However,
among stakeholders, requirements traceability is often perceived as an
extra task that disrupts their workflow. This perceived overhead
demotivates stakeholders to participate in the creation, maintenance
and use of traceability links. The challenges of implementing
requirements traceability are amplified when complex and large-scale
software systems are developed by cross-organizational and
distributed teams. Different organizational backgrounds, conflicting
objectives, and organizational boundaries lead to trust issues that
complicate the implementation of traceability in such settings. In this
paper, the authors propose a blockchain-enabled framework for
requirements traceability. This framework aims to: (i) enable a holistic
and reliable view of artifacts and traceability links, (ii) provide an
incentive mechanism for creators of traceability links, (iii) ensure the
authenticity and quality of traceability links by means of voting
mechanisms, (iv) facilitate comprehension from traceability
information through query services, and (v) enable interactive
graphical visualization of traceability links.

Keywords Requirements traceability – Blockchain technology – Smart

contracts – Distributed software development

1 Introduction
Requirements traceability refers to “the ability to follow the life of a
requirement in both a forward and backward direction” [1]. The need
to maintain bidirectional traceability of requirements for quality
purposes has been formulated by software process improvement
models, such as CMMI, ISO/IEC 15504 (SPICE) [2] and more recently
ISO/IEC 33000. Requirements traceability contributes to the
development of high-quality software, as it supports many activities of
the software development lifecycle, for instance, software maintenance
[3], project management [4], change management and impact analysis
[5]. However, in practice, traceability is perceived as an extra task that
practitioners need to perform or as an activity that disrupts their
workflow [6]. This perceived overhead can be explained by the
provider-user gap, meaning that creators of trace links are often not the
ones who use them [6, 7]. For instance, developers create links between
implementation tasks and source code commits which are actually used
by project managers to track project’s progress. Thereby, developers
become demotivated and set a low priority to traceability tasks, which
may lead to incorrect or missing links. Maro et al. [6] proposed the
incorporation of gamification elements into traceability tools to
increase the motivation and engagement of developers in traceability
creation and maintenance tasks. Moreover, Wohlrab et al. [7] carried
out 24 interviews to explore the relation between traceability
management and collaboration. The respondents proposed the
inclusion of voting features into traceability tools to enable
stakeholders to jointly indicate incorrect links or to agree with the
connected artifacts. This collaborative effort improves the
effort/benefit ratio, which in turn motivates developers to contribute to
traceability management.
As the complexity of software increases, the development is carried
out by cross-organizational and distributed teams. This paradigm
complicates traceability, particularly when distributed teams need to
share artifacts [6]. In such environments, previous literature proposed
the use of a centralized data storage in which all artifacts are stored and
accessed by distributed stakeholders [6]. However, artifacts provided
by distributed teams cannot always be trusted, as they may have
malicious intentions [8]. The participation of third-party vendors
exacerbates trust issues, due to different organizational background,
conflicting objectives, and organizational boundaries [9]. Different
organizations may use different tools, methodologies, and processes
that reside within the organizational boundaries, making it difficult to
leverage requirements traceability in an efficient manner [9].
Additionally, organizational objectives of one organization may
contradict objectives of the other organizations that are involved in the
project. For instance, organizations may create incompatible links in
terms of type or granularity, which leads to unusable trace links [6].
Finally, organizational boundaries can imply restricted access to some
artifacts due to confidentiality constraints [6, 9] which in turn
complicates the creation of complete traceability. To address these
challenges, there is a need for a reliable and shared traceability
knowledge base, in order to keep track of all artifacts and trace links
created by distributed stakeholders throughout the software
development lifecycle (SDLC). This can be achieved by means of
blockchain technology.
Blockchain is a distributed ledger that stores transaction records in
blocks. Each block includes the hash of the preceding block to point to
the previously validated block in the chain [10]. This structure of a
cryptographically linked list ensures immutability which refers to the
inability to tamper with the contents stored on the blockchain. The
main utility of blockchain is that it enables the exchange of data or
transactions among untrusted participants in a distributed network,
without relying on a centralized trusted party. Centralized third parties
are prone to failures, malfunctions, and security compromises which
may lead to system unavailability [11]. Blockchain-based systems
overcome these risks, as every participant keeps a copy of the ledger
and can verify the legitimacy of the transactions [10]. Since 2015, the
potential of blockchain technology extended greatly due to the
introduction of smart contracts [12]. Smart contracts are self-executing
computer programs that run across the blockchain network and enable
trusted transactions and agreements among different parties [13]. The
results of smart contracts execution are verified by the nodes of the
network and stored on the distributed ledger. Smart contracts were
originally conceived to automatically implement the terms of the
contract that two parties agreed upon in a trustless environment [14].
Nowadays, the scope of smart contracts has been largely extended to
perform any conceivable task, similarly to general-purpose software
programs [14]. Smart contracts are intended for a variety of application
domains, ranging from financial, notary, game, wallet to library which
comprises general-purpose operations that can be used by other smart
contracts [15].
In this paper, we propose a blockchain-enabled framework for
requirements traceability. To the best of our knowledge, this is the first
study that uses blockchain to keep track of artifacts and traceability
links in distributed settings. This framework aims to:
enable a holistic and reliable view of artifacts and traceability links
provide an incentive mechanism for creators of traceability links
ensure the authenticity and quality of traceability links by means of
voting mechanisms
facilitate comprehension from traceability information through
query services
enable interactive graphical visualization of traceability links
The paper is structured as follows: Related work is presented in
Sect. 2. Section 3 describes the proposed framework, and Sect. 4
concludes the work and presents future research directions.

2 Related Work
Mader et al. [16] emphasized the importance of a traceability
information model in facilitating traceability creation and maintenance.
These authors presented the traceability information model used by
their prototype, namely, traceMaintainer. They conducted experiments
with subjects who were provided with the traceability information
model and were required to create trace links between use cases and
analysis classes and trace links between analysis classes and design
classes. The subjects reported that they were satisfied with the
guidance provided when creating trace links and that traceMaintainer
prevented them from creating trace links in an inappropriate manner.
The authors advocate the use of traceability information models as they
enable different analyses, such as validating traces, impact analysis and
change propagation, coverage analysis, and relation count analysis.
Cleland-Huang et al. [17] proposed a model-based approach that
enables stakeholders to plan and execute traceability strategies in a
graphical modeling environment. This approach consists of four layers:
strategic layer, document management layer, stored query layer, and
executable layer. The strategic layer represents the traceability graph
structure which consists of artifacts and trace paths, using a standard
XML format. The document management layer documents individual
set of artifacts using a standard XML representation. The stored query
layer constructs queries for primitive traces between adjacent artifacts
types, and composite traceability paths between non-adjacent artifacts
in the strategic traceability graph. Finally, the executable layer provides
the user interface to display the pre-defined trace queries and visualize
the results. Our study adopts these conceptual layers, albeit it
implements them in a different manner.
Elamin and Osman [5] proposed a user-defined traceability
metamodel that uses XML patterns to define artifacts, trace links, and
trace type rules. According to these authors, the main limitations of
traceability approaches lie in the representation and storage of
traceability information. To address these limitations, the authors
implemented a graph traceability repository to store artifacts and trace
links. The benefits of the graph repository were demonstrated by
applying it to three varying datasets. The results confirmed that the
graph repository outperforms traceability matrices, cross-reference
tables and relational databases in terms of visualizing trace links,
representing multi-dimensional relations and performance. We adopt
the concept of rules for trace links semantics, however we encode these
rules into smart contracts and store artifacts and trace links on a
distributed ledger.
None of the aforementioned approaches address requirements
traceability in distributed environments. In this regard, Rempel et al.
[9] investigated the need for requirements traceability in inter-
organizational software projects. The authors carried out semi-
structured interviews with 17 organizations. The results indicated that
on the one hand requirements traceability has the potential to address
inherent issues of inter-organizational software projects, such as
compliance, operational excellence and communication between
parties. On the other hand, the different organizational backgrounds,
conflicting objectives, and organizational boundaries were found to
complicate the application of requirements traceability. The authors
presented the following guidelines for distributed requirements
traceability: ensure the reliability and availability of traceability
information, mitigate conflicting objectives and bridge the
technological gap that exists between clients and suppliers. Despite the
valuable insights, this study does not provide further information on
how these guidelines can be implemented.
Furthermore, recent literature has encouraged the cross-
fertilization of software engineering and hyped technologies, such as
blockchain technology [18, 19]. In fact, we have observed an increasing
trend of studies that use blockchain to support software engineering
activities during the last three years [20]. In what follows, we present a
few of these studies: Yilmaz et al. [21] used blockchain to improve the
integrity of the software development process. The authors proposed
an incentive mechanism where developers compete for developing the
best code, instead of being assigned a specific task by the project
manager. This proposal may be valuable to address trust issues,
particularly in large-scale agile development. Bose et al. [22] proposed
a blockchain-oriented framework for trustworthy software provenance
in global software development. The framework captures provenance
data from the variety of tools used throughout the SDLC and transforms
them according to PROV-specifications. The authenticity of these data is
verified by authorized personnel by means of voting mechanisms.
Recently, Singi et al. [23] proposed an incentive framework enabled by
blockchain technology that captures events throughout the entire
software development lifecycle, analyzes these events for their
compliance to incentive policies by means of smart contracts, and
automatically delivers incentives in the form of digitized tokens to
software engineers, accordingly. These studies provide valuable
insights into the applications of blockchain in the software engineering
landscape, however none of the aforementioned studies is devoted to
the use of blockchain for requirements traceability in distributed
settings.

3 Proposed Framework
Figure 1 depicts the blockchain-enabled requirements traceability
framework. The proposed framework consists of the following
components:

Fig. 1. Blockchain-enabled requirements traceability framework

Strategic Layer. A feasibility analysis should be carried out in order

to investigate whether the application of blockchain for requirements
traceability is required and feasible in the given environment. This
analysis should take into consideration the alignment between
blockchain features and requirements traceability strategies,
alternative tools, and technologies for representing and storing
traceability links. The latter has been achieved in the form of
traceability matrices, cross-reference tables, relational databases, and
graph traceability repositories [5]. It is also vital that the analysis
explores the benefits of applying blockchain for requirements
traceability, along with challenges, such as implementation costs,
technical, regulatory and governance challenges. The next component
of the strategic layer is the traceability information model (TIM) which
provides guidance on what software artifacts to trace and what
relations to establish, and consequently prevents inconsistent results in
large projects with many stakeholders [16]. Determining the traceable
artifacts and relations in advance has been considered a best practice
for establishing the traceability environment [24]. Figure 2 depicts a
simple traceability information model which consists of three main
elements, as follows [5]:
Artifacts to define what artifacts should be traced and their
properties.
Trace links to define relations between artifacts based on source
artifact ID and destination artifact ID.
Trace type rules to define the naming rules for the trace links. For
instance, if the source code is related to the requirement, then the
name of the relation is “satisfy”.
These elements can be encoded into smart contracts to enforce the
registration of only those artifacts and trace links that are needed in the
project and automatically identify trace links semantics.
Fig. 2. A simple traceability information model
The last component of the strategic layer is the incentive policy that
aims to define who is eligible to create trace links, how to validate the
quality of trace links, e.g., can be validated by stakeholders using
traceability quality metrics such as correctness, timeliness, accuracy,
completeness, consistency and usefulness [25], and how much
incentive goes for the creation of trace links based on their priority.

Blockchain Proposal. The blockchain proposal forms the core

component of the framework and consists of:
Data collection. A variety of tools are used throughout the software
development lifecycle, such as Rational DOORS for requirements
management, and Git as a version control system. These tools
generate artifacts that are defined in the traceability information
model. Artifacts generated from these disparate sources can be
captured automatically by means of data ingestion tools/plugins [22]
and are parsed prior to being recorded on the blockchain.
Additionally, stakeholders create trace links manually and invoke the
respective smart contract to register these links on the distributed
ledger.
Storage layer and smart contracts. Smart contracts are created to
enable the following functions: register artifacts, e.g., requirements
(id, type, name, description, priority, parent_id), register trace links
(source_artifact_id, destination_artifact_id, trace_type), validate trace
links quality and reward trace links creators, accordingly. On
platforms such as Ethereum, the storage costs gas and can lead to
network synchronization issues and the high consumption of disk
space on the nodes [26]. To resolve storage limitations, the
framework allows to store artifacts’ contents off-chain in immutable
storage, such as IPFS (InterPlanetary File System). Moreover, the
quality of trace links is validated by approvers or verifiers whose
selection depends on voting policies. The approvers provide their
consent or rejection which is logged as a vote on the distributed
ledger. The smart contract calculates cumulative votes and accepts or
rejects trace links based on the vote score. It is noteworthy that the
assessment of traceability links quality is challenging because it
requires manual checking [6]. Finally, the incentive policies are
encoded in the smart contract that distributes digitized tokens to
stakeholders who create quality trace links.
Query layer. This layer facilitates comprehension from traceability
information stored on the blockchain. Traceability-related queries
must be constructed from primitive and composite links [17].
Primitive links are links between adjacent artifacts types defined in
the traceability information model. These queries comprise simple
forms of traces, for instance, return the list of requirements satisfied
by source code or using filters to include only artifacts with a specific
attribute value. Composite trace links are more complicated to
implement as they take place between non-adjacent artifacts, for
instance return requirements that trace to source code which failed
its test case [17].
Presentation layer. This layer is responsible for the visualization of
traceability-related information. Traceability visualization enhances
stakeholders’ ability to comprehend relationships between artifacts.
Previous literature reports on difficulties in uncovering insights from
traceability information due to the fact that trace links are
represented through lists or mega tables [6, 27]. Other approaches
use two-dimensional graphical formats such as hierarchical leaf node
 and tree view. These representations fail to explore relations
between different artifacts in an interactive manner which aids in
comprehending the overall system [28]. Our framework suggests
hierarchical and interactive visualization of trace links to enhance
traceability comprehension.

Implementation. In this phase, the blockchain proposal is developed

and implemented. The development of the blockchain proposal
requires close cooperation between blockchain developers and
requirements traceability experts or professionals with skills in both
blockchain and requirements traceability. The need for new
professional roles has been also observed in the broader field of
blockchain-oriented software engineering by Porru et al. [29].
Furthermore, the best fitting blockchain platform should be selected by
mapping the requirements of the desired system and blockchain
features. As the number of blockchain platforms is growing rapidly, the
selection of the appropriate platform becomes challenging. To guide the
selection process, we refer to previous literature that provides a
grounded blockchain platform selection process [30]. The main items
to consider comprise network acessibility, smart contract support, and
whether tokens are required or not [30]. For instance, open-source
software with diverse contributors might require public accessibility
whereas the development of complex and large-scale software among a
set of known distributed teams or organizations might require
restricted accessibility. Finally, disruptive technologies such as
blockchain are adopted once organizational resistance is overcome
which in turn can be achieved if the organization perceives the value of
such a system [31]. Therefore, it is important to communicate the value
of implementing blockchain for requirements traceability in a
transparent and clear manner to all the participants involved in the
software development lifecycle.

Assessment. In this phase, the contributions of the blockchain

proposal to the software development lifecycle are assessed. The
proposed framework provides an incentive mechanism to create
quality trace links, which motivates stakeholders to participate in
traceability creation and maintenance. Furthermore, the framework
enables a holistic and trustworthy view of artifacts and trace links and
presents them in a hierarchical and graphical way which encourages
the use of traceability to support SDLC activities. In turn, the increased
use of traceability improves the performance of practitioners in solving
SDLC tasks, for instance maintenance tasks. The performance can be
measured as the combination of the time to solve the task and
correctness of the solution [3]. Finally, the increased quality and
completeness of traceability has a positive impact on software quality
which can be measured in terms of defect rate [32]. A reduced defect
rate implies less need for software maintenance and consequently cost
savings that can be quantified [32]. It is worthy to note that the
components of the proposed framework are designed to be extensible
and should be tailored to organizational requirements. For instance,
organizations developing safety-critical systems may use smart
contracts to automatically validate compliance to regulations or
standards that impose traceability requirements, e.g., ISO 26262 and
ASPICE in the automotive domain [6].

4 Conclusion
In this paper, we propose a novel blockchain-enabled framework for
requirements traceability. This framework uses blockchain as the
backbone of the software development lifecycle, to enable an auditable
trail of artifacts and trace links created by multiple distributed
stakeholders. Due to its inherent properties, blockchain ensures
visibility regarding what/how/when trace links were created and who
created them. Additionally, the framework can be used to query and
represent traceability-related information to enhance the
understanding of the overall system.
Blockchain, as any other technology, does not fit all the use cases in
requirements traceability however this ongoing study is exploring a
way of investing, using and taking the best from blockchain. Although
there is large setup and storage overhead when implementing
blockchain for software engineering [33], blockchain can ensure
visibility, transparency, traceability and trustworthiness of artifacts and
trace links. The framework comprises customizable incentive and
voting policies to ensure the trustworthiness of trace links and presents
them in an interactive manner to enhance comprehension. These
components can potentially encourage the use of traceability to
support SDLC activities, and in turn improve the performance of
practitioners in solving SDLC tasks and enhance software quality.
However, it could also be interesting to improve the proposed
framework by incorporating gamification elements in order to enhance
the motivation and engagement of practitioners in traceability tasks.
Despite the aforementioned potential benefits, the framework also
has limitations that are mainly related to the manual work involved in
the creation of smart contracts and in the validation of quality trace
links. Another open issue to be addressed is how to resolve conflicts
that may occur when different participants claim to have created the
same trace links. Furthermore, it is noteworthy that the
implementation of blockchain technology for requirements traceability
may be challenging due to the limited research efforts in this
dimension, the nascent stage of blockchain development and open
technical challenges. These limitations have also been identified when
implementing blockchain in conventional domains such as supply chain
[34]. Although the proposed framework aims to be easy to used, it
requires software practitioners to have knowledge of both fields:
blockchain technologies and requirements traceability. Further
research efforts devoted to the development of prototypes and proofs-
of-concept in this area may encourage software development
organizations to implement blockchain for requirements traceability.
Therefore, the blockchain-enabled framework proposed in this study
will be validated by means of blockchain and requirements traceability
experts. Then, a blockchain-enabled requirements traceability
prototype will be developed and use cases will be performed to test the
concept. In so doing, some questions arise: What will be the main
benefits of an organization to implement your framework? How easy is
the framework for use? What type of knowledge that engineering needs
to be able to use the framework? In a common project how should use
your framework?

References
1. Gotel, O.C.Z., Finkelstein, C.W.: An analysis of the requirements traceability
problem. In: Proceedings of IEEE International Conference on Requirements
Engineering, pp. 94–101 (1994)
2.
Gotel, O., Cleland-Huang, J., Hayes, J.H., et al.: The quest for ubiquity: a roadmap
for software and systems traceability research. In: 2012 20th IEEE International
Requirements Engineering Conference (RE), pp. 71–80 (2012)
3.
Mäder, P., Egyed, A.: Do developers benefit from requirements traceability when
evolving and maintaining a software system? Empir. Softw. Eng. 20(2), 413–441
(2014). https://​doi.​org/​10.​1007/​s10664-014-9314-z
4.
Murugappan, S., Prabha, D.: Requirement traceability for software development
lifecycle. Int. J. Sci. Eng. Res. 8, 1–11 (2017)
5.
Elamin, R., Osman, R.: Implementing traceability repositories as graph databases
for software quality improvement. In: 2018 IEEE International Conference on
Software Quality, Reliability and Security (QRS), pp. 269–276 (2018)
6.
Maro, S., Steghö fer, J.-P., Staron, M.: Software traceability in the automotive
domain: challenges and solutions. J. Syst. Softw. 141, 85–110 (2018). https://​doi.​
org/​10.​1016/​j .​j ss.​2018.​03.​060
7.
Wohlrab, R., Knauss, E., Steghö fer, J.-P., Maro, S., Anjorin, A., Pelliccione, P.:
Collaborative traceability management: a multiple case study from the
perspectives of organization, process, and culture. Requir. Eng. 25(1), 21–45
(2018). https://​doi.​org/​10.​1007/​s00766-018-0306-1
8.
Yau, S.S., Patel, J.S.: Application of blockchain for trusted coordination in
collaborative software development. In: 2020 IEEE 44th Annual Computers,
Software, and Applications Conference (COMPSAC), pp. 1036–1040 (2020)
9.
Rempel, P., Mäder, P., Kuschke, T., Philippow, I.: Requirements traceability across
organizational boundaries - a survey and taxonomy. In: Doerr, J., Opdahl, A.L.
(eds.) REFSQ 2013. LNCS, vol. 7830, pp. 125–140. Springer, Heidelberg (2013).
https://​doi.​org/​10.​1007/​978-3-642-37422-7_​10
10.
Tschorsch, F., Scheuermann, B.: Bitcoin and beyond: a technical survey on
decentralized digital currencies. IEEE Commun. Surv. Tutor. 18, 2084–2123
(2016)
11.
Agbo, C.C., Mahmoud, Q.H., Eklund, J.M.: Blockchain technology in healthcare: a
systematic review. Healthcare 7, 56 (2019). https://​doi.​org/​10.​3390/​
healthcare702005​6
12.
Marchesi, L., Marchesi, M., Destefanis, G., et al.: Design patterns for gas
optimization in ethereum. In: 2020 IEEE International Workshop on Blockchain
Oriented Software Engineering (IWBOSE), pp. 9–15 (2020)
13.
Vacca, A., Di Sorbo, A., Visaggio, C.A., Canfora, G.: A systematic literature review of
blockchain and smart contract development: techniques, tools, and open
challenges. J. Syst. Softw. 174, 110891 (2021). https://​doi.​org/​10.​1016/​j .​j ss.​2020.​
110891
14.
Pinna, A., Ibba, S., Baralla, G., et al.: A massive analysis of ethereum smart
contracts empirical study and code metrics. IEEE Access 7, 78194–78213
(2019). https://​doi.​org/​10.​1109/​ACCESS.​2019.​2921936
15.
Bartoletti, M., Pompianu, L.: An empirical analysis of smart contracts: platforms,
applications, and design patterns. In: Brenner, M., et al. (eds.) FC 2017. LNCS, vol.
10323, pp. 494–509. Springer, Cham (2017). https://​doi.​org/​10.​1007/​978-3-319-
70278-0_​31
16.
Mader, P., Gotel, O., Philippow, I.: Getting back to basics: promoting the use of a
traceability information model in practice. In: 2009 ICSE Workshop on
Traceability in Emerging Forms of Software Engineering, pp. 21–25 (2009)
17.
Cleland-Huang, J., Hayes, J.H., Domel, J.M.: Model-based traceability. In: 2009 ICSE
Workshop on Traceability in Emerging Forms of Software Engineering, pp. 6–10
(2009)
18.
Marchesi, M.: Why blockchain is important for software developers, and why
software engineering is important for blockchain software (Keynote). In: 2018
International Workshop on Blockchain Oriented Software Engineering
(IWBOSE), p. 1 (2018)
19.
Colomo-Palacios, R.: Cross fertilization in software engineering. In: Yilmaz, M.,
Niemann, J., Clarke, P., Messnarz, R. (eds.) EuroSPI 2020. CCIS, vol. 1251, pp. 3–13.
Springer, Cham (2020). https://​doi.​org/​10.​1007/​978-3-030-56441-4_​1
20.
Demi, S., Colomo-Palacios, R., Sánchez-Gordó n, M.: Software engineering
applications enabled by blockchain technology: a systematic mapping study.
Appl. Sci. 11, 2960 (2021). https://​doi.​org/​10.​3390/​app11072960
21.
Yilmaz, M., Tasel, S., Tuzun, E., Gulec, U., O’Connor, R.V., Clarke, P.M.: Applying
blockchain to improve the integrity of the software development process. In:
Walker, A., O’Connor, R.V., Messnarz, R. (eds.) EuroSPI 2019. CCIS, vol. 1060, pp.
260–271. Springer, Cham (2019). https://​doi.​org/​10.​1007/​978-3-030-28005-5_​20
22.
Bose, R.P.J.C., Phokela, K.K., Kaulgud, V., Podder, S.: BLINKER: a blockchain-
enabled framework for software provenance. In: 2019 26th Asia-Pacific Software
Engineering Conference (APSEC), pp. 1–8 (2019)
23.
Singi, K., Kaulgud, V., Chandra Bose, R.P.J., et al.: Are software engineers
incentivized enough? An outcome based incentive framework using tokens. In:
2020 IEEE International Workshop on Blockchain Oriented Software
Engineering (IWBOSE), pp. 37–47 (2020)
24.
Cleland-Huang, J., Berenbach, B., Clark, S., et al.: Best practices for automated
traceability. Computer 40, 27–35 (2007). https://​doi.​org/​10.​1109/​MC.​2007.​195
25.
Gotel, O., Cleland-Huang, J., Hayes, J.H., et al.: Traceability fundamentals. In:
Cleland-Huang, J., Gotel, O., Zisman, A. (eds.) Software and Systems Traceability,
pp. 3–22. Springer, London (2012). https://​doi.​org/​10.​1007/​978-1-4471-2239-5_​
1
26.
Singi, K., Kaulgud, V., Bose, R.P.J.C., Podder, S.: CAG: compliance adherence and
governance in software delivery using blockchain. In: 2019 IEEE/ACM 2nd
International Workshop on Emerging Trends in Software Engineering for
Blockchain (WETSEB), pp. 32–39 (2019)
27.
Mäder, P., Jones, P.L., Zhang, Y., Cleland-Huang, J.: Strategic traceability for safety-
critical projects. IEEE Softw. 30, 58–66 (2013). https://​doi.​org/​10.​1109/​MS.​
2013.​60
28.
Aung, T.W.W., Huo, H., Sui, Y.: Interactive traceability links visualization using
hierarchical trace map. In: 2019 IEEE International Conference on Software
Maintenance and Evolution (ICSME), pp. 367–369 (2019)
29.
Porru, S., Pinna, A., Marchesi, M., Tonelli, R.: Blockchain-oriented software
engineering: challenges and new directions. In: 2017 IEEE/ACM 39th
International Conference on Software Engineering Companion (ICSE-C), pp. 169–
171 (2017)
30.
Farshidi, S., Jansen, S., Españ a, S., Verkleij, J.: Decision support for blockchain
platform selection: three industry case studies. IEEE Trans. Eng. Manag. 67,
1109–1128 (2020)
31.
Beck, R., Mü ller-Bloch, C.: Blockchain as radical innovation: a framework for
engaging with distributed ledgers as incumbent organization. In: Proceedings of
the 50th Hawaii International Conference on System Sciences (2017)
32.
Rempel, P., Mäder, P.: Preventing defects: the impact of requirements traceability
completeness on software quality. IEEE Trans. Softw. Eng. 43, 777–797 (2016)
33.
Yau, S.S., Patel, J.S.: A blockchain-based testing approach for collaborative
software development. In: 2020 IEEE International Conference on Blockchain
(Blockchain), pp. 98–105 (2020)
34.
Chang, S.E., Chen, Y.: When blockchain meets supply chain: a systematic literature
review on current development and potential applications. IEEE Access 8,
62478–62494 (2020). https://​doi.​org/​10.​1109/​ACCESS.​2020.​2983601
© Springer Nature Switzerland AG 2021
M. Yilmaz et al. (eds.), Systems, Software and Services Process Improvement,
Communications in Computer and Information Science 1442
https://doi.org/10.1007/978-3-030-85521-5_2

To Work from Home (WFH) or Not to

Work from Home? Lessons Learned by
Software Engineers During the COVID-
19 Pandemic
Aifric Nolan1 , Rachel White1 , Mahjabeen Soomro1 ,
Boluwatife Comfort Dopamu1 , Murat Yilmaz2, 4 , David Solan3 and
Paul Clarke1, 2
(1) School of Computing, Dublin City University, Dublin, Ireland
(2) Lero, the Science Foundation Ireland Research Centre for Software,
Limerick, Ireland
(3) FINEOS Corporation, Dublin, Ireland
(4) Department of Computer Engineering, Faculty of Engineering, Gazi
University, Ankara, Turkey

Aifric Nolan
Email: aifric.nolan65@mail.dcu.ie

Rachel White
Email: rachel.white7@mail.dcu.ie

Mahjabeen Soomro
Email: mahjabeen.soomro2@mail.dcu.ie

Boluwatife Comfort Dopamu

Email: boluwatife.dopamu2@mail.dcu.ie
Another random document with
no related content on Scribd:
*** END OF THE PROJECT GUTENBERG EBOOK BOOK OF
DETECTIVE STORIES ***

Updated editions will replace the previous one—the old editions

will be renamed.

Creating the works from print editions not protected by U.S.

copyright law means that no one owns a United States copyright
in these works, so the Foundation (and you!) can copy and
distribute it in the United States without permission and without
paying copyright royalties. Special rules, set forth in the General
Terms of Use part of this license, apply to copying and
distributing Project Gutenberg™ electronic works to protect the
PROJECT GUTENBERG™ concept and trademark. Project
Gutenberg is a registered trademark, and may not be used if
you charge for an eBook, except by following the terms of the
trademark license, including paying royalties for use of the
Project Gutenberg trademark. If you do not charge anything for
copies of this eBook, complying with the trademark license is
very easy. You may use this eBook for nearly any purpose such
as creation of derivative works, reports, performances and
research. Project Gutenberg eBooks may be modified and
printed and given away—you may do practically ANYTHING in
the United States with eBooks not protected by U.S. copyright
law. Redistribution is subject to the trademark license, especially
commercial redistribution.

START: FULL LICENSE

THE FULL PROJECT GUTENBERG LICENSE
 PLEASE READ THIS BEFORE YOU DISTRIBUTE OR USE THIS WORK

To protect the Project Gutenberg™ mission of promoting the

free distribution of electronic works, by using or distributing this
work (or any other work associated in any way with the phrase
“Project Gutenberg”), you agree to comply with all the terms of
the Full Project Gutenberg™ License available with this file or
online at www.gutenberg.org/license.

Section 1. General Terms of Use and

Redistributing Project Gutenberg™
electronic works
1.A. By reading or using any part of this Project Gutenberg™
electronic work, you indicate that you have read, understand,
agree to and accept all the terms of this license and intellectual
property (trademark/copyright) agreement. If you do not agree to
abide by all the terms of this agreement, you must cease using
and return or destroy all copies of Project Gutenberg™
electronic works in your possession. If you paid a fee for
obtaining a copy of or access to a Project Gutenberg™
electronic work and you do not agree to be bound by the terms
of this agreement, you may obtain a refund from the person or
entity to whom you paid the fee as set forth in paragraph 1.E.8.

1.B. “Project Gutenberg” is a registered trademark. It may only

be used on or associated in any way with an electronic work by
people who agree to be bound by the terms of this agreement.
There are a few things that you can do with most Project
Gutenberg™ electronic works even without complying with the
full terms of this agreement. See paragraph 1.C below. There
are a lot of things you can do with Project Gutenberg™
electronic works if you follow the terms of this agreement and
help preserve free future access to Project Gutenberg™
electronic works. See paragraph 1.E below.
1.C. The Project Gutenberg Literary Archive Foundation (“the
Foundation” or PGLAF), owns a compilation copyright in the
collection of Project Gutenberg™ electronic works. Nearly all the
individual works in the collection are in the public domain in the
United States. If an individual work is unprotected by copyright
law in the United States and you are located in the United
States, we do not claim a right to prevent you from copying,
distributing, performing, displaying or creating derivative works
based on the work as long as all references to Project
Gutenberg are removed. Of course, we hope that you will
support the Project Gutenberg™ mission of promoting free
access to electronic works by freely sharing Project
Gutenberg™ works in compliance with the terms of this
agreement for keeping the Project Gutenberg™ name
associated with the work. You can easily comply with the terms
of this agreement by keeping this work in the same format with
its attached full Project Gutenberg™ License when you share it
without charge with others.

1.D. The copyright laws of the place where you are located also
govern what you can do with this work. Copyright laws in most
countries are in a constant state of change. If you are outside
the United States, check the laws of your country in addition to
the terms of this agreement before downloading, copying,
displaying, performing, distributing or creating derivative works
based on this work or any other Project Gutenberg™ work. The
Foundation makes no representations concerning the copyright
status of any work in any country other than the United States.

1.E. Unless you have removed all references to Project

Gutenberg:

1.E.1. The following sentence, with active links to, or other

immediate access to, the full Project Gutenberg™ License must
appear prominently whenever any copy of a Project
Gutenberg™ work (any work on which the phrase “Project
Gutenberg” appears, or with which the phrase “Project
Gutenberg” is associated) is accessed, displayed, performed,
viewed, copied or distributed:

This eBook is for the use of anyone anywhere in the United

States and most other parts of the world at no cost and with
almost no restrictions whatsoever. You may copy it, give it
away or re-use it under the terms of the Project Gutenberg
License included with this eBook or online at
www.gutenberg.org. If you are not located in the United
States, you will have to check the laws of the country where
you are located before using this eBook.

1.E.2. If an individual Project Gutenberg™ electronic work is

derived from texts not protected by U.S. copyright law (does not
contain a notice indicating that it is posted with permission of the
copyright holder), the work can be copied and distributed to
anyone in the United States without paying any fees or charges.
If you are redistributing or providing access to a work with the
phrase “Project Gutenberg” associated with or appearing on the
work, you must comply either with the requirements of
paragraphs 1.E.1 through 1.E.7 or obtain permission for the use
of the work and the Project Gutenberg™ trademark as set forth
in paragraphs 1.E.8 or 1.E.9.

1.E.3. If an individual Project Gutenberg™ electronic work is

posted with the permission of the copyright holder, your use and
distribution must comply with both paragraphs 1.E.1 through
1.E.7 and any additional terms imposed by the copyright holder.
Additional terms will be linked to the Project Gutenberg™
License for all works posted with the permission of the copyright
holder found at the beginning of this work.

1.E.4. Do not unlink or detach or remove the full Project

Gutenberg™ License terms from this work, or any files
containing a part of this work or any other work associated with
Project Gutenberg™.
 1.E.5. Do not copy, display, perform, distribute or redistribute
this electronic work, or any part of this electronic work, without
prominently displaying the sentence set forth in paragraph 1.E.1
with active links or immediate access to the full terms of the
Project Gutenberg™ License.

1.E.6. You may convert to and distribute this work in any binary,
compressed, marked up, nonproprietary or proprietary form,
including any word processing or hypertext form. However, if
you provide access to or distribute copies of a Project
Gutenberg™ work in a format other than “Plain Vanilla ASCII” or
other format used in the official version posted on the official
Project Gutenberg™ website (www.gutenberg.org), you must, at
no additional cost, fee or expense to the user, provide a copy, a
means of exporting a copy, or a means of obtaining a copy upon
request, of the work in its original “Plain Vanilla ASCII” or other
form. Any alternate format must include the full Project
Gutenberg™ License as specified in paragraph 1.E.1.

1.E.7. Do not charge a fee for access to, viewing, displaying,

performing, copying or distributing any Project Gutenberg™
works unless you comply with paragraph 1.E.8 or 1.E.9.

1.E.8. You may charge a reasonable fee for copies of or

providing access to or distributing Project Gutenberg™
electronic works provided that:

• You pay a royalty fee of 20% of the gross profits you derive from
the use of Project Gutenberg™ works calculated using the
method you already use to calculate your applicable taxes. The
fee is owed to the owner of the Project Gutenberg™ trademark,
but he has agreed to donate royalties under this paragraph to
the Project Gutenberg Literary Archive Foundation. Royalty
payments must be paid within 60 days following each date on
which you prepare (or are legally required to prepare) your
periodic tax returns. Royalty payments should be clearly marked
as such and sent to the Project Gutenberg Literary Archive
Foundation at the address specified in Section 4, “Information
 about donations to the Project Gutenberg Literary Archive
Foundation.”

• You provide a full refund of any money paid by a user who

notifies you in writing (or by e-mail) within 30 days of receipt that
s/he does not agree to the terms of the full Project Gutenberg™
License. You must require such a user to return or destroy all
copies of the works possessed in a physical medium and
discontinue all use of and all access to other copies of Project
Gutenberg™ works.

• You provide, in accordance with paragraph 1.F.3, a full refund of

any money paid for a work or a replacement copy, if a defect in
the electronic work is discovered and reported to you within 90
days of receipt of the work.

• You comply with all other terms of this agreement for free
distribution of Project Gutenberg™ works.

1.E.9. If you wish to charge a fee or distribute a Project

Gutenberg™ electronic work or group of works on different
terms than are set forth in this agreement, you must obtain
permission in writing from the Project Gutenberg Literary
Archive Foundation, the manager of the Project Gutenberg™
trademark. Contact the Foundation as set forth in Section 3
below.

1.F.

1.F.1. Project Gutenberg volunteers and employees expend

considerable effort to identify, do copyright research on,
transcribe and proofread works not protected by U.S. copyright
law in creating the Project Gutenberg™ collection. Despite
these efforts, Project Gutenberg™ electronic works, and the
medium on which they may be stored, may contain “Defects,”
such as, but not limited to, incomplete, inaccurate or corrupt
data, transcription errors, a copyright or other intellectual
property infringement, a defective or damaged disk or other
medium, a computer virus, or computer codes that damage or
cannot be read by your equipment.

1.F.2. LIMITED WARRANTY, DISCLAIMER OF DAMAGES -

Except for the “Right of Replacement or Refund” described in
paragraph 1.F.3, the Project Gutenberg Literary Archive
Foundation, the owner of the Project Gutenberg™ trademark,
and any other party distributing a Project Gutenberg™ electronic
work under this agreement, disclaim all liability to you for
damages, costs and expenses, including legal fees. YOU
AGREE THAT YOU HAVE NO REMEDIES FOR NEGLIGENCE,
STRICT LIABILITY, BREACH OF WARRANTY OR BREACH
OF CONTRACT EXCEPT THOSE PROVIDED IN PARAGRAPH
1.F.3. YOU AGREE THAT THE FOUNDATION, THE
TRADEMARK OWNER, AND ANY DISTRIBUTOR UNDER
THIS AGREEMENT WILL NOT BE LIABLE TO YOU FOR
ACTUAL, DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE
OR INCIDENTAL DAMAGES EVEN IF YOU GIVE NOTICE OF
THE POSSIBILITY OF SUCH DAMAGE.

1.F.3. LIMITED RIGHT OF REPLACEMENT OR REFUND - If

you discover a defect in this electronic work within 90 days of
receiving it, you can receive a refund of the money (if any) you
paid for it by sending a written explanation to the person you
received the work from. If you received the work on a physical
medium, you must return the medium with your written
explanation. The person or entity that provided you with the
defective work may elect to provide a replacement copy in lieu
of a refund. If you received the work electronically, the person or
entity providing it to you may choose to give you a second
opportunity to receive the work electronically in lieu of a refund.
If the second copy is also defective, you may demand a refund
in writing without further opportunities to fix the problem.

1.F.4. Except for the limited right of replacement or refund set

forth in paragraph 1.F.3, this work is provided to you ‘AS-IS’,
WITH NO OTHER WARRANTIES OF ANY KIND, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR
ANY PURPOSE.

1.F.5. Some states do not allow disclaimers of certain implied

warranties or the exclusion or limitation of certain types of
damages. If any disclaimer or limitation set forth in this
agreement violates the law of the state applicable to this
agreement, the agreement shall be interpreted to make the
maximum disclaimer or limitation permitted by the applicable
state law. The invalidity or unenforceability of any provision of
this agreement shall not void the remaining provisions.

1.F.6. INDEMNITY - You agree to indemnify and hold the

Foundation, the trademark owner, any agent or employee of the
Foundation, anyone providing copies of Project Gutenberg™
electronic works in accordance with this agreement, and any
volunteers associated with the production, promotion and
distribution of Project Gutenberg™ electronic works, harmless
from all liability, costs and expenses, including legal fees, that
arise directly or indirectly from any of the following which you do
or cause to occur: (a) distribution of this or any Project
Gutenberg™ work, (b) alteration, modification, or additions or
deletions to any Project Gutenberg™ work, and (c) any Defect
you cause.

Section 2. Information about the Mission of

Project Gutenberg™
Project Gutenberg™ is synonymous with the free distribution of
electronic works in formats readable by the widest variety of
computers including obsolete, old, middle-aged and new
computers. It exists because of the efforts of hundreds of
volunteers and donations from people in all walks of life.

Volunteers and financial support to provide volunteers with the

assistance they need are critical to reaching Project
Gutenberg™’s goals and ensuring that the Project Gutenberg™
collection will remain freely available for generations to come. In
2001, the Project Gutenberg Literary Archive Foundation was
created to provide a secure and permanent future for Project
Gutenberg™ and future generations. To learn more about the
Project Gutenberg Literary Archive Foundation and how your
efforts and donations can help, see Sections 3 and 4 and the
Foundation information page at www.gutenberg.org.

Section 3. Information about the Project

Gutenberg Literary Archive Foundation
The Project Gutenberg Literary Archive Foundation is a non-
profit 501(c)(3) educational corporation organized under the
laws of the state of Mississippi and granted tax exempt status by
the Internal Revenue Service. The Foundation’s EIN or federal
tax identification number is 64-6221541. Contributions to the
Project Gutenberg Literary Archive Foundation are tax
deductible to the full extent permitted by U.S. federal laws and
your state’s laws.

The Foundation’s business office is located at 809 North 1500

West, Salt Lake City, UT 84116, (801) 596-1887. Email contact
links and up to date contact information can be found at the
Foundation’s website and official page at
www.gutenberg.org/contact

Section 4. Information about Donations to

the Project Gutenberg Literary Archive
Foundation
Project Gutenberg™ depends upon and cannot survive without
widespread public support and donations to carry out its mission
of increasing the number of public domain and licensed works
that can be freely distributed in machine-readable form
accessible by the widest array of equipment including outdated
equipment. Many small donations ($1 to $5,000) are particularly
important to maintaining tax exempt status with the IRS.

The Foundation is committed to complying with the laws

regulating charities and charitable donations in all 50 states of
the United States. Compliance requirements are not uniform
and it takes a considerable effort, much paperwork and many
fees to meet and keep up with these requirements. We do not
solicit donations in locations where we have not received written
confirmation of compliance. To SEND DONATIONS or
determine the status of compliance for any particular state visit
www.gutenberg.org/donate.

While we cannot and do not solicit contributions from states

where we have not met the solicitation requirements, we know
of no prohibition against accepting unsolicited donations from
donors in such states who approach us with offers to donate.

International donations are gratefully accepted, but we cannot

make any statements concerning tax treatment of donations
received from outside the United States. U.S. laws alone swamp
our small staff.

Please check the Project Gutenberg web pages for current

donation methods and addresses. Donations are accepted in a
number of other ways including checks, online payments and
credit card donations. To donate, please visit:
www.gutenberg.org/donate.

Section 5. General Information About Project

Gutenberg™ electronic works
Professor Michael S. Hart was the originator of the Project
Gutenberg™ concept of a library of electronic works that could
be freely shared with anyone. For forty years, he produced and
distributed Project Gutenberg™ eBooks with only a loose
network of volunteer support.

Project Gutenberg™ eBooks are often created from several

printed editions, all of which are confirmed as not protected by
copyright in the U.S. unless a copyright notice is included. Thus,
we do not necessarily keep eBooks in compliance with any
particular paper edition.

Most people start at our website which has the main PG search
facility: www.gutenberg.org.

This website includes information about Project Gutenberg™,

including how to make donations to the Project Gutenberg
Literary Archive Foundation, how to help produce our new
eBooks, and how to subscribe to our email newsletter to hear
about new eBooks.