1. Derive an improvement and compare repaired obtaining arrangements
Applying SYSE.25, the team groups the observations by the developer’s failed undertaking. The first improvement hypothesis is a supported way to obtain trustworthy feedback and move the identified result into limited use. A new portal is one possible interface, not the user result.
The team uses SYSE.24 to construct three whole arrangements. The comparison holds constant the service class, source change, provider capabilities, artifact identity, isolated test data/environment, permission, deployment-test question and observation horizon. All three must include support, recovery, variation, maintenance and exit.
| Arrangement | Constructed provision | Choice-changing burden still to observe |
|---|---|---|
| A: repair and retain local pipelines | Each application repository owns its workflow and environment recipe, carries the verified artifact unchanged, creates an isolated test environment and provides its support/recovery procedure. The original identity and shared-staging faults are repaired here too. | Each consumer maintains and qualifies its implementation. Duplication and support difficulty are questions, not assumed defects. |
| B: thin shared provision over existing services | A versioned shared workflow/module supplies the same artifact/environment operations. Consumers pin their selected version and retain explicit service configuration. The provider supports the shared contribution and its compatibility path. | Shared-component maintenance, consumer qualification, coordinated support, migration and correlated failure remain real work. |
| C: portal plus its required backend | The interface exposes operations with the same artifact, environment, support and recovery obligations. | Its additional user gain must justify another interface’s implementation and maintenance. That gain is not yet established for this CI-familiar cohort. |
A matched constructed happy-path trial gives the same limited result for A and B: each carries the intended artifact unchanged, provides an isolated environment and completes the same bounded deployment test for the same ordinary changes. Both improve on the faulty baseline.
The choice result is a retained A/B tie and one discriminating probe. Apply the same provider/toolchain update and a recoverable failure to both arrangements. Include all affected consumer qualification and observe developer effort, maintainer effort, support fulfillment and correlated impact over the same interval. Counting only the shared-module edit or only local consumer maintenance would break the comparison.
C remains deferred until its extra user-result hypothesis can be tested fairly. The rest of this application develops B for the probe. A requested language-specific variant outside the probe remains unqualified; its existing local path is retained with its known limits.