Search

Capturing Requirement Attributes In Use Cases

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. So, what are attributes of requirements? 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- Complexity – Specifies how difficult it is to implement the requirement. This may be a subjective guesstimate made by the person eliciting and documenting the particular requirement. Complexity may be specified as ‘High’, ‘Medium’, ‘Low’ etc. when writing a use case description Absolute Reference – Unique identifier for the requirement. It remains same even if the requirement is moved, changed or deleted. This will be your unique use case ID. Risk – These are the severity levels of the uncertain events that may impact requirements. Risk may be specified as ‘High’, Medium’, ‘Low’ again in a use case. Author – Specifies who wrote the requirement or who is to be consulted if requirement is unclear. This attribute is important as it helps in situations where further clarification about requirements is required at a later stage such as during coding or testing. I know we don’t normally specify this in a use case description, but this should become the best practice. Source– Specifies the origin of the requirement. For example if we are eliciting requirements for a mobile version of a CRM solution for the sales department, we may elicit an important requirement from a sales executive on the field. The requirement may be documented in the use case as a scenario and it is important to mention the source so that the stakeholder can be contacted in future for further clarification. Stability – Describes the maturity of the requirement. Specifies whether the team is still in the initial stages of eliciting the requirement, whether elicitation and analysis is complete, whether adequate information has been gathered to ensure that the requirement may not change in the foreseeable future. Ownership– This identifies the individual or group that needs the requirement. This may be the business owner / sponsor or even a business division. For example, the owners of the CRM mobile solution for which requirements are being elicited can be the Sales Department. Urgency– It is important to indicate how soon the requirement is needed so that resources and schedules can be adjusted to implement and deliver the requirement as soon as possible. Urgency of requirements can again be documented as ‘High’, ‘Medium’, and ‘Low’. Priority– This indicates the relative importance of a requirement against other requirements. This can again be documented as ‘High’, ‘Medium’, and ‘Low’ and is important to clearly define the business priority against each use case as it will help identify features for the Minimal Viable Product (MVP). State– Indicates where the requirement definition stands. In the case of use cases this specifies whether the use case is in draft, reviewed, approved / rejected, implemented state etc. 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.
Rated 4.5/5 based on 20 customer reviews

Capturing Requirement Attributes In Use Cases

7K
Capturing Requirement Attributes In Use Cases

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.

So, what are attributes of requirements?

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-

  • Complexity – Specifies how difficult it is to implement the requirement. This may be a subjective guesstimate made by the person eliciting and documenting the particular requirement. Complexity may be specified as ‘High’, ‘Medium’, ‘Low’ etc. when writing a use case description
  • Absolute Reference – Unique identifier for the requirement. It remains same even if the requirement is moved, changed or deleted. This will be your unique use case ID.
  • Risk – These are the severity levels of the uncertain events that may impact requirements. Risk may be specified as ‘High’, Medium’, ‘Low’ again in a use case.
  • Author – Specifies who wrote the requirement or who is to be consulted if requirement is unclear. This attribute is important as it helps in situations where further clarification about requirements is required at a later stage such as during coding or testing. I know we don’t normally specify this in a use case description, but this should become the best practice.
  • Source– Specifies the origin of the requirement. For example if we are eliciting requirements for a mobile version of a CRM solution for the sales department, we may elicit an important requirement from a sales executive on the field. The requirement may be documented in the use case as a scenario and it is important to mention the source so that the stakeholder can be contacted in future for further clarification.
  • Stability – Describes the maturity of the requirement. Specifies whether the team is still in the initial stages of eliciting the requirement, whether elicitation and analysis is complete, whether adequate information has been gathered to ensure that the requirement may not change in the foreseeable future.
  • Ownership– This identifies the individual or group that needs the requirement. This may be the business owner / sponsor or even a business division. For example, the owners of the CRM mobile solution for which requirements are being elicited can be the Sales Department.
  • Urgency– It is important to indicate how soon the requirement is needed so that resources and schedules can be adjusted to implement and deliver the requirement as soon as possible. Urgency of requirements can again be documented as ‘High’, ‘Medium’, and ‘Low’.
  • Priority– This indicates the relative importance of a requirement against other requirements. This can again be documented as ‘High’, ‘Medium’, and ‘Low’ and is important to clearly define the business priority against each use case as it will help identify features for the Minimal Viable Product (MVP).
  • State– Indicates where the requirement definition stands. In the case of use cases this specifies whether the use case is in draft, reviewed, approved / rejected, implemented state etc.

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.

