<?xml version="1.0" encoding="ISO-8859-1"?>
<?xml-stylesheet type="text/xsl" href="behavior.1.2.xsl"?>
  <behavioral manifest="SoftTools.1.sys.xml">
    <file>"DocViewerProcessor.1.xml"</file>
    <Author>Ozer Ozkaraoglu</Author>
    <version No="1.1" date="11/23/02"/>
    <!--

    -->
 
    <process name="DocViewer Processor">
      Views the documentation files of manifests. All manifest files and its resources are provided by the user at saveDir.
    </process>
    <diagram diagramTitle="DocViewer Context">
      softTools_docviewer_context.gif
    </diagram>
    <diagram diagramTitle="DocViewer Data Flow">
      softTools_docviewer_DFD.gif
    </diagram>
     <inputs>
   <input variable="command">
      <def>contains information about type of the operation which will be performed</def>
      <text>The requested task is given by this input.</text>
      </input>
      <input variable="fileText">
        <def>is the data (content) coming from the foundry files - CHANGED</def>
        <text>Manifest files and the files referred by the manifests are read to display.</text>
      </input>
      <input variable="userCommands">
        <def>are the user commands to manipulate the documentation - CHANGED</def>
        <text>These commands are used to browse the documents.</text>
      </input>
 
    </inputs>
    <outputs>
      <output variable="documentationData">
        <def>contains the data (text) of the documentation files</def>
        <text>The data of the documents are sent to the Display Process to be displayed.</text>
        <connectsToTitle>Display Process</connectsToTitle>
        <connectsToFile>DocViewerDisplay.1.xml</connectsToFile>
      </output>
      <output variable="errorMessage">
        <def>contains the text about nature of the error</def>
        <text>All kinds of error messages are again passed to the Display Process.</text>
        <connectsToTitle>Display Process</connectsToTitle>
        <connectsToFile>DocViewerDisplay.1.xml</connectsToFile>
      </output>
      <output variable="fileName">
        <def>contains the physical location of a file - CHANGED</def>
        <text>The file system is sent filename to begin reading document contents.</text>
      </output>
    </outputs>
    <requirements>
      <test No="DocViewerProcessor_1">
        <def>Open the manifest (given by manifestName)</def>
        <text>The program lists the behavior/design documents of the given manifest, and displays the first behavior document (if not any, first design document) in alphabetical order of the document file names. The program does not display any document, if there weren't any defined in the manifest.</text>
      </test>
      <test No="DocViewerProcessor_2">
        <def>Browsing documentation references</def>
        <text>The program follows through and opens the documentation file references. These files include diagram files, and other documentation files.</text>
      </test>
      <test No="DocViewerProcessor_3">
        <def>Browsing manifest references</def>
        <text>The program follows thorugh and opens the referred manifest.</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>