One of the most recent additions to the iPhone is the Photo Editor, directly in the iPhone. Added in the update that came from Apple over the summer, this new photo editor brings efficiency, and simplicity to photo editing, right in your phone. If you have a photo that you just took a moment ago of you with your friends, and you want to edit some features before posting it on a social networking site, it becomes simpler with this new addition, right in the Photos Application.

Open up the Photos application, and tap on a picture you would like to edit. Once your picture comes up, tap in the top right on the button named “Edit.” A user interface that deals with editing will show up, and you are ready to rock and roll. First off, many times we take pictures at weird angles, we take them sideways, upside down, to the right, to the left, and our phone doesn’t recognize them. In the bottom left, you will see an arrow that is pointing counter clockwise; this is the button that you want to press if you want to flip your picture around to the correct orientation. Keep in mind that this flips counter clockwise, and it doesn’t matter if you pass the orientation that you wanted. Just keep flipping!

Next up is the simple enhance tool. Sometimes colors get drowned out if we don’t have the right lighting in our pictures, and makes the photo look dull, and dreary. You don’t want your colors to look dull and dreary while you are celebrating your trip to New York and seeing Times Square! Tapping on the button that looks similar to a magic wand, your picture will begin to look brighter and fuller. With the tap of a button, the iPhone detects what points in the picture is, as we said earlier, “dull, and dreary” and enhances those colors to their predicted colors, if the light was in the correct intensity. However, if you are dissatisfied with the outcome of the enhance tool, if your picture is not handled well by the phone, you are able to tap on the wand again, and remove your auto enhance.

In the rare case of red eye in your picture, the new photo editor has a solution. Moreover, a one-tap solution. With a simple tap on the red eye correction tool, between the crop tool, and the auto-enhance tool, you bring up a screen where you are now able to tap anywhere on your photo where red eye exists, and remove it. As simple as that. Remember when you had to do crazy dragging, selection, and odd stunts to remove red eye? Not any more.

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

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.