Requirements Analysis and Design Definition

This chapter covers the tasks that are used to structure the requirements that we have elicited and gathered.

During this chapter, you will learn what it means to verify and validate requirements, define the requirements architecture, and define the possible solution options that could be pursued. We will also describe the task of analyzing the potential value and provide guidelines for recommending a solution.

This chapter dives into some of the BABOK® v3 guide tasks—specifying and modeling requirements, verifying requirements, validating requirements, defining the requirements architecture, defining solution options, and analyzing the potential value and recommending a solution. We will also bring each task into the real world with scenarios and examples.

By the end of this chapter, you will understand the following concepts...

What is Requirements Analysis and Design Definition?

In the context of business analysis, the Requirements Analysis and Design Definition knowledge area describes the work involved in structuring and formulating the requirements information elicited during requirements elicitation activities.

Requirements and designs are important parts of an initiative where the business analyst has direct influence over supporting and guiding the changes that will be introduced. The level of detail of requirements and designs can vary depending on the purpose and the audience that will consume this information. It is imperative for the business analyst to model and captures the needs, requirements, and designs in an optimal way. This ensures effective communication of the required changes or solutions of the initiative to the appropriate stakeholders:

Requirements Analysis and Design Definition...

Business Analysis Core Concept Model™

Before we delve into each of the specific tasks in Requirements Analysis and Design Definition, let's understand how this knowledge area applies to BACCM™ with an example.

The six core concepts that are described in BACCM™ include the following:

• Change
• Need
• Solution
• Stakeholder
• Value
• Context

Here, we will consider how Requirements Analysis and Design Definition as a knowledge area applies to BACCM™ through the use of a practical example.

Change

This core concept refers to how elicitation results are transformed into requirements and designs in order to define change.

Let's look at an example to bring this concept around change to life.

Let&apos...

Task: Specifying and modeling requirements

The first task described as part of the Requirements Analysis and Design Definition knowledge area is about analyzing the requirements information that the business analyst has elicited from stakeholders and then creating requirements and design artifacts of those results.

In this section, we will cover the purpose of this task and the different aspects of specifying and modeling requirements in the context of the task's core elements. You will also learn the difference between a requirement and a design and how to apply these terms in your role as a business analyst.

Let's start by considering the purpose of this task.

Purpose

According to the BABOK® v3 guide, the...

Task: Verifying the requirements

The second task described as part of the Requirements Analysis and Design Definition knowledge area is about verifying the requirements so that the business analyst can ensure that the quality standards have been met and that the requirements are fit for purpose.

In this section, we will cover the different aspects of verifying the requirements and ensuring the requirements have been defined correctly. You will also learn about the important characteristics that a good requirement should always have. Let's start by considering the purpose of this task.

Purpose

The BABOK® v3 guide defines the purpose of verifying the requirements as follows:

"to ensure that requirements and designs...

Task: Validating the requirements

The third task described as part of the Requirements Analysis and Design Definition knowledge area is about validating the requirements that align with the business needs and support the delivery of the anticipated value.

In this section, you will learn about the nature of validating requirements and designs as part of your role as a business analyst. We will also outline the importance of making and documenting assumptions to ensure clear communication with stakeholders, both upstream and downstream in the delivery cycle. We will discuss the role of evaluation criteria to ensure the measurability of the value that our implemented requirements and designs will bring to the business. Let's now consider the purpose of the validating requirements task.

...

Task: Defining the requirements architecture

The fourth task described as part of the Requirements Analysis and Design Definition knowledge area is defining the requirements architecture. This task is about establishing the structure of all the requirements to form cohesive requirements that support the business objectives for the change.

In this section, you will learn about the different considerations when establishing a requirements architecture. You will also understand that a requirements architecture will assist the business analyst in all aspects of requirements management and communication throughout the life of the requirements. It will also become clear how the requirements architecture supports the successful delivery of the requirements. Let's start by defining the purpose of this task.

...

Task: Defining the design options

The fifth task described as part of the Requirements Analysis and Design Definition knowledge area is defining the design options. This task is about defining the solution approach as well as allocating requirements and designs in a way that will support achieving the desired future state.

In this section, you will learn about the different considerations when defining the design options.

Purpose

According to the BABOK® v3 guide, the purpose of defining the design options is as follows:

"to define the solution approach, identify opportunities to improve the business, allocate requirements across solution components, and represent design options that achieve the desired future state...

Task: Analyzing the potential value and recommending a solution

The sixth and final task described as part of the Requirements Analysis and Design Definition knowledge area is to analyze the potential value and recommend a solution. This task is about assessing the potential business value of each design option and recommending the best design option that will meet most of the business's defined requirements.

In this section, you will learn about the different considerations when analyzing the potential value of the design options, as well as what is involved when recommending a solution.

Purpose

According to the BABOK® v3 guide, the purpose of analyzing the potential value and recommending a solution is as follows...

Summary

In this chapter, you learned about the Requirements Analysis and Design Definition knowledge area.

The following are the key concepts and tasks we covered in this chapter:

• The Requirements Analysis and Design Definition knowledge area
• Specifying and modeling requirements
• Verifying requirements
• Validating requirements
• Defining the requirements architecture
• Defining the solution options

Make sure you revise these key learnings before completing the knowledge quiz at the end of this chapter.

You now have an understanding of the importance and purpose of the Requirements Analysis and Design Definition knowledge area and know what the scope is of performing analysis tasks for an initiative from an analysis point of view.

The learning outcome for the Requirements Analysis and...

Knowledge quiz

Consider the following real-world scenario and complete the micro mock exam based on this chapter.

Case study – a health solutions company

A health solutions company has been asked to develop a system for a large corporate client that monitors the time employees spend on projects and other tasks. The client wants this timesheet system to capture timesheets every week and employees must be able to update their personal details to keep them up to date. Line managers must be able to approve or reject a timesheet, as well as view and print their employees' timesheets. They should also be able to run and print management reports. As part of the time capture functionality, the system must validate whether...