•  Develop iteratively - and use agile methods and business rules together.

•  Manage requirements - but writing better requirements is a false hope so use business rules too

•  Proven architecture - business rules are well proven already

•  Modeling - they make the point that models need not be graphic and, in this sense, rules are a form of model

•  Continuously verify quality - rules are easier

•  Manage change - or come to love change

•  Collaborative development - Collaborative Business Engineering

•  Look beyond deployment - think about change-time

•  Deliver working software regularly - rules is great for this

•  Manage risk

•  Enterprise business modeling

Compliance and business rules are described as important here. While I agree, I do worry that the EUP implies that business rules are only an enterprise documentation thing. I feel that this is one use of rules but that production rules (business rules executed in production systems) are the best way to implement these high level rules. The authors also focused on policies that"stand the test of time" but my experience is that the details may vary a lot. For example, an enterprise rule to "pass postage rates through without a profit margin" has details that change every time the postage rates do. I did like their focus on automating repetitive tasks as I think this leads naturally to a focus on decisions.

•  Enterprise Portfolio Management

•  Enterprise Architecture

I particularly liked the idea that "modifiability" should be considered as part of an enterprise architecture. Far too few organizations do this well and fail to differentiate between stable services and much more changeable ones.

•  Strategic Reuse

Again I liked the called-out focus on this. Without a real plan no reuse is going to happen. I also like his definition of something not being reusable until it has been used 3 times! to the various kinds of reuse defined I would add rule reuse

•  People management

•  Enterprise Administration

•  Software Process Improvement

Another good one. A timely reminder to all that you should keep improving your software processes. Check out this post on lean manufacturing techniques in development too.