Use Cases
These are not formal use cases; however, they do represent different stakeholder discussions specific to software evaluation.
Stakeholder: Manager, Principal Investigator (manager in practice)
Statement: As a manager, I’m interested in using the rubric/progression as a learning tool to help improve the development practices in my research group.
Stakeholder: Principal Investigator
Statement: As a PI, I would like a tool to assess our progress and ensure we’re meeting our funder’s expectations for a software project based on the readiness level stated in the original proposal and as defined by the funder.
Stakeholder: Science Software Developer/Researcher Who Codes
Statement: As a science software developer, I’m interested in using the recommended practices to improve my own workflow and skillsets.
Stakeholder: Developer
Statement: As a developer, I would like community-supported guidelines to support requests to change our current dev team practices.
Stakeholder: Grad Student, Post-Doc or other Researcher interested in education/training beyond introductory workshops
Statement: I’ve taken the introductory courses and want to continue to improve my skills but don’t know good next steps. I’d like guidance on next steps given my skillset.