What makes a good engineering manager?

Order Description

a report on “what makes a good engineering manager?”

SUGGESTED TEXT: “PROFESSIONAL AND TECHNICAL WRITING STRATAGIES” by VanAlstyne and Tritt, Fifth Edition, Prentice Hall Publishers, 2002, ISBN 0-13-041279-1.  This is an optional book that can assist you in completing the project.  Other books about writing technical material may be found on library reserve.

CATALOG DESCRIPTION: In this course the student will apply classroom learning in the execution of a project of substantial magnitude.  Together, the student and faculty will select a topic that focuses on an application on one of the eight course areas, or one that is more broadly based.  Faculty will evaluate a detailed student report.

COURSE OBECTIVES:

1.    To achieve significant expertise in engineering projects due to an in-depth, integrated study of such projects.
2.    To work independently in applying previously learned concepts to develop solutions to specific problems
3.    To demonstrate appropriate written and oral communications skills in the development and presentation of a detailed project.
4.    To demonstrate the ability to select and utilize appropriate computer tools.

COURSE CONTENT: The student, in consultation with the instructor, will select a project to study which involves an in-depth, integrated analysis of a real world problem in engineering management.  The instructor must approve any potential project.  The student will consult with the instructor as required and will prepare an outline of the project to be discussed with the instructor at mid term. The student has the option of submitting a rough draft of the final report for analysis and discussion before the final draft is due. The final results of the study are to be reported in both oral and written form. The written report should be in the range of 15 to 20 pages and must include appropriate footnotes or documentation of sources cited and will also include a bibliography.

SUGGESTIONS FOR WRITING*

A format for an academic paper might be:

1.    Define the problem.
2.    Review of the literature.
3.    Results.
4.    Discussion.

When to document (via footnotes, for example):

1.    For ethical acknowledgement of sources.
2.    To establish authority and credibility.
3.    For efficient additional study by the reader.
4.    To avoid any possible accusations of plagiarism.

* Taken in part from “PROFESSIONAL & TECHNICAL WRITING STRATEGIES” by Vanalsyne and Tritt, Prentice Hall, 2002.

PROJECT IN ENGINEERING MANAGEMENT

I.    USE OF DOCUMENTATION (FOOTNOTES).

1.    For the ethical acknowledgement of sources.
2.    For the establishment of authority or credibility.
3.    Efficiency for further studies.

II.    A FORMAT FOR A TECHNICAL PAPER.

1.    Define the problem.
2.    Review the literature.
3.    Results
4.    Discussion and conclusions.

The above was taken from VanAlstyne and Tritt.