Larry Osterman had a good post the other day about the *bilities. He was pointing out to the developers that read his blog that you need to worry about serviceability, accessibility and all the other good stuff.
A corollary of this is that you need to understand what each of these *bilities means and what it does and doesn't give you.
A capability of enterprise systems is transactionality. We often loosely describe it as the thing that allows us to make sure that "either everything happens or nothing does".
David Currie has an excellent post that points out that you need to be a little more subtle than that. He is giving another example of how there is no susch concept of "simultaneous". Not in physics and certainly not in computer science.