I just came out of a design meeting and had a question posed to me about where I got one of my ideas about how to structure some .dlls of a project we are building. To be honest I have no idea where this "idea" came from it just seemed like natural knowledge to me. However it would useful if I could back up these opinions with some documented analysis.
Does anyone know of any resources that explicity discuss different mechanisms for structuring assemblies/modules/source?
UPDATE:
Well the idea was nothing special. We were discussing an abstraction layer for some hardware so the "app" that consumes these services could be (sort of) platform independant. Previously we've had an interfaces .dll that declares the interfaces the app requires and an implementation .dll that implements them for the one platform we've had thus far. Now we have two platforms but they are very similar. To prevent the interfaces .dll from being polluted or some hideous scenario where the implementations reference one another I merely suggested we create another .dll that sits between the interfaces and specificplatform.dlls where common abstract implementations can live.