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. Adequacy (of a requirement)

2. Changeability (of an artifact)
A baseline for a set of requirements.
The degree to which an artifact enables a required modification of the artifact.
In RE: A well-argued request for changing one or more baselined requirements.
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

3. Customer requirements specification

4. Application domain
Comprises requirements validation and checking requirements for qualities such as unambiguity or comprehensibility.
Those parts of the real world that are relevant for determining the context of a system.
A tabular - systematic representation of a complex decision that depends on multiple criteria.
Documents the importance of a requirement in comparison to other requirements according to given criteria.

5. Structured analysis
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
Requirements source
1. Analysis of elicited requirements in order to understand and document them. 2. Synonym for requirements engineering.
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

6. Cardinality
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
A tabular - systematic representation of a complex decision that depends on multiple criteria.
A collection of definitions of terms that are relevant in some domain. Frequently - a glossary also contains cross-references - synonyms - homonyms - acronyms - and abbreviations.
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.

7. Goal
A desired state of affairs (that a stakeholder wants to achieve). Goals describe intentions of stakeholders. They may conflict with one another.
A person who uses the functionality provided by a system. Also called end user.
The capabilities of a system as stated by its functional 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.

8. Requirements management
The process of managing existing requirements and requirements related artifacts. Includes particularly storing - changing and tracing of requirements traceability).
A characteristic property of an entity.
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.
Documents the importance of a requirement in comparison to other requirements according to given criteria.

9. Component
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 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
Multiple occurrence of the same information or resource.
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.

10. Statechart
An intermediate or final result of system development; for example - a requirements specification.
A state machine having states that are hierarchically and/or orthogonally decomposed.
The degree to which a set of requirements is free of contradicting statements.
A description of the interactions possible between actors and a system that - when executed - provide added value. They specify a system from a user's (or other external actor's) perspective: every use case describes some functionality that the syste

11. Artifact
An intermediate or final result of system development; for example - a requirements specification.
The degree to which a requirement is expressed such that it cannot be understood differently by different people.
A spot in an artifact that is incorrectly described or crafted. Synonym: fault - bug.
A state machine with atomic states.

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

13. Functionality
The degree to which a result is achieved with minimum consumption of resources.
Requirements source
The capabilities of a system as stated by its functional requirements.
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

14. Scope (of a system)
A requirement that limits the solution space beyond what is necessary for meeting the given functional requirements and quality requirements.
The range of things that can be shaped and designed when developing a system.
In RE: A well-argued request for changing one or more baselined requirements.
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.

15. Activity diagram
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.
Requirements elicitation.
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 capability of a system to protect (a) its data and resources against unauthorized use and (b) its legitimate users against denial of service.

16. Scenario
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
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 requirement that pertains to a quality concern that is not covered by functional requirements.
A configuration that has been released for installation and use by customers.

17. Correctness
A person who - in collaboration with stakeholders - elicits - documents - validates - and manages requirements.
Multiple occurrence of the same information or resource.
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
The degree to which the information contained in an artifact is probably true. In RE - correctness is frequently used as a synonym for adequacy.

18. Unambiguity (of requirements)
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
The degree to which a requirement is expressed such that it cannot be understood differently by different people.
The part of a system's environment that is relevant for the definition as well as the understanding of the requirements of a system to be developed.
A committee that supervises a project.

19. Defect
A spot in an artifact that is incorrectly described or crafted. Synonym: fault - bug.
A (software) system that helps develop - operate and maintain systems. In RE - tools support requirements management as well as modeling - documenting - and validating requirements.
The capabilities of a system as stated by its functional requirements.
Traceability of a requirement back to its origin.

20. Requirements document
Defect
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.
A document consisting of a requirements specification. Frequently used as a synonym for requirements specification.
The degree to which a result is achieved with minimum consumption of resources.

21. Sequence diagram
A model describing a system in its context.
The capabilities of a system as stated by its functional requirements.
Multiple occurrence of the same information or resource.
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.

22. Prototype
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.
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 range of relevant things (for some given matter); for example - an application domain.
A model that has been created with the purpose of specifying requirements.

23. Safety
A model that has been created with the purpose of specifying requirements.
The source from which a requirement has been derived. Typical sources are stakeholders - documents - existing systems and observations.
A description of the interactions possible between actors and a system that - when executed - provide added value. They specify a system from a user's (or other external actor's) perspective: every use case describes some functionality that the syste
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

24. Supplier
A person or organization who delivers a product or service to a customer.
A verb characterizing the required action in a requirement written in natural language.
A diagrammatic representation of a state machine.
In RE: A well-argued request for changing one or more baselined requirements.

