<?xml version="1.0" encoding="UTF-8"?>
<record
    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>02924cam a22003737a 4500</leader>
  <controlfield tag="001">17384187</controlfield>
  <controlfield tag="003">OSt</controlfield>
  <controlfield tag="005">20150408114201.0</controlfield>
  <controlfield tag="008">120712s2012    maua   f b    001 0 eng d</controlfield>
  <datafield tag="010" ind1=" " ind2=" ">
    <subfield code="a">  2011277627</subfield>
  </datafield>
  <datafield tag="016" ind1="7" ind2=" ">
    <subfield code="a">015959177</subfield>
    <subfield code="2">Uk</subfield>
  </datafield>
  <datafield tag="020" ind1=" " ind2=" ">
    <subfield code="a">9780123850515 (pbk)</subfield>
  </datafield>
  <datafield tag="020" ind1=" " ind2=" ">
    <subfield code="a">0123850517 (pbk)</subfield>
  </datafield>
  <datafield tag="035" ind1=" " ind2=" ">
    <subfield code="a">(OCoLC)ocn782206753</subfield>
  </datafield>
  <datafield tag="040" ind1=" " ind2=" ">
    <subfield code="a">AU@</subfield>
    <subfield code="b">eng</subfield>
    <subfield code="c">AU@</subfield>
    <subfield code="d">COO</subfield>
    <subfield code="d">COA</subfield>
    <subfield code="d">BTCTA</subfield>
    <subfield code="d">UKMGB</subfield>
    <subfield code="d">YDXCP</subfield>
    <subfield code="d">BWX</subfield>
    <subfield code="d">UBY</subfield>
    <subfield code="d">DLC</subfield>
  </datafield>
  <datafield tag="042" ind1=" " ind2=" ">
    <subfield code="a">lccopycat</subfield>
  </datafield>
  <datafield tag="050" ind1="0" ind2="0">
    <subfield code="a">QA76.5913</subfield>
    <subfield code="b">.W58 2012</subfield>
  </datafield>
  <datafield tag="082" ind1="0" ind2="4">
    <subfield code="a">651.8</subfield>
    <subfield code="2">23</subfield>
    <subfield code="b">WGW</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Witt, Graham C.</subfield>
    <subfield code="9">41787</subfield>
  </datafield>
  <datafield tag="245" ind1="1" ind2="0">
    <subfield code="a">Writing effective business rules :</subfield>
    <subfield code="b">a practical method /</subfield>
    <subfield code="c">Graham Witt.</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="a">Waltham, Mass. :</subfield>
    <subfield code="b">Morgan Kaufmann/Elsevier,</subfield>
    <subfield code="c">2012.</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">xx, 340 p. :</subfield>
    <subfield code="b">ill. ;</subfield>
    <subfield code="c">23 cm.</subfield>
  </datafield>
  <datafield tag="504" ind1=" " ind2=" ">
    <subfield code="a">Includes bibliographical references (p. 303-304) and index.</subfield>
  </datafield>
  <datafield tag="505" ind1="0" ind2=" ">
    <subfield code="a">The world of rules -- How rules work -- A brief history of rules -- Types of rules -- The building blocks of natural language rule statements -- Fact models -- How to write quality natural language rule statements -- An end-to-end rule management methodology -- Rule statement templates and subtemplates.</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">Writing Effective Business Rules moves beyond the fundamental dilemma of system design: defining business rules either in natural language, intelligible but often ambiguous, or program code (or rule engine instructions), unambiguous but unintelligible to stakeholders. Designed to meet the needs of business analysts, this book provides an exhaustive analysis of rule types and a set of syntactic templates from which unambiguous natural language rule statements of each type can be generated. A user guide to the SBVR [Semantics of Business Vocabulary and Business Rules] specification, it explains how to develop an appropriate business vocabulary and generate quality rule statements using the appropriate templates and terms from the vocabulary. The resulting rule statements can be reviewed by business stakeholders for relevance and correctness, providing for a high level of confidence in their successful implementation. A complete set of standard templates for rule statements and their component syntactic elements A rigorous approach to rule statement construction to avoid ambiguity and ensure consistency. A clear explanation of the way in which a fact model provides and constrains the rule statement vocabulary A practical reader-friendly user guide to the those parts of the SBVR specification that are relevant to rule authoring--</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="0">
    <subfield code="a">Semantic computing.</subfield>
    <subfield code="9">41788</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="0">
    <subfield code="a">Rule-based programming.</subfield>
    <subfield code="9">41789</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="0">
    <subfield code="a">Data structures (Computer science)</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="0">
    <subfield code="a">Natural language processing (Computer science)</subfield>
    <subfield code="9">40479</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="0">
    <subfield code="a">Electronic data processing.</subfield>
  </datafield>
  <datafield tag="906" ind1=" " ind2=" ">
    <subfield code="a">7</subfield>
    <subfield code="b">cbc</subfield>
    <subfield code="c">copycat</subfield>
    <subfield code="d">2</subfield>
    <subfield code="e">ncip</subfield>
    <subfield code="f">20</subfield>
    <subfield code="g">y-gencatlg</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="2">ddc</subfield>
    <subfield code="c">DVD</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">33030</subfield>
    <subfield code="d">267530</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="1">0</subfield>
    <subfield code="2">2014-01-08</subfield>
    <subfield code="4">0</subfield>
    <subfield code="7">0</subfield>
    <subfield code="a">651.8 WGW</subfield>
    <subfield code="d">2014-01-08</subfield>
    <subfield code="h">CL</subfield>
    <subfield code="m">CL</subfield>
    <subfield code="r">2014-01-08 00:00:00</subfield>
    <subfield code="t">BOOK</subfield>
    <subfield code="w">ddc</subfield>
    <subfield code="y">0</subfield>
  </datafield>
</record>
