Abstract
AbstractThree kinds of documentation are examined: summary documentation describes the intent and nature of the program; detail documentation gives all the information the user needs to put the program to work; intraprogram documentation is information written into the program to inform the user or programmer. The need for intraprogram documentation occurs at four different times: in the initial design period; during debugging; as the program and system evolve; when it is necessary to adapt the program to other systemsThere are several means for providing intraprogram documentation. There are comments which can be placed in the header, on each line, at the beginning and end of a subroutine. Also noted is the important use of space for making the comments easier to read and for separating chunks of the program. Special symbols serve the same purpose. Examples are provided to bring home these points.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
