Design history: exploring corporate communities

A design history is a narrative involving a multitude of social groups, interpretive flexibility, and eventual stabilization of shared understanding. Design history surfaces the practices that help shape and define engagements and can increase not only our theoretical understanding of what design is, but also our capacity to realize this understanding in practice. We use a design history perspective to examine how corporate technology initiatives establish and support open source communities and the crafting of relevant design practices that enable their advancement. We foster an evolving expression of design research that treats artifacts not as stable objects to be singularly evaluated, but as evolving systems contingent on historical trajectories.

The object binary interface: C++ objects for evolvable shared class libraries

Object-oriented design and object-oriented languages support the development of independent software components such as class libraries. When using such components, versioning becomes a key issue. While various ad-hoc techniques and coding idioms have been used to provide versioning, all of these techniques have deficiencies - ambiguity, the necessity of recompilation or re-coding, or the loss of binary compatibility of programs. Components from different software vendors are versioned at different times. Maintaining compatibility between versions must be consciously engineered. New technologies such as distributed objects further complicate libraries by requiring multiple implementations of a type simultaneously in a program. This paper describes a new C++ object model called the Shared Object Model for C++ users and a new implementation model called the Object Binary Interface for C++ implementors. These techniques provide a mechanism for allowing multiple implementations of an object in a program. Early analysis of this approach has shown it to have performance broadly comparable to conventional implementations.