Building application by assembling interchangeable parts

In the software engineering research area, there is a lot of talk about building application by assembling pre-fabricated interchangeable parts.Unfortunately, software researchers may never realize this goal, since software applications are so unique.Furthermore, the applications need to be constantly adoptable to changing needs, how one could find pre-fabricated parts for not yet known future needs?Let me outline a process to build applications by assembling interchangeable parts. As I said, we cannot use pre-fabricated interchangeable parts. So, I will be using “dynamically-configurable-interchangeable” components.The main requirements for the ‘interchangeable-parts’ are that, they must be: (i) Easy to replace or interchangeable by a new component in minutes,(ii) They must allow independent and easy reconfiguration or refinement to meet to evolving business needs.So, what are the pieces we must invent to accomplish that goal?The product makers assemble pre-fabricated interchangeable parts to build products such as computers and automobiles. The problem of assembling interchangeable-parts to build software-applications is not that much different from assembling products, for example automobiles. The only fundamental difference may be generally summarized as:The automakers need to build assembly line to make just one model car (e.g. either Camry or Accord).The software-makers need to build a universal assembly line to dynamically make any model car at real-time, based on user preferences:http://www.cbsdf.com/technologies/software-irony.htmThere are few issues we must address, to setup the supply chain for the software application:The method to assemble pre-fabricated interchangeable-components:http://www.cbsdf.com/Newbies/CBSE-Basics.htmThe process to assemble ‘dynamically-customizable-interchangeable-parts’ to build larger and larger components and finally the application:http://www.cbsdf.com/technologies/LC-CBSD.htmPioneer-soft is planning to create reusable Ajax-GUI-API, which are capable of generating XAML and/or SVG code-blocks for the ‘interchangeable-components’. The ‘developer guide’ to use the reusable GUI-Classes:http://www.cbsdf.com/developer-guide.htmAn example to build a reusable GUI-Class for Air-traffic-control system application:http://www.cbsdf.com/Newbies/Flight-main.htmA simple example for the Component-factory and assembling the components:http://www.cbsdf.com/technologies/misc-docs/CF-Goog-Charts.htmAn example for building component hierarchy:http://www.cbsdf.com/ps_blog/super-distribution-old.htmThis pattern may be used for building graphics intensive online applications.Best Regards,Raju