1 / 11

CPSC 315 Programming Studio

CPSC 315 Programming Studio. Spring 2009 Frank Shipman. People. Professor: Frank Shipman Teaching Assistant: Tim Mann. 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.

nodin
Télécharger la présentation

CPSC 315 Programming Studio

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. CPSC 315Programming Studio Spring 2009 Frank Shipman

  2. People • Professor: Frank Shipman • Teaching Assistant: Tim Mann

  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. “Studio” Course • Programming as “art,” “science,” “engineering.” • 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 • You should have plenty of interaction with and feedback from the professor/TA • Practice, practice, practice

  5. Lectures • We’ll meet on 20 class periods (out of 28) • Expect to meet most dates at the beginning of the semester • Will skip lectures later in semester, during projects • Lectures should be helpful for your programming work

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

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

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

  9. Lab • Note: Lab will meet tomorrow • Lab times: • TA demos/tools instructions • Use as team meeting times • Code reviews

  10. 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

  11. Syllabus Review • Questions?

More Related