Elaboration is all about making sure that our project is solving the right problem and solving the problem in the right way . When we move into Elaboration we get a project area in DevHome. Project Wikis have a basic structure to organize the few main artifacts that are used in a Fishbowl project. The core artifacts are the Vision Statement, Risk List and Use Cases. Once you have a project area, the first thing to do is put a copy of your proposal in the Wiki for historical reference.
Every project implies risks, both inside the software and in external forces.
It is important for the project owner to recognize these risks, and perhaps plan accordingly. The Risk List captures these risks associated with the project and the proposed solutions to those risks. The broad outlines of the project captured in the Vision Statement are then fleshed out in Use Cases. A good way to handle the description is to write it in a user documentation style as if it were to be consumed by the actor. If you've used Use Cases in an organization before then you know that there are endless opinions on how they should be done.