.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
 
Sign In
Register
 
Win Surprise Gifts!!!
Congratulations!!!


Top 5 Contributors of the Month
david stephan

Home >> Articles >> Architecture/Pattern >> Post New Resource Bookmark and Share   

 Subscribe to Articles

Essential documentation in projects

Posted By:Santhakumar M       Posted Date: November 25, 2010    Points: 50    Category: Architecture/Pattern    URL: http://www.dotnetspark.com  

In the previous article we discussed the various SDLC lifecycle models. For every stage in the model we have documents created according to phases such as
 

Essential documentation in projects

In the previous article we discussed the various SDLC lifecycle models. For every stage in the model we have documents created according to phases such as

Requirement stage:

-          Use case document

Design stage:

-          Technical document

Build stage:

-          Source code

Test stage:

-          Test result document

Deliver stage:

-          Sign off document

There are different documentation for every project and these documents change from company to company and project to project.

For example,

                  Some company will have 3 documents and some will have 12 documents in a project depending upon project manager or the policy of the company to execute a project

          Requirement document

          Estimation document

          Use case document

          Technical document

          Test plan document

          Source code

Requirement document:

          A requirement document can be a single English document, probably a recorded audio or video conversation or can be a complicated use case.

Estimation document:

          After getting requirement from the user we can judge cost for the project.

Use case document:

          This is a section of UML which basically describes in detail the requirement document which serves as an input to the Design stage

Technical document:

          This document contains detail of how the project being executed such as pseudo code, class diagram, objects diagram, etc.

Test result document:

          This document is written by the testers which describe the test plan which needs to be executed and thus giving project a green flag to production.

Source code:

          This is not basically a document but one of the important deliverable which maps to the execution phase of SDLC cycle.


 Subscribe to Articles

     

Further Readings:

Responses

No response found. Be the first to respond this post

Post Comment

You must Sign In To post reply
Find More Articles on C#, ASP.Net, Vb.Net, SQL Server and more Here

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend