James Taylor's Decision Management

Second change for Application Development 2.0 is declare don't code.
The second change is to move away from coding things procedurally to declaring them. Declarative and model-based approaches create more independent artifacts, minimizing the impact of changes on the rest of a system when a piece is changed, and are inherently more approachable for non-technical folks. Replacing code with process models, decisions described in business rules and reporting built using point-and-click dashboard or reporting tools dramatically increases the ability of non-technical users to participate while also taking advantage of tools suitable for specific problems and building a true composite application.
Here's a couple of links you might enjoy:

• Habits of effective developers
• Some thoughts on the fallacies of business process execution
• Composite applications, business processes and decisions