Skip to end of metadata
Go to start of metadata


Indicate the necessity for this enhancement. What does it accomplish?

The idea is that if someone is configuring a simple proposition to compare a term against some user supplied value which must be from a certain set, we want to be able to have KRMS' UI present them with either a select drop down, or a lookup to choose the value.

  • What this is - make it so when you specify the value a term is compared to, allow them to choose from a set of predefined values
  • Start by looking at what MIT COEUS provides for this
  • Should consider support in database for it, and for external data as well
  • Given term give me back valid values for it or a lookup for it
  • Simplest way to do it might be just a drop-down
  • Peter's original idea:
    • Have the term specification have a special type to signal that it's going to need to use this type of service to resolve it
    • Do a generic type parameter for it

Detailed Description

Give a detailed description for the enhancement. Clearly describe all concerns, eliminating ambiguities.

Usage Scenarios

Include at least one usage scenario, from the user's task perspective, that might be helpful in understanding the issue:

Mocks and Diagrams

Include any mocks (for UI enhancements) or diagrams that might be helpful in understanding the issue:


If applicable, list expectations for performance (optimal and worst cases would be fine, give time in seconds):


Include links to other confluence pages or external resources that might be helpful for this issue:

Requirements Listing

List all requirements (individual, verifiable statements) that indicate whether the work for this item has been complete. If there are requirements that are not essential to the functionality but would be nice to have if time allows, enter those under 'Non-Essential':

  1. item
  2. item
  1. item
  2. item


List any functional or technical work that must be completed before work on this item can begin:

  1. item


List any issues that need to be resolved before work on this item can begin:

  1. item
  2. item
  1. item
  2. item

QA or Regression Testing Plan

List steps needed to test the basic functionality of this update, enhancement, bug fix

  1. test/steps
  2. test/steps


Functional Analysis Complete? No (completed by SME)

Needs Review by KAI?No(completed by SME)

Technical Analysis Complete?No(completed by DM)

Needs Review by KTI?No(completed by DM)

Estimate: 160 hours(completed by DM)

Technical Design: Link Here(completed by DM)

Jira: (completed by SME)

Final Documentation:Link Here(completed by DM)

Added to QA: No (completed by SME)

  • No labels