CS 162 – Intro to CS II
|Instructor||Rob Hess (email@example.com)|
|TAs||See this page for more info|
|Lectures||MWF 12:00–12:50pm, LPSC 125|
|Labs||See this page for more info|
|Recitations||See this page for more info|
Rob: T 3:30-4:30pm, W 3:30-4:30pm (KEC 1109)
TAs: see the TA info page
|Syllabus||CS 162 Syllabus|
|Textbook||Gaddis, Walters, and Muganda. Starting Out with C++: Early Objects. 8th or 9th Ed.|
|Piazza||CS 162 on Piazza|
|Community||Please read this page about establishing a positive classroom community|
- Review chapters 8, 10, and 7 of Gaddis.
- Chapters 1 and 2 of Pro Git
- Chapter 7 of Gaddis.
- Classes – cplusplus.com
- We'll have our first exam on Wednesday this week. The exam will be in our normal lecture place and time and will cover topics through Week 4. We'll spend some time Monday of this week reviewing for the exam.
- Exam answers
- Inheritance (the "is-a" relationship) – notes – example code
- Polymorphism – notes – example code
- Exceptions – notes – example code
- We'll have our second exam on Friday this week. The exam will be in our normal lecture place and time and will cover topics from Week 5 through Week 9. We'll spend some time Wednesday of this week reviewing for the exam.
- Exam answers
Programming assignments will be managed via GitHub Classroom. Following the links below will prompt you to sign in to GitHub and to create an assignment repository for yourself. The assignment repository will at a minimum contain a
README.md file containing the assignment description. There may also be additional skeleton files in the repository to help you get started with the assignment. To submit an assignment, make sure you have committed your solution code and pushed it to your GitHub repository before the assignment deadline.
Note that all of your assignments will have a component of their grade based on your code style and commenting. Using descriptive comments and good, consistent code style is very important to ensure the code you write is readable, understandable, and maintainable. For more on why good, consistent style is important, check out the background and goals of Google's C++ style guide. Please read the style guidelines for this course and try to follow them when writing your assignments.
Assignment 1: Pointers, arrays, structs, and file I/O – Due by 11:59pm on Monday, 1/23/2017
- Grading demo due by 11:59pm on Friday, 2/3/2017
Assignment 2: Go Fish – Due by 11:59pm on Monday, 2/6/2017
- Grading demo due by 11:59pm on Friday, 2/17/2017
Assignment 3: Zoo Tycoon – Due by 11:59pm on Monday, 2/20/2017
- Grading demo due by 11:59pm on Friday, 3/3/2017
Assignment 4: Hunt the Wumpus – Due by 11:59pm on Monday, 3/6/2017
- Grading demo due by 11:59pm on Friday, 3/17/2017
- Final Project: Escape from CS 162 – Due by 6:00pm on Thursday, 3/23/2017