As part of our C++ Tutorials series, here is a free overview of C++ pointers you may enjoy and find beneficial.

C++ Pointers Tutorials

Back in the late 90's, there were a number of computer scienctists claiming to know java in hopes of landing a job for $80k+/year.  In fact, I know a woman you did just that:  land a project management position with a large telecom and have no experience whatsoever.  I guess the company figured that some talent was better than no talent and that, with some time and training, she would be productive.  Like all gravey train stories, that one, too, had an end.  After only a year, she was given a pink slip.

Not only are those days over, job prospects for the IT professional have become considerably more demanding.  Saying you know java today is like saying you know that you have expertise with the computer mouse; that's nice, but what else can you do.   This demand can be attributed to an increase in global competition along with the introduction of a number of varied technologies.   Take .NET, Python, Ruby, Spring, Hibernate ... as an example;  most of them, along with many others, are the backbone of the IT infrastructure of most mid-to-large scale US corporations.  Imagine the difficulty in finding the right mix of experience, knowledge and talent to support, maintain and devlop with such desparate technologies.

Well imagine no more.  According to the IT Hiring Index and Skills Report, seventy percent of CIO’s said it's challenging to find skilled professionals today.  If we add the rapid rate of technological innovation into the mix of factors affecting more businesses now than ever before, it’s understandable that the skill gap is widening.  Consider this as well:  the economic downturn has forced many potential retires to remain in the workforce.  This is detailed in MetLife's annual Study of Employee Benefits which states that“more than one-third of surveyed Baby Boomers (35%) say that as a result of economic conditions they plan to postpone their retirement.”  How then does the corporation hire new, more informed/better educated talent?    Indeed, the IT skills gap is ever widening.

In order to compensate for these skill discrepencies, many firms have resorted to hire the ideal candidates by demanding they possess a christmas wish list of expertise in a variety of different IT disciplines.  It would not be uncommon that such individuals have a strong programming background and are brilliant DBA's.  What about training?  That is certainly a way to diminish the skills gap.

Structure Rule Language

To aid in the ease of rule authoring, Blaze Software, now Fair Isaac, created the proprietary Structure Rule Language (SRL), an object-oriented programming language designed to enable those with little or no background in software development to pen rules. Although the capabilities of this language are far too extensive to detail in this article, we can examine the basic rule syntax.

Rules in the SRL take the following form:

rule RuleName [at | priority M] is

A business rule is the basic unit of rule processing in a Business Rule Management System (BRMS) and, as such, requires a fundamental understanding. Rules consist of a set of actions and a set of conditions whereby actions are the consequences of each condition statement being satisfied or true. With rare exception, conditions test the property values of objects taken from an object model which itself is gleaned from a Data Dictionary and UML diagrams. See my article on Data Dictionaries for a better understanding on this subject matter.

A simple rule takes the form:

if condition(s)

then actions.

An alternative form includes an else statement where alternate actions are executed in the event that the conditions in the if statement are not satisfied:

if condition(s)

then actions

else alternate_actions

It is not considered a best prectice to write rules via nested if-then-else statements as they tend to be difficult to understand, hard to maintain and even harder to extend as the depth of these statements increases; in other words, adding if statements within a then clause makes it especially hard to determine which if statement was executed when looking at a bucket of rules. Moreoever, how can we determine whether the if or the else statement was satisfied without having to read the rule itself. Rules such as these are often organized into simple rule statements and provided with a name so that when reviewing rule execution logs one can determine which rule fired and not worry about whether the if or else statement was satisfied. Another limitation of this type of rule processing is that it does not take full advantage of rule inferencing and may have a negative performance impact on the Rete engine execution. Take a class with HSG and find out why.

Rule Conditions