Complexity Management Patterns and Generative Software Development

Abstract

According to many researchers, Abstraction is the basis of mathematics, computing, counting devices, and computer science and engineering. What is more, all of the above deal with complexity management in some way, and abstraction is the most basic mechanism of complexity management.Generative software development - whether in the sense of empowering humans by machine to create software or in the sense of reusing products - has been and is one of the serious concerns and goals of software engineering. The interesting thing is that in both views of generativity, the main issue is still, in a way, complexity management: whether this complexity management is to achieve diversity and reuse management (Czarnecki’s approach) or to Structuring from existing structures (the approach of Alexander and his followers in an object-oriented society).In this article, we will first look at complexity and its various definitions. The definitions that show, despite the different perspectives on complexity in different disciplines and domains, all point in one direction. We will conclude that complexity is rooted in multiplicity. In the following, we will formally define complexity. In the following discussion, we will look at the generative patterns of software development, and then we will look at the complexity management patterns at seven levels.In this article, the author has tried to maintain a comprehensive approach to complexity and to consider the approaches of different domains to complexity.

A Conceptual Introduction to Model Driven Development: From Softness to Complexity

“…Since it was designed and developed to be changed and based on the idea of changeability. If the interlayer transformer software is not under complexity management [2] (=not modular and object-oriented), they will not have the ability to support changes. Software that lacks complexity management is harder than iron:…”

“…In Model-Driven Development (MDD) [1], the models, their generation [2], and imposing changes on them (model transformation) are used for the development of software. Models create a slow and steady transition from whatness to howness [3], [4], [5], i.e.…”

“…from the natural path of the generation of software. In the general sense, even code is a kind of model 2 . Once more in the general sense, a model can be described and imagined as the surroundings of an entity (a niche in the context [6] world), which is located in a specific level of abstraction.…”