Test your basic knowledge |

CPRE: Certified Professional Requirements Engineering

Subjects : certifications, cpre, it-skills

Instructions:

Answer 50 questions in 15 minutes.
If you are not ready to take this test, you can study here.
Match each statement with the correct term.
Don't refresh. All questions and answers are randomly picked and ordered every time you load a test.

This is a study tool. The 3 wrong answers for each question are randomly chosen from answers to other questions. So, you might find at times the answers obvious, but you will see it re-enforces your understanding as you take the test each time.

1. Stakeholder

Warning: Invalid argument supplied for foreach() in /var/www/html/basicversity.com/show_quiz.php on line 183

2. Correctness
An artificial language that has been created for expressing specifications.
An intermediate or final result of system development; for example - a requirements specification.
1. A need perceived by a stakeholder 2. A capability or property that a system shall have 3. A documented representation of a need - capability or property.
The degree to which the information contained in an artifact is probably true. In RE - correctness is frequently used as a synonym for adequacy.

3. Requirements analysis
1. Analysis of elicited requirements in order to understand and document them. 2. Synonym for requirements engineering.
A consistent set of logically coherent units. The units are individually identifiable artifacts or parts of artifacts (e.g. - requirements) in at most one version per unit.
A requirement that pertains to a quality concern that is not covered by functional requirements.
The degree to which something actually happens in the way it ought to happen. In RE - typically the degree to which a system actually enables its users to achieve their goals as stated in the system's requirements.

4. Standard
A uniform regulation for perceiving - manufacturing or executing something.
An intermediate or final result of system development; for example - a requirements specification.
Requirements elicitation
1. A need perceived by a stakeholder 2. A capability or property that a system shall have 3. A documented representation of a need - capability or property.

5. Requirements model
A model that has been created with the purpose of specifying requirements.
A committee that supervises a project.
A committee of client and supplier representatives that decides on change requests. Abbreviation: CCB
A verb characterizing the required action in a requirement written in natural language.

6. Reliability
The capability of a system to maintain a specified level of functionality and performance when used under specified conditions. Reliability may be stated as a quality requirement.
A committee that supervises a project.
Traceability of a requirement forward to its implementation in design and code - RS stands for requirements specification.
A delimitable characteristic of a system that provides value for stakeholders. Normally comprises several requirements and is used for communicating with stakeholders on a higher level of abstraction and for expressing variable or optional characteri

7. Checking (requirements)
1. In general: A principle for ordering and structuring. 2. In Informatics: A coherent - delimitable set of components that - by coordinated action - provides services. Requirements Engineering is concerned with the specification of requirements for
Comprises requirements validation and checking requirements for qualities such as unambiguity or comprehensibility.
A spot in an artifact that is incorrectly described or crafted. Synonym: fault - bug.
A systematic and disciplined approach to the specification and management of requirements with the following goals: (1) Knowing the relevant requirements - achieving a consensus among the stakeholders about these requirements - documenting them accor

8. Cardinality
Cardinality.
Traceability of a requirement back to its origin.
The rules for constructing structured signs in a language.
1. In modeling: The minimum and maximum number of objects in a relationship. In UML - the term multiplicity is used for cardinality. 2. In mathematics: The number of elements in a set.

9. Requirements elicitation
The meaning of a sign or a set of signs in a language.
A (software) system that helps develop - operate and maintain systems. In RE - tools support requirements management as well as modeling - documenting - and validating requirements.
A model of data that are relevant for a system - or of the data of an application domain. An ERM consists of a set of entity types that are each characterized by attributes and linked by relationships. Abbreviation: ERM - ER Model
The process of seeking - capturing and consolidating requirements from available requirements sources. May include the re-construction or creation of requirements. Aka Requirements discovery

10. Inspection

Warning: Invalid argument supplied for foreach() in /var/www/html/basicversity.com/show_quiz.php on line 183

11. Requirements discovery
Requirements elicitation
A document consisting of a requirements specification. Frequently used as a synonym for requirements specification.
The meaning of a sign or a set of signs in a language.
A person or organization who receives a product or service. Also see stakeholder.

