• A project vision statement. This should be written by the team and approved by the customer. It should be short and sharp. Perhaps imagine it as a piece of marketing literature. To get this right will take many drafts - I want to see them too.

• A public web site for the project, with a link to the vision statement and a nice logo, with links to all the project documents.

• A solid start constructing scenarios. These need not (yet) be formal use cases. We're looking now for narratives with as much detail as possible (from the user's point of view).

  Many small stories are better than few long ones. If you write long ones they should have identifiable small pieces. That way you will be able to construct verifiable milestones for your delivery schedule.

  Screen prototypes may help you formulate your ideas and communicate with your customer, but they are not sufficient. You need prose too.

  You could begin looking for a use case template (see link on course home page) that suits your needs.

Back to the cs681 home page.