System Document Register - modelint/shlaer-mellor-metamodel GitHub Wiki

There are three core models necessary to define a fully executable system: Class, State, and Action and we have a separate document register for each.

But we also need yet another grouping to represent a delivered system as a whole. Here we focus on how Domains themselves are organized as well as how Domains are wired together in the context of a delivered System.

Here are all the System level subsystems:

Technical Documents

#	Title	Author	Creation	Modification	Version	Native	Other
1	Domain Subsystem Class Model	Leon Starr	2006-8-20	2022-5-18	2.4.1	Flatland	1-19
2	Bridge Subsystem Class Model	Leon Starr	2022-6-4	2022-6-4	0.4.2	Flatland	1300-1399

Technical Notes

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	Half Table Study: Animation Example	Leon Starr	2022-6-4	2022-7-1	0.3.1	Wiki
2	Half Table Study: Elevator Case Study	Leon Starr	2022-7-1	2022-7-5	0.2.0	Wiki
3	Half Table Study: Signal IO MTC Example	Leon Starr	2022-7-5	2022-7-5	0.1.0 in progress	Wiki
10	Class to Class Join Point	Leon Starr	2022-7-5	2022-7-5	0.1.0 in progress	Wiki