Saturday, September 12, 2015

Encapsulated Genetic Algorithm within Input Framework creates Closed-loop model

The properties of an object define attributes and operating characteristics task information used to govern default values for object. Each object consists of specific Genetic Principles and unique inheritance patterns of phenotypic characters. Genetic Algorithms is comprehensive techniques for solutions to optimization problems. It is based on natural selection, Genetic Principles, and pattern matching mechanism within an object.
Genetic Algorithm within Input Framework is developed by Systems Owners and it ensures Harmonic Balance within designated System platform.  Genetic Algorithm provides key infrastructure support to Data resource within Input Framework and all resources (internal & external resources) in system platform.  Encapsulated Genetic Algorithm within Input can generate optimal resources and cause sustainable process operations.
Genetic Algorithm creates and instantiates Input parameters within objects and optimizes all resources through Information Processing System. Moreover, Genetic Algorithm provides standard and guidelines for quality Outputs. Genetic Algorithm builds extension key facilities for system platform in terms of meeting operational & functional requirements.
Input 1with encapsulated Genetic Algorithm generates Output 1with Genetic Algorithm pattern. There is appropriate analogy between Input 1properties and Output 1properties. Genetic Algorithm (Conventional Algorithm) within Input 1Framework optimizes all resources and system performance can set to realistic goals. Output 1 can accomplish more comprehensive coverage of complex parameters than “Unconventional Algorithm” within system platform. Eventually, the outcome mapping for encapsulated Genetic Algorithm shows Closed-loop model structure. (Fig 1)
System Owner develops “Unconventional Algorithm” for solving complex scenario in rationalization process. Input 2 data with “Encapsulated Unconventional Algorithm” process “Output 2 frameworks” through Information Processing System. Transparent analogical patterns between Input 2 and Output 2 can identify allocated “Unconventional Algorithm” within Input 2 Framework. Unconventional Algorithm focuses on instance parameters of complexity in rationalization process. Unconventional Algorithm would fail to respond internal & external resources; besides, it could not perceive and define requirements for functional & operational level strategy. Eventually, outcome mapping for encapsulated “Unconventional Algorithm” is partial open-loop model structure. Parameter complexity requires multiple sub-optimizations on the evolutionary path of systems performances. (Fig 1)

Friday, September 4, 2015

Partial Open-loops due to outrageous Hypocrisy in Source Codes

Hypocrisy is the natural state of the human mind. Naturally, Systems Owners would use instance parameters of Hypocrisy either intentionally or unintentionally. Parameters of Hypocrisy are instantiated in System Platform by programming codes and they can be built unpredictable complex behavioral operations from systems perspective. 
System Owner can establish policy strategy both for “process management activities” and “technological design process”. Two different project groups work with technological design process within enterprises. “Construction Project Team Members” build IT-technology solutions and “Maintenance Project Team Members” maintain a watch-list of encapsulated forms of technologies.
Potential Hypocrisy as an input in systems program can generate through Construction phase. Wrong mental model for “cost-effective assessment of technological design” and “lack of systems thinking” would modify Source Codes within Construction phase.
Example1: sometimes, operational system would produce outputs in the most cost-effective ways without understanding feedback-seeking behavior (learning and performance goal orientation).  Logical Consequences must be measured and identify source code needs before formulating algorithms on the state of UML objects.
Example 2: operational systems show paradox between strategic planning system (specific inputs) and instance of output patterns.
Potential Hypocrisy can generate through Maintenance phase while certain processes eliminate and modify due to costs-effectiveness.
Case study 1: System platform supposed to synchronize components and modules according accumulated data in case studies every “two weeks”. System components operate according to default mode and realistic natural behavior in system mode.  Case studies focus on functional programming principles, which associate with internal and external system changes. System developer evaluates new attribute values and encapsulates codes in system platform by programming languages.  
Strategic alignment model in Maintenance phase is based on reducing time series analysis in case studies. Accumulated data in time series analysis encapsulates in system platform every “three weeks” (change time interval from 2 weeks to 3 weeks).
Sometimes, Systems Owners would be compelled to change operational efficiency through cost- reduction measures in streamline manufacturing by reviewing following parameters:  

1- Time series analysis on case studies.
2- Labor expenses and overhead costs.
3- Add and eliminate functions.
4- Lifetime constraints for products due to competitive advantages.
5- Maximize quality products instead of developing useless marketing.

Discrepancy between “Default Maintenance Mode” and “Modified Maintenance Mode” generate outrageous Hypocrisy in source codes within system platform. Complexity among source codes causes partial open-loops in system performances. It requires sub-optimization mode in order to resolve integrative complexity for short term time series. (Fig 1)

Case study 2: Manufacture products move quickly to market in order to be available for sale due to time to market (TTM). Concept beyond TTM is profitability, return on investment (ROI) in short term mission, and speed innovation.
Instance parameters of TTM can encourage customers to help themselves by testing products and take care of technology.  Customer can return product to store three times for reparation and optimization.  Customer might get rewards with VIP status (a brand new product or service) if product or service fails for the third time. Error information about product failure can send to designated department in order to track error characteristics and improve assessment procedures. 

Enterprise focuses on developing and providing unique perspective for customer engagement model in order to rationalize operational costs. This type of customer engagement model would not be convenient and feasible for customers because customers must allocate private time for developing product and services. Sometimes, poor quality products can be devastating to customers’ wallets and Customer Value Proposition. (Fig 2)


Hypocrisy within TTM is Phenomenon that occurs in system platform when System Owner is aware of “Customer Dissatisfaction” and “Paradox in Complex Nature of Operational Outputs”.  One of Global strategy for the most enterprises is “Customer Satisfaction”; however, operational outputs might show Customer Dissatisfaction. 


Sub-optimization implies to short term gains instead of long term success. Sub-optimization must be used when Systems Owners articulate parameters of Hypocrisy in system platform. Sub-optimization is only solution to improve outrageous Hypocrisy in source codes. It allows system mechanism rollback to normal mode in short term performance goals. There are two possible case scenarios out of the several possibilities in Sub-optimization. These two possible case scenarios can define as following.
The best case scenario = short term gains + long term ambiguity (Depend on rational perceptions)
The worst case scenario can be divided into three consecutive processes as following.
1- The worst case scenario = short term losses + high costs and few benefits = complexities of multiple identities (Open-loop)
2- Open-Loop + approach for a new interval of Sub-optimization = outcome would be complexities (Open-loops)
3- Open-loops + execute multidisciplinary design Sub-optimization = complexities of multiple identities (Open-loop)


Lifetime constraints of products and system maintenance through modification in source codes can increase economic efficiency. This method is the economic Hypocrisy of source codes and it generates more profits at the expenses of loyal customers.


Hypocrisy Instinct (Hypocritical instinct) is efficient natural defense mechanisms against external entities and it activates in Brain for personal gains and desires, competitive advantage and productivities for multinational enterprises, sustainable competitiveness and security within a country, and Harmonic Balance in Global Economy. Hypocrisy causes complexity in environmental systems and then complexity generate side-effects, which is adopted by people all over the world. Eventually, people develop their own sophisticated methods in terms of obtaining profits in designated community.


Outrageous hypocrisy in “construction phase” (modules in entire system platform) and “maintenance phases of life cycle” within aerospace technology systems cause tragic circumstances that impact on mankind.