Restricting the scope of task classes targeted to MRP, MRPII, ERP and CRM, intensive efforts in standardization, rich experience and many solutions delivered by the Team result in passing through the following evolution phases of software manufacturing process automation (Fig.3).

Fig.3. Software manufacturing process automation levels

The above automation levels represent respective evolution phases for the corporate information system (CIS) manufacturing process.
The first evolution phase is typical of writing code, which fully describes both logic of program objects interaction and business logic of the CIS stipulating for a practically brand-new code creation each time a new system is manufactured. The manufacturing cycle here includes modeling, design and coding. As critical mass of source code accumulates after several projects completed, the possibility to create system of design patterns emerges. These are parameterized program solutions (PPS) to encapsulate basic solving logic for specific design tasks and essentially are the designer's distilled coding experience.

Creation of the PPS system (PPSS) signals transition to second evolution phase. This automation level is noted for substitution of plain coding with configuration of PPSS to deliver custom solutions. Resulting from PPSS configuration process is a PPSS custom operation logic or metalogic (a "logic operation" logic) specific to each custom solution delivered. At this step the PPSS can have a certain configuration interface thus becoming a Metalogic Interpreter able to interpret (execute) metalogic on the fly. This approach is advantageous both for design (several solution prototypes can be tested simultaneously, e.g. - Tcl/Tk environment for Unix-clone OSs) and system's architecture (this enables introduction of browser technology). The manufacturing cycle here includes modeling and design turning into configuring of PPSS using metalogic language (e.g. XML) with shortening of processing terms gained through elimination of plain coding. Designer's experience grades new at this point - now it is a metalogic coding experience.
As critical mass of metalogic code accumulates, the possibility to create system of modeling patterns emerges. These are now parameterized configuration solutions (PCS) to encapsulate basic PPSS configuration logic for specific design tasks.

Creation of the PCS system (PCSS) signals transition to third evolution phase. This automation level is noted for substitution of PPSS configuration with PCSS configuration to deliver custom solutions with certain modeling language (e.g. UML) providing PCSS configuration interface. A resulting model is then processed by Model Interpreter to finally produce metalogic code able to execute in Metalogic Interpreter. Such technique reduces manufacturing process to only modeling with further automatic model conversion into finished ready to ship solution.

The above evolution approach is practically realizable with restricted scope of tasks targeted by second and third automation levels as it is up to designer to provide maximal possible amount of PPSS / PCSS building blocks thus setting limit to the potential functionality of the system manufactured. Restrictions to the task classes targeted are defined in the means of language structures complexity for metalogic language (second automation level) and / or modeling language (third automation level). They are accordingly enforced through ability to process widest possible range of language structures implemented in Model Interpreter and Metalogic Interpreter engines.

Technological solutions

Based on the above described matter the principles of PPSS and PCSS design and interaction are of key importance for successful automation of CIS manufacturing process. The art of design here is to develop flexible and viable PPS and PCS systems featuring most complete set of functionality for target task classes. Speaking of the Team's technological solutions inspired by these considerations, it is necessary to declare the following issues: