000			04212nam a22004695i 4500
001			u375749
003			SIRSI
005			20160812084339.0
007			cr nn 008mamaa
008			110323s2011 gw | s |||| 0|eng d
020			_a9783642190414 _9978-3-642-19041-4
040			_cMX-MeUAM
050		4	_aHF54.5-54.56
082	0	4	_a650 _223
100	1		_aBoyer, Jérôme. _eauthor.
245	1	0	_aAgile Business Rule Development _h[recurso electrónico] : _bProcess, Architecture, and JRules Examples / _cby Jérôme Boyer, Hafedh Mili.
264		1	_aBerlin, Heidelberg : _bSpringer Berlin Heidelberg : _bImprint: Springer, _c2011.
300			_aXXVI, 567 p. _bonline resource.
336			_atext _btxt _2rdacontent
337			_acomputer _bc _2rdamedia
338			_aonline resource _bcr _2rdacarrier
347			_atext file _bPDF _2rda
505	0		_aIntroduction 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.-.
520			_aBusiness 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 JRules.
650		0	_aEconomics.
650		0	_aSoftware engineering.
650		0	_aArtificial intelligence.
650		0	_aManagement information systems.
650	1	4	_aEconomics/Management Science.
650	2	4	_aBusiness Information Systems.
650	2	4	_aSoftware Engineering.
650	2	4	_aInformation Systems Applications (incl. Internet).
650	2	4	_aArtificial Intelligence (incl. Robotics).
700	1		_aMili, Hafedh. _eauthor.
710	2		_aSpringerLink (Online service)
773	0		_tSpringer eBooks
776	0	8	_iPrinted edition: _z9783642190407
856	4	0	_zLibro electrónico _uhttp://148.231.10.114:2048/login?url=http://link.springer.com/book/10.1007/978-3-642-19041-4
596			_a19
942			_cLIBRO_ELEC
999			_c203629 _d203629