NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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?

Aspects/Sections

Architecture (document and highlight suggestions for best practices)

Introduction

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

Conclusion/Recommendations

  1. Migration to CloudOne?

Out of Scope for now

UI Design:

  • User Feedback
  • Usage metrics
  • Community penetration
  • Usability

Action items

  •