A typical VDMT operates on the intersection of Likelihood and Impact, often modifying the raw CVSS score. The decision logic usually looks like this:
The Output:
Below is a simple VDM-SL specification using a list to model a playlist. This illustrates the "liste" in action: vdmt liste
types SongId = token; Playlist = seq of SongId;functions AddSong: Playlist * SongId -> Playlist AddSong(playlist, newSong) == playlist ^ [newSong];
RemoveFirst: Playlist -> Playlist RemoveFirst(playlist) == if len playlist = 0 then [] else tl playlist;A typical VDMT operates on the intersection of
In this snippet, the Playlist is a liste — an ordered collection where songs can be appended, removed from the front, or indexed. The Output: Below is a simple VDM-SL specification
In VDM-SL (VDM Specification Language), a list is a finite ordered sequence of elements. Unlike sets, which ignore order and multiplicity, lists preserve both. Unlike tuples, lists are homogeneous (all elements must be of the same type) and can be of arbitrary, dynamic length. A list of integers is written as [3, 1, 4, 1, 5].
The "liste" in VDM is a powerful, built-in type with a rich set of operators: