Many requirements documents are described in a linear manner, which makes for “interesting times” when the system is highly concurrent and multi-threaded. Any attempt to take implementation of concurrency and distribution into account when expressing requirements can easily lead to premature design and difficulties in retargeting the application to a different environment. This paper describes an approach to capturing concurrency in requirements as models and providing rules to sequence them in an implementation on an RTOS.