-
Feature
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
False
-
-
False
-
Not Selected
Feature Overview (mandatory - Complete while in New status)
- The original plan of reconciliation involved breaking everything that is required for preprocessing of SDG into a separate API.
Goals (mandatory - Complete while in New status)
Provide high-level goal statement, providing user context and expected user outcome(s) for this Feature
- Preprocessing can eventually move over to CLI through ilab data process
- SDG is broken into a modular framework as opposed to a monolithic pipeline as it exists today
Requirements (mandatory -_ Complete while in Refinement status):
- Wrap everything after data ingestion and before SDG generation, into a separate API call
- That API call can be consumed by CLI
Done - Acceptance Criteria (mandatory - Complete while in Refinement status):
Use Cases - i.e. User Experience & Workflow: (Initial completion while in Refinement status):
Include use case diagrams, main success scenarios, alternative flow scenarios.
<your text here>
Out of Scope __(Initial completion while in Refinement status):
High-level list of items or persona’s that are out of scope.
<your text here>
Documentation Considerations __(Initial completion while in Refinement status):
Provide information that needs to be considered and planned so that documentation will meet customer needs. If the feature extends existing functionality, provide a link to its current documentation..
<your text here>
Questions to Answer __(Initial completion while in Refinement status):
Does preprocessing move to CLI ?
Who maintains the API once it is decoupled from SDG ?
Background and Strategic Fit (Initial completion while in Refinement status):
Provide any additional context is needed to frame the feature.
<your text here>
Customer Considerations __(Initial completion while in Refinement status):
Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.
<your text here>
- …