Smart questions
Smart answers
Smart people
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Member Login

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips now!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

Join Tek-Tips
*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

LINK TO THIS FORUM!

Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.
Just copy and paste the
code below into your site.

Partner With Us!

"Best Of Breed" Forums Add Stickiness To Your Site
Partner Button
(Download This Button Today!)

Feedback

"...Really appreciate your site. Really good site for learning what others do when they run into problems. You guy's are great!!!..."

Geography

Where in the world do Tek-Tips members come from?
RekhaShah (Programmer)
16 May 03 8:27
Hi

Could someone help me with the basic documents that have to be maintained during the SDLC of a product. I have gone through many sites and they provide such a lot of documentation that it does not seem to make sense.

Thanks
Rekha
DonQuichote (Programmer)
16 May 03 9:01
Depends on what methodology you want to follow. Do not overdo it. There are large forests cut for documentation that was never read and even more for documentation that has never been up-to date.

The "extreme programming" methodology (see http://www.xprogramming.com) therefore states that you must not make any unnecessary documents and sees the source code as the most important documentation ('cause it is per definition up-to-date).

Best regards
RekhaShah (Programmer)
17 May 03 0:01
Hi Don,

Don't we all just plan that we should maintain a few necessary documents. Somewhere down the line all the "I-think-its-important" documents just come along.

I do not seem to think that Xprogamming is right for my team. We are more of the traditional prototyping folks!!

I just need the elementary documents.

rekha

DonQuichote (Programmer)
19 May 03 3:35
Well, the only document that is really needed in whatever form is, in my opinion, a document that describes what the customer wants and what you are going to deliver. That document is difficult enough as it is. If you don't have incremental development, the client must imagine the program beforehand, without much knowledge of programming and user interfaces. And you must imagine the useage beforehand, without much knowledge of the clients exact working methods and processes. Needless to say that communication is vital here. You may have to draw some screens or build a non-functional prototype, just to be sure you are talking about the same things.

Other documents (database schema, UML diagrams, etc.) may come in handy, but I would only make them if I needed them. The client will probably not ask for it, so they are for your own convenience only.

The same appies for the user documentation. For an intuitive application in an easy process, you don't need it. But for more complex applications or processes, a helpfile and/or a printed manual can be necessary.

Best regards

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close