I feel.....overwhelmed. There's so much to do, so little I understand. I dont know where to begin and where to end. I'm talking about the bloody documentation!
There are just so many documents that have to be prepared for my project. I really dont know where to start. Do I do the Customer Requirements Analysis or the Functional Specification Document or prepare the test cases and the test logs? Or should I fill in every quality document that is available? Do I draw the Entity Relationship diagram or the Data Flow diagram or the Sequence diagram? I'm clueless :-(
The quality people are crazy. It really does not matter if the project works or not, it just has to follow company C quality principles.. Know what that means? No matter what you do, there should be a piece of paper( in a pre-defined format) saying that you did it.
It looks like I wont have any time to go near the actual code. I'm just going to be very busy preparing documents. It seems like just an awful waste of time :-(
Subscribe to:
Post Comments (Atom)
3 comments:
hehehe, 'c' is supposed to be creating paper less offices for its clients.
i know what u mean when it comes to project and documentation...
i'm doing my final year thesis on a network.. and both configuration and documenting it is such a hayvok...
i can just get a headache thinking bout it!! hahah....
Welcome to 'Software Engineering'.
In my second year at university we had to 'build' some software. Turns out- the documentation was more important than the code. So we spent 2 months on SPMP, SRS, SDD etc etc. And did exactly 1 week of coding in VB with MS Access(I don't consider VB as programming). It was a major disappointment.
Well, good luck anyways, have fun :-P
Post a Comment