You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Vision: Complete design of an event streaming based system to support scalable and reliable publication and replicaiton for the federation
Acceptance criteria:
detailed design document that describes the architecture
identified set of use cases that must be met
PoC of the end to end system
agreement among key federation partners on the design and operational metrics
Josh's Suggestion for breaking into stories
This largely the sum total of work that needs to be done for a PoC. I'd suggest breaking the detailed design doc requirement into stories for the following points:
Create block architectural diagram. (probably can be considered done?)
Create a sequence diagram detailing interactions between publisher submission through to indexing.
Create functional and operational requirements document for interactions outlined in sequence doc.
Create JSON schema for shared APIs (probably largely done for STAC, still needs to be done for event data).
I think the other bullet points of acceptance criteria can be largely met by other stories on the board, or will happen as a result of doing that work.
The text was updated successfully, but these errors were encountered:
Vision: Complete design of an event streaming based system to support scalable and reliable publication and replicaiton for the federation
Acceptance criteria:
Josh's Suggestion for breaking into stories
This largely the sum total of work that needs to be done for a PoC. I'd suggest breaking the detailed design doc requirement into stories for the following points:
I think the other bullet points of acceptance criteria can be largely met by other stories on the board, or will happen as a result of doing that work.
The text was updated successfully, but these errors were encountered: