COSC-052: Computer Science II

Spring 2017

Contents

• Announcements
• Where, When, Who
• Description
• Learning Goals
• Policies
• Teaching Assistants
• Schedule
• Assignments and Grading
• Materials: Readings, Videos, and Links
• Other Interesting Links

Announcements

5/1/17: Review for final is W 5/3 @ 1pm in REI 284.

4/27/17: Posted room for final exam: REI 281.

• C++ How to Program, Tenth Edition, by Deitel and Deitel.
• Starting out with C++, Early Objects, 7th–9th editions, by Gaddis, Walters, and Maganda.
• Data Structures and Algorithms in C++, by Goodrich, Tamassia, and Mount.

My course policies are designed to supplement the University's Undergraduate Honor System and the CS Department's Honor Policy. Unless stated otherwise when I distribute an assignment, the following is the default for all assignments for this course. I've developed my policies from past teaching experiences and from the CS Department's Honor Code at George Mason University.

I am obligated to refer all suspected cases of academic dishonesty by undergraduate students to Georgetown's Honor Council. If you have any questions about these policies or how they apply, please discuss such concerns with me during class, during office hours, or by e-mail.

In my experience, students at Georgetown do honest work. The small percentage of students who have submitted someone else's work as their own did so because they did not manage their time wisely.

Students must follow proper scholarly practice for all submitted work, whether graded or ungraded and whether a draft or final version of a proposal, paper, or program. We must acknowledge our reliance on the work of others through citation.

Students may be quite adept at and knowledgeable about citing and quoting material from traditional sources, such as books and articles. Typically, we do not have cite facts, common math formulae, or expressions of our own ideas, observations, interpretations, and analyses, However, students new to computer science may not realize that formulae, theorems, proofs, algorithms, and programs can require the same treatment as any other form of expression.

For convenience, you do not need to cite the course materials, conversations with me or information you obtain from class lectures and discussions. If you are unsure about what requires citation or what constitutes proper scholarly practice, please ask me during class, during office hours, or by e-mail.

I design my courses and assignments so students have what they need to complete the assignments individually without consulting outside resources. I determine the size of and credit for assignments based on the assumption that the work for them is the result of individual effort using only the course resources and materials. Students who use outside resources to complete assignments may not be eligible for full credit. Students who do not acknowledge their use of outside resources to complete assignments may be in violation of my course policies and the university's policies on academic integrity.

The following list details acceptable and unacceptable practices:

• You can:
  • obtain assistance in understanding course materials (textbooks, lecture notes, assignments);
  • obtain assistance in learning to use the computing facilities;
  • obtain assistance in learning to use special features of a programming language's implementation;
  • obtain assistance in determining the syntactic correctness of a particular programming language statement or construct;
  • obtain an explanation of a particular syntactic error;
  • obtain explanations of compilation or run-time error messages.
• You can obtain assistance only from me and the teaching assistants:
  • in designing the data structures and algorithms used in your solution;
  • in modifying the design of an algorithm or data structure determined to be faulty;
  • in implementing your algorithm or data structure in a programming language;
  • in correcting a faulty implementation of your algorithm or data structure;
  • in determining the semantic correctness of your program;
  • in designing an experimental study and interpreting its results.
• You can not:
  • show or give a copy of your work in any amount or form to another student;
  • see or receive a copy of someone else's work in any amount or form;
  • attempt to gain access to files other than your own or those that I designate and authorize;
  • inspect or retain in your possession another student's work, whether it was given to you by another student, it was found after other student discarded his or her work, or it accidentally came into your possession;
  • collaborate in any way with someone else in the design, implementation, or logical revision of an algorithm;
  • use or present as your own any algorithm, data structure, or implementation that is not of your own or of my design, or which is not part of the course's required reading. If you modify any procedure which is presented in the course's texts that is not specifically mentioned in class or covered in reading assignments, then a citation with page number must be given;
  • incorporate code written by others (such as can be found on the Internet).

Policies dealing with late projects, cell phones, attendance, and inclement weather.

• You should submit all assignments on time. For late projects, there will be a 1% deduction for each minute after the deadline. In the real world, it won't be your grade that decreases. It'll be your stock price.
• If you use your laptop for development, you should keep a backup of your projects on a university or department machine (e.g., cs-class).
• You must take the final exam with the section and during the period designated by the Registrar.
• It is my job to maintain a constructive learning environment for everyone. Students bringing cell phones to class must either set the phone to vibrate, turn the ringer volume off, or turn the phone off completely.
• Attendance is not required, but there is a correlation between attendance and grade. It's positive.
• It is fine if you must leave class early, arrive late, or leave the room to answer your phone, but you should do so in a manner that does not disturb your fellow students.
• In the case of inclement weather that results in the university's closure, we will meet virtually during normal class times using Zoom.

