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. Requirements analysis
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.
1. Analysis of elicited requirements in order to understand and document them. 2. Synonym for requirements engineering.
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.
State machines having states that are hierarchically and/or orthogonally decomposed.

2. Context

3. Scope (of a system)
The range of things that can be shaped and designed when developing a system.
Documents the importance of a requirement in comparison to other requirements according to given criteria.
A graphic representation of an entity-relationship model. Abbreviation: ERD
A diagrammatic representation of a state machine.

4. Reliability
Boundary between the context of a system and those parts of the application domain that are irrelevant for the system and its requirements. It separates the relevant part of the environment of a system to be developed from the irrelevant part - i.e.
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 formally organized endeavor for checking an artifact by a group of experts. Checking may be performed with respect to both contents and conformance.
The degree to which the fulfillment of a requirement by an implemented system can be checked - e.g. - by defining acceptance test cases - measurements or inspection procedures.

5. Requirements document
State machines having states that are hierarchically and/or orthogonally decomposed.
A person or organization who delivers a product or service to a customer.
A document consisting of a requirements specification. Frequently used as a synonym for requirements specification.
1. In general: The network of thoughts and meanings needed for understanding phenomena or utterances. 2. Especially in RE: The part of a system's environment being relevant for understanding the system and its requirements. Context in the second mea

6. Defect
The degree to which an artifact enables a required modification of the artifact.
A spot in an artifact that is incorrectly described or crafted. Synonym: fault - bug.
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 has been created with the purpose of specifying requirements.

7. Supplier
Multiple occurrence of the same information or resource.
Boundary between the context of a system and those parts of the application domain that are irrelevant for the system and its requirements. It separates the relevant part of the environment of a system to be developed from the irrelevant part - i.e.
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.

8. Multiplicity
A desired state of affairs (that a stakeholder wants to achieve). Goals describe intentions of stakeholders. They may conflict with one another.
Cardinality.
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.
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

9. Important facets of RE
A baseline for a set of requirements.
1. A diagrammatic representation of a context model. 2. In Structured Analysis - the context diagram is the root of the data flow diagram hierarchy.
(1) process- orientation - (2) stakeholder focus - and (3) importance of risk and value considerations.
The process of assessing whether a system satisfies all its requirements.

10. Sequence diagram
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.
An intermediate or final result of system development; for example - a requirements specification.
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.
A requirement that limits the solution space beyond what is necessary for meeting the given functional requirements and quality requirements.

11. Performance requirement
The degree to which a set of requirements is free of contradicting statements.
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
Boundary between the context of a system and those parts of the application domain that are irrelevant for the system and its requirements. It separates the relevant part of the environment of a system to be developed from the irrelevant part - i.e.
A collection of definitions of terms that are relevant in some domain. Frequently - a glossary also contains cross-references - synonyms - homonyms - acronyms - and abbreviations.

12. Conformity (of requirements)
Cardinality.
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
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.
The degree to which a requirements specification conforms to regulations given in some standard.

13. Functional requirement
A person who - in collaboration with stakeholders - elicits - documents - validates - and manages requirements.
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
A requirement concerning a result of behavior that shall be provided by a function of a system (or of a component or service).
The process of assessing whether a system satisfies all its requirements.

14. Functionality
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
A range of relevant things (for some given matter); for example - an application domain.
A requirement that pertains to a quality concern that is not covered by functional requirements.
The capabilities of a system as stated by its functional requirements.

15. Goal model
A graphic representation of an entity-relationship model. Abbreviation: ERD
A model that represents the goals of something as an ordered structure of sub-goals.
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
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.

16. Structured analysis
An approach for specifying the functionality of a system based on a hierarchy of dataflow diagrams. Data flows as well as persistent data are defined in a data dictionary. A context diagram models the sources of incoming and the destinations of outgo
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.
A model describing the behavior of a system or component - e.g. - by a state machine.
The meaning of a sign or a set of signs in a language.