Rumesh

Rumesh Wijetunge

Chief Innovation Officer - Zaizi Limited, Chief Operating Officer - LearntIn (Pvt) Ltd., Director /

Rumesh is an IT business leader with over 12 years of industry experience as a business analyst and project manager. He is currently the CIO of Zaizi Limited, a UK based data management company heading the operations in Sri Lanka, the COO of LearntIn, a global training institute based in Sri Lanka and is also a lecturer / trainer at multiple private universities on management, IT, business analysis and project management subjects. He is the current president of the IIBA Sri Lanka chapter and is one of the most qualified and sought after trainers in Sri Lanka. Refer his LinkedIn profile for more details and to see more articles he has written on linkedin

Join the Discussion

Your email address will not be published. Required fields are marked *

Suggested Blogs

The Certification World Of Business Analysis

Business Analysis has become one of the most promising career options currently in the corporate world.  The most prominent reason for failure of most projects has been attributed to poor business analysis which includes reasons like inadequately captured requirements, unclear business goals and objectives. There is a gap between what the clients wants and what we deliver to the client. Effective business analysis can help bridge that gap. Companies have started to realize the importance of business analysis, and there are opportunities globally to identify suitable business analysts to drive the projects to be successful, to ensure the client remains satisfied as we are able to deliver what is expected, and also the solution proposed provides business value to the client and also helps increase the revenues of the organization. It has now become important for a person to be certified in business analysis to take on the opportunities of business analysis in the organizations IIBA, International Institute of Business Analysis, the leading organization in business analysis have realized that there is a certification program to cater to any kind of professional in the industry. There are 4 kinds of certifications offered by IIBA based on the experience level of an individual. The certifications on offer are the ECBA ® (Entry Level Certificate in Business Analysis), CCBA® (Certification for Competency in Business Analysis), CBAP® (Certified Business Analysis Professional) and Certified Business Analyst Thought Leader® (CBATL) ECBA ®(Entry Level Certification in Business Analysis):- This is the certification for individuals who want to enter the field of business analysis. Some key pointers about ECBA® are: (1) No prior experience in business analysis is a prerequisite to this certification. (2) 21 hours of professional development in last 4 years is required to apply for this exam. (3) ECBA® exam is of 1 hour long duration and includes 50 multiple choice questions. CCBA®(Certification for Competency in Business Analysis):- This  CCBA certification for professionals with a minimum of 3750 hours or 2 to 3 years of business analysis experience. Some key pointers about CCBA® are:-                            (1) 3750 hours of work experience in the last 7 years of which a minimum of 900 hours in atleast 2 of the 6  BABOK®(Business Analysis Body of Knowledge) Guide Version 3.0 knowledge areas or minimum of 500 hours in atleast 4 of the 6 BABOK®(Business Analysis Body of Knowledge) Guide Version 3.0 knowledge areas is required (2) 21 hours of professional development in last 4 years is required to apply for this exam. (3) CCBA® exam is of 3 hour long duration and includes 130 multiple choice questions. CBAP ® (Certified Business Analysis Professional):- This CBAP certification for business analysis professionals with a minimum of 7500 hours or 5 years of business analysis experience. Some key pointers about CBAP® are:- (1) 7500 hours of work experience in the last 10 years of which a minimum of 900 hours in atleast 4 of the 6     BABOK®(Business Analysis Body of Knowledge) Guide Version 3.0 knowledge areas is required. (2) 35 hours of professional development in the last 4 years is required to apply for this exam. (3) CBAP® exam is of 3.5 hour-long duration and includes 120 multiple choice questions. CBATL® (Certified Business Analysis Thought Leader):- This is the certification for business analysis professionals which have over 10 years of experience.   Pursuing these certification programs provides a large number of advantages to the working professionals looking to build their career in the field of business analysis:- Personal Recognition:- Being a certified business analyst provides you recognition across the business analysis community and also in being connected with like minded business analysis professionals. Effective Business Analysis Execution:- Knowledge possessed by reading the BABOK®(Business Analysis Body of Knowledge) can be applied in the real life environment, and this leads to effective business analysis execution as the best practices outlined in the BABOK® are put into practice. Professional Development Opportunities:- Business Analysis is a promising career option and there are opportunities available worldwide for certified business analysis professionals. Increased Income:- Completing the business analysis certification can get you a promotion from a business analyst to a senior business analyst position in your organization, or can land you a job in a prestigious company in a business analysis profile.
Rated 4.5/5 based on 20 customer reviews
6665
The Certification World Of Business Analysis

