CSCE 315 Programming Studio Spring 2012 John Keyser

People Professor: John Keyser Teaching Assistants: Chris Pu, Chris Aikens Peer Teachers: Daniel Nemec, Andy Hampton

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)

Programming Is it engineering? Is it science? Is it art?

“Studio” Course Treat programming as somewhat of 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

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

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

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 when professor travels

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

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

Lab Note: Lab will not meet this week. Lab times: Use as team meeting times TA demos/tools instructions Use as instructor meeting times Code reviews Lab times are not optional!

Use of Lab Room RDMC 111C should be available to you 24/7 However, capstone classes will also meet there (do not go there these times): MW 4:10-7:05 TR 2:20-5:15 Other classes could be scheduled there.

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

Syllabus Review

Questions?