<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="titles.xsl"?>
<record
    biblionix-libraryname="Alliance Public Library"
    biblionix-libraryid="1085"
    biblionix-libraryusername="alliance"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd"
    xmlns="http://www.loc.gov/MARC21/slim">

  <leader>02621cmm a2200313   4500</leader>
  <controlfield tag="001">214821268</controlfield>
  <controlfield tag="003">TxAuBib</controlfield>
  <controlfield tag="005">20120507120000.0</controlfield>
  <controlfield tag="008">081017s2005||||||||||||||||||||||||eng|u</controlfield>
  <datafield tag="020" ind1=" " ind2=" ">
    <subfield code="a">9783540271260</subfield>
  </datafield>
  <datafield tag="020" ind1=" " ind2=" ">
    <subfield code="a">3540271260</subfield>
  </datafield>
  <datafield tag="020" ind1=" " ind2=" ">
    <subfield code="a">9783540225454</subfield>
    <subfield code="q">cloth</subfield>
  </datafield>
  <datafield tag="020" ind1=" " ind2=" ">
    <subfield code="a">3540225455</subfield>
    <subfield code="q">cloth</subfield>
  </datafield>
  <datafield tag="035" ind1=" " ind2=" ">
    <subfield code="a">(OCoLC)262680655</subfield>
  </datafield>
  <datafield tag="040" ind1=" " ind2=" ">
    <subfield code="a">GW5XE</subfield>
    <subfield code="b">eng</subfield>
    <subfield code="c">GW5XE</subfield>
    <subfield code="d">N$T</subfield>
    <subfield code="d">YDXCP</subfield>
    <subfield code="d">UAB</subfield>
    <subfield code="d">DKU</subfield>
    <subfield code="d">CNTRU</subfield>
    <subfield code="d">E7B</subfield>
    <subfield code="d">OCLCQ</subfield>
    <subfield code="d">IDEBK</subfield>
    <subfield code="d">OCLCQ</subfield>
    <subfield code="d">TUU</subfield>
    <subfield code="d">OCLCQ</subfield>
    <subfield code="d">TxAuBib</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Muth, Thomas G.</subfield>
  </datafield>
  <datafield tag="245" ind1="1" ind2=" ">
    <subfield code="a">Functional structures in networks</subfield>
    <subfield code="h">[electronic resource] :</subfield>
    <subfield code="b">AMLn - a language for model driven development of telecom systems /</subfield>
    <subfield code="c">Thomas G. Muth.</subfield>
  </datafield>
  <datafield tag="264" ind1=" " ind2="1">
    <subfield code="a">Berlin : </subfield>
    <subfield code="b">Springer-Verlag, </subfield>
    <subfield code="c">2005.</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">1 online resource (xvi, 280 p.) :</subfield>
    <subfield code="b">ill.</subfield>
  </datafield>
  <datafield tag="490" ind1="1" ind2=" ">
    <subfield code="a">Signals and communication technology</subfield>
  </datafield>
  <datafield tag="504" ind1=" " ind2=" ">
    <subfield code="a">Includes bibliographical references and index.</subfield>
  </datafield>
  <datafield tag="520" ind1="1" ind2=" ">
    <subfield code="a">"The book describes a method for creating models of telecom systems. The method is intended for practicing network architects and designers. This method emphasizes modeling the (very complex) functional structure of networks in a way that is independent of any hardware and software design methodology. The method also allows designers to express their model in two main views: a generic view and a system view that takes protocols and network configuration issues into account. The idea is to retain a stable view (the generic) in the context of constant changes and large variations within the system view. The expected benefits are large savings in telecom systems development and maintenance. The terminology is domain unique, i.e., based on de-facto telecom terminology. All concepts that are used in modeling are well-defined. The purpose of using a telecom-oriented terminology instead of industry-standard methods for software and protocol design (e.g., UML and SDL) is to be able to create models that are expressive and intelligible for network architects and designers. Models are created as graphical models that show the functional and physical structure of networks at different levels of details. Information on properties, including behavior is attached to the models. A fairly small set of symbols is used in modeling."--Jacket.</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2=" ">
    <subfield code="a">Telecommunication systems</subfield>
    <subfield code="x">Computer simulation.</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2=" ">
    <subfield code="a">System analysis.</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="1">
    <subfield code="a">Computers</subfield>
    <subfield code="x">Information Theory.</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="7">
    <subfield code="a">TECHNOLOGY &amp; ENGINEERING</subfield>
    <subfield code="x">Signals &amp; Signal Processing.</subfield>
  </datafield>
  <datafield tag="655" ind1=" " ind2="4">
    <subfield code="a">Electronic books.</subfield>
  </datafield>
  <datafield tag="830" ind1=" " ind2=" ">
    <subfield code="a">Signals and communication technology.</subfield>
  </datafield>
  <datafield tag="856" ind1=" " ind2=" ">
    <subfield code="u">https://search.ebscohost.com/login.aspx?direct=true&amp;scope=site&amp;db=nlebk&amp;db=nlabk&amp;AN=145794</subfield>
    <subfield code="3">EBSCOhost</subfield>
  </datafield>
</record>