Enhancement Request Form

Please fill out this enhancement request form template to the best of your ability. Providing enough detail will help eScholar Product Managers to make scoping decisions, and will help eScholar developers to have a clearer idea of what needs to be implemented.

If you prefer, you may download a PDF of this form and complete it offline.
  • Please provide a narrative description of the enhancement request and the purpose or goal of the enhancement. Please be as specific as possible including the component or module that needs to be modified. Include examples where appropriate.

    Example: In order to perform more effective near match decisions in eScholar Uniq-ID® we want to provide the user with entry and exit enrollment dates in the application.
  • Please explain the set of activities or business processes that currently exist to accomplish the specific goal. You may include a flow chart or story to describe the business process.

    Example: Currently users log into eScholar Uniq-ID® to review a pending near match. If the user is unable to make a decision about the potential match, the user has to log into the SIS to review enrollment history details to help determine if it is the same person.
  • Provide a detailed description of the functional requirements of the enhancement. Include business rules, screenshots, definitions of data to be handled, name of component or module being modified and record and field information.

    Examples:
    - Add the ability to store exit and entry dates in eScholar Uniq-ID®.
    - Only valid date formats should be accepted for the entry and exit dates
    - The entry and exit dates should be displayed on the screens where school information is available.
  • Use a narrative story or a series of numbered steps. Talk about the end-to-end scenario for the desired results. Make no assumptions about how the system will work, but explain what should happen instead. Recommendations for implementation can be included if desired, but should be called out as such.

    Examples:
    - Add the ability to store exit and entry dates in eScholar Uniq-ID®.
    - Only valid date formats should be accepted for the entry and exit dates
    - The entry and exit dates should be displayed on the screens where school information is available.
  • Please provide detailed definitions for each element; please also define the data type, maximum length, scale where applicable
    Sample:
    Element Name: School Year
    Data Type: Date
    Fixed length scale: 10
  • Please detail the number of times throughout the year this data will be collected / refreshed and during what times of the year.
  • Date Format: MM slash DD slash YYYY