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

Score Cards: Validation implementation

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major Major

      So, once we've identified what it is we need to validate we can set about implementing it!

      We should consider the 10 Usability Heuristics for User Interface Design as they relate to validation.

      These suggest:-

      #1 Visibility of system status
      #9 Help users recognize, diagnose, and recover from errors

      We should show an indicator beside sections containing invalid data to allow the User to identify problematic areas in the model from the top-level page/screen and drill down further to the point of error.

      #5 Error prevention

      We should endeavour to prevent Users from making mistake where possible.

      We should engage with the kogito-ui and kogito-tooling teams to discuss, propose and agree standards for "kogito editors" and what provision we can expect (or demand!) from the channel itself vs editor (e.g. if we show a list of validation errors this could possibly be supported by integrating with VSCode).

      Should validation errors be persisted or identified "on open"? (or other triggers)

      This JIRA is a placeholder.

        1.
        		 Score Cards: Validation: Prototype research Sub-task Done Major Michael Anstis
        2.
        		 Score Cards: Validation: MiningField.importance valid range Sub-task Done Major Michael Anstis
        3.
        		 Score Cards: Validation: MiningField.high/low value Sub-task Done Major Michael Anstis
        4.
        		 Score Cards: Validation: MiningField.missingValueReplacement Sub-task Done Major Michael Anstis
        5.
        		 Score Cards: Validation: MiningField.invalidValueReplacement Sub-task Done Major Michael Anstis
        6.
        		 Score Cards: Validation: Removal of MiningField needs to update Attributes' predicates Sub-task Done Major Michael Anstis
        7.
        		 Score Cards: Validation: ValidationService API rework Sub-task Done Critical Michael Anstis
        8.
        		 Score Cards: Validation: Move validation indicator "inside" label Sub-task Done Minor Roberto Emanuel
        9.
        		 Score Cards: Validation: Characteristic Baseline Score should be hidden when Model Baseline score is provided Sub-task Done Major Michael Anstis
        10.
        		 Score Cards: Validation: Outputs Sub-task Done Major Roberto Emanuel
        11.
        		 Score Cards: Move validation to post-commit update Sub-task Done Critical Michael Anstis
        12.
        		 Score Cards: Validation: Characteristics: Reason Code and Baseline/Partial scores Sub-task Done Major Roberto Emanuel

            manstis@redhat.com Michael Anstis
            manstis@redhat.com Michael Anstis
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: