24-780 Sec B – Engineering Computation

Fall 2019
Mon/Wed 4:30-6:20pm

Course Syllabus
1. Objectives
The practice of engineering in the 21st century relies heavily on the use of computing software. From
preliminary design using “back-of-the-envelope” calculations, through modeling, analysis and prototyping,
into the production of design documentation, all stages of the engineer’s work is supported by software.
Unfortunately, many engineers have only a marginal acquaintance with the programming required to create
the software packages they depend on to solve the technological challenges they must overcome. This
course seeks to provide engineers with the knowledge of how software is developed and with the skills to
develop software solutions that can be brought to bear on the unique problems they will encounter.
The skill of computer programming is part knowledge, part ingenuity, part sweat, and part art. With your
technical background, you are perfectly positioned to be a good programmer if you rely on your problem-
solving ability and judiciously apply your organizational skills. Your experience in design will also serve
you well as you proceed through the software implementation process.
In this course, you will expand on your ability to apply computing technology to engineering practice by:
 Identifying what parts of an engineered solution can benefit from a programming approach;
 Creating data models that best fit the engineering domain being implemented;
 Breaking down a large problem into workable parts and then integrating an overall solution;
 Effectively communicating design intent through documentation and programming style;
 Becoming adept at using online sources to enhance your coding prowess (life-long learning); and
 Visualize results using computer graphics (OpenGL).
Prerequisites: none

2. Instructors
Nestor Gomez, Ph.D., P.E. T.A.: Jaidev Singh Chadha
[email protected] T.A. email: [email protected]
Scaiffe Hall 305
(412) 944-6515 T.A: Yayati Jadhav
Office hours: Tues/Thurs, 9:30-noon T.A. email: [email protected]
Tues 1:30-4:40 or appmt.
3. Textbook and References
The recommended (not required) textbooks for the course are listed here, with the full knowledge that
you will likely not use them.
Stroustrup, Bjarne. The C++ Programming Language.
This is the classic reference book, written by the creator of the C++ programming language.
Shreiner, Dave and Mason Woo, Jackie Neider, and Tom Davis. OpenGL programming Guide: The
Official Guide to Learning OpenGL Version 2, 5th Edition
The official reference for OpenGL may be useful to have on hand.
In addition, it is likely that you may also want/need to use manuals and/or instruction guides for
programming, especially when you forget a small detail or need a little push. Here is a list of
recommended sources (printed and electronic):
http://www.google.com -> most questions are answered in first 5 hits.
http://www.codeguru.com -> more directed to Microsoft Visual C++, but good all-around too.
http://www.stackoverflow.com -> a discussion group where senior programmers answer questions.
https://www.khronos.org/registry/OpenGL/index_gl.php -> OpenGL documentation, a bit raw.

EngCompu_B., Fall 2019 Syllabus 1

4. Attendance
You are expected to come to every class session. Although there will be no “roll call” per say and no
grade will be assigned to attendance, missing lectures will surely reflect on your performance in problem
sets and examinations.
Class participation will be an integral part of the learning experience so get your money’s worth; come to
lecture.

5. Grade Breakdown
In‐class Exercises (participation mostly)   5% 
Problem Sets  60% 
12 assignments, 5% each    
Individual Project (Demo)    15% 
Team Project    25% 
Total     100% 

6. Problem Sets
Learning to program does not need to be intellectually problematic and emotionally torturous, as is often
believed and stereotyped. The analogy of learning to code with learning a new language is, I believe,
erroneous in that modern computer languages can be used to reflect the human way of thinking, rather than
having humans adapt to the computer’s limitations.
Since hands-on experience is an absolute must to truly internalize the use of a programming language and
apply it to the design process, all of your graded effort in the course will consist of problem sets and
projects. There will be 12 assignments in the course, mostly requiring the creation of code. Towards the
end of the course, you will work in small teams to develop your original software creations.
There will be a problem set due essentially every week and each should be turned in on time through the
Canvas. Problem sets are typically due at 11:59pm on Tuesdays. As a deterrent from untimely submittal,
there will be a 30% decrease in the homework’s score for every day (including weekends and holidays)
that the homework is late (e.g., 4 hours late = 23 hours late = 30% off, 25 hours late = 47 hours late = 60%
off, 49 hours late = 90% off, so why turn it in?). Extenuating circumstances will excuse at least part of the
deduction, but these should be discussed ahead of time.
I fervently advice you start working on the assignment as soon as it is posted, rather than waiting to the last
minute. Carefully re-read the previous sentence. I am not advising that you finish the assignment early
since I am realistic about how student life actually works. What I am suggesting is that you START early,
even if you cannot schedule enough time to finish until closer to the deadline. 30 minutes of work on a
Friday afternoon can save you three hours of frustration on Tuesday night.

