Wednesday, September 28, 2011

Multiple modes of convergence on Transition Chain between Discrepancy Values and Total Breakdown



A time interval between appearances of Discrepancy Values Mode and occurrences of Total Breakdown Mode are varied in accordance with the System Property. A time interval between the parameters generation of Discrepancy Values and the Total Breakdown can be between 1 second to 20 years. Multiple modes of convergence on Transition Chain are invisible for internal and external controllers. The number of moments in Transition Chain determines sometimes obscure deep divergence from Standard Values.

Evolutionary path of system performances modify by internal and external forces. Modifications cause diversion on Modes Property related to Evolutionary Path of system performances.
The above figure shows patterns and multiple modes of convergence on Transition Chain for Evolutionary Path of system performances.

Biological systems and non-biological systems develop gradually on axel of Common Standard Evolutionary path of system performances. Regularity in performances with parameter consistency indicates stability and Harmonic Balance in system framework (Mode 1 or M1).

A Resource Property and Performance Attributes modify and tackle by Unknown Entities; therefore, system can override its maximum potential resolution and compatibility. Discrepancy Values appear in Resource Property and Performance Attributes. At this juncture, system divert from the route of Common Evolutionary Path to (Mode 2 or M 2).

Discrepancy values in Resources Property and performance attributes generate Invisible Entities, which modify Processes and Normal Values of Balance Performances (Mode 3 or M3).

Instance parameters on Processes and Abnormal Value Levels of Balance Performances modify system environments. Modifications can cause billion Side-Effects. Three Side-Effects illustrate on above figure (M 4-0), (M 4-1), and (M 4-2). Mode (4-0) executes parameter complexity on several channels. Presumptive Side-Effects (M 4- 1) and (M 4-2) are ignored in class path setting in the above figure.

Allocation of a single Side-Effect on system framework can develop wide range of structures with Complexity Mapping Patterns (Mode 5 or M5).

Complexity Mapping Patterns hamper Progress and Pathophysiological Mechanisms in system performances. A serious Crash can encounter and disable System Restore Functions (Mode 6 or M6).

Disability in System Restore Functions can jeopardize entire system and instance thread storages. System performance can approach for Obsessive Compulsive Disorder. System would suppress process Output; however, process Input may be intact.
At this juncture, system has potential to congregate overriding values in entire layers through process Input (Mode 7 or M7).  System has not any potential to congregate overriding values in entire layers through process Input. System still remains inactive on suspended domain (Mode 8 or M8). System cannot reboot and enter to Safe Mode (Mode 7 or M7). Rational Suboptimization fails to create recovery key on system framework.

Observation:

Suboptimization always transforms Current Mode Setting to Previous Mode Setting. For example, Suboptimization on (Mode 7) alters System Status to (Mode 6); however, rational suboptimization cannot alter System Status from (Mode 8) to (Mode 6). Systems developers must approach to higher levels of awareness in System Status when system locates between Discrepancy Values Mode and Total Breakdown Mode.
The Rational suboptimization implies to rational test approach without entangling other subcomponents in the Life-cycle Procedure.

No comments: