<?xml version="1.0" encoding="ISO-8859-1"?>
<?xml-stylesheet type="text/xsl" href="behavior.xsl"?>
  <behavioral manifest="SoftTools.1.sys.xml">
    <file>"BuildProcessor.1.xml"</file>
    <Author>Ozer Ozkaraoglu</Author>
    <version No="1.0" date="10/27/01"/>
    <!--

    -->
 
    <process name="Build Script File Reference Process">
This class accepts a manifest name, remove the prepended file names in its refered files and all its sub level manifests.
				Store all file refered by one manifest in one directory named by it's manifest name.    </process>
    <diagram diagramTitle="Build Script Context">
      softTools_buildScript_diagrams1_raster.jpg
    </diagram>
    <diagram diagramTitle="Build Script Data Flow">
      softTools_buildScript_diagrams2_raster.jpg
    </diagram>
    <inputs>
      <input variable="maniestName">
      <def>The file name of the manifest name.</def>
      <text>The name of the top level manifest. </text>
      </input>
      <input variable="fileText">
        <def>The file content of each manifest.</def>
        <text>The program rquests all manifests refered by upper level ones.</text>
      </input>
    </inputs>
    <outputs>
      <output variable="errorMessage">
        <def>contains the text about nature of the error</def>
        <text>An error message is created when an error occurs.</text>
      </output>
    </outputs>

    <requirements>
    </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>