<?xml version="1.0" encoding="ISO-8859-1"?>
<?xml-stylesheet type="text/xsl" href="behavior.xsl"?>
  <behavioral manifest="Display.1.xml">
    <file>"DocBuildViewDisplay.1.xml"</file>
    <Author>Ozer Ozkaraoglu</Author>
    <version No="1.0" date="10/27/01"/>
    <!--

    -->
 
    <process name="DocBuildView Display">
      Views the documentation files of the currently-opened manifests.
    </process>
     <diagram diagramTitle="DocBuildView Context">
      softTools_docbuildview_diagrams1_raster.jpg
    </diagram>
    <diagram diagramTitle="DocBuildView Data Flow">
      softTools_docbuildview_diagrams2_raster.jpg
    </diagram>
    <inputs>
      <input variable="documentationData">
        <def>consists of the data of the documentation files to be displayed</def>
      </input>
      <input variable="errorMessage">
        <def>contains the text about nature of the error</def>
        <text>Any error accumulated by the Processor Process is passed as a message to this process to be displayed.</text>
      </input>
    </inputs>
    <outputs>
      <output variable="viewDisplay">
        <def>contains the documentation data formatted to be displayed to the user.</def>
        <text>The program shows the document data in an internet-browser-based view, which naturally enables the user to walk through the documentation file simply following the links.</text>
      </output>
      <output variable="errorMessage">
        <def>contains the text about nature of the error</def>
        <text>Any error message is output by using this variable</text>
      </output>
    </outputs>

    <requirements>
      <test No="Display_1">
        <def>view a behavior document, Req: (3.1.25)</def>
        <text>Views an already-existing behavior document, extracting necessary data from the manifest.</text>
      </test>
      <test No="Display_2">
        <def>view a design document, Req: (3.1.26)</def>
        <text>Views an already-existing design document, extracting necessary data from the manifest.</text>
      </test>
      <test No="Display_3">
        <def>view diagram as a link, Req: (3.1.27)</def>
        <text>Views links to the diagrams in the documents to increase readibility. This is the default.</text>
      </test>
      <test No="Display_4">
        <def>view full diagram, Req: (3.1.28)</def>
        <text>Views the full diagrams on a separate page. The user can then go back to the main document by using goBack() feature of the browser. Please note that this feature can be used by any key/hot-key which is programmed by the OS as back button. e.g. button4 of MS IntelliMouse points to this feature by default. Unlike it is mentioned at A-Spec Req. 3.1.28., this bevahior is not default, as the cutomer also deemed viewing as a link more appropriate in his sample view.</text>
      </test>
      <test No="Display_5">
        <def>hiding/showing sibling links</def>
        <text>Views the documentationData with the sibling viewing toggle switched on/off, by hiding/showing the sibling links.</text>
      </test>
    </requirements>

    <!--
      The sibling tag, below, is used to identify lower level process descriptions.  Sibling tags have a visibility
      attribute, allowing them to be part of the parent's behavior model, or excluded, at the descretion of the
      behavior RI.
    -->
    <sibling ref="child2.xml" manifest="xmlTran.xml" visible="false"></sibling>
  </behavioral>