Measuring FileMaker System Complexity
System complexity is the strongest predictor of how risky and expensive a change will be. Measuring it gives you better estimates and safer planning.
Signals of high complexity
Large numbers of tables and relationships, deeply nested scripts, and high coupling between modules are all signs that complexity is increasing.
Why complexity grows quietly
Most FileMaker systems grow incrementally. Each individual change feels small, but the cumulative effect is a system that's hard to reason about.
Quantifying complexity
Counting scripts is not enough. Useful metrics include script depth, fan-out (how many scripts a script calls), and table touchpoints per script.
Acting on the data
Once you know where complexity lives, you can plan refactors, isolate risk, and make better decisions about what to change next.
Related
Change Impact Analysis