Talk:Engineering

From Wikipedia, the free encyclopedia

You have new messages (last change).
 This article has been identified by the Version 1.0 Editorial Team as a Core Topic, one of the 150 most important articles for any encyclopedia to have. Please help improve this article as we push to 1.0. If you'd like help with this article, you may nominate it for the core topics collaboration.
B Engineering has been rated as B-Class on the assessment scale.
This article has been selected for Version 0.5 and the next release version of Wikipedia. This Engtech article has been rated B-Class on the assessment scale.

Contents

[edit] Arbitrary section heading to get unsectioned stuff below the TOC

Technology is the collection of state-of-the-art- techniques, knowledge etc on a certain subject.

  • It's not just the state-of-the-art techniques, but all the techniques. When it first happened the invention of the wheel became a technology, and it still is.

Science is the (planned and unplanned) unbound exploration of knowledge about a specific subject under the axioms accepted in scientific community (e.g. show something repeatedly)

Engineering is the proper application of technology.

  • Is "proper" essential to the definition?

There is a significant difference in the understanding and usage of the word engineer and Ingenieur.

the explanaition: Engineering is the proper application of technology. Is adequate for its current usage in English, as it is truly understood in describing a professionial capable of applying existing knowledge in technical fields and actually executing the task. It is expected of an engineer to understand a drawing, but not to make one to describe something new.

An Ingenieur understands his profession as applying existing knowledge or finding new knowledge in technical fields in new (novel), often non-obvious (the core requisite for a patent) ways, using drawings to communicate these new ways without depending on language. This automatically includes Architecture. The history of Ingenieur is based on core inventions like wheel, lever and pulley leading to building of fortresses already in prehistoric times, followed by the building of pyramids and the modern world. An Ingenieur should be able to, but usually does not execute the task(s).

A common language is essential for communication and led to latin being taught at universities since the first one in Bologna in 1088. Without a common laguage exchange and discussion of new ways is not possible. Drawings of spears launched via a Throw Stick (Wurfstock [German], Woomera [Aboriginal], Pe [Phönizisch]later Pi [Greek] ) a novel step to encrease speed and thereby distance can be seen on prehistoric drawings.

The introduction of a new title intended for world wide usage: http://en.wikipedia.org/wiki/European_Engineer is a step to unravel/address this difference in understanding. Walter Hartmann 23:08, 12 October 2006 (UTC)







I always liked this informal definition: Once scientists discover the principles by which a bridge can be made, anybody can make bridge that will hold 100 tons. It takes a good engineer to make a bridge that will hold 100 tons, but that won't hold 110. --LDC

  • With such a low tolerance above specifications you may be building another Galloping Gertie of Tacoma Narrows.
I thought civil engineers always used a safety factor of at least ten times!
  • No, safety factors are much lower than that in general, because the situation is well understood, and often there are mutliple safety factors for different things which makes it larger. Safety factors are only high if the the situation is less predictable. John 08:32, 24 November 2005 (UTC)

It seems to me that this entry needs a lot more work. I'll try revising it later, but if someone wanted to take a look at it now... -- ansible

[edit] Definition of engineering

This article contains many factual errors but most significantly it opens with the following statement:

Engineering is the application of scientific and technical knowledge to solve human problems.

This is misleading, even meaningless, for the following reasons:

  1. It fails to distinguish engineering from similar fields. Medicine, for example, could equally well be described as "the application of scientific and technical knowledge to solve human problems".
  2. It (and the following sentence) fails to identify the fundamental characteristic of engineering, design, that distinguishes engineering from fields like medicine. Such an inclusion needs to be qualified by the types things created by engineers to distinguish it from, say, architecture or wall paper design.
  3. The phrase "to solve human problems" is too vague also. I might have a problem of knowing what shoes to wear. Engineering is not likely to help solve it.
  4. It implies a dependence on science. Systematic science based engineering as a discipline is only about 200 years old (originating in institutions such as the École Polytechnique) and the underlying sciences originated in the seventeenth century (for example in Galileo’s Two New Sciences). For this reason the definition effectively rules out what can justifiably be described as engineering such as ancient road, bridges and irrigation systems. If we include naval architecture as an engineering disciple it also rules out things like Greek triremes. In fact the Romans demonstrate that you can take both science and mathematics out and still get engineering but if you take the creativity out you are likely to get nothing.

