Details
-
Enabler
-
Must have
-
None
-
True
-
Obs Mgt & Controls
-
-
-
7
-
7
-
20
-
2.857
-
Team_KAROO
-
Sprint 4
-
-
-
-
15.6
-
Stories Completed, Outcomes Reviewed, NFRS met, Demonstrated, Satisfies Acceptance Criteria, Accepted by FO
-
-
Team_KAROO
Description
Where do you observe the technical debt in the development artefacts?
- DishMaster readthedocs
- This assessment of ska-dish-lmc against SKA software standards (see section 1)
What remedial work is needed to eliminate the debt? Describe the rework needed.
- Rename DishMaster to DishManager (as per Dish LMC design),
- Make changes in order to pass tests that passed before the refactoring,
- Fix DishMaster (renamed DishManager) errors that show up in logs,
- Add unit tests for DishManager,
- Add documentation for the new version as per Definition of Done,
- This work will be done by replacing the existing C++ DishMaster device with a Python ska-tango-base based device as most economic way of adopting the latest version of SKA base classes, considering Karoo team skill set and business logic isolation in the existing code.
- DishManager health states reflect the status of subservient devices (e.g. not running).
Why is it important to address this technical debt item i.e. consequences or costs accrued by this item?
To improve maintainability, enable adding implementation of long running commands, comply to Dish LMC requirements, increase confidence (unit tests).
Attachments
Issue Links
- Is delivered by
-
REL-92 SKA-MID-MVP v0.1.0-experiment
- Discarded
-
REL-97 SIGNAL-CHAIN-MID v0.1.0-experimental
- Discarded
- is required by
-
SP-2546 CLONE - Dish LMC - basic SPFRx control
- Done
-
SP-2668 Dish LMC - basic control and monitoring
- Done
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...