Adrian:
Data Flow Diagrams or Use Cases?
It has always been my experience that , especially for larger scale efforts, proceeding in a pure top-down fashion (i.e., STARTING with a Context diagram that is anywhere near adequate and then proceeding to lower level diagrams) is not possible. If an analyst is on a larger scale project where someone, anyone, has, at the start fo the project, an adequate top-down understanding of the essential functionality within the scope of the system, I would say that analyst is in a very rare situation. Recognizing this unfortunate but typical reality is key, as it helps explain why good Context diagrams, especially for larger scale efforts, are so rare in the business world.
It has always been my experience that the analyst(s) need to proceed from somewhere in the middle and then go up levels of abstraction. In other words, we must first create some lower level data flow diagrams and then summarize them upwards into a Context diagram.. I know, if we could start from a context diagram, analysis would be alot easier.
At what point can we switch to use cases? That point is debatable. However, for larger scale projects, the required need for data flow diagrams often extends well beyond the Context diagram.
Tony