12. Constraint
A requirement that limits the solution space beyond what is necessary for meeting the given functional requirements and quality requirements.
A coarse description of the required capabilities of a system from the customer's perspective. Usually supplied by the customer.
A requirement that pertains to a quality concern that is not covered by functional requirements.
Requirements elicitation.

13. Requirements source
The source from which a requirement has been derived. Typical sources are stakeholders - documents - existing systems and observations.
A person or organization who receives a product or service. Also see stakeholder.
A requirements specification pertaining to a system. Frequently considered to be a synonym for requirements specification.
The capability of a system to maintain a specified level of functionality and performance when used under specified conditions. Reliability may be stated as a quality requirement.

14. Requirement (modern definition)
1. A need perceived by a stakeholder 2. A capability or property that a system shall have 3. A documented representation of a need - capability or property.
A blueprint for the syntactic structure of individual requirements.A phrase template is a specific requirements template for requirements written in natural language.
A model of data that are relevant for a system - or of the data of an application domain. An ERM consists of a set of entity types that are each characterized by attributes and linked by relationships. Abbreviation: ERM - ER Model
A person who uses the functionality provided by a system. Also called end user.

15. Quality requirement
A requirement concerning a result of behavior that shall be provided by a function of a system (or of a component or service).
A requirement that pertains to a quality concern that is not covered by functional requirements.
A systematically represented collection of requirements - typically for a system or component - that satisfies given criteria. In some situations we distinguish between a customer requirements specification (typically written by the customer) and a s
An excerpt from an artifact - containing only those parts one is currently interested in. A view can abstract or aggregate parts of the artifact.

16. User
A person who uses the functionality provided by a system. Also called end user.
A desired state of affairs (that a stakeholder wants to achieve). Goals describe intentions of stakeholders. They may conflict with one another.
The capability of a system to be understood - learned - used - and liked by its users. Usability (or parts thereof) may be stated as quality requirements.
An excerpt from an artifact - containing only those parts one is currently interested in. A view can abstract or aggregate parts of the artifact.

17. End user
The degree to which a requirement is expressed such that it cannot be understood differently by different people.
A requirements specification pertaining to a software system. Abbreviation: SRS
The process of checking whether documented requirements match the stakeholders' needs.
User.

18. Error
If an entity exists in multiple - time-ordered occurrences - where each occurrence has been created by modifying one of its predecessors - every occurrence is a version of that entity.
A discrepancy between an observed behavior or result and the specified behavior or result. An error typically is a symptom for the existence of a fault or defect in some artifact. In colloquial English - there is sometimes no distinction between the
The capability of a system to achieve an acceptable level of probability that operating the system will not result in harming people - property or the environment. Safety requirements may be stated as quality requirements or in terms of functional re
1. A need perceived by a stakeholder 2. A capability or property that a system shall have 3. A documented representation of a need - capability or property.

19. Class diagram
A spot in an artifact that is incorrectly described or crafted. Synonym: fault - bug.
A collection of definitions of terms that are relevant in some domain. Frequently - a glossary also contains cross-references - synonyms - homonyms - acronyms - and abbreviations.
The source from which a requirement has been derived. Typical sources are stakeholders - documents - existing systems and observations.
A diagrammatic representation of a class model.

20. Change control board
The capability of a system to maintain a specified level of functionality and performance when used under specified conditions. Reliability may be stated as a quality requirement.
The capability of a system to achieve an acceptable level of probability that operating the system will not result in harming people - property or the environment. Safety requirements may be stated as quality requirements or in terms of functional re
A committee of client and supplier representatives that decides on change requests. Abbreviation: CCB
Requirements source

21. State machine
A coarse description of the required capabilities of a system from the customer's perspective. Usually supplied by the customer.
A model describing the behavior of a system or component by a finite set of states and state transitions. State transitions are triggered by events and can in turn trigger actions and new events.
1. In modeling: The minimum and maximum number of objects in a relationship. In UML - the term multiplicity is used for cardinality. 2. In mathematics: The number of elements in a set.
The capability of a system to achieve an acceptable level of probability that operating the system will not result in harming people - property or the environment. Safety requirements may be stated as quality requirements or in terms of functional re

