工程学的思维方式和辩术
某网站上看到的，作者讲了工程师如何思考问题，解决问题，如何说明自己的方案是足够好的，以及工程学教育的问题。里面的一些观点很不错，如作者文中提到工程学的思维方法类似于医学和经济学（而不是我们通常认为的数学和物理，工程学只是用到数学和物理的知识）。文中将工程问题可分为简单问题(simple problems)和复合问题(compound problems)，并重点论述了复合问题的解决步骤。作者认为工程师应重点掌握“类比”的思维方式。原文摘录如下，内容有一点艰涩，我自己也理解地不是很好。Engineering Thinking and Rhetoric
John A. Robinson
Faculty of Engineering and Applied Science
Memorial University of Newfoundland
St. John's, NF, Canada
Abstract
Engineers seek optimal solutions to problems. Often,though, the constraints of the problem and the solution criteria are ofseveral, qualitatively different types, and there is no formal way to find thebest trade-offs. Nevertheless, engineers make judgments and provideexplanations to justify their choices. Engineering thinking and rhetoric is thedevelopment of such explanations that identify and validate a particularsolution as the best. Engineering thinking involves analogical reasoning aswell as deduction. This implies that in teaching engineering, descriptivecase-based examples are important to the student as source analogs for problemsolving.
Introduction
William Wordsworth, in The Prelude , writes:
Science appears as what in truth she is,
Not as our glory and our absolute boast,
But as a succedaneum, and a prop
To our infirmity.
Scientists and engineers would agree that Wordsworthgot it wrong. He was talking about engineering. Science is our glory,the scientists would say, because it is a proven road to discovery. By framingquestions and seeking answers in a formal and consistent way without fear orfavor, science enables us to know the truth about the world. While thescientists happily strike out "Science" from Wordsworth's first line,the engineers just as happily insert "Engineering", because thatdiscipline is all about service. Being "a prop to our infirmity" is anoble enough cause for engineers.
Perhaps because they see their work in servanthoodterms , engineers are reluctant to claim it is intellectually profound.Memorial University's library has several hundred books on the philosophy ofscience and not one on the philosophy of engineering. Engineers deal withcomplicated and difficult problems that admit many possible solutions but fewgood ones; they have theories and methodologies, some of which can be appliedvery broadly; but they shy away from advertising their way of thinking assomething distinct and valuable in its own right.
On the other hand, engineers argue that the creativeaspect of their thinking cannot be analyzed completely. "Engineeringjudgment", the ability to make sound design choices based on experienceand intuition, cannot be summarized in a list of rules. This may be true, butfor scholars of the discipline in a University, engineering judgment issomething that should be analyzed. To understand knowledge, and in particular,to educate engineers, academics should attempt to explain, as clearly aspossible, what engineers do intuitively.
Consider the question: "If there were nopractical use for engineering, what could be said about the way engineers thinkas an alternative to the way (for example) mathematicians, physicists,anthropologists and historians think?" A good answer will mark out theintellectual dimension to engineering which draws on and can contribute toother areas of scholarship. It will identify the academic role of engineeringeducation. A good answer will also show what kind of argument or rhetoric isappropriate for explaining engineering decisions. This paper attempts apreliminary answer, and identifies the central role of analogy in engineeringthinking.
What Engineers Do
The Oxford English Dictionary defines an Engineeras "one who contrives, designs or invents; an author, designer; also aninventor, plotter, a layer of snares". Delightful though this definitionis, it does not capture why or how an engineer works. The EncyclopaediaBrittanica has "engineering the application of scientific principlesto the optimal conversion of natural resources into structures, machines,products, systems and processes for the benefit of mankind" . CambellMartin succinctly identifies the "essence of the engineeringapproach" as "using models to make proper decisions" . Ioffer the following five-point description of engineering as a synthesis:
• Engineering is applying scientific knowledge andmathematical analysis to the solution of practical problems.
• It usually involves designing and buildingartifacts.
• It seeks good, and if possible, optimum, solutions,according to well-defined criteria.
• It uses abstract and physical models to represent,understand and interpret the world and its artifacts.
• It applies well-established principles and methods,adapts existing solutions, and uses proven components and tools.
The above definitions include the key issues ofproblem solving, the reliance on science and math, and methodology. However,they do not say much about how engineers think. What can be added to expressthe intellectual root of engineering? I suggest the following:
• Engineering is the development of an explanatoryframework that identifies and validates a particular solution to a problem asthe best.
This supplementary definition builds on the idea of optimalproblem solving already suggested in the earlier definitions, but it emphasizesexplanation. The idea is that engineering has a rhetoric, or a mode of argumentto justify what it does. Indeed, there are at least two modes of argument, andthese depend on what the word "best" means for a particular problem.For some problems, which here will be termed "simple problems", bestmeans the solution which can be proved optimal through mathematical analysis orother deductive reasoning. For other problems, here called "compoundproblems", it is not possible to find such an analytic optimum, and bestmeans the solution which is judged the most suitable tradeoff. That judgment ismade, and justified, through "engineering thinking".
How Engineers Think
Simple Problems
In simple problems, the constraints and criteria forevaluating the solution are all qualitatively similar. Even difficult problemsin computational terms can be simple according to this definition. Thetraveling salesman problem, which involves working out the shortest path tovisit a number of cities, is computationally hard, but because it has a singleevaluation criterion (distance) it is a simple problem. Many other engineeringoptimization problems are simple in this sense. Designing a circuit that has tomeet its specification with the minimum number of devices is a simple problem,because two solutions can be compared and the better one selected.
The explanatory framework of simple problem solving isdeductive. Engineers solving such problems are thinking more likemathematicians than scientists (science is fundamentally inductive). Thesimilarity should not be overstressed however. In many branches of math,optimally is not essential. For a mathematician, finding any proof isoften a triumph. Engineers, by contrast, are not satisfied with existenceproofs. Getting something to work is inadequate; it has to work well accordingto parameters of the problem. Even in simple problem solving, the engineerlooks for evidence that the space of possible solutions was properly searched,and the chosen solution correctly proved to be optimal.
Compound problems
In compound problems, the evaluation criteria are notqualitatively similar and cannot be jointly optimized. Engineering jobs whichrequire the balancing of cost, safety and aesthetics are compound. Most systemsengineering jobs are compound. Wherever there are choices of materials,subsystems or methods that emphasize one or another property, the problem iscompound. The engineer can now apply several strategies:
1 Disqualify (ignore) criteria that cannot bemeasured.
2 Express relative values of criteria based on someevidence, then try to reduce the problem to a simple one.
3 Divide the problem into parts which can beindependently solved as simple problems.
Strategy 1 sometimes has to do. For example, it may beimpossible to say how the aestheics of a bridge are to be measured. However, ifa criterion like aesthetics is rejected, there may still be some implicit lowerlimit on ugliness. It is part of the job of engineering, as an intellectualdiscipline, to understand how immeasurable but implicit criteria are to bedealt with.
Strategy 2 is important. Cost-benefit analysis usesmoney as the common currency of diverse constraints and criteria. Whenengineers do this, they are acting like economists, and must answer the sameeconomic (and philosophical) questions about attributed value. But engineershave a wider gamut of mappings between qualitatively different constraints.Speed/accuracy and speed/size are common tradeoffs. When the engineer chooses atradeoff, a judgment is being made about relative value, and that must beexplained.
Strategy 3 is pervasive. Almost all real engineeringprojects are decomposed into subproblems which are then solved almostindependently. Explaining why the problem has been decomposed is usually easy:The problem would be insoluble otherwise. But engineers should also be able toexplain why a particular decomposition has been chosen, to justify the beliefthat the aggregate of optimal subproblem solutions will be the best overallsolution, or, at least, close to it. Usually a project-wide goal, for exampleuse of existing components, re-usability of new designs, or localizingproperties and features into modules, guides the decomposition. Such a goal isreally an evaluation criterion, and engineering rhetoric should explain why itis weighted so highly.
Compound problems include simple problems and theirsolution is therefore partly deductive. But trading off between qualitativelydifferent domains requires a different kind of thinking. It has much in commonwith legal reasoning. In law, some decisions are made by the interpretation oflegislation; some are made by developing earlier case decisions. These tworoutes to a decision are different: the first is the application of an abstractrule to a particular instance, the second is dealing with a particular instanceaccording to similar previous instances. The first is a top-downtheory-to-application route, while the second is a sideways precedents-to-applicationroute. Compound problem solving uses the same two routes. Abstract rules areapplied when the relative values of different courses of action can be measuredand compared. This is not usually the case in design, so exemplars (previousdesigns) have to be applied too. By analogy with these precedents, compoundproblem solving decides on a best solution.
Practicing engineers probably make use of analogy asoften as practicing lawyers. Reference to previous jobs, identifyingsimilarities and differences, making linkages between contexts, are all regularhabits. In many cases the analogies will be simple and direct, but, especiallyin systems engineering, the linkage can be between two very different domains.The ability to see analogical situations, particularly in balancing the valuesof different criteria, is central to engineering judgement. The ability toexplain these analogies, and argue their relevance, is engineering rhetoric.
Links with other disciplines
Engineering solves problems using physical science andmathematics. Its links to those disciplines are clear. Yet, in terms ofengineering thinking and rhetoric, its dependence on them is really accidentalrather than essential. Engineering's goal (problem solving) and its method(deduction and analogy) is much closer to medicine and ethics than to science. Itsrhetoric (justifying its analogies) is close to law, and perhaps to economics.Table 1 summarizes three approaches to thinking, which groups engineering withthese disciplines. While this classification is very tentative, I find it helpsin introducing students to the academic place of engineering (see below).
AimMethodArgument
ScienceToexplainObserve\Hypothesize\TestFalsifiablehypothesis has been corroborated and not refuted
HumanitiesTointerpretCollect\Critique\SynthesizeInterpretationis coherent and revealing
EngineeringTosolveSpecify\Design\VerifyDesignis optimal analytically or by analogy
Engineering does differ from other disciplines thatrely on analogical reasoning. For medicine and law it is usually very easy todefine the terms of success. Not so for engineering, which must begin itssearch for solutions by demanding clarity on what sort of solutions will do,and how they will be measured. The criterion question, "How will I know Ihave succeeded?", is the first step in design, and uncovers userrequirements, presuppositions, physical limitations, and values. Definingcriteria requires systematic analysis, and again draws on both analogy anddeduction.
Teaching Engineering
Engineering students should be taught both simple andcompound problem solving. Because the modes of thinking are different, theteaching methods will also be different.
Simple problem solving is deductive. It may be taughtnormatively; that is, students are told what they should do. Method,theory, its application, heuristics, are all appropriately taught with rigor.Illustrative examples do not validate concepts in simple problem solving; theconcepts stand in their own right, derived from theory. Examples simply helpstudents to master the application of those concepts.
Compound problem solving relies on analogy. Normativeteaching is still important, but there should also be teaching which recognizesthe role of analogy. This will be of two types -- how to think analogically,and case-based descriptive teaching of particular engineering topics. Courseson critical thinking are useful for alerting students to the dangers ofreasoning based on patterns (including analogies) alone. However, they rarelyincorporate insights about how to use analogy effectively. This subject is nowbeginning to be taught in philosophy departments alongside traditionalreasoning courses (see, for example ), and engineering students could bea prime audience. Learning to use analogy effectively and reliably is aworthwhile complementary studies component in any engineer's program. Thesecond type of analogy-based teaching is in the engineering discipline itself.In learning new engineering subjects, students should be told what has beendone in a variety of past situations. Practical examples now take on a muchmore fundamental role -- they do not merely illustrate concepts, they contributeto them.
In the teaching of analogical reasoning, engineeringeducators can learn from other disciplines which make heavy use of analogy.Foremost among these is law, but literature, rhetoric and philosophy havecontributions to make too. More important, they are taught how to find, adaptand apply previous cases to new situations.
To see how the understanding of compound problemsolving affects teaching, consider design methodology. Because design is commonto all kinds of engineering, it has often been understood, researched andtaught as an abstraction. In teaching, the abstraction is illustrated throughreal design projects for students to tackle. This mode of teaching reflects thenormative stance of simple problem solving -- develop a common theory, apply itto examples. But if the understanding of compound problem solving as analogicaljudgment is correct, then design methodology teaching should also includecase-based teaching. Rather than learning to solve problems by following ageneric recipe, students should be learning to solve problems by getting asmuch information as possible on analogous previous problems, their solutions,and their solution processes, and then applying this information skillfully.This does not mean there is no place for teaching design in the abstract -- butit does mean that the sideways links between different instances of design mustbe taught and exploited too.
In teaching courses in digital systems engineering andsoftware engineering, I have introduced students to the subject with adiscussion of analogy in engineering design and in the particularsubdiscipline. The introductory lecture invariably excites a small portion ofthe class who seem not to have either a common ability level or a sharedspecial interest within engineering. For these students, seeing therelationship of engineering to other disciplines is highly motivational, andoccasionally leads to further study of engineering education and philosophy. Mypurpose in writing this paper is to stimulate similar interest among theprofessoriat.
Conclusion
Engineering problems involve interacting, butqualitatively different, constraints. Engineering solutions must be justifiedby explaining the weights given to qualitatively different criteria. The impactof technology on its problem domain, on the business developing it, and onsociety are important management, historical and ethical questions. But theylogically depend on deeper philosophical and psychological questions about whatjustifies the arguments, what validates the method, what makes explanationsplausible and why. This is engineering thinking.
In making decisions concerning qualitatively differentconstraints and criteria, the engineer draws on similar previous problems andsolutions. Analogical reasoning is thus at the heart of Engineering Thinking.Therefore engineers should be trained in the use of analogy, and given a richset of source analogs from which to reason.
Engineers are not alone in facing the problems oftechnology, society and values, but they have a special responsibility. If theyare well trained in both simple and compound problem solving, they will alsohave special expertise. With training in finding solutions subject toqualitatively different constraints, engineers will have the tools andexperience for meeting situations where costs must be balanced, but there areambiguities about relative value. Understanding engineering thinking thereforeleads to better training of engineers as society's servants
挑肥拣瘦，通读一遍，摘要如下。
介绍
科学能使我们了解世界的真谛。
工程师在处理复杂艰难问题的同时，往往问题有多种可能的解决方案，但只有少数是算得好方案。
工程师们常争论，没人能完全分析他们创造性的思考。“工程上的判断力”来自于经验和直觉，不能被总结成教条。
文章尝试回答，并且说明工学思维在分析中的核心地位。
工程师干什么？
牛津字典解释“设计或发明”。
大英百科解释“科学原理的应用、把自然资源转优化变成结构、机器、产品、系统和一切为人类服务的过程。
总结为五条工程规律：
1.应用知识和数学分析来解决实际问题。
2.设计和制造。
3.追求最优方案。
4.应用抽象的物理模型。
5.应用已有的原理和方法、移花接木现有的方案、并使用被证明有效的组件和工具。
但这五条没讲工程师如何思考。
工程师如何思考？
简单问题 - 问题的边界和标准已量化，就比如简单的数学证明题，尝试几次就可以了。
复杂问题 - 问题虽难，也有对策。
1.忽略那些不能量化的标准。
2.分成若干有关联的简单。
3.分成若干独立的问题。
借鉴其他学科的规律，比如法律和医药学。
工程教育- 简单问题和复杂问题的思考方法不同，所以教学方式也不同。
结论：
工程问题的解决在逻辑上是基于哲学问题和精神问题。
工程师应该有类比的训练。
培训工程思维。
评语：空洞。建议作者写诗。
又学英语了 如果，哪位高人能够翻译成汉语，大家都可以学习了。 看着长篇英文
顿感压力，，， 可惜一片好文章，只字不识 还不如那位嚷嚷中学的家伙写的呢。 工程猿懂的还真真多 从几处细节（没断句好的）可以看出是老兄手打的，辛苦了哈{:soso_e100:} leungc 发表于 2012-10-23 20:39 static/image/common/back.gif
可惜一片好文章，只字不识
深有同感！
页:
[1]