agile, analysis, best practice, business sponsors, conflict, data design, design, functional decomposition, iterative, lifecyle, management, model choices, modeling, old school, perspective, planning, process, requirements, scope, state, state transition, state transition diagrams, swim lane, use case, visual
Since when did Swim Lane Diagrams take the place of more rigorous Software Engineering Requirements gathering models like: Process Models, Data Relationship Models, State Transition Diagrams, Use Cases and Event Models?
I’ve been managing several smaller projects lately and if they have any kind of Analysis efforts and documented Requirements, they are only represented in Swim Lane diagrams that are syntactically broken! And, do not have any written or graphic supporting materials to explain any of the intent of these Swim Lanes.
How can ONE diagram be a defensible proof that we have investigated all perspectives of a proposed solution and that we have proven to ourselves, with some level of reliability, that we have a complete and cohesive solution? I, for one, think that we CAN’T!
Ed. I’ve just started on this line of thought and will have more shortly. bgbg