The Community Blog for Business Analysts


Requirements Analysis (BABOK KA)

NO Image:
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
  ISO 25010, "Systems and software engineering - System and software quality models" was published in March 2011. The ISO 25010 standard defines 2 broad non-functional categories of requirements, "Quality in use" and "Product quality", articulated in 13 characteristics, many of which are further subdivided into sub-characteristics. This new ...
1 Responses
This entry was published on Jan 20, 2012 / Adriano Comai. Posted in Requirements Analysis (BABOK KA) , Requirements Management and Communication (BABOK KA), Testing & Quality Assurance (QA). Bookmark the Permalink or E-mail it to a friend.
Requirements gathering is an essential part of any project and project management. Understanding fully what a project will deliver is critical to its success. This may sound like common sense, but surprisingly it's an area that is often given far too little attention. Many projects start with the barest headline list of requirements, only to find ...
2 Responses
This entry was published on Jun 08, 2011 / a.prvz. Posted in Elicitation (BABOK KA), Requirements Analysis (BABOK KA) , Business Analysis. Bookmark the Permalink or E-mail it to a friend.
I have spent the last year and a half working on an enterprise software solution development effort where we do not use a Requirements Management tool like Caliber or Visual Studio TFS. Our requirements are created in Word using standardized templates and distributed to Development and Test teams for consumption. Test cases are written in Excel an...
1 Responses
I've been blogging lately about a couple of topics pertaining to 'agile' methods. Along those lines, I wanted to consider one suggested practice that I think is worth reflecting on, that is; the treatment of NFRs (non-functional requirements) as stories. Let's draw back for a moment. Regardless of process approach, be it traditional or agile, po...
0 Responses
This entry was published on Dec 17, 2010 / FergalMcGovern. Posted in Business Analysis Planning (BABOK KA), Requirements Analysis (BABOK KA) , Requirements Management and Communication (BABOK KA). Bookmark the Permalink or E-mail it to a friend.
Page 3 of 4First   Previous   1  2  [3]  4  Next   Last   

Modern Analyst Blog Latests

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-...
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...
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

 



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.

 




Copyright 2006-2021 by Modern Analyst Media LLC