Functional decomposition is the analysis of complex systems by breaking them down into smaller simpler elements.  It inv olves breaking down processes, systems, functional areas, or deliverables into simpler components, so that each part can be analyzed separately 1 2 . By breaking down larger components into smaller parts, it allows the organization to measure and track each work effort involved in implementing the solution.  It also helps in the assessment of the effectiveness of each sub-component as it relates to other larger or smaller components 3 .  Functional decomposition is a tec hnique used in business analysis to facilitate the understanding and management of large and complex processes 2 .  It is also used in systems engineering, software architecture, database theory, machine learning, and a variety of other fields 2 .  References :  1 : Functional decomposition in business analysis – The Functional BA  2 : Functional Decomposition: Defini tion, Diagrams, and Applications  3 : 10.22 Functional Decomposition | IIBA®

The business analysis process that ensures that requirements specifications and models meet the necessary standard of quality to allow them to be used effectively to guide further work is verify requirements.  According to the BABOK® Guide 1 , this process involves checking that the requirements are well-defined, clear, consist ent, complete, correct, fea sible, modifiable, testable, and traceable. It also involves resolving any defects or issues that may affect the quality of the requirements. The purpose of this process is to confirm that the requirements specifications and mode ls accurately reflect the stakeholder needs and expectations, and that they are ready for validation and approval.

The other options are not correct, but rather:

A. Identify constraints and assumptions is a task within the assess capability gaps process, which involves comparing the current and future states of the organization to identify the gaps that must be addressed by a solution.

B. Validate requirements is a process that ensures that the requirements support the delivery of value to the stakeholders and achieve the goals and objectives of the project or initiative. It involves evaluating the alignment, acceptability, and approval of the requirements by the stakeholders.

D. Specify and model requirements is a process that involves defining and representing the requirements in various formats, such as textual, graphical, or tabular. It helps to communicate, analyze, and refine the requirements more effectively.

References :

CBAP® Handbook , page 6, section 4. Review the Exam Blueprint, under Requirements Analysis and Design Definition, task 5.3: Verify Requirements

BABOK® Guide , page 33, section 4.2.3: Verify Requirements

How Do Business Analysts Verify Requirements? (BABOK 6.5)

What Is Requirements Analysis? Process and Techniques

Functional decomposition is a technique that breaks down a complex solution scope into smaller and manageable work products or deliverables. It helps to understand the scope of work that needs to be completed, an d to organize and prioritize the requirements. Functional decomposition can be represented in various ways, such as hierarchical diagrams, tables, or lists. It can also be used to create a work breakdown structure (WBS) for the project management. Function al decomposition is useful for projects that have a large or unclear solution scope, as it helps to reduce ambiguity and complexity, and to identify dependencies and gaps.  References :

Using Scope Models to Manage Solution Scope

Solution Scope vs. Project Scope

Solution Scope – An Insight

Overlooking a key set of stakeholders can have serious consequences for the project, as they may have different needs, expectations, and perspectives than the existing stake holders. Thei r requirements may conflict with or invalidate the ones that have been already elicited and analyzed, leading to rework, delays, and increased costs. Alternatively, they may introduce new requirements that require changes to the project scope, schedule, bu dget, or quality. Therefore, it is important to identify all relevant stakeholders as early as possible in the business analysis process and to engage them throughout the project lifecycle.  References :

CBAP Handbook , page 12, section 2.0 Nine-Steps to Certification, step 3. Enter Your Eligibility Details into the BA Development Log

[BABOK Guide], page 30, section 2.2 Conduct Stakeholder Analysis, task description and output

CBAP/CCBA Study Guide , page 55, section 2.2.3 Stakeholder Analysis, stakeholder identification and analysis techniques

Prioritizing requirements by the likelihood of success is a technique that can help build confidence and trust among the project stakeholders, especially if the project is complex, risky, or has a long duration. By delivering s ome of the requirements that have a high chance of success early in the project, the business analyst can demonstrate the value of the project and the effectiveness of the business analysis process. This can also help reduce resistance to change and increa se user satisfaction and adoption. Some of the other factors that can be used to prioritize requirements are business value, urgency, dependency, risk, cost, and effort.  References :

Certified Business Analysis Professional (CBAP) Handbook , page 6, section 4. Review the Exam Blueprint.

