Contains two glossaries of commonly-used terms. Select each letter for that part of the glossary.
Contains a list of the terminology used in requirements management, systems engineering and V&V (validation and verification), including terms used in model-based systems engineering (MBSE). The definitions of some of these terms are often the subject of debate. These are our definitions. If you disagree with any of them, please contact us to discuss! This list is not exhaustive.
A B C D E F G H I N O P Q R S T U V W
E: |
|---|
|
Elicitation, Requirements |
|
The process of identifying software or system requirements from various sources through interviews, workshops, workflow and task analysis, document analysis, and other mechanisms. |
|
Entity |
|
An item in the business domain about which data will be collected and stored. |
|
Entity-Relationship Diagram |
|
An analysis model that identifies the logical relationships between pairs of entities. |
|
Essential |
|
Devoid of implementation specifics and constraints. An essential model depicts information at a conceptual level, independent of how it might be implemented in a system. |
|
Event |
|
A trigger or stimulus that takes place in a system’s environment that leads to a system response, such as a functional behaviour or a change in state. |
|
Event-Response Table |
|
A list of the external or time-triggered events that could affect the system and a description of how the system is to respond to each event. |
|
Evolutionary Prototype |
|
A fully-functional prototype created as a skeleton or an initial increment of the final product, which is fleshed out and extended incrementally as requirements become clear and ready for implementation. |
|
Exception |
|
A condition that prevents a use case from successfully concluding. The use case’s post-conditions are not reached and the actor’s goal is not satisfied. |
|
Extends Relationship |
|
A construct in which an alternative course in a use case interrupts the normal sequence of steps. The steps that the actor follows when executing the alternative course can be packaged into an extension use case that is invoked to complete the alternative. |
|
External Interface Requirement |
|
A description of an interface between a software system and a user, another software system, or a hardware device. |
|
Extreme Programming |
|
An "agile" software development methodology characterised by face-to-face collaboration between developers and an on-site customer representative, limited documentation of requirements in the form of "user stories," and rapid and frequent delivery of small increments of useful functionality. |
Contains a list of the principal terminology used in Cradle. This list is not exhaustive.