The Community Blog for Business Analysts


Requirements Analysis (BABOK KA)

NO Image:
Requirements define the needs of the project to provide best of its utility and benefits. If they aren’t clear or analysis is not done properly, it might lead to failure of the project no matter how good the concept and design is. Just as a system is composed of various functionalities, requirements too are identified in various forms. This ...
1 Responses
This entry was published on Apr 10, 2017 / Surbhi Mahnot. Posted in Requirements Analysis (BABOK KA) , Requirements Management and Communication (BABOK KA). Bookmark the Permalink or E-mail it to a friend.
All professionals talk about identifying business needs, identifying requirements to create tools so that they can help businesses take better decisions. In your career as an IT professional, I am sure at some point you must have heard terms such as “Requirements”, “Business Requirements”, “Software Requirements”...
3 Responses
This entry was published on Mar 16, 2017 / Surbhi Mahnot. Posted in Requirements Analysis (BABOK KA) , Requirements Management and Communication (BABOK KA). Bookmark the Permalink or E-mail it to a friend.
As business analysts, we are often in the fray of designing.  Whether it’s a user interface, report or data fed from one system to another; business analysts create interfaces with human beings and systems.  Our design choices impact users and other systems in a very real way.  This power can go unnoticed even in our own minds....
1 Responses
Scope – the last frontier.  We are on a mission where no business analyst has gone before.  To explore strange new diagrams and to have the project scope clearly understood.  Extra credit to those who remember which TV show that was from!  Scope and context are the number one reason business expectations about a project ar...
0 Responses
Being a badass isn’t about intimidation or trying to be something you simply are not.  It’s about knowing who you are and using your strengths to drive forward.  So let’s look at a few of the ways to be a badass in business: 1. Passion for Your Craft Is a Powerful and Infectious Energy Showing passion for your work in ...
1 Responses
The  International Institute of Business Analysis defines in its “Business Analysis Body of Knowledge” (BABoK) that business analysis is “the practice of enabling change in an enterprise by defining needs and recommending solutions that deliver value to stakeholders”. To fulfil this task to a good standard bus...
1 Responses
This entry was published on Aug 30, 2016 / Katarzyna. Posted in Requirements Analysis (BABOK KA) . Bookmark the Permalink or E-mail it to a friend.
The previous two posts in the Requirements Prioritization series, we discussed the honest difficulty that stakeholders face when asked to simply prioritize requirements, and how to overcome this obstacle by using prioritization parameters. If you have not read these posts, I recommend you read them first here and here....
1 Responses
This entry was published on Jun 08, 2016 / Praveen Udupa. Posted in Requirements Analysis (BABOK KA) . Bookmark the Permalink or E-mail it to a friend.
If you’re a business analyst whose company recently made the move to agile, you may be wondering where you fit in when there is no business analyst role. Or maybe you made the move to be an agile business analyst or product owner but don’t know how your traditional business analyst skills figure into this new agile world. Well the good ...
0 Responses
This entry was published on May 31, 2016 / Candase Hokanson. Posted in Requirements Analysis (BABOK KA) , Data Analysis & Modeling, Agile Methods. Bookmark the Permalink or E-mail it to a friend.
In my previous blog post titled "All requirements are important!", I reasoned that stakeholders only appear to be uncooperative in the prioritization process. In reality, they are unable to prioritize requirements because they cannot see one requirement more or less important than the other. I urged you to ponder whether ...
4 Responses
This entry was published on May 19, 2016 / Praveen Udupa. Posted in Requirements Analysis (BABOK KA) , Business Analysis. Bookmark the Permalink or E-mail it to a friend.
This is in continuation of my earlier post on Business Requirement. If you have not read that post, I recommend you take a few minutes to study that first before continuing with this post. In this post, let's discuss Stakeholder Requirement. Some people refer to this as User Requirement, but BABOK's nomenclature is Stakeholder Requi...
0 Responses
This entry was published on May 06, 2016 / Praveen Udupa. Posted in Requirements Analysis (BABOK KA) , Functional Specifications, Business Analysis. Bookmark the Permalink or E-mail it to a friend.
"Business Requirement" is a maligned phrase. Different people have different interpretations for what it means. The worst interpretation that I have come across is, “hey, if the requirement comes from a business stakeholder, then it is a business requirement”. Requirement from business is NOT business requirement. For God's sake, every ...
2 Responses
This entry was published on May 06, 2016 / Praveen Udupa. Posted in Requirements Analysis (BABOK KA) , Functional Specifications, Business Analysis, IIBA & BABOK. Bookmark the Permalink or E-mail it to a friend.
Years ago, I was consulting as a Principal Business Analyst for the second largest company in the world in the money transfer business. One fine morning, I was engrossed in my work when my business stakeholder, (let's call him Tom) arrived at my desk.  Tom: Praveen, I have a change request for you. Well, this is a new business requiremen...
2 Responses
This entry was published on May 01, 2016 / Praveen Udupa. Posted in Elicitation (BABOK KA), Requirements Analysis (BABOK KA) . Bookmark the Permalink or E-mail it to a friend.
Use case modelling is the most powerful requirements modelling technique to model solution requirements if applied correctly. I have come across many BA teams (including my own) that made lot of common mistakes in use case modelling. By avoiding the top 10 mistakes identified in this paper, BA teams can not only save lot of efforts in use...
1 Responses
This entry was published on Jan 10, 2016 / Trividh Patel, CBAP. Posted in Requirements Analysis (BABOK KA) , Use Cases, Functional Specifications, Systems Analysis, Business Analysis. Bookmark the Permalink or E-mail it to a friend.
The question will undoubtedly arise during your tenure as a business analyst, ‘How do I manage a difficult stakeholder?’ I once encountered a stakeholder, a very highly respected mathematician, who had developed an application based on a mathematical model of his weather systems. The algorithm was amazing. The application sucked. It wa...
4 Responses
As part of preparation to sit the IIBA CBAP exam, I wanted a one page summary of the overall BABOK flow. The first step of creating a summary matrix showing a derived master list of documents (e.g. Inputs + Outputs) versus the process that creates or uses it was interesting, but not entirely helpful. By using the matrix to create an indicative ...
1 Responses
Developing requirements is a process with many moving parts. It involves aligning multiple stakeholders from different areas within an organization to determine what must be developed to fulfill a business need.  Because it is a process, there are a number of factors that can cause the process to break down and lead to the development of fault...
0 Responses
This entry was published on Aug 07, 2013 / Ken Young. Posted in Requirements Analysis (BABOK KA) , Requirements Management and Communication (BABOK KA), Functional Specifications, Business Analysis. Bookmark the Permalink or E-mail it to a friend.
Background The Agile methodology originated within the software development industry. Since its inception in 2001 – Agile has expanded beyond an initial developer-centric community – to being embraced by multi-discipline teams working across numerous industries. The antecedent of Agile within IT was the Waterfall methodology. The Waterfall framew...
0 Responses
This entry was published on May 27, 2013 / Ryan Thomas Hewitt. Posted in Requirements Analysis (BABOK KA) , Soft Skills, Agile Methods. Bookmark the Permalink or E-mail it to a friend.
For those of you who do define requirements for their software development projects, but are new to buying packages, a cautionary warning; they are not the same thing. Consider the following “the system shall” requirement  statements.   1) The system shall determine if a person ordering pizza is a current customer. 2) The system shal...
0 Responses
This entry was published on Feb 08, 2013 / David Wright. Posted in Elicitation (BABOK KA), Requirements Analysis (BABOK KA) . Bookmark the Permalink or E-mail it to a friend.
In the wide world of information systems, development of new software receives the most attention from industry writers. Whether it is traditional magazine articles and books, or blog posts, or discussions in groups on LinkedIn and other sites, it is all about “green field” development. However, when one considers the wider view of organizations c...
0 Responses
This entry was published on Dec 30, 2012 / David Wright. Posted in Requirements Analysis (BABOK KA) . Bookmark the Permalink or E-mail it to a friend.
  Its quite a feat of strength to pretend you don’t have any weaknesses. I don’t pretend to be that strong. Its quite a bit easier for me to look for faults, gaps, misses, short comings, imperfections and details that spell out why something is not right. Its a blessing and a curse. Looking at my deliverables in this light is second nature...
