Lost time due to sync/handoff issues between service areas during the "real" operator workflow that is triggered by a web application
Risk Description:
In the 23.3 planning we have noticed that each service area is building successfully to requirements for that service area. We are seeing that some hand-off (e.g. how do we hand something from Dockstore off to WPS-T directly) is not quite working as expected. Suggest that we work through some sort of description (maybe with screen mockups) of an operator going through the entire workflow to help set expectations of handoff across services. I think there's some previous work I/Rob did like this but it was perhaps a bit too abstract. E.g. activity diagram in Lucid: https://lucid.app/lucidchart/8cfdfeb4-f244-4a38-b574-fde8c7c1feed/edit?viewport_loc=-828%2C-406%2C3234%2C1551%2CvoXFe0~85mnn&invitationId=inv_872ddff4-3919-4423-b821-1efc12e7b000
-N2 Diagram and interaction/use cases/scenarios will help identify these areas
Response to a risk:
Lost time due to sync/handoff issues between service areas during the "real" operator workflow that is triggered by a web application
Risk Description:
In the 23.3 planning we have noticed that each service area is building successfully to requirements for that service area. We are seeing that some hand-off (e.g. how do we hand something from Dockstore off to WPS-T directly) is not quite working as expected. Suggest that we work through some sort of description (maybe with screen mockups) of an operator going through the entire workflow to help set expectations of handoff across services. I think there's some previous work I/Rob did like this but it was perhaps a bit too abstract. E.g. activity diagram in Lucid: https://lucid.app/lucidchart/8cfdfeb4-f244-4a38-b574-fde8c7c1feed/edit?viewport_loc=-828%2C-406%2C3234%2C1551%2CvoXFe0~85mnn&invitationId=inv_872ddff4-3919-4423-b821-1efc12e7b000
-N2 Diagram and interaction/use cases/scenarios will help identify these areas