Contribution 12

From WikiContent

(Difference between revisions)
Jump to: navigation, search
Current revision (17:58, 14 July 2008) (edit) (undo)
(Use Contextual Sense)
 
(12 intermediate revisions not shown.)
Line 1: Line 1:
-
== Contribution 12: There Is No One-Size-Fits-All Solution ==
+
== Use Contextual Sense ==
-
''(note: the current revision of this page, and the following text, is serving as a placeholder, to be further elaborated very soon)''
+
Architects must continuously develop and exercise “contextual sense” – because there is no one-size-fits-all solution to problems which may be widely diverse.
-
There is no one-size-fits-all solution; the right solution is sensitive to context (see http://c2/com/cgi/wiki?ContextualSense)
+
The incisive phrase “contextual sense” was coined, and its meaning insightfully described, by Eberhardt Rechtin in his 1991 book <u>Systems Architecting: Creating & Building Complex Systems</u>:
 +
 
 +
<blockquote>[The central ideas of the ‘heuristic approach’ to architecting complex systems] come from asking skilled architects what they do when confronted with highly complex problems. The skilled architect and designer would most likely answer, ‘Just use common sense.’ … [A] better expression than ‘common sense’ is ''contextual'' sense – a knowledge of what is reasonable within a given context. Practicing architects through education, experience, and examples accumulate a considerable body of contextual sense by the time they’re entrusted with solving a system-level problem – typically 10 years.” [Rechtin SysArch] (emphasis in the original)</blockquote>
 +
 
 +
A big problem in the software industry, in my opinion, is that people are often responsible for solving problems requiring more contextual sense than they’ve accumulated. Perhaps this is because the software industry is barely two generations old and growing explosively; perhaps it will be a sign of maturity in the software industry when this problem no longer exists.
 +
 
 +
The most important knowledge of software patterns is the knowledge of when to apply them and when not to apply them, and the same is true of different root cause hypotheses and associated corrective actions during problem analysis. In both activities – system architecting and problem analysis – it is axiomatic that there is no one-size-fits-all solution; architects must develop and exercise contextual sense in formulating and troubleshooting their architectures.
 +
 
 +
(RMH Edited 7/14/2008)
 +
 
 +
By [[Randy.stafford|Randy Stafford]]
 +
 
 +
This work is licensed under a
 +
[http://creativecommons.org/licenses/by/3.0/us/ Creative Commons Attribution 3]
-
--[[User:Randy.stafford|Randy.stafford]] 17:46, 13 May 2008 (PDT)
 
Back to [[97 Things Every Software Architect Should Know]] home page
Back to [[97 Things Every Software Architect Should Know]] home page

Current revision

Use Contextual Sense

Architects must continuously develop and exercise “contextual sense” – because there is no one-size-fits-all solution to problems which may be widely diverse.

The incisive phrase “contextual sense” was coined, and its meaning insightfully described, by Eberhardt Rechtin in his 1991 book Systems Architecting: Creating & Building Complex Systems:

[The central ideas of the ‘heuristic approach’ to architecting complex systems] come from asking skilled architects what they do when confronted with highly complex problems. The skilled architect and designer would most likely answer, ‘Just use common sense.’ … [A] better expression than ‘common sense’ is contextual sense – a knowledge of what is reasonable within a given context. Practicing architects through education, experience, and examples accumulate a considerable body of contextual sense by the time they’re entrusted with solving a system-level problem – typically 10 years.” [Rechtin SysArch] (emphasis in the original)

A big problem in the software industry, in my opinion, is that people are often responsible for solving problems requiring more contextual sense than they’ve accumulated. Perhaps this is because the software industry is barely two generations old and growing explosively; perhaps it will be a sign of maturity in the software industry when this problem no longer exists.

The most important knowledge of software patterns is the knowledge of when to apply them and when not to apply them, and the same is true of different root cause hypotheses and associated corrective actions during problem analysis. In both activities – system architecting and problem analysis – it is axiomatic that there is no one-size-fits-all solution; architects must develop and exercise contextual sense in formulating and troubleshooting their architectures.

(RMH Edited 7/14/2008)

By Randy Stafford

This work is licensed under a Creative Commons Attribution 3


Back to 97 Things Every Software Architect Should Know home page

Personal tools