Guide Implementation

• Can I implement from this?

  • Define the data types

    What does the data look like - format, type.

  • Define the inputs and outputs.

    Reading the password

  • Define the transformations.

    Create a new group - how? what's involved?

• But, don't implement.

• Can I generate test cases from this?

  What are the error conditions.

Be consistent

• Pick one of functional or oo design and stick with it.

  It should be clear from your design which you're using.

• Don't mix terms or concepts.

  Function oriented design, . . ., in a class called "group."

• Follow the requirements document.

  Major features of the requirements should be in the design.

Strategy

• Design the overall architecture.

  One big box and arrow diagram.

• Pick one or two components and describe them in more detail.

  Define everything: inputs, outputs, transformations.

  Remember implementation.

• Make sure you answer the obvious questions.

  Go back to the informal spec and make sure.

This page last modified on 21 February 2001.