ISQI IREB Certified Professional for Requirements Engineering. Foundation Level - CPRE-FL_Syll_3.0 Exam Practice Test

A. Excitement attributes

B. Goals

C. Performance attributes

D. Basic attributes

E. Needs

A. Cost conflict

B. Structural conflict

C. Value conflict

D. Architectural conflict

E. Subject matter conflict

A. Actors, messages and activities

B. Objects, activities and associations

C. Actors, use cases and associations

D. Objects, use cases and activities

A. Version numbers always start with "one".

B. Version control is useful for following the evolving history of a requirement.

C. Each new version requires a clear description of what was changed in relation to the last version.

D. Version numbers are typically composed of at least 2 components: version and increment.

A. Universal quantifiers have been used.

B. Nominalizations have been used.

C. The requirement has incomplete conditions.

D. The requirement is written in the passive voice.

A. Domain-specific standards

B. Geographic distance

C. Informed mutual trust

D. Large and diverse teams

A. Will is used for factual statements, not requirements.

B. Even requirements using may are mandatory.

C. Should is used for mandatory requirements.

D. Shall is used for requirements that are strongly desired but not mandatory.

A. All the other options are wrong.

B. Contractual RE Process

C. Product-Oriented RE Process

D. Participatory RE Process

A. "Collaboration in RE" tools are used for sharing requirements.

B. All the other options are wrong.

C. Office tools should never be used to manage requirements.

D. "Management of requirements" tools are used to manage the RE workflow.

A. The ability to change requirements easily is important for the project.

B. The development process for the system is plan-driven.

C. A comprehensive requirements specification is required as a contractual basis for outsourcing or tendering the design and implementation of the system.

D. The stakeholders are available, know their requirements, and can specify them up front.

A. Ubiquitous requirements

B. Unwanted behaviour

C. Event-driven requirements

D. State-driven requirements

A. Stakeholders are available such that short feedback loops can be established.

B. Few requirements are known up front and many more will emerge and evolve.

C. Requirements tend to change frequently.

D. A comprehensive requirements specification is required as a contractual basis for outsourcing or tendering.

A. They improve the focus on the content.

B. They are extremely flexible.

C. They help to capture the most relevant information.

D. They have high ambiguity.

A. The RE effort should be directly proportional to the risk that the enterprise is willing to take.

B. All the other options are wrong.

C. The benefits of Requirements Engineering are usually short term.

D. The costs of Requirements Engineering are immediate.

A. Make sure that identification and correction of defects are done by the same workers.

B. Repeat validation in successive milestones.

C. Perform validation from different views.

D. Make sure that there is independence between the people involved in the elicitation of the requirements and those validating them.