Proceedings of the 8th International Conference on Intellectual ...

Figure 4: Modeling knowledge subsystems
S1. Input
conversion
S2. Internal
conversion
Igor Hawryszkiewycz
S3. Decoding –
changing into useful
information
S4. Channeling–
moving information
about
S5. Memory – keep record <strong>of</strong> actions
(learning)
S6. Association –
combining messages
Community
S7. Decider looks at
messages and decides
on course <strong>of</strong> action
S8. Encoder sends
information out
Figure 5: Guideline 2 - information subsystems in living systems <strong>the</strong>ory
These subsystems can now be used as guidelines for <strong>the</strong> completeness <strong>of</strong> information or knowledge
flows. What is <strong>the</strong>n needed is to follow <strong>the</strong> flow <strong>of</strong> each message through <strong>the</strong> system. The message
can <strong>the</strong>n be used in a number <strong>of</strong> ways. These are:
To trace through <strong>the</strong> system to ensure that each message is handled in its entirety
Identify <strong>the</strong> services needed by each role to process <strong>the</strong> message, and
Ensure that learning takes place through <strong>the</strong> storage <strong>of</strong> outcomes <strong>of</strong> interactions between
associations.
Some such flows are illustrated in Figure 4 with messages labeled by <strong>the</strong> identifier. One message in
Figure 4 is a request for change to system requirements. Here a request for a change request is
231