EICC demo walkthrough

This silent recording follows a SOAP contract failure through correction, retesting, acceptance, and a fictional release. All organizations and approvals are fictional. The opening Northstar tour uses seeded records; qualification outcomes are created during the recording. Release transitions stay within the local demonstration.

1. 00:00

   Welcome to EICC: A recorded walkthrough of the redesigned app. All organizations, records, and approvals are fictional.

2. 00:05

   Project overview: Coverage, test results, and release readiness are calculated from persisted Northstar records.

3. 00:17

   Dark theme: The same workspace, with a dark slate palette and accessible semantic status colors.

4. 00:22

   Requirements and traceability: Business needs connect to functional and technical requirements, integrations, tests, and release scope.

5. 00:35

   Integration catalog: Inspect system boundaries, REST and SOAP contracts, mappings, and connected delivery evidence.

6. 00:40

   Explainable release gates: The Northstar pilot remains blocked. Every failed gate identifies the evidence or work still required.

7. 00:48

   Run a real SOAP test: In a separate qualification project, submit integer case ID 42 to a contract that requires an XML string.

8. 00:53

   Inspect the failure: The captured request sends xsd:int. The local SOAP service rejects it because case_id must be xsd:string.

9. 01:00

   Investigate a linked defect: Create the defect from the failed execution, then record the root cause and the intended correction.

10. 01:11

    Correct the source mapping: Change the case_id transformation from identity to to_string. The test payload remains the integer 42.

11. 01:24

    Retest and retain the evidence: The corrected mapping sends xsd:string and returns HTTP 200. The earlier failure remains in execution history.

12. 01:38

    Close the evidence loop: Resolution requires investigation details and a later passing retest against the current contract.

13. 01:42

    Complete the linked requirements: Complete the reviewed business, functional, and technical requirements after the contract has passed qualification.

14. 01:53

    Record acceptance evidence: The case operator verifies the current SOAP result and attaches the retained request and response.

15. 02:07

    Record stakeholder sign-off: Approval identifies both the represented fictional stakeholder and the authenticated demo actor.

16. 02:15

    Assess and approve the change: Record impact from stored relationships before approval; validation checks the current passing test evidence.

17. 02:42

    Verify every release gate: Requirements, current tests, acceptance, defects, change validation, deployment notes, and rollback all satisfy the gates.

18. 02:51

    Complete the fictional release: Authorized transitions record Planned, Ready, Deployed, and Completed. This does not deploy external software.

19. 03:08

    Generate the delivery document: Release notes are a versioned snapshot generated from the project's stored scope, deployment plan, and readiness.

20. 03:16

    A connected delivery record: The business-to-technical chain now has passing tests, accepted UAT, a closed defect, and a completed release.