intra-disciplinary in systems thinking

In previous postings I use the term Internet Systematics to denote an approach very similar to Systems Thinking as given by the full review of the field by C.Francois. A comment on previous posting underlined the problem what is a systems approach ?


George Adamopoulos, the constant postmaster (*) located a relevant paper
a very welcoming comment that has me going on this "systems" direction.


The title was "A bootstrap is cooking" signaling the feeling that a legitimization of the work is on the way. I am close but not quite there. How can you express something to Systemists that I am not certified in their full language versus how to introduce Systems thinking to Networkers without going into details that do not interest them for sure adn for what purpose ?

The best I have done so far is the book The phenomenon of Science a really simple introduction though is using the term cybernetics. But my real work is almost a redux of the book, for example Automation Quantum or Network Transition instead of Turchin's Metasystem Transition (see wikipedia) so it will be to talk about two evolutionary cases.

Systems, General Systems, Cybernetics is really a inter-disciplinary approach applied across Science fields like Biology, Economy etc.

Internet Systematics (or Systemics) seems to constitute an intra-discipline systems approach applied across the complexity layers of the Network phenomenon. Hum ?

Googling the term takes to a Phd program in MIT !


Intra-disciplinary knowledge areas

The intradisciplinary computing knowledge areas are organized into the three I's: interaction, informatics, and infrastructure.

Interaction refers to topics related to the combined action of two or more entities (human or computational) that both affect one another and work together when facilitated by technology. It in turn encompasses several subtopics relating to how people and technology interact and interface.

Informatics is the study of computational/algorithmic techniques applied to the management and understanding of data-intensive systems. It focuses on the capture, storage, processing, analysis, and interpretation of data. Topics include primarily algorithms, complexity, and discovery informatics.

infrastructure comprises aspects primarily related to hardware, software (both system software and applications), communications technology, and their integration with computing systems through applications. The focus is on the best organization of these elements to provide optimal architectural solutions. It includes, on the hardware side, system-level design (e.g., for system-on-a-chip solutions) and their building block components. On the software side, it covers all aspects of systems and applications software development, including specification and design languages and standards; validation and prototyping, and multi-dimensional Quality-of-Service management; software product lines, model-driven architectures, component-based development, and domain-specific languages; and product estimation, tracking, and oversight. The communications subtopic includes sensor networks and protocols, as well as active networks, wireless networks, mobile networks, configurable networks, and high speed networks as well as network security and privacy, quality of service, reliability, service discovery, and integration and interworking across heterogeneous networks. At the system level there are issues related to conformance and certification; system dependability, fault tolerance, verifiable adaptability, and reconfigurable systems; and real-time, self-adaptive, self-organizing, and autonomic systems.



(*) Constant Gardener, is a John Le Carre recent title that I think best describes Adamo's consistent attention to Network Administration, a noble profession and discipline still out of the radar of many Universities and Research Centers.