I have been very fortunate to see a lot of this history first hand. I have observed changes not just in terms of systems and computers, but also how the trade press has evolved and the profession in general. It has been an interesting ride.

Throughout all of this, there have been some very intelligent people who have impacted the industry, there have also been quite a few charlatans, but there has only been a handful of true geniuses, one of which was Robert W. Beamer who passed away just a couple of years ago. Bob was the father of ASCII code, without which we wouldn't have the computers of today, the Internet, the billions of dollars owned by Bill Gates, or this document.

I always find it amusing when I tell a young person in this industry that I worked with punch cards and plastic templates years ago. Its kind of the same dumbfounded look I get from my kids when I tell them we used to watch black and white television with three channels, no remote control, and station signoffs at midnight. It has been my observation that our younger workers do not have a sense of history; this is particularly apparent in the systems world. If they do not have an appreciation of whence we came, I doubt they will have an appreciation of where we should be going. Consequently, I have assembled the following chronology of events in the hopes this will provide some insight as to how the systems industry has evolved to its current state.

I'm sure I could turn this into a lengthy dissertation but, instead, I will try to be brief and to the point. Further, the following will have little concern for academic developments but rather how systems have been implemented in practice in the corporate world.

Recently I wrote a paper on the general state of craftsmanship which was geared more for public consumption as opposed to any specific industry. To my way of thinking, craftsmanship is a universal concept that touches all industries, regardless if they are product or service related.  This resulted in a flurry of e-mails to me questioning how it pertains to specific types of work, including Business Systems Analysis (BSA) which, of course, is applicable but I question whether we have truly realized craftsmanship in this field.

From the outset, let me say unequivocally that business systems analysis is not a new concept and has been with us for a long time, actually predating the modern computer era of the 20th century.  Prior to this, companies had formal "Systems & Procedures" departments with analysts focusing on streamlining business processes and primarily using paper and manual procedures.  As tabulating and other office equipment emerged, they were responsible for their integration into the business.  But as computers were introduced, a new function was devised that greatly impacted the future of analysts, namely programmers. 

Before we go further, let's examine what exactly we mean by the term "craftsmanship":

"The practice and pursuit of excellence in building/delivering superior work products by workers."

This implies craftsmanship is a universally applicable concept for any field of endeavor, be it producing a product or delivering a service. Basically, it is a commitment to excellence which is most definitely not the same as quality. Quality simply relates to the absence of errors or defects in the finished product or service. In other words, finished goods operate according to their specifications (customers get precisely what they ordered). Although quality is certainly an element of craftsmanship, the emphasis on "superior work products" means the worker wants to go beyond the status quo and is constantly looking for new and imaginative ways to produce superior results. This suggests the craftsman is personally involved with the work products and treats them as an extension of his/her life.

Craftsmanship can be found in either the overall work process or a section of it.

Business analysts often end up in this role by accident, as their careers evolve. They are perhaps called on to work jointly with the business or computer department, and end up linking the two. Two major sources of BA professionals can therefore be considered: the computer world (e.g. architects, developers) and the business world.

What is the best background for becoming a business analyst? The debate is still ongoing in the community. Both have their qualities and their faults—computer people have a tendency to anticipate the solution while mangers sometimes lack the knowledge to interact with IT.

I believe that good business analysts are above all specialists in business analysis. They have backgrounds in both disciplines and act as a bridge between the two worlds.

Requirements Risk management could be a useful approach to requirements analysis, and lead to better requirements management.

High level the idea goes like this:

Risk management is an important part of project management
Requirements management is also a critical part of the puzzle
Should we be running a requirements risk management process on our projects?
The purpose of this article is to introduce the topic of Requirements risk into the Requirements Management discussion. Feedback and commentary is welcome and can be provided at ModernAnalyst.com

Whether you call them Systems Analysts, Business Analysts, Systems Engineers, or Enterprise Architects, it is very encouraging to see this vital function being reintroduced to companies. As far as I am concerned, it was inevitable. I guess companies finally figured out you cannot satisfy your systems problems simply by using better programming tools and techniques.