Conduct a research study evaluating the scope of maintenance needs by one research discipline or field Determine the order of magnitude of the maintenance backlog for research software #34
Potential Activity Scope
This would involve: (1) Initially conducting a survey within a discipline to identify commonly used software, then (2) gathering input from the developers associated with that software to ask about maintainance backlogs. Delivering this project would involve specific steps, such as the following:
Designing the Survey: A survey would need to be designed to identify the commonly used software within the chosen discipline. This would involve defining the target population, crafting relevant questions, and determining the appropriate methodology for administering the survey.
Conducting the Survey: The survey would be conducted within the selected discipline, targeting researchers, practitioners, and other stakeholders who are likely to have insights into the commonly used software. This could involve online distribution, interviews, or other methods, depending on the context.
Analyzing Survey Results: The results of the survey would be analyzed to identify the key software tools and applications that are commonly used within the discipline. This would provide a foundational understanding of the software landscape within that field.
Identifying Developers: Once the commonly used software has been identified, efforts would be made to gather input from the developers associated with that software. This could involve reaching out directly to developers, utilizing professional networks, or leveraging existing relationships within the community.
Inquiring About Maintenance Backlogs: Developers would be asked about maintenance backlogs for the identified software. This could involve structured interviews, questionnaires, or other methods to gather detailed information about the nature, extent, and implications of maintenance needs.
Analyzing Maintenance Needs: The information gathered from developers would be analyzed to determine the order of magnitude of the maintenance backlog. This would involve quantitative analysis, as well as qualitative insights to understand the underlying factors and dynamics that contribute to maintenance needs.
Interpreting Findings: The findings would be interpreted in the context of the broader research discipline or field, considering the potential impact of maintenance backlogs on research quality, efficiency, innovation, and other key factors.
Disseminating Results: The results of the study would be disseminated to relevant stakeholders, including researchers, developers, funders, policymakers, and others who may have an interest or influence in addressing maintenance needs.
Documentation and Reporting: Finally, the entire process, findings, and recommendations would be documented in a report.
Potential Objectives
To select a specific research discipline or field that would benefit from an evaluation of software maintenance needs.
To design and conduct a survey within the chosen discipline to identify commonly used software, ensuring that the survey reaches a representative sample of the community.
To analyze the survey results to pinpoint key software tools and applications that are integral to the discipline.
To identify and engage with developers associated with the identified software, gathering their insights and input regarding maintenance backlogs.
To inquire about and analyze the maintenance needs for the identified software, determining the order of magnitude of the maintenance backlog.
To interpret the findings in the context of the broader research discipline or field, understanding the potential impact and implications of maintenance backlogs.
To disseminate the results to relevant stakeholders, fostering awareness, understanding, and action regarding maintenance needs.
To consider and recommend follow-up actions that could address the identified maintenance backlogs, aligning with the interests, needs, and capacities of the discipline or field.
To document the process, findings, and recommendations in a report, providing a resource for future reference and decision-making.
Targeted Impacts
To enhance awareness and understanding of the scope and significance of maintenance needs within the chosen research discipline or field, contributing to informed decision-making and prioritization.
To foster collaboration and communication between researchers, developers, funders, and other stakeholders, building a shared commitment to addressing maintenance needs.
To provide actionable insights and recommendations that can guide efforts to reduce maintenance backlogs, enhancing the quality, efficiency, and innovation of research software within the discipline.
This potential activity was curated as part of "Charting the Course: Policy and Planning for Sustainable Research Software," a Sloan Foundation-funded project within URSSI dedicated to supporting the future of research software through evidence-informed policy work (Project contacts are: @danielskatz and @dr-eric-jensen). If you are interested in working on this, please add a comment.
Potential Activity Scope This would involve: (1) Initially conducting a survey within a discipline to identify commonly used software, then (2) gathering input from the developers associated with that software to ask about maintainance backlogs. Delivering this project would involve specific steps, such as the following:
Potential Objectives
Targeted Impacts
This potential activity was curated as part of "Charting the Course: Policy and Planning for Sustainable Research Software," a Sloan Foundation-funded project within URSSI dedicated to supporting the future of research software through evidence-informed policy work (Project contacts are: @danielskatz and @dr-eric-jensen). If you are interested in working on this, please add a comment.