Thursday, July 24, 2008

Invisible entities in system's scenario

Multilevel performance analysis of scenarios can illustrate those performance scenarios after operating system failure would create illusions for observers. Illusions show up originally through side effects by complicated multiple processes in system environments.
Observers have difficulties to interpret facts and make decision base on scenarios; therefore, system behavior is not predictable easily after system break down.
Observation 1:
Developers focus in system issues and have ambitious to interpret behavioral scenario; nevertheless, side effects of main issue may detect through scenario observations. That is why almost many functional systems do not full optimize today and many IT projects fail to achieve its goal.
Scenario illustrates series of data, action, and event. Each scenario has identification and modifies history of certain invisible entities. Observers recognize two types of scenarios in field of their studies 1) Static scenarios 2) dynamic scenarios.
Static scenarios illustrate data, action and event without any threads to instances in global variables. This type of scenario is not sensitive and do not have multiple-variables. Observer can interpret scenario because qualitative pattern does not show up in wide variety of simulated actions and series of data.
Dynamic scenarios are sensitive, contingent and have multi-threads to global variables. Many observers have dilemma to detect significant threads for possible interpretation and analysis. It requires time, capital, and sophisticated methods in order to analyze series of data and multi-events. Observers should detect hierarchy path and complex thread, which refer to instances in global variables in system environments.

No comments: