GoConqr hat ein neues Design! Sag uns, wie es dir gefällt.

Mindmap

IEEE Standard Classification for Software Anomalies

angel valdez Spanisch

Inhalt der Mindmap

IEEE Standard Classification for Software Anomalies

  1. 4- phase resolution process

    • Step 1: Recognition
      • Step 2: Investigation
        • Step 3: Action
          • Step 4: Disposition
            • There is only one level of categorization during the Disposition phase.
              • Resolution implemented
          • During the action phase, anomalies are classified according to
            • Resolution
              • Corrective action
        • During the investigation phase, anomalies are classified according to
          • Actual cause
            • Source
              • Type
      • During the recognition phase, anomalies are classified according to
        • Project activity
          • Project phase
            • Suspected cause
              • Repeatability
                • System symptom
                  • Product status
  2. This standard accommodates the center arrangement of traits for grouping of defects and failures

    • provides a highly detailed classification scheme
      • It is perceived that there are different properties of defects or fails that are of interesting an incentive to explicit software or business necessities.
  3. Impact clasification used

    • Severity
      • Priority
        • Customer Value
  4. Relationships

    • Problem-Failure
      • Failure-Fault
        • Fault-Defect
          • Defect-Change Request
            • A defect may be removed via completion of a corrective change request. A corrective change request is intended to remove a defect. (A change request may also be initiated to perform adaptive or perfective maintenance.)
          • A fault is a subtype of the supertype defect. Every fault is a defect, but not every defect is a fault. A defect is a fault if it is encountered during software execution (thus causing a failure). A defect is not a fault if it is detected by inspection or static analysis and removed prior to executing the software.
        • A failure may be caused by (and thus indicate the presence of) a fault.
          • A fault may cause one or more failures.
      • A problem may be caused by one or more failures.
        • A failure may cause one or more problems

Informationen

Beschreibung
Mindmap am IEEE Standard Classification for Software Anomalies, erstellt von angel valdez am 16/05/2019.
Erstellt von
angel valdez
Aufrufe
0
Bewertung

Feedback

Worum geht es?

Wie gefällt dir das neue Design?

Dein Eindruck