Rapid Application Development

Hi All,

I work in a BPO company where we have a small software team of 3-4
programmers. Because our core competency is BPO, our software team has
been functioning without any docuemnation till now. We are unable to
follow the regular SDLC documentation because we need to develop
applications very quickly based on the deadline from the Top
Management.

I heard about Rapid application development and wanted to know if there
is a way of structured documentation process for Rapid Application
Development. Our main need to document this is to ensure that the
requirement is correctly understood by us, to be able to transfer
system understanding to the new programmers quickly and maintain
quality. However, we are never going to be able to follow the detailed
documentation structure of flowcharting, algorithms, dfd's, SRS,
modular breakdown documents, testing reports etc.

Is there a way to skip a few of these and still maintain quality
documentation to meet the above mentioned goals.

It would be great if someone can help me out of this.

Thanks,
Yash

.

Relevant Pages

  • documentation in SDLC
    ... I work in a BPO company where we have a small software team of 3-4 ... is a way of structured documentation process for Rapid Application ... system understanding to the new programmers quickly and maintain ...
    (microsoft.public.vb.general.discussion)
  • Re: documentation in SDLC
    ... I work in a BPO company where we have a small software team of 3-4 ... is a way of structured documentation process for Rapid Application ... system understanding to the new programmers quickly and maintain ...
    (microsoft.public.vb.general.discussion)
  • Re: Your opinion on the Agner fog manuals.
    ... Thats exactly the reason for exposing it. ... why gives him the right to teach "advanced assembly programmers"? ... full applications in assembly language. ... Feel free to write the comparable documentation that preaches whole ...
    (alt.lang.asm)
  • Re: Which do you prefer?
    ... or because of a business reason. ... programmers have quit. ... developers recognize it as a "stable sort" just by reading the code? ... An automated system for producing printed documentation ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Which do you prefer?
    ... or because of a business reason. ... Robin S. ... programmers have quit. ... An automated system for producing printed documentation ...
    (microsoft.public.dotnet.languages.vb)