EE 298: Introduction to Computer Engineering II (EE 107)

Announcements:  Check here regularly for announcements!

Welcome to EE298! 

The grades for Spring 2007 are online.

Here is a link to instructions for moving files from Mavdisk to your home computer.  If you are on campus you can still use this method but you can also mount mavdisk on your computer. 

The software you can download is described here.

Previous Announcements

Course description: This is a continuation of EE 298 in Fall 06 (to be known in the future as EE 106).  The combination of these two courses will prepare students for upper division courses requiring an understanding of digital logic and experience with programming.  The focus of this course will be algorithmic approaches to problem solving and computer program design for engineers using the C language.  Students will explore Boolean expressions, implement programs, and interface the computer with external hardware using robots and sensors.  Students will also have experience with control structures, modular code and file input/output. 

Pre-requisites: There are currently no pre-requisites for this class but students should be prepared for calculus I. 

Professor: Rebecca Bates (bates@mnsu.edu) 
Contact Information

Course Hours and Location
Lectures:  M, Th 1-2:30pm TN N241
Lab 1: W 11-12:50pm TN N192
Lab 2: W 4-5:50 TN N192

Office Hours
Monday Tuesday Wednesday Thursday Friday
11-12 4:30-5:30 2-4* 2:30-3 11:30-1:30**
*will be held in WH 125A
**will be held in the ACC or WH243

Prof. Bates will also read and respond to email questions within 24 hours.  You can usually expect responses to questions the same day if received prior to 10pm. If things that are useful for the entire class come up, they will be posted on the announcement section of the class webpage so check it regularly.

Course Materials
Required Text: Engineering Problem Solving with C, 3rd ed., Delores M. Etter, Prentice Hall, 2005.

Course Syllabus

Course Policies

Course Outcomes
Overall field:

  1. Review basic problem solving and extend to algorithm development.
  2. Maintain an effective study regime.
  3. Continue discussion of ethics and implications in oral and written forms.
  4. Connect engineering to at least one issue affecting society using fictional and non-fictional sources.
Problem Solving and Analysis:
  1. Identify the software development process including analysis, design, coding and testing in its higher level context of design and development, maintenance and documentation.
  2. Perform algorithm development using flow charts and pseudocode.
  3. Use testing plans in the development of C code and apply tests to output.
  4. Perform statistical data analysis from measurements using both spreadsheets and high-level code.
  5. Use C code to solve engineering problems such as line fitting and model estimation and prediction.
Hardware:
  1. Manipulate binary, octal and hexadecimal number systems in order to relate data storage with software data types.
  2. Will implement code in robots to perform a variety of tasks to reinforce applied software problem solving strategies.
Software:
  1. Recognize different operating systems and organization of file structures.
  2. In at least one development environment, write, compile, run, and test C code.
  3. Declare, initialize and manipulate programming variables.
  4. Simulate computer behavior in arithmetic using order of operations.
  5. Use standard input/output as well as file input/output.
  6. Translate Boolean logic into C syntax.
  7. Implement programming concepts like data storage, selection structures and repetition structures.
  8. Manipulate text files containing character and numeric data with C file input/output structures.
  9. Develop modular code using functions.
  10. Use 1 and 2 dimensional arrays for data storage and manipulation.
Hardware/Software Interface
  1. Create programs to interface with external hardware using robots and sensors.

Grading
Homework and Lab work: 35%
Midterm Exams: 45%        
Final exam: 20%

Exam Dates
Written: February 22, April 2
Practical:  assigned April 18, due April 20 at 4pm
Final: Tuesday 8 May, 12:30-2:30pm

Course Tools

Other Information

EE298 Handouts and Assignments

EE298 Grading, Collaboration and Make-up Policies

Additional Resources

On-line programming help (various tutorials)

What do all the acronyms mean?

How can I get information on just about anything?

She said something I don't understand:

Page last modified by R.A. Bates on 05/16/2007 08:44 AM.