NIH | National Cancer Institute | NCI Wiki  

WIKI MAINTENANCE NOTICE

Please be advised that NCI Wiki will be will be undergoing maintenance on Monday, June 24th between 1000 ET and 1100 ET.
Wiki will remain available, but users may experience screen refreshes or HTTP 502 errors during the maintenance period. If you encounter these errors, wait 1-2 minutes, then refresh your page.

If you have any questions or concerns, please contact the CBIIT Atlassian Management Team.

Date

Attendees



Goals

  • We need to start planning the architectural review deliverable for PDC.  Let’s start with laying out what we want to cover (identify sections) and then make assignments for each of those sections.  I can handle coordinating the overall document.  This will be our initial planning meeting.

Discussion items

TimeItemWhoNotes

BackgroundJohnPDC now under FNL control.  Like Gen3, need to do evaluation and provide report to NCI at a high level how it's architected and areas we think appropriate for change.  Bear in mind it has to be part of CRDC and work with DCF components.  No preconceived notions of what this report should look like, however, as we look at things and identify problems, Bento might be an option, but not in the official report.  Could craft presentation for Henry/Tony Kerlavage.  Report should include not just how it's architected but how they're doing it (e.g., no automated QA).  What's the data of the QA as it passed through the pipeline.  Engineering viewpoint.  Design reviewed needs to be discussed if it should be included.  Are there best practices that can be adopted that affect engineering robustness, pricing, performance, or design?  Our role is to help NCI get the best value, not to take the project from ESAC necessarily.

Aspects/Sections

Architecture (document and highlight suggestions for best practices)

Introduction/Overview

  1. SDLC (participants: scrums, sprint planning, etc.) - should include Federal Lead? (Matt)
  2. Dev/Ops (Amit)
  3. UI (code being used) (Amit)
  4. QA (Barry)
    1. Load testing
    2. Automation (looked at Katalon, but didn't adopt)
  5. Integration with CRDC (Amit)
  6. Security (Matt)
    1. ATO
    2. Processes
  7. Data (Mark)
    1. Data Processes (including: ingestion, transferring between stages, etc.) (Mark)

Conclusion/Recommendations

  1. Migration to CloudOne?

Out of Scope for now

UI Design:

  • User Feedback
  • Usage metrics
  • Community penetration
  • Usability

CPTAC Assay Data Portal Review


Schedule

1st Draft: July 8, 2020

Draft Review Meeting: July 15, 2020

Final Draft: July 30, 2020

Action items

  •