Laserfiche WebLink
the source code for the model. HTML and UNIX man page source files will be maintained under <br />revision control (see Task Memorandum 1.05-20). <br />It is anticipated that documentation that is developed for new CRDSS products (e.g., database <br />Mosaic <br />utilities) will reside only as documentation and UNIX man pages. Such information can be <br />viewed on-line and can be printed. <br />3.0 CONCLUSIONS AND RECOMMENDATIONS <br />The following recommendations are made related to model documentation: <br />Model documentation for each model will be available in on-line and hard-copy forms. <br />? <br />On-line documentation will consist of overview information for users and technical <br />information for developers (and interested users). Hard-copy documentation may be <br />generated from existing documentation by using PostScript output from the original (e.g., <br />use WordPerfect to create a PostScript output file) or will be printed from on-line <br />documentation using standard methods available on the workstations (e.g., from within <br />Mosaic <br /> or by using UNIX man pages). <br />Mosaic <br />The public domain program will provide the entry point to display on-line <br />? <br />documentation for models. Overview material will be provided which will reference <br />existing documentation that has been ported to HTML format, preformatted ASCII files, <br />and viewable PostScript files. UNIX man pages will be used for technical documentation <br />such as a summary of how to execute models (program names, etc.). <br />The extent of the documentation for each model will depend on the extent of existing <br />? <br />documentation and the level of effort needed to provide documentation in formats for <br />Mosaic <br /> and UNIX man pages. It is anticipated that providing model documentation in a <br />brief man page and/or a PostScript file created from existing documenting will not require a <br />great deal of effort. However, implementing a full set of documentation for each model <br />will require that cost-effective documentation conversion procedures are outlined. In some <br />cases, this will mean that only PostScript versions of the documentation are available, <br />rather than full hypertext versions (this applies to the MODSIM documentation). This is <br />because some of the formatting in existing documentation (e.g., equations, figures) cannot <br />easily be translated to other formats. <br />The goal of all documentation efforts will initially be to provide complete content in <br />documentation rather than concentrating on providing extensive hypertext. If deemed cost- <br />effective, more extensive hypertext will be added to documentation. Based on RTi' initial <br />review of documentation, it appears that MODSIM documentation will consist primarily of <br />wp2x <br />existing documentation dumped as PostScript or converted to HTML using the <br />program. The CU documentation will contain preformatted ASCII material taken from <br />existing sources but will contain hypertext HTML files developed for the CRDSS. The <br />AOP and CRSM documentation will consist primarily of overview material. Screen dumps <br />of the model interfaces will be incorporated into documentation where appropriate. All <br />models will have man pages. <br />3 <br />A275 06.29.94 1.17-1 Malers <br />