Dec 14, 2025
1056 Views
0 Comments
“Let’s add AI” is not a requirement. It’s a vague wish that can turn into a costly prototype, a security headache, or an embarrassing production incident if the basics aren’t defined up front.  Business Analysts are in the best position to prevent that outcome...
“Let’s add AI” is not a requirement. It’s a vague wish that can turn into a costly prototype, a security headache, or an embarrassing production incident if...
An inflection point. A forcing function. A once-per-civilization opportunity to prove that human judgment, contextual understanding, and adaptive intelligence remain indispensable ...
This article describes using a Requirements-Friendly Data Dictionary (RFDD) as an alternative to representing a software solution’s data-related requirements as User Stories,...

More Articles

20838 Views
2 Likes
0 Comments

There’s always more than one design solution for a software problem and seldom a single best solution. The first design approach you conceive won’t be the best option. As one experienced designer explained it:

You haven’t done your design job if you haven’t thought of at least three solutions, discarded all of them because they weren’t good enough, and then combined the best parts of all of them into a superior fourth solution. Sometimes, after considering three options, you realize that you don’t really understand the problem.

15879 Views
1 Likes
0 Comments

Is your requirements approach friendly to vocabulary, policies and messages? I mean directly. Wouldn’t it be of great help to your organization in achieving its goals if they were? In our experience, policy sources almost always need interpretation and disambiguation to achieve an effective practicable form. As this column discusses, the rule message ‘Reserved for Green Car’ provides an excellent case in point.

20706 Views
3 Likes
0 Comments

It is true that a structural element of the conceptual framework of the BABOK knowledge areas is tailoring. The philosophy that a specific sequential approach does not fit in all circumstances is clear across all the knowledge areas and techniques presented. A business analyst has to critically filter and pick up the most useful techniques and approaches given the specific circumstances.

48357 Views
14 Likes
0 Comments

I was teaching a business analysis course recently and noted that few students had used a Fishbone Diagram along with the Five Whys for root cause analysis. This motivated me to write an article on root cause analysis using the combo method along with a short example.

19062 Views
0 Likes
0 Comments

BPMS has evolved and has come a long way over the past one or two decades. It's quite interesting to take a peek into the BPMS journey then and now. Business needs and technology, both have gone through a huge change in the meantime.

Right since the earlier days of BPMS, I always found working in this space quite an intriguing thing. The very capability of BPM to model, design, automate, run and track any process seemed to be extremely useful.

Page 46 of 100First   Previous   41  42  43  44  45  [46]  47  48  49  50  Next   Last   

Templates & Aides

Templates & AidesTemplates & Aides: find and share business analysis templates as well as other useful aides (cheat sheets, posters, reference guides) in our Templates & Aides repository.  Here are some examples:
* Requirements Template
* Use Case Template
* BPMN Cheat Sheet

Community Blog - Latest Posts

One of the most underrated skills for a business or system analyst in integration projects is knowing when to recommend a message queue — tools like RabbitMQ, Kafka, or Azure Service Bus. Let’s be honest: not every integration needs one. But when it does, queues can save your system from chaos. What Queues Actually Solve Messag...
When building integrations between systems, one of the first architectural choices you’ll face is how to align data between them. Two main approaches dominate this conversation: direct field mapping and the canonical data model. Let’s break them down. Field Mapping: Simple but Fragile Field mapping means you connect each field f...
System Analysts who work with integration processes should formulate user stories in a way that diverges from the traditional structure. This is primarily due to the need for a more technical and structured description, which allows for the inclusion of integration-specific details. The user story might need to specify exactly what kind of data ...

 



Upcoming Live Webinars

 




Copyright 2006-2025 by Modern Analyst Media LLC