The purpose of this excersice is for the team to get a clear
idea, and buy-in from everyone, on what the project will be and
how it will be developed as well as how you will work together as
a team. You should read Chapter 4.
- Drawings of how every window in your program will look
like. You can use pen and paper: just take a digital picture and
upload it to picasaweb then link to it from your wiki.
- Set of use cases describing how a user will interact with your program.
- Describe how ignorant users will interact with your program.
- Agreement on IDE and programming languages.
- Agreement on third-party libraries to be used.
- Have you read and understood the library's documentation?
- Have you installed the svn plugin for your IDE?
- Have you defined coding conventions for names, comments, and layout?
- Have you defined specific coding practices? how will error conditions be handled? how will security be addressed? how much will you consider performance while coding?
- What are the specific steps a programmer must go through before checking code into subversion?
- Will programmers work in pairs, or individually?
- When will your team meet? for how long? will there be food?
- Will programmers write test cases for their code before writing the code itself?
- Will programmers write unit tests? (YES)
- Will programmers step through their code in the debugger before they check it in?
- Will programmers integration-test their code before they check it in?
- Will programmers review or inspect each other's code?
- Will you be using a unit-testing library? (JUNIT)
Jose M Vidal
Last modified: Fri May 16 15:01:49 EDT 2008