1. A condition or capability needed by a user to solve a problem or achieve an objective
2. A condition or capability that must be met or possessed by a system or component to satisfy a contract, standard, specification, or other formally imposed documents
3. A documented representation of a condition or capability
4. Depending on the context, one of the three propositions above

1. Liability is the degree of obligation relative to a requirement.
2. Liability is an attribute that may imply legal responsibility.
3. The degree of commitment is calculated by multiplying the priority index by the criticity index.
4. The MoSCoW notation expresses the required degree of liability.

1. The counter-requirements, which cover the features that the solution must not contain
2. The threshold attributes, that the users will expect in all cases
3. The performance attributes, that present a proportional relation between functionality and satisfaction
4. The excitement attributes, that the users don't expect, but will enjoy and find delightful

1. Verification helps to know if you have created the product correctly; validation helps to know if the product meets the customer's needs.
2. Validation is the sum of all incremental verifications.
3. Validation is a verification which takes place in the target environment.
4. Verification is conducted by the project team, while validation is conducted by third-party teams (for example during an audit)

1. The vertical prototype, which offers a reduced number of features, but where each feature is detailed
2. The horizontal prototype, which contains a large number of features, but where each features is mostly incomplete
3. The diagonal prototype, which shows superficially a large number of features, and shows in depth a small number of features
4. The scenario-oriented prototype, where all involved features are simulated for a specific task, combining vertical and horizontal prototypes

1. Overall more expensive than other types of defects
2. Overall non-functional defects
3. Generally not critical
4. Generally easy to identify

8 - Which of these elements helps to improve the testability of a requirement?

1. The involvement of stakeholders, especially customers
2. Risk analysis
3. The outputs of the elicitation phase
4. The acceptance criteria

9 - In an agile environment, through which mechanism the requirements are not communicated?

1. It is common to represent human actors, for example by modeling them with a drawing of a man
2. In this type of diagram, the use cases represented do not follow one another (there is no temporal representation)
3. It is possible to use a use case diagram to macroscopically represent the rights granted to each main type of users of a solution.
4. The prerequisites of a use case are expressed by the keyword 'extend'.

1. Activity diagrams focus on processes by focusing on actions, as opposed to objects.
2. An activity diagram can be produced to describe a use case.
3. In the representation of a conditional transition, the different decisions must be mutually exclusive.
4. Actions are represented by arrows and transitions are represented by nodes.

1. This diagram offers a complete and unambiguous view of all the behaviors of the element represented.
2. This diagram represents an element of the system within its environment: actors (human or systems) are included.
3. Waiting times may appear on this type of diagram.
4. It is mandatory to represent the initial state, but not the final state(s).

13 - A software publisher is developing a home automation application. Regulations on the security required for this type of software come into effect. For the application in development, this impacts in the first place:

1. System boundary and requirements management
2. System boundary and requirements priorization
3. System context and requirements sources
4. System sources and requirements context

15 - According to IREB, models have three important properties. Which one is not part of it?

1. Models map reality (representation)
2. Models reduce the represented reality (reduction)
3. Models are constructed for a special purpose (pragmatic)
4. Models are maintainable by all stakeholders (shared responsibility)

16 - Which of these aspects is not one of the eight criteria for validating the content of a requirement?

17 - Which of these activities is not part of the four requirements negotiation activities?

1. Conflict analysis
2. Resolution scenario development
3. Conflict resolution
4. Documentation of conflict resolutions

1. Elicitation - Documentation - Validation/negotiation - Management of requirements
2. Elicitation - Analysis - Synthesis - Development
3. Elicitation - Delimitation - Completion / Simplification - Finalization
4. Elucidation - Decomposition - Modeling - Confirmation

19 - Using the Karl Wiegers priority matrix (1999), how is the priority index of a requirement calculated?

1. Priority = Value in % / Cost in % * Cost weight / Risk in % * Risk weight
2. Priority = Value in % / (Cost in % * Cost weight + Risk in % * Risk weight)
3. Priority = Value in % / Cost in % * Cost weight * Risk in % * Risk weight
4. Priority = Value in % * Cost in % * Cost weight * Risk in % * Risk weight

20 - According to IREB, there are three kinds of changes in requirements. Which one is not part of it?

IREB CPRE, Foundation Level online training