ISQI IREB Certified Professional for Requirements Engineering. Foundation Level - CPRE-FL_Syll_3.0 Free Exam Questions

A. Cost conflict

B. Structural conflict

C. Value conflict

D. Subject matter conflict

E. Architectural conflict

A. Y = Implementation of requirements; X = Happiness of stakeholders

B. Y = Customer satisfaction; X = Specified requirements

C. Y = Customer satisfaction; X = Implementation of requirements

D. Y = Happiness of stakeholders; X = Implementation of requirements

A. Experimental prototype

B. Exploratory prototype

C. Evolutionary prototype

D. Mock-ups

E. Technical feasibility prototype

A. Ability to analyze requirements for contradictory content, especially between the requirements specifications and the test cases

B. Traceability of the effort for the elicitation of requirements, beginning with the elicitation of the documentation right to the point of requirements acceptance

C. Traceability of the requirements, along with the associated documents, from the requirements elicitation to the implementation

D. Level of stabilisation between the elicited and approved requirements

E. Monitoring of progress in requirements elicitation

A. Stakeholder-Activity Diagram

B. Block Definition Diagram

C. Use case diagram

D. Data Flow Diagram

A. "Conformant" is a quality criteria for work products covering multiple requirements.

B. "Non-redundant" is a quality criteria for single requirements.

C. "Traceable" is a quality criteria for single requirements.

D. "Consistent" is a quality criteria for work products covering multiple requirements.

A. Experimental prototype

B. Shared-understanding prototype

C. Exploratory prototype

D. Evolutionary prototype

A. The developing team is less familiar with the context.

B. Freedom given to developers is low.

C. Shared understanding of the problem is low.

D. The availability of feedback from stakeholders is high.

A. Traceability Matrix

B. Configuration Control Board

C. Decision Matrix

D. Kano Analysis Matrix

A. The focus on a single aspect makes it easy to understand the requirements modeled.

B. Requirements models do not have to be accompanied by natural language.

C. Requirement models are less flexible than requirements written with natural language.

D. Requirement models have a lacking focus on quality requirements and constraints.

A. Non-validated requirements are worthless.

B. Systems should be isolated from proper understanding.

C. Requirements Engineering is about satisfying only users' needs.

D. Requirements should be viewed as means to an end, not the end in itself.

E. Changing requirements are the exception, not the normal case.

A. Excitement attributes

B. Goals

C. Performance attributes

D. Needs

E. Basic attributes