CPS Definition of Done

DoD for a typical User Story

1. Code reviewed and Merged
2. Release Notes updated
3. Latest Yaml files copied to /docs folder (see step2 on CPS Release Process)
4. Acceptance Criteria of the User Story have been met
5. New functionality Demoed to Team and Stakeholders
   1. Uploaded recording of demo to CPS User Story Demos

Additional checks for a Bug

1. Consider cherry-pick for previous release(s)

2. Complete Fault-Slip-through Analysis template below and add as comment

   1. Bug Category:

      1. 3PP

      2. Critical Vulnerability

      3. Documentation

      4. Functional

      5. High Availability

      6. Install

      7. Logging

      8. Performance

      9. Robustness

      10. Rollback

      11. Scalability

      12. Security

      13. Testware/CI

      14. Upgrade
   2. Reason for Slippage: 
      1. Insufficient test coverage
      2. Intermittent Fault/Timing Issue
      3. Missed impact
      4. Missed in code review
      5. Missed in design analysis
      6. Missed in document review
      7. Missing requirement
      8. Unrealistic Development timeframe
      9. Late requirement: insufficient analysis
      10. Environment
   3. Action needed to prevent slippage: <free text>
   4. Phase it should have been found in: 
      1. Design
      2. Review
      3. Automated (unit) Test
      4. Microservice CI (CIST)
      5. Release
   5. Category of test it should have been found in:
      1. Unit
      2. Integration Test
      3. Performance
   6. Description of test it should have been found in: <free text>
   7. Link(s) To JIRA improvement record: <free text>

      Complete and Fault Slip-through Analysis (FSA) as a comment in Jira
      template