0 Responses
Page 1 of 2First   Previous   [1]  2  Next   Last   


Blog Information

» What is the Community Blog and what are the Benefits of Contributing?

» Review our Blog Posting Guidelines.

» I am looking for the original Modern Analyst blog posts.



Modern Analyst Blog Latests

Jarett Hailes
Jarett Hailes
As we start a new year many of us will take the time to reflect on our accomplishments from 2012 and plan our goals for 2013. We can set small or large goals. goals that will be accomplished quickly or could take several years. For 2013, I think Business Analysts should look to go beyond our traditional boundaries and set audacious goals. Merriam-...
2 Responses
Howard Podeswa
Howard Podeswa
Recently, I was asked by the IIBA to present a talk at one of their chapter meetings. I am reprinting here my response to that invitation in the hope that it will begin a conversation with fellow EEPs and BAs about an area of great concern to the profession. Hi xx …. Regarding the IIBA talk, there is another issue that I am considering. It's p...
11 Responses
Adrian M.
Adrian M.
Continuing the ABC series for Business Analysts, Howard Podeswa created the next installment titled "BA ABCs: “C” is for Class Diagram" as an article rather than a blog post. You can find the article here: BA ABCs: “C” is for Class Diagram Here are the previous two posts: BA ABCs: “A” is for Activity Diagram BA ABCs: “B” is for BPMN
1 Responses
Featured Digital Library Resources 
Copyright 2006-2015 by Modern Analyst Media LLC