<?xml version="1.0" encoding="ISO-8859-1" ?>
<?xml-stylesheet type="text/xsl" href="behavior.xsl"?>
  <behavioral manifest="SoftTools.1.sys.xml">
  <file>"BehaviorDocBuilderInputInterpreter.1.xml"</file>
  <Author>Ozer Ozkaraoglu</Author>
  <version No="1.1" date="11/23/02" />
  <!--

    -->
  <process name="BehaviorDocBuilder Input Interpreter">
    Interpretes the given commands and calls the related functions.
    </process>
  <diagram diagramTitle="BehaviorDocBuilder Context">
      softTools_behaviordocbuilder_context.gif
    </diagram>
  <diagram diagramTitle="BehaviorDocBuilder Data Flow">
      softTools_behaviordocbuilder_DFD.gif
    </diagram>
  <inputs>
    <input variable="documentFileName">
      <def>holds the physical location of the document file to be processed</def>
      <text>All modifications are essentially performed on this file.</text>
    </input>
    <input variable="refListFileName">
      <def>holds the physical location of the file that contains the list of files that can be referred.</def>
      <text>This file holds the CSV (Comma Separated Value) list of files (supposedly in the Foundry) that can be referred in the documentation file.</text>
    </input>
  </inputs>
  <outputs>
    <output variable="command">
      <def>contains information about the operation which will be performed</def>
      <text>This processor compiles the input from the user and creates a command, which drives the BehaviorDocBuilder Processor.</text>
      <connectsToTitle>Processor Process</connectsToTitle>
      <connectsToFile>BehaviorDocBuilderProcessor.1.xml</connectsToFile>
     </output>
    <output variable="errorMessage">
      <def>contains the text about nature of the error</def>
      <text>This output is created when there is an invalid / corrupt input given.</text>
    </output>
  </outputs>
  <requirements>
    <test No="BehaviorDocBuilderInputInterpreter_1">
      <def>invalid documentFileName given</def>
      <text>The program passes an appropriate errorMessage.</text>
    </test>
    <test No="BehaviorDocBuilderInputInterpreter_2">
      <def>invalid refListFileName given</def>
      <text>The program passes an appropriate errorMessage.</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>