605.604.81 - Object-Oriented Programming with C++

Course Structure

The course materials are divided into modules which can be accessed by clicking Course Modules on the left menu. A module will have several sections including the overview, content, readings, discussions, and assignments. You are encouraged to preview all sections of the module before starting. Most modules run for a period of seven (7) days, exceptions are noted on the Course Outline page. You should regularly check the Calendar and Announcements for assignment due dates.

Course Topics

Introduction
Intro to Classes, Objects, Strings, & Control Statements
Control Statements, Logical Operators, Functions, and Recursion
Arrays, Vectors, & Pointers
Classes - A Deeper Look
Operator Overloading
Inheritance
Polymorphism
Stream Input-Output File Processing
Standard Template Library and STL Algorithms
Exceptions
Data Structures
Bits, Characters, Strings and Other Topics
C++11 Additional Features

Course Goals

To master all techniques of software development in the C++ Programming Language and demonstrate these techniques by the solution of a variety of problems spanning the breadth of the language including C++11 changes

Course Learning Outcomes (CLOs)

• Perform object oriented programming to develop solutions to problems demonstrating usage of control structures, modularity, I/O. and other standard language constructs.
• Demonstrate adeptness of object oriented programming in developing solutions to problems demonstrating usage of data abstraction, encapsulation, and inheritance.
• Demonstrate ability to implement one or more patterns involving realization of an abstract interface and utilization of polymorphism in the solution of problems which can take advantage of dynamic dispatching.

Textbooks

C++ How to Program  Edition: 11th ISBN: 9780138092542
or C++ How to Program (10th Edition) 10th Edition ISBN-10: 0134448235 Edition: 10th

Required Software

A C++ Development Environment which supports C++11 and later features such as Visual Studio Code, Visual Studio, Netbeans, Eclipse CDT, or other IDE

Student Coursework Requirements

It is expected that each module will take approximately 7–12 hours per week to complete. Here is an approximate breakdown: reading the assigned sections of the texts (approximately 3–4 hours per week) as well as some outside reading, listening to the audio annotated slide presentations (approximately 2–3 hours per week), and developing projects (approximately 2–5 hours per week).

This course will consist of the following basic student requirements:

Preparation and Participation

Discussions

You are responsible for carefully reading all assigned material and being prepared for discussion. The majority of readings are from the course text. Additional reading may be assigned to supplement text readings.

Post your initial response to the discussion questions by the evening of day 3 for that module week. Posting a response to the discussion question is part one of your grade for module discussions (i.e., Timeliness).

Part two of your grade for module discussion is your interaction (i.e., responding to classmate postings with thoughtful responses) with other classmates (i.e., Critical Thinking). Just posting your response to a discussion question is not sufficient; we want you to interact with your classmates. Be detailed in your postings and in your responses to your classmates' postings. Feel free to agree or disagree with your classmates. Please ensure that your postings are civil and constructive.

I will monitor module discussions and will respond to some of the discussions as discussions are posted. In some instances, I will summarize the overall discussions and post the summary for the module.

Evaluation of preparation and participation is based on contribution to discussions.

Quizzes

Each module of the course content may have a quiz encompassing items in the module. The student is expected to complete these each week during the week of the associated module to gauge their mastery of the material and identify areas needing additional study and review. Quizzes can be taken as many times as desired and the grade is the average of all Quiz attempts.

Course Projects

Each course project is evaluated by the following grading elements:

Programming assignments are to be submitted as a SINGLE PDF FILE containing

Design - Stating HOW your code classes/methods/class relationships will meet the Project or Assignment requirements

Using whatever means you desire, state your Software design

There are many options, some of which could be varying combinations of the following

     A description in text
     Hand drawn figures
     Diagrams drawn using Office Tools such as Word or Visio
     Diagrams drawn using design tools such as UML or SysML tools

Implementation-Your complete source code for implementation of the project as copyable text from the pdf, no line numbers, black text, white background, at least 10pt fixed point font

Test results to determine Correctness

If you want the grader to know why a submission is late or want to understand any other part of the submission, put a "Notes to the Grader" section at the beginning of your submission. For example, if the instructor grants you a week extension you need to state that in the Notes to the Grader section at the beginning of your submission so the grader does not deduct late points.

This class uses an Outlook Group to assist collaboration.  At the beginning of the semester, all student's JHU emails are added to the Group which allows students to send an email to the group which is sent to all other students including myself and graders.  Likewise, when a reply is sent to the Google Group, it is sent to all others in the group working as a distribution list.  

Students are encouraged to collaborate and help each other with the projects.  As such, students can team with one other student where there is only one submission for the team to Canvas where the front page CLEARLY indicates the names of both students in the group.  The one submission will be graded using the Assignment Rubric and both students will receive the same grade for that project submission.   

Sharing-It is extremely beneficial for learning for students to share with each other their work on projects.  Each project's artifacts are shared between students in the respective Discussion Board for Project Sharing.  This course uses Canvas discussions to facilitate sharing where each module has a "Project Sharing" discussion for students to share their work with other students and collaborate with each other.  As a student, you decide what to share or not share with other students in your Project Sharing discussion post for each module.  It is easiest to just post the pdf you submitted to Canvas for grading, or you could submit anything else like a short video, or you could reply with comments to other students shared artifacts, but you do need to post something to get credit for sharing.  You need to share no earlier than one module after the module due and before four modules after the module due.  As projects are graded before they are shared, credit is initially giving for sharing. Four modules after the module due and definitely by the end of the semester, the credit for Sharing for students who do not share any material will be revised.  Please help each other!  For many students the material is totally new and the first time you learn new concepts is difficult so please help each other!

