TEAM 4 TRR PRESENTATION

Outline Operational Concept Overview Demo Support Plan Transition Objective, Strategy, and Plan Project Manager: Baker

Operation Concept Overview

OPERATION CONCEPT OVERVIEW Holistic Office has a goal of 5 core features Tasks Patients Products Dashboard Users Over the course of this presentation we will be updating on the status of each of these and explaining the path forward Project Manager: Baker

THE GOOD We are production ready for the following two features Tasks Dashboard Fully functional End to end Ready for live testing Project Manager: Baker

THE OK We are in the middle of development for the following two features Patients Users Basically functional Important features missing Users is end to end for log in Patients is nearly end to end Project Manager: Baker

THE BAD We are not ready for the following one feature Products Not really started Not enough time Project Manager: Baker

Requirements Metrics Requirements Tested and Met (3) WC_4811 As a developer, I need to protect the app against SQL Injections and Cross Site Scripting WC_4743 As a user, I am able to create new patient records WC_4692 As a user, I can generate tasks with varying levels of importance. Requirements to Be Tested Next Development Cycle, Post-Delivery (3) WC_4815 As a user, I can import vendor information with a CSV file WC_4740 As a doctor, I can match patients to products WC_4720 As a user, I can access information such as articles or videos that will train me to use the system.

Requirements Metrics Requirements Descoped (10) WC_4812 As a user, I can trust the application securely handles personal information (e.g., full names, social security numbers, credit card information.) WC_4739 As a user, I can have reports automatically generated on a schedule WC_4738 As a user, I can track customers who have been referred WC_4744 As a doctor, I am able to view a report of product purchases WC_4719 As a doctor, my patients and my data will be preserved for a specific amount of time after the free trial ends or subscription ends WC_5048 As a user, I can add a new form WC_5047 As a user, I can download a form or a set of forms at once WC_5046 As a user, I can delete a form or a set of forms at once. WC_4712 As a user, I can create an invoice for my patients.

TRACEABILITY MATRIX (1 of 2) Test Case Sub-ID Name Requirement Mapping TC-01-01 Sign up for a new account (non-existent user) TC-01-02 Sign up for a new account (existing user) TC-01-03 Sign up for a new account (invalid input data) TC-02-01 Product import (non-existent product) WC_4815 TC-02-02 Product import (existing product) TC-02-03 Product import (missing required fields) TC-03-01 Map a product to a patient WC_4740 TC-04-01 Invoice creation WC_4812 TC-05-01 Ensure privilege separation between user types WC_4699 TC-06-01 Reporting schedule generation (non-existent schedule) WC_4739 TC-06-02 Reporting schedule generation (existing schedule) TC-07-01 Ensure referral mappings are valid WC_4738 TC-08-01 Perform security scans WC_4811 TC-09-01 Create patient record WC_4743 TC-10-01 Report generation WC_4744 TC-11-01 Archival/Retrieval of Patient Documents WC_4745 Testing: Nick

TRACEABILITY MATRIX (2 of 2) Test Case Sub-ID Name Requirement Mapping TC-12-01 Login TC-12-02 Logout TC-13-01 Validate documentation integrity WC_4720 TC-13-02 Validate documentation correctness TC-14-01 Task Generation WC_4692 TC-15-01 Ensure doctors’ data persists for a specified amount of time beyond their trial period WC_4719 TC-16-01 Modify user permissions WC_4785 TC-17-01 Access training documentation TC-18-01 Add a new form WC_5048 TC-18-02 Edit a form TC-18-03 Download a form WC_5047 TC-18-04 Delete a form WC_5046 TC-19-01 (TBD) Ensure validity of payment inputs (TBD) TC-19-02 (TBD) Validate payment (payment method accepted) TC-19-03 (TBD) Validate payment (payment method declined) Testing: Nick

NEXT STEPS Patients Users Products Live Testing Merge changes Connect features E2E little by little Users Create user management page Link FHIR identity and Cognito identities together. Products Create using patients as a blueprint Live Testing Project Manager: Baker

