<?xml version="1.0" encoding="ISO-8859-1"?>
<?xml-stylesheet type="text/xsl" href="behavior.xsl"?>
 <behavioral manifest="Display.1.xml">
    <file>"BehaviorDocBuilderDisplay.1.xml"</file>
    <Author>Ozer Ozkaraoglu</Author>
    <version No="1.1" date="11/23/02"/>
    <!--

    -->
 
    <process name="BehaviorDocBuilder Display">
      Displays the current status of the documentation file and all other messages passed to the user.
    </process>
     <diagram diagramTitle="BehaviorDocBuilder Context">
      softTools_behaviordocbuilder_context.gif
    </diagram>
    <diagram diagramTitle="BehaviorDocBuilder Data Flow">
      softTools_behaviordocbuilder_DFD.gif
    </diagram>
    <inputs>
      <input variable="documentationData">
        <def>consists of the data of the documentation file 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 - CHANGED</def>
        <text>The program shows the document data to ease editing process.</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="BehaviorDocBuilderDisplay_1">
        <def>display an existing behavior document</def>
        <text>Displays the data of an already-existing behavior document, reading data from the existing file.</text>
      </test>
      <test No="BehaviorDocBuilderDisplay_1">
        <def>display modifications to the behavior document</def>
        <text>Displays the modifications to the behavior document as they're done by the user.</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>