Page Comparison

...

Custom History Event Producer
- Populate additional data in history with extensibility

Component Dependencies
- The following diagram depicts the component dependencies.
- Components can be built in parallel. The longest component build time is 120 hours.
- Each estimate includes unit testing, component integration and integration testing.

Image Added

Estimates
- Note:
  - It is a rough estimate - to be refined
  - Estimate includes development and unit testing time
  - As mentioned above section, the components can be built in parallel.

Component	Development Estimate	Comments
SO Service List widget	80 hours / UI developer	populate serach filter criteria Displays a service list panel control action buttons
Statistic Dashboard	40 hours / UI developer	Displays statistic for the selected service scope
Service Instance Rendering and Detail Panel	120 hours / UI developer	Renders service instance workflow graphically provides the service instance details and selected task details Provides drill-down and drill-up capabilities
Rest APIs for supplying data	80 hours / Java developer	REST facade for collecting and conslidating various Camunda process instance and history data to simplify GUI data collection interaction. collecting SO Request DB data
Custom History Producer	40 hours / Java developer	Produce history with additional data population This is an option, and is used only if the Camunda history data is not sufficient.

...

Versions Compared