7. Individual Project
In the individual project, students write a 1-minute long demo program and present it in class. A demo
program is a non-interactive presentation of graphical and audio programming techniques. See Demoscene
(http://www.demoscene.info/the-demoscene) for more details. We’ll discuss this in more later in the
semester, but rest assured that this is fun/creative activity.

8. Team Project
In software development, collaborative coding is the norm. Thus, the primary focus of the team project is
to experience writing a program in a team environment. The project will require your team (3 to 5
members) to develop a program in an engineering field (with perhaps some leanings towards educational
or entertainment, but don’t forget who you are). Commercial-grade software is absolutely NOT expected.

9. In-class Exercises
Since we cannot cover every topic in the problem sets and we do not want to miss out on the hands-on
experience for learning programming skills, we will be performing in-class exercises sporadically
throughout the semester. It is suggested that you bring your laptop to each lecture in order to take full
advantage of these exercises (although not all exercises require actual coding).

EngCompu_B., Fall 2019 Syllabus 2

10. Examinations
None.

11. Individual Work

Unless specially noted (team project), assignments you submit in this course must be your own individual
work. Note how this statement, although quite discouraging of it, does not necessarily rule out working in
groups from time to time since even in a group’s collaborative setting, your own work can come through.
However, I strongly suggest that you at least attempt the assignments individually and resort to groups
only when you get stuck and you cannot get hold of me or the TA.
Some other warnings about working in groups:
 Don’t let yourself or anyone else be “carried”. No one is doing anybody any favors that way. A person
who asks you for “a quick look just this once” has been asking for the same thing since 2nd grade.
 Limit the group’s size to 3 members. Larger groups have the tendency to lose their focus and make it
easier for the clueless to get by unnoticed.
 Use groups only in a cooperative mode, never in a “divide and conquer” mode. In other words, be
sure that everyone in the group works out every part for the problem instead of splitting it up among
the group members and then synthesizing an answer.
Now for a note on cheating as it refers to programming courses specifically. We all know that there is a lot
of sample code on the internet. The best advice is that you only use code that you truly understand and
never just blindly copy/paste into your problem set solutions. Remember that you owe it to yourself to
actually learn something from this course.
CMU maintains an honesty policy regarding cheating. Specific policies can be found at:
http://www.cmu.edu/policies/student-and-student-life/academic-integrity.html

12. Work Quantity

It is not my intention to have you spend more time on problem sets than is necessary for the learning
process. As a 12-unit course with 4 hours of lecture time, you should be spending about 8 hours a week of
your own time working on problem sets (a bit more or a bit less based on experience, errors, time
management, perfectionism, etc.). If you find that you are devoting an excessive amount of time on this
course, please let me know as soon as possible. There is a good chance that you have misunderstood the
requirements rather than the subject matter. We are here to learn, not to test your endurance or sleep-
deprivation capabilities.
As a graduate student, you are likely entering the phase of life in which you establish the work-life balance
that you’ll keep for your most of your career. Be sure that the choices you make about how to achieve your
academic goals do not adversely impact your ability to maintain your body and mind healthy.

13. Students with Disabilities

Students requesting classroom accommodation must first register with the Dean of Students Office. The
Dean of Students Office will provide documentation to the student who must then provide this
documentation to the Instructor when requesting accommodation.

14. Use of Mobile Devices and Laptops

All mobile devices should be turned off during class. You may follow the course material or take notes on
your laptop, but you must turn the sound off so that you do not disrupt other students' learning. I should
mention, however, that research has shown that handwritten notes lead to better comprehension of class
material (http://www.npr.org/2016/04/17/474525392/attention-students-put-your-laptops-away).

EngCompu_B., Fall 2019 Syllabus 3

15. Approximate Course Schedule
Lect Date (2019) Topic/Event Problem Sets
1 Mon, Aug 26 Intro to C++ Language. PS1 out
Steps to write a computer program.
Using a C++ compiler.
Console Input and Output
Basic Data Types and Variables
High-Low game
Writing without dialects
2 Wed, Aug 28 C++ in PC commercial software development
Dealing with compiler errors
Functions
Arrays
Loops
Auto data type and range-based for
Mon, Sept 2 Labor Day, No classes
3 Wed, Sept 4 Type Casting PS2 out
Range-based for and reference
Switch and case
Shuffling
Intro to numerical integration
2-player Tic-Tac-Toe
Infinite loop
Math library
Binary numbers
4 Mon, Sept 9 Macro
C-style Text String
Intro to State Transition (Word Counting)
Bubble Sort
Merging Two Pre-Sorted Arrays (Pre-requisite
for merge sort)
5 Wed, Sept 11 Compiling multiple source files PS3 out
Intro to OpenGL
Animation
Modern graphics hardware
Computational Cost (Big-O Notation)
6 Mon, Sept 16 Interactive Program (A shooting game)
Euler’s Method
Visual effects in OpenGL
7 Wed, Sept 18 Intro to Pointers PS4 out
Parsing
File Input / Output
8 Mon, Sept 23 Text-drawing functions
Dealing with Window Resizing
Sub-second timer
Mouse event and mouse state
Monte-Carlo method
9 Wed, Sept 25 Introduction to audio programming. PS5 out. Special creative assignment.
10 Mon, Sept 30 Intro to Object-Oriented programming
Difference between C and C++
House cleaning using C++ classes
Writing a C++ program in a team.
11 Wed, Oct 2 More about member functions PS6 out
Splitting the shooting-game into multiple .cpp /
.h files
12 Mon, Oct 7 Resource management and RAII concept
Constructor and destructor
Protected members
Dynamic memory allocation
Building a mesh viewer

EngCompu_B., Fall 2019 Syllabus 4

Lect Date (2019) Topic/Event Problem Sets
13 Wed, Oct 9 Bitmap PS7 out
Contrast maximizing filter
Texture mapping
‘const’ qualifier
Constructor with parameters.
14 Mon, Oct 14 textString class (How std::string works)
Copy constructor and copy operator
15 Wed, Oct 16 TextInput class PS8 out
Image Processing
Inheritance
Templates
std::vector
16 Mon, Oct 21 Intro to 3D graphics
Coordinate transformation
Z-buffering
Z-fighting problem
Writing a 3D graphics framework
Fly-through
Orbit
17 Wed, Oct 23 Project Introduction PS9 out
More examples of 3D graphics
18 Mon, Oct 28 Polymorphism
Function overloading
Template
Virtual function
‘decltype’
std::function and std::bind
19 Wed, Oct 30 Runtime Type Information (RTTI) and dynamic PS10 out
cast
Singly-linked list
Doubly-linked list
20 Mon, Nov 4 Laplacian smoothing
Recursion
Flood-fill by recursion
Flood-fill by todo-list (or stack)
Tues, Nov 5 Election Day
21 Wed, Nov 6 Individual Project Presentations PS11 out
22 Mon, Nov 11 Parallel processing
std::thread and std::mutex
23 Wed, Nov 13 Binary Tree PS12 out
Merge Sort
24 Mon, Nov 18 Writing a 1st-Person 3D Maze from Scratch
Wed, Nov 20 Make-up day
25 Mon, Nov 25 Make-up day
26 Wed, Nov 27 Thanksgiving Break. No Classes
27 Mon, Dec. 2 Project Presentations
28 Wed, Dec. 4 Project Presentations Last Day of Classes

EngCompu_B., Fall 2019 Syllabus 5