- EG 32 Syllabus -
Fundamentals of Engineering 2
Spring Semester, 2012
INSTRUCTOR: Jeffrey N. Denenberg, PhD.
LECTURERS: Interdisciplinary Faculty Team
EMAIL: [email protected]
GOOGLE
VOICE: (203) 513-9427
WEBSITE: http://doctord.webhop.net
OFFICE HOURS: One hour prior to Monday class
and Wednesday class, McAuliffe 102
(And
After Wednesday Class)
CLASS HOURS: 6:00
p.m. - 9:00 p.m. Tuesdays (Section 01)
2:00 p.m. - 4:30 p.m. Wednesdays
(Section 02)
LECTURE ROOM: McAuliffe
102 (Both Sections)
TEXTBOOK: Exploring
Engineering, Academic Press, Ed.
2, 2010 (ISBN 978-0-12-374723-5).
SUPPLEMENTAL: Engineering by Design, G. Voland, 2nd
Ed, Pearson Prentice Hall 2004 (ISBN 0131409190).
EG31 Syllabus
SOFTWARE: PingLive, (Attendance and Pop Quizzes)
– you will receive a PayPal invoice for $19.95
SUMMARY COURSE DESCRIPTION
This two-course sequence provides core knowledge and
competencies in engineering and computer science to engineering students in
their first year. Topics include computer-based computational skills,
principles of engineering design and software design, digital logic and
programming, laboratory data acquisition and reporting, along with probability
and statistical analysis of data, design analysis techniques, implementation of
engineering projects. In EG 32, hands-on team projects are core learning
experiences. They are structured to introduce students to the implementation of
principles of design and engineering methodologies, system engineering
management, and presentation skills. Guest presenters and field trips augment
these courses, which are taught by interdisciplinary faculty teams. Pre-requisites or co-requisites are MA 125
and PS 15.
COURSE LEARNING
GOALS
EG32 introduces
the student to the systematic design process and to the application of
statistics to engineering data. The student is expected to conduct the active
and diligent study needed to meet the following learning goals.
® Understand the purpose and methods of
the systematic design process
® Appreciate how to work as part of a
successful interdisciplinary engineering team
® Understand how a design specification
of performance and characteristics supports the user need statement
® Understand how verification confirms
that the design specification requirements are met
® Learn to communicate experimental
procedures and results through written engineering laboratory reports
® Learn how engineering analysis is
conducted with MathCAD
® Learn to apply Excel and Word in
engineering written communications
® Learn to apply PowerPoint for oral
design reviews
® Learn to apply Project Planning tools
in a design project
COURSE LEARNING OUTCOMES
After
meeting the EG32 learning goals, the student is expected to have the following
abilities.
® Prepare a user need statement for a
hardware or software design
® Maintain a continuing archive of team
meeting notes.
® Create function and morphological
matrices
® Write design specification requirements
® Identify test, demonstration,
measurement, or analysis for the verification of design requirements
® Prepare and present a team design
review
® Prepare an engineering design report
® Prepare an engineering lab report
including tabulation and charting of data
® Conduct a basic analysis with the aid
of Mathcad
STUDENT RESPONSIBILITIES
Attendance
EG32 is a fast-paced course to introduce the student to a range of subjects and skills. A substantial portion of a topic would be missed by being absent from even a single session.
® Students
are required attend each regularly scheduled session.
® Releases
are to be submitted to the instructor prior to missing a specific class for
athletic participation.
®
The student
is responsible for acquiring all notes and assignments from any missed class.
® Field
trip participation is not mandatory unless the student registers with the
instructor to attend. If a student commits to a field trip but doesn’t attend,
Professionalism points will be subtracted from the final grade.
Homework
True
learning of a subject requires thoughtful and thorough completion of homework
study and written assignments in a timely manner (hint: if you can teach the
lesson…you’ve learned it). Also, since an underlying objective of EG32 is to
encourage a sense of professional responsibility, students are required to turn
in their assignments on time.
® Students
are expected to spend nine or more hours per week on EG32 homework and project
assignments.
® Written
and problem assignments are to be prepared by each individual student unless
specifically identified by the instructor as a team effort. Duplicate written
assignments will be returned without a grade.
® Credit
is to be given in footnote format for information you extract or download from
published sources and incorporate into your lab or project reports.
® Since
homework submittals are technical communication, grammar, spelling, appearance and organization will impact
your grade.
Mentor and Reflections
® The
Mentor system along with the course web site will be used to manage this
course.
® Students
should submit their assignments into Mentor for archival and grading.
® The
Reflections functionality on Mentor will allow you to record your thoughts on
the learning process in EG32. There will
be about 4 specific reflection assignments, but feel free to use this system as
your diary on your learning experiences.
® There
will be a Threaded discussion group available for interaction among your peers
and instructor on Mentor. Use it to
share information and perspectives as well as to get help in EG32 and other
courses. Activity in the discussion is a
primary measure of class participation.
Exams
® Exams
can be taken only during the scheduled sessions.
COURSE REQUIREMENTS
Materials
®
The textbook is to be brought to every
class for reference during lectures and open-book exams.
® A
stapler is to be used for fastening multiple pages of homework assignments.
®
A USB Flash Drive may be used to save
any computer files created during class.
Email
®
Each student is expected to have an email address
for receiving class-related communications.
®
Computer files generated in the classroom may be
emailed to your personal account for retention and printing.
COURSE AND ASSIGNMENT GRADING
A final grade below C- is assumed to reflect failure
on the part of the student to meet the Course Learning Goals.
Final grades are weighted as follows.
EG32 Results –
Final GradeS, Spring 2012
Tuesday Evening Class, Wednesday Afternoon Class
INSTRUCTOR
FEEDBACK
® Instructors are available for
discussion of lecture topics or to provide feedback on graded assignments
following each session, via email or by appointment.
FREE STUDY ASSISTANCE
Tutoring
in engineering, math, and science courses is available between 6 p.m. and
® For alternate help with math
courses, contact the Math Center, x2515, BNW 12.
® For
help with writing papers, contact the
Disability
If you have a documented disability and wish
to discuss academic accommodations, please contact: David Ryan-Soderlund at Academic
and Disability Support Services (203) 254-4000, x2615, or email
[email protected], and notify the course instructor within the
first two weeks of the semester.
ACADEMIC
DISHONESTY
Students are sometimes unsure of what
constitutes academic dishonesty. In all
academic work, students are expected to submit materials that are their own and
are to include attribution for any ideas or language that are not their
own. Examples of dishonest conduct
include, but are not limited to:
•
Falsification
of academic records or grades, including but not limited to any act of
falsifying information on an official academic document, grade report, class
registration document or transcript.
•
Cheating,
such as copying examination answers from materials such as crib notes or
another student’s paper. .
•
Collusion,
such as working with another person or persons when independent work is
prescribed. .
•
Inappropriate
use of notes.
•
Falsification
or fabrication of an assigned project, data, results, or sources. .
•
Giving,
receiving, offering, or soliciting information in examinations.
•
Using
previously prepared materials in examinations, tests, or quizzes.
•
Destruction
or alteration of another student’s work.
•
Submitting
the same paper or report for assignments in more than one course without the
prior written permission of each instructor.
•
Appropriating
information, ideas, or the language of other people or writers and submitting
it as one’s own to satisfy the requirements of a course – commonly known as
plagiarism.
Plagiarism constitutes theft and deceit.
Assignments (compositions, term papers, computer programs, etc. .)
acquired either in part or in whole from commercial sources, publications,
students, or other sources and submitted as one’s own original work will be
considered plagiarism.
•
Unauthorized
recording, sale, or use of lectures and other instructional materials.
In the event of such dishonesty, professors
are to award a grade of zero for the project, paper, or examination in
question, and may record an F for the course itself. When appropriate, expulsion may be
recommended. . A notation of the event is made in the student’s file in the
academic dean’s office. The student will
receive a copy.
Use of guest lecturers
gives the student an opportunity to interact with practicing engineers having
industry and research experience in their topic areas. The Instructor and guest
lecturers often provide copies of their presentations (via the on-line links
below) for home study but the student is still expected to actively follow the
discussion and take written notes to record clarification or additional
insight.
Use of
guest lecturers gives the student an opportunity to interact with practicing
engineers having industry and research experience in their topic areas. Guest
lecturers often provide copies of their presentations for home study but the
student is still expected to actively follow the discussion and take written
notes to record clarification or additional insight.
Session |
Tues (01) 6:00-9:00 |
Wed (02) |
EG32 Topic (Spring 2008) |
Instructor |
Reference |
Assignment |
Notes |
I |
Jan 17 |
Jan 18 |
EG31 Final Exam Reprise, EG32 Intro and Digital Logic Review |
Denenberg |
Get ahead in your reading |
|
|
II |
Jan 24 |
Jan 25 |
Systematic Design Process INTRO TO DESIGN |
Denenberg |
Text p. 309-322 |
Define your Project, Write
a Problem Definition (PPT) |
|
III |
Jan 31 |
Feb 1 |
Team Design Project Planning INTERDISCIPLINARY TEAMING, S/W TOOL |
Denenberg |
Prepare Initial Project
Plan |
|
|
IV |
Feb 7 |
Feb 8 |
Digital Logic Circuits (Multisym) [Lab] INTRO TO COMP. ENG; SW
TOOL; LAB |
Denenberg Craciun |
Text: Multisym Files: html |
Text Chapter 9: # 1-9 |
|
V |
Feb 14 |
Feb 15 |
Programming in MatLab |
Denenberg |
|||
|
Feb 20 |
|
President’s Day - No class |
|
|
|
|
|
Feb 21 |
|
“Tuesday is Monday” Follow
Mon. Sched. ! |
|
|
|
|
VI |
Feb 28 |
Feb 22 |
Engineering Standards, CAREER SELECTION |
Denenberg |
|
|
|
VII |
Mar 6 |
Feb 29 |
Intermediate
Exam |
|
|
|
|
VIII |
Mar 20 |
Mar 7 |
Exam 1 Results,
Methods & MS Math |
Denenberg |
|
||
|
Mar 13 |
Mar 14 |
Spring Recess - No class
all week! |
|
|
|
|
IX |
Mar 27 |
Mar 21 |
Materials Testing and Data Reporting INTRO TO MECH ENG; COMMUNICATION |
Denenberg |
Text: |
Lab Report |
|
X |
Apr 3 |
Mar 28 |
Computer
Networks |
Denenberg |
|
|
|
XI |
Apr 10 |
Apr 4 |
Design Analysis Procedures COMMUNICATIONS |
Denenberg |
Text p. 354-388 |
Prep Verification Testing |
|
XII |
Apr 17 |
Apr 11 |
Team
Project Verification Testing [Lab] INTERDISCIPLINARY TEAMING |
Denenberg |
|
Prep Practice Presentation |
|
XIII |
Apr 24 |
Apr 18 |
Oral Design Presentation
Practice COMMUNICATIONS; INTERDISCIPLINARY |
Denenberg |
|
Prep Final Presentation |
|
XIV |
May 1 |
Apr 25 |
Team Design Project Reviews & Reports
COMMUNICATIONS; INTERDISCIPLINARY |
Teams |
|
Final Presentation &
Report Due |
|
XV |
Tuesday |
Tuesday May 8 11:30 AM |
Team Design Project Reviews & Reports
COMMUNICATIONS; INTERDISCIPLINARY |
Teams |
|
As required during Finals
Week May 5 – May11 |
|