<?xml version="1.0" encoding="UTF-8"?>
<collection 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">
 <record>
  <leader>00000cmm a22000003a 4500</leader>
  <controlfield tag="001">UP-99796217611000204</controlfield>
  <controlfield tag="003">Buklod</controlfield>
  <controlfield tag="005">20240919092423.0</controlfield>
  <controlfield tag="006">m    go  j        </controlfield>
  <controlfield tag="007">cr nn |||uuu|a</controlfield>
  <controlfield tag="008">240919s2011    nyu    go  j        eng  </controlfield>
  <datafield tag="020" ind1=" " ind2=" ">
   <subfield code="a">9783642190414 (eBook)</subfield>
  </datafield>
  <datafield tag="035" ind1=" " ind2=" ">
   <subfield code="a">(iLib)UPD-00206905154</subfield>
  </datafield>
  <datafield tag="040" ind1=" " ind2=" ">
   <subfield code="a">DLC</subfield>
   <subfield code="d">DML</subfield>
   <subfield code="e">rda</subfield>
  </datafield>
  <datafield tag="041" ind1="0" ind2=" ">
   <subfield code="a">eng</subfield>
  </datafield>
  <datafield tag="084" ind1=" " ind2=" ">
   <subfield code="a">HB 5548.2</subfield>
   <subfield code="b">B69 2011eb</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
   <subfield code="a">Boyer, Jérôm</subfield>
   <subfield code="q">(Jérôme Roger Luc),</subfield>
   <subfield code="e">author.</subfield>
  </datafield>
  <datafield tag="245" ind1="1" ind2="0">
   <subfield code="a">Agile business rule development</subfield>
   <subfield code="b">process, architecture, and JRules examples</subfield>
   <subfield code="h">[electronic resource]</subfield>
   <subfield code="c">by Jérôme Boyer, Hafedh Mi.</subfield>
  </datafield>
  <datafield tag="264" ind1=" " ind2="1">
   <subfield code="a">Berlin, Heidelberg</subfield>
   <subfield code="b">Springer Berlin Heidelberg</subfield>
   <subfield code="c">[©2011]</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
   <subfield code="a">1 online resource (xxvi, 567 pages)</subfield>
   <subfield code="b">illustrations</subfield>
  </datafield>
  <datafield tag="336" ind1=" " ind2=" ">
   <subfield code="a">text</subfield>
   <subfield code="2">rdacontent</subfield>
  </datafield>
  <datafield tag="337" ind1=" " ind2=" ">
   <subfield code="a">computer</subfield>
   <subfield code="2">rdamedia</subfield>
  </datafield>
  <datafield tag="338" ind1=" " ind2=" ">
   <subfield code="a">online resource</subfield>
   <subfield code="b">cr</subfield>
   <subfield code="2">rdacarrier</subfield>
  </datafield>
  <datafield tag="505" ind1="0" ind2=" ">
   <subfield code="a">Introduction to business rules -- Business rules in practice -- Agile Business Rule Development -- Rule Harvesting -- Prototyping and Design -- Rule engine technology -- Issues in designing business rule applications -- IBM Websphere ILOG JRules -- Issues in rule authoring -- Rule authoring infrastructure in JRules -- Rule authoring in JRules</subfield>
  </datafield>
  <datafield tag="506" ind1=" " ind2=" ">
   <subfield code="a">IP-based subscription, on campus only.</subfield>
   <subfield code="c">Access via Electronic Resources of the UPD University Library Websi</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
   <subfield code="a">Business rules are everywhere. Every enterprise process, task, activity, or function is governed by rules. However, some of these rules are implicit and thus poorly enforced, others are written but not enforced, and still others are perhaps poorly written and obscurely enforced. The business rule approach looks for ways to elicit, communicate, and manage business rules in a way that all stakeholders can understand, and to enforce them within the IT infrastructure in a way that supports their traceability and facilitates their maintenance. Boyer and Mili will help you to adopt the business rules approach effectively. While most business rule development methodologies put a heavy emphasis on up-front business modeling and analysis, agile business rule development (ABRD) as introduced in this book is incremental, iterative, and test-driven. Rather than spending weeks discovering and analyzing rules for a complete business function, ABRD puts the emphasis on producing executable, tested rule sets early in the project without jeopardizing the quality, longevity, and maintainability of the end result. The authors' presentation covers all four aspects required for a successful application of the business rules approach: (1) foundations, to understand what business rules are (and are not) and what they can do for you; (2) methodology, to understand how to apply the business rules approach; (3) architecture, to understand how rule automation impacts your application; (4) implementation, to actually deliver the technical solution within the context of a particular business rule management system (BRMS). Throughout the book, the authors use an insurance case study that deals with claim processing. Boyer and Mili cater to different audiences: Project managers will find a pragmatic, proven methodology for delivering and maintaining business rule applications. Business analysts and rule authors will benefit from guidelines and best practices for rule discovery and analysis. Application architects and software developers will appreciate an exploration of the design space for business rule applications, proven architectural and design patterns, and coding guidelines for using JRul</subfield>
  </datafield>
  <datafield tag="533" ind1=" " ind2=" ">
   <subfield code="a">Electronic reproduction.</subfield>
   <subfield code="b">New York</subfield>
   <subfield code="c">SpringerLink</subfield>
   <subfield code="d">c2011.</subfield>
   <subfield code="n">Available via World Wide Web through SpringerLink</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="0">
   <subfield code="a">Business enterprises</subfield>
   <subfield code="x">Databases</subfield>
   <subfield code="x">Management.</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="0">
   <subfield code="a">Information technology</subfield>
   <subfield code="x">Management.</subfield>
  </datafield>
  <datafield tag="700" ind1="1" ind2=" ">
   <subfield code="a">Mili, Hafedh</subfield>
   <subfield code="e">joint author.</subfield>
  </datafield>
  <datafield tag="710" ind1="2" ind2=" ">
   <subfield code="a">SpringerLink (Online services).</subfield>
  </datafield>
  <datafield tag="773" ind1="0" ind2=" ">
   <subfield code="t">Springer eBooks.</subfield>
  </datafield>
  <datafield tag="842" ind1=" " ind2=" ">
   <subfield code="a">Electronic Resource</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2="0">
   <subfield code="u">https://link.springer.com/book/10.1007/978-3-642-19041-4</subfield>
   <subfield code="y">Available for University of the Philippines Diliman via SpringerLink. Click here to access</subfield>
  </datafield>
  <datafield tag="905" ind1=" " ind2=" ">
   <subfield code="a">FO</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="a">Monograph</subfield>
  </datafield>
  <datafield tag="852" ind1="0" ind2=" ">
   <subfield code="a">UPD</subfield>
   <subfield code="b">DMLR</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
   <subfield code="a">Electronic Resource</subfield>
  </datafield>
 </record>
</collection>
