When creating or maintaining a VDMT list for your team:
Below is a simple VDM-SL specification using a list to model a playlist. This illustrates the "liste" in action:
types SongId = token; Playlist = seq of SongId;functions AddSong: Playlist * SongId -> Playlist AddSong(playlist, newSong) == playlist ^ [newSong]; vdmt liste
RemoveFirst: Playlist -> Playlist RemoveFirst(playlist) == if len playlist = 0 then [] else tl playlist;
In this snippet, the Playlist is a liste — an ordered collection where songs can be appended, removed from the front, or indexed.
It is easy to confuse the VDMT Liste with other documents. Here is a quick differentiation: When creating or maintaining a VDMT list for
| Document Type | Purpose | Time Horizon | Focus | | :--- | :--- | :--- | :--- | | VDMT Liste | Validation & Verification | Post-repair or scheduled | Double-check + Compliance | | To-Do List | Task management | Daily | Productivity only | | Work Order | Authorization to spend | Financial | Budget & parts | | SOP (Standard Operating Procedure) | How to perform a task | Permanent | Methodology |
The VDMT Liste sits after the Work Order and before the final release certificate. In this snippet, the Playlist is a liste
Order the tasks logically. You cannot validate the pressure sensor before installing the hydraulic line. The VDMT Liste must respect dependency logic.