When businesses are trying to expand and require professionals to lead teams, terminology may get in the way of who performs what roles. When it comes to information technology (IT), new and vital professionals may seem hard to differentiate between one another. However, there are key differences between specific professionals needed with IT departments. Here are the responsibilities that differentiate between an IT manager and an IT project manager.

IT Managers

IT managers are the leaders of the entire IT infrastructure a business has to function properly. The IT manager must lead the entire IT department to regulate and maintain the IT network for the business. As a manager, this IT professional corresponds with other departments in the business about how the IT department is implementing the goals the business is aiming toward. In addition, the manager must be fiscally responsible and answer to executives and financial officers in the business the reasons behind certain costs and investments. Because of the dual computer technology and business acumen this profession requires, many IT managers have a Master of Business Administration (MBA) related to information technology.

IT Project Managers

I suspect that many of you are familiar with the term "hard coding a value" whereby the age of an individual or their location is written into the condition (or action) of a business rule (in this case) as shown below:

if customer.age > 21 and customer.city == 'denver'

then ...

Such coding practices are perfectly expectable provided that the conditional values, age and city, never change. They become entirely unacceptable if a need for different values could be anticipated. A classic example of where this practice occurred that caused considerable heartache in the IT industry was the Y2K issue where dates were updated using only the last 2 digits of a four digit number because the first 2 digits were hard-coded to 19 i.e. 1998, 1999. All was well provided that the date did not advance to a time beyond the 1900’s since no one could be certain of what would happen when the millennia arrived (2000). A considerably amount of work (albeit boring) and money, approximately $200 billion, went into revising systems by way of software rewrites and computer chip replacements in order to thwart any detrimental outcomes. It is obvious how a simple change or an assumption can have sweeping consequences.

You may wonder what Y2K has to do with Business Rule Management Systems (BRMS). Well, what if we considered rules themselves to be hard-coded. If we were to write 100s of rules in Java, .NET or whatever language that only worked for a given scenario or assumption, would that not constitute hard-coded logic? By hard-coded, we obviously mean compiled. For example, if a credit card company has a variety of bonus campaigns, each with their own unique list of rules that may change within a week’s time, what would be the most effective way of writing software to deal with these responsibilities?

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

In Python, we can create three types of methods in a class:  instance or regular method, classmethod and staticmethod.  Instance methods are associated, as the name infers, with an instance or object of the class and take self as the first parameter.  Classmethods take a reference to the class, cls, as the first parameter of the class.  Staticmethods, for the most part, are convenience methods that could be declared as functions since they really do not have much to do with the class itself.  They were probably added at some time after the advent of Python in order to make the language more object oriented i.e. minimize the number of free floating functions. 

Refer the our article static, class and regular methods in Python for a detailed explanation on this subject.