Uploaded image for project: 'Fidelis AI'
  1. Fidelis AI
  2. FAI-266

Scorecard model: Outputs Fields UX

    XMLWordPrintable

Details

    • Story
    • Resolution: Done
    • Major
    • 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 34-36 (from Aug 17), 2020 Week 37-39 (from Sep 7), 2020 Week 40-42 (from Sep 28)

    Description

      User stories:

      • As a user I want to apply a predictive model to a set of data, so that I can generate predictive scores based on historical data.
      • As a user I want to use a scorecard editor that will allow me to enter or edit scorecard configuration data (characteristics, attributes, baseline score, partial score etc.) 
      • As a user I want to use a scorecard editor that will allow me to enter input to retrieve the calculated evaluation

      Note - Fields might include, but not all of them are mandatory at the same time"

      name
      optype
      dataType
      feature
      value
      targetField

       

      http://dmg.org/pmml/v4-4-1/Output.html

      Attachments

        Issue Links

          clones

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. FAI-255 Scorecard model: Mining Schema UX

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Done
          is related to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. FAI-174 PMML Score Card editor: Iteration 1

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Done

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. FAI-184 Score Cards: New Model Wizard

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Backlog

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. FAI-183 Score Cards: Landing page

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Done

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. FAI-185 Score Cards: Data Dictionary component

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Done

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. FAI-186 Score Cards: Prototype Mining Schema component

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Done

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. FAI-187 Score Cards: Prototype: Outputs component

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Done
          relates to

          Task - Represents a small unit of work that is not end-user facing. DROOLS-4589 Refactor of Scorecards

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              rhn-support-eclayton Elizabeth Clayton
              rhn-support-eclayton Elizabeth Clayton
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: