nUse cases are one way to document the functional requirements of a system
nThere is no one
standard, so each organization needs to decide which sections to implement
nUse cases should
not be used as a design document--they describe what the system needs to do, not how to do
it.
nA high level design process (and meetings?) should precede any actual code development.
n