Requirements Engineering Vocabulary

Flashcards about key terms and concepts from the Requirements Engineering lecture notes.

Vision

Defines an intended change to a current reality, is brief and precise, guides requirement definition and system development, states a goal, is the basis for decisions, and justifies expenses.

System Context

The part of the requirements engineering context in which the system to be developed is operating/embedded.

Development Context

The part of the requirements engineering context in which the system is being developed.

Subject facet

Comprises system context objects about which information is represented in the system or which influence or constrain the representation of information represented in the system.

Usage facet

Comprises all system context objects (people and/or systems) which directly or indirectly interact with the system or which influence or benefit from the usage of the system.

IT system facet

Comprises all system context objects of the technical and operational environment in which the system is going to be deployed in or which influence or constraint the deployment of the system.

Elicitation

Identify relevant requirements sources, elicit existing requirements from the identified sources, and develop new and innovative requirements.

Negotiation

Identify conflicts, analyse the cause of each conflict, resolve the conflicts by means of appropriate strategies, and document conflict resolution and their rationale.

Documentation

Document relevant requirements information according to the defined documentation guidelines, specify requirements according to the defined specification guidelines and Choose documentation formats and notations which fit the stakeholder needs, and are defined for the project.

Goal

Describes a high level objective of one or more stakeholders about a property of the system to be developed or the development project.

Scenario

Describes a concrete example of satisfying or failing to satisfy a goal (or set of goals).

Data Perspective

Considers the static data structures; it defines data types, attributes, and relationships between data types.

Functional Perspective

Considers the manipulation of data by system functions; it defines the transformation of inputs by functions into outputs.

Behavioral Perspective

Considers the system behavior; it defines the reactions to external stimuli in the form of permitted states, transitions, and outputs.

Validation

Aims at detecting defects in requirements by validating the artefacts with regard to the content, the documentation and the agreement dimensions and checking the fulfilment of validation criteria.

Management

Management of the requirements artifacts throughout the system lifecycle, Management of the core activities and Management of the context