Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

"Confirm that resources have been allocated to perform such activities" - at this point I do not have enough resources to cover both making the changes for Platform Maturity and help with testing.

  • Gaps

This section is used to document a limitation on a functionality or platform support. We are currently aware of this limitation and it will be delivered in a future Release.
List identified release gaps (if any), and its impact.

Gaps identifiedImpact
Template Code is inefficient with respect to threadingDrools is single-threaded. When a RESTful API call is made, it should be done in a thread vs polling. Else it holds up the processing of events/rules. The RESTful API calls to A&AI, SO and VF-C should be done in a separate thread.
Policy GUI limitations

Unable to update templates

This visual update of Control Loop Operational Policies is not user-friendly

Not a truly model-driven architecture. Code must be written in order to support new models.

...

Risk identifiedMitigation PlanContingency Plan
ResourcesActively seeking community support.Current resources are only enough to satisfy the Highest Priority Epics (Platform Maturity, JUnit 50% test coverage). But that will be difficult to achieve.
policy/engine - Difficult to obtain 50% JUnit code coverage based on the extreme amount of cyclomatic complexity and code refactoring needed to remove nested statements.Deprecation of the repository is possible with re-write of components that is needed to support Platform Maturity requirements.Request TSC for exception for that specific repository.
  • Resources

Fill out the Resources Committed to the Release centralized page.

...