The Decision Model (TDM) is a methodology and framework for modelling the business logic behind business decisions. Its popularity, adoption, and number of ground-breaking success stories are increasing significantly. TDM, as a powerful but simple graphical notation, is easy for both business people to understand and IT professionals to implement. As such, it puts business people in control of their business rules and logic and it accelerates IT’s ability to automate them quickly and without errors.

This article describes an integrated system of actions, tasks, and methods for managing project stakeholders. It highlights the strategic business actions, the tactical project tasks, and operational methods conducted by project sponsors, project managers and business analysts respectively.

 Analytics drive key strategic decisions in major corporations every day. However most legacy tools and solutions that help companies make these critical strategic decisions, simply aren’t built to deal with the reality of today’s modern business environment. Below are some essential questions to ask as you assess the potential benefits and limitations of new strategic analytic platforms for your organization.
 

Unified Modeling Language (UML) Activity Diagrams are rather like traditional flowcharts that may be used to describe the steps required to enact high level business processes or low level algorithms. From the software analyst’s perspective these diagrams are most useful for representing business processes, so this will be our focus here. Whereas activity diagrams are often relegated to the final chapters of the UML text books, I prefer to present them up-front as the logical starting point for any UML analysis and design endeavor.

Sure, you put a lot of time into creating a prototype, a mockup, screenshot, or wireframe (are there any other names for the user interface drawing I’ve missed?). You may have drawn it on a whiteboard, in VISIO, or even used a requirements tool to create it. At the end of the day, no matter how much time you spend on it, it’s nothing more than a picture. And those of you who have worked in IT know developers cannot code and create a solution solely from a picture. 

As Business Analysts, we are involved in requirements development and management day in and day out with most of the time spent on eliciting, analyzing and specifying business and software requirements for multiple projects. We follow or adopt multiple frameworks, approaches and tools that help us to successfully gather and analyze requirements. Having done all these things to ensure the success of the projects, we still end up in a few projects wherein we have “missed” few requirements.

An operational business decision has structure that you can’t capture using business process models, use cases, or similar techniques. If you fail to delineate that structure, you completely miss a core part of what makes business processes smart. The structure of a decision can be diagrammed in top-down, business-friendly fashion using a Question Chart (Q-Chart™ for short).

But what about user experience or interaction designers? Does every software project truly need a UX/UI specialist (or team of specialists)? Or could this aspect of the solution be taken care by the collaboration between the BA and the development team?

Unlike decision rules, behavioral rules do not pertain directly to determining the best or most appropriate answer (outcome) among alternatives... Three simple but typical examples in article illustrate. Avoid force-fitting a decision-oriented approach to every business rule problem. It simply doesn’t work!

As the Agile movement continues to gain momentum and managing projects using Agile methods becomes more and more prolific, project professionals must become more savvy in their use of Agile methods. While the techniques and processes associated with Agile are different than those associated with Waterfall, many innovative project teams are incorporating non-Agile techniques into the Agile environment, with great success.

Business analysts need to understand their role on a project. Please note I use the word 'role' and not 'job' or 'the work we do'. As business analysts, our role is to deliver business value. If you do not have a clear definition of what that business value is, how can you expect to deliver it? “Improve the customer experience.” Where is the business value in that? And how do you measure it? When faced with objectives that are poorly defined, the business analyst is allowed to become like that irritating toddler, constantly asking “why? why? why? why? why?”.

As a business analyst you are the all-important glue between the business and technology. Your skills range from various kinds of modeling to gathering of high-level as well as detailed robust requirements. Sometimes you operate in traditional systems development and sometimes within agile approaches. A business analyst’s responsibilities are wide and deep... What Are the New Opportunities for Business Analysts?

The CEO of a major corporation who was present when I described requirements traceability at a seminar asked, “Why wouldn’t you create a requirements traceability matrix for your strategic business systems?” That’s an excellent question. He clearly saw the value of having that kind of data available to the organization for each of its applications. If you agree with this executive's viewpoint, you might be wondering how to incorporate requirements traceability into your systems development activities in an effective and efficient way.

Recently I saw the movie “42,” based on the true story of Jackie Robinson,who in 1947 bravely fought custom, bigotry, and violent hostility to become the first African American to play major league baseball. His courage came from his inner strength which allowed him to withstand with dignity the cruel behavior from fans, other team managers and players, and at first some of his own teammates.

Many BAs are using the  BABOK which contains information about a Requirements Management process, from identifying organizational situations that give cause to a project, through to starting the requirements gathering process, to delivering a solution to the business or a client. TOGAF 9, from an Enterprise Architecture viewpoint, also provides some techniques to gather requirements to equally deliver business solutions. This paper illustrates the two processes, defines the mapping between the two approaches and identifies gaps in each.