Page Comparison

...

Component Build Dependencies
- The following diagram depicts the component build dependencies.
- Components can be built in parallel with a certain level of sequential integration.
- Each estimate includes code development and unit testing plus some component integration and integration testing (since there are API dependencies).

Estimates (T-Shirt Size: M)
- Note:
  - It is a rough estimate - to be refined
  - Estimate includes development and unit testing time
  - As mentioned in the above section, the components can be built in parallel.
  - 5 hours / day

Priority	Component	Development Estimate	Comments
Priority	Component	Development Estimate	Comments
1	REST APIs for providing data to UIs	60 40 hours / Java developer	REST facade for collecting and consolidating various Camunda process instance and history data to simplify GUI data collection interaction. collecting SO Request DB data
2	SO Service List widget	60 hours / UI developer	populate search filter criteria Displays a service list panel control action buttons
3	Service Instance Rendering and Detail Panel	40 60 hours / UI developer	Renders service instance workflow graphically provides the service instance details and selected task details Provides drill-down and drill-up capabilities
4	Statistic Dashboard (stretch goal)	40 hours / UI developer	Displays statistic for the selected service scope
5	~~Custom History Producer (stretch goal)~~	~~40 hours / Java developer~~	Not need for Casablanca Produce history with additional data population This is an option, and is used only if the Camunda history data is not sufficient.

Versions Compared