Kuali Rice Roadmap
  1. Kuali Rice Roadmap
  2. KRRM-135

KRAD Phase 2 - essential enhancements for KS 2.0

    Details

    • Type: Rice Enhancement Rice Enhancement
    • Status: Resolved Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: KR 2.2
    • Component/s: KRAD
    • Labels:
      None
    • Rice Theme:
      Kuali Application Business Drivers
    • Priority Score:
      5
    • Functional Justification :
      Hide
      There are several compelling reasons to support KRAD as a priority. Over the past year Kuali Student has partnered in the development of KRAD by committing resources both devoted and secondary. The primary justification for this effort is to complete some of the critical features of the original vision of KRAD. KRAD is evolving into a UI framework to support a rich user experience along with continuing to improve development velocity and these features are critical to meet that vision. Kuali Student has a dependency on providing a rich user experience primarily for student facing features, i.e., student registration, etc. Beginning in 2012 KS is embarking on a major development effort which includes a significant number of these rich UI requirements. Further our timelines are dependent upon the improved development velocity envisioned through KRAD. Therefore this effort is a critical dependency for meeting these upcoming development priorities.
      Show
      There are several compelling reasons to support KRAD as a priority. Over the past year Kuali Student has partnered in the development of KRAD by committing resources both devoted and secondary. The primary justification for this effort is to complete some of the critical features of the original vision of KRAD. KRAD is evolving into a UI framework to support a rich user experience along with continuing to improve development velocity and these features are critical to meet that vision. Kuali Student has a dependency on providing a rich user experience primarily for student facing features, i.e., student registration, etc. Beginning in 2012 KS is embarking on a major development effort which includes a significant number of these rich UI requirements. Further our timelines are dependent upon the improved development velocity envisioned through KRAD. Therefore this effort is a critical dependency for meeting these upcoming development priorities.
    • Priority - KFS:
      No Priority
    • Priority - KC:
      No Priority
    • Priority - KS:
      No Priority
    • Priority - Rice:
      No Priority
    • Effort Estimate:
      Very High ~ 2500 hrs

      Description

      Effort Estimate ~ 4000 hours according to Scott Gibson.

      The below requirements are in prioritized order for KRAD for Phase 2 of KRAD Development with KS. This list was updated by KS/Rice group and approved by ARC & KAI in January 2012.

      1. Performance Improvements (Req #1)
      2. Framework Code Improvements (Req #2)
      3. Validation Message refactoring for Accessibility (Req #3)
      4. Tooltip (relates to Help framework - see next item for the larger context of choices) (Req #4)
      5. Help Framework (needed for KNS Equivalence) (Req #5)
      6. Question Framework - configurable modal dialog box (needed for KNS Equivalence) - see also #11 below. (Req #6)
      7. Messages from Central Repository (Req #7)
      8. Rich Messages (Req #8)
      9. State-based validation (Req #9)
      10. Access (view only) without authenticating into portal (Req #10)
      11. General Lightbox Div Content - (this is the UI aspect of the question framework item above - that one is the backend aspect) (Req #11)
      12. Dictionary Validation (validation of XML configuration on startup or by separate program) (Req #12)
      13. Missing Lookup Functionality (needed for KNS Equivalence) (Req #13)
      14. Tables - standard semantics encoded (accessibility & readies for smaller devices) (Req #14)
      15. Tabs - standard semantics encoded (accessibility & readies for smaller devices) (Req #15)
      16. Keyboard Support (enter key, other shortcuts) (Req #16)
      17. Code cleanup - Compliance to W3C standards (code checker output) (Req #17)
      18. Improved Session Support (restore when session dies, multiple user tab support) - Multi-tasking support capability - so that documents don't "hose" each other when multiple processes from the same user session are invoked. Support multiple browser tab support. (Req #18)
      19. Missing Maintenance Functionality (needed for KNS Equivalence) (Req #19)
      20. Finish support for Authorizer and Presentation Controller (needed for KNS Equivalence) (Req #20)
      21. Convert Portal to use Spring (needed for KNS Equivalence) (Req #21)
      22. Applications access data via Services versus via direct database access (Req #22)
      23. Legend tag for fieldsets (Req #23)
      24. Collections re-design: behavioral - data entry/checked & temp/saved without add (Req #24)
      25. Collections re-design: Add collection item via lightbox (or other) (Req #25)
      26. Collections re-design: action field column placement (left or right) configurable (Req #26)
      27. Collections re-design: Yellow highlighting on new collection items (until submit) - & maybe when hovering on delete function (Req #27)
      28. Collections re-design: Total Lines and Grouping (needed for KNS Equivalence) (Req #28)
      29. Allow wildcard searches on numeric fields (e.g. DocID) (Req #29)
      30. Master detail relationship within a table (Req #30)
      31. Filtered & Faceted search, including Existing Req #12: Lookup Support for Faceted Search (Req #31)
      32. Combobox Control (Req #32)
      33. Inline Edit widget (Req #33)
      34. Table sub-collections within table collections_(Req #34)_
      35. User Preferences (Req #35):

      • global
      • per session
      • per BO
      • Filter search results by user
        36. Support for breadcrumbs in a lightbox (chain) that aren't view lookups (Req #36)
        37. Unique URLs for pages (in the left nav or tab) (Req #37)
        38. Back-button support for js actions (pushing history of js actions to browsers history) - (relates to #16 in set 1 above) (Req #38)
        39. Left navigation widget comprised of anchors (Req #39)
        40. UI boilerplate elements - make always in view (left nav, buttons, breadcrumbs), while others scroll away or collapse (Req #40)
        41. Undo support (Req #41)
        42. "Back to top" link or keyboard shortcut for all section and subsection headers (relates to #16 in set 1 above) (Req #42)
        43. Combine "lookup" and "inquiry" or "maintenance" views on one page, or easily get back and forth between the two (Req #43)

        Issue Links

          Activity

          Hide
          Hampton Sublett (Inactive) added a comment -

          Hi Dan,
          Thanks for the conference call regarding the urgency of KRRM-135. We ask that each enhancement "assignee" or "champion" fill out a Functional Justification to ensure that anyone reading it will be able to easily and quickly understand the need and/or the impact of each enhancement. Please do so at your earliest convenience. Thank you.

          Show
          Hampton Sublett (Inactive) added a comment - Hi Dan, Thanks for the conference call regarding the urgency of KRRM-135 . We ask that each enhancement "assignee" or "champion" fill out a Functional Justification to ensure that anyone reading it will be able to easily and quickly understand the need and/or the impact of each enhancement. Please do so at your earliest convenience. Thank you.
          Hide
          Dan McDevitt (Inactive) added a comment -

          Added functional justification. Please let me know if this needs further refinement.

          Show
          Dan McDevitt (Inactive) added a comment - Added functional justification. Please let me know if this needs further refinement.
          Hide
          Ailish Byrne added a comment -

          i'm going to break user preferences (requirement 35) into a separate jira

          Show
          Ailish Byrne added a comment - i'm going to break user preferences (requirement 35) into a separate jira
          Hide
          Jessica Coltrin (Inactive) added a comment -

          core feature work here is done.

          Show
          Jessica Coltrin (Inactive) added a comment - core feature work here is done.

            People

            • Assignee:
              Dan McDevitt (Inactive)
              Reporter:
              Jessica Coltrin (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Structure Helper Panel