CPSC 315 Programming Studio:
Fall 2015


NEWS: 11/3/15, 09:53AM (Tue)
Read-Only Bulletin Board.: 9/3/15, 12:16PM (Thu)

Page last modified: 12/11/15, 01:58AM Friday.

General Information Resources Weekly Schedule Credits Lecture Notes Example Code Read-Only Board

I. General Information


Dr. Yoonsuck Choe
Email: choe at tamu.edu
Office: HRBB 322B
Phone: 979-845-5466
Hours: TR 2:00pm-3:00pm

Teaching assistants and peer teachers:

Chien-An "Jay" Chen (TA: all sections)
Email: jaychen at cse.tamu.edu
Office: RDMC 021 111B (basement)
Office hours: MW 2-3pm.

Purnendu Kaul (Grader)
Email: pkaul at tamu.edu
Debanik Lahiri (Grader)
Email: debaniklahiri at tamu.edu

Jason Krezinski (Peer teacher, all sections)
Office hours: MW 10:00am-11:00am, F 10:00am-12:00pm
Office: HRBB 129


This class is intended for students who have completed CPSC 314 - Programming Languages, and are concurrently taking CPSC 313 - Intro to Computer Systems. It is meant to be somewhat of a "capstone" course for the lower-level computer science courses, before taking courses in the upper-level tracks.


TR 12:45pm–2:00pm, HRBB 124

The course is listed as a 2-hour per week lecture, and 2-hour per week lab, however it has been intentionally scheduled for 3 hours per week of lecture (along with the lab). We will meet a minimum of 19 lecture periods over the course of the semester. The idea is to "front-load" these lectures in the earlier part of the semester, to cover material that might be useful when working on the programming projects, and spend less lecture time during the project periods themselves. Also, some days when the instructor travels might be used as some of the "missed" days. The specific list of days we will meet will be provided on the course web page.

There is a final exam time reserved for this class. Although the plan is to wrap up the course before this time, students should leave the final exam time available until instructed otherwise, since it might be used for project presentations or something similar. However, there will not be a final exam in the course.

Labs: taught by the TA

Section 501: MW 3:00 pm-3:50 pm RMDC 111C
Section 502: MW 4:10 pm-5:00 pm RMDC 111C
Section 503: MW 5:45 pm-6:35 pm RMDC 111C


This course is intended as an intensive programming experience that integrates core concepts in Computer Science and familiarizes students with a variety of programming/development tools and techniques. Students will primarily work in small teams on month-long projects emphasizing different specializations within computer science. The course focuses on honing good programming techniques to ease code integration, reuse, and clarity.

The primary goal for this class is to have students emerge with strong programming skills, able to address both individual and team programming challenges competently. The class is meant to allow students to improve their programming skills through significant practice.


The expected accomplishments of the students are as follows:
  1. Become a confident software developer experienced in the full software development cycle.
  2. Become a capable and effective member in a small software development team.
  3. Become an effective communicator within the context of software projects.


The students who take this course should be able to demonstrate the following upon the completion of this course.
  1. Knowledge of programming and debugging tools.
  2. Knowledge of various programming paradigms.
  3. Ability to design and refine large software systems based on rough system requirements.
  4. Ability to implement and test software system design.
  5. Ability to work as a member of a software project development team.
  6. Knowledge of various software development paradigms.
  7. Ability to manage software development projects.
  8. Ability to write technical documentation regarding software systems.
  9. Ability to communicate the overall design and details of software systems.
  10. Introductory-level knowledge in database systems, artificial intelligence, and software engineering.


We will be using the following textbook: Other books that may be drawn from, and that might be useful references include both the first edition of Code Complete, as well as:

Computer Accounts:

  1. Computer accounts: if you do not have a unix account, ask for one on the CSE web page.

Topics to be covered:

Among the topics to be covered in lecture periods are: Though many topics will overlap, this course is not intended to be as in-depth or comprehensive as a standard software engineering course, which focuses more on project management - students may take the software engineering class after taking this class.

Note: You should expect to spend a significant amount of time (>10 hours/week) outside of class time on programming projects. This may require meeting with team members outside of the class/lab periods.

See the Weekly Schedule section for more details.


There will be three major projects in the course, each counting for 28% of the overall grade. Specific grading practices for each project will be announced when that project is given out, but the grade may include factors such as evaluation of code clarity, teamwork, etc. Peer evaluation may be used as a significant contributing factor to these grades (see below). The remaining 16% of the grade will be based on attendance (6%: attendance sheets will be circulated) and the two online quizzes (5% each).

The projects are scored by the team, however, different individual contribution can lead to differential grades given the same team score.

The grading scale expected to be used is: >90 = A; >80 = B; >70 = C; >60 = D; all else F.

Academic Integrity:

AGGIE HONOR CODE: An Aggie does not lie, cheat, or steal or tolerate those who do.

Upon accepting admission to Texas A&M University, a student immediately assumes a commitment to uphold the Honor Code, to accept responsibility for learning, and to follow the philosophy and rules of the Honor System. Students will be required to state their commitment on examinations, research papers, and other academic work. Ignorance of the rules does not exclude any member of the TAMU community from the requirements or the processes of the Honor System.

For additional information please visit: http://aggiehonor.tamu.edu/

