Of all the reasons for data quality problems, I find user interface design issues to be the most interesting. This may be because it is tied to the software requirements, and I have worked as a requirements analyst for a number of years.

Next time you start to think that your stakeholder is crazy, ask yourself why. Chances are that there is a rational rationale, and it will be up to you to come up with a solution that meets the needs of your organization and your stakeholders.

The World Cup fever is in full swing, presenting an opportunity for all of us to reflect on some real-life lessons the world of football (soccer) offers to BAs interested in getting better at their craft.

I have had business friends over the years ask me why it seems so difficult and time consuming to upgrade their corporate systems to take advantage of the latest computer technology. In their minds, their systems are relatively simple; the concepts of such things as accounts receivable, accounts payable, inventory, manufacturing, etc. are relatively straight forward. Yet, companies incur millions of dollars in keeping them up-to-date. The question is, "Why?"

The TDM business glossary is the home for naming conventions, data types, and domain values that are meaningful to, and defined by, the business audience. Best of all is that resulting decision models are exactly as the business community wants and in the business’s own terminology.

In this day and age of “globalization” more and more Information Systems are crossing geographical boundaries. Because of this, serious consideration should be given to making systems universally applicable to any country. Some might consider this an impossible task, but it is actually easier than you might think. It just requires a little common sense and some planning.

As a business analyst (BA), what would you say during the initial conversation with your project manager (PM)? First, do not assume that the PM knows what to expect from a BA. In fact, this is your opportunity to set expectations and explain your value added to the project.

Tracking project status means comparing where you really are at a particular time against the expectation of what “complete” means for this development cycle.  Monitor the status of just those functional requirements that were committed for the current release, because that’s the set that’s supposed to be 100 percent done before you declare success and ship the release.

In my experience of pursuing the CBAP certification, while there are tangible benefits from the outcome of being certified, there are some very real and very significant benefits generated as a by-product of the certification process itself, even when it was painful and downright frustrating.

Some programmers consider documentation a waste of time (see “Agile programming”), even going so far as to claim it is detrimental to productivity. Instead of getting all the software specifications recorded on paper at the start, they prefer to begin hacking on the program code and keep modifying it until the end-user is satisfied.

Probably the most used facilitation technique in business analysis is brainstorming.  In summary, a group meets with a facilitator and attempts to gather as many ideas as possible to address a problem. The facilitator sets rules at the beginning of the session of which the most important is “no adverse judgment of ideas” during the session.

Many BAs (especially the most experienced ones) should be familiar with processes...  Let us try to reveal, how BA skills are applicable to BPM and which steps a BA should take to transfer their knowledge to a state sufficient to fully enter the BPM sphere.

Now we delve into data modeling, one of the core model types. We choose to start here because data requirements are an important foundation for most information technology projects. If you are a business analyst and not doing data modeling today, you should be able to at least read them to validate requirements against what a data modeler has created and our bias is that business analysts can and should be doing “functional” data modeling.

In the real world, good decision modeling is always a balance between science and art. The science is systematic decomposition of a structure (of data or logic) into a set of smaller structures based on the definitions of successive normal forms. The art, on the other hand, is a general decomposition into a set of smaller structures based on factors not related to detecting and correcting normalization errors.

How often has a customer asked you to write software that is user-friendly, robust, fast, or secure? No one will argue that those are worthy goals that everyone wants in their software products. However, they are terrible requirements. They give you no idea of just what “user-friendly” means, or how to tell if you’ve achieved the desired characteristics that mean “user-friendly” to a particular customer.