[MSOE Homepage]

Dr. Taylor's MSOE Homepage


Unix is a Four
Letter Word

My Photo Album

My Personal Homepage

Optional Homework Assignments


Quiz 1 -- Electronic Submission


Lab 1: Microsoft Visual C++

Lab 2: Grade Calculator

Lab 3: Grade Calculator revisited

Lab 4: Generic Calculator

Lab 5: Postal Bar Codes

Lab 6: Palindromes

Lab 7: Estimating Pi

Final Project: Paragraph Justification

CS-100 - Introduction to Engineering Computing

Fall Quarter 1999

Electrical Engineering and Computer Science Department
Dr. Christopher C. Taylor

S-331, 277-7339


This course provides the students with a working knowledge of the design and implementation of computer programs to solve problems encountered in engineering practices. Structured programming techniques are introduced in this course. Particular emphasis is placed on the discussion of problem investigation, algorithm development, flowchart development, pseudocode development, coding, execution, debugging, and documentation. Topics include data types, assignment statements, I/O statements, I/O files, control contructs, looping techniques, arrays and vectors, user-defined functions, library functions, and modules. Data visualization is also be discussed. Problems related to engineering applications are emphasized. The high-level computer language C++ is used to illustrate and implement the topics. (Coreq: MA 127) (2-2-3)


Computing Concepts with C++ Essentials, 2nd Ed., by Cay Horstmann, John Wiley and Sons, 1999.


Upon successful completion of this course, the student should be able to design computer software to solve engineering problems that make use of the following C++ components:
  • data types,
  • input/output statements,
  • arithmetic and assignment statements,
  • logical expressions and control constructs,
  • looping statements,
  • subscripted variables, and
  • library and user-defined functions.

My Schedule

Time Mon Tues Wed Thur Fri
8 CS-321
S 307
10 CS-321
CC 11
CC 11
CC 11
12 XX  
1 Dept
S 358
2 CS-100
S 358
S 358
S 366
4 CS-381
S 362
S 362
S 362
additional office hours by appointment.


A quiz will be given at the beginning of each lab period. The lowest quiz score will be dropped. No make-up quizzes will be given.


Each student must submit an individually written report for each laboratory assignment. Laboratory reports should include software code written as part of the lab project and should conform to the specified documentation standards. There is a 10% per business day late penalty for lab reports submitted after the scheduled due date. No reports will be accepted after 4:30pm, November 12, 1999.


There will be three hour exams in this course. It is your responsibility to be present for all exams. Please contact me in advance if you have a valid conflict with a scheduled exam.




Lab projects:


Final project:


Hour exams: (9/27, 10/11 and 11/5)





Attendance in lab is mandatory. Students who miss lab or leave early will only be eligible for 50% of the possible points for that lab assignment. Attendance in class and lab is expected. If you decide to drop out of the course, it is your responsibility to notify the registrar. I will not drop you for missing class. If you stop coming to class without notifying the registrar that you are dropping the course, it is likely that you will receive an "F" grade.


Students are expected to act in a professional manner in dealing with all matters pertaining to this course. In particular, deceptive practices of any sort are unacceptable (e.g., submitting source code that does not run correctly without clearly identifying the problems with it). Note that copying is not necessarily unprofessional; engineers copy good ideas from many sources all the time (subject to ethical and legal constraints). If you do copy something, you must give explicit credit to the source (e.g., article, book, web URL); also, be sure you understand anything that you copy, as I may choose to quiz you orally over that material.

Lab projects are to be your own work. This does not mean that you cannot discuss ideas and approaches with other students or faculty, but the final product must be yours alone. At times it may be difficult to know where to draw the line between beneficial cooperation and parasitic freeloading. For this course, it is not legitimate to collaborate to the extent of sharing source code for all or part of a particular lab project. In particular, you should never be in possession of a copy (in any form) of all or part of another student's source code. (This includes students from other sections and students who previously took this course.) If you have any question as to what types of cooperation are acceptable, please talk to me.


You are responsible for assignments and announcements made in class or lab. In addition, you should periodically check your email account and the Web pages for this course.

Special Needs

If you have special educational needs, it is your responsibility to meet with me in my office in the first three weeks of the quarter to discuss them.

Feedback Wanted

I am interested in your feedback on how I can improve this course. Please feel free to stop by my office, send me email, or drop an anonymous note in my departmental mailbox with suggestions on how I can make this a better class for you. Don't wait until evaluation time because I won't see those comments until the quarter is over.

Electronic Submission Procedure

All laboratory reports for this course must be submitted electronically. You are responsible for ensuring that each report is emailed to me. In particular, it is your responsibility to make sure you type in the correct email address, etc... If you do not receive a message confirming that I received your submission, you should assume that I didn't receive it.

All reports will be graded and returned to you by email. The graded reports will be in Adobe Acrobat's Portable Document Format (PDF).

Tentative Schedule