Business Analysis has become one of the most promi... Read More

7 Tools to Improve Your Business Writing Skills

Now, if you are not so confident in your business writing skills but time calls and you need to step up your game there are quite a few things that you might want to take into account. Luckily for you, there are quite a lot of available tools online which will provide you with a lot of prominent capabilities that you need to take into account. With this in mind, let’s go right ahead and take a look at 7 of them which are particularly convenient. 1. Wridea This is a tool which is going to help you out with the preliminary part of your writing. Before you go ahead and sit down to write something, the first thing you do is organize your thoughts and ideas into a proper table in order to make them easy to follow. This is where this tool comes into the picture. It’s free and you can work on all of your ideas throughout the usage of tools provided by the platform. Apart from those, there are other things that you can take into account of. You can invite your friends so that you can organize your thoughts together. 2. Grammarly Grammarly is an educational platform which is going to ensure that everything is handled as per the highest standards. This is something particularly important, especially when it comes to business writing. You need to ensure that everything is taken care of perfectly so that you can rest assured that your business writing is professional and appealing. The last thing you’d want is to have mistakes in your writing. Make sure that it’s perfectly flawless and polished so that you don’t make a fool of yourself. Grammarly is a place where you can find a lot of helpful information. 3. Literatureandlatte.com This is another comprehensive service that you can take advantage of, especially if you have a fairly busy schedule. Thanks to this particular tool, you will have an easier way to go ahead and create a perfectly amazing story without having to place a lot of stress on yourself. The site comes with a free version of Scrivender which is going to help you make your writing tasks a lot easier. Furthermore, you will be provided with easy step-by-step guides that will show you how to prepare business plans as well as other important documentation. 4. Allcorrect.org Let’s be honest for a second – no one likes to proofread. That’s why you are a writer – to write. And, when you have so much work at hand, the last thing you’d want is to waste your time with having to go through everything carefully in order to proofread it. This is something that you need to account for when it comes to it. With the professional editorial team of Allcorrect.org, you will be given the chance of letting someone else do this jobs and probably better than you. The solution is reliable, affordable and of high quality and there isn’t a lot that you can ask for. 5. Dragon Dictation Now, this wouldn’t be a great list if there wasn’t a voice recognition app in it. The truth is that you would have to handle quite a lot of multi-tasking when it comes to business. Thanks to the technology that is currently available, there are tools that will make your life a lot easier in this regard. Dragon Dictation is an amazing app which would allow you to speak instead of write and the app will automatically transcribe it for you. This is a great way to handle your business writing communication as well as to place some convenient personal notes. 6. Stoodle Stoodle is another great site which is going to enable you to learn and improve quite a lot as a business writer. There are a lot of tools which are specifically designed to enable learners to have the best experience and this is one of them. With this particular website you will be given real-time communication as well as collaboration available online. If you need any additional help with your business matters, this is the place to find it. It’s definitely something that you might want to take into consideration. 7. Prowritingaid.com This is another convenient resource which is going to show you how to improve your business writing. This is an integrated software which turns your good writing in what can be perfect writing. You can easily improve your overall readability and handle different errors of any kind with this particular tool. It’s free to use and it’s basically an online editor which is going to help you check your grammar and ensure that everything is handled properly. The truth is that you can’t afford to look bad when it comes to business writing. This is something that you should definitely take into account and make sure that it’s worthwhile. You need it to be flawless because, after all, there is a lot which is at stake here. Your business writing is something which will potentially ensure the proper representation of your business and even get you new clients. This is something that you need to take into the most serious consideration because it could definitely reshape the overall appeal of your company. You shouldn’t underestimate its importance at all costs.
Rated 4.0/5 based on 20 customer reviews
16351
7 Tools to Improve Your Business Writing Skills

