Sorry I am a Mechanical Engineer. You are right that is similiar to a Domain Specific language without any Domain dependency. It is basically a simple language

Sorry I am a Mechanical Engineer. You are right that is similiar to a Domain Specific language without any Domain dependency. It is basically a simple language of assembly which can be used to build complex software as long as you have components. Regarding my analogy of a Car which i illustrated to show having assembly as part of product development is how they have handled complexity of the car manufacture and this has been followed by every industry other than software. When a specific product is development, specifically to handle complexity and productivity, other industries separate manufacturing of components from assembly and assemble to create a finished product. Here assembly and manufacture is different and can be done by separate teams/companies without any problem even when both are clearly dependent. In software this is still not the case. I have handled Outsources teams/Insourced teams for development of enterprise software and allways found it is not easy even when my projects have been very successfull. Basically it involved too tight control and sleepless nights. That is why I have to still learn and code instead of concentrating on managing projects like typical project managers. If we split software development into software assembly and software coding, i thought i should have higher order of productivity and separate domain from code. Any way i will try this on a new project and find out whether it works. May be or May be not. Anyway thanks for your comments.