Book Description
· This is the only book that demonstrates how to develop a business rules engine. Covers user requirements, data modeling, metadata, and more.
· A sample application is used throughout the book to illustrate concepts. The code for the sample application is available online at http://www.refdataportal.com.
· Includes conceptual overview chapters suitable for management-level readers, including general introduction, business justification, development and implementation considerations, and more.
· This is the only book that demonstrates how to develop a business rules engine. Covers user requirements, data modeling, metadata, and more.
· A sample application is used throughout the book to illustrate concepts. The code for the sample application is available online at http://www.refdataportal.com.
· Includes conceptual overview chapters suitable for management-level readers, including general introduction, business justification, development and implementation considerations, and more.
Book Info
Provides a detailed roadmap, with examples, for building a business rules engine. Covers the necessary background and concepts, as well as the specific steps needed to build a rules engine. Discusses components and organizational issues. Softcover.
From the Back Cover
[shelving code] Data Management/Programming
Business rules engines can make organizations more agile by allowing them to manage diverse sets of operating rules, such as many different contracts for goods and services with different clients. For example, business rules engines can contain interfaces that allow users to define business rules to add specific functionality to software applications in order to take advantage of particular business arrangements. This enables organizations to overcome the barriers of time, money, and reliability that traditional programming approaches present when trying to include variable business situations within information systems. Rules engines can also speed software implementation, provide increased auditability, and ensure engineering compliance. The capacity to understand and manage business rules outside of the "black box" of program code can improve the overall quality of IT infrastructures.
How to Build a Business Rules Engine is the first book to provide a detailed roadmap, with examples, for building a business rules engine. Written from the author"s 12 years of experience building business rules functionality, this book covers the necessary background and concepts, as well as the specific steps needed to build a rules engine. The book describes not only the components that a rules engine must have, but also the organizational issues that may determine its success after it has been built and implemented.
Features
· The only book that demonstrates how to develop a business rules engine. Covers user requirements, data modeling, repository design, metadata engineering, and more.
· Includes conceptual overview chapters suitable for management-level readers, including general introduction, business justification, and development and implementation considerations.
· A sample application is used throughout the book to illustrate concepts. The code for the sample application is available online at http://www.bizrulesengines.com.
About the Author
Malcolm Chisholm holds an M.A. from the University of Oxford, and a Ph.D. from the University of Bristol. He has over 20 years of experience in information technology and 12 years building business rules engines. His expertise has allowed him to work in various industries focusing on systems development and data administration. Recently he has worked with the United Nations Development Program and Deloitte and Touche.
How to Build a Business Rules Engine: Extending Application Functionality Through Engineering ANNOTATION
Audience: Database designers, data modelers, database administrators, software engineers, systems architects, project leader, project manager, programmer, and other IT staff.
FROM THE PUBLISHER
Business rules engines can make organizations more agile by allowing them to manage diverse sets of operating rules, such as many different contracts for goods and services with different clients. For example, business rules engines can contain interfaces that allow users to define business rules to add specific functionality to software applications in order to take advantage of particular business arrangements. This enables organizations to overcome the barriers of time, money, and reliability that traditional programming approaches present when trying to include variable business situations within information systems. Rules engines can also speed software implementation, provide increased auditability, and ensure engineering compliance. The capacity to understand and manage business rules outside of the "black box" of program code can improve the overall quality of IT infrastructures. How to Build a Business Rules Engine is the first book to provide a cetailed roadmap, with examples, for building a business rules engine. Written from the author's 12 years of experience building business rules functionality, this book covers the necessary background and concepts, as well as the specific steps needed to build a rules engine. The book describes not only the components that a rules engine must have, but also the organizational issues that may determine its success after it has been built and implemented.