CSCE 315 Programming Studio Fall 2017 Tanzir Ahmed

People Instructor: Teaching Assistants: Peer Teachers: Tanzir Ahmed Teaching Assistants: Jorge Ivan Fuentes Rosado (501-503) Jinhao Chen(504-506) Peer Teachers: Katherine Drake (501-503) Kristen Pekala (504) William Flores (505) Regan Gunhouse (506) Credits for the materials (throughout the semester): Dr. John Keyser, Dr. Andruid Kerne

Background on the Course Meant to be a “capstone” to the lower- level classes Intention is to give lots of programming experience, mainly 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? Hint: Think in terms of “automating programming itself”

Programming Is it engineering? Yes. Is it science? Yes. Is it art? Yes. Hint: Think in terms of “automating programming itself”

“Studio” Course Treat programming more like an art Of course, after accepting the fact that there is significant science in it 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 This is, in reality, less than ideal

Software Development Lifecycle System Specification Our primary focus in this course, while learning a little bit of all others 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 Software project management (e.g., Agile) Programming tools (e.g., debuggers, profilers, testers) Project-specific subjects Databases Artificial Intelligence Human-Computer Interaction

Syllabus Review

Lectures We’ll meet for approximately 24 classes out of the 35 that we have available 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 or has conflicts

Attending Lectures Several lectures will be directly relevant to your projects Will be tested on the tightly-deadline projects Some lectures will cover topics not put into practice in these projects Tested on the quizzes (~6% of total) These are not just thrown in for fun! The lecture may be your only exposure to some important topics

Quizzes and Other Assignments Several small assignments and/or quizzes Some larger quizzes might be announced, while some others unannounced Makeups not allowed to ensure attendance Other assignments We will have an early individual programming assignment Later (if any) might have small programming exercises or short written reports

Projects 3 team projects, each about a month long Each project will be a team effort 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: Labs will not meet until 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!

Use of Lab Room RDMC 111C should be available to you when not being used for labs See the schedule of lab times to find busy times.

Reviews Might include code reviews Some code will be graded by other students! 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

Questions?