Dec 21, 2025
1070 Views
0 Comments
This transition from “trust but verify” to “never trust and always verify” is a completely new way of thinking about the architecture of cybersecurity. At the heart of this change is the role of the Business Analyst (BA), who, given their role, bridges the gap between busines...
This transition from “trust but verify” to “never trust and always verify” is a completely new way of thinking about the architecture of cybersecurity. At t...
“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 ...

More Articles

Jul 07, 2024
26376 Views
6 Likes
0 Comments

This article discusses capability-based detailed requirements (DTRs) for a selected Commercial-Off-the-Shelf (COTS) information system. A complete set of DTRs identifies which “Out-of-the-Box” (OOTB) capabilities are to be implemented as is, which need changing, which aren’t needed, and which unsupported capabilities need to be added. A spreadsheet-based template is offered for documenting and managing these requirements.

Jun 30, 2024
29023 Views
176 Likes
0 Comments

In business analysis, the Business Analysis Body of Knowledge (BABOK) serves as a comprehensive guide, offering structured methodologies and best practices. However, it is crucial to remember that "the map is not the territory," a phrase coined by the Polish-American philosopher and engineer Alfred Korzybski. He used it to convey the fact that people often confuse models of reality with reality itself. While BABOK is a valuable resource, it is not an absolute authority. Business analysts must exercise flexibility and critical thinking, adapting the guidelines to fit the unique context and needs of each project. Next, we explore why the BABOK should be seen as a guideline rather than a rigid rulebook.

Jun 23, 2024
25576 Views
6 Likes
0 Comments

Systems analysts play a crucial role in bridging the gap between business needs and technology solutions. To be successful in 2024, they need a mix of technical, analytical, and communication skills.

This is because they have to understand complex systems, determine what businesses need, and ensure that tech solutions meet those needs.

Good systems analysts also have to stay on top of the latest technology trends and be able to work well with both tech teams and non-technical business staff.

 

Jun 16, 2024
22228 Views
167 Likes
0 Comments

Professionals in the dynamic field of business analysis must constantly adjust to shifting surroundings and a wide range of stakeholder needs. Surprisingly, there are a lot of lessons to be gained from the natural world, especially from chameleons, which are known for their remarkable adaptability.

Let’s discover useful insights that can be applied to the subject of business analysis as we examine the striking parallels between a chameleon and a business analyst (BA).

Jun 09, 2024
30530 Views
10 Likes
0 Comments

This article discusses the role of Capability-Based High-Level Requirements (HLRs) when an organization has chosen to acquire a Commercial-Off-The-Shelf (COTS) information system. The objective of the system is to contribute to the solution to a business problem or help take advantage of a business opportunity.

Page 16 of 100First   Previous   11  12  13  14  15  [16]  17  18  19  20  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