For this class, certain aspects of the honor code need to be clarified.

  1. There may be times in this course where you or your team make use of external code/software/libraries. Whenever this is done, you must make sure that, in addition to following any restrictions on that code itself, you clearly document what the source of the external code was, and how it was used.
  2. There may be cases in this course where you or your team seeks outside assistance related to one of the projects. Any assistance received from people other than members of your team, the professor, teaching assistant, or peer teacher needs to be clearly documented.
  3. You will be working in team environments in this course, and your work as a team will be used to determine grades. As such, it is your responsibility, when asked, to:
    • accurately describe the work that you have done on a team project. Claiming credit for work that you have not done or that others did instead is a violation of the code.
    • accurately describe (to the best of your knowledge) the performance of other team members. "Covering" for another team member (claiming they did more work than you know they did) or "spiking" them (claiming they did less work than you know they did) are examples of honor code violations.
    • prevent (as best you can) or report (known) violations of the honor code by your other team members. You share responsibility when a project is turned in; if you are aware of a teammate having violated the code in his/her work on the project, and do not report it, you are claiming credit for that violation yourself.
If there are any questions or concerns about whether an action is appropriate, you should check with the professor or teaching assistant first. If in doubt, assume that it is not appropriate.

Course Policy:

Students with Disabilities:

The Americans with Disabilities Act (ADA) is a federal anti-discrimination statute that provides comprehensive civil rights protection for persons with disabilities. Among other things, this legislation requires that all students with disabilities be guaranteed a learning environment that provides for reasonable accommodation of their disabilities. If you believe you have a disability requiring an accommodation, please contact the Department of Student Life, Services for Students with Disabilities, in Cain Hall or call 845-1637.

II. Resources

  1. TBA

III. Weekly Schedule and Class Notes





1 9/1 Introduction; Project 1: Intro to Databases, Entity-relationship model, relational DB [Chapters 1, 9.1, 9.2]; IDE, programming proficiency survey.     slide01
1 9/3 Project 1: SQL Schema; Project 1 announcement IDE, GIT, Team assignment     slide03
2 9/8 Project 1: SQL queries, Database implementation; API Design Debugger use; Project 1 Design, DB engine [Chapter 23]   Project 1 Design Documents Due slide05
2 9/10 Software Design Principles; Testing and Test-Driven Development (TDD) [Chapter 5, Chapter 22] (SELF-STUDY: Naming, Style, Commenting [Chapters 11.1, 11.2, 31]) Project 1, DB engine     slide08
3 9/15 Debugging, Software development approaches; Agile Development [Chapter 5.1, 5.2, 5.3, 8.1, 8.2, 8.3] Project 1: Parsing   Project 1 DB Engine code due slide11
3 9/17 Agile Development; Collaborative Code Development; Project 1 intermediate review Project 1: Parsing, DB Engine Code Review/Debug     slide13
4 9/22 Design patterns; Code portability [Chapter 21, 24] Project 1: Integrating parser and DB engine   Project 1: Parser code due slide18
4 9/24 Code portability; Code performance; Code Tuning [Chapter 25, 26] Project 1: Integrating parser and DB engine     slide20
5 9/29 Project 2: Introduction to AI, Search Project 1: DB application coding   Project 1 Parser+DB engine integrated code due slide14
5 10/1 Project 2: Game Search Project 1: DB application coding     slide15
6 10/6 Project 2 Announcement, Network protocols and socket programming [General reading: Chapter 6.1-6.4] Project 1 status checl; Project 2 design (Choe) Project 2 announced Project 1 final version due web_link;
6 10/8 Project 1 presentation Project 2: game mechanics     web_link;
7 10/13 Advanced AI: Intro to machine learning Project 2: game mechanics / socket programming   Project 2 design documents due slide16-ml
7 10/15 Advanced AI: Neuroevolution Project 2: socket programming     slide16
8 10/20 No class Project 2: AI engine   Project 2 Game mechanics and server code due slide16
8 10/22 Project 3: Android introduction Project 2: AI engine     kwon-android01-choe
9 10/27 Project 3: Android programming Project 2: client GUI   Project 2 AI engine due kwon-android02-choe
9 10/29 No class Project 3: Android programming Project 2: client GUI    
10 11/3 Project 3: XML; SOLID principles Project 2 status check Project 3 announced Project 2 final version (including GUI client) due slide22
10 11/5 No class Android SDK installation and testing, emulator test run    
11 11/10 No class Android SDK user interface   Project 3 Design documents due
11 11/12 No class Android SDK: graphics    
12 11/17 Project 2 Live competition Project 3 status check   Project 3 user interface code due
12 11/19 No class Project 3 status check    
13 11/24 No class Project 3 status check   Project 3 core algorithm implementation due
13 11/26 No class (Thanksgiving) No labs on Wednesday    
14 12/1 Final project presentation: 501a-501g Project 3 status check    
14 12/3 Final project presentation: 502a-502h Project 3 status check    
15 12/8 Final project presentation: 503b-503h Project 3 status check   Project 3 final version due

IV. Credits

Most of the course content and lecture slides were originally developed by Prof. John Keyser, Prof. Jennifer Welch, and Prof. Jaakko Järvi. Thanks to Long Mai and Allen Hurst at Improving Enterprises for valuable feedback.

$Id: index.php,v 2014/08/30 20:21:26 choe Exp choe $