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

Architecture and functionality review of KEN

    Details

    • Type: Rice Research Item
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Component/s: KEN
    • Labels:
      None
    • Rice Theme:
      Project Standardization
    • Priority Score:
      9
    • Functional Justification :
      Hide
      The concept of a component which handles notification and user preferences toward that effect makes sense from a functional perspective as well as an architectural one. In fact the original Coeus has a piece which handles this currently.

      KEN should ideally provide the ability to support multiple types of notification including email, SMS, instant messenger, etc. Additionally, a user should be able to configure their preferences for how they want to be notified about various events through a central channel instead of requiring them to go to multiple places. As it stands, currently KEN has been somewhat neglected and really does not have any actual real-world usage so it's suffering from a complete lack of adoption (at least to the best of my knowledge). Either we need to reaffirm the usefulness of this component and have it undergo both a functional and technical review or we need to remove it from the Kuali Rice project.
      Show
      The concept of a component which handles notification and user preferences toward that effect makes sense from a functional perspective as well as an architectural one. In fact the original Coeus has a piece which handles this currently. KEN should ideally provide the ability to support multiple types of notification including email, SMS, instant messenger, etc. Additionally, a user should be able to configure their preferences for how they want to be notified about various events through a central channel instead of requiring them to go to multiple places. As it stands, currently KEN has been somewhat neglected and really does not have any actual real-world usage so it's suffering from a complete lack of adoption (at least to the best of my knowledge). Either we need to reaffirm the usefulness of this component and have it undergo both a functional and technical review or we need to remove it from the Kuali Rice project.
    • Technical Justification:
      Hide
      As I've mentioned before, this module of Rice is half-baked. Much of the functional justification is relevant to the technical justification as well.

      Currently, the KEW module of Rice has the ability to handle it's own notification and it also includes user preferences to that effect. I know specifically at Indiana University we have "disabled" the KEN-based notification because it has had various strange bugs with the way it was implemented and the value (based on what is currently implemented there) is not particularly compelling.
      Show
      As I've mentioned before, this module of Rice is half-baked. Much of the functional justification is relevant to the technical justification as well. Currently, the KEW module of Rice has the ability to handle it's own notification and it also includes user preferences to that effect. I know specifically at Indiana University we have "disabled" the KEN-based notification because it has had various strange bugs with the way it was implemented and the value (based on what is currently implemented there) is not particularly compelling.
    • Impact if not Implemented:
      KEN will continue to be a module is not useful or used by any of the projects or implementers.
    • Priority - KFS:
      Medium
    • Priority - KC:
      Medium
    • Priority - KS:
      High
    • Priority - Rice:
      Medium
    • Theme:
      Modularity, Service Orientation, Adopting Existing Code, Industry Standards
    • Application Impact:
      Low
    • Effort Estimate:
      Medium ~ 500 hrs

      Description

      KEN is hasn't really been given much attention since it was originally written. Therefore it's tended to atrophy in the face of the work being done on the other modules.

      One big problem is that it does not have a full set of maintenance screens for maintaining it's various pieces of data. Converting it to use the KNS will allow for easier creation of these which is represented by another roadmap item.

      Summary of work involved: Kuali Enterprise Notifications (KEN) was intended to be a fully functional module of Rice that would allow users to configure what and how they would like to be notified of various items that were passed through Rice. This would included email, SMS, instant messenger, etc. and tools to indicate preferences. However, KEN was never fully developed and is currently only partially functional in these aspects and mostly unused by implementations and applications.

      This task would involve a full functional review of KEN as it stands now, requirements gathering to upgrade the module for better functionality including new maintenance screens, and an architectural review. The end result would be a full set of specifications for future work to revamp KEN.

        Attachments

          Issue Links

            Activity

            Hide
            cfairlie Cath Fairlie (Inactive) added a comment -

            KS comment - We don't know if KEN will satisfy all of our notification needs as it stand now, so doing the research to figure out where this product could go is pretty important.

            Show
            cfairlie Cath Fairlie (Inactive) added a comment - KS comment - We don't know if KEN will satisfy all of our notification needs as it stand now, so doing the research to figure out where this product could go is pretty important.
            Hide
            ewestfal Eric Westfall added a comment -

            KEN is currently a fairly stagnant module and it needs to go through a design, architecture and relevance review to determine what needs to be done to promote and encourage wider usage of this module of Rice.

            Show
            ewestfal Eric Westfall added a comment - KEN is currently a fairly stagnant module and it needs to go through a design, architecture and relevance review to determine what needs to be done to promote and encourage wider usage of this module of Rice.

              People

              • Assignee:
                ewestfal Eric Westfall
                Reporter:
                ewestfal Eric Westfall
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated: