Child pages
  • WBS 2.3.2 Requirements Analysis and Planning 2017-03-30 Meeting
Skip to end of metadata
Go to start of metadata

Date

Agenda

  1. Use Cases and CDPs
  2. Activities
  3. PY7 Plan

1. Use Cases and CDPs

Use Case Development

Group Management
  • Lee Liming prepared a Requirements Summary of discussions with various XSEDE groups.
  • Jim Basney and JP Navarro provided Requirements Summary feedback.
  • Next Lee Liming will propose use cases and prepare them with Jim and JP help if desired.
  • We will then circulate the Requirements Summary and Use Cases to the groups we spoke to for their review.
  • We will then prepare CDPs for those use cases we will present to the UREP
  • We will then present the Use Cases and CDPs to the UREP sometime this summer

Use Cases that need CDPs

CI-01 Access XSEDE system details

CI-02 Manually update XSEDE system details 

CI-03 Continuously maintain service availability and status details

IDM-11 Use an XSEDE identity for InCommon authentication

 

SGW-04 Data movement between gateway users' desktop/laptops and XSEDE resources

 

  • Lee Liming to follow-up with Marlon on whether capability documentation exists; adjust CDP as necessary

SPI-05 Active account information

  • Jim Basney to prepare CDP by next UREP/Spring  XCI-40 - Getting issue details... STATUS  

SPI-06 Emergency account suspension 

  • Jim Basney to prepare CDP by next UREP/Spring  XCI-39 - Getting issue details... STATUS

Use Case Backlog

GRP-01 Researcher manages membership of a project group

  • Waiting for other Group use cases
  • Future CDP prep  XCI-42 - Getting issue details... STATUS

IAAS-08 Dynamically acquire and manage hosted computer systems and storage volumes  

  • Defer CDP until it's clear that this is needed

IAAS-09 Reliably acquire and manage hosted computer systems and/or storage volumes 

  • Defer CDP until it's clear that this is needed

IDM-03 Change an XSEDE user profile

  • Waiting for 2-factor vendor decision
  • Future CDP prep  XCI-47 - Getting issue details... STATUS

IDM-12 Single sign-on for XSEDE OpenStack resources

  • We don't think there's any demand for this yet
  • Future CDP prep  XCI-48 - Getting issue details... STATUS

IDM-13 Authenticate to XSEDE OpenStack APIs

  • We don't think there's any demand for this yet
  • Future CDP prep  XCI-49 - Getting issue details... STATUS

2. Current Activities

CB-08 Use XSEDE SSO with campus login servers

  • Jim Basney finished CDP XCI-33 - Getting issue details... STATUS
  • Activity Launched  XCI-36 - Getting issue details... STATUS
  • Remove from future planning agenda

SPI-01 Resource Integration Console

  • JP Navarro finished the CDP
  • Capability fully delivered in the CSR
  • JP Navarro deliver testing plan to Shava
  • JP Navarro notify originators that use case has been delivered after testing passes

SPI-03 View all resource information

  • JP Navarro finished the CDP
  • Capability fully delivered in the CSR
  • JP Navarro deliver testing plan to Shava
  • JP Navarro notify originators that use case has been delivered after testing passes

SPI-04 Access resource information from an application

  • JP Navarro finished the CDP
  • Capability fully delivered in the CSR
  • JP Navarro deliver testing plan to Shava
  • JP Navarro notify originators that use case has been delivered after testing passes

DA-01 Analytics resources and information

DA-02 Data preparation

  • JP Navarro identified non-XCI project participants
  • JP Navarro prepare draft activity plan in JIRA and/or Google showing major tasks, deliverables, and contributions from XCI and non-XCI groups to share with all contributors; once contributors agree launch activities

SGW-01 Science Gateways user authentication and identity management

  • What about CDP gap: XCI-­31 Provide a science gateway developer's dashboard?

 

3. PY7 Plans

Overview:

  • Our RACD PY7 Plan is due by .
  • A single document includes the PY7 Plan (green highlight) and PY6 Annual Report (yellow highlight).
  • We don't need to work on the annual report yet.
  • RACD Plan and Report (a pruned copy of the PY7 Plan Template); XCI starts on page 21.

Guidance:

  • Provide RY2 Metrics Targets in the Metrics tables, AND a succinct narrative addressing your PY7 Activities

  • Discuss metric targets first. If your targets have not changed from PY6 to PY7, state this.
  • For new/adjusted targets, please explain why you chose the target you did.
  • Next, discuss metrics added/removed for PY7. Give explanations as to why you have either added or removed metrics.
  • Finally, discuss activities. Refer to your PY7 SOW for the list of activities you have committed to for PY7 and refer to your section of the PY6 plan for examples of what to discuss about those activities

Style:

  • The report should be consistent in writing style and level of detail. 

  • The report should be written in first person where possible. 
  • Section contents should be written in an essay type format (not sub-headings by L3 or metrics).
  • Do not use contractions (unless quoting).
  • Italicize names of systems.
  • In the L1/L2 highlights, (1) avoid repeating text and (2) forward referencing of metrics is acceptable.
  • Reporting period v. quarter: Now that we have transitioned our reports to Interim Project Reports, we need to align our language accordingly. As such, please refer to the period as “reporting period” as opposed “quarter” in text.

References:


Attendees

Action items

  • Lee Liming record UREP priorities in CDP listed activities and advance to Prioritized state\
  • Create XCI activities for all CDP preparation tasks and to use Kanban to track requirements analysis and capability delivery tasks.
  • JP NavarroShava Smallen Incorporate Agile testing into Agile activities