Embedded systems software is often developed targeting only one Real-Time Operating System (RTOS) for execution. Such approach causes the software under development to hard-code its interactions with the RTOS, making it difficult to port to a different RTOS. Business opportunities are often cut short because of the lack of capacity to take fully functioning source code from one RTOS to another. The SCA addresses this constraint with the definition of an Application Environment Profile (AEP) that identifies a set of operations that can be invoked into a compliant RTOS from an SCA Application. The SCA AEP is a subset of the Portable Operating System Interface (POSIX) standard, and most RTOS nowadays comply with the POSIX SCA requirements. The impact on embedded systems software development under this approach is profound, as now complex algorithms implemented in source code can be easily moved from one RTOS to another.