3. Create a code specification
uBefore you start writing code, you need written specifications.
uA good code specification should address the following questions:
ØWhy is this code or modification being written (in
business terms)?
ØWhat procedures will be created?
ØHow will these procedures be named?
ØWhat modifications to the database are required?
ØWhat are the detailed design constraints, if any?
uGoal is to create functioning code - not create a large
pile of documentation that few people will read.
