OK. You've detailed the requirements. You've built the use case model, detailing all of the basic and alternative flows to realize those requirements. You've completed the mock-up of the UI, and written requirements and scenarios on reusable UI controls. You've created the sequence diagrams and designed all of your classes, database tables, and stored procedures.
Now what?
I'm interested in hearing about the most effective ways other people have found to communicate all of the wonderful information in EA to the developers.
What I'm envisioning is that I'd create a project plan that would direct them in (generally) the right direction, as follows:
1. I make a project plan that outlines the use cases to be implemented as a deliverable.
2. For each of the use case "deliverables," it will include a list of the associated UI screens that are required (this is so the UI designer can be assigned the tasks of mocking them up) as well as general tasks such as "stored procedures," "UI controls," and "business classes."
This is all great. What I'm trying to figure out is the best way to deliver this stuff. I really like the HTML documentation, but there's no way to search! How is my developer going to find the "Create Widget" use case buried down 2 package levels deep? (Use cases\Widget Management or something like that)
Do I nix the HTML idea and just create RTF docs for each use case? This is a pain, because the docs are created at the package level.
Basically, the problem I'm trying to solve is the developer starting work on a use case, and instantly being able to put his hands on all of the information he needs.
I wonder if the easiest way is to simply associate the use case with all of the classes, UI screens, and requirements. Then, the developer could just click on each hyperlink on the use case page to get to the associated information.
Anyhow, I'm not sure of what the right answer is, so I'd love to hear how others have "packaged up" the information the developer needs to implement a particular use case.
