Versions Compared

Key

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

...

  1. getServiceList(Map searchCriteria...)                                                 // invokes new getInfraRequest(Map searchCriteria...)
    1. getServiceStatistic(Map searchCriteria, String status);            // get the statistic percentage for the status
  2. getProcessInstanceId(String serviceInstanceId);                               // get the processInstanceId through GET /history/variable-instance/{id}
  3. getprocessDiagramXML(String processInstanceId);                          // get a process instance, get a process definition id, and get diagram
  4. getprocessInstanceDetail(String processInstanceId); 
  5. getHistoryActivityInstance(String processInstanceId);                       // GET /history/activity-instance?processInstanceId={processInstanceId}
  6. getProcessInstanceParent (String processInstanceId);
  7. getProcessInstanceChildren(String processInstanceId);
  8. getProcessTaskDetail(String processInstanceId, String taskId);
  9. getProcessTaskType(String processInstanceId, String taskid);        // query if this task type is "Call Activity" for drilling down

    • The following diagram depicts the API interaction.

Image Removed

...


...

Image Added

  • 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

...

Priority

Component

Development Estimate

Comments

1REST APIs for providing data to UIs40 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
2SO Service List widget60 hours / UI developer
    • populate search filter criteria
    • Displays a service list panel
    • control action buttons
3

Process/Service Instance Rendering

and Detail Panel

60 hours / UI developer
    • Renders process/service instance workflow graphically
    • provides the process/ service instance details and selected task details
    • Provides drill-down and drill-up capabilities
4Statistic Dashboard (stretch goal)40 hours / UI developer
    • Displays statistic for the selected service scope
5Custom 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.