HeFDI Data Talk: NFDIxCS. National Research Data Infrastructure for and with Computer Science

HeFDI Data Talk Abstract: In this presentation, abrief introduction of research data management in Computer Science as well as objectives and offers of the NFDIxCS consortium is given.The emphasis is on an encompassing solution which includes not only the "data" in atraditional sense but the related software components and systems for the research data as well. About the HeFDI Data Talks: The HeFDI Data Talks are abi-weekly open information and discussion event focused on data management in the context of science, in which relevant NFDI consortia as well as research data management services present themselves.The series discusses current topics and presents numerous – including local and regional –tools and services.The HeFDI Data Talks are an offer of the HeFDI Initiative (Landesinitiative HeFDI), which is funded by the Hessian Ministry of Higher Education, Research, Science and the Arts (HMWK). DOI link:https://doi.org/10.5281/zenodo.14800820;License information:Creative Commons Attribution 4.0 International (CC BY 4.0) Date Topic Presenter(s) 13 December 2024 NFDIxCS. National Research Data Infrastructure for and with Computer Science Prof. Michael Goedicke (University of Duisburg-Essen / paluno) gefördert durch National Research Data Infrastructure for and with Computer Science https://nfdixcs.org/ as part of https://nfdi.de Overview presented by Michael Goedicke Funding information DFG NFDI 52/1 Projektno. 501930651 NFDI National Infrastructure for Research Data Management •Nfdi.de (NFDI association, www.nfdi.de) , see also www.dfg.de/nfdi •26 Consortia àdiscipline-oriented approach „bottom up“ plus BASE4NFDI •Each consortium has ca. 10-20 Partners plus so-called participants •Current budget ≈ 10-15 M€ for 5 years, “kein Blech” i.e. no hardware but investment in brains aka people •Two phases of 5 years each •International outreach mandatory for each consortium plus NFDI association is mandated member (i.e. representative) of Germany in the European Open Science Cloud (EOSC) •FAIR = Findable, Accessible, Interoperable, Reusable Challenges in Research Data Management in Computer Science •Context … Execution, Experiment •Software •Diverse Types, Meta Data 3 409-01 Theoretical Computer Science 409-02 Software Engineering / Programming Languages 409-03 Security & Dependability 409-04 Operating, Communication,Dat abase & Distributed Systems 409-05 Visual Computing 409-06 Business Information Systems 409-07 Computer Architecture & Embedded Systems 409-08 Massively Parallel & DataIntensive Systems 409-09 Artificial Intelligence & Machine Learning 409-10 Interactive Systems 4 Scientific Evidence Publication Research Data No Data without Software … what is about Hardware? Two Central Concepts (1) RDMC •Research Data Management Container c.f. FAIR Data Objects •Strong Link between the actual research data, context information incl. meta data, execution environment & SBOMs 5 Access Control Workflows Filter & Transformation Context Software Data Two Central Concepts (2) Participation of the CS-Community in NFDIxCS •Sub disciplines of CS get involved to define via community processes •Meta data standards incl. context information, execution environment •Quality criteria for RDMC curation •Representation in the General Assembly •Internationalisation •IFIP Publication Committee •Informatics Europe Open Science Initiative and other national associations •Tentative ACM / IEEE CS 6 RDMC as Time Capsule c.f. FAIR Data Object •Data àprocessed in different forms … SW needed •Bringing Data back to life àExecution of SW •Operating system, frameworks, libraries … … need to be fixed and optionally referenced … Software Heritage Foundation Access Control Workflows Filter & Transformation Context Software Data RDMC –Central NFDIxCS Concept Architecture –Implementation –Operation •Architecture: sustainable result •Implementation(s) … series of prototypes … reference implementation … purpose-built versions •Reusable Execution Environment •Technology change … Architecture! NFDIxCS Consortium Thank you for your attention 15NFDIxCS.org Thank you for your attention … questions ... https://www.nfdixcs.org 16 Part Two •Discussion ... 17 Towards Defining Lifecycles and Categories of Research Software Yo Yehudi1, Mikaela Cashman2, Michael Felderer3, Michael Goedicke4, Wilhelm Hasselbring5, Daniel S. Katz6, Frank Löffler7, Sebastian Müller8, Bernhard Rumpe9 1OLS, Manchester, UK; 2Lawrence Berkeley National Laboratory, USA; 3German Aerospace Center (DLR) & University of Cologne, Germany; 4University of Duisburg-Essen / paluno and NFDIxCS, Germany; 5Kiel University, Germany; 6University of Illinois Urbana-Champaign, USA; 7Friedrich-Schiller-University Jena, Jena, Germany; 8Humboldt-Universität zu Berlin, Germany; 9RWTH Aachen University, Germany Target Audiences / Motivation Funders Who should we fund? RSEs How do I explain/justify my work to my {institute, boss, team…} Users Should we use the software? Developers Should I contribute? Software Engineering Researchers (SERs) How do we consistently understand and improve research software? Domain PIs How can I follow team progress? Research Software Category Readiness TRL 1 - Basic Principles Observed TRL 2 - Technology Concept Formulated TRL 3 - Experimental Proof of Concept TRL 4 - Technology Validated in Lab TRL 5 - Technology Validated in Relevant Environment TRL 6 - Technology Demonstrated in Relevant Environment TRL 7 - System Prototype Demonstration in Operational Environment TRL 8 - System complete and Qualified TRL 9 - Actual System Proven in Operational Environment Active Development Stage Initial Growth Evolution New Features Maintenance Blocked Reduced Activity Finished EOL Support Dormant Fallow Orphaned sub role See also https://doi.org/10.48550/arXiv.2404.14364 (previous, preliminary version) Role in Research Modeling, Simulation and Data Analytics Modeling and Simulation Numerical Modeling Agent-based Modeling Data Analytics Integrative Analysis Technology Research Software Research Infrastructure Software Control and Monitoring Software Data Collection Pipelines / Workflows Laboratory Notebooks Data Management Software Management Collaboration Software Software Analytics Scientific Visualization Data Method Observation Data Simulation Data Statistical Analysis Machine Learning Embedded Web-Based Native Static Dynamic Evolution Repository Mining Data Assimilation Decision Analysis This poster was developed during the Dagstuhl seminar 24161 “Research Software Engineering: Bridging Knowledge Gaps”, https://www.dagstuhl.de/24161 Research Software CategoryResearch Software Lifecycle Leave Feedback Here! Special thanks to Heidi Seibold for the persona graphics Dissemination Open Source Closed Source Software as a Service Developer Individual Researcher Local Research Group Project group Community Contractor Project in use, but declining. Graceful plans for support until end of life EOL Support Community desires evolution, will resume if resources allow Dormant: Orphaned/Abandoned Few contributors, few users. Possibly unfunded. Initial Stage More contributors, increased funding, paid staff, leadership > 1. Growth No development or maintenance planned Finished Evolution desired by project leadership, will resume if resources allow Dormant: Fallow New resources enable evolution Sufficient resources New features Maintenance Evolution Reduced activity Sunset Reactivation Active development Resurrection Reactivation Sunset Challenge event Yes No Unable to proceed Blocked *Additional categories not depicted: Criticality, Maturity Handled successfully? Does your software fall into a defined category? What category definition is missing? Can you trace your projects through the lifecycle diagram? Do you hit all the stages? Is something missing or unclear? Would this provide benefit to your team/project?