Name	NetID	Operating System	IDEs and command-line tools
Jonathan Gibson	jeg263	MacOS	Xcode
Guy Burstein	gb654	MacOS, Windows, Linux	Xcode, Visual Studio, Linux is my IDE, The Terminal app is my IDE, vi, FileZilla, sftp and scp
Jordan Mallen	jam497	MacOS	Xcode
Eamon Cagney	esc61	MacOS, Windows	Eclipse, Visual Studio, FileZilla
William Stubbs	wgs11	MacOS	Xcode, FileZilla
Roger Wang	rw794	Windows	Eclipse, Visual Studio, Code::Blocks, FileZilla
Jonathan Guerin	jgg41	Windows	Visual Studio
Eibhlin Goggins	esg41	MacOS	Xcode, FileZilla
Dongpeng Xia	dx21	MacOS	Xcode, FileZilla
Isabella Schwartz	is392	MacOS	Xcode, FileZilla
Mary Joy Kozak	mk1527	Windows	Visual Studio
Sarah Curtis	sgc46	MacOS	Xcode, Eclipse, FileZilla
Jerzy Lasota	jml352	MacOS	Xcode, Code::Blocks, The Terminal app is my IDE, FileZilla, sftp and scp
Parth Patel	pbp25	Windows	Visual Studio, FileZilla
Ahmed Latif	aml295	MacOS	Xcode, vi, emacs
Elly Meng	sm3008	MacOS	Xcode, The Terminal app is my IDE, make, FileZilla
Aicha Nzie	an585	MacOS	Xcode, The Terminal app is my IDE

• Programming Projects, 40%
• Project 1, assigned W 1/11, due F 2/3 @ 5 PM, 6 points
• Project 2, assigned F 2/3, due F 2/24 @ 5 PM, 6 points
• Project 3, assigned F 2/24, due F 3/24 @ 5 PM, 8 points
• Project 4, assigned F 3/24, due W 4/12 @ 5 PM, 10 points
• Project 5, assigned W 4/12, due M 5/1 @ 11:59 PM, 10 points
• Midterm Exam, W 3/1, 20%
• Final Exam, F 5/12 4–6 PM, REI 281, 30%
• Homework (10%)
• Homework 1, assigned W 1/11, due F 1/20 @ 5 PM, 2 points
• Homework 2 (optional)
• Homework 3 (optional)

String Grades::getLetterGrade()
{
  if (grade >= 94)
    return "A";
  else if (grade >= 90)
    return "A-";
  else if (grade >= 87)
    return "B+";
  else if (grade >= 84)
    return "B";
  else if (grade >= 80)
    return "B-";
  else if (grade >= 77)
    return "C+";
  else if (grade >= 74)
    return "C";
  else if (grade >= 70)
    return "C-";
  else if (grade >= 67)
    return "D+";
  else if (grade >= 64)
    return "D";
  else
    return "F";
} // Grades::getLetterGrade

• Autolab, for submitting projects
• Blackboard, for online discussions and submitting projects if something goes wrong with Autolab
• cplusplus.com
• C programming.com–Your Resource for C and C++ Programming
• Google C++ Style Guide
• Book: Managing projects with GNU make, 3rd Edition, by Robert Mecklenburg. We will give you Makefiles that you can modify, but if you want to learn more, Chapters 1 and 2 are probably sufficient for this class.
• Screencast: Program Organization
• Screencast: Basic Makefiles
• Screencast: Date Class Design and Implementation
• Screencast: Makefile Magic
• Screencast: DOC comments, doxygen, and posting documentation on the Web
• YouTube Playlist: Classes
• YouTube Playlist: C++ Vectors
• YouTube Playlist: Pointers
• YouTube Playlist: Self-referential Classes
• vi Reference Card
• emacs Reference Card
• gdb Reference Card
• How to Write Doc Comments for the Javadoc Tool
• doxygen: A documentation system for C++, C, Java, and other languages
• Unix as IDE
• Xcode, Apple's free integrated development environment (IDE). Make sure you install the command-line tools.
• Eclipse, a free integrated development environment (IDE) for Linux, OS X, and Windows
• NetBeans, a free IDE for Linux, OS X, and Windows (Oh! And Solaris)
• Code::Blocks, a free IDE for Linux, OS X, and Windows
• Visual Studio Express, a free IDE for Windows
• vim, an improved vi editor for Unix, OS X, and Windows. It's usually already installed on OS X and Unix systems
• Interactive Vim Tutorial
• Useful Unix Commands
• HOWTO: Log in and transfer files to cs-class from OS X and Linux
• HOWTO: Log in and transfer files to cs-class from Windows
• HOWTO: Create and compile files under Unix
• WinSSH: a secure telnet and ftp client for Windows (educational license)
• PuTTY: a free secure telnet and ftp client for Windows

• The 2016 Top Programming Languages
• xkcd: Old Days
• Computer Language Benchmarks Game
• An Interview with Bjarne Stroustrup, which includes his thoughts on educating computer scientists
• Now Blooming: Digital Models
• Teach Yourself Programming in Ten Years, by Peter Norvig
• Computer Science Education: Where Are the Software
Engineers of Tomorrow?, by Dewar and Schonberg
• The 18 Mistakes that Kill Startups, by Paul Graham
• Hackers and Painters, by Paul Graham
• In the Beginning was the Command Line, by Neal Stephenson
• Bjarne: the man, the language
• The Deitel Empire
• GNU gcc, which includes g++, our C++ compiler
• Peet's
• Fast Lane
• Red Bull

Copyright © 2019 Mark Maloof. All Rights Reserved. This material may not be published, broadcast, rewritten, or redistributed.