one of the basic purposes of system architecture is to partition a system into one of roles and responsibilities. For instance, software belongs to the ISV; co

one of the basic purposes of system architecture is to partition a system into one of roles and responsibilities. For instance, software belongs to the ISV; configuration belongs technicians, and business rules belong to analysts. Since each have their own core competencies and access to tools, one would not expect the system analyst to write the rules out in C++ even if the system was developed in that language. However, the author is right in that traditional programming processes still ought to apply, and many in non-programming fields will have to learn this skill before they can execute this properly. Rule engines like Tibco actually provide tools for users to perform regression tests. In fact, in the game world, Chris Crawford had an interactive story engine that will perform regression tests on their storylines - which I find very cool.