REVIEW-4: SDIACT-118 Improve Software and Service Information Management - Joint SD&I Test and Operations Readiness Review

Static Software and Services Description Information Management will provide XSEDE SP and User Services staff the ability to manage static software and service descriptive information available to users using the User Portal software search interface.

• Add documentation for SP administrators (Shava) - Done
• Who will own and maintain quality of information and resolve conflicts (Tabitha) – recommend User Services and will discuss with them.

Materials for SDIACT-118 are linked below and have been checked into SVN at:

https://software.xsede.org/svn/sdi/activities/sdiact-118/trunk/

Software

• This package delivers pages in the XUP (test portal) at https://xup3.xsede.org:8443/web/staff/software-admin/

Documentation

• Introduction
  • Please see description at https://xup3.xsede.org:8443/web/staff/software-admin/
• Design/Security overview
  • Security and General Design Description
• Installation guide
  • n/a
• Deployment Plan
  • SDIACT-118 Deployment Plan
• User guide
  • Please see description at https://xup3.xsede.org:8443/web/staff/software-admin/
• Defect, issue, and risk reporting
  • See SDIACT-118 test plan below
• Acceptance test plan
  • Test Plan
• Testing resources
  • XUP test server
  • Browsers: Firefox, Chrome, and Safari

Package information: All software packages (e.g., server and client packages) for this CI are listed.

Documentation and Installation instructions: The deployment plan for this CI on XSEDE is clearly described as well as the installation instructions and any XSEDE specific configuration instructions.

Test environment and facilities: The test environment needed to adequately to validate this component is described. Should indicate also whether testing can be performed within a VM and if not, the reasons for it.

Assumptions: Lists any assumptions needed before testing can begin (e.g., accounts needed).

Test procedures, cases, and scenarios: Lists the tests that should be run or an associated test suite and expected performance metrics if applicable.

Defect, issue, and risk reporting: Deployment plans should include defect and issue reporting information. The testing plan could reference that same information from the deployment plan, or provide alternate information if defects and issues need to be reported differently during testing. Risks, as well as defects and issues, should be part of the testing report.