最新的ISQI IREB Certified Professional for Requirements Engineering. Foundation Level - CPRE-FL_Syll_3.0免費考試真題

A. Backward traceability

B. Integrated traceability

C. Traceability between requirements

D. Forward traceability

A. The requirement has incomplete conditions.

B. Nominalizations have been used.

C. Universal quantifiers have been used.

D. The requirement is written in the passive voice.

A. all stakeholders interpret it in the same way, leaving no room for multiple interpretations.

B. it falls within the relevant system scope, ensuring it contributes to fulfilling at least one stakeholder goal or need.

C. it is self-contained, providing all the necessary information for its understanding, implementation, and verification.

D. it reflects the genuine and agreed-upon needs of the stakeholders.

A. The more complex the system to be implemented is, the more formal and rigorous the RE process should be.

B. When there is a high degree of trust between the customer and the supplier, more formal specifications should be used.

C. The stronger the shared understanding, the more complex and rigorous the RE process should be.

D. The less experienced the Requirements Engineers are, the less sophisticated the RE process should be.

E. When schedules and budgets are constrained, a lightweight RE process is often adopted.

A. There is no selective view represented in the figure.

B. View A

C. View B

D. View C

A. Prescriptive & Customer-oriented

B. Explorative & Customer-oriented

C. Explorative & Market-oriented

D. Prescriptive & Market-oriented

A. Constraints limit the solution space to the point that quality and functional requirements can be fulfilled.

B. "The system shall have at least 90% of availability" is an example of a functional requirement.

C. Quality requirements describe how a system interacts with its environment.

D. All the other options are wrong.

A. There is no problem in mixing requirements from different abstraction levels in medium sized work products.

B. In small work products, requirements should stay at the same abstraction level.

C. If the subject to be specified is a low level element of the solution, the requirement should naturally be specified at a low abstraction level.

D. In large work products, requirements from different abstraction levels should be organized by structuring the specification.

A. Constraints

B. Regulations

C. Elicitation

D. Documents

A. The freedom of the developers decreases.

B. The cost of the specification increases.

C. The risk of missing features decreases.

D. The cost of the system increases.

A. They have high ambiguity.

B. They help to capture the most relevant information.

C. They are extremely flexible.

D. They improve the focus on the content.

A. A situation where stakeholders disagree due to differing interpretations of the same information.

B. A conflict arising from misunderstandings due to ambiguous terminology in requirements documentation.

C. A disagreement caused by stakeholders having competing goals, such as cost reduction versus performance improvement.

D. A scenario where two workers that dislike each other avoid talking to reach a common ground.

A. Inspection

B. Apprenticing

C. Walk through

D. Visualization

E. Generalization

F. Monitoring

G. Perspective-based reading

H. Validation by using an interface prototype

I. Decomposition

J. Stakeholder analysis

K. Ranking