IREB-CPRE Dumps
IREB-CPRE Braindumps IREB-CPRE Real Questions IREB-CPRE Practice Test IREB-CPRE Actual Questions
killexams.com
IREB Certified Professional for Requirements Engineering (CPRE)
https://killexams.com/pass4sure/exam-detail/IREB-CPRE
When creating a system prototype, which of the following is a significant advantage?
It guarantees successful implementation of the final system
It reduces the overall project cost
It eliminates the need for further requirement gathering
It provides a concrete basis for discussing requirements
It ensures stakeholder approval before implementation Answer: D
Explanation: Prototypes serve as a tangible reference for stakeholders to visualize and discuss requirements, clarifying their needs and expectations.
In the context of requirements engineering, which two statements regarding non-functional requirements are accurate? (Choose two)
Non-functional requirements are optional and can be ignored.
They define system attributes such as performance, usability, and security.
Non-functional requirements are always more difficult to measure than
functional ones.
They should be specified in the same way as functional requirements. Answer: B, C
Explanation: Non-functional requirements describe essential system attributes and are often more challenging to quantify than functional requirements.
Which of the following is the most effective way to ensure that a requirement is testable?
Use vague terms to allow flexibility
Define it in natural language without metrics
Specify acceptance criteria and measurable outcomes
Keep it at a high level to avoid complexity
Rely on developer intuition for implementation Answer: C
Explanation: Specifying acceptance criteria and measurable outcomes ensures that the requirement can be objectively validated during testing.
What is the primary purpose of a requirements traceability matrix (RTM)?
To document design decisions
To track changes in project scope
To manage project timelines
To ensure each requirement is addressed in the final product
To allocate resources Answer: D
Explanation: An RTM ensures that each requirement is accounted for throughout the project lifecycle, linking requirements to their corresponding design, implementation, and testing artifacts.
In a requirements gathering session, a stakeholder suggests a feature that is technically complex and outside the current scope, What is the best approach to handle this suggestion?
Document the suggestion for future consideration
Reject the suggestion outright
Immediately escalate it to upper management
Analyze the technical complexity and present findings
Ask the stakeholder to provide a detailed proposal Answer: A
Explanation: Documenting the suggestion allows for future evaluation without dismissing potentially valuable ideas, fostering an inclusive atmosphere for
stakeholders.
When should requirements traceability be established in a project?
After the testing phase
Only if there is time available
At the end of the project
During the requirements elicitation phase Answer: D
Explanation: Requirements traceability should be established during the requirements elicitation phase to ensure all requirements can be tracked throughout the project lifecycle.
Which two benefits does prototyping provide in the requirements engineering process?
It eliminates the need for requirements documentation.
It helps validate requirements with users and stakeholders.
It reduces development time significantly.
It facilitates early detection of misunderstandings.
Answer: B, D
Explanation: Prototyping validates requirements and facilitates early detection of misunderstandings, improving stakeholder engagement and satisfaction.
You are tasked with documenting requirements for a new system. Which of the following practices should be avoided to maintain clarity?
Using clear and concise language.
Writing ambiguous statements to cover multiple interpretations.
Including diagrams and visual aids.
Ensuring that all stakeholders review the requirements document. Answer: B
Explanation: Writing ambiguous statements can lead to misinterpretation and confusion, undermining the clarity and effectiveness of the requirements documentation.
Which of the following statements about use cases is correct?
They are only useful for functional requirements.
They provide a detailed technical specification.
They focus on user interactions with the system.
They replace the need for other requirement documents.
They are primarily used for non-functional requirements. Answer: C
Explanation: Use cases focus on user interactions with the system, detailing the steps taken by users to achieve specific goals, making them valuable for functional requirements.
In the context of requirements documentation, which two characteristics indicate a high-quality requirement?
It is vague and open to interpretation.
It is clear, concise, and unambiguous.
It is documented in lengthy and complex language.
It is testable and verifiable. Answer: B, D
Explanation: High-quality requirements are clear, concise, unambiguous, and testable, ensuring they can be understood and verified effectively.
A project manager asks you to prioritize requirements based on return on investment (ROI). Which method should you use?
MoSCoW method
Cost-benefit analysis
Kano model
User story mapping Answer: B
Explanation: A cost-benefit analysis is appropriate for prioritizing requirements based on ROI, as it evaluates the potential financial returns against implementation costs.
You are analyzing the requirements for a new software application. A stakeholder mentions that a feature should be "user-friendly." Which of the following approaches is best to clarify and refine this ambiguous requirement?
Create a requirements traceability matrix
Conduct a SWOT analysis
Use a prototyping approach
Develop a state machine diagram
Implement a waterfall model
Explanation: Prototyping allows stakeholders to visualize and interact with the software early in the development process, helping to clarify ambiguous terms like "user-friendly."
What is the primary benefit of using a user acceptance test (UAT) in the requirements engineering process?
To ensure that requirements are technically feasible.
To validate that the system meets the needs of the users and stakeholders.
To document all requirements in detail.
To prioritize requirements based on stakeholder input. Answer: B
Explanation: UAT is conducted to ensure the final product fulfills the requirements and expectations of users, validating that it is ready for deployment.
Which two types of requirements are typically included in a Software Requirements Specification (SRS)?
Technical specifications
Non-functional requirements
Marketing strategies Answer: A, C
Explanation: An SRS typically includes business requirements and non- functional requirements, focusing on what the software must achieve.
Which of the following best describes the purpose of a feasibility study in the context of requirements engineering?
To identify all possible requirements for the system.
To assess the viability of the project in terms of technical, financial, and operational aspects.
To finalize the project timeline and budget.
To eliminate all risks associated with the project. Answer: B
Explanation: A feasibility study assesses whether a project is viable by examining its technical, financial, and operational aspects, guiding decision- making.
What role does a requirements traceability matrix play in the requirements engineering process?
It simplifies the coding process
It helps in tracking requirements throughout the project lifecycle
It eliminates the need for stakeholder input
It guarantees that all requirements will be implemented Answer: B
Explanation: A requirements traceability matrix is a tool that helps track requirements throughout the project lifecycle, ensuring that all requirements are addressed and tested.
Which two characteristics are most critical for writing effective and clear requirement statements? (Choose two)
Ambiguity
Testability
Lengthy descriptions
Specificity
Technical jargon Answer: B, D
testing, while specificity provides clear, detailed information on what is expected, reducing ambiguity and misunderstandings during development.
Which of the following is NOT a characteristic of a well-defined requirement?
Unambiguous
Vague
Comprehensive
Testable
Feasible Answer: B
Explanation: A well-defined requirement must be unambiguous, meaning it should clearly convey its intention without room for misinterpretation.
A requirement states, "The system should be user-friendly." What is the primary issue with this requirement?
It is a business requirement
It is not aligned with stakeholder needs
It is too technical
It is subjective and lacks measurable criteria
Answer: D
Explanation: The term "user-friendly" is subjective and can vary widely in interpretation. Good requirements should be specific and measurable to ensure clarity and testability.
How should requirements be prioritized to ensure alignment with stakeholder value?
Use a value-based approach to prioritize requirements according to their impact on business objectives.
Prioritize based on technical complexity.
All requirements should be treated equally, regardless of value.
Prioritize based on the preferences of the most vocal stakeholders. Answer: A
Explanation: A value-based prioritization approach ensures that requirements are aligned with strategic business goals, maximizing the value delivered by the system.
What approach should be taken to manage conflicting requirements from different stakeholders?
Ignore conflicting requirements as they will resolve themselves.
Accept the requirements from the most senior stakeholder only.
Facilitate discussions among stakeholders to negotiate and prioritize conflicting requirements.
Document all conflicting requirements without addressing them. Answer: C
Explanation: Facilitating discussions allows stakeholders to negotiate and find common ground, leading to more effective prioritization and resolution of conflicts.
In the context of requirements verification, which two statements are true? (Choose two)
Verification checks if the product meets user needs and requirements.
It is an ongoing process conducted throughout the development lifecycle.
Verification is solely concerned with the correctness of requirements documentation.
Reviews and inspections are common techniques for verification. Answer: B, D
Explanation: Verification is an ongoing process ensuring that requirements are met, typically using reviews and inspections to confirm correctness.
Which practice is essential for effective requirements communication among stakeholders?
Using complex technical language
Relying solely on written documentation
Engaging stakeholders through workshops and discussions
Limiting communication to formal meetings Answer: C
Explanation: Engaging stakeholders through workshops and discussions fosters effective communication, ensuring that all parties understand and agree on the requirements.
A project manager wants to understand the feasibility of a proposed feature that requires significant resources. Which technique is best suited for a preliminary feasibility analysis?
Cost-benefit analysis
Use case analysis
Requirements prioritization
Stakeholder analysis
Risk assessment Answer: A
Explanation: A cost-benefit analysis helps to evaluate whether the benefits of implementing the feature outweigh the costs, providing a clear indication of its feasibility.
Which two methods can help in achieving a shared understanding of requirements among stakeholders? (Choose two)
Creating visual models to represent requirements.
Relying solely on written documentation.
Conducting regular review sessions to gather feedback.
Limiting stakeholder involvement to only key individuals. Answer: A, C
Explanation: Visual models enhance comprehension, and regular reviews facilitate feedback, promoting a shared understanding among all stakeholders.