Reducing Complexity in OTC Clearing

We are developing solutions for the OTC Clearing market place that will lead to reductions in cost, complexity and operational inefficiencies for market participants.

Working software is the primary measure of progress - agile manifesto

Below is an extract of a bunch of simple statistics from product development to show how things are progressing at REDUKTI.

Artifact Type Language July August September October November Jan-17 May-17
Design Documents English 2 docs, 797 words 5 docs, 2414 words 5 docs, 2927 words 7 docs, 3736 words 10 docs, 5891 words 12 docs, 9837 words 16 docs, 11350 words
Source Code C++ 21 files, 1338 lines 28 files, 3868 lines 28 files, 3764 lines 56 files, 17386 lines 63 files, 20367 lines 69 files, 22295 lines 72 files, 23642 lines
Source Code C# 58 files, 4133 lines 59 files, 5540 lines 94 files, 19733 lines 94 files, 19733 lines 112 files, 24987 lines 139 files, 29844 lines 165 files, 34968 lines
Source Code XAML 19 files, 670 lines 19 files, 670 lines 26 files, 875 lines 26 files, 875 lines 30 files, 1135 lines 34 files, 1250 lines 34 files, 1253 lines
Interface Definitions Protobuf 14 enums, 49 messages 18 enums, 68 messages 39 enums, 121 messages 43 enums, 134 messages 49 enums, 186 messages 54 enums, 203 messages 59 enums, 239 messages
Scripts Lua       4 scripts, 512 lines 4 scripts, 512 lines 4 scripts, 512 lines 35 scripts, 1767 lines

Above tells a story of course.

We are making heavy use of Google Protobuf technology. The statistics exclude any generated code for the Protobuf definitions. Also excuded are external projects used.

We are using Microsoft’s XAML technology to build the user interface. I will explain the rationale for this in another post.

Further updates to follow.