Unless someone can suggest how to modify this to address these deficiencies I propose replacing the definition with one that recognizes design, does not imply dependence on science or mathematics and which identifies engineering with its products. IanWills 00:47, 19 June 2006 (UTC)IanWills


Perhaps wikipedia needs an information engineer to deal with this subject.

It seems to me that this is a cheap oppertunity for so called scientists to gang on engineers. To those who actually are interested in learning the difference between the two schools of thought, you will find that in the real world they are much more closely related than the people here are willing to admit. I would go so far as to say that there is a "peanut butter and jelly" relationship between them.

Science is generally the abstraction of reality, broken out into specific namespaces and processes for the purpose of describing and understanding the universe. Engineering is generally the application of science to make something useful, or solve real-world problems. Engineering is the "hardware" that makes the software (science) actually do something. It is the actual action that follows the dream from the night before. For without the dream, one may not have acted. But without the action, the dream did not find fruition. Peanut butter and jelly.

So as much as these "scientists" rag on the engineers, the stunning reality is that not everybody can get a job as a scientist. And many graduate college to become engineers.. After all, "applied knowledge" needs application or we would never experience progress. The economy really dictates the future for many of us. So when you are hungry looking for a job as a scientist somewhere, you may find that it is not so bad to become an engineer instead. This way, you may actually get things done ;)

- Aperry

I may be blinded by scientists' prejudices on engineering, but is it really appropriate or accurate to describe the work of an engineer as application of the scientific method?!

  • Well, in a broad sense, yes, I think so. However one has to be brutally honest to do so, and admit that an engineer assumes a certain fixed price per human life when setting safety standards, i.e. the "will hold 100 tons but will not hold 110", "recall the Pinto or not", etc. They will now be more likely to do that in skyscrapers after 9/11. The scientific method in this case is the correlation data that tells you what tolerances you're working with, and each artifact, e.g. bridge, or airplane, you build, is like an experiment. If and when it falls down, you learn something. The forensics are most obvious in air crashes... it's the full scientific method applied to that case and generalized to all aircraft of that model, pilots and mechanics of that airline, etc., and whatever they learn goes back into the building and maintenance process. That's the tightest engineering loop you're likely to see... except in the military where they do the same thing but put the price of the training of the crew and some nominal compensation (pensions paid to families) into the equation. So, more important than the method is the means of risk assessment...
  • note also that software engineering "is" engineering in the sense of the scientific method and each service, i.e. online service whether processor is local or not, being an experiment, and "isn't" engineering in the sense of direct risk of bodily harm to the user, except in military applications or certain extreme civilian emergency response situations where life and death decisions are made by the software itself and the human must trust it completely... which ain't often.
    • According to American Society of Engineering Education (ASEE), software engineering/computer science is considered as an engineering field. In fact, it is the third largest field by number of graduates, after mechanical and electrical. Engineering statistics 2003. --JamesTseng 16:34, Oct 27, 2004 (UTC)

