Versions Compared

Key

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

...

Project RoleTeam member(s)
Technical Product Owner / LTSLT OwnerStefano Cossu (LTS)

Software engineers

Brian Hoffman (LTS), JJ Chen (LTS)

QA

Stefano Cossu, Brian Hoffman, JJ Chen, Paul Aloisio (LTS), Imaging Services

Functional documentation

Stefano Cossu, Brian Hoffman, JJ Chen

Scrum Master

Stefano Cossu

Project Manager

Vitaly Zakuta (LTS)

...

VIII. Assumptions, Constraints, Dependencies, and Risks

Project Assumptions

  • Enough time has been allotted for developers to set up one batch at a time.
  • Remediation processes can take a very long time but should require very little oversight once started.
  • Some remediation batches can be deferred for a long time if their priority is low.

Project Constraints

  • Other DRS Futures integration priorities contending for developers' time
  • Infrastructure capacity and cost (the tools should be scalable, but some batches could still take many weeks or months to complete)

Project Dependencies

The following dependencies apply only to the effective remediation process. Other parts of the project (analysis, reporting, etc.) can start immediately.

  • Image conversion service (imgconv) and ETL framework (drs-pipelines) available in production

Project Risks

DescriptionPlanImpactOwner
Remediation process takes an unexpectedly long timeStart with a small batch; extrapolate timing; increase batch size progressively; adjust forecast iterativelyProject timeline
Remediation process is unstable and requires frequent monitoringBuild solid exception handling; perform extensive load testing in advanceStaff time
Large numbers of image conversion tasks failBuild non-blocking reporting system; allow automatic retrying for 5xx errors; review failures separatelyStaff time; may require re-engineering remediation tools or infrastructure
Reference replacement does not go according to plansTest small batch of replacement actions; back up databases; report failed replacement to avoid failures falling through cracks; test each image (HEAD req) before deleting old versionLost references / broken images; old images cannot be replaced for a long time and impose extra storage costs

...