This week's book giveaway is in the General Computing forum. We're giving away four copies of Arduino in Action and have Martin Evans, Joshua Noble, and Jordan Hochenbaum on-line! See this thread for details.
1. Assumption, 2. A Class Diagram 3. A Component diagram 4. Sequence or Collaboration diagram for each use case
My questions are:
1. Shall I add the reason for my design choices under assumption or shall I create a new sec.(say: Design approach ) and explain design choices.
2. I feel that component diagram can be broken into 3-4 simple component diagrams. Having all components in a single component diagram is making it messy. But just wanted to make sure that SUN do not enforce for having a single component diagram