Hi all,

This is the final planning for the SrrTrains v0.01 project (nothing new so far):

I added the key words *TODO11*, *TODO12* and *TODO* into the Concepts’ Descriptions to have a feeling of

1. What has already been done – no tagging
2. What is planned for step 0033.11 – tagged by *TODO11*
3. What is planned for step 0033.12 – tagged by *TODO12*
4. What has not been planned yet – tagged by *TODO*

Please find the updated Concepts’ Descriptions here:

001_Glossary…*TODO12*………overview of the concepts and some terms
011_NamingRules……………..using names in an SMS; the MMF paradigm
012_FrameAndModules………….the frame and the modules
013_ModelsAndObjects…………astral, bound and unbound objects
014_ConsoleInterface…………influencing an SMS from a Command Line Interface
051_Extensibility……………extending the software (e.g. for road vehicles)
052_UnboundModels.*TODO11*……creating and deleting models at runtime
053_Handover.*TODO11*………..unbound models changing modules dynamically
054_MovingModules.*TODO11*……including modules as parts of a model (eMMF)
099_PerformanceConsiderations…is performance an issue?

The Overall Planning (i.e. Prophecy)

STEP0033.11 / architectural features

unbound models, handover, moving modules with experimental vehicles (v=const)
not before 2020

STEP0033.12 / railway kinetics (v not equal const)

with basic vehicles
not before 2021

LATER

1. Rebase to some “SMS”/”DIGITS” environment
2. additional railway features
   1. coupling and collisions
   2. 1900’s Interlocking

Have a nice week
Yours Christoph