-
Notifications
You must be signed in to change notification settings - Fork 0
Document Register
All models, technical notes, background documents and other documentation are organized in this document register.
For tracking and reference purposes, every document has a unique document identifier. This identifier remains valid regardless of configuration management system organization, path name or web location.
To make the table easy to read in this wiki we show only the document number (#) and not the full document id.
The prefix for all documents in the Dataflow Semantics Subsystem is: mint.mx.<doc_type>.<num>
In Executable UML we split a domain into one or more subsystems. The Data Flow Semantics domain is fairly small so it is represented by a single subsystem with the same name.
So, in the title block of a Technical Note document type, the full document id might be: mint.mx.td.2
Informal notes, anything from a photo of a napkin or whiteboard sketch to a neatly formatted pdf is included here. These notes describe key concepts, challenges, issues and anything else contributing to the construction of the more formal Technical Documents.
| # | Title | Author | Creation | Modification | Version | Native |
|---|---|---|---|---|---|---|
| 1 | Simple elevator scenarios | Leon Starr | 2025-4-6 | 2026-1-21 | 0.2 | |
| 2 | Relational variable management | Leon Starr | 2026-3-15 | 2026-3-15 | 0.1 | Wiki |
Documents under formal review. Typically these are incorporated into code artifacts.
For class models, the Other column shows the relationship numbering range.
| # | Title | Author | Creation | Modification | Version | Native | Other |
|---|---|---|---|---|---|---|---|
| 1 | Model debugger class model | Leon Starr | 2026-2-9 | 2026-2-13 | 0.2.0 | Flatland | 1-99 |
Copyright © 2025-2026, Leon Starr at Model Integration, LLC under the MIT Open Source License