17. Attribute
The process of managing existing requirements and requirements related artifacts. Includes particularly storing - changing and tracing of requirements traceability).
Comprises requirements validation and checking requirements for qualities such as unambiguity or comprehensibility.
Multiple occurrence of the same information or resource.
A characteristic property of an entity.

18. Elicitation (of requirements)
A structured set of signs for expressing and communicating information. Signs are elements that are used for communication: expressions in a language - symbols - gestures - etc.
Abbreviation for Unified Modeling Language - a standardized language for modeling problems or solutions.
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.

19. Language
A structured set of signs for expressing and communicating information. Signs are elements that are used for communication: expressions in a language - symbols - gestures - etc.
A coarse description of the required capabilities of a system from the customer's perspective. Usually supplied by the customer.
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
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.

20. Context diagram
1. A diagrammatic representation of a context model. 2. In Structured Analysis - the context diagram is the root of the data flow diagram hierarchy.
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 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
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.

21. Checking (requirements)
Comprises requirements validation and checking requirements for qualities such as unambiguity or comprehensibility.
1. A diagrammatic representation of a context model. 2. In Structured Analysis - the context diagram is the root of the data flow diagram hierarchy.
In RE: A well-argued request for changing one or more baselined requirements.
Traceability of a requirement back to its origin.

22. Scenario
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 coarse description of the required capabilities of a system from the customer's perspective. Usually supplied by the customer.
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 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

23. Verifiability (of requirements)
A uniform regulation for perceiving - manufacturing or executing something.
The ease with which a system can be transferred to another platform (while preserving its functionality). Portability may be stated as a quality requirement.
The process of seeking - capturing and consolidating requirements from available requirements sources. May include the re-construction or creation of requirements. Aka Requirements discovery
The degree to which the fulfillment of a requirement by an implemented system can be checked - e.g. - by defining acceptance test cases - measurements or inspection procedures.

24. Change control board
Documents the importance of a requirement in comparison to other requirements according to given criteria.
A committee of client and supplier representatives that decides on change requests. Abbreviation: CCB
A requirement concerning a result of behavior that shall be provided by a function of a system (or of a component or service).
The capability of a system to protect (a) its data and resources against unauthorized use and (b) its legitimate users against denial of service.

25. State machine
The process of managing existing requirements and requirements related artifacts. Includes particularly storing - changing and tracing of requirements traceability).
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 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.
An approach for specifying the functionality of a system based on a hierarchy of dataflow diagrams. Data flows as well as persistent data are defined in a data dictionary. A context diagram models the sources of incoming and the destinations of outgo

26. Validation (of requirements)

27. Domain
The degree to which a requirements specification conforms to regulations given in some standard.
A language for expressing models of a certain kind. May be textual - graphic - symbolic or some combination thereof.
A range of relevant things (for some given matter); for example - an application domain.
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

28. Post-RS traceability
Multiple occurrence of the same information or resource.
A requirements specification pertaining to a software system. Abbreviation: SRS
The range of things that can be shaped and designed when developing a system.
Traceability of a requirement forward to its implementation in design and code - RS stands for requirements specification.

29. Glossary
A (software) system that helps develop - operate and maintain systems. In RE - tools support requirements management as well as modeling - documenting - and validating requirements.
An approach for specifying the functionality of a system based on a hierarchy of dataflow diagrams. Data flows as well as persistent data are defined in a data dictionary. A context diagram models the sources of incoming and the destinations of outgo
A collection of definitions of terms that are relevant in some domain. Frequently - a glossary also contains cross-references - synonyms - homonyms - acronyms - and abbreviations.
A kind of review where the author of an artifact under review walks a group of experts systematically through the artifact. The experts' findings are then collected and consolidated.

30. Steering committee
A committee that supervises a project.
The source from which a requirement has been derived. Typical sources are stakeholders - documents - existing systems and observations.
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 template for the syntactic structure of a phrase that expresses an individual requirement in natural language

31. Standard
A uniform regulation for perceiving - manufacturing or executing something.
A kind of review where the author of an artifact under review walks a group of experts systematically through the artifact. The experts' findings are then collected and consolidated.
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.
The meaning of a sign or a set of signs in a language.

