The Guide to the Business Analysis Body of Knowledge® or the BABOK® Guide as popularly known, which is published by the International Institute of Business Analysis (IIBA) is the globally recognized standard for the practice of Business Analysis. It defines how industry practitioners playing any sort of analysis role and even business organizations should operate, to deliver value to stakeholders through which to achieve superior business change or outcomes.
The BABOK® Guide defines Requirements as a condition or capability that is required in a solution that is developed to achieve a change in a business which is operating within a certain business context. This business need that may be to solve a problem or to make tap into an opportunity is what is documented as different types of requirements using requirements modeling techniques as appropriate.
I will not be talking about ‘types of requirements’ or ‘types of requirements modeling techniques’ here. I invite you to investigate more on this. I will today be talking about what requirement attributes are and how we can specify these when modeling requirements as use case descriptions. Again, I will not be discussing what a use case is and the best practices when modeling requirements as a use case here in this article. That may be for a later day!!
A proper understanding of requirement attributes is essential for IIBA ECBA® certification, CCBA® certification and CBAP® certification. A person attempting the ECBA® and CCBA® exams must be able to list all the 10 attributes, as well as be able to discuss its importance in analyzing and managing requirements. For the CBAP® exam, the individual is expected to be able to apply the concepts of requirement attributes to a practical situation. Capturing requirement attributes when writing use cases is a practical scenario faced by business analysts on a daily basis and this article is expected to serve as a pre-cursor to get such thought process going.
The BABOK® defines requirements attributes as information about requirements. Requirements need to be managed during its lifecycle from identification right until it satisfies with a solution to the need for change. The information about requirements often pop-up or must be planned to be captured along with the requirements. These attributes help in effectively and efficiently managing requirements, methodically managing the change and efficiently managing the stakeholders.
As per the BABOK® there are ten pieces of information to be captured as attributes. They are-
Lots of information, isn’t it? ☺. How do we remember these first of all? I use the acronym ‘CARA’S SOUPS’ for this purpose taking the first letter of each requirement attribute.
I would now like to conclude by giving an extended template for a use case description. Why extended? A use case description has a defined set of sections that must be included such as pre-conditions, primary flow, alternate flows, exceptional flows, post-conditions etc. So, given below is the structure I use. You are free to use it or customize it as you deem fit.
We often miss out on these important pieces of information about requirements and get into trouble mid way in projects. So, let’s make sure that we capture requirements attributes for a smoother communication and implementation of requirements.