K-Team Minutes

SDD Internal Review Meeting

21st October 1999

11:00 - 01:00 PM

Attendees:
Joanna Araminta, Victor Leung, Joel Brakey, Michael Hart, Dean Cortinovis, Long Tang
Apologies: 
None
Secretary: 
Joanna Araminta


This Meeting
  1. OVERALL
    • Remove all references to the SADD file. State that the architectural design is now included as part of the SDD.
    • Add a glossary
    • Fix up section references so that they all conform to the (see Section x.x) standard
    • Make all references to teh MultiMahjongClient and MultiMahjongServer modules as MMC and MMS module (after first use)
    • Get rid of all ?'s
  2. TITLE and Introduction
    • Fix up the abstract (architectural only mentioned)
    • Update TOC and TOF
    • Fill in the QAR as Lachlan
    • Add a paragraph referencing the Design Notebook
    • References to Swing and RMI in the glossary
  3. Design Methodology
    • Clearly explain which stages in the Booch method correspond to which section in the SDD
    • Add web references for the Booch methodology for further reading
    • Split K-Team's implementation into 2 sections: architectural and detailed phases
    • Add traceability to the Booch process at the end of each step in K-Team's implementation
    • Talk about how we used prototyping in the design process
    • Mention Mahjong specific algorithms in the steps of refinement
    • Also mention how packages and stubs fit in with our design process
    • Define UML in the glossary
  4. Design of the Modules
    • Update al diagrams to reflect our latest design
    • Add Shared module and relate it to the MMC and MMS
    • Update module descriptions
    • Change the header to "Module Designs"
  5. The Class Designs
    • Change section heading (get rid of "The")
    • Explain how the class description fir in withe the architectural adn detailed design
    • Justify the used of Javadocs and explain how it is used in the SDD
    • Explain about it being architectural by browsing just the SDD and then becomes detailed when browsing the Javadoc generated files
    • Update all class descriptions of each module
    • Add screen shots from prototype and use an image map to add llnks to the various classes in the UserGui
    • Add responsibilities from the SADD.  Allow for multiple links from each description
    • Double check all SRS references
  6. Use cases
    • Give an introduction to the section explaining how it fits in with our steps of the design process
    • Double check all SRS references
  7. Scenario Diagrams
    • Add a description as to what scenario diagrams are
    • Add SRS references
    • Add scenario diagrams for the Game, Co and Shared modules
    • Get rid of module headings as they are not necessarily just intra-module dependent
    • Links should be made to the full size images
    • A brief caption saying "Click to enlarge"
  8. Traceability
    • Add references to the use cases and scenario diagram sections


Client Minutes    General Minutes    Review Minutes    Supervisor Minutes