While code size is not a great measure for software, the sizes of the core and intralogistics kernel code modules (with some other explanations and measures), are presented below.

Files and lines are the number of C# files and raw code lines in the package source. “Maintain” is the Visual Studio maintainability index, which the article explains better than I even care to. Complexity likewise is a Visual Studio metric based on “amount of decisioning logic in a source code function”, summed up over each code class and package. Higher numbers means more things are decided (more branching on conditions and therefore more potential code paths that can be taken on any call). The “class coupling” numbers are rather abysmal by performance metric standards (even if I drill into the class and functions units themselves), which is why I often don’t care for those metrics.

Since maintainability is calculated from the other metrics , the high complexity and coupling numbers seem to show that overall the maintainability numbers are pretty good, being “least maintainable” in the services packages. These integrate other packages and perform the most useful intra-logistic and kernel-specific “work”, so that shouldn’t be surprising.

Overall, the size and complexity increases from the core through users, operations, and inventory. Each builds to a degree on the others, so the less dependent ones has less complexity. Fulfillment and stockflow are relatively complex, but rely heavily on the inventory management packages, so do not reach the same heights of complexity.