I about "busted a gut" laughing so hard at the first reason Roger Session listed for IT solution complexity.
I mean functional modeling using the industry standard UML techniques ( Use Cases and Activity Diagrams) is BASED upon a forced, artificial partitioning. Poor partitioning, especially for a larger scale systems, is a given. If a poor partitioning is a given going into a project, why bother to recognize it as a problem? Why not just put our fingers in our ears and repeat out loud "La, La, La, La" at any mention of the need for proper partitioning?
I could go on at talk about the UML and next item Roger listed Decomposition failures, but it is just too much to - just too much.
Tears In My Eyes,
Tony
brought to you by enabling practitioners & organizations to achieve their goals using:
enabling practitioners & organizations to achieve their goals using: