Course Specific Information by Discipline

Civil Engineering Courses

  • 200 Mechanics of Materials: talk to your professor – no additional information
  • 340 Concrete Structures: talk to your professor – no additional information
  • 350 Soil Mechanics: talk to your professor – no additional information
  • 410 Foundation Engineering: talk to your professor – no additional information
  • 440 Water Treatment: talk to your professor – no additional information

Computer Engineering Courses

  • 320 Operating Systems: talk to your professor – no additional information
  • 411 Adv Operating Systems: talk to your professor – no additional information
  • 499 Engineering Design: talk to your professor – no additional information

Computer Science Courses

  • 103 Overview Computer Science: talk to your professor – no additional information
  • 104 Python: talk to your professor – no additional information
  • 110 Computer Science I: Your professor asks you to check the D2L website for all information related to this course.
  • 111 Computer Science II: talk to your professor – no additional information
  • 310 Algorithms: talk to your professor – no additional information
  • 350 Computer Graphics: talk to your professor – no additional information
  • 371 Databases: Your professor asks you to check the D2L website for all information related to this course.
  • 402 Big Data Analytics: talk to your professor – no additional information
  • 451 Graphics Algorithms: talk to your professor – no additional information
  • 498 Sr research Methods: talk to your professor – no additional information
  • 523 High Performance Comp: talk to your professor – no additional information
  • 559 Agile Software Methods: talk to your professor – no additional information
  • 570 Adv Databases: talk to your professor – no additional information
  • 571 Data Mining: talk to your professor – no additional information

Electrical Engineering Courses

  • 220 Linear Circuits: talk to your professor – no additional information
  • 310 Signals & Systems: talk to your professor – no additional information
  • 422 High Speed Circuits: talk to your professor – no additional information

General Engineering Courses

  • 110 Modeling & Simulation: talk to your professor – no additional information
  • 120 Programming for Engineers: talk to your professor – no additional information
  • 200 Engineering Seminar II: The D2L course shell for our class is up and running, please make sure that you are checking that regularly!!!  I have put FAQs and a lot of other information up there. We have transitioned from playing the board game Zombicide to playing WoW online.  I have updated groups that were outside of the range of players allowed for WoW team play and posted those in D2L. Yes, we will still be using GitLab for most of your project submissions, however, I did go ahead and create assignment folders in D2L as well for those of you who just can’t seem to get into GitLab to use for project submission.  Due to other responsibilities that I have during our class times for the remainder of the semester, as well as some students having technology/internet restrictions, I am pre-recording the lectures for each week and putting them up in D2L for you to watch at your convenience. For the few of you who could not play WoW with the rest of us, I have uploaded a different project for you in the Discussion board for your group in D2L.  As always, please email me if you have any questions, but please check D2L first! I am getting way too many questions emailed to me for which the answers are already provided in our D2L course shell.
  • 300 Engineering Seminar III: talk to your professor – no additional information
  • This image has an empty alt attribute; its file name is unknown.png390 Special Topics: For this course, we are flipping the classes: videos with the content posted HERE. During our regular class time, we are answering questions, clarifying topics from the videos, and designing the project we were already working on. Class time and our weekly individual meetings are held in Merlin’s Zoom Room (meeting id 555 477 1424). Some of our classmates have new obligations that conflict with our class time, so we are using zoom recordings of those meetings. In addition, students are using zoom to help each other with programming issues. Those can also be captured as videos that we share. This will let people see how others are approaching the problem and highlight skills like refactoring and debugging. Look for commentary by Peppermint

Mechanical Engineering Courses

  • 100 Engineering Graphics: talk to your professor – no additional information
  • 200 Statics: talk to your professor – no additional information
  • 210 Dynamics: talk to your professor – no additional information
  • 230 Materials: talk to your professor – no additional information
  • 310 Manufacturing Processes: talk to your professor – no additional information
  • 420 Machine Design: talk to your professor – no additional information
  • 450 Thermal Systems: talk to your professor – no additional information

Software Engineering Courses

  • 200 Design Patterns: talk to your professor – no additional information
  • 300 Crafting Quality Code: talk to your professor – no additional information
  • 415 Interdisciplinary Dev: This class has become a team of remote developers. We are still practicing agile software development techniques, but are now doing it from afar. Our alumni who work as remote developers have given us some advice on tools, process, and codes of conduct. We are pair programming using our personal zoom rooms. During class, we meet in Merlin’s Zoom Room (meeting id 555 477 1424). After our daily stand up, we use the breakout rooms to pair program. That allows Merlin to keep an eye on things and helps us stay connected. Our customers are committed to going forward, so we will also get some practice doing remote presentations.
  • 420 Extreme Programming: This class has become a team of remote developers. We are still practicing agile software development techniques, but are now doing it from afar. Our alumni who work as remote developers have given us some advice on tools, process, and codes of conduct. We are pair programming using our personal zoom rooms. During class, we meet in Merlin’s Zoom Room (meeting id 555 477 1424). After our daily stand up, we use the breakout rooms to pair program. That allows Merlin to keep an eye on things and helps us stay connected. Since everyone else is online, we are hoping to get some feedback from other SWE students about how the game is progressing and what features we should be building.