In Part 1 Dave Harms introduced the idea of a feature toggle library, and wrote that the starting point for Clarion development should not be the data dictionary. In many cases the data dictionary comes at the very end of the process. But If the data dictionary doesn't come first, what does? There are a lot of different answers to that question, depending on what kind of application you're developing, the stage of development, and the scope of the requirement. In Part 2 Dave demonstrates his favorite way to design small- to medium-sized chunks of business logic.