Showing posts with label Journal of Systems Architecture Principles. Show all posts
Showing posts with label Journal of Systems Architecture Principles. Show all posts

Thursday, May 20, 2010

Principle 42

"Instead of an inflexible, hierarchical process that is designed once and executed many times, we must imagine how we might create highly flexible, constantly evolving system in which each exchange between participants is an opportunity for empathy, insight, innovation and implementation"  (Tim Brown, 2009).

Principle 41

"Design can help to improve our lives in the present. Design thinking can help us chart a path into the future" (Tim Brown, 2009).

Tuesday, March 2, 2010

Principle 40

While a system traditionally is modeled by decomposition into structural elements, the dynamic behavior of systems and actors is modeled by decomposition of the behavioral flow into events (Jens Rasmunssen).

Thursday, February 11, 2010

Principle 39

"Time and space are modes by which we think and not conditions in which we live" (Albert Einstein).

Principle 38

"To think means in any case, to bridge the gap in experience, to bind together facts and deeds otherwise isolated" (John Dewey).

Monday, February 8, 2010

Principle 37

"A fact poorly observed is more treacherous than faulty reasoning" (Paul Valery).

Principle 36

"The only relevant learning in a company is the learning done by those people who have the power to act"  (Arie P.De Geus).

Friday, February 5, 2010

Principle 35

"The cause is the sum total of the conditions, positive and negative, taken together, the whole of the contingencies of every description, which being realized, the consequence invariably follows"  (John Stuart Mill).

Tuesday, January 26, 2010

Principle 34

"An idea will seem self-evident - once you have forgotten learning it!" (Marvin Minsky).

Principle 33

"Many good ideas are really two ideas in one - which form a bridge between two realms of thought or different points of view" (Marvin Minsky).

Principle 32

"Some of the most crucial steps in mental growth are based not simply on acquiring new skills, but on acquiring new administrative ways to use what one already knows" (Papert's Principle).

Monday, January 18, 2010

Principle 31

"Just as we talk without thinking, we think without thinking" (Marvin Minsky)

Friday, January 8, 2010

Principle 30

"A System is Less Receptive to Negative Information the Closer It Gets to the Deadline" (Pr. Katz lecture on Human Side of Innovation).

Tuesday, November 17, 2009

Principles 28-29

"Even small changes introduced to the system may produce discontinuous, unpredicted effects (28).


Adaptive changes within a system can grow from learning generated by the individual interactions in the networks of system participants (29)."


(Metropolitan Development as a Complex System:  A New Approach to Sustainability, Judith E. Innes and
David E. Booher, Working Paper #699, University of California at Berkeley, December 1997).

Friday, November 13, 2009

Principle 27

"Do not plan a testing effort under the tacit assumption that no errors will be found" (Nancy Leveson, ESD.355)

Thursday, November 5, 2009

Principle 26

"1. Capabilities, Not Just Strategy.


2. Pull, Don't Just Push.


3. Scope, Not Just Scale.


4. Flexibility, Not Just Efficiency.


5. Platforms, Not Just Products.


6. Services, Not Just Products (or Platforms)"


(Michael Cusumano, lecture "In Search of Best Practice: Enduring Ideas in Strategy, Innovation and Technology Management" on the 24th Forum on COCOMO and System/Software Cost Modeling), November 5, 2009.

Tuesday, October 27, 2009

Principle 25

"A program is a human artifact, a real-life program is a complex human artifact; and any human artifact of sufficient size and complexity is imperfect" (De Millo, Lipton, Perlis. 1979.

Friday, October 23, 2009

Principle 24

“It is the last lesson of modern science, that the highest simplicity of structure is produced, not by few elements, but the highest complexity” (Ralph Waldo Emerson).

Thursday, October 22, 2009

Principle 23

"An important distinction to be made between programs properties that cause the program to be complex and program characteristics that are associated with complexity" (Kearney, 1986).

Principle 22

"Complexity usually arises from a small number of disproportionally complex procedures" (Henry, Kafura, 1984).