Need advice on standarizing documentation in a project
Hi all:
this is pretty much a tipical situation in everybook in OOA/D however
come to the practice the implementation is cumbersome.
this project has grown from one to four developers, theres no standard
documentation or documentation at all except for a few written
documents in business level, how can we move from that scenario to one
where there is standard documentation, there is a design phase, etc.
I am lost, any guidelines more than welcome.
.
Relevant Pages
- Re: How does pydoc parse code?
... > standard documentation, I am not sure how pydoc interprets its input. ... > In its basic operation it evidently looks at the first string literal in ...
(comp.lang.python) - Re: The Schneider Scam
... You can't fail somebody for driving, ... him the practice time, or you don't allow him to complete the course. ... I don't know about a dumbell, since I asked you to e-mail me documentation. ... First of all Schneider training isn't free, ...
(misc.transport.trucking) - Re: Filtering a tachometer generator
... Jerry Avins wrote: ... > As for documentation, it has been my practice to write down what needs ... > produce working code from it, ... It has been common practice in the places I have worked not ...
(comp.dsp) - Re: My first C# project
... With practice, I found that I could write easily understandable code in only 10% more time than rushing and writing code 'normally'. ... High-level documentation is stored elsewhere and documentation saying what a few lines of code do is redundent if you make sure that those lines express what you're doing in a *clear* way. ...
(microsoft.public.dotnet.framework.windowsforms) - Re: unittest: Calling tests in liner number order
... For my major project I've got my own test case extraction ... freedom to be quite useful in thinking about the test case. ... signal that it's good practice to allow dependencies between tests. ... documentation with a caveat that it's not good practice, ...
(comp.lang.python) |
|
