School of Engineering and Engineering Technology
Fairleigh Dickinson University
I. Course: ENGR 1204 Programming Languages in
Engineering
Semester: Spring Year: 2002 Credits: 3
Class
Hours: Tues. 10-11:15 am (M-205)
Wed. 11-11:50 am (M-205)
Thur. 10-11:15 am (UH-23, Computer Lab)
II. Instructor:
Prof. Howard Silver Office:
M-114
Office
Hours: Mon., Tues., Wed. 4-5 pm & other times by appointment
Phone: (201) 692-2830 Fax: (201) 692-2130 Email: silver@fdu.edu
III. Text: 1. Etter & Ingber;
AEng=ring Problem Solving with C A(2nd
Ed.); Prentice Hall;2000.
2. Palm; AIntroduction to MATLAB 6 for Engineers@;
McGraw Hill; 2001.
IV. Course Description: C language and MATLAB applied to engineering problem solving.
V.
Prerequisites:
None
VI. Course
Objectives and Expected Learning Outcomes:
Objective
1: Become familiar with C language and MATLAB.
Outcome
1.1: Understand interaction of computer
hardware and software.
Outcome 1.2: Learn
the language structure and syntax to enable writing of error free programs.
Outcome 1.3: Become aware of importance of structured
programming and analysisand documentation tools
(flowcharts and pseudocode).
Objective
2: Be able to create computer programs to solve
engineering problems.
Outcome 2.1: Understand numerical methods
to enable solving for roots of a nonlinear equation, approximating area under a
curve and solving
linear simultaneous equations.
Outcome 2.2: Become familiar
with random number generators and their use in simulation.
Outcome 2.3: Be able to use built-in C
library functions and MATLAB Toolbox
functions, and to write user functions
appropriate to applications.
VII. Usage/Skills: Computer
- writing and debugging of programs
Writing - submitting computer projects
with appropriate comments and conclusions
VIII. Grading Policy:
(Type of Evaluation/Assessment Tools) (Number) (Percentage)
Exams 2 50
%
Final Exam 1 25 %
Computer
Projects 8 25 %
IX. Course Lecture Weekly Schedule:
(Week) (Topic) (Chapter/Section)
1, 2 Computer
Hardware and Software Etter: Sec.
1.1 to 1.4, 2.1 to 2.4,
Introduction to C-language 2.7,
2.10, 3.6
programming, Data Files
3, 4, 5 Structured
Programming: Etter: Sec. 3.1 to 3.4, 3.8
Program Control Flow -
Sequence,
Selection, Repetition
QUIZ 1
6, 7, 8 Modular
Programming Etter:
Sec. 4.1 to 4.5, 4.7, 4.9
Applications
- Root Finding,
Numerical
Integration
Random
Numbers and Simulation
9, 10 Arrays
and Matrices Etter:
Sec. 5.1, 5.2, 5.4, 5.8, 5.10
Applications - Statistical Palm:
Sec. 6.2, 6.3
Measurements,
Solution to
Simultaneous
Equations
QUIZ
2
11, 12 Introduction
to MATLAB: Palm:
Sec. 1.1 to 1.5, 1.7, 2.1 to 2.4,
Scalars and arrays, script and 3.3
to 3.5
function files, plotting
13, 14 Matrix
Operations and Functions Palm:
Sec. 4.1 to 4.4, 5.1, 5.3, 5.6,
Program Control Flow 7.1
to 7.3
Engineering Applications
15 FINAL
EXAM
X. Laboratory
Experimentation Weekly Schedule:
Week Experiment
(Computer Project)
C
language:
1 Prelim.
Lab 1 - Program creation and compilation, formatted output
2 Prelim.
Lab 2 - Program debugging, input and output, file writing
3 Lab
1 - Program to calculate time to drain water from a cylindrical tank
4, 5 Lab
2 - Repeat of water tank problem using repetition structure (looping)
6 Lab
3 - Program to approximate
area under a curve using rectangle midpoint method
7, 8 Lab
4 - Program to approximate area, volume and weight of a parabolic archway,
using trapezoidal method
9 Lab
5 - Program to generate and sort a simulated batch of electrical resistors with
a normal distribution
10 MATLAB:
Prelim. Lab - Introduction to MATLAB command mode,
elementary operations and data plotting
11 Lab
6 - Approximation of parabolic archway area by simulation (using scalars)
12 Lab
7 - Parabolic archway simulation using vectors to generate a plot
13 Lab
8 - Generation of fractals using recursive relationships
14 Review
Lab
XI.
Instructions and Formats for Computer Project Reports:
Requirements
generally include the following:
1.
Comment lines at top of all programs, with course number and name, student name
and date, lab number and statement of purpose of program.
2.
Print out of source code and relevant program output
3.
Appropriate hand calculations to validate computer output
4.
Flowchart or pseudocode along with comments in the
program
5.
Graphs, if required,
with axes scaled and labeled and title provided
6.
Conclusions