[thisiswrongggg]

I'm not talking block diagrams here. I'm talking about fully fleshing out issues down to the level of functions inputs and outputs(1). So that managers will be pleased with the "planning" and "sizing" and some other buzzwords...

(1) Which (outputs) are another bitter story since we are building on top of legacy code that is working with side effects from head to toes. But let's not touch this can of worms.

[greenbit]

Yeah, that's nuts. That's way beyond where even the 'detailed design' phase should go. I've been on projects where DD has delved to the level of identifying individual classes, and I think even that's a bit of a reach. But managers do love their metrics.