1. CSCE 315 Programming Studio Spring 2013 John Keyser

2. People Professor: –John Keyser Teaching Assistants: –Chris Pu –Bill Hamilton Peer Teachers: –David Blalock –Nick Melnyk –Aaron Moore –Christine Woods

3. Background on the Course Meant to be a “capstone” to the lower-level classes. Intention is to give lots of programming experience, in a team environment. Should be prepared for any programming assignment in upper-level classes Should be better prepared for industry programming jobs (internships/co-ops)

4. Programming Is it engineering? Is it science? Is it art?

5. Programming Is it engineering? Yes. Is it science? Yes. Is it art? Yes.

6. “Studio” Course Treat programming more like an art The idea of a studio course is to have an environment where students can practice and refine their skills –Your skills should markedly improve over the semester –Practice, practice, practice –Ideally, you should have plenty of interaction with and feedback from the professor/TA/PTs

7. Code Construction System Specification Requirements Analysis Architectural Design Detailed Design Coding and Debugging Maintenance System Testing Unit Testing Taken from Code Complete

8. Topics Programming techniques and style Software design principles Basic collaborative programming skills Programming tools Project-specific subjects

9. Syllabus Review

10. Lectures We’ll meet on 28 class periods (out of 42) –Expect to meet most dates at the beginning of the semester –Will skip lectures later in semester, during projects –Will skip lectures if professor travels

11. Attending Lectures Several lectures will be directly relevant to your projects Some lectures will cover topics not put into practice in these projects –These are not just thrown in for fun! –The lecture may be your only exposure to some important topics

12. Quizzes and Other Assignments Several small assignments and/or quizzes Quizzes will be unannounced, and makeups not allowed Other assignments –We will have an early individual programming assignment –Later might have small programming exercises or short written reports

13. Projects 3 projects, each about a month long Each project will be a team project –3 people per team Might require use of specific tools, languages, approaches Topics from range of CS fields –Lectures will cover additional material

14. Lab Note: Lab will not meet until Wednesday. –Probably only Tuesday and Wednesday of next week. Lab times: –Use as team meeting times –TA demos/tools instructions –Use as instructor meeting times –Code reviews Lab times are not optional!

15. Use of Lab Room RDMC 111C should be available to you 24/7 However, the class is in use: –9:10-5:00 MW –9:35-4:45 TR Can use at other times; some TA office hours in there.

16. Reviews Might include code reviews Public review/comments on code/design/documentation/etc. –During lab or lecture times Programs you work on/submit will not be considered private, for this class You might be asked to present your code

17. Questions?

18. Homework Download and read this article: Don Knuth’s Turing Award Lecture: –“Computer Programming as an Art” –http://doi.acm.org/10.1145/361604.361612http://doi.acm.org/10.1145/361604.361612