The Requirements Analysis and Capability Delivery (RACD) team prepares and supports software and services that: 1) enable user access to and use of XSEDE federated infrastructure, and 2) enable infrastructure and service providers to federate with XSEDE. Starting from XSEDE prioritized user requirements (use cases) RACD coordinates the engineering work necessary to integrate software and services into production at SPs and campuses, as XSEDE central services, as external vendor services, or on user personal systems. RACD uses engineering best practices and tools, works with external vendors and software partners to minimize integration cost to XSEDE, and aims to maximize ROI to XSEDE and the NSF.
RACD Metric | Target | Subgoal |
---|---|---|
Number of capability delivery plans (CDPs) prepared for UREP prioritization | 12/yr | Advance - Create an open and evolving e-infrastructure |
Number of CI integration assistance engagements | 6/yr | Advance - Create an open and evolving e-infrastructure |
Number of significant fixes and enhancements to production components (a) | 16/yr | Advance - Create an open and evolving e-infrastructure |
Number of new components instrumented and tracked for usage and ROI analysis | 4/yr | Advance - Create an open and evolving e-infrastructure |
Average satisfaction rating for RACD services (b) | 4 of 5/yr | Advance - Create an open and evolving e-infrastructure |
Average time from support request to solution | <30 days | Advance - Create an open and evolving e-infrastructure |
RACD Appendix Metric | Target | Subgoal |
---|---|---|
Number of maintenance releases and upgrades delivered of service provider software (a) | 4/yr | Advance - Create an open and evolving e-infrastructure |
Number of fixes and enhancements to centrally operated services (a) | 12/yr | Advance - Create an open and evolving e-infrastructure |
User rating of components delivered in production (b) | 4 of 5/yr | Advance - Create an open and evolving e-infrastructure |
Operator rating of components delivered for production deployment (b) | 4 of 5/yr | Advance - Create an open and evolving e-infrastructure |
Software/service provider rating of our integration assistance (b) | 4 of 5/yr | Advance - Create an open and evolving e-infrastructure |
Name | Institution | Position |
---|---|---|
JP Navarro | Univ. of Chicago/Argonne Nat. Lab. | Manager, Requirements Analysis Engineer, and Integration Engineer |
Shava Smallen | SDSC | Deputy Manager, Evaluation and Testing Coordinator |
Kate Kaya | SDSC | Management Support |
Lee Liming | Univ. of Chicago | Requirements Analysis Lead |
Jim Basney | NCSA | Lead Security Designer and Requirements Analysis Engineer |
Eric Blau | Univ. of Chicago/Argonne Nat. Lab. | Integration & Information Services Engineer |
Rob Light | PSC | Information Services Engineer |
Galen Arnold | NCSA | Security Engineer and Evaluation & Testing Engineer |
Choonhan Youn | SDSC | Evaluation & Testing Engineer |
Christopher Irving | SDSC | Evaluation & Testing Engineer |
Susan Litzinger | PSC | Evaluation & Testing Engineer |
Derek Simmel | PSC | Evaluation & Testing Engineer |
Peter Enstrom | NCSA | Evaluation & Testing Engineer |
Description | Catalog | Source | Published |
---|---|---|---|
Use Cases | Registry ![]() | Google Drive ![]() | Ideals ![]() |
Capability Delivery Plans | JIRA ![]() | Google Drive ![]() | |
Activities | JIRA ![]() | ||
Reviews | View ![]() | ||
Available Components | Registry | Development Repo ![]() Production Repo ![]() | |
Deployed Components | Registry ![]() | ||
Bugs and Feature Requests | JIRA ![]() | ||
Tickets | Ticket System ![]() |