DOC PREVIEW
TAMU CSCE 315 - Introduction

This preview shows page 1-2-3-4 out of 11 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 11 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 11 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 11 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 11 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 11 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

CPSC 315 Programming StudioPeopleBackground on the Course“Studio” CourseLecturesCode ConstructionTopicsProjectsLabReviewsSyllabus ReviewCPSC 315Programming StudioSpring 2009Frank ShipmanPeople•Professor: Frank Shipman•Teaching Assistant: Tim MannBackground 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)“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, practiceLectures•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 workCode ConstructionSystem SpecificationRequirements AnalysisArchitectural DesignDetailed DesignCoding and DebuggingMaintenanceSystem TestingUnit TestingTaken from Code CompleteTopics•Programming techniques and style•Software design principles•Basic collaborative programming skills•Programming tools•Project-specific subjectsProjects•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 materialLab•Note: Lab will meet tomorrow•Lab times:–TA demos/tools instructions–Use as team meeting times–Code reviewsReviews•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 codeSyllabus


View Full Document

TAMU CSCE 315 - Introduction

Download Introduction
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Introduction and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Introduction 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?