[edit] Nav point #1

      • What a bullshit! I am a computer science researcher and I never considered myself an engineer. Moreover, it is blasphemy to call these people and these people engineers. Software engineering, as practical application of computer science, could perhaps be considered an engineering field (though it's a moot point), but computer science itself (???) - give me a break. I am not an American and I don't give a damn what ASEE says - I'd rather rely on opinion of a professional computing society like ACM. - 195.252.80.127, Mar 13, 2005 (GMT)
Agree. They all look like mathematicians who dont know one end of a 'driver from the other to me. BTW thers nothing wrong in that!.--Light current 23:11, 14 November 2005 (UTC)

Any interest in articles about the History of Engineering? What I see this covering would include:

Just compiling this list, & testing the proposed links show some areas that need attention. -- llywrch 01:14 Nov 21, 2002 (UTC)

I think a historical overview of engineering technology would be excellent. More detailed lengthy chapters could be spun off to articles as appropriate. user:mirwin

Regarding the first sentence: "Engineering provides the plans to (re)produce, process, or control artifacts" However, engingeering does not necessarily deal with artifacts, it can deal with aspects of the natural world that would exist even if there were no humans. For example, you can engineer a systems to locate, catch and process fish from the sea. These fish, especially before being caught, aren't artifacts. So, I think the definition that engineering deals with artifacts is too restrictive. User:Ike9898

Agreed. I widened the definition slightly. I still don't like it, though. If I were starting from nothing, I would say something like "Engineering is the application of scientific knowledge and practical experience to the production or processing of useful objects." I put in the word "useful" to exclude artistic creation. Also, I prefer definitions that begin "X is..." rather than "X provides..." -- Heron

I made some significant changes to the page, many based on 'talk-page' comments. I also added a bit about engineering as a profession and a little about margins of error. Please review and comment User:Ike9898

Engineers apply integration of thought to specific application or purpose. As we go deeper into this new era of High Technology, There is going to be a merging of Engineering, Architecture and Information Science and the interpretive lens of Engineering is going to lead the way.

A Design Engineer alway integrates to application or purpose. And when he [she] interprets, he always interprets every process or component as an interdependency of the integrated whole.

Engineering in the past has alway applied Science. Engineering today is about to reinterpret Science. The biosphere through the lens of a design engineer is "Context Driven Dynamic Architecture integrated to Automation." Our viewing lens for interpreting is entering the next level of Advanced Logic >"Context Driven Dynamic Architecture" and it will take the engineer to lead the way. His [her] interpretive lens is imperative. That interpretive lens will seemlessly integrate Physical Chemistry, Organic Chemistry and Biochemistry. Biology as the "logical study of living things" will enter a whole realm of understanding.

Through the lens of an engineer, all integrations are context driven > integration of thought to application or purpose. The context of the integration is embedded in the integration's interdependencies and requirements that have to be satisfied to enable the integration's application or purpose.

That definition brings a new term to the floor > "threshold enabled." A lot of processes of an integration don't exist until specific interdependencies are satisfied to enable them.

The context of a computing system is much more than the Operating System. In PCs, it is only because Intel and Microsoft pre-integrated the hardware and the software that makes the operating system useable.

The lens of engineering is about to give a whole new meaning to the term "Analytic Science." This is a wonderful time in which to be alive! All other generations were searching for what we are about to extract > the context of the integrated whole and the True Narrative! The lens of Engineering is going to lead the way. Have a great day!

[edit] Its history and its etymology

Rogper, we can't have to different etymologies and claim that they are both correct. As proof of the one currently in the text,

The American Heritage® Dictionary of the English Language: Fourth Edition. 2000.

Middle English enginour, from Old French engigneor, from
Medieval Latin ingenitor, contriver, from ingenire, to
contrive, from Latin ingenium, ability.

If you have a source for yours, we can list them both with a note to say that they are alternatives. Rmhermen 17:22, Oct 22, 2003 (UTC)

Yes, I have sources. I will get better one that I can referate to, right now it has only been said by one. When I have time, I will go to the library and look up this issue. Anyway, its origin is from 'encignerius', related to 'ingignerius'. Maybee there is some inter-connection between the words, I don't know. It is known to have been used in 1196 for the meaning building contractor of war. The Swedish national encyklopedia [1] says exactly the same as your America Heritage Dictionary, but I think they have wrong. :-) Otherwise I have wrong. :-( // Rogper 17:39, 23 Oct 2003 (UTC)

Engineer is one of those words that have evolved along several parallel paths. All versions start with the Latin ingenium (skill). The OED believes that the main path was:

ingenium -> Old French engigneor (contriver, advisor) -> Middle English engyneour -> 16C enginer/inginer -> 17C engineer/ingineer,

which is similar to the American Heritage version. The OED notes an alternative route:

ingenium -> Old French engin (skill or machine) -> English engine -> 16C enginer/inginer -> 17C engineer/ingineer.

Eric Partridge (in Origins) gives precedence to the second route. A third route, mentioned by the OED as an influence on the first two, but not the main origin, is

ingenium -> *ingeniarius -> Old French engignier -> English engineer.

This appears to be Rogper's version. The OED has a long and complex article on this word, so it's not surprising that there are Wikipedians with differing views. -- Heron

I've probably wrong. But note that it seems to be some 500 year gap between it was first used and when it is etablished in non-Italian countries, if I'm having right. Wonder how people like those editors in OED and Am. Hert. construct a word's etymology. SAOB (the 'Swedish OED') notes in its articles when the word was first used in written form. Anyway it was not used before 17C in Sweden, since there was a "dude" (called Cristopher Polhem a.k.a. 'the (Swedish) father of mechanics' ) that tried to start 'Laboratorium mechanicum'; so in a sense, in contradiction to the Am. Herit. and honoring the 'Patridge-path'.Anyway, I'm not very sure so I got to check before doing anything else. // Rogper 21:58, 26 Oct 2003 (UTC)

I suppose that it wouldn't hurt to mention a couple insightful jokes on engineers:

  • To an optimist the glass is half full. To a pessimist the glass is half empty. To an engineer the glass is twice as big as it needs to be.
  • A priest, a doctor, and an engineer were playing golf one day, but they were stuck behind this group of very slow-moving golfers that just couldn't seem to hit the holes. They asked the course owner, who knew them, what the deal was with those folks. He said, "Those are blind war veterans. We let them play here for free whenever they want." The priest said, "Oh, I will pray for them!" The doctor said, "I hope medical science can one day help them." The engineer said, "Why can't they play at night?"
  • There was an engineer who had an exceptional gift for fixing all things mechanical. After serving his company loyally for over 30 years, he happily retired. Several years later the company contacted him regarding a seemingly impossible problem they were having with one of their multi-million-dollar machines.
They had tried everything and everyone else to get the machine fixed, but to no avail. In desperation, they called on the retired engineer who had solved so many of their problems in the past.
The engineer reluctantly took the challenge. He spent a day studying the huge machine. At the end of the day, he marked a small "x" in chalk on a particular component of the machine and proudly stated, "This is where your problem is." The part was replaced and the machine worked perfectly again.
The company received a bill for $50,000 from the engineer for his service. They demanded an itemized accounting of his charges.
The engineer responded briefly:
One chalk mark ................. $1
Knowing where to put it ... $49,999
Feel free to delete this if you deem it clutter. - "Nocturnal"

[edit] major branches

I removed Mechatronics, Petroleum Engineering and Structural Engineering as being not major branches. Mechatronics is a subbranch of both electrical and mechanical, structural is a subbranch of civil, and petroleum is a minor branch. Theon 15:21, Aug 23, 2004 (UTC)

  • Theon, I would like to add and remove some engineering fields, judging from the membership of their respective professional associations. On the other hand, removal of above engineering fields is not a discrimination against them, but rather, they do not hold substantial representation of engineers. --JamesTseng 23:45, Oct 26, 2004 (UTC)

I have replaced the existing list, which required a certain amount of inference from the ASEE reference (and could thus be interpreted as original research), with a list that is based on a National Society of Professional Engineers reference which explicitly identifies its list as the "major branches of engineering". --Allan McInnes (talk) 20:49, 6 July 2006 (UTC)

Expanded this with some comments on the peculiar characteristics of engineering research; engineering is more than simply the application of science to practical means. The whole entry could possibly do with a re-write, as it's a bit clunky, no doublt due to people like me coming and adding bits piecemeal... Jakob 21:54, Sep 19, 2004 (UTC)

[edit] Examples of Engineers in Cultural Presence -- Ralph Nader

Ralph Nader has engineering background? I looked up Princeton's web site, it says that Nader received A.B. in Politics and Economics in 1955. After his undergraduate education, he moved on to Harvard Law School. Student Body Politics --JamesTseng 16:29, Oct 27, 2004 (UTC)

Gone. Vsmith 12:51, 21 Dec 2004 (UTC)

Whoops. I did that a while ago. My source was bad.

To make up for it, I'm adding two people who verifiably started out as engineers.

Nuclear Physicist Edward Teller and New York City Mayor Michael Bloomberg --Lent 06:19, 28 February 2006 (UTC)

[edit] Geomatics Engineering

I put Geomatics Engineering back up in place of "engineering management". I mean come on, what the hell is that? Either you're an engineer or not.

  • Apparently, Geomatics Engineering is not a "top 15" engineering discipline. How about change the heading to "top 14" and remove GE? Also, I put "engineering" with "material science", otherwise it wouldn't be engineering. --JM Robert 06:17, Nov 22, 2004 (UTC)

[edit] Iron Ring

I'm not a canadian and so that probably explains why I never heard of the Iron Ring. Anyone care to decide if a link to ironring.ca (posted by an anonymous) is relevant? Cburnett 02:21, 8 Mar 2005 (UTC)

I've had look at the two Engineering Ring links, and I would get rid of this one: The orgin of then Engineer's Ring, and possibly keep the other one, but I'd prefer to see it as a link next to the paragraph about the ring. --John 11:01, 8 Mar 2005 (UTC)
In Canada, this iron ring is an important symbol of Engineering. In Quebec, there is even this strange rumor that the rings are made from piece of a bridge that felt into the St-lawrence river. It's just a rumor but it's a perfect exemple of what the ring represents. -- Sepper 23:15, 8 Mar 2005 (UTC)
My opinion: this Iron Ring thing should be launched. 29 Dec 2005

[edit] Engineering vs. Science

When my daughter was between her 3rd & 4th year in high school she attended a week long summer institute in science & engineering. On the first day the students were asked if they knew the difference between science & engineering and she raised her hand and answered, "Engineers are interested in how high and steep you can pile dirt and scientists are interested in what the dirt is made of." My daughter is now working on a PhD in geophysics at MIT. Jay Gregg 22:58, 27 August 2005 (UTC)

  • Good for her. How is this relevant? My comment on this section: It claims science and engineering are two separate things, yet Applied Science claims to be synonomous to engineering suggesting that engineering is a type of science. Not very consistent. Any suggestions out there? [this edit by 24.170.192.184 Steven McCrary 23:23, 22 October 2005 (UTC)]

Greetings all. Engineering is not merely the application of science, pure or not, nor is it even predominately the application of science. Engineering is not a part of science; engineering is a discipline of technology (not science), it existed prior to science, and exists separately from science. Engineering applies technical knowledge to solve human problems, including science, technology, mathematics, and practical experience. To say that engineering is the application of pure science is incorrect. I have reverted those edits that make that statement. Steven McCrary 22:51, 22 October 2005 (UTC)

I like to look at at this way: the goal of engineering is synthesis, while the goal of science is analysis (bumper sticker version: scientists want to understand the world, engineers want to change the world). Of course, each discipline uses some of elements of both analysis and synthesis to accomplish its goals. In fact, that's one of the hallmarks of professional engineering - synthesis without analysis is basically just tinkering. But science and engineering are fundamentally different disciplines with fundamentally different goals. The engineer, as you rightly point out, will use the tools of science, but also a lot of other tools (including previous experience) to accomplish his job. It's a pragmatic approach to problem solving. --Allan McInnes 15:46, 27 January 2006 (UTC)
In addition, the engineer attempts to solve a problem in order to provide a usable solution, within constraints (such as cost— which is where "software engineering" becomes almost an oxymoron, since software types seem never to care about cost). The scientist is looking to advance knowledge (and recognizes no constraints), and is unconcerned with whether the solution is usable or not. The applied scientist does seek usable solutions to generally practical problems, but disregards constraints. He tends to be interested in advancing the state of the (engineering) art. ⇒ normxxx| talk ⇒ email 03:18, 25 February 2006 (UTC)

[edit] New Engineering Wiki

Engineering Wiki is a wiki entirely dedicated to collecting information about Engineering. I invite you to join this wiki. [this edit by 219.65.122.162 Steven McCrary 23:21, 22 October 2005 (UTC)]

[edit] Top 15?

  • On what basis is it Top 15 Branches,i hope its not a POV.—The preceding unsigned comment was added by 59.144.18.157 (talk • contribs) .

[edit] DesignBreak.org

An anonymous user keeps adding links to designbreak.org to the "external links" section of this article. I have removed these links twice, because I consider them linkspam. Designbreak.org is asserted to be "A new open design initiative which advocates for open designers, and their designs." Based on that assertion, I'm prepared to concede that designbreak.org might be a relevant external link for the Open design article (where I notice it is also listed), but it does not seem particularly relevant to an article on engineering as a whole. If there's some reason why designbreak.org should be listed in the external links of this article, please outline that reason here, instead of continuing to add the designbreak.org link without justification. Thanks. --Allan McInnes (talk) 23:56, 10 February 2006 (UTC)

[edit] Recent Overlooked Vandalism

Please do not get so wrapped up in editing (or counter-editing) that you overlook recent vandalism, such as that which I just reverted from several days ago.

⇒ normxxx| talk ⇒ email 02:55, 25 February 2006 (UTC)

[edit] Definition of engineering

This article contains a number of factual errors. Most significantly it opens with the following misleading, even meaningless, statement:

Engineering is the application of scientific and technical knowledge to solve human problems.

It is an unsatisfactory definition the following reasons:

  1. It fails to distinguish engineering from similar fields. Medicine, for example, could equally well be described as "the application of scientific and technical knowledge to solve human problems".
  2. The phrase "to solve human problems" is too vague also. I might have a problem of knowing what shoes to wear. Engineering is not likely to help solve it.
  3. It implies a dependence on science. Systematic science based engineering as a discipline is only about 200 years old (originating in institutions such as the École Polytechnique) and the underlying sciences originated in the seventeenth century (for example in Galileo’s Two New Sciences). For this reason the definition effectively rules out creations that can justifiably be described as engineering such as ancient roads, bridges and irrigation systems. If we include naval architecture as an engineering disciple it also rules out things like Greek triremes. In fact the Romans demonstrate that you can take both science and mathematics out and still get engineering but if you take the design and creativity out you are likely to get nothing.

Unless someone can suggest how to modify the definition to address these deficiencies I propose replacing the definition with one that recognizes design, which identifies engineering with its products and does not imply dependence on science or mathematics. IanWills 00:47, 19 June 2006 (UTC)IanWills

[edit] See also

The first link (automotive engineering) under 'see also' links back to this page... methinks that should be fixed?

Removed. Vsmith 22:11, 30 June 2006 (UTC)

[edit] Engineering by Country

Hey I suggest for this article to add a section with a list of countries, which those link to articles detailing info about engineers and their invents on each country. All this 'cause there are such many invents developed through history and engineers on all countries. This should give a very strict order to engineering related articles. --Walter Humala 01:26, 23 August 2006 (UTC)

[edit] Merge proposal

For discussion of the recently proposed merge of this article and Engineer, please see Talk:Engineer#Merge?. Thanks. --Allan McInnes (talk) 20:19, 22 September 2006 (UTC)

[edit] "Major Branches" section

I've just reverted changes to the "Major Branches" section of the article. In answer to the question included in the article comments about why the list shouldn't be longer, I see two reasons:

  1. A complete list of all branches of engineering would completely dominate the article, which isn't particularly good style. Besides, the Fields of engineering article already provides the same information, and is already included as a {{main}} link. I see no reason to duplicate the same information here.
  2. The current list is referenced and verifiable, which is preferable from a policy point of view.

--Allan McInnes (talk) 17:40, 15 October 2006 (UTC)

[edit] Fields of engineering merge proposal

Please see the discussion at Talk:Fields of engineering --Allan McInnes (talk) 17:48, 15 October 2006 (UTC)

FYI -- problem solved (likely ...). Both merger proposals deleted. Many links between the articles added to help readers navigate them. FactsAndFigures 16:22, 21 October 2006 (UTC)

[edit] "Cultural presense" section

The last sentence of this section, "While it appears Engineers still only need..." is opinion, and perhaps factually incorrect as well. Hypothetically speaking, a young, recent engineering graduate could receive respect from the public. This sentence seems inappropriate for an encyclopedia article. Hildenja 06:22, 24 November 2006 (UTC)

Agreed. I've removed that sentence. The rest of the section could use a bit of a cleanup too... --Allan McInnes (talk) 17:27, 24 November 2006 (UTC)

[edit] "The" engineering design process?

I'm posting the question on this talk page because I'm not an engineer. There is a page that suggest by it's very title that there is only one engineering design process. That seems a little odd. The page is The engineering design process. Is this accurate? Oicumayberight 00:46, 30 November 2006 (UTC)

There isn't really a single design process in the sense that every engineer follows exactly the same steps to a design. And there are certainly variations in the design process across discipline and industry. That said, in the abstract there is a common approach that might be referred to as the "engineering design process" (although a good argument can be made that it is more generally the "problem solving process" - for example, note the similarity with these process steps). A quick Googling shows several other websites that describe an engineering design process that is roughly the same as that described in the article you're concerned about, e.g here, here, or here. However, note that each process description, while describing essentially the same process, breaks down the steps of the "design process" in slightly different ways. My concerns with The engineering design process article are thus threefold:
  1. It seems under-referenced, and presents only a single way of dividing up the design process when in fact there isn't a single agreed way to define the process steps
  2. The tone of the article is not particularly encyclopedic, and it borders on a how-to guide at times
  3. It's not clear to me that "the engineering design process" warrants a separate encyclopedia article, since there isn't much that's engineering-specific about it - the steps presented in the article are fairly generic problem-solving process steps, or alternatively represent a generic design process.
--Allan McInnes (talk) 04:53, 30 November 2006 (UTC)

I agree that the reference article is not very useful as is, but could be marginally useful with some modifications: 1) strangely, there is not mention of the DESIGN of the product in the 10-step process - hard to engineer a product without doing that! 2) There should be a disclaimer at the start of the article that what follows is just one template or example, that that there is no one generic engineering design process.

