Different requirement classifications in business analysis.

Updated: Jun 7, 2019


Business Analysis role has been growing and evolving so fast over the years that it is not even bound by the usual boundaries in some organisations. Business analysis has become a broad profession where business analyst performs work for many different kind of initiatives for the enterprise.


So what exactly is business analysis and how many different kind of requirements are there?


Simply put, business analysis is the practice of enabling change in an enterprise by defining needs and recommending solutions that deliver value to stakeholders. An enterprise can articulate needs and the rationale for change. Business analysts help the enterprise to design and describe solutions that can deliver value.


Going beyond the usual use cases and functional requirements, its important to understand the overall map of what different kind of requirements a business analyst needs to analyse and how they are interconnected.


Look at the below categorisations:

  1. Business requirements: statements of goals, objectives, and outcomes that describe why a change has been initiated. They can apply to the whole of an enterprise, a business area, or a specific initiative.

  2. Stakeholder requirements: describe the needs of stakeholders that must be met in order to achieve the business requirements. They may serve as a bridge between business and solution requirements.

  3. Solution requirements: describe the capabilities and qualities of a solution that meets the stakeholder requirements. They provide the appropriate level of detail to allow for the development and implementation of the solution. Solution requirements can be divided into two sub-categories: functional requirements: describe the capabilities that a solution must have in terms of the behaviour and information that the solution will manage, and non-functional requirements: do not relate directly to the behaviour of functionality of the solution, but rather describe conditions under which a solution must remain effective or qualities that a solution must have.

  4. Transition requirements: describe the capabilities that the solution must have and the conditions the solution must meet to facilitate transition from the current state to the future state, but which are not needed once the change is complete. They are differentiated from other requirements types because they are of a temporary nature. Transition requirements address topics such as data conversion, training, and business continuity.

Familiarise yourself with these classifications and then as a business analyst, you can decide how and in which format you want to document them. It doesn't matter whether you use Predictive (waterfall) or Agile methods. The way you categorise requirements and connect them remains unaffected,


Will cover these in more details in upcoming posts.


Happy reading!

What is it that fuels you? For me, it’s agileincrement.com

 

 I love writing about my passions, what interests me, what interests others, and sharing all of my thoughts with my readers. I hope you enjoy browsing my site and all of the unique content I have to offer. Take a look around; perhaps you’ll discover what fuels you as well. Read on and enjoy!

©2018 Agile Increment