Using work from other places-It facilitates learning to garner information from other sources to accomplish you own work. We are now at a point of time where you can get examples of work from the net, other students, AI like ChatGPT, and a myriad of other places all of which help you not only learn in this class but be more productive in your jobs.  JH just asks that you cite what you use from other sources and where you got it from. Never take any credit for work you did not do yourself.  Al Gore did not invent the internet.  As long as you give credit for where you get material, you can use any material you find anywhere to help you with your projects 

Grading Policy

Evaluation and Grading

Final grades will be determined by the percentage of total points earned divided by the total possible points in Canvas.

Late submissions will be reduced by 10% for each week late with max of 30%(no exceptions without prior coordination with the instructors).

There is no weighting of grades.

EP uses a +/- grading system (see “Grading System”, Graduate Programs catalog, p. 10).

Points Possible and distribution

Course Evaluation

Course Evaluation:  " data-mce-style="-webkit-tap-highlight-color: transparent; -webkit-print-color-adjust: exact; white-space: normal;">

You are responsible for carefully reading all assigned material and being prepared for discussion. The majority of readings are from the course text. Additional reading may be assigned to supplement text readings.

Post your initial response to the discussion questions by the evening of day 3 for that module week. Posting a response to the discussion question is part one of your grade for module discussions (i.e., Timeliness).

Part two of your grade for module discussion is your interaction (i.e., responding to classmate postings with thoughtful responses) with at least two classmates (i.e., Critical Thinking). Just posting your response to a discussion question is not sufficient; we want you to interact with your classmates. Be detailed in your postings and in your responses to your classmates' postings. Feel free to agree or disagree with your classmates. Please ensure that your postings are civil and constructive.

Discussions

Evaluation of preparation and participation is based on contribution to discussions.

Preparation and participation is graded with the following Discussion Rubric:

Assignments and Projects are evaluated by the following grading Rubric:

10% (max 30%) is deducted when late and per week late.

Quizzes on modules may include material from the current as well as prior modules, have a one hour limit, allow up to three attempts, are scored as the average of all attempts, and must be submitted by the 11:30pm on the 7th day of the module which is a Sunday.

Submit per the “Assignment and Project Submission” document.

Either a written, or graphical depiction of the design or combination of written + graphical depiction.  This does not need to be from a tool.  A hand drawn design may be all that is needed to convey your design, but generally ones from tools appear better.

Your source code for implementation of the project.

Output from Execution demonstrating meeting requirements.

During the Open Office, you can present your submitted projects with other students and any time during any module if any student asks for help, it is strongly appreciated when other students step in and help them get their projects working.

Academic Policies

Deadlines for Adding, Dropping and Withdrawing from Courses

Students may add a course up to one week after the start of the term for that particular course. Students may drop courses according to the drop deadlines outlined in the EP academic calendar (https://ep.jhu.edu/student-services/academic-calendar/). Between the 6th week of the class and prior to the final withdrawal deadline, a student may withdraw from a course with a W on their academic record. A record of the course will remain on the academic record with a W appearing in the grade column to indicate that the student registered and withdrew from the course.

Academic Misconduct Policy

All students are required to read, know, and comply with the Johns Hopkins University Krieger School of Arts and Sciences (KSAS) / Whiting School of Engineering (WSE) Procedures for Handling Allegations of Misconduct by Full-Time and Part-Time Graduate Students. This policy prohibits academic misconduct, including but not limited to the following: cheating or facilitating cheating; plagiarism; reuse of assignments; unauthorized collaboration; alteration of graded assignments; and unfair competition. Course materials (old assignments, texts, or examinations, etc.) should not be shared unless authorized by the course instructor. Any questions related to this policy should be directed to EP’s academic integrity officer at ep-academic-integrity@jhu.edu.

Students with Disabilities - Accommodations and Accessibility

Johns Hopkins University is committed to providing welcoming, equitable, and accessible educational experiences for all students. If disability accommodations are needed for this course, students should request accommodations through Student Disability Services (SDS) as early as possible to provide time for effective communication and arrangements.  For further information about this process, please refer to the SDS Website.

Student Conduct Code

The fundamental purpose of the JHU regulation of student conduct is to promote and to protect the health, safety, welfare, property, and rights of all members of the University community as well as to promote the orderly operation of the University and to safeguard its property and facilities. As members of the University community, students accept certain responsibilities which support the educational mission and create an environment in which all students are afforded the same opportunity to succeed academically.  For a full description of the code please visit the following website: https://studentaffairs.jhu.edu/policies-guidelines/student-code/

Classroom Climate

JHU is committed to creating a classroom environment that values the diversity of experiences and perspectives that all students bring. Everyone has the right to be treated with dignity and respect. Fostering an inclusive climate is important. Research and experience show that students who interact with peers who are different from themselves learn new things and experience tangible educational outcomes. At no time in this learning process should someone be singled out or treated unequally on the basis of any seen or unseen part of their identity.    If you have concerns in this course about harassment, discrimination, or any unequal treatment, or if you seek accommodations or resources, please reach out to the course instructor directly. Reporting will never impact your course grade. You may also share concerns with your program chair, the Assistant Dean for Diversity and Inclusion, or the Office of Institutional Equity. In handling reports, people will protect your privacy as much as possible, but faculty and staff are required to officially report information for some cases (e.g. sexual harassment).

Course Auditing

When a student enrolls in an EP course with “audit” status, the student must reach an understanding with the instructor as to what is required to earn the “audit.” If the student does not meet those expectations, the instructor must notify the EP Registration Team [EP-Registration@exchange.johnshopkins.edu] in order for the student to be retroactively dropped or withdrawn from the course (depending on when the "audit" was requested and in accordance with EP registration deadlines). All lecture content will remain accessible to auditing students, but access to all other course material is left to the discretion of the instructor.