A business analyst (BA) has elicited the following requirement; "The solution must ensure the portal response times are under 2 seconds." What requirement classification schema does this requirement belong to?
The requirement classification schema that this requirement belongs to is nonfunctional requirements. Nonfunctional requirements are statements of conditions or restrictions on a solution or its components that affect its quality, performance, usability, reliability, security, etc. Nonfunctional requirements specify how well a solution should perform or behave.
The other options are incorrect because:
Option B is incorrect because stakeholder requirements are not a requirement classification schema, but a requirement type. Stakeholder requirements are statements of needs, expectations, preferences, or problems of stakeholders or an organization.
Option C is incorrect because transitional requirements are not a requirement classification schema, but a requirement type. Transitional requirements are statements of capabilities or conditions that enable a solution to transition from its current state to its desired future state.
Option D is incorrect because functional requirements are not a requirement classification schema, but a requirement type. Functional requirements are statements of features, functions, or behaviors of a solution or its components that enable it to provide value to stakeholders.
BABOK Guide v3, section 6.1: Specify and Model Requirements
CCBA Exam Questions, question 35
You are the business analyst for your organization and you're working with the project manager to complete some business analysis activities. The project manager has the authority to approve the requirements based on the short iterations of business analysis activities.
What approach of business analysis are you using in this scenario?
According to the BABOK Guide, a change-driven approach of business analysis is one that ''emphasizes rapid delivery of business value in short iterations'' (p. 31). This approach allows for frequent feedback and validation of the requirements and the solution, as well as adaptation to changing business needs and priorities. The project manager's authority to approve the requirements based on the short iterations of business analysis activities indicates that this approach is being used in this scenario. The other options are not correct because:
Progressive elaboration is a technique of gradually refining the level of detail and accuracy of the requirements as more information becomes available, not an approach of business analysis (p. 36).
Plan-driven approach is one that ''emphasizes upfront definition of the requirements and the plan to deliver the solution'' (p. 31). This approach requires more formal approval and change control processes than the change-driven approach.
Iterative approach is a generic term that can apply to both plan-driven and change-driven approaches, as long as they involve repeating cycles of analysis and delivery (p. 31). It is not a specific approach of business analysis by itself.Reference:
BABOK Guide, p. 31, 36
Business Analysis: Definition, Process, Techniques and Tips, section ''What are the different types of business analysis techniques?''
The Chief Information Officer (CIO) of a large financial services firm with many technology applications was formally reviewing all ongoing projects and noticed that the requirements were complex and difficult to follow. The CIO asks the business analyst (6A) what would improve the stakeholder's ability to understand the requirements. Which of the following will improve the requirements quality?
The BA should improve the stakeholder's ability to understand the requirements by following the IEEE/ISO 29148 requirements standards. This is because IEEE/ISO 29148 is an international standard that provides guidelines for developing good quality requirements. The standard covers aspects such as requirements processes, elicitation, analysis, documentation, validation, and management. Following the standard can help to ensure that the requirements are clear, complete, consistent, traceable,verifiable, and modifiable. The other options are not as effective or comprehensive as following the standard.Reference:
IEEE/ISO 29148: Systems and software engineering --- Life cycle processes --- Requirements engineering
CCBA Practice Test, question 101
Which basis for prioritization allows the project team to work initially with lower-risk requirements first?
Positive risk ranking is a basis for prioritization that allows the project team to work initially with lower-risk requirements first. Positive risk ranking is a technique that assigns a score to each requirement based on the level of risk associated with it, where a higher score indicates a lower risk and a lower score indicates a higher risk. The requirements are then prioritized in descending order of their scores, so that the project team can focus on the requirements that have the least uncertainty, complexity, or volatility first, and defer the requirements that have the most uncertainty, complexity, or volatility later.Positive risk ranking helps to reduce the likelihood and impact of potential problems, issues, or changes that may affect the requirements or the solution12
Option A is incorrect because quantitative ranking is not a basis for prioritization that allows the project team to work initially with lower-risk requirements first, but a technique that uses numerical values to compare and rank the requirements based on multiple criteria, such as value, cost, risk, urgency, dependency, etc.Quantitative ranking does not necessarily prioritize the lower-risk requirements first, but the requirements that have the highest overall score based on the weighted criteria34
Option C is incorrect because relationship to other requirements is not a basis for prioritization that allows the project team to work initially with lower-risk requirements first, but a factor that considers the dependencies and interdependencies among the requirements, such as prerequisite, co-requisite, or conflicting requirements. Relationship to other requirements does not necessarily prioritize the lower-risk requirements first, but the requirements that have the most influence or impact on the other requirements.
Option D is incorrect because implementation difficulty is not a basis for prioritization that allows the project team to work initially with lower-risk requirements first, but a factor that considers the effort, time, resources, and skills required to implement the requirements. Implementation difficulty does not necessarily prioritize the lower-risk requirements first, but the requirements that have the least difficulty or complexity to implement.
Business Analysis Techniques - ECBA, CCBA, CBAP Endorsed, Section 8.5: Prioritization, p. 101-102.
Certification of Capability in Business Analysis (CCBA) - Simplilearn, Module 7: Requirements Analysis and Design Definition, Lesson 7.5: Define Transition Requirements, p. 6-7.
Business Analysis Techniques - ECBA, CCBA, CBAP Endorsed, Section 8.5: Prioritization, p. 102-103.
Certification of Capability in Business Analysis (CCBA) - Simplilearn, Module 7: Requirements Analysis and Design Definition, Lesson 7.5: Define Transition Requirements, p. 8-9.
[Business Analysis Techniques - ECBA, CCBA, CBAP Endorsed], Section 8.5: Prioritization, p. 100-101.
[Certification of Capability in Business Analysis (CCBA) - Simplilearn], Module 7: Requirements Analysis and Design Definition, Lesson 7.5: Define Transition Requirements, p. 10-11.
[Business Analysis Techniques - ECBA, CCBA, CBAP Endorsed], Section 8.5: Prioritization, p. 100.
[Certification of Capability in Business Analysis (CCBA) - Simplilearn], Module 7: Requirements Analysis and Design Definition, Lesson 7.5: Define Transition Requirements, p. 12-13.
You are the business analyst for your organization and you're performing the solution assessment process. When you assess a solution, what are you actually looking for?
When you assess a solution, what you are actually looking for isto determine the value of the proposed solution to the stakeholder requirements.This is the main purpose of the solution assessment and validation knowledge area, which involves measuring and evaluating the performance and benefits of the solution, and ensuring that it meets the stakeholder needs and expectations12.Value is defined as the worth, importance, or usefulness of something to a stakeholder within a context3.To determine the value of the proposed solution, you need to identify and analyze the value proposition, the value drivers, the value measures, and the value delivery4.The other options are not what you are actually looking for when you assess a solution, but rather aspects that may contribute to the value of the solution, such as the quality (B), which is the degree to which a solution meets the requirements and delivers the expected benefits5, the cost , which is the amount of resources expended or consumed to implement and operate the solution, or the accuracy (D), which is the extent to which a solution represents the true or exact state of the problem or the need.Reference:Business Analysis Expert Certification, CCBA | IIBA,Certification of Capability in Business Analysis (CCBA),Business Analysis Certification Competencies, CCBA | IIBA,The Ultimate Guide to Business Capability Analysis,CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, [Certification of Capability in Business Analysis (CCBA) - Simplilearn], [A GUIDE TO THE BUSINESS ANALYSIS BODY OF KNOWLEDGE]
Gladys
5 days agoAdria
12 days agoVirgie
20 days agoHaydee
27 days agoJolene
1 month agoErnest
1 month agoPeggie
2 months agoMichel
2 months agoDorothy
2 months agoPamella
2 months agoLauna
3 months agoIrene
3 months agoJaclyn
3 months agoGladys
3 months agoLatricia
4 months agoElsa
4 months agoMaryln
4 months agoNana
4 months agoKaycee
5 months agoCristy
5 months agoKarl
5 months agoRodolfo
5 months agoIsadora
6 months agoLashanda
6 months agoFelicidad
6 months agoMadalyn
6 months agoOwen
7 months agoLamar
7 months agoJill
9 months agoFlo
9 months agoLenny
11 months agoKenneth
1 year agoParis
1 year agoJerry
1 year agoJanessa
1 year agoEmiko
1 year agoGeraldine
1 year agoKrissy
1 year agoTamra
1 year agoMacy
1 year agoTheron
1 year agoPenney
1 year agoVeronika
1 year agoAlecia
1 year agoMelvin
1 year agoDiego
1 year agoTrina
1 year agoYaeko
1 year agoLetha
1 year agoJanine
1 year agoCarlee
1 year agoLorean
1 year agoMertie
1 year agoJame
2 years agoVilma
2 years agoFranchesca
2 years agoMary
2 years agoAja
2 years agoFernanda
2 years agoBrande
2 years agoBenton
2 years agoAudry
2 years agoKimberely
2 years agoRodrigo
2 years agoTawanna
2 years ago