1 / 46

COMP 1600

Introduction to Programming. COMP 1600. Who am I?. Dr. Barry Wittman Not Dr. Barry Whitman Education: PhD and MS in Computer Science, Purdue University BS in Computer Science, Morehouse College Hobbies: Reading, writing Enjoying ethnic cuisine DJing Lockpicking Stand-up comedy.

parrish
Download Presentation

COMP 1600

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Introduction to Programming COMP 1600

  2. Who am I? • Dr. Barry Wittman • Not Dr. Barry Whitman • Education: • PhD and MS in Computer Science, Purdue University • BS in Computer Science, Morehouse College • Hobbies: • Reading, writing • Enjoying ethnic cuisine • DJing • Lockpicking • Stand-up comedy

  3. How can you reach me? • E-mail:wittman1@otterbein.edu • Office: The Point 105 • Phone: (614) 823-2944 • Office hours: MWF 10:30 a.m. – 12:00 p.m., MWF 1:50 – 2:45 p.m., (in The Point 113) TR 1:00 – 4:00 p.m., and by appointment • Website: http://faculty.otterbein.edu/wittman1/

  4. Who are you?

  5. Why are we here? • What's the purpose of this class? • What do you want to get out of it? • Do you want to be here? • Have you programmed before?

  6. Course Overview

  7. Textbook • Barry Wittman, Aditya Mathur, and Tim Korb • Start Concurrent: An Introduction to Problem Solvingin Java with a Focus on Concurrency • Available: https://start-concurrent.github.io/

  8. A note about the book… • The book's not bad • At least it's free • Your feedback is highly valued for the next edition • I highly encourage you to read it • However, computer science is very much an applied science • Reading the book is not enough • You should be programming every day (or maybe every other day) to master the concepts

  9. Computer science • What's a computer? • What's computer science? • What's a computer program?

  10. Algorithms • What's an algorithm? • A finite set of steps you can follow to solve a problem • Can you give an example? • Long division

  11. Programming languages • What's a programming language? • Examples: • C++ • Java • PHP • ML • Prolog • A language we can use to encode an algorithm into a form a computer can execute

  12. Compiler • What's a compiler? • Turns the (human readable) programming language into the (computer readable) instructions that a computer executes • For Java, we'll be using Eclipse as our compiler

  13. Course focus • Problem solving (writing the algorithm) • Converting the algorithm to Java • Features of Java we will focus on: • Variables • Mathematical operations • Selection statements (making choices) • Loops (repeating things) • Methods (dividing work into chunks) • Arrays (lists of things) • Input and output • Classes and object orientation • Searching and sorting • Image and audio processing

  14. More information • For more information, visit the webpage: http://faculty.otterbein.edu/wittman1/comp1600 • The webpage will contain: • The most current schedule • Notes available for download • Reminders about projects and exams • Syllabus (you can request a printed copy if you like) • Detailed policies and guidelines • Piazza will allow for discussion and questions about the projects: https://piazza.com/otterbein/fall2019/comp1600

  15. Projects

  16. Five projects • 35% of your grade will be five projects • Each will focus on a different area from the course: • I/O and arithmetic • if statements • Loops • Methods and arrays • Sorting, searching, and image processing • Each project is individual

  17. Turning in projects • Projects must be turned in by uploading them to Blackboard (https://otterbein.blackboard.com) before the deadline • Do not put projects in your public directories • Late projects will not be accepted • Exception: Each student will have 3 grace days • You can use the grace days together or separately as extensions for your projects • You must inform me before the deadline that you are going to use grace days • Assignments that don't compile get 0 points

  18. Labs In-class Programming Exercises

  19. Labs • 15% of your grade will be based around programming labs • Labs are on Tuesdays and Thursdays (mostly Tuesdays) • Each lab will focus on the solution of a problem • Work should be done individually, but the goal is to learn, and I will help everyone

  20. Quizzes

  21. Pop Quizzes • 5% of your grade will be pop quizzes • These quizzes will be based on material covered in the previous one or two lectures • They will be graded leniently • They are useful for these reasons: • Informing me of your understanding • Feedback to you about your understanding • Easy points for you • Attendance

  22. Exams

  23. Exams • There will be two equally weighted in-class exams totaling 30% of your final grade • Exam 1:09/23/2019 • Exam 2: 11/04/2019 • The final exam will be worth 15% of your grade • Final:8:00 – 10:00 a.m. 12/11/2019

  24. Exam format • Conceptual portion • Multiple choice and short answer • Programming portion • Short programming problems you will write code for

  25. Course Schedule

  26. Tentative schedule

  27. Project schedule • Project 1: 5% Tentatively due 09/20/2019 • Project 2: 6% Tentatively due 10/04/2019 • Project 3: 7% Tentatively due 10/25/2019 • Project 4: 7% Tentatively due 11/15/2019 • Project 5: 10% Tentatively due 12/06/2019

  28. Policies

  29. Grading breakdown

  30. Grading scale

  31. Attendance • You are expected to attend class • You are expected to have read the material we are going to cover before class • Missed quizzes cannot be made up • Exams and labs must be made up before the scheduled time, for excused absences

  32. R-E-S-P-E-C-T • I hate having a slide like this • I ask for respect for your classmates and for me • You are smart enough to figure out what that means • A few specific points: • Silence communication devices • Don't use the computers except when explicitly asked to • No food or drink in the lab

  33. Computer usage • Sometimes, I will do code examples in class • In those cases, you are welcome to follow along • However, students are always tempted to browse the Internet, etc. • Research shows that it is nearly impossible to do two things at the same time (e.g. use Reddit and listen to a lecture) • For your own good, I will enforce this by taking 1% of your final grade every time I catch you using your computer for anything other than coding

  34. Academic dishonesty • Don't cheat • First offense: • I will give you a zero for the assignment, then lower your final letter grade for the course by one full grade • Second offense: • I will fail you for the course and try to kick you out of Otterbein University • Refer to the Student Handbook for the official policy • Ask me if you have questions or concerns • You are never allowed to look at another student's code • I will use tools that automatically test code for similarity

  35. Programming projects • Must compile • If your program does not compile, it will score zero points • Must be handed in on time • If your program is late (and grace days are not available), it will score zero points • Must be done individually • If I can ascertain that code from one student's project appears in another student's project, both projects will score zero points • Both students will also have a full letter grade reduction at the end of the semester

  36. Learning Differences • If you have a documented learning difference please contact Kera McClain Manley, the Disability Services Coordinator, to arrange for whatever assistance you need. The Disability Services is located in Room #13 on the second floor of the Library in the Academic Support Center. You are welcome to consult with me privately to discuss your specific needs. For more information, contact Kera at kmanley@otterbein.edu, (614) 823-1618 or visit Disability Services.

  37. How to Succeed in this Course

  38. Bad students… • Don't ask questions • Don't come to office hours • Don't ask for help • Treat education as a passive experience • Are happy when a class is easy • In other words, they act as if college is high school

  39. Good students… • Ask questions • Come to office hours • Ask for help • Actively pursue all the knowledge and skills they can • Are angry when a class is easy

  40. Flowcharts for COMP 1600 Flowchart for success: Flowchart for failure:

  41. Computers

  42. What is a computer? • Hard to define exactly • The term "computer" originally referred to a person who did computations • A computer is a machine that manipulates data according to a list of instructions

  43. Kinds of computers

  44. Upcoming

  45. Next time… • Come to lab tomorrow (even though we won't have a graded assignment) just to get familiar with Eclipse and make sure you can log in • On Wednesday, we'll cover a few Java basics • Then we will talk about the history of computers and the definition of computer science

  46. Reminders • Read Chapter 1

More Related