From my research in Software Factory/Domain Specific Languages/Frameworks i crystalized certain rules for assembly and the funny thing is it is simple and not d

From my research in Software Factory/Domain Specific Languages/Frameworks i crystalized certain rules for assembly and the funny thing is it is simple and not domain specific and should be implementable in any language. Rule 1 - Define a context - Give it a name Rule 2 - Add Components into that context Rule 3 - Configure those Components in that context Rule 4 - Link those Components in that context If i create a assembly framework which understand the above 4 simple rules, i should be able to assemble components into applications thereby separating assembly from coding. Assembling components implicitly gives meaning (domain) functionality to an application where the components may be generic or specific and can be rewired to give different meaning. The edge cases will be that the components are very specific for a very narrow functional area which is like a single large component. Even in these case, no component is standalone and can provide all the functionality, even specific components will need to link to generic components to provide all the desired funtionality. To prove to myself this is possible is why I created my website www.arshu.com using an assembled approach. If you visit my site and move the cursor to the top right hand site [red mark] of a page, i will tell you how many components this page uses, how many properties is being set and how many links i am creating. Thanks for the links