6: RA - Requirement Analysis Flashcards
What types of requirement are defined during Requirement Analysis KA?
Stakeholder Requirement
Solution Requirement
RA covers the definition of stakeholder requirements, which describe what a solution must be capable of doing to meet the needs of one or more stakeholder groups,
and solution requirements, which describe the behavior of solution components in enough detail to allow them to be constructed.
The tasks in this knowledge area apply to both stakeholder and solution requirements.
When the model of current stated is developed?
Requirements analysis may used to develop models of the current state of an organization.
What the acronym for Requirement Analysis KA?
PrO and SAVVy analysis P = Priorities Requirement O = Organise Requirements S = Specify and Model Requirements A = Define Assumption and Constraints V = Verify Requirement V = Validate Requirement
For Prioritization of Requirement, the importance of Requirement is based on what factors?
The importance of requirements may be based on their relative value, risk, difficulty of implementation, or on other criteria.
What input is optional during priorities requirement task of Requirement Analysis KA?
Business Need
Business Need: Serves as an alternative to the business case if no business case has been defined.
At what stage/state requirement can be prioritized?
Requirement can be prioritized at any point in lifecycle. Only the requirements have been stated by stakeholders; may not have been fully analyzed or in their final form.
Why Requirement Mng plan is used as input for Priorities Requirements?
Requirements Management Plan defines the process that will be used to prioritize requirements.
What are the different criteria for Requirement Prioritization?
Loan US DVR3
L = Likelihood of Success U = Urgency S = Stakeholder Agreement D = Difficulty of Implementation V = Value (Business) R = Risk (Business or Technical) R = Regulatory or Policy Compliance R = Relationship to Other Requirements
What are the element of Priorities Requirement task under Requirement Analysis?
- Basis for Prioritization
2. Challenges
What are the challenges may occur during requirements prioritization session?
- Non-negotiable Demand
2. Unrealistic Tradeoffs
What “Non-negotiable Demand” refers to during Requirement Prioritization?
Non-negotiable Demands:
- Stakeholders attempt to avoid difficult choices,
- Fail to recognize the necessity for making tradeoffs, or 3. Desire to rank all requirements as high priority.
What “Unrealistic Tradeoffs” refers to during Requirement Prioritization?
Unrealistic Tradeoffs: The solution development team may try to influence the result of the prioritization process by overestimating the difficulty or complexity of implementing certain requirements.
What is Timeboxing or Budgeting technique and When it is used?
Timeboxing or Budgeting technique is used to Priorities Requirements
Timeboxing or budgeting prioritizes requirements for investigation and implementation based on allocation of a fixed resource.
What are the Pre-requisite for using Timeboxing or Budgeting technique?
It is used when the solution approach has been determined.
Which Stakeholder is much intrested in Requirement Prioritization Results?
Project Manager
Project Manager: The project manager is responsible for the implementation of the solution and will use the priority of requirements as an input into the project plan.
What is the purpose of Organize Requirements under Requirement Analysis KA?
To create a set of views of the requirements that are comprehensive, complete, consistent, and understood from all stakeholder perspectives.
What are the key objectives of Organize Requirements under Requirement Analysis KA?
- Understand which models are appropriate for the business domain and solution scope.
- Identify model interrelationships and dependencies.
Requirements alone are not complex; it is the relationships and inter dependencies among requirements that adds the element of complexity.
What state of requirement is used as input for Organise Requirement under Requirement Analysis KA?
Requirement [Stated]
Stated requirements are the expressed desires of stakeholders, which must be analyzed to ensure that they reflect a genuine need.
What is the Key in Organizing Requirements under Requirement Analysis KA?
It will usually be beneficial to create multiple models of and perspectives on the requirements in order to ensure understanding, although any given requirement should only appear in one model in order to avoid confusion or contradictions
What does it mean by Model in Organizing Requirements under Requirement Analysis KA?
Models abstract and simplify reality. No model can be a complete description of reality; the objective of developing a model is to simplify reality in a way that is useful.
What are the elements of Organise Requirement?
- Levels of Abstraction
2. Model Selection
What are general modeling concepts that are relevant to business analysis?
sUPER Car U = User Classes, Profiles, or Roles P = Processes E = Events R = Rules C = Concepts and Relationships
What tasks uses Requirement [Prioritised]?
Assess Proposed Solution (7.1)
Allocate Requirements (7.2)
Validate Solution (7.5)
Requirement Mng and Communication
What is the output of Organize Requirement and What does it consist of ?
Requirements Structure is the output of Organize Requirement task.
Requirements Structure is an organized structure for the requirements and a documented set of relationships between them.
What is the difference between Requirements Structure and Requirement Tractability?
Tracing links related requirements;
Structure specify where a specific requirement should be found. b/c Each model or set of requirements within the structure should have a clear implicit scope.
What the purpose of Specify and Model Requirements under Requirement Analysis KA?
To analyze expressed stakeholder desires and/or the current state of the organization using a combination of textual statements, matrices, diagrams and formal models.
What the Objectives of Specify and Model Requirements ?
It can serve various objectives, specifics of this task are highly dependent on the techniques used for specifying and modeling requirements.
What state of Requirement is used as input for Specify and Model Requirements under Requirement Analysis KA?
Requirement [Stated]
Specification or modeling of requirements is performed to structure and improve our understanding of needs as expressed by stakeholders.
What are the element of Specify and Model Requirements?
- Text
- Matrix Documentation
- Models
- Capture Requirement Attributes
- Improvement Opportunities
What are often used candidates of Matrix Documentation during Specify and Model Requirements?
Requirements attributes and data dictionaries are often expressed in tabular form - Matrices
What the use of Model?
Models may be used
- to document requirements in their final form,
- As a tool while performing elicitation activities.
What the Opportunities of Improvement during Specify and Model Requirements?
I2 EARs
Lending your two ears (as expression of listening)
I = Improve access to information I = Increase Consistency of Behavior E = Eliminate Redundancy A = Automate or Simplify the work R = Reduce Complexity of Interface
Which stakeholder is the main one during Specify and Model Requirements?
Business Analyst is the main stakeholder and may chooses to perform this task alone. Any other stakeholders can be included.
What is the output of Specify and Model Requirements?
Stakeholder or Solution Requirements
OR
Requirement [Analysed]
What is assumptions?
Assumptions are factors that are believed to be true, but have not been confirmed.
What is constraints?
Constraints are defined as restrictions or limitations on possible solutions.
What is Solution Constraints?
Solution constraints describe aspects of the current state, or planned future state that may not be changed.
Which Stakeholder is responsible to document Assumption and Constraints?
The business analyst is responsible for documenting Assumption and any restrictions or limitations to the solution design, construction, testing, validation and deployment.
What are the attributes of Assumption and Constraints?
Assumptions and constraints are attributes (e.g.,
- Date identified,
- Owner,
- Impact,
- Associated risk, and
- Other explanatory information).
Which Task have only one input?
Define Assumption and Constraints has only one input as “Stakeholder Concerns”
Steak
What other Task uses Stakeholder or Solution Requirements OR Requirement [Analysed] ? Output from
Specify and Model Requirements.
Priorities Requirements (6.1) Verify Requirements (6.5) Requirements Management and Communication
What other Task uses ‘Assumption and Constraints” - output from Define Assumption and Constraints?
Define Scope (5.4)
Define Business Case (5.5)
Assess Proposed Solution (7.1)
Requirements Management and Communication
What is the purpose of Verify Requirements?
Requirements verification ensures that requirements specifications and models meet the necessary standard of quality.
For what Requirements verification is deemed as a final check for requirements?
To determine that the requirements are:
- ready for formal review and validation by the customers
and users, and
- provide all the information needed for further work
based on the requirements to be performed.
What should be state of Requirement as input for Verify Requirement Task?
Requirement [Any Except Stated]
What type (not the state) of requirement can be verified?
Any requirement may be verified including business, stakeholder, solution, and transition requirements.
What are the elements of Verify Requirements?
- Characteristics of Requirements Quality
2. Verification activities
What are the Characteristics of Requirement Quality?
TUMs 4 Cold & Flue
When Requirement are not of desired Quality and Sick them it need TUMs for Cold and Flue
T = Testable U = Unambiguous M = Modifiable C = Correct C = Cohesive C = Consistent C = Complete F = Feasible
What is special technique used for Verify Requirement?
Checklist
Which stakeholder has the primary responsibility for Verifying Requirement?
The business analyst, in conjunction with the domain and technical subject matter experts, has the primary responsibility for determining that this task has been completed.
In which Task of “Requirement Analysis” KA All Stakeholder are involved?
Verify Requirement
Validate Requirement
In which Task of “Requirement Analysis” KA Any Stakeholder are involved?
Specify and Model Requirements
Business Analyst is the main stakeholder and may chooses to perform this task alone. Any other stakeholders can be included.
What other Task uses Requirements [Verified] - Output from Verify Requirement task?
Validate Requirement [6.6]
Requirements Mng and Communication
What is the purpose of Validate Requirements?
To ensure that
- all requirements support the delivery of value to the business,
- fulfill its goals and objectives, and
- meet a stakeholder need.
When Validating Requirement task can begin and stops?
Validation activities may begin before requirements are completely verified.
Requirements validation is an ongoing process to ensure that stakeholder, solution, and transition requirements align to the business requirements.
What types and in what state requirement are used as input for Validate Requirements?
Stakeholder, Solution, or Transition Requirements in [Verified] state
What are the elements of Validate Requirements?
- Identify Assumptions
- Define Measurable Evaluation Criteria
- Determine Business Value
- Determine Dependencies for Benefits Realization
- Evaluate Alignment with Business Case and Opportunity Cost
What are Validated Requirement?
Validated requirements are those that can be demonstrated to deliver value to stakeholders and are aligned with the business goals and objectives.
What other tasks use the Requirement [Validated]?
- Validate Solution (7.5)
2. Requirements Management and Communication
When can a business requirement be prioritized?
Select one:
a. After conducting the verify requirements task.
b. At any point in its life cycle.
c. While conducting the prioritize requirements task. Incorrect
d. While conducting the specify and model requirements task.
The correct answer is:
b. At any point in its life cycle.
Page Number(s) 100
Correct Answer Feedback
BABOK 6.1.3. Any requirement may be prioritized at any point in its lifecycle.
Who are primarily responsible to verify requirement (QA things)?
The business analyst, in conjunction with the domain and technical subject matter experts, has the primary responsibility for determining that this task has been completed. Other stakeholders may discover problematic requirements during requirements communication.
What is the definition of the term “Checklist” ?
Select one:
a. A quality control technique. This may include a standard set of quality elements that reviewers use for requirements verification and requirements validation or be specifically developed to capture issues of concern to the project.
b. A quality control technique; however this doesn’t include a standard set of quality elements that reviewers use for requirements verification and requirements validation or be specifically developed to capture issues of concern to the project.
c. A quality control check. This may include a standard set of quality elements that reviewers use for capturing issues of concern to the project. Incorrect
d. A quality control technique.
The correct answer is:
a. A quality control technique. This may include a standard set of quality elements that reviewers use for requirements verification and requirements validation or be specifically developed to capture issues of concern to the project.
Which of the following statements does NOT describe assumptions or constraints?
a. Assumptions may affect all aspects of the project and pose a certain degree of risk.
b. Assumptions and constraints are generally documented with associated attributes.
d. Constraints are defined as restrictions or limitations on possible solutions.
c. Assumptions and constraints are generally documented to be generic, like business rules.
The BABOK mentions that assumptions and constraints are documented along with associated attributes. BABOK 6.4.2.
