The mainstay of a corporation is the data that it possesses. By data, I mean its customer base, information about the use of its products, employee roles and responsibilities, the development and maintenance of its product lines, demographics of supporters and naysayers, financial records, projected sales ... It is in the organization of this data that advancements to the bottom line are often realized i.e. the nuggets of gold are found. Defining what is important, properly cataloging the information, developing a comprehensive protocol to access and update this information and discerning how this data fits into the corporate venacular is basis of this data organization and may be the difference between moving ahead of the competition or being the one to fall behind.

Whenever we attempt to develop an Enterprise Rule Application, we must begin by harvesting the data upon which those rules are built. This is by no means an easy feat as it requires a thorough understanding of the business, industry, the players and their respective roles and the intent of the application. Depending upon the scope of this undertaking, it is almost always safe to say that no one individual is completely knowledgeable to all facets needed to comprise the entire application.

The intial stage of this endeavor is, obviously, to decide upon the intent of the application. This requires knowledge of what is essential, what is an add-on and which of all these requirements/options can be successfully implemented in the allotted period of time. The importance of this stage cannot be stressed enough; if the vision/goal cannot be articulated in a manner that all can understand, the knowledge tap will be opened to become the money drain. Different departments may compete for the same financial resources; management may be jockeying for their day in the sun; consulting corporations, eager to win the bid, may exaggerate their level of competency. These types of endeavors require those special skills of an individual or a team of very competent members to be/have a software architect, subject matter expert and business analyst.

Once the decision has been made and the application development stages have been defined, the next step is to determine which software development tools to employ. For the sake of this article, we will assume that the team has chosen an object oriented language such as Java and a variety of J EE components, a relationsional database and a vendor specific BRMS such as Blaze Advisor. Now, onto the point of this article.

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

One of the most anticipated features that came on the iPhone 4S was a new thing called: Siri. Zooming out before concentrating on Siri, mobile assistants were the new rage. Beforehand, people were fascinated by the cloud, and how you could store your files in the Internet and retrieve it from anywhere. You could store your file at home, and get it at your workplace to make a presentation. However, next came virtual assistants. When you’re in the car, it’s hard to send text messages. It’s hard to call people. It’s hard to set reminders that just popped into your head onto your phone. Thus, came the virtual assistant: a new way to be able to talk to your phone to be able to do what you want it to do, and in this case, text message, or call people, and many other features. Apple jumped onto the bandwagon with the iPhone 4S and came out with the new feature: Siri, a virtual assistant that is tailored to assist you in your endeavours by your diction.

Getting started with Siri

To get Siri in the first place, you need an iPhone 4S; although you may have the latest updates on your iPhone 4 or earlier, having an iPhone 4S means you have the hardware that is required to run Siri on your phone. Therefore, if you are interested in using Siri, check into getting an iPhone 4S, as they are getting cheaper every single day.

Programmers often tend to be sedentary people. Sitting in a chair and pressing keys, testing code, and planning out one logical step-wise strategy after another to get the computer to process data the way you want it to is just what life as a programmer is all about. But, is being too sedentary hindering a programmers max potential? In other words, will getting up, moving around, and getting the blood pumping make us better programmers? To answer this question more efficiently, we will need to consider the impact of exercise on various aspects of programming.

Alertness And Focus

It is no surprise that working up a sweat makes the mind wake up and become more alert. As the blood starts pumping, the body physically reacts in ways that helps the mind to better focus. And improving our focus might make us better programmers in the sense that we are more able to wrap our mind around a problem and deal with it more efficiently than if we feel sluggish and not so alert. However, improving one's focus with exercise can be augmented by taking such vitamins as B6, Coleen, and eating more saturated fats rather than so many sugars. Exercise alone may be a good start, but it is important to realize that the impact of exercise on overall focus can be enhanced when combined with other dietary practices. However, it never hurts to begin a day of programming with fifteen minutes of rigorous workout to give the mind a little extra push.

Increase In Intellect

Does exercise cause a programmer to become a smarter programmer? This is perhaps a trickier question. In some sense, it might seem as if exercise makes us more intelligent. But, this may be more because our focus is sharper than because of any increase in actual knowledge. For example, if you don't know how to program in Python, it is highly doubtful that exercising harder will all of a sudden transfer such insights directly to your brain. However, exercise might have another indirect impact on a programmer’s intellect that will help them to become a better programmer. The more a person exercises, the more stamina and energy they will tend to have, as compared to programmers who never exercise all that much. That additional energy and stamina might help a programmer to be able to push themselves to learn things more efficiently, simply because they aren't getting tired as much as they study new languages or coding techniques. If you have more energy and stamina throughout the day, you will likely be more productive as a programmer as well. Greater productivity can often make one program better simply because they actually push themselves to finish projects. Other programmers who do not exercise on a regular basis may simply lack the energy, stamina, and motivation to follow through and bring their programming projects to completion.

Memory

The ability to remember things and recall them quickly is key to being an efficient programmer. Getting up and getting real exercise may be central to making sure that one does not lose control of these cognitive abilities. According to the New York Times, article, Getting a Brain Boost Through Exercise, recent research studies on mice and humans have shown that, in both cases, exercise does in fact appear to promote better memory function as well as other cognitive factors like spacial sense. (1) Consequently, if a person intends to be a programmer for a long time and wants their mind to be able to remember things and recall them more easily, then exercise may need to become an essential part of such a programmer's daily routine.

As much as one might want to resist the need for exercise and be sedentary programmers, the simple fact is that exercise very well could improve our ability to program in numerous ways. More importantly, exercise is critical to improving and maintaining good health overall. Even if a person does not have much time to get up and move around during the day, there are exercises that one can do while sitting, which would be better to do than no exercise at all.

What are a few unique pieces of career advice that nobody ever mentions?

What Options do Freelance Consultants Have with Large Corporations