Documenting Stuff

[wendigo100]

ffs its only documentation

Oy! Nothing is only documentation!

icw, they must already have a method of documenting whatever it is they are asking you to do. First thing you do on Monday is ask them to show you how they have been doing it so you can fall in with their standards.

[andy]

ffs its only documentation

[cojak]

And don't forget your version control, obv...

[icw]

Thanks

[MrsGoof]

They've probably got a method / document format they like, so it'll be easier to just follow on from that.

[icw]

Thanks for the suggestion Kramer. It's not anything high level and it's not software development. It's just changing a few data entry practises and ways in which they use a particular software.

[kramer]

Have you looked at MSF???

[icw]

Thanks for your help guys

[Pondlife]

You sure your not out of your depth doing this?

[Troll]

I am starting a contract on Monday. I'll be reviewing systems and making some changes. Of course they want it all documenting. I am trying to figure out if there is a standard or accepted practise for documenting stuff. i.e. is it enough just to create a folder with subolders containing various word docs with the changes in. Or should it be by date order or something else.
Anyone used onenote to document stuff.

Any ideas and advice gratefully accepted

thanks
ICW

You sure your not out of your depth doing this?

[icw]

I am starting a contract on Monday. I'll be reviewing systems and making some changes. Of course they want it all documenting. I am trying to figure out if there is a standard or accepted practise for documenting stuff. i.e. is it enough just to create a folder with subolders containing various word docs with the changes in. Or should it be by date order or something else.
Anyone used onenote to document stuff.

Any ideas and advice gratefully accepted

thanks
ICW