Skip to end of metadata
Go to start of metadata

Any items that are not struck through below are being moved to the KRRM-141 - KRAD Phase 3 page for 2.3 release planning.


Rice 2.2 Project Plan with Milestones

Requirement Documents

Copy Requirements Template to complete a new requirement document.

See child pages at bottom below for more details on each committed requirement.

The complete prioritized list of KRAD requirements can be found at

New Candidate List - Prioritization

note: struck through items are already fixed or will be moved under KRRM-144 

  1. Performance Improvements (Req #1)
  2. Framework Code Improvements (Req #2)
  3. Error & other 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 (also needed for KNS equivalence) (Req #5)
  6. Question Framework - configurable modal dialog box (also needed for KNS equivalence).   See also #11 below. (Req #6)
  7. Master detail relationship within a table (Req #30)
  8. Collections re-design: Add collection button adds line with blank fields, user enters data in fields, no additional add action needed (Req #24)
  9. Collections re-design: Add collection item via lightbox (or other) (Req #25)
  10. Collections re-design: action field column placement (left or right) configurable (Req #26)
  11. Collections re-design: Yellow highlighting on new collection items (until submit) - & maybe when hovering on delete function (Req #27)
  12. Collections re-design: Total Lines and Grouping (needed for KNS Equivalence) (Req #28)
  13. Messages from Central Repository (Req #7)
  14. Rich Messages (Req #8)
  15. State-based validation (Req #9)
  16. Access (view only) without authenticating into portal (Req #10)
  17. General Lightbox Div Content - (this is the UI aspect of the question framework item above - that one is the backend aspect) (Req #11)
  18. Table sub-collections within table collections_(Req #34)

Phase 3

  1. Dictionary Validation (validation of XML configuration on startup or by separate program) (Req #12)
  2. Missing Lookup Functionality (needed for KNS Equivalence) KULRICE-5435 (Req #13)
  3. Tables - standard semantics encoded (accessibility & readies for smaller devices) (Req #14)
  4. Tabs - standard semantics encoded (accessibility & readies for smaller devices) (Req #15)
  5. Keyboard Support (enter key, other shortcuts, back to top) (Req #16) 
  6. Code cleanup - Compliance to W3C standards (code checker output) (Req #17) - needs more detail/clarification and if it should be part of this or just general maintenance work.
  7. 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)
  8. Missing Maintenance Functionality (needed for KNS Equivalence) KULRICE-8055, KULRICE-8056 (Req #19)
  9. Finish support for Authorizer and Presentation Controller (needed for KNS Equivalence) KULRICE-8049 (Req #20)
  10. Convert Portal to use Spring  (needed for KNS Equivalence) KULRICE-8244 (Req #21)
  11. Applications access data via Services versus via direct database access (Req #22)
  12. Legend tag for fieldsets (Req #23)
  13. Allow wildcard searches on numeric fields (e.g. DocID) (Req #29)
  14. Filtered & Faceted search, including Was previously Req #12:  Lookup Support for Faceted Search (Req #31)
  15. Combobox Control (Req #32)
  16. Inline Edit widget (Req #33) 
  17. User Preferences (Req #35)
    1. global
    2. per session
    3. per BO
    4. Filter search results by user
  18. Breadcrumbs revisit and support for breadcrumbs in a lightbox (chain) that aren't view lookups (Req #36)
  19. Unique URLs for pages (in the left nav or tab) (Req #37)
  20. Back-button support for js actions (pushing history of js actions to browsers history) (Req #38)
  21. Left navigation widget comprised of anchors (Req #39)
  22. UI boilerplate elements - make always in view (left nav, buttons, breadcrumbs), while others scroll away or collapse (Req #40)
  23. Undo support (Req #41)
  24. "Back to top" link or keyboard shortcut for all section and subsection headers (relates to #16 in set 1 above) (Req #42)
  25. Combine "lookup" and "inquiry" or "maintenance" views on one page, or easily get back and forth between the two (Req #43)
  • No labels