Jeanette Said:

how to write internship report on civil engineering?

We Answered:

search some samples from www.docstoc.com and www.scribd.com

Dianne Said:

I have to write an abstract report on something to do with electronic engineering.?

We Answered:

An abstract is an analysis of an analysis. So basically you have to find a critical essay on electronic engineering and write a report on that essay. You have to figure out the thesis (why the person's argument is) of the essay and use that as your thesis. Your essay is a summary of the critical essay and in the last paragraph you state your opinion on the essay. Whether you agree or disagree with the critical essay, or whatever your opinion is. Its not that fun but you dont have to think of your own thesis and your essay is basically a summary of the critical essay.

Gertrude Said:

an engineering/technology mind speaking to the business mind?

We Answered:

This is one of the most thought provoking questions I have ever come across. I am a business professor.
Some of my peers also have degrees in physics or chemistry and I DO NOT.

My son is an engineer and we have
a hard time communiting about what each of us calls simple stuff.

He wants exact specifications in order to answer a question I ask and
i WANT only what is the end objective and what are your resources and
who are your competitors.

38 yrs ago, I created the non-college
business incubator and I found that
many science inventors only invent
for fun, they do not try to solve current problems and business
is interested in earning $ by servicing
known or unknown markets.

Thus, many items produced for the market place have no home --yet!
The fax took 35 yrs to find a market.
Yet, the pet rock sold immediately!
Go figure!

A car engine was made by a mechanic but designed by a scientist.
YET, when we consumers go into the shop for maintenance, what used to be a 5 min repair or action [changing
oil or an oil filter] can take 30 min to an hour on different vehicle].

thus, scientists and business people
did not get together.

by the same token, science often
discovers things-ideas for which
there is not market and a market
is immediately created!

All that said, if a scientist would take their ideas or gizmos and find a business plan template, I am betting
both scientist and business person
would have an easier time communicating because they both have the desire to "fiscally" succeed
and a biz plan combines emotion
and hard data.

Maureen Said:

Need to write a report. The subscribers are people who claim their Engineers.?

We Answered:

You question is not really clear.

I will make these comments. In addition to knowing the MTBF you also need to know the cost of equipment failure. Does it destroy the machine in question or does it just result in down time and loss of revenue.

It has been my experience that if you can clearly show a cost savings to take a specific action then managers will always follow that course but you need to have good documentation to back up your plan. Logic and common sense almost always wins.

Yolanda Said:

How do i write like an engineer?

We Answered:

This is a simple question. I can give you 10 easy steps

Basically, as an Engineer, you want to write such that nobody will dispute your dominance of the subject matter. If someone can understand what you've written, then they can disagree. If they can't, then they just have to take you at your word.

1. Use as many acronyms and as much jargon as possible. Like painting all your street signs in broken German, it'll make sure most people can't understand your deusche gagen stand stark aus sprechen.

2. Small blocks of text,or simple lists, are a definite NO. Structuring your information in an easy to read, easy to understand manner, is terrible, not how an Engineer writes.

3. Using drawings to explain things is definitely bad. DO NOT use drawings, whatever you do.

4. Definitely use more words than you need. A big block of text makes you look smart, where a small, precisely worded sentence or two saying the same thing makes you look dumb. Engineers need to look smart!

5. Remember, the point of engineering writing is NOT to express ideas, but to spend as much time as possible on the clock to get your 40 hours out of the way. There is no audience. Ignore anyone who tries to read what you've written, because they're not the audience, because we've already established there is no audience.

6. Remember to throw thinly veiled personal attacks into everything you write. This way, you look smarter than everyone else, and at the same time make other people realise their place in the world.

7. Always throw vague conjecture alongside facts, so nobody really knows which are which. You must be certain to NEVER test your conjectures, and if you do, CERTAINLY never document this process. You're an Engineer, and thus infallible. Your opinion might as well be fact.

8. Engineers are scatterbrained and elusive. Always make sure you provide far more information than is required, and make doubly sure that important facts don't stand out. You're smart enough to realise what's important, anyone else should be too, or they're not worth dealing with.

9. Never include references to other documents you got your information from. Nobody will ever want more information about something. Nobody will ever want to check a fact, and shouldn't want to, since you're infallible. It's just a waste of company resources.

10. Finally, when you're using equations, there are two schools of thought. Either include long, unexplained derivations that anyone reading "should" explain right in the main text taking up page after page and making the document inaccessible for the proles, or don't include them at all. Never include a neat appendix which you reference for additional information about numbers derived or equations used.

Follow these steps, and you'll definitely write like an unemployed engineer(with no degree).

Don Said:

i want to write a detailed engineering & design report on IT integration.?

We Answered:

The main concepts you'll need to address are covered in the IETF RFCs. Lately, there have been a number of entries dealing with iSCSI and the protocols associated with LANs. If you need a way to break down your topic into categories that will be sure to cover the main areas, you should look over the RFC indexes and download some of the files numbering in the 5000-6000 range, which are pretty recent. In addition, the references at the end of each article will give you a good start at making sure you've got the main points without wasting time hunting around for documents. Try RFC1972, RFC3270, and RFC4173 to start.