Subsystems in Holistic Programming

Talking about subsystems in Holistic Programming could be seen as an contradiction. Still, the term subsystem seams to be most appropriate to talk about components of a holistic system, considering these resource, for example:

"Sụbsystem, Bereich innerhalb eines Systems, der selbst Merkmale eines Systems aufweist." (Meyers Lexikon) - (Engl.: "Subsystem, area within a system that has attributes of a system itself".

 "A subsystem is a coherent and somewhat independent component of a larger system." (SIL LinguaLinks) -I'd like to emphasis the phrase "somewhat independent". SIL LinguaLinks lists as examples for subsystems those of the human body like nervous system.

While we are in "danger" of analysing a holistic system (which would not work well), we stil are able to identify subsystems, that connect to other subsystems, but are not independent from these, as the connections are not trival. It's important clearly to distinct between "classical" components in software development. These are explicitely defined to have narrow interfaces, that don't change to keep the component connections intact.

In Holistic Programming, a subsystem can be identified, even can get a name, and the connections to other subsystems can be identified (within a holistic programming system we have the knowledge about every relation between it's parts). The nice thing in Holistic Programming - since we know the whole system - we also know the subsystem - and we can deal with it. The main difference between subsystems in Holistic Programming and those in classical software development is, that design entities like objects are not nessisarily completely part of one subsystem. It's possible that an object like "Person" as assigned to the subsystem "Partner Management", but the attribute "Wearing Shoe Size" (which related to the person's feet) is defined in the subsystem "Shoe Shop".