Better though to have the referenced article, if there is to be one, drastically rewritten. This topic is one of major importance to engineering organizations, and many texts and papers have been written about it. The reviewer who noticed this, even as a non-engineer, has done a service by noticing this disparity. But these comments should be transfered over to the referenced article to be effective.

Tony 15:36, 12 December 2006 (UTC)

[edit] Computer Use section

1. The statement "The application of computers in the area of engineering of goods is known as Product Lifecycle Management (PLM)" is incorrect. PLM is just one, rather minor, application of computers to engineering (see PLM page in Wikipedia).

A more pertinent area of description would be Computer Aided Engineering (CAE), a set of computer programs and systems oriented to carrying out engineering calculation, analysis, and visualization to enhance an engineer's capabilities, really an extension of CAD. PLM is really only a repository and manager for the data created by CAD and CAE programs.

2. The sentence: "Electronics engineers make use of a variety of circuit schematics software to aid in the creation of circuit designs that perform an electronic task when used for a printed circuit board (PCB) or a computer chip" could use additional commentary:

a) Software is not only oriented to circuit schematics for PCB and IC (Integrated Circuit) design, but also to layout software for PCBs and ICs. Such software is as important as circuit design.

b) It should be pointed out that today's ICs are so complex (e.g. up to 1 billion transistors) that manual circuit design and layout is impractical if not impossible. This is also true for complex PCBs.

Tony 15:23, 12 December 2006 (UTC)

Actually CAE (or CAx) is a group of applications under the topic of PLM. Do not get PLM confused with PDM (also part of PLM) which manages data. PLM involves creation as well as management of product data. Freeformer 17:01, 12 December 2006 (UTC)

It might help to have an explanation of this fact in the article (I'd never heard it before, and I've worked as an engineer in several different industries for about a decade now). A reference or two would also be nice :-)
Retrieved from "http://en.wikipedia.org../../../e/n/g/Talk%7EEngineering_0915.html"