Quality @ Source

High Availability

(5 9’s)Low Latency (in µ/m seconds)

High throughput (1000’s per second)

Super Correct (trillions, 0.XXXXXX, complex)

Long product life (10’s of years)

“Functional Correctness @ High Throughput having Low Latency

running for Decades with High Availability”

“Anything that can go wrong, will go wrong”

Impossible to cover all possible fault

Permutations

Build Robust Software from ground up!

Framework(Structure)

Review(Improve)

Guidelines(Patterns)

ProcessSpec

Design

DevelopTest

Each line of code Design, Code, Test Reviewed

Tight feedback loops continuous integration fully automated testing

UnitComponent

End to End

The closer the test to the code, the more useful

Behaviour Driven Development

Validating the Requirement

Executable Acceptance Criteria for User Stories with a DSL modeled using the conceptual system model

- Readable/Reusable

Scenario: Submit trade for a valid instrument with set mandatory fields

Given a registered user “CCP Admin” is available And an instrument “ABC100” is available And a trade is created with mandatory-trade-fields set to “mandatory-trade-values-A” And the trade is updated with instrument-id “ABC100” When the user submits the trade Then the processed trade is acknowledged as accepted And the processed trade has it’s fields user-set-fields available

Fault ModelingFramework to discover & address potential faults

@ Requirement@ Design@ Development

Tiered containment

Active MonitoringSynthetic usage probes

Cross Company – Annual Millennium Excellence Audit

Team – Monthly Engineering Review

Thank You!