Documentation (1 Viewer)

coold00d

New Member
Joined
May 4, 2003
Messages
1
hey guys i just found this site and thought it was really cool how you help eachother out

i was wondering if anyone could provide me with a bit of help :confused:

mmm the questoin is

"Why would you keep documentation on the progres made during building the solution"

(I think its talking about the software development cycle here)

can any1 help? if it sounds familiar its frmo the preliminary carole wilson software design book :p
 

del

Member
Joined
Jul 8, 2002
Messages
412
Gender
Undisclosed
HSC
N/A
- so you know how the solution is progressing, whether you are on track for time, budget etc

- also so that what you have done is documented. for example you may make a modification to the code, then later on realise it doesn't work as well as intended and the original code worked better. So instead of trying to remember what was changed, you can look back through the documentation to see what changes you made


hm yeah there just 2 examples....
 

yoshi

Member
Joined
Feb 24, 2003
Messages
157
Originally posted by coold00d
"Why would you keep documentation on the progres made during building the solution"
Maybe they would like some realistic answers in the HSC exam, might as well try it;
So if you are sued for negligence as a contractor, you can defend your actions as a programmer [it does happen].
 

Users Who Are Viewing This Thread (Users: 0, Guests: 1)

Top