Develop decision services, Part 1, A smarter city case study
From the developerWorks archives
Date archived: January 3, 2017 | First published: June 28, 2011
In today's ever-changing business environment, there is a need for systems to be smarter to reduce the overall cost and complexity and to help businesses react quickly to changing environments. To do this, a smarter system needs an effective decision subsystem. In this three-part article series, we use a smarter city use case to guide architects and developers in selecting and implementing a decision subsystem. We walk you through a complete application development lifecycle of a business rule management system (BRMS). We discuss the BRMS architecture, rules discovery process, developing the rule application, and rule maintenance. The smarter city use case involves implementing a decision subsystem for intelligent coordination among multiple city departments during severe weather emergencies. The decision subsystem is based on IBM WebSphere® ILOG® JRules to automate the decision-making process.
This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.