Composability, a system design principle, is mainly concerned with the inter-workings and relationships among system components. The keyword "recombinant" is often used to further elucidate composition, and means that a sufficiently composable system allows components to be combined and assembled in varying combinations to satisfy user requirements. Self-containment, the ability of a component to be deployed independently, and statelessness are also key properties of a ?composable' component. Composability thus seems to underlie the concept of ease of integration of systems. An example of a composable product would be an off-the-shelf program that can be integrated into a larger system via a simple configuration file or script [1]. Ideally, in such a case, existing formats would not require vast infrastructure changes to accommodate the new, off-the-shelf component. In many modern cases, however, great reengineering efforts have been required to do just that. Composability therein demonstrates its importance: a truly composable component or system may be integrated fully and seamlessly with another application with minimal reengineering effort.
According to IBM, composability is the "ultimate security goal" for designing cryptographic protocols as they guarantee security even in the event of mixed or arbitrary protocols. Truly composable mixed or arbitrary protocols should integrate seamlessly, allowing a central point of security administration in cryptographic systems. In "Universal Composability," IBM makes the assertion that a general series of steps may be taken to achieve Universal Composability, a proposition that is significant for its boldness. ...