theory of (computerised) "organisational intelligence"

From: mountain man <hobbit_at_southern_seaweed.com.op>
Date: Fri, 09 Mar 2007 05:39:28 GMT
Message-ID: <kq6Ih.9003$8U4.8931_at_news-server.bigpond.net.au>


"Walt" <wamitty_at_verizon.net> wrote in message news:kXUHh.2934$pi.293_at_trndny09...
>
> "paul c" <toledobythesea_at_oohay.ac> wrote in message
> news:0wJHh.1243698$1T2.634148_at_pd7urf2no...
>> mountain man wrote:
>> > ..
>> > We are discussing the change management of databases and their
>> > schemas. ...
>>
>> I'm glad you have made that qualification as just exactly what the cm
>> theory that you have in mind isn't very tightly drawn for me at this
> moment.
>>
>> However, I note that in a later post, you accept Walt's reply in its
>> entirety and if I understand him, he said that concurrency results are
>> part of the theory.
>
> Yes, concurrency results are part of the theory.
>
> However, there is a recurring theme in many of mountain man's other posts,
> that is only tangentially related to concurrency results.
>
> I can't state it precisely , but it's along the lines of "change
> management
> in the schema itself" (as distinct from "change managment in the data
> content"). Kinda like the difference between CREATE, ALTER, and DROP on
> the
> one hand and INSERT, UPDATE, and DELETE on the other. But mountain man's
> issue is at a different level of abstraction than what I just outlined.
>
> This can be one of the largest issues for "large, shared databases" going
> forward. On the one hand, you want flexibility, so that requirements
> that
> didn't go into the logical model of prior versions can be accommodated.
> On
> the other hand you want extreme backward compatibility, so that the
> longevity of the database can be appropriately exploited. The sweet spot
> on
> the trade-off is difficult to find.
>
> I'm sure mountain man can state this better than I can.

Thats a good start. The problem actually specify things in this arena is the absolute rampant diversity of the environments one is likely to find relating to:

  1. the database (DBMS RDBMS whatever)
  2. the associated suite of software applications
  3. the evolution and change management of both

The sum total of all these things above, I descibe by the term of "organisational intelligence", where the word "computerised" is implied and understood. That is, computerised OI is the sum total of all the data and all the lines of program code forming the associated suite(s) at 2 above.

I have some years back attempted to outline and discuss what I termed a gernal theory of "organisational intelligence". At that time, perhaps it was not understood that I was talking about these three things above, and that the term "computerised" perhaps should have been made explicit.

Nevertheless, the article is located here: http://www.mountainman.com.au/software/Theory_of_Organizational_Intelligence.htm

Its a journey and IMO a relatively new area of definition, and I have not at all wanted to remain formal. This you will find frequent references to ying and yang, and other philosophical attributes.

Thanks for the feedback. Received on Fri Mar 09 2007 - 06:39:28 CET

Original text of this message