Kennesaw State University



|Kennesaw State University |

|DEPARTMENT OF COMPUTER SCIENCE |

|SPRING 2018 |

|CS 1302/01 Programming Principles II (MW 5pm) |

|Dr. Clincy |

| | |

|Course Description: |The second course in computer science provides coverage of more advanced topics of object-oriented programming. |

| |This includes the use of static variables and classes, multi-dimensional arrays, inheritance and polymorphism, |

| |text files and exception handling, recursion, and parameterized types. Elementary data structures (linked lists, |

| |stacks, and queues) are introduced to solve application problems. Graphical user interfaces and event driven |

| |programming are also introduced. Students must continue to use good programming style including proper |

| |documentation. |

|Learning Outcomes |After successful completion of this course, a student should: |

| | |

| |Design and use classes in programs. |

| |Construct programs that read and write data from/to hard drives. |

| |Recognize the difference between iterative and recursive methods and use them correctly in a program. |

| |Construct programs that use linear data structures. |

| |Develop correct/secure, reasonably efficient, and well-documented programs. |

| |Understand both the "program driven" and "event-driven" approaches to user interaction, including the relationship|

| |between event-driven programs and Graphical User Interfaces. |

| |Realize vulnerabilities in libraries or JRE when programming. |

|Prerequisites: |CS/CSE 1301 Programming Principles I |

|Textbooks and Resources: |Introduction to Java Programming, Comprehensive Version, 10th Edition (or 11th Edition) By Y. Daniel Liang Pearson|

| |Publishing, 2015 ISBN#: 978-0-13-376131-3 |

|Professor: |Dr. Clincy |

|Office: |Atrium Building – Office J-328 |

|Email Address: |vclincy at kennesaw.edu |

|Phone: |470-578-4440 |

| |Ms Tori McCullah (vmcculla@students.kennesaw.edu), Mr. Connor Kendrick (jkendr24@students.kennesaw.edu) |

|Office Hours: |MW: 315pm-5pm, 7:20pm-8pm (except 1/8, 1/15, 4/2, 4/4, 4/30, 5/2) |

|Time & Location: |MW 5pm-7:20pm, Atrium 110 |

|Website Address: |http:/ /ksuweb.kennesaw.edu/ ~vclincy/ (course lectures and handouts) |

| |D2L (labs and project assignments) |

|Tentative Course Schedule: Subject to Change (CS1302, MW, 5PM J-110) |

|Week |Dates |Activity |

|1 |1/8/2018, 1/10/2018 |Closed due to weather, Introduction |

|2 |1/15/2018, 1/17/2018 |Dr. MLK Holiday, Closed due to weather |

|3 |1/22/2018, 1/24/2018 |Chapters 9 Classes, Chapter 10 Thinking OOP |

|4 |1/29/2018, 1/31/2018 |Chapter 11 – Inheritance and Polymorphism |

|5 |2/5/2018, 2/7/2018 |Chapter 11 – Inheritance and Polymorphism, Chapter 12 – Exception Handling and Text I/O |

|6 |2/12/2018, 2/14/2018 |Chapter 12 – Exception Handling and Text I/O |

|7 |2/19/2018, 2/21/2018 |Project 1, Exam #1 (Ch 9,10,11 and 12) |

|8 |2/26/2018, 2/28/2018 |Chapter 13 – Abstract Classes & Interfaces, Chapter 14 – JavaFX Basics |

|9 |3/5/2018, 3/7/2018 |Chapter 14 – JavaFX Basics, Chapter 15 – Event-Driven Programming and Animation |

|10 |3/12/2018, 3/14/2018 |Chapter 15 – Event-Driven Programming and Animation, Project 2 |

|11 |3/19/2018, 3/21/2018 |Exam #2 (Ch 13, 14 and 15), Chapter 16 – JavaFX UI Controls |

|12 |3/26/2018, 3/28/2018 |Chapter 17 – Binary I/O, Chapter 18 – Recursion |

|13 |4/2/2018, 4/4/2018 |Spring Break, Spring Break |

|14 |4/9/2018, 4/11/2018 |Chapter 19 – Generics (Rollout Project 3) |

|15 |4/16/2018, 4/18/2018 |(Work on Project 3) Chapter 20 – Lists, Stacks, and Queues |

|16 |4/23/2018, 4/25/2018 |Project 3 Presentations 1of2 , Project 3 Presentations 2of2 |

|17 |4/30/2018, 5/2/2018 |Reading Day, Final Exam 6pm-8pm (6pm vs 5pm) |

| |

|Assessment: | |Grade Evaluation: |

|Labs |10% | | |

|Projects (1 & 2 - 6%/each, 3 - 12%) |24% |A |90% - 100% |

|Exam 1 |20% |B |80% - 89% |

|Exam 2 |20% |C |70% - 79% |

|Final Exam |26% |D |60% - 69% |

| | |F |59% or below |

|General Policies and Expectations: |

|Attendance at all classes is highly encouraged. Concepts and ideas discussed in one class are used as building blocks for more concepts and ideas in|

|the next class. In being successful in this subject matter, a good rule-of-thumb is to study at least 3 hours per one hour of lecture. Any class |

|sessions missed by the student are the student's responsibility to make up, not the Professor's. Makeup exams will NOT be given; instead, the final|

|exam will count in place of the missed exam; if the final exam is missed, an average of the other exams will be used. No finals will be given |