22. State charts
The capability of an artifact to adhere to standards - regulations - laws - or other formally imposed documents. Systems frequently need to comply with standards - regulations - and laws constraining the domain where the system is deployed. Such com
State machines having states that are hierarchically and/or orthogonally decomposed.
The process of seeking - capturing and consolidating requirements from available requirements sources. May include the re-construction or creation of requirements. Aka Requirements discovery
A certain perspective on the requirements of a system. Typical viewpoints are perspectives that a stakeholder or stakeholder group has (for example - an end user's perspective or an operator's perspective). However - there can also be topical viewpoi

23. Software requirements specification
A requirements specification pertaining to a software system. Abbreviation: SRS
Those parts of the real world that are relevant for determining the context of a system.
Requirements elicitation.
An artificial language that has been created for expressing specifications.

24. Adequacy (of a requirement)

Warning: Invalid argument supplied for foreach() in /var/www/html/basicversity.com/show_quiz.php on line 183

25. Configuration
A spot in an artifact that is incorrectly described or crafted. Synonym: fault - bug.
A consistent set of logically coherent units. The units are individually identifiable artifacts or parts of artifacts (e.g. - requirements) in at most one version per unit.
The capability of a system to maintain a specified level of functionality and performance when used under specified conditions. Reliability may be stated as a quality requirement.
The degree to which something actually happens in the way it ought to happen. In RE - typically the degree to which a system actually enables its users to achieve their goals as stated in the system's requirements.

26. Supplier
A quality requirement or a constraint. Performance requirements may be regarded as another category of non-functional requirements. In this glossary - performance requirements are considered to be a sub-category of quality requirements. Synonym: Extr
Comprises requirements validation and checking requirements for qualities such as unambiguity or comprehensibility.
Something which is formal to some extent - but not completely. An artifact is called semi-formal if it contains formal parts - but isn't formalized totally. Typically - a semi-formal artifact has a defined syntax - while the semantics is partially de
A person or organization who delivers a product or service to a customer.

27. Source (of a requirement)
Requirements source
An artificial language that has been created for expressing specifications.
1. Analysis of elicited requirements in order to understand and document them. 2. Synonym for requirements engineering.
A model that has been created with the purpose of specifying requirements.

28. Class model
The capability of a system to achieve an acceptable level of probability that operating the system will not result in harming people - property or the environment. Safety requirements may be stated as quality requirements or in terms of functional re
The degree to which a requirements specification conforms to regulations given in some standard.
A document consisting of a requirements specification. Frequently used as a synonym for requirements specification.
A model consisting of a set of classes and relationships between them.