How to improve these going forward Prototypes should be representative Run into problems early Use the right tools to build the prototype Everything should be prototyped Prototype Back end and integration Smaller prototypes are helpful Schedules should be more flexible. Assume delays due to learning curves, unforseen problems. Focus on getting tasks completed Develop less features, but higher quality Favor a working copy vs. a beautiful copy Develop for incremental improvement. Project Manager: Baker

Demo of IOC

Website Demonstration Authentication Signup Login/Logout Routing Tasks Create/Read/Update/Delete Patients Create using patients as a blueprint Project Manager: Baker

Final Architecture Project Manager: Baker

Maintenance Demonstration Local Development How will a new developer develop for Holistic Office? Server Side Elastic Beanstalk (environment configuration) HAPI FHIR Tester (DB insights) Client Side S3, CloudFront, Lambdas (infrastructure configuration) Pipeline Build logs, deployments, etc. Project Manager: Baker

Support Plan

E2E Testing Demo Currently Implemented Coming Soon TC-01: Sign up for a new account (partial) TC-08: Perform Security Scans (manual) TC-09: Manage Patient Records (partial) TC-12: Login/Logout TC-14: Task Generation Coming Soon TC-02: Import/export products TC-03: Map products to patients TC-13: Validate documentation (manual) Test cases cannot currently be demonstrated in full due to maintenance on an Angular routing issue. Project Manager: Baker

Support Plan Our support plan aims at compiling high level information and guidelines regarding the following Support Requirements Detailed software usage information Release strategy Support information for contacting the USC CSCI 577 developers Project Manager: Baker

Support Plan - Support Requirements Necessary Assumptions: Clients able to find appropriate maintainers and maintain contact with HIPAA expert Clients have funding to continue support of project (AWS costs, Atlassian Wiki costs, etc.) Documentation is sufficient for continued operation (provided in Wiki) Continued external support of used frameworks/infrastructure Project Manager: Baker

Support Plan - Software Only Hardware and Facility environments are not applicable Provided Information: Software name and version as appropriate Description/rationale for usage Reference to site where applicable License type Project Manager: Baker

Support Plan - Release Strategy Release for usage -- Continual incremental updates as available. Changes are integrated and deployed via AWS CodePipeline. Current setup: Beta Build → E2E Tests → Prod Build Project Manager: Baker

Support Plan - Release Strategy Next items for development: Finish patients, user linkage. Evolutionary requirements: products, forms, reports, subscription (with PCI Compliance), user management Integrating automated test cases into the build pipeline Additional items for development based on: User feedback - customer discovery surveys Feasibility Project Manager: Baker

Support Plan - USC CSCI 577 Developers All team members have agreed to support Holistic Office by email for at least 4 months with regard to: Technology Infrastructure/Design Decisions Documentation Project Manager: Baker

Transition Objectives Strategy & Plan

Objectives Goals Minimize need for current team Future development team continues work Expectations Initial transition completed 4/19 Current team available via email for ~4 months Project Manager: Baker

TRANSITION Next Developers: Raghav Prakash - current team member Andrew Tsun - current team member (consulting) Other Help Kristen Ford and Rich Ford - Clients Kimberly Shutters Kurling Robinson - Management Consultant Project Manager: Baker

TRANSITION Responsibilities to transfer Infrastructure: AWS credentials, assets, expertise Software Development: Developer training. Development Process: JIRA development history Confluence Responsibilities Source Code: GitHub Repository Clean up GitHub commit history Shared Media: Google Drive files ownership Communications: Slack ownership Project Manager: Baker

Stakeholder Roles and Responsibilities Date Role Responsibility Location 2/3 - 4/19 Client Testing Receiving Training Confirmation of transfer of ownership Online By 4/19 Continuing Team Members Assume responsibility for all code Ensure all necessary documentation is completed 4/15 - 4/19 Project Manager Oversee transfer of ownership ~4/17 Rebuild Training - final wipe and rebuild Architect Verify Transfer of Ownership Training 4/19 -> Kurling Robinson Management consulting Project Manager: Baker

Questions?