<?xml version="1.0" encoding="utf-8" ?>
<?xml-stylesheet type="text/xsl" href="design.xslt"?>
<!--
    This is a design desciption of server process. This template cannot be pointed to by any
    source code files as build scripts and also as maintainence 
    histroy pages
-->
<design manifest="DocumentViewer.1.xml" version="2.0">
<def>
Supports display both behavior and design documents.  
</def>
<text>
DocumentViewer module uses an interface for given manifest file. It gets directory (which is where all files are extracted in) and manifest filename, then displays both behavior and design documents of given manifest. 
</text>
<architecture>
<def>
</def>
<text>
The program provides Windows.Forms dialog to display behavior and design documents of the manifest. It takes the full path where the all file are already extracted and manifest name. The program finds all the behavior and design documents and shows them in embedded browser when user requests. There can be one or more than one behavior and design documents, or none for each module.   
</text>

<context>
<diagram>
<ref>softTools_docViewer_context1_raster.jpg</ref>
</diagram>
<def>
</def>
<text>DocumentViewer accepts saveDir and manifestName. If any saveDir is not provided, it uses the current path as a default. It lists and displays behavior and design documents in a Windows.Forms dialog. </text>
</context>

<structure>
<diagram>
<ref>softTools_docViewer_strucMain1_raster.jpg</ref>
<ref>softTools_docViewer_strucFormView1_raster.jpg</ref>
<ref>softTools_docViewer_strucMnfParser1_raster.jpg</ref>
<ref>softTools_docViewer_events1_raster.jpg</ref>
</diagram>
<def>Structure Overview</def>
<text>FormDocViewer gets manifestName and saveDir as arguments. ManifestParser loads given manifest name and lists behavior and design documents.</text>
</structure>
<!-- References for each class have to be traversed by the design doc builder tools and add  here all the parts escept history and public Interfaces
  --> 

</architecture>

<modules>
<diagram>
<ref>softTools_docViewer_class1_raster.jpg</ref>
</diagram>
<def></def>
<text></text>
<!-- References for each module have to be traversed by the design doc builder tools and add here all the parts escept history and public Interfaces
 --> 
<module ref="FormDocViewer.cs">
<def>FormDocViewer Module</def>
<text>The module provides an interface to user to display behavior and design documents of given manifest name. Each behavior or design document can be shown in embedded browser  when user requests. </text>
</module>

</modules>
</design>