The implementation of the design—the writing of the code that manifests it—will be included in the plan. It is typically the largest module in the plan. Projecting the number of hours it takes to write code is also typically one of the most challenging, and poorly executed parts of planning. For these reasons, the design should be broken down into theoretical design components that will take no longer than five hours to implement.

Show us some complete form of heirarchical design that groups individual five-hour-or-less implementation tasks together into design modules, the data flow between modules, the logical flow of the programs, the algorithms used, the file structures, the method interfaces, the network design, the security model, and so on. UML design images (but without designation of five hour implementation tasks) Typically you will have several walls full of these.

Design presentation format

• Ryan Ferretti Example
  
• Globetrotter group example.

(P = presenter)

1. P presents a top level slide (e.g., level 0 DFD, context diagram) which shows the full project design. Very high level, very complete, global coverage. Brief discussion. P Teaches us the three or four main components of the design.

2. P "clicks on" a portion of the design [which contains a hyperlink] to retrieve a more detailed design representation [level 1] of a portion of the project, with brief explanatory comments about how that portion of the project works.

3. [ if you have level-two diagrams:] P "clicks on" a portion of the more detailed design to retrieve a very detailed design representation (level 2) of a very specific part of the project, with brief explanatory comments.

4. P "clicks on" a portion of the very specific design representation and retrieves the code implementation for that module.

5. P then returns to the top level and asks an audience member to pick ANY displayed module, at each level, and repeats the cycle above, down to the level of code, with brief explanatory comments. [Note, early in the project you would not likely have all the code written, so just present a stub for that terminal link.]

6. Notes: During the first iteration P can guide the demo toward the most interesting piece of the implementation, and along the way familiarize the audience with the procedure. The second iteration, where the audience is free to chose any module "proves" that the entire project can be viewed from the highest level design view down to the code implementation. The whole process takes, possibly, two minutes, which makes a strong statement in a short amount of time.

   The second interation may have to be finessed during the presentation. Presentation manager, plan around potential risky choices by the audience!

7. Comments:
   • Data Flow Diagrams (DFDs) are one way to express design ideas, but there are others as well.

   • It is a common mistake to have fonts that are too small for display in the presentation design graphics. Check your fonts on the overhead, in class, before you present.