A.   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

B.   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

C.   The rules for constructing structured signs in a language.

A.   A person or organization who receives a product or service. Also see stakeholder.

B.   (1) process- orientation - (2) stakeholder focus - and (3) importance of risk and value considerations.

D.   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.

A.   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.

B.   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

D.   Comprises requirements validation and checking requirements for qualities such as unambiguity or comprehensibility.

B.   An intermediate or final result of system development; for example - a requirements specification.

C.   The meaning of a sign or a set of signs in a language.

D.   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.   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

B.   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.

C.   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

B.   A model consisting of a set of classes and relationships between them.

C.   Comprises requirements validation and checking requirements for qualities such as unambiguity or comprehensibility.

D.   A person who uses the functionality provided by a system. Also called end user.

A.   Documents the importance of a requirement in comparison to other requirements according to given criteria.

B.   A blueprint for the syntactic structure of individual requirements.A phrase template is a specific requirements template for requirements written in natural language.

D.   (1) process- orientation - (2) stakeholder focus - and (3) importance of risk and value considerations.

A.   A model consisting of a set of classes and relationships between them.

B.   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

D.   (1) process- orientation - (2) stakeholder focus - and (3) importance of risk and value considerations.

A.   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

C.   An artificial language that has been created for expressing specifications.

D.   Defect

B.   Defect.

C.   The process of managing existing requirements and requirements related artifacts. Includes particularly storing - changing and tracing of requirements traceability).

D.   A requirement that pertains to a quality concern that is not covered by functional requirements.

B.   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

C.   The source from which a requirement has been derived. Typical sources are stakeholders - documents - existing systems and observations.

D.   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.   The degree to which a requirement is expressed such that it cannot be understood differently by different people.

B.   Defect.

D.   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

B.   Traceability of a requirement back to its origin.

C.   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

D.   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.   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.

B.   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

D.   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.

B.   1. Analysis of elicited requirements in order to understand and document them. 2. Synonym for requirements engineering.

C.   A diagrammatic representation of a state machine.

D.   A spot in an artifact that is incorrectly described or crafted. Synonym: fault - bug.

B.   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.

C.   A characteristic property of an entity.

D.   An artificial language that has been created for expressing specifications.

A.   A graphic representation of an entity-relationship model. Abbreviation: ERD

C.   The process of checking whether documented requirements match the stakeholders' needs.

D.   A diagrammatic representation of a state machine.

A.   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

B.   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.

C.   Requirements source

A.   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

C.   The process of managing existing requirements and requirements related artifacts. Includes particularly storing - changing and tracing of requirements traceability).

D.   1. Analysis of elicited requirements in order to understand and document them. 2. Synonym for requirements engineering.

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.

B.   A spot in an artifact that is incorrectly described or crafted. Synonym: fault - bug.

D.   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.

A.   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

B.   A person who - in collaboration with stakeholders - elicits - documents - validates - and manages requirements.

C.   In RE: A well-argued request for changing one or more baselined requirements.

A.   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.

B.   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

C.   Requirements elicitation.

A.   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

C.   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

D.   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

A.   The capability of a system to protect (a) its data and resources against unauthorized use and (b) its legitimate users against denial of service.

B.   A requirement that limits the solution space beyond what is necessary for meeting the given functional requirements and quality requirements.

D.   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.   A person or organization who receives a product or service. Also see stakeholder.

B.   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.

D.   A template for the syntactic structure of a phrase that expresses an individual requirement in natural language

B.   An intermediate or final result of system development; for example - a requirements specification.

C.   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

D.   A language for expressing models of a certain kind. May be textual - graphic - symbolic or some combination thereof.

B.   A state machine having states that are hierarchically and/or orthogonally decomposed.

C.   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.

D.   User.

A.   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.

B.   A desired state of affairs (that a stakeholder wants to achieve). Goals describe intentions of stakeholders. They may conflict with one another.

C.   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

B.   Comprises requirements validation and checking requirements for qualities such as unambiguity or comprehensibility.

C.   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

D.   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.

B.   A state machine with atomic states.

C.   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

D.   An intermediate or final result of system development; for example - a requirements specification.