BABOK Guide v3 , page 34, section 4.2.3. Prioritize Requ irements.

 Scope creep is the change or expansion in the project scope that occurs without proper assessment and approval. It can result in cost overruns, delays, and client sat isfaction issues. Scope creep can happen due to unclear or changing requirements, lack of stakeholder involvement, poor communication, or inadequate change control. To prevent scope creep, business analysts should define the project scope clearly, manage s takeholder expectations, document and prioritize requirements, and follow a change management process.  References :

Scope Creep: Definition, Examples & How To Prevent It - Forbes

What is Scope Creep and 7 Ways to Avoid it [2023] • Asana

What is the meaning of Scope Creep in Project Management?

 The management horizon is the time period over which the costs and benefits of a proposed solution are evaluated. It is also the point in time when the ne t present value of the solution becomes positive, meaning that the solution has recovered its initial investment and started to generate a profit. The management horizon helps to determine the feasibility and viability of a solution, as well as its alignme nt with the strategic goals of the organization.  References :

CBAP® Handbook , page 15, section 4.1.2.3

BABOK® Guide , page 32, section 3.2.3

How to Write a Business Case (Template Included) , under Step 3: Calculate the Financials

Solution components are the parts of the physical architecture that implement the solution requirements. They include business processes , business policies, business rules, software applications, hardware devices, data structures, and other elements that constitute the solution. Solution components are identified and defined during the design process, and they are allocated to the requirem ents during the allocate requirements process.  The purpose of allocating requirements to solution components is to ensure that each requirement is fulfilled by on e or more solution components, and that each solution component contributes to one or more requirements 1 2 3 .

Assessment of proposed solution is not a solution component, but a technique that evaluates the feasibility, desirability, and suitability of a so lution option. Assessment of proposed solution is used during the enterprise analysis process, which involves defining the business need, assessing the capability gaps, determining the solution approach, defining the solution scope, and defining the busine ss case.  The purpose of assessing the proposed solution is to compare the expected benefits and costs of the solution option, and to identify the risks, assumptions, and de pendencies that may affect the solution delivery 4 5 6 .  References :  1 : BABOK® Guide v3, section 7.2 Allocate Requirements, page 254  2 : CBAP / CCBA Certified Business Analysis Study Guide, chapter 7, page 243  3 : Allocation and Traceability 7   4 : BABOK® Guide v3, section 3.4.5.1 Assessment of Proposed Solution, page 75  5 : CBAP / CCBA Certified Business Analysis Study Guide, chapter 4, page 122  6 : Business Analysis Techniques: Assessing the Proposed Solution, page 27

Before making a presentation about the requirements for a large software development project, Gary should determine an appropriate format for the presentation. This means he should consider the following factors:

The audience: Who are the stakeholders that will attend the presentation? What are their roles, interests, and expectations? How familiar are they with the project and the requirements? How much detail do they need to understand the requirements?

The purpose: What is the goal of the presentation? Is it to inform, persuade, or seek feedback from the stakeholders? What are the key messages and takeaways that Gary wants to convey?

The time: How much time does Gary have to present the requirements? How can he allocate the time effectively to cover the most important and relevant aspects of the requirements?

The tools: What tools and resources does Gary have to create and deliver the presentation? Does he have access to a projector, a laptop, a microphone, or a whiteboard? What software or applications does he need to use to create the presentation slides or documents?

The style: How can Gary make the presentation engaging, clear, and professional? What visual aids, diagrams, charts, or examples can he use to illustrate the requirements? How can he use colors, fonts, images, and animations to enhance the presentation? How can he structure the presentation to have a logical flow and a strong introduction and conclusion?

By determining an appropriate format for the presentation, Gary can ensure that he communicates the requirements effectively and efficiently to the stakeholders, and that he addresses their needs and concerns.

References :

How to Make Interesting Presentations for Software Projects , paragraphs 1-3

How To Wri te The Software Development Project Brief , steps 1-7

Complete Guide to Software Development Requirements , paragraphs 1-2

A plan-driven approach to business analysis is a methodology that focuses on minimizing up-front uncertainty and ensuring that the solution is fully define d before implementation begins in order to maximize control and minimize risk. This approach tends to be preferred in situations where requirements are stable and clear, and where changes are costly and disruptive. Therefore, a plan-driven approach has the most business analysis work at the beginning of the project or during the start of a project phase, as it involves detailed planning, analysis, and documentation of the requirements and the solution.  A plan-driven approach also requires formal approval and sign-off of the requirements and the solution before moving to the next phase 1 2 3 .  References :  1 : How to Choose the Right Business Analysis Approach 1   2 : Plan driven projects versus change driven 2   3 : Business Analysis Methodology 3