URL
https://opencores.org/ocsvn/socgen/socgen/trunk
Subversion Repositories socgen
[/] [socgen/] [trunk/] [doc/] [src/] [guides/] [guide_documentation.html] - Rev 124
Go to most recent revision | Compare with Previous | Blame | View Log
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <meta http-equiv="CONTENT-TYPE" content="text/html; charset=UTF-8"> <title>Documentation Guidelines</title> <meta name="GENERATOR" content="OpenOffice.org 3.0 (Linux)"> <meta name="CREATED" content="0;0"> <meta name="CHANGED" content="20100309;9322200"> <meta name="KEYWORDS" content="start"> <meta name="Info 3" content=""> <meta name="Info 4" content=""> <meta name="date" content="2008-01-08T12:01:41-0500"> <meta name="robots" content="index,follow"> </head> <body dir="LTR" lang="en-US"> <div id="toc__header" dir="LTR"> <p><br> <br> </p> </div> <h1><a name="socgen_project"></a>SOCGEN Project</h1> <h2><a name="manifesto"></a>Documentation Guidelines</h2> <p><br> <br> </p> <p>Every component must include a minimum set of documents. This consists of a ./doc directory that contains a html file named "index.html". This file is the link that all external users will use to access each components documents. Those documents consist of:<br> </p> <p><br> </p> <ul> <li>A Socgen datasheet for the component and each of it's variants</li> <li>Application notes detailing how to use the component.</li> <li>Any 3rd party produced reference material needed to support the component</li> <li>Test plans detailing how the component rtl was simulated and what was tested.<br> </li> <li>Test plans detailing how to synthesis the component and prove functionality in silicon. <br> </li> </ul> <p><br> <br> </p> <p>All documentation source will be stored as html files. A pdf will be extractred from each source and also included. <br> </p> <p><br> </p> <p><br> <span style="font-weight: bold;"></span></p> <h2><a name="manifesto"></a>Tool support for documentation creation</h2> <br> The Socgen project uses and supports three opensourced tools for creating and maintaining component documentation. The key to accurate and timely documents is to automate their creation as part of the IP build process.<br> <br> <br> <br> SEAMONKEY<br> <br> Seamonkey composer is the main tool used to edit the html files.<br> <br> <br> GSCHEM<br> <br> Geda and friends are used to create any and all graphics used in the html files. Several support tools are provided that can extract schematic and symbol information directly from the database ensuring that the database and documents stay in sync <br> <br> <br> OPENOFFICE WORD PROCESSOR<br> <br> Is used to create the pdf for each component <br> <br> <p><br> <br> </p> <p><br> <img style="width: 800px; height: 600px;" alt="" src="../png/doc_fig1.png"><br> </p> <p><br> <br> </p> <p><br> <br> </p> <p><br> <br> </p> <p><br> <br> </p> <p><br> <br> </p> <p><br> <br> </p> <p><br> <br> </p> <p><br> <br> </p> <p><br> <br> </p> <p><br> <br> </p> <p><br> <br> </p> <p><br> <br> </p> <p><br> <br> </p> <p><br> <br> </p> <p><br> <br> </p> <p><br> <br> </p> </body> </html>
Go to most recent revision | Compare with Previous | Blame | View Log