29. Artifact
An intermediate or final result of system development; for example - a requirements specification.
The ease with which a system can be transferred to another platform (while preserving its functionality). Portability may be stated as a quality requirement.
A diagram modeling the functionality of a system or component by processes (also called activities) - data stores and data flows. Incoming data flows trigger processes which then consume the received data - transform them - read/write persistent data
1. A description of a potential sequence of events that lead to a desired (or unwanted) result. 2. An ordered sequence of interactions between partners - in particular between a system and external actors. May be a concrete sequence (instance scenari

30. Compliance
A diagram type in UML which models the interactions between a selected set of objects and/or actors in the sequential order that those interactions occur.
When viewed in isolation - a component is a system by itself. 1. In general: A delimitable part of a system. 2. In software architecture: An encapsulated set of coherent objects or classes that jointly provide a service.
Requirements elicitation.
The capability of an artifact to adhere to standards - regulations - laws - or other formally imposed documents. Systems frequently need to comply with standards - regulations - and laws constraining the domain where the system is deployed. Such com

31. Acceptance
The degree to which a requirement expresses the stakeholders' true desires and needs (i.e. - those they had actually in mind when stating the requirement).
A state machine with atomic states.
The process of assessing whether a system satisfies all its requirements.
A committee that supervises a project.

32. UML
Abbreviation for Unified Modeling Language - a standardized language for modeling problems or solutions.
Documents the importance of a requirement in comparison to other requirements according to given criteria.
Requirements elicitation
A tabular - systematic representation of a complex decision that depends on multiple criteria.

33. Entity
A diagram modeling the functionality of a system or component by processes (also called activities) - data stores and data flows. Incoming data flows trigger processes which then consume the received data - transform them - read/write persistent data
The degree to which a requirement expresses the stakeholders' true desires and needs (i.e. - those they had actually in mind when stating the requirement).
If an entity exists in multiple - time-ordered occurrences - where each occurrence has been created by modifying one of its predecessors - every occurrence is a version of that entity.
1. In general: an element or set of elements that may stand for any conceivable item - e.g. - a system - a part of reality - a thing - an organization - a process - etc. 2. In entity-relationship-modeling: an individual object which has an identity a

34. Prototype
A state machine having states that are hierarchically and/or orthogonally decomposed.
1. In manufacturing: a piece which is built prior to the start of mass production. 2. In software engineering: An executable piece of software that implements critical parts of a system in advance. In Requirements Engineering - prototypes are used as
A term looking identical to another term - but having a different meaning. For example - bill as a bank note and bill as a list (of materials) are homonyms.
A spot in an artifact that is incorrectly described or crafted. Synonym: fault - bug.

35. Fault
A model describing the behavior of a system or component - e.g. - by a state machine.
Defect.
A model that represents the goals of something as an ordered structure of sub-goals.
The degree to which a set of inherent characteristics of an entity fulfills requirements. The entity may be a system - service - product - artifact - process - person - organization - etc. An inherent characteristic is a distinguishing feature of or

36. Context

Warning: Invalid argument supplied for foreach() in /var/www/html/basicversity.com/show_quiz.php on line 183

37. Performance requirement
A formally organized endeavor for checking an artifact by a group of experts. Checking may be performed with respect to both contents and conformance.
A requirement concerning a result of behavior that shall be provided by a function of a system (or of a component or service).
The degree to which a result is achieved with minimum consumption of resources.
A requirement describing a performance characteristic (timing - speed - volume - capacity - throughput...). Is regarded in this glossary as a sub-category of quality requirements - but can also be considered as a non-functional requirements category

38. Priority (of a requirement)
A consistent set of logically coherent units. The units are individually identifiable artifacts or parts of artifacts (e.g. - requirements) in at most one version per unit.
(1) process- orientation - (2) stakeholder focus - and (3) importance of risk and value considerations.
Documents the importance of a requirement in comparison to other requirements according to given criteria.
A systematically represented description of the properties of an entity (a system - a device - etc.) that satisfies given criteria. It may be about required properties (requirements specification) or implemented properties (e.g. - a technical product

39. Phrase template
A template for the syntactic structure of a phrase that expresses an individual requirement in natural language
A document consisting of a requirements specification. Frequently used as a synonym for requirements specification.
The degree to which a requirement is expressed such that it cannot be understood differently by different people.
The process of checking whether documented requirements match the stakeholders' needs.

40. Activity diagram
A template for the syntactic structure of a phrase that expresses an individual requirement in natural language
A uniform regulation for perceiving - manufacturing or executing something.
A diagram type in UML which models the flow of actions in a system or in a component including data flows and areas of responsibility where necessary.
1. Generally in RE: A person - a system or a technical device in the context of a system that interacts with the system. 2. Especially in goal-oriented RE: a person - a system or a technical device that may act and process information in order to ach

41. Behavior Model
A model describing the behavior of a system or component - e.g. - by a state machine.
The ease with which a software system can be modified to correct faults or adapt the system to changing needs. Maintainability may be stated as a quality requirement
A person who - in collaboration with stakeholders - elicits - documents - validates - and manages requirements.
The degree to which a set of requirements is free of contradicting statements.

42. System boundary
The process of checking whether documented requirements match the stakeholders' needs.
The degree to which a requirements specification conforms to regulations given in some standard.
A document consisting of a requirements specification. Frequently used as a synonym for requirements specification.
The boundary between a system and its surrounding context.It separates the system to be developed from its environment; i.e. - it separates the part of the reality that can be modified or altered by the development process from aspects of the environ

43. Context model
A model describing the behavior of a system or component by a finite set of states and state transitions. State transitions are triggered by events and can in turn trigger actions and new events.
1. In general: an element or set of elements that may stand for any conceivable item - e.g. - a system - a part of reality - a thing - an organization - a process - etc. 2. In entity-relationship-modeling: an individual object which has an identity a
Requirements elicitation.
A model describing a system in its context.

44. Defect
A spot in an artifact that is incorrectly described or crafted. Synonym: fault - bug.
1. A description of a potential sequence of events that lead to a desired (or unwanted) result. 2. An ordered sequence of interactions between partners - in particular between a system and external actors. May be a concrete sequence (instance scenari
The degree to which a set of requirements is free of contradicting statements.
A blueprint for the syntactic structure of individual requirements.A phrase template is a specific requirements template for requirements written in natural language.

45. Scope (of a system)
A kind of review where the artifact under review is inspected by a group of experts according to given criteria. The experts' findings are then collected and consolidated.
The range of things that can be shaped and designed when developing a system.
A person or organization who receives a product or service. Also see stakeholder.
A uniform regulation for perceiving - manufacturing or executing something.

46. Non-functional requirement
A quality requirement or a constraint. Performance requirements may be regarded as another category of non-functional requirements. In this glossary - performance requirements are considered to be a sub-category of quality requirements. Synonym: Extr
The capability of a system to achieve an acceptable level of probability that operating the system will not result in harming people - property or the environment. Safety requirements may be stated as quality requirements or in terms of functional re
A systematic and disciplined approach to the specification and management of requirements with the following goals: (1) Knowing the relevant requirements - achieving a consensus among the stakeholders about these requirements - documenting them accor
The ability to trace a requirement (1) back to its origins - (2) forward to its implementation in design and code - (3) to requirements it depends on (and vice-versa). Origins may be stakeholders - documents - rationale - etc. Sometimes - traceabilit

47. Efficiency
The degree to which a result is achieved with minimum consumption of resources.
A requirement describing a performance characteristic (timing - speed - volume - capacity - throughput...). Is regarded in this glossary as a sub-category of quality requirements - but can also be considered as a non-functional requirements category
1. In general: A principle for ordering and structuring. 2. In Informatics: A coherent - delimitable set of components that - by coordinated action - provides services. Requirements Engineering is concerned with the specification of requirements for
The capability of a system to achieve an acceptable level of probability that operating the system will not result in harming people - property or the environment. Safety requirements may be stated as quality requirements or in terms of functional re

48. System
An event that threatens the success of an endeavor - e.g. - of developing or operating a system. A risk is typically assessed in terms of its probability and potential damage.
A model that represents the goals of something as an ordered structure of sub-goals.
1. In general: A principle for ordering and structuring. 2. In Informatics: A coherent - delimitable set of components that - by coordinated action - provides services. Requirements Engineering is concerned with the specification of requirements for
Defect.

49. Baseline
The range of things that can be shaped and designed when developing a system.
A stable - change-controlled configuration of artifacts. Baselines serve for release planning and release definition as well as for project management purposes such as effort estimation.
A coarse description of the required capabilities of a system from the customer's perspective. Usually supplied by the customer.
A person or organization who delivers a product or service to a customer.

50. System requirement
A requirement pertaining to a system or to a component of a system.
A state machine having states that are hierarchically and/or orthogonally decomposed.
The degree to which a requirement is expressed such that it cannot be understood differently by different people.
1. Generally in RE: A person - a system or a technical device in the context of a system that interacts with the system. 2. Especially in goal-oriented RE: a person - a system or a technical device that may act and process information in order to ach