Appendix B: Design Diagrams

The design diagrams in this section are guides to designing your own Mooglesuite. They are not intended to be complete, authoritative, or required. You MAY choose to follow them or you MAY choose to develop your own design. NOTE These diagrams are not complete. Additional methods, fields, and functionality will be necessary to produce a working Mooglesuite.

Figure 1: High-level decomposition of the Mooglesuite, including information flow directions. Note that this is an informal sketch and not a UML diagram.

[width=7in,angle=-90]pics/top-level-decomp

Figure 2: UML Diagram for the WEB DATABASE module. Note that the types given are conceptual and do not necessarily represent the actual types used in a real implementation. For example, the items denoted as Sets might be implemented in terms of a MondoHashMap with null values.

[width=5in]pics/webdb_decomp

Figure 3: UML Diagram for the URLMap class referenced in Figure 2.

[width=2.5in]pics/urlmap_class

Figure 4: UML Diagram for the MSpiderprogram.

[width=6in]pics/mspider_decomp

Figure 5: UML Diagram for the Moogleclient program.

[width=6.5in]pics/moogle_decomp