32. System context

33. Model
A range of relevant things (for some given matter); for example - an application domain.
A uniform regulation for perceiving - manufacturing or executing something.
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.
An abstract representation of an existing reality or a reality to be created.

34. Requirements engineering (RE)
The process of assessing whether a system satisfies all its requirements.
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
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 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

35. Fault tolerance
A spot in an artifact that is incorrectly described or crafted. Synonym: fault - bug.
The capability of a system to continue normal operation despite the presence of (hardware or software) faults. Fault tolerance may be stated as a quality requirement.
A requirements specification pertaining to a system. Frequently considered to be a synonym for requirements specification.
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

36. Review
A requirement that pertains to a quality concern that is not covered by functional requirements.
A diagrammatic representation of a class model.
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 person or organization that has a (direct or indirect) influence on a system's requirements. Indirect influence also includes situations where a person or organization is impacted by the system.

37. User
A person or organization who delivers a product or service to a customer.
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 template for the syntactic structure of a phrase that expresses an individual requirement in natural language
A person who uses the functionality provided by a system. Also called end user.

38. Baseline
A requirement that limits the solution space beyond what is necessary for meeting the given functional requirements and quality requirements.
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.
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
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

39. Finite state automaton
A state machine with atomic states.
A person who uses the functionality provided by a system. Also called end user.
A document consisting of a requirements specification. Frequently used as a synonym for requirements specification.
The process of checking whether documented requirements match the stakeholders' needs.

40. Class
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
Represents a set of objects of the same kind by describing the structure of the objects - the ways they can be manipulated and how they behave.
User.
The degree to which a requirement is expressed such that it cannot be understood differently by different people.

41. Safety
The process of checking whether documented requirements match the stakeholders' needs.
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
A characteristic property of an entity.

42. Requirements templates
A language for expressing models of a certain kind. May be textual - graphic - symbolic or some combination thereof.
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
Represents a set of objects of the same kind by describing the structure of the objects - the ways they can be manipulated and how they behave.
A blueprint for the syntactic structure of individual requirements.A phrase template is a specific requirements template for requirements written in natural language.

43. Version (of an entity)
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
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 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
The capabilities of a system as stated by its functional requirements.

44. Usability
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.
A graphic representation of an entity-relationship model. Abbreviation: ERD
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 kind of review where the author of an artifact under review walks a group of experts systematically through the artifact. The experts' findings are then collected and consolidated.

45. Kind of requirement
There are several kinds of requirements. Requirements Engineering is primarily concerned with system requirements. Beyond that - there are project requirements and process requirements. Requirements are typically sub-classified into functional requir
The ease with which a system can be transferred to another platform (while preserving its functionality). Portability may be stated as a quality requirement.
The degree to which the information contained in an artifact is probably true. In RE - correctness is frequently used as a synonym for adequacy.
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

46. Completeness (of requirements)
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
A document consisting of a requirements specification. Frequently used as a synonym for requirements specification.
1. For a single requirement: The degree to which a requirementcontains all necessary information. 2. For a requirements specification: The degree to which the specification contains all information which is necessary for developing a system that sati
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

47. Use case diagram
Traceability of a requirement back to its origin.
The meaning of a sign or a set of signs in a language.
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
A diagram type in UML that models the actors and the use cases of a system. The boundary between the actors and the use cases constitutes the system boundary.

48. Requirement (original IEEE definition)
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
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 system component to satisfy a contract - standard - specification - or other formally i
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.

49. Homonym
A model describing a system in its context.
A state machine having states that are hierarchically and/or orthogonally decomposed.
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 kind of review where the author of an artifact under review walks a group of experts systematically through the artifact. The experts' findings are then collected and consolidated.

50. 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
An intermediate or final result of system development; for example - a requirements specification.
The capability of a system to continue normal operation despite the presence of (hardware or software) faults. Fault tolerance may be stated as a quality requirement.
Cardinality.