This course covers the fundamental concepts of object-oriented programming languages, including data abstraction and typing, class inheritance and generic types, prototypes and delegation, concurrency control and distribution, object-oriented databases, and implementation. Object-oriented solutions will be developed in one or more high-level object-oriented programming languages.
This course explores the object-oriented programming paradigm in detail. Object-oriented programming is a shift in the way programs are designed as well as implemented.
Students will understand the difference between traditional structured programming design and implementation and object-oriented design and implementation. Specifically, students will understand and be capable of appropriately using:
Students will be familiar with an object-oriented design methodology (for example, using the Unified Modeling Language—UML).
Students will utilize one or more object-oriented programming languages to develop object-oriented solutions to programming problems.
Object-oriented programming is both a way of thinking and conceptually designing software, as well as a programming methodology. Thus this course will devote an equal amount of time to understanding the object-oriented design paradigm and object-oriented programming. A well-designed object-oriented model is easily translated into any number of programming languages that support object-oriented concepts, while a poorly-designed model can result in endless difficulties—regardless of the power of the implementation language or the skill of the programmer.
The course will include regular homework and/or programming assignments. Unless otherwise specified, assignments are due before the beginning of class on the due date. There will be no credit given for late assignments (without an excused absence)—turn in as much as you can.
Reading assignments should be completed before the lecture covering the material. Not all reading material will be covered in the lectures, but you will be responsible for the material on homework and exams. Quizzes over the assigned reading may be given at any time.
See the GFU CS/IS/Cyber policies for collaboration and discussion of collaboration and academic integrity. Most students would be surprised at how easy it is to detect collaboration in programming—please do not test us! Remember: you always have willing and legal collaborators in the faculty.
Almost all of life is filled with collaboration (i.e., people working together). Yet in our academic system, we artificially limit collaboration. These limits are designed to force you to learn fundamental principles and build specific skills. It is very artificial, and you'll find that collaboration is a valuable skill in the working world. While some of you may be tempted to collaborate too much, others will collaborate too little. When appropriate, it's a good idea to make use of others—the purpose here is to learn. Be sure to make the most of this opportunity but do it earnestly and with integrity.
The mission and vision statement of the Computer Science & Information Systems (CSIS) program states that our students are distinctive by "bringing a Christ-centered worldview to our increasingly technological world."
As one step towards the fulfillment of this objective, each semester, the engineering faculty will collectively identify an influential Christian writing to be read and reflected upon by all engineering faculty and students throughout the term. As part of the College of Engineering, CSIS students participate in this effort, known as Engineering Your Soul (EYS). This exercise will be treated as an official component of every engineering course (including CSIS courses) and will be uniquely integrated and assessed at my discretion, typically as a component of the quiz grade.
Students should read the assigned reading each week. Regular meetings will be scheduled throughout the semester that can be attended for chapel elective credit. Students should attend these meetings prepared to discuss the assigned reading, or email a reflection on the assigned reading on or before each meeting date.
It is our hope that students will not view this as one more task to complete, but as a catalyst for continued discussion ultimately leading to a deeper experience of Jesus Christ.
All students in the College of Engineering are required to create and maintain an online portfolio on Portfolium to showcase their best work. Portfolium is a "cloud-based platform that empowers students with lifelong opportunities to capture, curate, and convert skills into job offers, while giving learning institutions and employers the tools they need to assess competencies and recruit talent."
Students will post portions of their coursework to Portfolium as directed by their instructor. For example, a portfolio entry might be PDF of poster or presentation content, screenshots or a video demonstration of a software or hardware project, or even an entire source code repository. In addition to required portfolio entries, students are encouraged to post selected work to their portfolios throughout the year.
Students will work with their faculty advisor to curate and refine their portfolios as they progress through the program. Students shall ensure that all portfolio entries are appropriate for public disclosure (i.e., they do not reveal key components of assignment solutions to current or future students).
If you have specific physical, psychiatric, or learning disabilities and require accommodations, please contact the Disability Services Office as early as possible so that your learning needs can be appropriately met. For more information, go to ds.georgefox.edu or contact Rick Muthiah, Director of Learning Support Services (503-554-2314 or email@example.com).
The Academic Resource Center (ARC) on the Newberg campus provides all students with free writing consultation, academic coaching, and learning strategies (e.g., techniques to improve reading, note-taking, study, time management). The ARC, located in the Murdock Learning Resource Center (library), is open from 1:00–10:00 p.m., Monday through Thursday, and 12:00–4:00 p.m. on Friday. To schedule an appointment, go to the online schedule at arcschedule.georgefox.edu, call 503-554-2327, email firstname.lastname@example.org, or stop by the ARC. Visit arc.georgefox.edu for information about ARC Consultants' areas of study, instructions for scheduling an appointment, learning tips, and a list of other tutoring options on campus.
The final course grade will be based on:
|Week 1–2||Introduction to C++||Ch. 1–6||-||-|
|1/16||Martin Luther King, Jr. Day — no class|
|Week 3||Introduction to OOP and UML||Sec. 15.1||Ch. 1–2||-|
|Week 4||Class Diagrams||-||Ch. 3–4||pp. xi, xiii, xv|
|Week 5||Object Interaction||-||Ch. 4, 9||pp. 1–8|
|Week 6||Class Relationships||-||Ch. 5||pp. 11–23|
|Week 7–9||C++ Implementations||Ch. 7, 14–15; Sec. 19.3||-||pp. 23–31|
|2/28||Midterm exam||Ch. 1–7||Ch. 1–5, 9||-|
|Week 10||Collections||Ch. 9–11; Appx. A||-||pp. 8–11, 351–355|
|Week 11||Exception Handling||Sec. 18.1||-||pp. 81–95, 107–116, 135–136|
|Week 12||Spring break — no class||-||-||-|
|Week 13||Templates||Ch. 16||-||pp. 137–150|
|Week 14||C++ I/O||Ch. 8||-||pp. 163–184, 219–220|
|4/14||Good Friday — no class|
|Week 15||Design Patterns||-||-||pp. 221–222, 257–271, 293–303, 315–330|
This page was last modified on 2017-08-18 at 07:44:43.
George Fox University · 414 N Meridian St · Newberg, Oregon 97132 · 503-538-8383
Copyright © 2015–2017 George Fox University. All rights reserved.