forked from rdmorganiser/rdmo-catalog
-
Notifications
You must be signed in to change notification settings - Fork 0
/
questions-smp.xml
3080 lines (3014 loc) · 180 KB
/
questions-smp.xml
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
<?xml version="1.0" encoding="UTF-8"?>
<rdmo xmlns:dc="http://purl.org/dc/elements/1.1/" created="2024-03-12T14:56:06.262241+01:00" version="2.1.3">
<catalog dc:uri="https://rdmorganiser.github.io/terms/questions/smp">
<uri_prefix>https://rdmorganiser.github.io/terms</uri_prefix>
<uri_path>smp</uri_path>
<dc:comment>This software project management catalogue was developed by the Max Planck Digital Library in 2022. Thanks to all our team colleagues for their support.
This SMP template was inspired by some documentation, specially:
* https://www.software.ac.uk/resources/guides/software-management-plans
* https://opencarp.org/about/software-management-plan</dc:comment>
<order>98</order>
<title lang="en">Software Management Plan for Researchers</title>
<help lang="en">This catalogue is for the management of scientific software projects. It supports scientists in the development and project organisation of software developments through fifty questions in different topic blocks. This is version 3.0 of the catalogue.</help>
<title lang="de">Software-Management-Plan für Forschende</title>
<help lang="de">Dieser Katalog ist für das Management von wissenschaftlichen Software-Projekten. Er unterstützt Wissenschaftler_innen bei der Entwicklung und der Projektorganisation von Software-Entwicklungen durch fünfzig Fragen in unterschiedlichen Themenblöcken. Dies ist Version 3.0.</help>
<title lang="fr">Plan de gestion des logiciels pour chercheurs</title>
<help lang="fr">Ce catalogue est destiné à la gestion de projets de logiciels scientifiques. Il aide les scientifiques à développer et à organiser des projets de développement de logiciels grâce à cinquante questions réparties en différents blocs thématiques. Il s'agit de la version 3.0.</help>
<title lang="it">Piano di gestione del software per ricercatori</title>
<help lang="it">Questo catalogo è destinato alla gestione di progetti software scientifici. Supporta gli scienziati nello sviluppo e nell'organizzazione di progetti software con cinquanta domande in diversi blocchi tematici. Questa è la versione 3.0.</help>
<title lang="es">Plan de gestión del software para investigadores</title>
<help lang="es">Este catálogo está destinado a la gestión de proyectos de software científico. Apoya a los científicos en el desarrollo y la organización de proyectos de desarrollo de software con cincuenta preguntas en diferentes bloques temáticos. Se trata de la versión 3.0.</help>
<sections>
<section dc:uri="https://rdmorganiser.github.io/terms/questions/smp/general" order="0"/>
<section dc:uri="https://rdmorganiser.github.io/terms/questions/smp/technical" order="1"/>
<section dc:uri="https://rdmorganiser.github.io/terms/questions/smp/quality-assurance" order="2"/>
<section dc:uri="https://rdmorganiser.github.io/terms/questions/smp/release-and-publish" order="3"/>
<section dc:uri="https://rdmorganiser.github.io/terms/questions/smp/legal-and-ethics" order="4"/>
</sections>
</catalog>
<section dc:uri="https://rdmorganiser.github.io/terms/questions/smp/general">
<uri_prefix>https://rdmorganiser.github.io/terms</uri_prefix>
<uri_path>smp/general</uri_path>
<dc:comment/>
<title lang="en">General</title>
<title lang="de">Allgemein</title>
<title lang="fr"/>
<title lang="it"/>
<title lang="es"/>
<pages>
<page dc:uri="https://rdmorganiser.github.io/terms/questions/smp/general/topic" order="0"/>
<page dc:uri="https://rdmorganiser.github.io/terms/questions/smp/general/project-partner" order="1"/>
<page dc:uri="https://rdmorganiser.github.io/terms/questions/smp/general/schedule" order="2"/>
<page dc:uri="https://rdmorganiser.github.io/terms/questions/smp/general/project-management" order="3"/>
<page dc:uri="https://rdmorganiser.github.io/terms/questions/smp/general/software-requirements" order="4"/>
</pages>
</section>
<page dc:uri="https://rdmorganiser.github.io/terms/questions/smp/general/topic">
<uri_prefix>https://rdmorganiser.github.io/terms</uri_prefix>
<uri_path>smp/general/topic</uri_path>
<dc:comment/>
<attribute/>
<is_collection>False</is_collection>
<title lang="en">Topic</title>
<help lang="en">If you are looking for an introduction to the topic before completing a software management plan, then we recommend Martinez-Ortiz et al. (2022): Practical guide to Software Management Plans, v1.0, <a href="https://doi.org/10.5281/zenodo.7589725" target="_blank">https://doi.org/10.5281/zenodo.7589725</a>.</help>
<verbose_name lang="en"/>
<title lang="de">Thema</title>
<help lang="de">Falls Sie vor dem Ausfüllen eines Software-Management-Plans nach einer Einführung in das Thema suchen, dann empfehlen wir Martinez-Ortiz et al. (2022): Practical guide to Software Management Plans, v1.0, <a href="https://doi.org/10.5281/zenodo.7589725" target="_blank">https://doi.org/10.5281/zenodo.7589725</a>.</help>
<verbose_name lang="de"/>
<title lang="fr"/>
<help lang="fr"/>
<verbose_name lang="fr"/>
<title lang="it"/>
<help lang="it"/>
<verbose_name lang="it"/>
<title lang="es"/>
<help lang="es"/>
<verbose_name lang="es"/>
<questionsets/>
<questions>
<question dc:uri="https://rdmorganiser.github.io/terms/questions/smp/general/topic/project-title" order="0"/>
<question dc:uri="https://rdmorganiser.github.io/terms/questions/smp/general/topic/research-field" order="1"/>
<question dc:uri="https://rdmorganiser.github.io/terms/questions/smp/general/topic/application-class" order="2"/>
<question dc:uri="https://rdmorganiser.github.io/terms/questions/smp/general/topic/intended-use" order="3"/>
<question dc:uri="https://rdmorganiser.github.io/terms/questions/smp/general/topic/buy-or-make" order="4"/>
</questions>
<conditions/>
</page>
<question dc:uri="https://rdmorganiser.github.io/terms/questions/smp/general/topic/project-title">
<uri_prefix>https://rdmorganiser.github.io/terms</uri_prefix>
<uri_path>smp/general/topic/project-title</uri_path>
<dc:comment/>
<attribute dc:uri="https://rdmorganiser.github.io/terms/domain/project/title"/>
<is_collection>False</is_collection>
<is_optional>False</is_optional>
<help lang="en">The title of the software can, of course, still change or be specified in the course of a project. Nevertheless, it makes sense to give the project a specific name at the beginning in order to facilitate further (internal) communication about it.</help>
<text lang="en">What is the title of the software project?</text>
<default_text lang="en"/>
<verbose_name lang="en"/>
<help lang="de">Der Titel der Software kann sich im Laufe eines Projekts noch ändern oder spezifiziert werden. Es ist dennoch schon zu Beginn sinnvoll, dem Projekt eine konkrete Bezeichnung zu geben, um die weitere (interne) Kommunikation darüber zu erleichtern.</help>
<text lang="de">Wie lautet der Titel des Softwareprojekts?</text>
<default_text lang="de"/>
<verbose_name lang="de"/>
<help lang="fr"/>
<text lang="fr"/>
<default_text lang="fr"/>
<verbose_name lang="fr"/>
<help lang="it"/>
<text lang="it"/>
<default_text lang="it"/>
<verbose_name lang="it"/>
<help lang="es"/>
<text lang="es"/>
<default_text lang="es"/>
<verbose_name lang="es"/>
<default_option/>
<default_external_id/>
<widget_type>text</widget_type>
<value_type>text</value_type>
<maximum/>
<minimum/>
<step/>
<unit/>
<width/>
<optionsets/>
<conditions/>
</question>
<question dc:uri="https://rdmorganiser.github.io/terms/questions/smp/general/topic/research-field">
<uri_prefix>https://rdmorganiser.github.io/terms</uri_prefix>
<uri_path>smp/general/topic/research-field</uri_path>
<dc:comment/>
<attribute dc:uri="https://rdmorganiser.github.io/terms/domain/project/research_field"/>
<is_collection>True</is_collection>
<is_optional>False</is_optional>
<help lang="en">The list of disciplines follows the <a href="http://www.dfg.de/en/dfg_profile/statutory_bodies/review_boards/subject_areas/index.jsp" target="_blank">subject classification of the DFG (German Research Foundation)</a>.</help>
<text lang="en">Which research field(s) does this software belong to?</text>
<default_text lang="en"/>
<verbose_name lang="en"/>
<help lang="de">Die Liste der Disziplinen entspricht der <a href="http://www.dfg.de/en/dfg_profile/statutory_bodies/review_boards/subject_areas/index.jsp" target="_blank">Fachsystematik der Deutschen Forschungsgemeinschaft (DFG)</a>.</help>
<text lang="de">Zu welchem(n) Forschungsbereich(en) gehört diese Software?</text>
<default_text lang="de"/>
<verbose_name lang="de"/>
<help lang="fr"/>
<text lang="fr"/>
<default_text lang="fr"/>
<verbose_name lang="fr"/>
<help lang="it"/>
<text lang="it"/>
<default_text lang="it"/>
<verbose_name lang="it"/>
<help lang="es"/>
<text lang="es"/>
<default_text lang="es"/>
<verbose_name lang="es"/>
<default_option/>
<default_external_id/>
<widget_type>select</widget_type>
<value_type>text</value_type>
<maximum/>
<minimum/>
<step/>
<unit/>
<width/>
<optionsets>
<optionset dc:uri="https://rdmorganiser.github.io/terms/options/research_fields"/>
</optionsets>
<conditions/>
</question>
<question dc:uri="https://rdmorganiser.github.io/terms/questions/smp/general/topic/application-class">
<uri_prefix>https://rdmorganiser.github.io/terms</uri_prefix>
<uri_path>smp/general/topic/application-class</uri_path>
<dc:comment>The application classes are essentially based on the "DLR Software Engineering Guidelines" (https://zenodo.org/record/1344612), p. 7-8. Depending on the selection in this questions a selection of different questions is provided below.</dc:comment>
<attribute dc:uri="https://rdmorganiser.github.io/terms/domain/smp/application-class"/>
<is_collection>False</is_collection>
<is_optional>False</is_optional>
<help lang="en">The application classes are essentially based on the "DLR Software Engineering Guidelines" (<a href="https://doi.org/10.5281/zenodo.1344612" target=" _blank">https://doi.org/10.5281/zenodo.1344612</a>), p. 7-8. Depending on the selection in this questions a selection of different questions is provided below.
<details>
<summary>Click here for more information on the application classes for research software</summary>
<b>Application Class 0</b>:
<ul>
<li>Scripts to process data for a publication.</li>
<li>Simple administrative scripts to automate specific tasks.</li>
<li>Software that only demonstrates certain functions or is developed to test them.</li>
</ul>
<b>Application Class 1</b>:
<ul>
<li>Software that students develop during studies, bachelor or master theses.</li>
<li>Software resulting from dissertations in which the long-term development does not matter. </li>
<li>Software resulting from third-party projects with focus on demonstration and without planned long-term development.</li>
</ul>
<b>Application Class 2</b>:
<ul>
<li>Software resulting from dissertations in which maintainability and long-term usage matter.</li>
<li>Software from third-party projects in which maintenance and long-term usage matter beyond the project.</li>
<li>Large research frameworks which are developed by a majority of a department.</li>
</ul>
<b>Application Class 3</b>:
<ul>
<li>Mission critical software, for example, in context of aircraft, autonomous vehicles, health care, patients relation, or space missions.</li>
<li>Software for which the facility gives a warranty within or outside the own institution (e.g., via an external company).</li>
<li>Software that makes a significant contribution to third party funding and research results of the facility, and must therefore work reliably.</li>
</ul>
</details></help>
<text lang="en">In which application class is the software categorised?</text>
<default_text lang="en"/>
<verbose_name lang="en"/>
<help lang="de">Die Anwendungsklassen orientieren sich im Wesentlichen an den "DLR Guidelines for Research Guidelines" (<a href="https://doi.org/10.5281/zenodo.1344612" target=" _blank">https://doi.org/10.5281/zenodo.1344612</a>), S. 7-8. Abhängig von der Auswahl in diesen Fragen wird unten eine Auswahl verschiedener Fragen bereitgestellt.
<Details>
<summary>Hier finden Sie weitere Informationen zu den Anwendungsklassen für Forschungssoftware</summary>
<b>Anwendungsklasse 0</b>:
<ul>
<li>Skripte zur Verarbeitung von Daten für eine Publikation.</li>
<li>Einfache administrative Skripte, um bestimmte Aufgaben zu automatisieren.</li>
<li>Software, die nur bestimmte Funktionen demonstriert oder entwickelt wird, um sie zu testen.</li>
</ul>
<b>Anwendungsklasse 1</b>:
<ul>
<li>Software, die Studierende im Rahmen von Studien-, Bachelor- oder Masterarbeiten entwickeln.</li>
<li>Software, die aus Diplomarbeiten resultiert, bei denen die langfristige Entwicklung keine Rolle spielt. </li>
<li>Software, die aus Drittmittelprojekten mit Schwerpunkt auf Demonstration und ohne geplante langfristige Entwicklung resultiert.</li>
</ul>
<b>Anwendungsklasse 2</b>:
<ul>
<li>Software, die aus Dissertationen resultiert, bei denen Wartbarkeit und langfristige Nutzung eine Rolle spielen.</li>
<li>Software aus Drittmittelprojekten, bei denen Wartung und langfristige Nutzung über das Projekt hinaus von Bedeutung sind.</li>
<li>Große Forschungsrahmenwerke, die mehrheitlich von einer Abteilung entwickelt werden.</li>
</ul>
<b>Anwendungsklasse 3</b>:
<ul>
<li>Missionskritische Software, z.B. im Zusammenhang mit Flugzeugen, autonomen Fahrzeugen, Gesundheitsfürsorge, Patientenbeziehungen oder Weltraummissionen.</li>
<li>Software, für die die Einrichtung innerhalb oder außerhalb der eigenen Institution (z.B. über ein externes Unternehmen) eine Garantie übernimmt.</li>
<li>Software, die einen wesentlichen Beitrag zu Drittmitteln und Forschungsergebnissen der Einrichtung leistet und daher zuverlässig arbeiten muss.</li>
</ul>
</details></help>
<text lang="de">In welche Anwendungsklasse wird die Software eingeordnet?</text>
<default_text lang="de"/>
<verbose_name lang="de"/>
<help lang="fr"/>
<text lang="fr"/>
<default_text lang="fr"/>
<verbose_name lang="fr"/>
<help lang="it"/>
<text lang="it"/>
<default_text lang="it"/>
<verbose_name lang="it"/>
<help lang="es"/>
<text lang="es"/>
<default_text lang="es"/>
<verbose_name lang="es"/>
<default_option/>
<default_external_id/>
<widget_type>radio</widget_type>
<value_type>text</value_type>
<maximum/>
<minimum/>
<step/>
<unit/>
<width/>
<optionsets>
<optionset dc:uri="https://rdmorganiser.github.io/terms/options/application-class"/>
</optionsets>
<conditions/>
</question>
<question dc:uri="https://rdmorganiser.github.io/terms/questions/smp/general/topic/intended-use">
<uri_prefix>https://rdmorganiser.github.io/terms</uri_prefix>
<uri_path>smp/general/topic/intended-use</uri_path>
<dc:comment/>
<attribute dc:uri="https://rdmorganiser.github.io/terms/domain/project/research_question/title"/>
<is_collection>False</is_collection>
<is_optional>False</is_optional>
<help lang="en">The intention for developing software in a scientific context can be manifold. The same applies to the specific application of the software and the contribution to scientific knowledge. Depending on the scientific community, these points can also differ significantly from each other.
We offer here some recommended reading that may be helpful in answering the questions:
* Anzt et al.(2021): deRSE Position Paper: "An environment for sustainable research software in Germany and beyond: Current state, open challenges, and call for action", <a href="https://doi.org/10.12688/f1000research.23224.2" target="_blank">https://doi.org/10.12688/f1000research.23224.2</a>.
* Gardner et al. (2022): Sustained software development, not number of citations or journal choice, is indicative of accurate bioinformatic software, In: Genome Biology 23, 56, <a href="https://doi.org/10.1186/s13059-022-02625-x" target="_blank">https://doi.org/10.1186/s13059-022-02625-x</a>.
* Katerbow, & Feulner (2018): Recommendations on the development, use and provision of Research Software, <a href="https://doi.org/10.5281/zenodo.1172988" target="_blank">https://doi.org/10.5281/zenodo.1172988</a>.
* Lee, et al. (2021): Barely sufficient practices in scientific computing, In: Patterns, 2(2), 100206, <a href="https://doi.org/10.1016/j.patter.2021.100206" target="_blank">https://doi.org/10.1016/j.patter.2021.100206</a>.
* Wuttke et al. (2022): Guidelines for collaborative development of sustainable data treatment software, In: Journal of Neutron Research, vol. 24, no. 1, pp. 33-72, <a href="https://doi.org/10.3233/JNR-220002" target="_blank">https://doi.org/10.3233/JNR-220002</a>.
* Wilson et al. (2017): Good enough practices in scientific computing, In: PLOS Computational Biology, 13(6), e1005510, <a href="https://doi.org/10.1371/journal.pcbi.1005510" target="_blank">https://doi.org/10.1371/journal.pcbi.1005510</a>.
By their very nature, these references are not exhaustive. If you need particular assistance in answering them, it is best to talk to your local colleagues from IT, the Scientific Computing Unit, and so on. They will probably be able to help you.</help>
<text lang="en">What is the intended use of the software? How will your software contribute to research?</text>
<default_text lang="en"/>
<verbose_name lang="en"/>
<help lang="de">Die Intention für die Entwicklung von Software im wissenschaftlichen Kontext kann vielfältig sein. Gleiches gilt für die konkrete Anwendung der Software und dem Beitrag zum wissenschaftlichen Erkenntnisgewinn. Je nach Fachkultur können sich diese Punkte auch deutlich voneinander unterscheiden.
Zur Orientierung und als Unterstützung bieten wir hier einige Literaturempfehlungen, die bei der Beantwortung der Fragen hilfreich seinen können:
* Anzt et al.(2021): deRSE Position Paper: "An environment for sustainable research software in Germany and beyond: Current state, open challenges, and call for action", <a href="https://doi.org/10.12688/f1000research.23224.2" target="_blank">https://doi.org/10.12688/f1000research.23224.2</a>.
* Gardner et al. (2022): Sustained software development, not number of citations or journal choice, is indicative of accurate bioinformatic software, In: Genome Biology 23, 56, <a href="https://doi.org/10.1186/s13059-022-02625-x" target="_blank">https://doi.org/10.1186/s13059-022-02625-x</a>.
* Katerbow, & Feulner (2018): Recommendations on the development, use and provision of Research Software, <a href="https://doi.org/10.5281/zenodo.1172988" target="_blank">https://doi.org/10.5281/zenodo.1172988</a>.
* Lee, et al. (2021): Barely sufficient practices in scientific computing, In: Patterns, 2(2), 100206, <a href="https://doi.org/10.1016/j.patter.2021.100206" target="_blank">https://doi.org/10.1016/j.patter.2021.100206</a>.
* Wuttke et al. (2022): Guidelines for collaborative development of sustainable data treatment software, In: Journal of Neutron Research, vol. 24, no. 1, pp. 33-72, <a href="https://doi.org/10.3233/JNR-220002" target="_blank">https://doi.org/10.3233/JNR-220002</a>.
* Wilson et al. (2017): Good enough practices in scientific computing, In: PLOS Computational Biology, 13(6), e1005510, <a href="https://doi.org/10.1371/journal.pcbi.1005510" target="_blank">https://doi.org/10.1371/journal.pcbi.1005510</a>.
Es liegt in der Natur der Sache, dass diese Literaturhinweise nicht vollumfänglich sind. Wenn Sie bei der Beantwortung konkrete Unterstützung benötigen, dann sprechen Sie am besten mit Ihren lokalen Kolleg_innen von der IT, der Scientific Computing Unit usw. Diese können Ihnen weiterhelfen.</help>
<text lang="de">Was ist der beabsichtigte Verwendungszweck der Software? Wie wird Ihre Software zur Forschung beitragen?</text>
<default_text lang="de"/>
<verbose_name lang="de"/>
<help lang="fr"/>
<text lang="fr"/>
<default_text lang="fr"/>
<verbose_name lang="fr"/>
<help lang="it"/>
<text lang="it"/>
<default_text lang="it"/>
<verbose_name lang="it"/>
<help lang="es"/>
<text lang="es"/>
<default_text lang="es"/>
<verbose_name lang="es"/>
<default_option/>
<default_external_id/>
<widget_type>textarea</widget_type>
<value_type>text</value_type>
<maximum/>
<minimum/>
<step/>
<unit/>
<width/>
<optionsets/>
<conditions/>
</question>
<question dc:uri="https://rdmorganiser.github.io/terms/questions/smp/general/topic/buy-or-make">
<uri_prefix>https://rdmorganiser.github.io/terms</uri_prefix>
<uri_path>smp/general/topic/buy-or-make</uri_path>
<dc:comment/>
<attribute dc:uri="https://rdmorganiser.github.io/terms/domain/smp/buy-or-make"/>
<is_collection>False</is_collection>
<is_optional>False</is_optional>
<help lang="en">Please consider whether it would be more effective to purchase existing software or to adapt an existing open source instead of developing software yourself.
The following (selected) platforms can help:
<ul>
<li>bio.tools (<a href="https://bio.tools" target="_blank" >https://bio.tools</a>)</li>
<li>pypi (<a href="https://pypi.org/" target="_blank" >https://pypi.org/</a>)</li>
<li>Research Software Directory (<a href="https://research-software-directory.org/" target="_blank" >https://research-software-directory.org/</a>)</li>
<li>...</li>
</ul></help>
<text lang="en">What function does the new software have that previous software does not cover? What related software exists and why is it not suitable?</text>
<default_text lang="en"/>
<verbose_name lang="en"/>
<help lang="de">Bitte überlegen Sie, ob es nicht zielführender ist eine existierende Software einzukaufen oder eine bestehende Open Source-Variante anzupassen anstatt eine eigene Software vollständig selbst zu entwickeln.
Folgende (ausgewählte) Plattformen können hierbei helfen:
<ul>
<li>bio.tools (<a href="https://bio.tools" target="_blank" >https://bio.tools</a>)</li>
<li>pypi (<a href="https://pypi.org/" target="_blank" >https://pypi.org/</a>)</li>
<li>Research Software Directory (<a href="https://research-software-directory.org/" target="_blank" >https://research-software-directory.org/</a>)</li>
<li>...</li>
</ul></help>
<text lang="de">Welche Funktion hat die neue Software, die bisherige Software nicht abdeckt? Welche verwandte Software gibt es und warum ist diese nicht geeignet?</text>
<default_text lang="de"/>
<verbose_name lang="de"/>
<help lang="fr"/>
<text lang="fr"/>
<default_text lang="fr"/>
<verbose_name lang="fr"/>
<help lang="it"/>
<text lang="it"/>
<default_text lang="it"/>
<verbose_name lang="it"/>
<help lang="es"/>
<text lang="es"/>
<default_text lang="es"/>
<verbose_name lang="es"/>
<default_option/>
<default_external_id/>
<widget_type>textarea</widget_type>
<value_type>text</value_type>
<maximum/>
<minimum/>
<step/>
<unit/>
<width/>
<optionsets/>
<conditions/>
</question>
<page dc:uri="https://rdmorganiser.github.io/terms/questions/smp/general/project-partner">
<uri_prefix>https://rdmorganiser.github.io/terms</uri_prefix>
<uri_path>smp/general/project-partner</uri_path>
<dc:comment/>
<attribute/>
<is_collection>False</is_collection>
<title lang="en">Software Project Partner(s)</title>
<help lang="en"/>
<verbose_name lang="en"/>
<title lang="de">Software-Projektpartner</title>
<help lang="de"/>
<verbose_name lang="de"/>
<title lang="fr"/>
<help lang="fr"/>
<verbose_name lang="fr"/>
<title lang="it"/>
<help lang="it"/>
<verbose_name lang="it"/>
<title lang="es"/>
<help lang="es"/>
<verbose_name lang="es"/>
<questionsets/>
<questions>
<question dc:uri="https://rdmorganiser.github.io/terms/questions/smp/general/project-partner/project-participants" order="0"/>
<question dc:uri="https://rdmorganiser.github.io/terms/questions/smp/general/project-partner/funding" order="2"/>
</questions>
<conditions>
<condition dc:uri="https://rdmorganiser.github.io/terms/conditions/application-class-1"/>
<condition dc:uri="https://rdmorganiser.github.io/terms/conditions/application-class-2"/>
<condition dc:uri="https://rdmorganiser.github.io/terms/conditions/application-class-3"/>
</conditions>
</page>
<question dc:uri="https://rdmorganiser.github.io/terms/questions/smp/general/project-partner/project-participants">
<uri_prefix>https://rdmorganiser.github.io/terms</uri_prefix>
<uri_path>smp/general/project-partner/project-participants</uri_path>
<dc:comment/>
<attribute dc:uri="https://rdmorganiser.github.io/terms/domain/project/partner"/>
<is_collection>True</is_collection>
<is_optional>False</is_optional>
<help lang="en">Please enter the name and contact details as well as institution, position as well as role in the software project, if applicable.</help>
<text lang="en">Who are the project participants that deal with this software?</text>
<default_text lang="en"/>
<verbose_name lang="en"/>
<help lang="de">Bitte geben Sie den Namen und Kontaktdaten sowie ggf. Institution und Position sowie Rolle im Software-Projekt.</help>
<text lang="de">Wer sind die Projektteilnehmer, die an dieser Software arbeiten?</text>
<default_text lang="de"/>
<verbose_name lang="de"/>
<help lang="fr"/>
<text lang="fr"/>
<default_text lang="fr"/>
<verbose_name lang="fr"/>
<help lang="it"/>
<text lang="it"/>
<default_text lang="it"/>
<verbose_name lang="it"/>
<help lang="es"/>
<text lang="es"/>
<default_text lang="es"/>
<verbose_name lang="es"/>
<default_option/>
<default_external_id/>
<widget_type>text</widget_type>
<value_type>text</value_type>
<maximum/>
<minimum/>
<step/>
<unit/>
<width/>
<optionsets/>
<conditions>
<condition dc:uri="https://rdmorganiser.github.io/terms/conditions/application-class-2"/>
<condition dc:uri="https://rdmorganiser.github.io/terms/conditions/application-class-3"/>
</conditions>
</question>
<question dc:uri="https://rdmorganiser.github.io/terms/questions/smp/general/project-partner/funding">
<uri_prefix>https://rdmorganiser.github.io/terms</uri_prefix>
<uri_path>smp/general/project-partner/funding</uri_path>
<dc:comment/>
<attribute dc:uri="https://rdmorganiser.github.io/terms/domain/project/funder"/>
<is_collection>False</is_collection>
<is_optional>False</is_optional>
<help lang="en">Here, for example, personnel or financial resources from the regular budget or already existing project funds can be mentioned.
Scientific software is becoming increasingly important as a source of knowledge. Therefore, the development of software in a scientific context is also becoming more and more relevant for funding organisations. A software management plan can be a useful basis for applying for (partial) project funding, as software is increasingly considered worthy of funding.
For further reference, we recommend these publications:
* Rand et al., Visibility of Research Software Engineers in research funding, 2022, Software Sustainability Institute Blog, <a href="https://www.software.ac.uk/blog/2022-06-20-visibility-research-software-engineers-research-funding" target="_blank">https://www.software.ac.uk/blog/2022-06-20-visibility-research-software-engineers-research-funding</a>.
* Strasser et al. (2022): 10 Simple Rules for Funding Scientific Open Source Software, <a href="https://doi.org/10.5281/ZENODO.6611500" target="_blank">https://doi.org/10.5281/zenodo.6611500</a>.</help>
<text lang="en">Is there existing (financial/personnel) resources or will there be specific funding for the software development?</text>
<default_text lang="en"/>
<verbose_name lang="en"/>
<help lang="de">Hier können beispielsweise personellen oder finanzielle Mittel aus dem regulären Haushalt oder bereits vorhandene Projektmittel erwähnt werden.
Wissenschaftliche Software gewinnt als Erkenntnisgewinn zunehmend an Bedeutung. Daher wird die Entwicklung von Software im wissenschaftlichen Kontext auch für Förderorganisationen zunehmend relevanter. Ein Software-Management-Plan kann daher eine sinnvolle Grundlage für eine Beantragung von (Teil-)Projektmitteln sein, da Software zunehmend auch als förderwürdig erachtet wird.
Als weiterführenden Hinweise empfehlen wir diese Publikationen:
* Rand et al., Visibility of Research Software Engineers in research funding, 2022, Software Sustainability Institute Blog, <a href="https://www.software.ac.uk/blog/2022-06-20-visibility-research-software-engineers-research-funding" target="_blank">https://www.software.ac.uk/blog/2022-06-20-visibility-research-software-engineers-research-funding</a>.
* Strasser et al. (2022): 10 Simple Rules for Funding Scientific Open Source Software, <a href="https://doi.org/10.5281/ZENODO.6611500" target="_blank">https://doi.org/10.5281/zenodo.6611500</a>.</help>
<text lang="de">Gibt es existierende (personellen/finanziellen) Ressourcen oder wird es eine spezielle Finanzierung für die Softwareentwicklung geben?</text>
<default_text lang="de"/>
<verbose_name lang="de"/>
<help lang="fr"/>
<text lang="fr"/>
<default_text lang="fr"/>
<verbose_name lang="fr"/>
<help lang="it"/>
<text lang="it"/>
<default_text lang="it"/>
<verbose_name lang="it"/>
<help lang="es"/>
<text lang="es"/>
<default_text lang="es"/>
<verbose_name lang="es"/>
<default_option/>
<default_external_id/>
<widget_type>textarea</widget_type>
<value_type>text</value_type>
<maximum/>
<minimum/>
<step/>
<unit/>
<width/>
<optionsets/>
<conditions>
<condition dc:uri="https://rdmorganiser.github.io/terms/conditions/application-class-1"/>
<condition dc:uri="https://rdmorganiser.github.io/terms/conditions/application-class-2"/>
<condition dc:uri="https://rdmorganiser.github.io/terms/conditions/application-class-3"/>
</conditions>
</question>
<page dc:uri="https://rdmorganiser.github.io/terms/questions/smp/general/schedule">
<uri_prefix>https://rdmorganiser.github.io/terms</uri_prefix>
<uri_path>smp/general/schedule</uri_path>
<dc:comment/>
<attribute/>
<is_collection>False</is_collection>
<title lang="en">Software Project Schedule</title>
<help lang="en"/>
<verbose_name lang="en"/>
<title lang="de">Zeitplan für Softwareprojekte</title>
<help lang="de"/>
<verbose_name lang="de"/>
<title lang="fr"/>
<help lang="fr"/>
<verbose_name lang="fr"/>
<title lang="it"/>
<help lang="it"/>
<verbose_name lang="it"/>
<title lang="es"/>
<help lang="es"/>
<verbose_name lang="es"/>
<questionsets/>
<questions>
<question dc:uri="https://rdmorganiser.github.io/terms/questions/smp/general/schedule/start-date" order="1"/>
<question dc:uri="https://rdmorganiser.github.io/terms/questions/smp/general/schedule/end-date" order="2"/>
</questions>
<conditions>
<condition dc:uri="https://rdmorganiser.github.io/terms/conditions/application-class-1"/>
<condition dc:uri="https://rdmorganiser.github.io/terms/conditions/application-class-2"/>
<condition dc:uri="https://rdmorganiser.github.io/terms/conditions/application-class-3"/>
</conditions>
</page>
<question dc:uri="https://rdmorganiser.github.io/terms/questions/smp/general/schedule/start-date">
<uri_prefix>https://rdmorganiser.github.io/terms</uri_prefix>
<uri_path>smp/general/schedule/start-date</uri_path>
<dc:comment/>
<attribute dc:uri="https://rdmorganiser.github.io/terms/domain/project/schedule/project_start"/>
<is_collection>False</is_collection>
<is_optional>False</is_optional>
<help lang="en"/>
<text lang="en">When does the software project start?</text>
<default_text lang="en"/>
<verbose_name lang="en"/>
<help lang="de"/>
<text lang="de">Wann beginnt das Softwareprojekt?</text>
<default_text lang="de"/>
<verbose_name lang="de"/>
<help lang="fr"/>
<text lang="fr"/>
<default_text lang="fr"/>
<verbose_name lang="fr"/>
<help lang="it"/>
<text lang="it"/>
<default_text lang="it"/>
<verbose_name lang="it"/>
<help lang="es"/>
<text lang="es"/>
<default_text lang="es"/>
<verbose_name lang="es"/>
<default_option/>
<default_external_id/>
<widget_type>date</widget_type>
<value_type>datetime</value_type>
<maximum/>
<minimum/>
<step/>
<unit/>
<width/>
<optionsets/>
<conditions/>
</question>
<question dc:uri="https://rdmorganiser.github.io/terms/questions/smp/general/schedule/end-date">
<uri_prefix>https://rdmorganiser.github.io/terms</uri_prefix>
<uri_path>smp/general/schedule/end-date</uri_path>
<dc:comment/>
<attribute dc:uri="https://rdmorganiser.github.io/terms/domain/project/schedule/project_end"/>
<is_collection>False</is_collection>
<is_optional>False</is_optional>
<help lang="en"/>
<text lang="en">When does the software project end?</text>
<default_text lang="en"/>
<verbose_name lang="en"/>
<help lang="de"/>
<text lang="de">Wann endet das Softwareprojekt?</text>
<default_text lang="de"/>
<verbose_name lang="de"/>
<help lang="fr"/>
<text lang="fr"/>
<default_text lang="fr"/>
<verbose_name lang="fr"/>
<help lang="it"/>
<text lang="it"/>
<default_text lang="it"/>
<verbose_name lang="it"/>
<help lang="es"/>
<text lang="es"/>
<default_text lang="es"/>
<verbose_name lang="es"/>
<default_option/>
<default_external_id/>
<widget_type>date</widget_type>
<value_type>datetime</value_type>
<maximum/>
<minimum/>
<step/>
<unit/>
<width/>
<optionsets/>
<conditions/>
</question>
<page dc:uri="https://rdmorganiser.github.io/terms/questions/smp/general/project-management">
<uri_prefix>https://rdmorganiser.github.io/terms</uri_prefix>
<uri_path>smp/general/project-management</uri_path>
<dc:comment/>
<attribute/>
<is_collection>False</is_collection>
<title lang="en">Software Project Management</title>
<help lang="en"/>
<verbose_name lang="en"/>
<title lang="de">Software-Projekt-Management</title>
<help lang="de"/>
<verbose_name lang="de"/>
<title lang="fr"/>
<help lang="fr"/>
<verbose_name lang="fr"/>
<title lang="it"/>
<help lang="it"/>
<verbose_name lang="it"/>
<title lang="es"/>
<help lang="es"/>
<verbose_name lang="es"/>
<questionsets/>
<questions>
<question dc:uri="https://rdmorganiser.github.io/terms/questions/smp/general/project-management/development-process" order="0"/>
<question dc:uri="https://rdmorganiser.github.io/terms/questions/smp/general/project-management/track-tasks" order="1"/>
<question dc:uri="https://rdmorganiser.github.io/terms/questions/smp/general/project-management/specification-sheet" order="2"/>
</questions>
<conditions>
<condition dc:uri="https://rdmorganiser.github.io/terms/conditions/application-class-1"/>
<condition dc:uri="https://rdmorganiser.github.io/terms/conditions/application-class-2"/>
<condition dc:uri="https://rdmorganiser.github.io/terms/conditions/application-class-3"/>
</conditions>
</page>
<question dc:uri="https://rdmorganiser.github.io/terms/questions/smp/general/project-management/development-process">
<uri_prefix>https://rdmorganiser.github.io/terms</uri_prefix>
<uri_path>smp/general/project-management/development-process</uri_path>
<dc:comment/>
<attribute dc:uri="https://rdmorganiser.github.io/terms/domain/smp/development-process"/>
<is_collection>False</is_collection>
<is_optional>False</is_optional>
<help lang="en">For this question, it is useful to first describe the type of project management. Examples here would be agile methods such as Scrum. But a more classical approach like e.g. the "waterfall" model is also possible. Ultimately, it is crucial that the chosen method fits the goal and is communicated to and works for the people involved.
Once a methodological approach has been established, it may be useful to define different roles for the software project. Examples would be "Developer", "Tester", "Scrum Master" etc. At the same time, it is advisable to already draft a specification document for the project with requirements, usage scenarios and other specifications. The requirements from the user's point of view should be clear so that the conception and specification process by the developers can start on this basis.
For guidance, these texts may be of interest:
* Smith, Srinivasan and Shankar (2019): Debunking the Myth That Upfront Requirements Are Infeasible for Scientific Computing Software, IEEE/ACM 14th International Workshop on Software Engineering for Science (SE4Science), pp. 33-40, <a href="https://doi.org/10.1109/SE4Science.2019.00011" target="_blank">https://doi.org/10.1109/SE4Science.2019.00011</a>.
* Marques and Milewicz (2022): User Stories in Scientific Software Development, Better Scientific Software Blog, <a href="https://bssw.io/blog_posts/user-stories-in-scientific-software-development" target="_blank">https://bssw.io/blog_posts/user-stories-in-scientific-software-development</a>.</help>
<text lang="en">Which software development process is defined? How will process roles be assigned?</text>
<default_text lang="en"/>
<verbose_name lang="en"/>
<help lang="de">Bei dieser Frage bietet es sich an, zuerst die Art des Projektmanagements zu beschreiben. Beispiele wären hier besonders die agilen Methoden, wie Scrum. Aber auch ein eher klassisches Vorgehen mit z.B. der "Wasserfall"-Methode ist möglich. Letztendlich ist es entscheidend, dass die gewählte Methode für das Ziel passt und an die beteiligten Personen kommuniziert ist sowie für diese funktioniert.
Nach der Festlegung auf ein methodisches Vorgehen kann es sinnvoll sein, verschiedene Rollen für das Software-Projekt zu definieren. Beispiele hierfür wären "Entwickler", "Tester", "Scrum Master" etc. Gleichzeitig empfiehlt es sich, für das Projekt bereits einen Leistungskatalog mit Anforderungen, Nutzungsszenarien und Spezifikationen zu entwerfen. Die Anforderungen aus Nutzendensicht sollten klar vorliegen, sodass auf dessen Grundlage dann der Konzeptions- und Spezifikationsprozess durch die Entwickler beginnen kann.
Zur Unterstützung können diese Texte interessant sein:
* Smith, Srinivasan und Shankar (2019): Debunking the Myth That Upfront Requirements Are Infeasible for Scientific Computing Software, IEEE/ACM 14th International Workshop on Software Engineering for Science (SE4Science), S. 33-40, <a href="https://doi.org/10.1109/SE4Science.2019.00011" target="_blank">https://doi.org/10.1109/SE4Science.2019.00011</a>.
* Marques und Milewicz (2022): User Stories in Scientific Software Development, Better Scientific Software Blog, <a href="https://bssw.io/blog_posts/user-stories-in-scientific-software-development" target="_blank">https://bssw.io/blog_posts/user-stories-in-scientific-software-development</a>.</help>
<text lang="de">Welcher Softwareentwicklungsprozess wird definiert? Wie werden die Prozessrollen zugewiesen?</text>
<default_text lang="de"/>
<verbose_name lang="de"/>
<help lang="fr"/>
<text lang="fr"/>
<default_text lang="fr"/>
<verbose_name lang="fr"/>
<help lang="it"/>
<text lang="it"/>
<default_text lang="it"/>
<verbose_name lang="it"/>
<help lang="es"/>
<text lang="es"/>
<default_text lang="es"/>
<verbose_name lang="es"/>
<default_option/>
<default_external_id/>
<widget_type>textarea</widget_type>
<value_type>text</value_type>
<maximum/>
<minimum/>
<step/>
<unit/>
<width/>
<optionsets/>
<conditions>
<condition dc:uri="https://rdmorganiser.github.io/terms/conditions/application-class-2"/>
<condition dc:uri="https://rdmorganiser.github.io/terms/conditions/application-class-3"/>
</conditions>
</question>
<question dc:uri="https://rdmorganiser.github.io/terms/questions/smp/general/project-management/track-tasks">
<uri_prefix>https://rdmorganiser.github.io/terms</uri_prefix>
<uri_path>smp/general/project-management/track-tasks</uri_path>
<dc:comment/>
<attribute dc:uri="https://rdmorganiser.github.io/terms/domain/smp/track-tasks"/>
<is_collection>True</is_collection>
<is_optional>False</is_optional>
<help lang="en">The development of software goes hand in hand with a high degree of complexity. In order to keep track of the diverse requirements, tasks and problems, it is advisable to organise these points in a clear structure. At the same time, this enhances the traceability of developments.
Examples of applications are stand-alone ticket systems such as Jira or Redmine. However, integrated systems can also be used just as well, such as provided in GitHub/GitLab (<a href="https://carpentries-incubator.github.io/git-novice-branch-pr/" target="_blank">see for example the Carpentries Lesson</a>). Working with a (digital) Kanban board can also support software development.</help>
<text lang="en">How do you track the different tasks and use cases?</text>
<default_text lang="en"/>
<verbose_name lang="en"/>
<help lang="de">Die Entwicklung von Software geht einher mit einer hohen Komplexität. Um die vielfältigen Anforderungen, Aufgaben und Probleme nachzuvollziehen, empfiehlt es sich diese Punkte in einer klaren Struktur zu organisieren. Gleichzeitig fördert dies die Rückverfolgbarkeit von Entwicklungen.
Beispiele für Anwendungen sind etwa eigenständige Ticket-Systeme wie Jira oder Redmine. Ebenso gut können aber auch integrierte Systeme verwendet werden, wie etwa in GitHub/GitLab bereitgestellt (<a href="https://carpentries-incubator.github.io/git-novice-branch-pr/" target="_blank">siehe etwa die Carpentries Lesson</a>). Auch das Arbeiten mit einem (digitalen) Kanban-Board kann bei der Software-Entwicklung unterstützen.</help>
<text lang="de">Wie verfolgen Sie die verschiedenen Aufgaben und Anwendungsfälle?</text>
<default_text lang="de"/>
<verbose_name lang="de"/>
<help lang="fr"/>
<text lang="fr"/>
<default_text lang="fr"/>
<verbose_name lang="fr"/>
<help lang="it"/>
<text lang="it"/>
<default_text lang="it"/>
<verbose_name lang="it"/>
<help lang="es"/>
<text lang="es"/>
<default_text lang="es"/>
<verbose_name lang="es"/>
<default_option/>
<default_external_id/>
<widget_type>text</widget_type>
<value_type>text</value_type>
<maximum/>
<minimum/>
<step/>
<unit/>
<width/>
<optionsets/>
<conditions>
<condition dc:uri="https://rdmorganiser.github.io/terms/conditions/application-class-1"/>
<condition dc:uri="https://rdmorganiser.github.io/terms/conditions/application-class-2"/>
<condition dc:uri="https://rdmorganiser.github.io/terms/conditions/application-class-3"/>
</conditions>
</question>
<question dc:uri="https://rdmorganiser.github.io/terms/questions/smp/general/project-management/specification-sheet">
<uri_prefix>https://rdmorganiser.github.io/terms</uri_prefix>
<uri_path>smp/general/project-management/specification-sheet</uri_path>
<dc:comment/>
<attribute dc:uri="https://rdmorganiser.github.io/terms/domain/smp/specification-sheet"/>
<is_collection>False</is_collection>
<is_optional>False</is_optional>
<help lang="en">The description of the requirements can be one of the cornerstones for a successful software. It is therefore advisable to invest time resources into this right from the start.</help>
<text lang="en">Will there be a specification document (briefly) outlining the most important requirements?</text>
<default_text lang="en"/>
<verbose_name lang="en"/>
<help lang="de">Die Beschreibungen der Anforderungen kann einer der zentralen Grundstein für eine gelungene Software sein. Daher empfiehlt es sich hierfür von Beginn an zeitliche Ressourcen zu investieren.</help>
<text lang="de">Wird es einen Anforderungskatalog oder ein Lastenheft geben, in dem (kurz) die wichtigsten Anforderungen skizziert werden?</text>
<default_text lang="de"/>
<verbose_name lang="de"/>
<help lang="fr"/>
<text lang="fr"/>
<default_text lang="fr"/>
<verbose_name lang="fr"/>
<help lang="it"/>
<text lang="it"/>
<default_text lang="it"/>
<verbose_name lang="it"/>
<help lang="es"/>
<text lang="es"/>
<default_text lang="es"/>
<verbose_name lang="es"/>
<default_option/>
<default_external_id/>
<widget_type>yesno</widget_type>
<value_type>boolean</value_type>
<maximum/>
<minimum/>
<step/>
<unit/>
<width/>
<optionsets/>
<conditions>
<condition dc:uri="https://rdmorganiser.github.io/terms/conditions/application-class-2"/>
<condition dc:uri="https://rdmorganiser.github.io/terms/conditions/application-class-3"/>
</conditions>
</question>
<page dc:uri="https://rdmorganiser.github.io/terms/questions/smp/general/software-requirements">
<uri_prefix>https://rdmorganiser.github.io/terms</uri_prefix>
<uri_path>smp/general/software-requirements</uri_path>
<dc:comment/>
<attribute/>
<is_collection>False</is_collection>
<title lang="en">Software Development Requirements</title>
<help lang="en"/>
<verbose_name lang="en"/>
<title lang="de">Anforderungen an die Softwareentwicklung</title>
<help lang="de"/>
<verbose_name lang="de"/>
<title lang="fr"/>
<help lang="fr"/>
<verbose_name lang="fr"/>
<title lang="it"/>
<help lang="it"/>
<verbose_name lang="it"/>
<title lang="es"/>
<help lang="es"/>
<verbose_name lang="es"/>
<questionsets/>
<questions>
<question dc:uri="https://rdmorganiser.github.io/terms/questions/smp/general/software-requirements/institutional-requirements" order="0"/>
<question dc:uri="https://rdmorganiser.github.io/terms/questions/smp/general/software-requirements/community-requirements" order="1"/>
</questions>
<conditions>
<condition dc:uri="https://rdmorganiser.github.io/terms/conditions/application-class-1"/>
<condition dc:uri="https://rdmorganiser.github.io/terms/conditions/application-class-2"/>
<condition dc:uri="https://rdmorganiser.github.io/terms/conditions/application-class-3"/>
</conditions>
</page>
<question dc:uri="https://rdmorganiser.github.io/terms/questions/smp/general/software-requirements/institutional-requirements">
<uri_prefix>https://rdmorganiser.github.io/terms</uri_prefix>
<uri_path>smp/general/software-requirements/institutional-requirements</uri_path>
<dc:comment/>
<attribute dc:uri="https://rdmorganiser.github.io/terms/domain/smp/institutional-requirements"/>
<is_collection>False</is_collection>
<is_optional>False</is_optional>
<help lang="en">For the development of software in a scientific context, the rules of good scientific practice at one's own institution or organisation apply. Software might not explicitly mentioned there. Nevertheless, these rules for scientific results can apply to the development (and sharing) of software.
At the same time, individual institutes, working groups, etc. can also impose rules on the use of software. If you are unsure about the institutional requirements that apply to you, it is best to contact your local colleagues from the Research Coordination or IT, Scientific Computing Unit, etc. They can provide you with competent support.
Below you will find a collection of examples of institutional regulations related to software:
* Budich & Funk (2022): Software Licensing and Copyright Policy for Research Software CODE @ Max Planck Institute for Meteorology, <a href="https://hdl.handle.net/21.11116/0000-000C-80B1-A" target="_blank">https://hdl.handle.net/21.11116/0000-000C-80B1-A</a>.
* European Space Agency: ESA Open Source Policy, <a href="https://essr.esa.int/esa-open-source-policy" target="_blank">https://essr.esa.int/esa-open-source-policy</a>.
* Akhmerov et al. (2021): TU Delft Research Software Policy, <a href="https://doi.org/10.5281/zenodo.4629662" target="_blank">https://doi.org/10.5281/zenodo.4629662</a>.</help>
<text lang="en">Are there institutional requirements for software development?</text>
<default_text lang="en"/>
<verbose_name lang="en"/>
<help lang="de">Für die Entwicklung von Software im wissenschaftlichen Kontext gelten die Regeln zur guten wissenschaftlichen Praxis der eigenen Institution oder Organisation. Software muss dort noch nicht explizit erwähnt. Dennoch können diese entsprechenden Regeln für wissenschaftliche Ergebnisse auch für die Entwicklung (und Veröffentlichung) von Software gelten.
Gleichzeitig können sich auch einzelne Institute, Arbeitsgruppen etc. Regeln zum Umgang mit Software auferlegen. Sollten Sie unsicher sein, inwiefern institutionelle Anforderungen für Sie zutreffen, dann kontaktieren Sie am besten Ihre lokalen Kolleg_innen von der Forschungskoordination oder der IT, Scientific Computing Unit etc. Diese können Sie dabei kompetent unterstützen.
Im Folgenden finden Sie eine Beispielsammlung für institutionelle Regelwerke mit Bezug zu Software:
* Budich & Funk (2022): Software Licensing and Copyright Policy for Research Software CODE @ Max Planck Institute for Meteorology, <a href="https://hdl.handle.net/21.11116/0000-000C-80B1-A" target="_blank">https://hdl.handle.net/21.11116/0000-000C-80B1-A</a>.
* European Space Agency: ESA Open Source Policy, <a href="https://essr.esa.int/esa-open-source-policy" target="_blank">https://essr.esa.int/esa-open-source-policy</a>.
* Akhmerov et al. (2021): TU Delft Research Software Policy, <a href="https://doi.org/10.5281/zenodo.4629662" target="_blank">https://doi.org/10.5281/zenodo.4629662</a>.</help>
<text lang="de">Gibt es institutionelle Anforderungen an die Softwareentwicklung?</text>
<default_text lang="de"/>
<verbose_name lang="de"/>
<help lang="fr"/>
<text lang="fr"/>
<default_text lang="fr"/>
<verbose_name lang="fr"/>
<help lang="it"/>
<text lang="it"/>
<default_text lang="it"/>
<verbose_name lang="it"/>
<help lang="es"/>
<text lang="es"/>
<default_text lang="es"/>
<verbose_name lang="es"/>
<default_option/>
<default_external_id/>
<widget_type>textarea</widget_type>
<value_type>text</value_type>
<maximum/>
<minimum/>
<step/>
<unit/>
<width/>
<optionsets/>
<conditions/>
</question>
<question dc:uri="https://rdmorganiser.github.io/terms/questions/smp/general/software-requirements/community-requirements">
<uri_prefix>https://rdmorganiser.github.io/terms</uri_prefix>
<uri_path>smp/general/software-requirements/community-requirements</uri_path>
<dc:comment/>
<attribute dc:uri="https://rdmorganiser.github.io/terms/domain/smp/community-requirements"/>
<is_collection>False</is_collection>
<is_optional>False</is_optional>
<help lang="en">In addition to institutional requirements, there may also be other conditions or communities that need to be taken into account when developing software in a scientific context. For example, if the software is developed in a third-party project, then the requirements of the funding body are binding. Likewise, there may be various agreements in one's own community that need to be taken into account in software development.
It is advisable to familiarise yourself with the FAIR Principles for Research Software (<a href="https://doi.org/10.15497/RDA00068" target="_blank">FAIR4RS</a>) at an early stage. For example, this question about requirement for software is required in <a href="https://doi.org/10.15497/RDA00068" target="_blank">FAIR4RS</a> I1 and R3. At the same time, orientation towards the <a href="https://doi.org/10.15497/RDA00068" target="_blank">FAIR4RS</a> principles can significantly increase the quality and acceptance of the software. An interactive guide to FAIR software can be found here: <a href="https://fair-software.nl" target="_blank">https://fair-software.nl</a>.</help>
<text lang="en">Are there requirements regarding the software development form other parties?</text>
<default_text lang="en"/>
<verbose_name lang="en"/>
<help lang="de">Neben institutionellen Anforderungen können ebenso weitere Bedingungen oder Communities existieren, die es bei der Entwicklung von Software im wissenschaftlichen Kontext zu beachten gilt. Wenn beispielsweise die Software in einem Drittmittelprojekt entwickelt wird, dann sind die Vorgaben des Mittelgebers bindend. Ebenso können verschiedene Vereinbarungen in der eigenen Fächergruppe bestehen, die es bei der Software-Entwicklung zu berücksichtigen gilt.
Parallel dazu ist es empfehlenswert, sich mit den FAIR Principles for Research Software (<a href="https://doi.org/10.15497/RDA00068" target="_blank">FAIR4RS</a>) schon frühzeitig vertraut zu machen. So wird beispielsweise diese Anforderung in <a href="https://doi.org/10.15497/RDA00068" target="_blank">FAIR4RS</a> I1 und R3 gefordert. Die Orientierung an den <a href="https://doi.org/10.15497/RDA00068" target="_blank">FAIR4RS</a>-Prinzipien kann gleichzeitig die Qualität und Akzeptanz der Software deutlich steigern. Eine interaktive Hilfestellung zu FAIR Software findet sich hier: <a href="https://fair-software.nl" target="_blank">https://fair-software.nl</a>.</help>
<text lang="de">Gibt es Anforderungen bezüglich der Softwareentwicklung von externer Seite?</text>
<default_text lang="de"/>
<verbose_name lang="de"/>
<help lang="fr"/>
<text lang="fr"/>
<default_text lang="fr"/>
<verbose_name lang="fr"/>
<help lang="it"/>
<text lang="it"/>
<default_text lang="it"/>
<verbose_name lang="it"/>
<help lang="es"/>
<text lang="es"/>
<default_text lang="es"/>
<verbose_name lang="es"/>
<default_option/>
<default_external_id/>
<widget_type>textarea</widget_type>
<value_type>text</value_type>
<maximum/>
<minimum/>
<step/>
<unit/>
<width/>
<optionsets/>
<conditions/>
</question>
<section dc:uri="https://rdmorganiser.github.io/terms/questions/smp/technical">
<uri_prefix>https://rdmorganiser.github.io/terms</uri_prefix>
<uri_path>smp/technical</uri_path>
<dc:comment/>
<title lang="en">Technical</title>
<title lang="de">Technische Informationen</title>
<title lang="fr"/>
<title lang="it"/>
<title lang="es"/>
<pages>
<page dc:uri="https://rdmorganiser.github.io/terms/questions/smp/technical/code" order="0"/>
<page dc:uri="https://rdmorganiser.github.io/terms/questions/smp/technical/components" order="1"/>
<page dc:uri="https://rdmorganiser.github.io/terms/questions/smp/technical/Infrastructure" order="2"/>
<page dc:uri="https://rdmorganiser.github.io/terms/questions/smp/technical/preservation" order="3"/>
<page dc:uri="https://rdmorganiser.github.io/terms/questions/smp/technical/security" order="4"/>
</pages>
</section>
<page dc:uri="https://rdmorganiser.github.io/terms/questions/smp/technical/code">
<uri_prefix>https://rdmorganiser.github.io/terms</uri_prefix>
<uri_path>smp/technical/code</uri_path>
<dc:comment/>
<attribute/>
<is_collection>False</is_collection>
<title lang="en">Code</title>
<help lang="en"/>
<verbose_name lang="en"/>
<title lang="de">Code</title>
<help lang="de"/>
<verbose_name lang="de"/>
<title lang="fr"/>
<help lang="fr"/>
<verbose_name lang="fr"/>
<title lang="it"/>
<help lang="it"/>
<verbose_name lang="it"/>
<title lang="es"/>
<help lang="es"/>
<verbose_name lang="es"/>
<questionsets/>
<questions>
<question dc:uri="https://rdmorganiser.github.io/terms/questions/smp/technical/code/language" order="0"/>
<question dc:uri="https://rdmorganiser.github.io/terms/questions/smp/technical/code/versioning" order="1"/>
</questions>
<conditions/>
</page>
<question dc:uri="https://rdmorganiser.github.io/terms/questions/smp/technical/code/language">
<uri_prefix>https://rdmorganiser.github.io/terms</uri_prefix>
<uri_path>smp/technical/code/language</uri_path>
<dc:comment/>
<attribute dc:uri="https://rdmorganiser.github.io/terms/domain/smp/language"/>
<is_collection>True</is_collection>
<is_optional>False</is_optional>
<help lang="en">The software languages go hand in hand with different methods, focuses and required skill levels. Here you can document which language(s) you choose and why. Examples of software languages can be Java, Python, R, etc.
At this point it is also useful to document whether technical standards are relevant for the development of software. Examples include <a href="https://www.iso.org/standard/38421.html" target="_blank">IEC Standard 62304</a> for software in medical applications, or <a href="https://ecss.nl/standard/ecss-e-st-40c-software-general-requirements/" target="_blank">ECSS-E-ST-40C</a> for software in space applications, or <a href="https://www.dicomstandard.org" target="_blank">DICOM</a> for the exchange of medical image data.</help>
<text lang="en">Which programming language(s) do you plan to use?</text>
<default_text lang="en"/>
<verbose_name lang="en"/>
<help lang="de">Die Softwaresprachen gehen einher mit unterschiedlichen Methoden, Schwerpunkten und benötigten Fähigkeitsgraden. Hier können Sie dokumentieren, für welche Sprache(n) Sie sich entscheiden und weshalb. Beispiele für Softwaresprachen während Java, Python, R, usw.
An dieser Stelle bietet es sich zusätzlich an, zu dokumentieren, ob technische Standards für die Entwicklung von Software relevant sind. Beispiele hierfür sind etwa der <a href="https://www.iso.org/standard/38421.html" target="_blank">IEC Standard 62304</a> für Software bei medizinischen Anwendungen, oder <a href="https://ecss.nl/standard/ecss-e-st-40c-software-general-requirements/" target="_blank">ECSS-E-ST-40C</a> bei Software für Anwendungen im Weltraum oder <a href="https://www.dicomstandard.org" target="_blank">DICOM</a> für den Austausch von medizinischen Bilddaten.</help>
<text lang="de">Welche Programmiersprache(n) planen Sie zu verwenden?</text>
<default_text lang="de"/>
<verbose_name lang="de"/>
<help lang="fr"/>
<text lang="fr"/>
<default_text lang="fr"/>
<verbose_name lang="fr"/>
<help lang="it"/>
<text lang="it"/>
<default_text lang="it"/>
<verbose_name lang="it"/>
<help lang="es"/>
<text lang="es"/>
<default_text lang="es"/>
<verbose_name lang="es"/>
<default_option/>
<default_external_id/>
<widget_type>textarea</widget_type>
<value_type>text</value_type>
<maximum/>
<minimum/>
<step/>
<unit/>