IREB_CPRE_Glossary Flashcards
1
Q
Acceptance
A
The process of assessing whether a system satisfies all its requirements
2
Q
Acceptance test
A
A test that assesses whether a system satisfies all its requirements.
3
Q
Activity diagram
A
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.
4
Q
Actor
A
- Generally in RE: A person, a system or a technical device in the context of a system that interacts with the system.
- Especially in goal-oriented RE: a person, a system or a technical device that may act and process information in order to achieve some goals.
5
Q
Adequacy (of a requirement)
A
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).
6
Q
Application domain
A
Those parts of the real world that are relevant for determining the context of a system.
7
Q
Artifact
A
An intermediate or final result of system development; for example, a requirements specification.
8
Q
Attribute
A
A characteristic property of an entity.
9
Q
Baseline
A
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.
10
Q
Behavior model
A
A model describing the behavior of a system or component, e.g., by a state machine.
11
Q
Bug
A
A spot in an artifact that is incorrectly described or crafted. Synonyms: for Defect, Fault.
12
Q
Cardinality
A
- In modeling: The minimum and maximum number of objects in a relationship. In UML, the term multiplicity is used for cardinality.
- In mathematics: The number of elements in a set.
Synonym: Multiplicity
13
Q
Change control board
A
A committee of client and supplier representatives that decides on change requests.
Abbreviation: CCB
14
Q
Change request
A
In RE: A well-argued request for changing one or more baselined requirements.
15
Q
Changeability (of an artifact)
A
The degree to which an artifact enables a required modification of the artifact.
16
Q
Checking (requirements)
A
Comprises requirements validation and checking requirements for qualities such as unambiguity or comprehensibility.
Note that some sources define validation broader and consider the terms checking and validation to be synonyms.
17
Q
Class
A
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.
18
Q
Class diagram
A
A diagrammatic representation of a class model.
19
Q
Class model
A
A model consisting of a set of classes and relationships between them.
20
Q
Completeness (of requirements)
A
- For a single requirement: The degree to which a requirement contains all necessary information
- For a requirements specification: The degree to which the specification contains all information which is necessary for developing a system that satisfies the stakeholders’ desires and needs.
21
Q
Compliance
A
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 compliance can only be ensured systematically if compliance checking already starts with the requirements.
22
Q
Component
A
- In general: A delimitable part of a system.
- In software architecture: An encapsulated set of coherent objects or classes that jointly provide a service.
Note: When viewed in isolation, a component is a system by itself.
23
Q
Configuration
A
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.
24
Q
Conformity (of requirements)
A
The degree to which a requirements specification conforms to regulations given in some standard.
25
Consistency (of requirements)
The degree to which a set of ?requirements is free of contradicting statements.
26
Constraint
A requirement that limits the solution space beyond what is necessary for meeting the given functional requirements and quality requirements.
27
Context
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 meaning is also called the system context.
28
Context boundary
Boundary between the context of a system and those parts of the application domain that are irrelevant for the system and its requirements.
The context boundary separates the relevant part of the environment of a system to be developed from the irrelevant part, i.e., the part that does not influence the system to be developed and, thus, does not have to be considered during requirements engineering.
29
Context diagram
1. A diagrammatic representation of a context model.
| 2. In Structured Analysis, the context diagram is the root of the dataflow diagram hierarchy.
30
Context model
A model describing a system in its context.
31
Correctness
The degree to which the information contained in an artifact is provably true.
In RE, correctness is frequently used as a synonym for adequacy.
32
Customer
A person or organization who receives a product or service.
| Also see stakeholder.
33
Customer requirements specification
A coarse description of the required capabilities of a system from the customer’s perspective.
Usually supplied by the customer.
34
Dataflow diagram
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 held in data stores and then produce new data flows which may be intermediate results that trigger other processes or final results that leave the system.
35
Decision table
A tabular, systematic representation of a complex decision that depends on multiple criteria.
36
Defect
A spot in an artifact that is incorrectly described or crafted.
Synonym: fault, bug
37
Domain
A range of relevant things (for some given matter); for example, an application domain.
38
Effectiveness
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.
39
Efficiency
The degree to which a result is achieved with minimum consumption of resources.
40
Elicitation (of requirements)
The process of seeking, capturing and consolidating requirements from available requirements sources. May include the re-construction or creation of requirements.
Synonym: Requirements discovery, Requirements elicitation
41
End user
A person who uses the functionality provided by a system.
| Synonym: User.
42
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 and does not depend on another object.
43
Entity-relationship diagram
A graphic representation of an entity-relationship model.
| Abbreviation: ERD
44
Entity-relationship model
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
45
Error
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.
46
Fault
A spot in an artifact that is incorrectly described or crafted.
Synonym: Bug, Defect
47
Fault Tolerance
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.
48
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 characteristics.
49
Functional requirement
A requirement concerning a result of behavior that shall be provided by a function of a system (or of a component or service).
50
Functionality
The capabilities of a system as stated by its functional requirements.
51
Glossary
A collection of definitions of terms that are relevant in some domain. Frequently, a glossary also contains cross-references, ?synonyms, homonyms, acronyms, and abbreviations.
52
Goal
A desired state of affairs (that a stakeholder wants to achieve).
Goals describe intentions of stakeholders. They may conflict with one another.
53
Goal model
A model that represents the goals of something as an ordered structure of sub-goals.
54
Homonym
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.
55
Inspection
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.
56
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 requirements, quality requirements and constraints. The latter two are also called non-functional requirements.
57
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.
58
Maintainability
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.
59
Model
An abstract representation of an existing reality or a reality to be created.
This definition covers the most frequent case in requirements engineering, but is a bit narrow. More generally speaking, a model is an abstract representation of an existing entity or an entity to be created, where entity denotes any part of reality or any other conceivable set of elements or phenomena, including other models. With respect to a model, the entity is called the original.
In Requirements Engineering, requirements can be specified by models.
Note that entity in this definition is used in its general meaning which is different from the one used in Entity-relationship models.
60
Modeling language
A language for expressing models of a certain kind. May be textual, graphic, symbolic or some combination thereof.
61
Multiplicity
In UML, the term multiplicity is used for cardinality.: The minimum and maximum number of objects in a relationship.
Synonym: Cardinality
62
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: Extra-functional requirement
63
Performance requirement
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 of its own.
64
Phrase template
A template for the syntactic structure of a phrase that expresses an individual requirement in natural language.
Example: 'As a [user], I want [function], so that [value]'
65
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.
66
Priority (of a requirement)
Documents the importance of a requirement in comparison to other requirements according to given criteria.
67
Process verb
A verb characterizing the required action in a requirement written in natural language.
68
Prototype
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 means for requirements elicitation and validation.
69
Quality
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 property of an entity which is inherent to the entity and has not been assigned explicitly.
This is the notion of quality that is generally used in industry. Note that quality in this definition just means fitness for intended use, as stated in the requirements. This is in contrast to the colloquial notion of quality which is typically connoted with goodness or excellence.
70
Quality requirement
A requirement that pertains to a quality concern that is not covered by functional requirements.
71
Redundancy
Multiple occurrence of the same information or resource.
72
Release
A configuration that has been released for installation and use by customers.
73
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.
74
Requirement
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 imposed documents.
3. A documented representation of a condition or capability as in (1) or (2).
Note: The definition above is the classic one from IEEE Std 610.12 of 1990.
Alternatively, we also give a more 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.
75
Requirements analysis
1. Analysis of elicited requirements in order to understand and document them.
2. Synonym for requirements engineering.
76
Requirements baseline
A baseline for a set of requirements.
77
Requirements discovery
The process of seeking, capturing and consolidating requirements from available requirements sources. May include the re-construction or creation of requirements.
Synonym: Requirements elicitation.
78
Requirements document
A document consisting of a requirements specification.
| Frequently used as a synonym for requirements specification.
79
Requirements elicitation
The process of seeking, capturing and consolidating requirements from available requirements sources. May include the re-construction or creation of requirements.
Synonym: Requirements discovery
80
Requirements engineer
A person who – in collaboration with stakeholders – elicits, documents, validates, and manages requirements.
81
Requirements Engineering
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 according to given standards, and managing them systematically,
(2) Understanding and documenting the stakeholders’ desires and needs,
(3) Specifying and managing requirements to minimize the risk of delivering a system that does not meet the stakeholders’ desires and needs.
Abbreviation: RE
Note: All three goals address important facets of RE: (1) process-orientation, (2) stakeholder focus, and (3) importance of risk and value considerations.
82
Requirements management
The process of managing existing requirements and requirements related artifacts. Includes particularly storing, changing and tracing of requirements (traceability).
83
Requirements model
A model that has been created with the purpose of specifying requirements.
84
Requirements source
The source from which a requirement has been derived. Typical sources are stakeholders, documents, existing systems and observations.
Synonym: Source (of a Requirement)
85
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 system requirements specification or software requirements specification (written by the supplier).
Requirements specification may also denote the activity of specifying requirements.
86
Requirements template
A blueprint for the syntactic structure of individual requirements.
A phrase template is a specific requirements template for requirements written in natural language.
87
Review
A formally organized endeavor for checking an artifact by a group of experts.
Checking may be performed with respect to both contents and conformance.
88
Risk
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.
89
Safety
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 requirements.
90
Scenario
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 scenario) or a set of potential sequences (type scenario, use case).
3. In UML: An execution trace of a use case.
91
Scope (of a system)
The range of things that can be shaped and designed when developing a system.
92
Security
The capability of a system to protect (a) its data and resources against unauthorized use and (b) its legitimate users against denial of service.
93
Semantics
The meaning of a sign or a set of signs in a language.
94
Semi-formal
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 defined only.
95
Sequence 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.
96
Software requirements specification
A requirements specification pertaining to a software system.
Abbreviation: SRS
97
Source (of a requirement)
The source from which a requirement has been derived. Typical sources are stakeholders, documents, existing systems and observations.
Synonym: Requirements source
98
Specification
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 specification).
99
Specification language
An artificial language that has been created for expressing specifications.
100
Stakeholder
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.
101
Standard
A uniform regulation for perceiving, manufacturing or executing something.
102
State machine
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.
Related terms:
- A state machine with atomic states is called a finite state automaton.
- State machines having states that are hierarchically and/or orthogonally decomposed are called statecharts.
103
State-transition diagram
A diagrammatic representation of a state machine.
104
Statechart
A state machine having states that are hierarchically and/or orthogonally decomposed.
105
Steering committee
A committee that supervises a project.
106
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 outgoing data flows.
107
Supplier
A person or organization who delivers a product or service to a customer.
108
Synonym
A word having the same meaning as another word.
109
Syntax
The rules for constructing structured signs in a language.
110
System
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 systems consisting of software components, technical elements (computing hardware, devices, sensors,...) and organizational elements (persons, positions, business processes,...).
Note that a system may comprise other systems. Therefore, components or services of a system are also considered to be systems.
111
System boundary
The boundary between a system and its surrounding context.
The system boundary 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 environment that cannot be changed or modified by the development process.
112
System context
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.
113
System requirement
A requirement pertaining to a system or to a component of a system.
114
System require-ments specification
A requirements specification pertaining to a system.
| Frequently considered to be a synonym for requirements specification.
115
Tool (in software engineering)
A (software) system that helps develop, operate and maintain systems.
In RE, tools support requirements management as well as modeling, documenting, and validating requirements.
116
Traceability (of requirements)
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.
Traceability of a requirement back to its origin is also called pre-RS traceability. Conversely, traceability of a requirement forward to its implementation in design and code is also called post-RS traceability. RS stands for requirements specification.
Sometimes, traceability to the rationale of a requirement is considered to be a traceability category of its own.
117
UML
Abbreviation for Unified Modeling Language, a standardized language for modeling problems or solutions.
118
Unambiguity (of requirements)
The degree to which a requirement is expressed such that it cannot be understood differently by different people.
119
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.
120
Use case
A description of the interactions possible between actors and a system that, when executed, provide added value.
Use cases specify a system from a user’s (or other external actor’s) perspective: every use case describes some functionality that the system must provide for the actors involved in the use case.
121
Use case diagram
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.
122
User
A person who uses the functionality provided by a system. Also called end user.
123
Validation (of requirements)
The process of checking whether documented requirements match the stakeholders’ needs.
Note that some sources define requirements validation broader by also including checking requirements for qualities such as unambiguity or comprehensibility, thus considering the terms validation and checking to be synonyms.
124
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.
125
Version (of an entity)
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.
126
View
An excerpt from an artifact, containing only those parts one is currently interested in.
A view can abstract or aggregate parts of the artifact.
127
Viewpoint
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 viewpoints such as a security viewpoint.
Note that this definition is somewhat different from the definition of an architectural viewpoint in the international standard ISO/IEC42010: 2007 (IEEE Std 1471-2000).
128
Walkthrough
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.
129
CCB
Change Control Board
130
CPRE
Certified Professional for Requirements Engineering
131
ER
Entity-Relationship
132
ERD
Entity-Relationship Diagram
133
ERM
Entity-Relationship Model
134
IREB
International Requirements Engineering Board
135
RE
Requirements Engineering
136
SRS
Software Requirements Specification
137
UML
Unified Modeling Language