Now, if you are not so confident in your business ... Read More

BCW: The Nuts and Bolts of Preparing a Business Case

Every business needs a change in order to boost its productivity and performance. Getting quality work or projects from clients will play a major role in achieving this. A business would need to rake in stakeholders if it wants to bring about a substantial change. As there are many crucial things that are involved you won’t be able to get these stakeholders very easily. In such a situation, a business case plays its part. The business case is a document that will allow you to have an effective communication and convince the people that matter. These people called the stakeholders will deeply go through this document before they decide to finally buy-in. The business case will consist of all the valid reasons that will persuade a key person to support a project. The document will explain in details the aftermaths of a decision that is related to your business. Starting from the initial stage where all the important groundwork is done to finally implementing the whole process. By going through the business case a stakeholder can have a clear idea as to whether should buy-in or not. Qualities an Efficient Business Case The main purpose of a business case is to have an impact on the person who reads it. So, if you are among those who is planning to write one for your business, have a look at the below points. These points will enable you to draft an effective business case for your organization. Firstly, you need to do an in-depth research on all the possible effects on your business. This will also include the costs and the expected benefits. You must have a valid reason for all the points that you have put forward in the document. There must be a link between the costs incurred and what will be the impact of it on the benefits. All the possible outcomes that range from the positive and the negative issues should be presented in an effective manner. The business case that you present must be able to summarize all the important points and provide a proper judgment or verdict. Writing A Business Case Writing a business case is a job that cannot be performed by a single person. It’s a collective effort of an entire team. The requirement of a team is necessary due to the large amount of information that is needed to write the case. The team will have to conduct meeting within themselves so that all the relevant information can be used judiciously. Enrolling into a Business Case Writing (BCW) training course will prove to be very beneficial for an individual. You will be able to learn about all the basic and the advanced level skills that are needed to write an effective case. Who All Are In A Team? A team will consist of professionals that are related to different domains like finance, human resources and IT. Based on their roles they will cater the required information. This will include data related to the value and cost of the effect of IT operations, contributions that can be made to escalate the expected benefits and the cost that is associated with hiring people. What Should a Business Case Comprise of?  You can write a business case in whatever format you want to. There is no fixed pattern that needs to be followed. However, by including the below-mentioned points you can make your business proposal an impactful one. Title Page Table of Contents Project Summary Mission Statement Objective of the Project Performance Measures Needs Assessment Technical Analysis Project Work Plan Financial Plan Conclusion A business case is an integral part of project management. It will define all the management factors and parameters that are included in a project. With the help of this, a project manager can analyze a project in a step-by-step manner. I would love to have your views about the article. Do let me know about them in the comments section below.
Rated 4.0/5 based on 20 customer reviews
13285
BCW: The Nuts and Bolts of Preparing a Business Ca...

Every business needs a change in order to boost it... Read More

Useful links