-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathANNEX IV IT Principles.html
1275 lines (1244 loc) · 65.2 KB
/
ANNEX IV IT Principles.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head>
<meta charset="utf-8">
<meta name="generator" content="quarto-1.5.56">
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes">
<meta name="author" content="European Environment Agency (EEA)">
<meta name="dcterms.date" content="2024-11-08">
<meta name="keywords" content="Copernicus Land Monitoring Service, CLMS IT Architecture, European Environment Agency, IT Principles and Guidelines, IT Ecosystem, IT Security, EUPL Licensing, Reproducibility, Reusability, Transparency, Scalability, Maintainability, Resilient IT Solutions, Modular IT Architecture, Continuous Integration">
<title>Copernicus Land Monitoring Service IT Architecture Principles and Implementation Guidelines</title>
<style>
code{white-space: pre-wrap;}
span.smallcaps{font-variant: small-caps;}
div.columns{display: flex; gap: min(4vw, 1.5em);}
div.column{flex: auto; overflow-x: auto;}
div.hanging-indent{margin-left: 1.5em; text-indent: -1.5em;}
ul.task-list{list-style: none;}
ul.task-list li input[type="checkbox"] {
width: 0.8em;
margin: 0 0.8em 0.2em -1em; /* quarto-specific, see https://github.com/quarto-dev/quarto-cli/issues/4556 */
vertical-align: middle;
}
</style>
<script src="ANNEX IV IT Principles_files/libs/clipboard/clipboard.min.js"></script>
<script src="ANNEX IV IT Principles_files/libs/quarto-html/quarto.js"></script>
<script src="ANNEX IV IT Principles_files/libs/quarto-html/popper.min.js"></script>
<script src="ANNEX IV IT Principles_files/libs/quarto-html/tippy.umd.min.js"></script>
<script src="ANNEX IV IT Principles_files/libs/quarto-html/anchor.min.js"></script>
<link href="ANNEX IV IT Principles_files/libs/quarto-html/tippy.css" rel="stylesheet">
<link href="ANNEX IV IT Principles_files/libs/quarto-html/quarto-syntax-highlighting.css" rel="stylesheet" id="quarto-text-highlighting-styles">
<script src="ANNEX IV IT Principles_files/libs/bootstrap/bootstrap.min.js"></script>
<link href="ANNEX IV IT Principles_files/libs/bootstrap/bootstrap-icons.css" rel="stylesheet">
<link href="ANNEX IV IT Principles_files/libs/bootstrap/bootstrap.min.css" rel="stylesheet" id="quarto-bootstrap" data-mode="light">
</head>
<body>
<div id="quarto-content" class="page-columns page-rows-contents page-layout-article">
<div id="quarto-margin-sidebar" class="sidebar margin-sidebar">
<nav id="TOC" role="doc-toc" class="toc-active">
<h2 id="toc-title">Index</h2>
<ul>
<li><a href="#preface" id="toc-preface" class="nav-link active" data-scroll-target="#preface"><span class="header-section-number">1</span> Preface</a></li>
<li><a href="#introduction" id="toc-introduction" class="nav-link" data-scroll-target="#introduction"><span class="header-section-number">2</span> Introduction</a></li>
<li><a href="#scope-and-key-terms" id="toc-scope-and-key-terms" class="nav-link" data-scroll-target="#scope-and-key-terms"><span class="header-section-number">3</span> Scope and key terms</a></li>
<li><a href="#principles" id="toc-principles" class="nav-link" data-scroll-target="#principles"><span class="header-section-number">4</span> Principles</a>
<ul class="collapse">
<li><a href="#reproducibility" id="toc-reproducibility" class="nav-link" data-scroll-target="#reproducibility"><span class="header-section-number">4.1</span> Reproducibility</a></li>
<li><a href="#reusability" id="toc-reusability" class="nav-link" data-scroll-target="#reusability"><span class="header-section-number">4.2</span> Reusability</a></li>
<li><a href="#transparency" id="toc-transparency" class="nav-link" data-scroll-target="#transparency"><span class="header-section-number">4.3</span> Transparency</a></li>
<li><a href="#scalability" id="toc-scalability" class="nav-link" data-scroll-target="#scalability"><span class="header-section-number">4.4</span> Scalability</a></li>
<li><a href="#maintainability" id="toc-maintainability" class="nav-link" data-scroll-target="#maintainability"><span class="header-section-number">4.5</span> Maintainability</a></li>
<li><a href="#it-security" id="toc-it-security" class="nav-link" data-scroll-target="#it-security"><span class="header-section-number">4.6</span> IT security</a></li>
<li><a href="#resilience" id="toc-resilience" class="nav-link" data-scroll-target="#resilience"><span class="header-section-number">4.7</span> Resilience</a></li>
</ul></li>
</ul>
<div class="quarto-alternate-formats"><h2>Other Formats</h2><ul><li><a href="ANNEX IV IT Principles.docx"><i class="bi bi-file-word"></i>MS Word</a></li><li><a href="ANNEX-IV-IT-Principles.pdf"><i class="bi bi-file-pdf"></i>PDF</a></li></ul></div></nav>
</div>
<main class="content" id="quarto-document-content">
<header id="title-block-header" class="quarto-title-block default">
<div class="quarto-title">
<h1 class="title"><p>Copernicus Land Monitoring Service IT Architecture Principles and Implementation Guidelines</p></h1>
<p class="subtitle lead">ANNEX IV</p>
</div>
<div class="quarto-title-meta">
<div>
<div class="quarto-title-meta-heading">Author</div>
<div class="quarto-title-meta-contents">
<p>European Environment Agency (EEA) </p>
</div>
</div>
<div>
<div class="quarto-title-meta-heading">Published</div>
<div class="quarto-title-meta-contents">
<p class="date">November 8, 2024</p>
</div>
</div>
</div>
<div>
<div class="keywords">
<div class="block-title">Keywords</div>
<p>Copernicus Land Monitoring Service, CLMS IT Architecture, European Environment Agency, IT Principles and Guidelines, IT Ecosystem, IT Security, EUPL Licensing, Reproducibility, Reusability, Transparency, Scalability, Maintainability, Resilient IT Solutions, Modular IT Architecture, Continuous Integration</p>
</div>
</div>
</header>
<section id="preface" class="level1" data-number="1">
<h1 data-number="1"><span class="header-section-number">1</span> Preface</h1>
<p>The EEA (European Environment Agency) CLMS IT architecture principles are indicative and must be evaluated in all IT deliverables.</p>
</section>
<section id="introduction" class="level1" data-number="2">
<h1 data-number="2"><span class="header-section-number">2</span> Introduction</h1>
<p>The IT architecture principles set the overall framework for the EEA CLMS IT landscape. The principles are designed to ensure a consistency in deliverables and at the same time support the CLMS program’s IT vision and -strategy. The principles are designed to ensure that IT solutions are coherent, can be further developed and operated efficiently, that they support business needs and security requirements, etc.</p>
<p>A uniform approach is required to ensure the coherency goal. The EEA CLMS programs IT applications may depend on and interact with each other. It is therefore important that IT solutions focus on connectivity and potential synergy effects to ensure continued coherence in the IT landscape.</p>
<p>Any application provided may be developed, operated, maintained, and further developed by a supplier different from the supplier who delivered the initial application. Therefore, efforts must always be made to be supplier independent. Other suppliers must be able to continue working from where the previous supplier left off.</p>
</section>
<section id="scope-and-key-terms" class="level1" data-number="3">
<h1 data-number="3"><span class="header-section-number">3</span> Scope and key terms</h1>
<p>The scope of the EEA CLMS IT architecture principles is IT solutions to be delivered to the CLMS. The solutions delivered will include functionalities required to support the program (for Example, maintain and operate CLC+ Core multi-use grid-based Land Cover/Land Use hybrid data repository). This includes also the dependencies of these IT solutions to other internal or external systems.</p>
<p>Definition of the key terms used within this document:</p>
<ul>
<li><p><strong>Application Programming Interface (API)</strong> - is a set of protocols, tools, and definitions that allow different software applications to communicate with each other. It defines the methods and data structures that developers can use to interact with a service or application, facilitating the exchange of data and functionality.</p></li>
<li><p><strong>Automation scripts</strong> – refers to sets of instructions, written in scripting languages designed to automate repetitive tasks and processes. These scripts streamline workflows, reduce the need for manual intervention and ensure consistency and efficiency in performing tasks.</p></li>
<li><p><strong>Client specific software/IT solution</strong> – is a custom-designed software/solution that is tailored to meet the unique needs, requirements, and preferences of a particular client or organization.</p></li>
<li><p><strong>Commercial software</strong> – software products that are developed, marketed, and sold for profit by software companies or developers. Commercial software is typically licensed to end-users, who must purchase it or pay a subscription fee.</p></li>
<li><p><strong>Continuous Integration and Continuous Deployment (CI/CD) –</strong> are closely related methodologies designed to streamline and automate software development. Together, they ensure that code changes are continuously tested, integrated, and deployed to production environments, enabling teams to deliver updates more rapidly, reliably, and with minimal manual intervention.</p></li>
<li><p><strong>Deliverables</strong> – specific outputs, products, or results provided as part of the contract or a contractual agreement.</p></li>
<li><p><strong>End of life (EOL)</strong> – refers to the date after which a product will no longer be sold or renewed (though still might receive some form of support, such as security patches).</p></li>
<li><p><strong>End of support (EOS)</strong> – refers to the date of complete cessation of all support services for the product, including new patches, updates or fixes.</p></li>
<li><p><strong>Infrastructure-as-a-code</strong> – is an IT practice that involves managing and provisioning computing infrastructure through machine-readable definition files, rather than physical hardware configuration or interactive configuration tools.</p></li>
<li><p><strong>IT ecosystem</strong> – is a network of interconnected technologies, software, hardware, and services that work together to support an organization’s digital operations. It includes applications, infrastructure, cloud services, and networks, all integrated to ensure seamless communication, scalability, security, and efficiency.</p></li>
<li><p><strong>IT solution continuity</strong> - involves a collection of strategies and plans focused on maintaining an organization’s essential operations during and after disruptions. The goal is to minimize downtime, limit financial losses, and safeguard the organization’s reputation when faced with interruptions.</p></li>
<li><p><strong>IT solutions</strong> – services, products and processes that use information technology to solve business problems, improve operational efficiency, and enhance overall performance. IT solutions are typically composed by various parts. For Example, the codebase, CI/CD routines, documentation etc.</p></li>
<li><p><strong>Open-ended</strong> – refers to components or features that are flexible, adaptable, and capable of evolving over time to meet a wide range of needs and requirements.</p></li>
<li><p><strong>Pre-processing</strong> - refers to the series of operations performed on raw data to prepare it for further analysis and processing.</p></li>
<li><p><strong>REST API service</strong> - is a type of web service that allows systems to communicate over HTTP by accessing and manipulating resources using standard methods such as GET, POST, PUT, and DELETE. RESTful APIs are stateless, meaning each request from a client to the server must contain all the necessary information, and they typically return data in formats like JSON or XML. This approach is widely used for building scalable, lightweight web services and enabling seamless integration between different systems.</p></li>
<li><p><strong>Software development tools</strong> – applications, frameworks, and utilities that software developers use to create, debug, maintain, or support software.</p></li>
<li><p><strong>Software product</strong> – a collection of computer programs, procedures, and documentation that performs a specific task or function or provides a comprehensive solution to a particular problem.</p></li>
<li><p><strong>Source code</strong> – a set of instructions and statements written by a programmer using human-readable programming language. It is the original code written and saved in files before being compiled or interpreted into executable programs. Source code serves as the blueprint for creating software applications.</p></li>
<li><p><strong>Workflow</strong> – systematic sequence of processes and activities.</p></li>
</ul>
</section>
<section id="principles" class="level1" data-number="4">
<h1 data-number="4"><span class="header-section-number">4</span> Principles</h1>
<p>The principles are grouped into 6 overarching IT architectural themes:</p>
<ol type="1">
<li><p><strong>Reproducibility</strong> - the overarching goal is to ensure that any deliverable in the form of an IT solution may be reproduced given sufficient time.</p></li>
<li><p><strong>Reusability</strong> - the services and products provided through the EEA CLMS are to be reused by the end users as the foundation of their further work.</p></li>
<li><p><strong>Transparency</strong> - the EEA CLMS program is funded by the EU and supports its community with data and products. These products are to be part of the foundation for further work in the field and hence transparency is key to ensuring that extended work can be carried out.</p></li>
<li><p><strong>Scalability</strong> - the delivered IT solutions must be scalable to ensure future enhancements can fulfil coming demands and requirements.</p></li>
<li><p><strong>Maintainability</strong> - the EEA aims in the CLMS program to be able to provide updated products when new data becomes available e.g. on yearly basis. To reduce the time to market the principle of maintainability is to be followed.</p></li>
<li><p><strong>IT security</strong> – IT solutions of the EEA CLMS are utilized by multiple stakeholders and thus IT security is paramount. This is especially critical for the open-ended aspects such as the use of APIs and outward facing web solutions.</p></li>
<li><p><strong>Resilience</strong> – IT solutions of the EEA CLMS are designed to withstand and recover from disruptions by remaining operational during unforeseen events.</p></li>
</ol>
<p>Together, these principles guide design, development, and evolution of the IT solutions in the EEA CLMS program. The principles should be periodically reviewed and updated to ensure alignment with the latest technological advancements and emerging best practices. This ongoing evaluation will help maintaining the relevance, effectiveness, and security of the IT solutions.</p>
<section id="reproducibility" class="level2" data-number="4.1">
<h2 data-number="4.1" class="anchored" data-anchor-id="reproducibility"><span class="header-section-number">4.1</span> Reproducibility</h2>
<p>The overarching principle of reproducibility is further unfolded below in the following sub-principles:</p>
<table class="caption-top table">
<colgroup>
<col style="width: 26%">
<col style="width: 73%">
</colgroup>
<thead>
<tr class="header">
<th style="text-align: right;"><strong>Reproducibility 1:</strong></th>
<th style="text-align: left;"><strong>Description of workflows must be provided</strong></th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td style="text-align: right;"><strong>What:</strong></td>
<td style="text-align: left;">Deliverables which are a result of pre-processing of data must be provided with a description of the workflow for the pre-processing</td>
</tr>
<tr class="even">
<td style="text-align: right;"><strong>Why:</strong></td>
<td style="text-align: left;">To ensure that the deliverable can be re-produced, details must be provided on how this can be achieved</td>
</tr>
<tr class="odd">
<td style="text-align: right;"><strong>Consequence:</strong></td>
<td style="text-align: left;">Descriptions of pre-processing workflow steps are to be provided with deliverables. Ideally the workflows delivered as scripts or similar. At a minimum documentation of how the workflows are to be set up is to be provided</td>
</tr>
<tr class="even">
<td style="text-align: right;"><strong>Example:</strong></td>
<td style="text-align: left;"><em>A delivery that includes a web application, shall include description of the build process, such as the compilation of source code, packaging of the application, and deployment steps. This for instance could include details on the specific versions of tools used (e.g. Node.js, Docker etc.)</em></td>
</tr>
</tbody>
</table>
<table class="caption-top table">
<colgroup>
<col style="width: 26%">
<col style="width: 73%">
</colgroup>
<thead>
<tr class="header">
<th style="text-align: right;"><strong>Reproducibility 2:</strong></th>
<th style="text-align: left;"><strong>Data sources to be supplied with deliverables</strong></th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td style="text-align: right;"><strong>What:</strong></td>
<td style="text-align: left;">IT solutions which utilize data sources must supply the data sources</td>
</tr>
<tr class="even">
<td style="text-align: right;"><strong>Why:</strong></td>
<td style="text-align: left;">To ensure that the deliverable can be re-produced details are required on data sources used along with any enrichment which have been applied to the data source</td>
</tr>
<tr class="odd">
<td style="text-align: right;"><strong>Consequence:</strong></td>
<td style="text-align: left;">Data source location must be provided if data are publicly available. If data are not accessible to the CLMS, the data are to be provided as part of the deliverable</td>
</tr>
<tr class="even">
<td style="text-align: right;"><strong>Example:</strong></td>
<td style="text-align: left;"><em>If the software relies on a proprietary weather data API that is not publicly accessible, the data, or at least a sample dataset, should be provided with the delivery. If the API is publicly available, detailed instructions on how to access it (e.g., API keys, endpoint URLs) must be included</em></td>
</tr>
</tbody>
</table>
<table class="caption-top table">
<colgroup>
<col style="width: 26%">
<col style="width: 73%">
</colgroup>
<thead>
<tr class="header">
<th style="text-align: right;"><strong>Reproducibility 3:</strong></th>
<th style="text-align: left;"><strong>List of software used in development of IT solution to be provided</strong></th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td style="text-align: right;"><strong>What:</strong></td>
<td style="text-align: left;">The software products which have been used in the development of the software are to be listed as part of the deliverable</td>
</tr>
<tr class="even">
<td style="text-align: right;"><strong>Why:</strong></td>
<td style="text-align: left;">To ensure that the IT solution can be further developed details are required of the software components/products that were used in the development</td>
</tr>
<tr class="odd">
<td style="text-align: right;"><strong>Consequence:</strong></td>
<td style="text-align: left;">List of software development tools used in the production to be provided. Further for client specific developments the source code must also be provided</td>
</tr>
<tr class="even">
<td style="text-align: right;"><strong>Example:</strong></td>
<td style="text-align: left;"><em>A system consisting of several building blocks, such as User Interface, backend, importer, and exporter modules, shall be provided with a list of software development tools, used for production of these building blocks and modules</em></td>
</tr>
</tbody>
</table>
<table class="caption-top table">
<colgroup>
<col style="width: 26%">
<col style="width: 73%">
</colgroup>
<thead>
<tr class="header">
<th style="text-align: right;"><strong>Reproducibility 4:</strong></th>
<th style="text-align: left;"><strong>Automation tool/scripts used in the production of the IT solution must be provided</strong></th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td style="text-align: right;"><strong>What:</strong></td>
<td style="text-align: left;">IT solutions which include automation scripts/workflows in the development must supply these scripts as part of the deliverable</td>
</tr>
<tr class="even">
<td style="text-align: right;"><strong>Why:</strong></td>
<td style="text-align: left;">Automation scripts used in development are viewed as part of the deliverable and are required for reproduction of the solution</td>
</tr>
<tr class="odd">
<td style="text-align: right;"><strong>Consequence:</strong></td>
<td style="text-align: left;">Automation scripts whether as stand-alone scripts or as a configuration of standard/commercial software must be provided as part of the deliverable</td>
</tr>
<tr class="even">
<td style="text-align: right;"><strong>Example:</strong></td>
<td style="text-align: left;"><em>If the IT deliverable includes an automatic backup that generates full backups in certain increments, then the automation scripts behind the backup generation must be provided as part of the deliverable, so that they could be recreated</em></td>
</tr>
</tbody>
</table>
<table class="caption-top table">
<colgroup>
<col style="width: 26%">
<col style="width: 73%">
</colgroup>
<thead>
<tr class="header">
<th style="text-align: right;"><strong>Reproducibility 5:</strong></th>
<th style="text-align: left;"><strong>If a solution includes outcomes of pre-executed algorithms the prerequisites for running the algorithms must be provided</strong></th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td style="text-align: right;"><strong>What:</strong></td>
<td style="text-align: left;">To ensure reproducibility, the algorithms must be provided either as pseudo code or as source code</td>
</tr>
<tr class="even">
<td style="text-align: right;"><strong>Why:</strong></td>
<td style="text-align: left;">The foundation of the IT solution must be re-producible to ensure future enhancements are possible say if new insights/data become available also after the end of the contractual agreement</td>
</tr>
<tr class="odd">
<td style="text-align: right;"><strong>Consequence:</strong></td>
<td style="text-align: left;">Supplier must as part of the deliverable also detail any algorithms which form the basis of the solution</td>
</tr>
<tr class="even">
<td style="text-align: right;"><strong>Example:</strong></td>
<td style="text-align: left;"><em>A spatial product, providing a detailed pan-European wall to wall 10-meter spatial resolution raster product, that is based on a supervised classification of satellite image time-series. The supplier must provide a detailed description of the algorithm that was used for classifying satellite-imagery time-series</em></td>
</tr>
</tbody>
</table>
</section>
<section id="reusability" class="level2" data-number="4.2">
<h2 data-number="4.2" class="anchored" data-anchor-id="reusability"><span class="header-section-number">4.2</span> Reusability</h2>
<p>The principle of reusability is detailed in the following sub-principles:</p>
<table class="caption-top table">
<colgroup>
<col style="width: 25%">
<col style="width: 75%">
</colgroup>
<thead>
<tr class="header">
<th style="text-align: right;"><strong>Reusability 1:</strong></th>
<th style="text-align: left;"><strong>IT solutions should be open-ended equipped with APIs</strong></th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td style="text-align: right;"><strong>What:</strong></td>
<td style="text-align: left;">IT solutions should be open-ended equipped with APIs through which functionality or data key for the end user may be accessed</td>
</tr>
<tr class="even">
<td style="text-align: right;"><strong>Why:</strong></td>
<td style="text-align: left;">To ensure that further work benefit from existing solutions it is paramount that systems delivered are open ended. Future work can hereby utilize and benefit from previous work. Delivered IT solutions should form part of the overall IT ecosystem of the EEA CLMS program so that the “whole is greater than the sum”</td>
</tr>
<tr class="odd">
<td style="text-align: right;"><strong>Consequence:</strong></td>
<td style="text-align: left;">IT solutions should be provided with APIs which access key functionality of the IT solutions</td>
</tr>
<tr class="even">
<td style="text-align: right;"><strong>Example:</strong></td>
<td style="text-align: left;"><em>A webservice provided, which publishes geospatial data, has an API Rest service, which grants users direct access to the data</em></td>
</tr>
</tbody>
</table>
<table class="caption-top table">
<colgroup>
<col style="width: 25%">
<col style="width: 75%">
</colgroup>
<thead>
<tr class="header">
<th style="text-align: right;"><strong>Reusability 2:</strong></th>
<th style="text-align: left;"><strong>Scripts used in production must be delivered as part of IT solutions</strong></th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td style="text-align: right;"><strong>What:</strong></td>
<td style="text-align: left;">Scripts should be delivered with code so that they may be used as templates for the end user for further development</td>
</tr>
<tr class="even">
<td style="text-align: right;"><strong>Why:</strong></td>
<td style="text-align: left;">Data, conditions, or requirements may change for an IT solution. To ensure that such changes can be accommodated the underlying script must be possible to modify to reflect and support such changes</td>
</tr>
<tr class="odd">
<td style="text-align: right;"><strong>Consequence:</strong></td>
<td style="text-align: left;">Scripts used in the productions form part of the final deliverable</td>
</tr>
<tr class="even">
<td style="text-align: right;"><strong>Example:</strong></td>
<td style="text-align: left;"><em>IT delivery, consisting of several building blocks, shall be provided with scripts, included with the final delivery of the code, so that the end users of the system could modify, expand, or adopt the building blocks/modules to suit specific needs or add new features</em></td>
</tr>
</tbody>
</table>
<table class="caption-top table">
<colgroup>
<col style="width: 25%">
<col style="width: 75%">
</colgroup>
<thead>
<tr class="header">
<th style="text-align: right;"><strong>Reusability 3:</strong></th>
<th style="text-align: left;"><strong>Documentation of IT solutions are to be provided</strong></th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td style="text-align: right;"><strong>What:</strong></td>
<td style="text-align: left;">Documentation of the developed IT solutions must be provided. The requested documentation shall also be provided in quarto markdown format on the dedicated EEA GitHub repository</td>
</tr>
<tr class="even">
<td style="text-align: right;"><strong>Why:</strong></td>
<td style="text-align: left;">For the further use and improvements of the IT solution, technical documentation is paramount.</td>
</tr>
<tr class="odd">
<td style="text-align: right;"><strong>Consequence:</strong></td>
<td style="text-align: left;">Documentation including but not limited to System Description Document (SDD), System Deployment Document and Examples must be provided with IT solution deliverables. The requested documents shall also be provided in the quarto markdown format.</td>
</tr>
<tr class="even">
<td style="text-align: right;"><strong>Example:</strong></td>
<td style="text-align: left;"><em>An IT delivery, consisting of several building blocks, shall be provided with SDD, user guidelines, and detailed documentation of system deployment, including, but not limited to system and storage architecture, infrastructure setup, provisioning, monitoring, disaster recovery, accessibility, scalability options and performance. If requested, this documentation shall be provided in quarto markdown format on the dedicated EEA GitHub repository</em></td>
</tr>
</tbody>
</table>
</section>
<section id="transparency" class="level2" data-number="4.3">
<h2 data-number="4.3" class="anchored" data-anchor-id="transparency"><span class="header-section-number">4.3</span> Transparency</h2>
<p>The CLMS is funded by the EU and supports its community with data and services. As such, these products and services are to be part of the foundation for further work in the field and accessible to the community. To support this, the principle of transparency is detailed in the following subprinciples:</p>
<table class="caption-top table">
<thead>
<tr class="header">
<th style="text-align: right;"><strong>Transparency 1:</strong></th>
<th style="text-align: left;"><strong>Source code of client specific software to be supplied with IT solution</strong></th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td style="text-align: right;"><strong>What:</strong></td>
<td style="text-align: left;">Source code including deployment and integration scripts of client specific IT solution is supplied as part of the deliverable and made publicly available under the EUPL-1.2<a href="#fn1" class="footnote-ref" id="fnref1" role="doc-noteref"><sup>1</sup></a> license</td>
</tr>
<tr class="even">
<td style="text-align: right;"><strong>Why:</strong></td>
<td style="text-align: left;">To ensure transparency, it is essential to have clear insights into the client-specific software. This enables efficient future developments and modifications</td>
</tr>
<tr class="odd">
<td style="text-align: right;"><strong>Consequence:</strong></td>
<td style="text-align: left;">Source code of client specific software must be delivered with IT solution. The source code shall include CI/CD (Continuous Integration/Continuous Development), Docker recipes and be published under the EUPL-1.2. license</td>
</tr>
<tr class="even">
<td style="text-align: right;"><strong>Example:</strong></td>
<td style="text-align: left;"><em>Source code of all the components of the specific IT solution must be delivered. Any updates or developments of the source code shall be reflected in the EEA GitHub repository, which is the main repository of the system. Moreover, the specific client IT solutions shall be published under the EUPL-1.2 license, so the openness and transparency are ensured</em></td>
</tr>
</tbody>
</table>
<table class="caption-top table">
<colgroup>
<col style="width: 26%">
<col style="width: 73%">
</colgroup>
<thead>
<tr class="header">
<th style="text-align: right;"><strong>Transparency 2:</strong></th>
<th style="text-align: left;"><strong>Inline documentation of the source code</strong></th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td style="text-align: right;"><strong>What:</strong></td>
<td style="text-align: left;">Source code of client specific IT solution must be documented in-line</td>
</tr>
<tr class="even">
<td style="text-align: right;"><strong>Why:</strong></td>
<td style="text-align: left;">To effectuate the handover from one developer to the next inline documentation are to be included to guide the developer on the job</td>
</tr>
<tr class="odd">
<td style="text-align: right;"><strong>Consequence:</strong></td>
<td style="text-align: left;">Source code must have inline documentation. Inline code should be formatted so that it may be easily extracted to generate online documentation</td>
</tr>
<tr class="even">
<td style="text-align: right;"><strong>Example:</strong></td>
<td style="text-align: left;"><em>Source code of all the components of the IT solution must have inline documentation. The documentation shall be structured, following common conventions, and kept at a minimal, but comprehensive level</em></td>
</tr>
</tbody>
</table>
<table class="caption-top table">
<colgroup>
<col style="width: 26%">
<col style="width: 73%">
</colgroup>
<thead>
<tr class="header">
<th style="text-align: right;"><strong>Transparency 3:</strong></th>
<th style="text-align: left;"><strong>Commercial software used in the production/development must be attainable by the EEA or a third-party provider</strong></th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td style="text-align: right;"><strong>What:</strong></td>
<td style="text-align: left;">Commercial software which are prerequisites must be attainable on comparable terms. Such software is justified only if no open alternative exists</td>
</tr>
<tr class="even">
<td style="text-align: right;"><strong>Why:</strong></td>
<td style="text-align: left;">To ensure that further work may be carried out any prerequisites in the form of software must be attainable by the EEA or a supplier</td>
</tr>
<tr class="odd">
<td style="text-align: right;"><strong>Consequence:</strong></td>
<td style="text-align: left;">Generally attainable commercial software used in production must be listed when delivering an IT solution. Name of software, version, EOL and EOS to be supplied</td>
</tr>
<tr class="even">
<td style="text-align: right;"><strong>Example:</strong></td>
<td style="text-align: left;"><em>An IT solution is deploying various components and the set-up of the virtual machines that houses the components is done by means of an infrastructure as-a-code-tool. All the capabilities of the infrastructure as-a-code-tool, that require purchasing must be listed when delivering the IT solution</em></td>
</tr>
</tbody>
</table>
</section>
<section id="scalability" class="level2" data-number="4.4">
<h2 data-number="4.4" class="anchored" data-anchor-id="scalability"><span class="header-section-number">4.4</span> Scalability</h2>
<p>The delivered IT Solutions must be scalable to ensure future enhancements and demands. Scalability in this sense covers both scalability in functionality as well as scalability in terms of being able to handle an increased load/traffic. To this end the following scalability principles apply</p>
<table class="caption-top table">
<colgroup>
<col style="width: 26%">
<col style="width: 73%">
</colgroup>
<thead>
<tr class="header">
<th style="text-align: right;"><strong>Scalability 1:</strong></th>
<th style="text-align: left;"><strong>Client specific IT solutions should have a modular structure</strong></th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td style="text-align: right;"><strong>What:</strong></td>
<td style="text-align: left;">Modular structure of client specific IT solutions is a requirement. This may be achieved using e.g. microservices</td>
</tr>
<tr class="even">
<td style="text-align: right;"><strong>Why:</strong></td>
<td style="text-align: left;">A modular structure is sought to ensure further development, and updates are possible. The possibility of substituting or adding modules in an IT solution will increase the lifespan of a solution</td>
</tr>
<tr class="odd">
<td style="text-align: right;"><strong>Consequence:</strong></td>
<td style="text-align: left;">Modular architecture of IT solutions is a requisite</td>
</tr>
<tr class="even">
<td style="text-align: right;"><strong>Example:</strong></td>
<td style="text-align: left;"><em>If the client specific IT solution has, for Example, grown its user base since the launch of the solution, then scaling up shall be possible at any time – both vertically (more CPUs, RAM) and horizontally (more VMs)</em></td>
</tr>
</tbody>
</table>
<table class="caption-top table">
<colgroup>
<col style="width: 26%">
<col style="width: 73%">
</colgroup>
<thead>
<tr class="header">
<th style="text-align: right;"><strong>Scalability 2:</strong></th>
<th style="text-align: left;"><strong>Client specific IT solutions must be able to interface with other IT solutions</strong></th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td style="text-align: right;"><strong>What:</strong></td>
<td style="text-align: left;">The IT deliverable must be able to be used in conjunction with other deliverables to form a composite solution</td>
</tr>
<tr class="even">
<td style="text-align: right;"><strong>Why:</strong></td>
<td style="text-align: left;">To make the most of the funds available the developed solutions should form part of an IT ecosystem making up a whole</td>
</tr>
<tr class="odd">
<td style="text-align: right;"><strong>Consequence:</strong></td>
<td style="text-align: left;">IT deliverables must be equipped with documented APIs for interfacing with other IT applications</td>
</tr>
<tr class="even">
<td style="text-align: right;"><strong>Example:</strong></td>
<td style="text-align: left;"><em>A client specific product, which can be used for extracting and manipulating data, should be accessible programmatically through e.g. well documented REST services</em></td>
</tr>
</tbody>
</table>
</section>
<section id="maintainability" class="level2" data-number="4.5">
<h2 data-number="4.5" class="anchored" data-anchor-id="maintainability"><span class="header-section-number">4.5</span> Maintainability</h2>
<p>The EEA aims in the CLMS program to be able to provide updated products when new data becomes available. To reduce the time to market the principle of maintainability is to be followed.</p>
<table class="caption-top table">
<colgroup>
<col style="width: 26%">
<col style="width: 73%">
</colgroup>
<thead>
<tr class="header">
<th style="text-align: right;"><strong>Maintainability 1:</strong></th>
<th style="text-align: left;"><strong>IT solutions are to be delivered on a principle of CI/CD</strong></th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td style="text-align: right;"><strong>What:</strong></td>
<td style="text-align: left;">The launch of new releases of IT deliverables are to be configured and managed so that new functionality is available as soon as possible. The principle of CI/CD are to be adhered to</td>
</tr>
<tr class="even">
<td style="text-align: right;"><strong>Why:</strong></td>
<td style="text-align: left;">Time to market is to be reduced through an approach of maintainability of deployments as soon as possible</td>
</tr>
<tr class="odd">
<td style="text-align: right;"><strong>Consequence:</strong></td>
<td style="text-align: left;">IT deliverables are to be supplied with a dev-ops set-up which supports CI/CD</td>
</tr>
<tr class="even">
<td style="text-align: right;"><strong>Example:</strong></td>
<td style="text-align: left;"><em>A delivered IT solution is organized with a test server environment potentially a pre-production environment, used for quality assurance and continuous development, so that deployment to production can be initiated smoothly</em></td>
</tr>
</tbody>
</table>
<table class="caption-top table">
<colgroup>
<col style="width: 26%">
<col style="width: 73%">
</colgroup>
<thead>
<tr class="header">
<th style="text-align: right;"><strong>Maintainability 2:</strong></th>
<th style="text-align: left;"><strong>IT solutions are to be Dockerized or similar</strong></th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td style="text-align: right;"><strong>What:</strong></td>
<td style="text-align: left;">The use of container technology is encouraged</td>
</tr>
<tr class="even">
<td style="text-align: right;"><strong>Why:</strong></td>
<td style="text-align: left;">Container technology eases the work of moving IT solutions around the IT infrastructure making deployment easier to automate</td>
</tr>
<tr class="odd">
<td style="text-align: right;"><strong>Consequence:</strong></td>
<td style="text-align: left;">IT solutions are to be deployed using Dockerization or similar</td>
</tr>
<tr class="even">
<td style="text-align: right;"><strong>Example:</strong></td>
<td style="text-align: left;"><em>Software components of the client specific IT solution shall be provided as docker images so that deployment is flexible with respect to hardware</em></td>
</tr>
</tbody>
</table>
<table class="caption-top table">
<colgroup>
<col style="width: 26%">
<col style="width: 73%">
</colgroup>
<thead>
<tr class="header">
<th style="text-align: right;"><strong>Maintainability 3:</strong></th>
<th style="text-align: left;"><strong>Tests are to be organised so that they may be automated</strong></th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td style="text-align: right;"><strong>What:</strong></td>
<td style="text-align: left;">Tests are to be structured so that they may be easily automated</td>
</tr>
<tr class="even">
<td style="text-align: right;"><strong>Why:</strong></td>
<td style="text-align: left;">To ensure that the CI/CD process does not introduce bugs or deployment failures, tests are to be automated so that they can continuously be run to ensure the quality of the solution and its possible enhancements</td>
</tr>
<tr class="odd">
<td style="text-align: right;"><strong>Consequence:</strong></td>
<td style="text-align: left;">Tests are to be delivered so that they can be automated</td>
</tr>
<tr class="even">
<td style="text-align: right;"><strong>Example:</strong></td>
<td style="text-align: left;"><em>The delivered solution has in the test phase run through a number of tests e.g. unit tests and result verification tests. These will be the basis for automated regression tests</em></td>
</tr>
</tbody>
</table>
<table class="caption-top table">
<colgroup>
<col style="width: 26%">
<col style="width: 73%">
</colgroup>
<thead>
<tr class="header">
<th style="text-align: right;"><strong>Maintainability 4:</strong></th>
<th style="text-align: left;"><strong>IT solutions are to be regularly assessed</strong></th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td style="text-align: right;"><strong>What:</strong></td>
<td style="text-align: left;">IT solutions are to be automatically monitored with a notification service, and their performance routinely evaluated to ensure optimal functioning</td>
</tr>
<tr class="even">
<td style="text-align: right;"><strong>Why:</strong></td>
<td style="text-align: left;">Regular assessments ensure that IT solutions can be maintained so as to meet emerging needs, threats and technological advancements</td>
</tr>
<tr class="odd">
<td style="text-align: right;"><strong>Consequence:</strong></td>
<td style="text-align: left;">IT solution’s scalability, security, and overall performance are continuously monitored and evaluated to address performance and or security issues</td>
</tr>
<tr class="even">
<td style="text-align: right;"><strong>Example:</strong></td>
<td style="text-align: left;"><em>The delivered IT solution and its associated dependencies are regularly assessed and evaluated. The evaluation process should also account for advancements in technology and track developments to ensure the solution remains relevant and effective</em></td>
</tr>
</tbody>
</table>
</section>
<section id="it-security" class="level2" data-number="4.6">
<h2 data-number="4.6" class="anchored" data-anchor-id="it-security"><span class="header-section-number">4.6</span> IT security</h2>
<p>The IT solutions of the CLMS program shall ensure system integrity against various security threats, protection of the data, and maintenance of privacy. The following sub-principals are to be followed:</p>
<table class="caption-top table">
<colgroup>
<col style="width: 26%">
<col style="width: 73%">
</colgroup>
<thead>
<tr class="header">
<th style="text-align: right;"><strong>IT security 1:</strong></th>
<th style="text-align: left;"><strong>Incorporate security considerations from the beginning of the system development</strong></th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td style="text-align: right;"><strong>What:</strong></td>
<td style="text-align: left;">Ensure security is integrated into all stages of the system development lifecycle, from planning to deployment</td>
</tr>
<tr class="even">
<td style="text-align: right;"><strong>Why:</strong></td>
<td style="text-align: left;">Early integration of security measures reduces vulnerabilities, lowers costs associated with late-stage fixes, and ensures robust protection against threats</td>
</tr>
<tr class="odd">
<td style="text-align: right;"><strong>Consequence:</strong></td>
<td style="text-align: left;">Threat modelling and security assessments need to be conducted from the start, as well as allocation of resources for ongoing security reviews and testing</td>
</tr>
<tr class="even">
<td style="text-align: right;"><strong>Example:</strong></td>
<td style="text-align: left;"><em>Standard aspects such as two factor authentication, protection against SQL injection, encryption of sensitive data, etc.</em></td>
</tr>
</tbody>
</table>
<table class="caption-top table">
<colgroup>
<col style="width: 26%">
<col style="width: 73%">
</colgroup>
<thead>
<tr class="header">
<th style="text-align: right;"><strong>IT security 2:</strong></th>
<th style="text-align: left;"><strong>Compliance with relevant laws, regulations and industry standards</strong></th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td style="text-align: right;"><strong>What:</strong></td>
<td style="text-align: left;">IT-solutions must adhere to legal requirements, industry standards, and regulations e.g. EUDPR, ISO</td>
</tr>
<tr class="even">
<td style="text-align: right;"><strong>Why:</strong></td>
<td style="text-align: left;">Compliance ensures legal and regulatory adherence, builds trust, protects sensitive data, and mitigates risk of legal penalties and breaches</td>
</tr>
<tr class="odd">
<td style="text-align: right;"><strong>Consequence:</strong></td>
<td style="text-align: left;">IT deliverables need to incorporate robust security measures, include documentation of compliance efforts, and ensure features and processes aligned with legal and industry measures</td>
</tr>
<tr class="even">
<td style="text-align: right;"><strong>Example:</strong></td>
<td style="text-align: left;"><em>Data handling agreements must be in place, consideration of server location in EU, etc.</em></td>
</tr>
</tbody>
</table>
<table class="caption-top table">
<colgroup>
<col style="width: 26%">
<col style="width: 73%">
</colgroup>
<thead>
<tr class="header">
<th style="text-align: right;"><strong>IT security 3:</strong></th>
<th style="text-align: left;"><strong>Ensuring that users and systems have appropriate permissions based on their roles and responsibilities</strong></th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td style="text-align: right;"><strong>What:</strong></td>
<td style="text-align: left;">Implement role-based access control (RBAC) to manage user and system permissions according to their roles</td>
</tr>
<tr class="even">
<td style="text-align: right;"><strong>Why:</strong></td>
<td style="text-align: left;">It prevents unauthorized access, minimizes the risk of data breaches, and ensures that users only have access to the information necessary for their roles</td>
</tr>
<tr class="odd">
<td style="text-align: right;"><strong>Consequence:</strong></td>
<td style="text-align: left;">The provider will need to define clear roles and responsibilities, implement RBAC policies, regularly review and update access controls</td>
</tr>
<tr class="even">
<td style="text-align: right;"><strong>Example:</strong></td>
<td style="text-align: left;"><em>A delivered IT solution has role-based accesses, which ensures that only Admin-Users are allowed to manage (add, edit, activate, inactivate) users and organisations. Also, only administrator can view and edit any ingestion and extraction within the system to support users if they need any help</em></td>
</tr>
</tbody>
</table>
</section>
<section id="resilience" class="level2" data-number="4.7">
<h2 data-number="4.7" class="anchored" data-anchor-id="resilience"><span class="header-section-number">4.7</span> Resilience</h2>
<table class="caption-top table">
<colgroup>
<col style="width: 26%">
<col style="width: 73%">
</colgroup>
<thead>
<tr class="header">
<th style="text-align: right;"><strong>Resilience 1:</strong></th>
<th style="text-align: left;"><strong>IT solution should have a disaster recovery plan</strong></th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td style="text-align: right;"><strong>What:</strong></td>
<td style="text-align: left;">IT solution should have a well-defined process of restoring IT systems, data, and operations following a disruption</td>
</tr>
<tr class="even">
<td style="text-align: right;"><strong>Why:</strong></td>
<td style="text-align: left;">To ensure that the IT solution and data are recoverable after an unforeseen event</td>
</tr>
<tr class="odd">
<td style="text-align: right;"><strong>Consequence:</strong></td>
<td style="text-align: left;">IT deliverables will be provided with well-prepared disaster recovery plan that will ensure a rapid restoration of services and data integrity, and minimize damage</td>
</tr>
<tr class="even">
<td style="text-align: right;"><strong>Example:</strong></td>
<td style="text-align: left;"><em>A delivered IT solution has a disaster recovery plan that includes backup protocols, data replication, and recovery timelines</em></td>
</tr>
</tbody>
</table>
<table class="caption-top table">
<colgroup>
<col style="width: 26%">
<col style="width: 73%">
</colgroup>
<thead>
<tr class="header">
<th style="text-align: right;"><strong>Resilience 2:</strong></th>
<th style="text-align: left;"><strong>Ensuring IT solution continuity</strong></th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td style="text-align: right;"><strong>What:</strong></td>
<td style="text-align: left;">IT solution is designed and implemented in a way that ensures continuous operation during a disruption</td>
</tr>
<tr class="even">
<td style="text-align: right;"><strong>Why:</strong></td>
<td style="text-align: left;">To maintain critical operations with a minimal downtime, even when confronted with unforeseen events</td>
</tr>
<tr class="odd">
<td style="text-align: right;"><strong>Consequence:</strong></td>
<td style="text-align: left;">IT deliverables are designed for high availability, incorporating redundancy so that in case of a disruption/failure, restore service can immediately take over, minimizing downtime and ensuring continuous operation</td>
</tr>
<tr class="even">
<td style="text-align: right;"><strong>Example:</strong></td>
<td style="text-align: left;"><em>In the event of a system failure or disruption of the delivered IT solution, restore service automatically take over to maintain service continuity. For instance, if a primary system goes down, a secondary system activates, ensuring that users experience no downtime.</em></td>
</tr>
</tbody>
</table>
<p>…</p>
</section>
</section>
<div id="quarto-appendix" class="default"><section id="footnotes" class="footnotes footnotes-end-of-document" role="doc-endnotes"><h2 class="anchored quarto-appendix-heading">Footnotes</h2>
<ol>
<li id="fn1"><p><a href="https://commission.europa.eu/content/european-union-public-licence_en">European Union Public Licence - European Commission (europa.eu)</a><a href="#fnref1" class="footnote-back" role="doc-backlink">↩︎</a></p></li>
</ol>
</section></div></main>
<!-- /main column -->
<script id="quarto-html-after-body" type="application/javascript">
window.document.addEventListener("DOMContentLoaded", function (event) {
const toggleBodyColorMode = (bsSheetEl) => {
const mode = bsSheetEl.getAttribute("data-mode");
const bodyEl = window.document.querySelector("body");
if (mode === "dark") {
bodyEl.classList.add("quarto-dark");
bodyEl.classList.remove("quarto-light");
} else {
bodyEl.classList.add("quarto-light");
bodyEl.classList.remove("quarto-dark");
}
}
const toggleBodyColorPrimary = () => {
const bsSheetEl = window.document.querySelector("link#quarto-bootstrap");
if (bsSheetEl) {
toggleBodyColorMode(bsSheetEl);
}
}
toggleBodyColorPrimary();
const icon = "";
const anchorJS = new window.AnchorJS();
anchorJS.options = {
placement: 'right',
icon: icon
};
anchorJS.add('.anchored');
const isCodeAnnotation = (el) => {
for (const clz of el.classList) {
if (clz.startsWith('code-annotation-')) {
return true;
}
}
return false;
}
const onCopySuccess = function(e) {
// button target
const button = e.trigger;
// don't keep focus
button.blur();
// flash "checked"
button.classList.add('code-copy-button-checked');
var currentTitle = button.getAttribute("title");
button.setAttribute("title", "Copied!");
let tooltip;
if (window.bootstrap) {
button.setAttribute("data-bs-toggle", "tooltip");
button.setAttribute("data-bs-placement", "left");
button.setAttribute("data-bs-title", "Copied!");
tooltip = new bootstrap.Tooltip(button,
{ trigger: "manual",
customClass: "code-copy-button-tooltip",
offset: [0, -8]});
tooltip.show();
}
setTimeout(function() {
if (tooltip) {
tooltip.hide();
button.removeAttribute("data-bs-title");
button.removeAttribute("data-bs-toggle");
button.removeAttribute("data-bs-placement");
}
button.setAttribute("title", currentTitle);
button.classList.remove('code-copy-button-checked');
}, 1000);
// clear code selection
e.clearSelection();
}
const getTextToCopy = function(trigger) {
const codeEl = trigger.previousElementSibling.cloneNode(true);
for (const childEl of codeEl.children) {
if (isCodeAnnotation(childEl)) {
childEl.remove();
}
}
return codeEl.innerText;
}
const clipboard = new window.ClipboardJS('.code-copy-button:not([data-in-quarto-modal])', {
text: getTextToCopy
});
clipboard.on('success', onCopySuccess);
if (window.document.getElementById('quarto-embedded-source-code-modal')) {
// For code content inside modals, clipBoardJS needs to be initialized with a container option
// TODO: Check when it could be a function (https://github.com/zenorocha/clipboard.js/issues/860)
const clipboardModal = new window.ClipboardJS('.code-copy-button[data-in-quarto-modal]', {
text: getTextToCopy,
container: window.document.getElementById('quarto-embedded-source-code-modal')
});
clipboardModal.on('success', onCopySuccess);
}
var localhostRegex = new RegExp(/^(?:http|https):\/\/localhost\:?[0-9]*\//);
var mailtoRegex = new RegExp(/^mailto:/);
var filterRegex = new RegExp('/' + window.location.host + '/');
var isInternal = (href) => {
return filterRegex.test(href) || localhostRegex.test(href) || mailtoRegex.test(href);
}
// Inspect non-navigation links and adorn them if external
var links = window.document.querySelectorAll('a[href]:not(.nav-link):not(.navbar-brand):not(.toc-action):not(.sidebar-link):not(.sidebar-item-toggle):not(.pagination-link):not(.no-external):not([aria-hidden]):not(.dropdown-item):not(.quarto-navigation-tool):not(.about-link)');
for (var i=0; i<links.length; i++) {
const link = links[i];
if (!isInternal(link.href)) {
// undo the damage that might have been done by quarto-nav.js in the case of
// links that we want to consider external
if (link.dataset.originalHref !== undefined) {
link.href = link.dataset.originalHref;
}
}
}
function tippyHover(el, contentFn, onTriggerFn, onUntriggerFn) {
const config = {
allowHTML: true,
maxWidth: 500,
delay: 100,
arrow: false,
appendTo: function(el) {
return el.parentElement;
},
interactive: true,
interactiveBorder: 10,
theme: 'quarto',
placement: 'bottom-start',
};
if (contentFn) {
config.content = contentFn;
}
if (onTriggerFn) {
config.onTrigger = onTriggerFn;
}
if (onUntriggerFn) {
config.onUntrigger = onUntriggerFn;
}
window.tippy(el, config);
}
const noterefs = window.document.querySelectorAll('a[role="doc-noteref"]');
for (var i=0; i<noterefs.length; i++) {
const ref = noterefs[i];
tippyHover(ref, function() {
// use id or data attribute instead here
let href = ref.getAttribute('data-footnote-href') || ref.getAttribute('href');
try { href = new URL(href).hash; } catch {}
const id = href.replace(/^#\/?/, "");
const note = window.document.getElementById(id);
if (note) {
return note.innerHTML;
} else {
return "";
}
});
}
const xrefs = window.document.querySelectorAll('a.quarto-xref');
const processXRef = (id, note) => {