Skip to content

[General]: Decide how SIST and SIDD should be supported together #29

Description

@harryswift01

Feedback or Inquiry

We need to decide how SIDD should be made available alongside SIST before implementation begins.

Possible approaches include full integration, an optional workflow, separate related packages, or separate packages with a shared interface.

Proposed Work

  • Identify the authoritative SIDD version.
  • Document its inputs, outputs, dependencies, and tests.
  • Identify genuinely shared functionality.
  • Identify behaviour that should remain SIDD-specific.
  • Compare the main integration and packaging options.
  • Consider configuration, CLI, Python API, and result-format implications.
  • Consider ownership, maintenance, and versioning.
  • Record the decision in an architecture decision record.

Done When

  • The current SIDD implementation is documented.
  • Shared and algorithm-specific functionality is understood.
  • The main architecture options have been compared.
  • Packaging and maintenance implications are clear.
  • The selected approach has a documented justification.
  • The architecture decision has been approved.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions