Tag the questions with any skills you have. Your dashboard will track each student's mastery of each skill.
Give this quiz to my class
Q 1/23
Score 0
An attribute sheme is the definition of the attribute structure for the requirements.
120
true
false
Q 2/23
Score 0
Attribute schemes can only be defined in tabular form.
120
false
true
23 questions
Q.
An attribute sheme is the definition of the attribute structure for the requirements.
1
120 sec
Q.
Attribute schemes can only be defined in tabular form.
2
120 sec
Q.
Attribute schemes are frequently defined and adapted on program level on the basis of specific conditions.
3
120 sec
Q.
The definition of an attribute includes a unique name, a short description, and condition to test for valid values.
4
120 sec
Q.
Defining different attribute schemes for the different kinds of requirements (functional, quality, constraints) is sensible.
5
120 sec
Q.
The testers in the project are interested only in a certain set of requirements to start defining test cases for them. Which ONE of the following criteria best matches the selection query for the required selective view?
6
120 sec
Q.
Prioritization of requirements is based on one or more attributes. Which is/are NOT typically used to decide on the priority?
7
120 sec
Q.
A medium sized company decides to procure an Enterprise Resource Planning (ERP) system. Which of the following prioritization technique for the requirements of the ERP system is most suitable?
8
120 sec
Q.
A company develops an innovative software product. Which of the following prioritization technique is most suitable to support the release planning?
9
120 sec
Q.
Traceability simplifies the verifiability of requirements, i.e. to check if requirements have been implemented in the system or not.
10
120 sec
Q.
Traceability supports the maintenance and administration, e.g. cause and effects of defects can be identified much simpler.
11
120 sec
Q.
Traceability supports the reuse of requirements by comparing the goals and tracing them to the supporting requirements.
12
120 sec
Q.
Traceability supports accountability, i..e in case of a liability issue, the requirements engineer that authored a requirement can be traced.
13
120 sec
Q.
Traceability helps to determine the impact in case of a change request.
14
120 sec
Q.
Versioning of requirements helps managing the changes over the lifecycle of a system.
15
120 sec
Q.
Versioning provides at a later stage access to development states of requirement documents
16
120 sec
Q.
Applying versioning makes only sense for the versioning of requirements documents.
17
120 sec
Q.
A version number has at least the following three components: version, major increment and minor increment.
18
120 sec
Q.
A requirements configuration is a set of loosely related requirements, for which up to two different versions of each requirement can be contained in the configuration.
19
120 sec
Q.
A requirements baseline is a specific requirements configuration for a special purpose.
20
120 sec
Q.
What is NOT the reason why different views should be applied (which show only parts of the requirements at a time) instead of displaying all requirements and attributes?
21
120 sec
Q.
Which of the following statements about traceability is FALSE?
22
120 sec
Q.
Additional information on requirements is managed using attributes. An example of such additional information is a unique identifier. Which of the followings is FALSE?
