Uploaded image for project: 'Kuali Rice Roadmap'
  1. Kuali Rice Roadmap
  2. KRRM-51

Rice tooling: administrative tools for all Rice components (KEW, KIM, BRMS etc). Generalizes KRRM-29

    Details

    • Priority Score:
      8
    • Priority - KFS:
      Low
    • Priority - KC:
      Critical
    • Priority - KS:
      No Priority
    • Priority - Rice:
      Medium
    • Theme:
      Ease of Implementation
    • Application Impact:
      Medium
    • Effort Estimate:
      Very High ~ 2500 hrs

      Description

      Tooling for Rice
      This item generalizes KRRM-29 (GUI for KEW routing). The idea is a set of general administrative tools for all Rice infrastructure components:
      1 GUI for KEW routing. Target: business user
      2 Generalized GUI for BRMS (defining and managing rules). Target: business user
      3 KSB deployment GUI (defining deployment topology, protocols etc). Target: technologists
      4 KSB performance metrics GUI (traffic, endpoint availability etc). Target: technologists
      5 KIM management GUI's Target: business users and technologists
      6 Integrated configuration tools (Dictionary-workflow-IdM). The ability to track the effects of a configuration change through various levels of the infrastructure

        Attachments

          Issue Links

            Activity

            Hide
            kymber Kymber Horn added a comment -

            KFS thinks this needs to be broken in out since some of them are already covered in other issues (ie item 1 is in KRRM-29) and we think these should be prioritized separately.

            Thanks, Kymber

            Show
            kymber Kymber Horn added a comment - KFS thinks this needs to be broken in out since some of them are already covered in other issues (ie item 1 is in KRRM-29 ) and we think these should be prioritized separately. Thanks, Kymber
            Hide
            cfairlie Cath Fairlie (Inactive) added a comment -

            Support the comment that it needs to be broken out. Some of these items may have different priorities and it is unlikely that we can do it all at the same time.

            Show
            cfairlie Cath Fairlie (Inactive) added a comment - Support the comment that it needs to be broken out. Some of these items may have different priorities and it is unlikely that we can do it all at the same time.
            Hide
            lschultz Lori Schultz (Inactive) added a comment -

            KC supports separating and prioritizing these individually.

            Show
            lschultz Lori Schultz (Inactive) added a comment - KC supports separating and prioritizing these individually.
            Hide
            lschultz Lori Schultz (Inactive) added a comment -

            Items related to successful completion of KRRM-29 and KRRM-30 are critical for KC to meet functional equivalence with Coeus.

            Show
            lschultz Lori Schultz (Inactive) added a comment - Items related to successful completion of KRRM-29 and KRRM-30 are critical for KC to meet functional equivalence with Coeus.
            Hide
            ewestfal Eric Westfall added a comment - - edited

            I would posit that this particular roadmap item should be split up into the following, based on the original breakdown in the description:

            1) A graphical user interface for authoring of workflow processes (i.e. boxes/circles and arrows, in a drag-and-drop fashion)
            2) BRMS interface - can we can consider this being satisfied by the KRMS work in Rice 2.0?
            3) Enhanced GUI for the KSB. Would include improved information about the service registry and the services contained that are deployed
            4) User interface for viewing and tracking statistics, specifically related to the KSB (traffic, message routing, endpoint availability and general health)
            5) Improvements to KIM guis - i think this is already represented by a different roadmap item (KRRM-7)?
            6) I'm not sure what the last item is that Leo mentions of "integrated configuration tools". I know we already have a jira item for data dictionary configuration (KRRM-23) does that encompass the full scope of number 6 in the description of this issue?

            Out of all of these, the GUI for KEW authoring seems to be the item of highest interest to most (with the exception of the BRMS which is being done in Rice 2.0)

            So, if I was going to make a recommendation, I would recommend the following:

            1) Create a new roadmap item for graphical drag-and-drop KEW process configuration.
            2) Consider existing BRMS/Rules Engine roadmap items to encompass the "BRMS" portion of this roadmap item.
            3) Create a new roadmap item for improving the KSB Service Registry user interface.
            4) Create a new roadmap item related to business activity monitoring (traffic flow, endpoint availability, metrics).
            5) Consider KRRM-7 to encompass KIM management GUI functionality.
            6) Consider KRRM-23 to encompass data dictionary tooling.

            Are there any suggestions for an alternate course of action regarding this roadmap item?

            Show
            ewestfal Eric Westfall added a comment - - edited I would posit that this particular roadmap item should be split up into the following, based on the original breakdown in the description: 1) A graphical user interface for authoring of workflow processes (i.e. boxes/circles and arrows, in a drag-and-drop fashion) 2) BRMS interface - can we can consider this being satisfied by the KRMS work in Rice 2.0? 3) Enhanced GUI for the KSB. Would include improved information about the service registry and the services contained that are deployed 4) User interface for viewing and tracking statistics, specifically related to the KSB (traffic, message routing, endpoint availability and general health) 5) Improvements to KIM guis - i think this is already represented by a different roadmap item ( KRRM-7 )? 6) I'm not sure what the last item is that Leo mentions of "integrated configuration tools". I know we already have a jira item for data dictionary configuration ( KRRM-23 ) does that encompass the full scope of number 6 in the description of this issue? Out of all of these, the GUI for KEW authoring seems to be the item of highest interest to most (with the exception of the BRMS which is being done in Rice 2.0) So, if I was going to make a recommendation, I would recommend the following: 1) Create a new roadmap item for graphical drag-and-drop KEW process configuration. 2) Consider existing BRMS/Rules Engine roadmap items to encompass the "BRMS" portion of this roadmap item. 3) Create a new roadmap item for improving the KSB Service Registry user interface. 4) Create a new roadmap item related to business activity monitoring (traffic flow, endpoint availability, metrics). 5) Consider KRRM-7 to encompass KIM management GUI functionality. 6) Consider KRRM-23 to encompass data dictionary tooling. Are there any suggestions for an alternate course of action regarding this roadmap item?
            Hide
            sagee Sandra Agee (Inactive) added a comment -

            This scope is confirmed

            Show
            sagee Sandra Agee (Inactive) added a comment - This scope is confirmed
            Hide
            ewestfal Eric Westfall added a comment -

            Closing this issue because the actions defined on the later comments has been taken and it has been broken out into KRRM-124, KRRM-125, and KRRM-126.

            Show
            ewestfal Eric Westfall added a comment - Closing this issue because the actions defined on the later comments has been taken and it has been broken out into KRRM-124 , KRRM-125 , and KRRM-126 .

              People

              • Assignee:
                cderosa Christopher De Rosa (Inactive)
                Reporter:
                lfernig Leo Fernig (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: