<?xml version="1.0" encoding="ISO-8859-1"?>
<?xml-stylesheet type="text/xsl" href="behavior.xsl"?>
  <behavioral manifest="SoftTools.1.sys.xml">
    <file>"DocBuildViewProcessor.1.xml"</file>
    <Author>Ozer Ozkaraoglu</Author>
    <version No="1.0" date="10/27/01"/>
    <!--

    -->
 
    <process name="DocBuildView Processor">
      Views / Edits the documentation files of manifests. All manifest files and its resources are provided by the user at saveDir.
    </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="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</def>
        <text>Manifest and project files are read to gather the necessary information for build, while some other files (e.g. code files) are accessed during build process.</text>
      </input>
      <input variable="documentationData">
        <def>consists of modifications to documentation data</def>
        <text>This modification data is applied to the documentation of the currently-opened manifest</text>
      </input>
      <input variable="userCommands">
        <def>are the user commands to manipulate the documentation</def>
        <text>These commands are used to make modifications to the document other than the raw data inputs, e.g. adding / deleting section.</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>DocBuildViewDisplay.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>DocBuildViewDisplay.1.xml</connectsToFile>
      </output>
      <output variable="fileName">
        <def>contains the physical location of a file</def>
        <text>The file system is sent filename to begin writing output of document compilation.</text>
      </output>
      <output variable="fileText">
        <def>is the compiled documentation data</def>
        <text>Raw documentation data is sent to its corresponding documentation file.</text>
      </output>
    </outputs>

    <requirements>
      <test No="Processor_1">
        <def>building a new behavior document</def>
        <text>Creates a behavior document from scratch.</text>
      </test>
      <test No="Processor_2">
        <def>building a new design document</def>
        <text>Creates a design document from scratch.</text>
      </test>
      <test No="Processor_3">
        <def>open a behavior document</def>
        <text>Opens an already-existing behavior document, extracting necessary data from the manifest. The user may then edit the document and save changes. Please not that, these editions are not made on the original files (which reside in server), but on the temporary files. Therefore, these modifications are not reflected if they are not submitted to the server as a new revision (version) of the manifest.</text>
      </test>
      <test No="Processor_4">
        <def>open a design document</def>
        <text>Opens an already-existing design document, extracting necessary data from the manifest. The user may then edit the document, where the principles of test Processor_3 applies.</text>
      </test>
      <test No="Processor_5">
        <def>hiding/showing sibling links</def>
        <text>Switches the sibling viewing toggle to on/off and changes the documentationData, which is output to the Display process, accordingly.</text>
      </test>
      <test No="Processor_6">
        <def>deleting deletable document elements in documents</def>
        <text>The editor is able to delete any deletable element from an opened design/behavior document (e.g. input, output, and diagram elements for behavior document). Again, these modifications are not made on the originals, but on the files extracted from the original source.</text>
      </test>
s    </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>