Eric Moore, the co-founder of Corticon, introduces his series of tips for Java programmers using Corticon to manage business rules with a few basics.
As Ankur Goyal recently discussed, adopting a BRMS like Progress® Corticon® helps IT and Business collaborate on business rule changes and shorten develop time dramatically. Corticon helps accomplish this by separating rules logic from application code, so that rules can be adjusted without requiring IT development resources. This makes it an ideal tool for business analysts in a variety of industries that use complex business logic to make hundreds of business decisions a day quickly and competently.
Analysts can quickly model required rules changes and test them within Corticon without needing to run a complete application development lifecycle. Corticon provides a range of tools to test rules for conflicts, rule completeness and logic.
Corticon can be understood as a code-generation system that creates components to do the rules processing that a programmer wants to accomplish. Corticon is thus a fourth-generation programming language because of its semantic, human-readable approach. By capturing human logic—for example, “no one under the age of 18 is eligible to vote”—Corticon provides a model-driven design environment with which to discover, model, execute and improve operational decisions and associated business rules within information systems.
Corticon is strictly declarative, that is, expressed what the program is supposed to achieve—in our website example, close the survey and thank the user—without specifying the exact steps the program must take or in what order. A declarative approach allows for business processes that cannot be predicted in advance—something that is necessary in industries where complex rules are in effect depending upon large sets of variables, such as insurance or finance.
Next week, I’ll be discussing how Corticon handles rule dependencies. But remember that help is always available should you need it. Check out these online resources, or contact us anytime.
Eric Moore is a Software Architect at Progress.
Copyright © 2018 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.