|outside of the University finals schedule. Project assignments MUST be turned in on time to receive full credit. Students will not be allowed to |

|makeup missed project assignments or labs. Students are expected to read the text and any other supporting documentation the Professor distributes.|

|If the student requires additional materials to read or additional problems to solve in better understanding the topics and concepts, the Professor |

|expects the student to take the initiative in locating additional materials or problems. The Professor expects students to take advantage of office |

|hours when needing clarification or help. The Professor greatly supports students sending emails at any time – it will be the goal of the Professor|

|to reply to emails within a 24-hour time span. |

| |

|Lab Work Grading Policy: Typically, each lab assignment is required to be accomplished in the corresponding lab session. |

| |

|Project Grading Policy: Each project assignment is expected to be accomplished in the corresponding session. If you cannot finish a project |

|assignment during the session, you are expected to finish it outside the class time and before the due date. Successfully completed programs must |

|satisfy their requirements outlined in the programming assignments. The grade depends on the quality of the program. All projects are individual |

|work. You are encouraged to discuss project assignments with other students and tutors as long as the following rules are followed: |

|You may provide assistance on how to use any of the software used by this course. |

|You view another student's code only for the purpose of offering debugging assistance. Students can only give advice on what to look for, but they |

|cannot debug your code for you. All changes to your code must be made by you. |

|Your discussion is subject to the empty hands policy, which means that you leave the discussion without any record (electronic or physical) of the |

|discussion. |

|Submissions that show identical code or slightly modified code will be considered plagiarism and are a violation of the Student Code of Conduct. |

| |

|For all project assignments, if a student consults any resource (other than the text and class notes) including another individual, this |

|consultation must be documented on the submission. This documentation must include what (or who) was consulted and what information was obtained. |

|Copying or paraphrasing code from another source or failure to provide this documentation will be considered a violation of the Student Code of |

|Conduct. |

| |

|Due dates for labs abd projects will be specified on the assignments themselves. Late labs and projects will be accepted up to 24 hours after the |

|due date for 50% credit. Assignments submitted more than 24 hours late will not be accepted. |

|Withdrawal Policy: |

|The last day to withdrawal without academic penalty is February 28, 2018. Ceasing to attend class or oral notice thereof DOES NOT constitute |

|official withdrawal and will result in the rendering of a grade of “F” for the class. Students wishing to withdrawal after the scheduled change |

|period (add/drop) must obtain and complete a withdrawal form from the Academic Services Department in the Registrar’s Office. |

|Enrollment Policy: |

|Only those students who are enrolled in the class may attend lectures, receive assignments, take quizzes and exams, and receive a grade in the |

|class. If a student is administratively withdrawn from this course, they will not be permitted to attend class nor will they receive any grade for |

|the class. |

|Academic Integrity Statement: |

|Every KSU student is responsible for upholding the provisions of the Student Code of Conduct, as published in the Undergraduate and Graduate |

|Catalogs. Section II of the Student Code of Conduct addresses the University's policy on academic honesty, including provisions regarding |

|plagiarism and cheating, unauthorized access to University materials, misrepresentation/falsification of University records or academic work, |

|malicious removal, retention, or destruction of library materials, malicious/intentional misuse of computer facilities and/or services, and misuse |

|of student identification cards. Incidents of alleged academic misconduct will be handled through the established procedures of the University |

|Judiciary Program, which includes either an "informal" resolution by a faculty member, resulting in a grade adjustment, or a formal hearing |

|procedure, which may subject a student to the Code of Conduct's minimum one semester suspension requirement. |

| |

|The provisions of the STUDENT CONDUCT REGULATIONS II regarding Academic Honesty in the KSU Undergraduate and Graduate catalogs will be strictly |

|enforced in this class. |

| |

|It is the student’s responsibility to ensure they fully understand to what extent they may collaborate or discuss content with other students. No |

|exam work may be performed with the assistance of others or outside material unless specifically instructed as permissible. If an exam or |

|assignment is designated “no outside assistance” this includes, but is not limited to, peers, books, publications, the Internet and the WWW. If a |

|student is instructed to provide citations for sources, proper use of citation support is expected. Additional information can be found at the |

|following locations. |

| |

| |

| |

| |

| |

Acknowledgement and Acceptance of Academic Honest Statement

In any academic community, certain standards and ethical behavior are required to ensure the unhindered pursuit of knowledge and the free exchange of ideas. Academic honesty means that you respect the right of other individuals to express their views and opinions, and that you, as a student, not engage in plagiarism, cheating, illegal access, misuse or destruction of college property, or falsification of college records or academic work.

As a member of the Kennesaw State University academic community you are expected to adhere to these ethical standards. You are expected to read, understand and follow the code of conduct as outlined in the KSU graduate and undergraduate catalogs. You need to be aware that if you are found guilty of violating these standards you will be subject to certain penalties as outlined in the college judiciary procedures. These penalties include permanent expulsion from KSU.

Read the Academic Honesty Statement and then sign and date in the space below. You are required to abide by these ethical standards while you are a student at KSU. Your signature indicates that you understand the ethical standards expected of you in this academic community, and that you understand the consequences of violating these standards.

CS1302___________ _____ ___ Dr. Clincy _________________________

Course Name Professor’s Name

Print Name Student ID Number

Signature Date

(Please fill-out, sign and turn-in this page to the Professor at the beginning of the semester – the Professor will not issue grades until this page is received from the student)

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download