The Community Blog for Business Analysts


Functional Specifications

NO Image:
If you are building a reusable Security Product tool to specifically address Security Technical Implementation Guide (STIG)  Findings, should the requirements be considered Non Functional Requirements or Functional Requirements? For example if there are a number of STIGs such as: The minimum password length shall be 15 characters ...
1 Responses
This entry was published on Aug 22, 2017 / Peter. Posted in Functional Specifications, Business Analysis. 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
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.
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.
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.
In my previous posts I outlined how I was able to succeed being the first and only BA at a company and the importance of establishing trust between you and the stakeholders.   So you're the first BA at a company.   All are looking at you and thinking what can this person do for me? Good question.   What can you do f...
0 Responses
Not a suggestion for eliminating the process of documenting a software application, but rather a proposed for replacement of the documenting activity and manually produced documents with something more manageable and less likely to frighten the development team. Initiative for this work comes from a number of discussions I have been following and ...
1 Responses
This entry was published on Mar 22, 2010 / Leslie. Posted in Requirements Management and Communication (BABOK KA), Functional Specifications, SDLC, Process, and Methodologies. Bookmark the Permalink or E-mail it to a friend.
  This model is provided by Don Firesmith of SEI.  Note the lack of an NFR category. More
4 Responses
This entry was published on Sep 24, 2009 / Craig Brown. Posted in Requirements Analysis (BABOK KA) , Functional Specifications, Systems Analysis, Business Analysis, Structured Systems Analysis (DFDs, ERDs, etc.). Bookmark the Permalink or E-mail it to a friend.
User stories have a place in modern requirements management.  They may not be going to replace use cases but you shoulod know how to write them well. Invest In Good User Stories View SlideShare presentation or Upload your own. (tags: agile scrum)
0 Responses
This entry was published on Jan 09, 2009 / Craig Brown. Posted in Requirements Management and Communication (BABOK KA), Functional Specifications, Systems Analysis, Agile Methods. Bookmark the Permalink or E-mail it to a friend.


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