25. Class diagram
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.
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 diagrammatic representation of a class model.
An abstract representation of an existing reality or a reality to be created.

26. Consistency (of requirements)
An artificial language that has been created for expressing specifications.
The degree to which a set of requirements is free of contradicting statements.
The degree to which a result is achieved with minimum consumption of resources.
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

27. Class model
A description of the interactions possible between actors and a system that - when executed - provide added value. They specify a system from a user's (or other external actor's) perspective: every use case describes some functionality that the syste
A uniform regulation for perceiving - manufacturing or executing something.
A model consisting of a set of classes and relationships between them.
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.

28. Fault tolerance
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 description of the interactions possible between actors and a system that - when executed - provide added value. They specify a system from a user's (or other external actor's) perspective: every use case describes some functionality that the syste
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 formally organized endeavor for checking an artifact by a group of experts. Checking may be performed with respect to both contents and conformance.

29. Bug
State machines having states that are hierarchically and/or orthogonally decomposed.
A state machine having states that are hierarchically and/or orthogonally decomposed.
(1) process- orientation - (2) stakeholder focus - and (3) importance of risk and value considerations.
Defect

30. Portability
The ease with which a system can be transferred to another platform (while preserving its functionality). Portability may be stated as a quality requirement.
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
Those parts of the real world that are relevant for determining the context of a system.
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

31. Review
Traceability of a requirement forward to its implementation in design and code - RS stands for requirements specification.
A formally organized endeavor for checking an artifact by a group of experts. Checking may be performed with respect to both contents and conformance.
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
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

32. Language
Traceability of a requirement forward to its implementation in design and code - RS stands for requirements specification.
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 requirements specification pertaining to a software system. Abbreviation: SRS
The ease with which a system can be transferred to another platform (while preserving its functionality). Portability may be stated as a quality requirement.

33. Security
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 person who uses the functionality provided by a system. Also called end user.
The capability of a system to protect (a) its data and resources against unauthorized use and (b) its legitimate users against denial of service.
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

34. Fault
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
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.
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.
Defect.

35. Feature
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
Those parts of the real world that are relevant for determining the context of a system.
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.
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.

36. Validation (of requirements)

37. Decision table
A tabular - systematic representation of a complex decision that depends on multiple criteria.
A baseline for a set of requirements.
A requirement that limits the solution space beyond what is necessary for meeting the given functional requirements and quality requirements.
A configuration that has been released for installation and use by customers.

38. Compliance
An intermediate or final result of system development; for example - a requirements specification.
A configuration that has been released for installation and use by customers.
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
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

39. Context

40. Requirements model
A description of the interactions possible between actors and a system that - when executed - provide added value. They specify a system from a user's (or other external actor's) perspective: every use case describes some functionality that the syste
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 that has been created with the purpose of specifying requirements.
The meaning of a sign or a set of signs in a language.

41. Process verb
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 degree to which the information contained in an artifact is probably true. In RE - correctness is frequently used as a synonym for adequacy.
A verb characterizing the required action in a requirement written in natural language.
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.

42. Behavior Model
A verb characterizing the required action in a requirement written in natural language.
A model describing the behavior of a system or component - e.g. - by a state machine.
Traceability of a requirement forward to its implementation in design and code - RS stands for requirements specification.
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

43. State-transition diagram
Those parts of the real world that are relevant for determining the context of a system.
The meaning of a sign or a set of signs in a language.
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 diagrammatic representation of a state machine.

44. User
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 person who uses the functionality provided by a system. Also called end user.
The process of managing existing requirements and requirements related artifacts. Includes particularly storing - changing and tracing of requirements traceability).
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.

45. Verifiability (of requirements)
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.
The part of a system's environment that is relevant for the definition as well as the understanding of the requirements of a system to be developed.
A committee that supervises a project.
The rules for constructing structured signs in a language.

46. Acceptance test
The degree to which a requirements specification conforms to regulations given in some standard.
A test that assesses whether a system satisfies all its requirements.
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
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

47. Homonym
A model describing a system in its context.
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 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 blueprint for the syntactic structure of individual requirements.A phrase template is a specific requirements template for requirements written in natural language.

48. Model
An abstract representation of an existing reality or a reality to be created.
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
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 person who uses the functionality provided by a system. Also called end user.

49. Completeness (of requirements)
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.
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
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 template for the syntactic structure of a phrase that expresses an individual requirement in natural language

50. Constraint
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 language for expressing models of a certain kind. May be textual - graphic - symbolic or some combination thereof.
User.
A requirement that limits the solution space beyond what is necessary for meeting the given functional requirements and quality requirements.