Welcome!

Welcome to the CSE 308 Web site. If you are enrolled in the course, be sure to periodically check the course schedule for all materials and changes as the semester moves along. Note that all grades will be posted to Blackboard. Also note that all students enrolled in this course should have U4 standing, and thus have experience in 300-level classwork, and so must be on track to graduate in either May or December, 2014.

The Project

This semester, all teams will be developing a Google App Engine Web App which will be deployed at the end of the semester to Appspot. The technology choices for teams this semester have been limited in comparison to semesters past. The hope is that it prevents teams from spinning their wheels while deciding which APIs to go with. There may be things you won't like about the tech choices made, but you'll just have to work around those issues. Note that students pursuing the Game Programming Specialization may do an alternate (but closely related) game project using the same technologies. More on this during the project unveiling the first week of class.

Roles

For the group project, students will be divided into teams of four. Project responsibilities will be carefully divided such that all students are making contributions and the project benefits as a whole. Each team will have four members that fit into one of the roles listed below. This is not to say that students in these roles are solely responsible for these domains, all team members should make contributions as needed to progress the project across all domains. But, the person in each role will be the primary decision maker for that doamin. Note that all students are considered Software Engineers, but additionally, students will be assigned the following roles:

Rules

Before starting the semester, there are a few rules of note that everyone must understand.

Team Programming

One of the principles that will be emphasized this semester is team programming, which involves multiple programmers working collaboratively on the same task. This is an efffective technique for preventing stalls in the development process. Students will be encouraged to do all programming using this technique and in addition, for all project responsibilities, teams will designate backup developers who will aid in the completion of a task when needed and will take over a task when a developer is overloaded.

Teams

Development teams, with roles, will be listed below as they are determined. Students may form their own teams if they wish. Remaining students not assigned to a team will be placed by the instructor. I strongly advise forming teams around similar schedules. For example, past experience has shown that communiting students work well together because they may choose to meet and work off-campus rather than on. Note that should any changes to a team occur, the instructor must immediately be informed, as this is the only official teams list. Note that the instructor has assigned a name to each team (using Crayola Crayon colors), if you really hate your team name, you may select another if the entire team agrees. Below is the current pool of students, again, as students form teams they will be listed below as such.

The Alien Armpit Team
Konstantin Uroskin
Konstantin Uroskin
Joseph Siffert
Joseph Siffert
Jason Keil
Jason Keil
Jonathan Stein
Jonathan Stein
Lead Programmer Project Manager Lead Designer Data Designer


The Cerulean Frost Team
Rasmita Adhikary
Rasmita Adhikary
Soo Yeon Kim
Soo Yeon Kim
Maxwell Stein
Maxwell Stein
Brian Glatt
Brian Glatt
Lead Programmer Project Manager Lead Designer Data Designer


The Cyber Grape Team
Philip Ammirato
Philip Ammirato
Shane Harvey
Shane Harvey
Jamie Lapine
Jamie Lapine
Soumadip Mukherjee
Soumadip Mukherjee
Lead Programmer Project Manager Lead Designer Data Designer


The Electric Lime Team
Akbar Hirani
Akbar Hirani
David Sam
David Sam
Jacky Liang
Jacky Liang
Anne Chen
Anne Chen
Lead Programmer Project Manager Lead Designer Data Designer


The Fuzzy Wuzzy Team
Changda Li
Changda Li
Xun Zhu
Xun Zhu
Zhe Wang
Zhe Wang
Wenhao Lu
Wenhao Lu
Lead Programmer Project Manager Lead Designer Data Designer


The Jazzberry Jam Team
Christopher Ogden
Christopher Ogden
Varsha Paidi
Varsha Paidi
Hanne Paine
Hanne Paine
Scott Macdonell
Scott Macdonell
Lead Programmer Project Manager Lead Designer Data Designer


The Laser Lemon Team
Anas Patel
Anas Patel
Stephanie Shaffer
Stephanie Shaffer
Jamin Park
Jamin Park
Jaehyeong Lee
Jaehyeong Lee
Lead Programmer Project Manager Lead Designer Data Designer


The Magic Mint Team
Yi Zhou
Yi Zhou
Hao Wang
Hao Wang
Shixiong Liu
Shixiong Liu
Yunlong Zhang
Yunlong Zhang
Lead Programmer Project Manager Lead Designer Data Designer


The Mango Tango Team
Sakib Ahmed
Sakib Ahmed
Wei Chen
Wei Chen
James Snak
James Snak
Mohammad Asif
Mohammad Asif
Lead Programmer Project Manager Lead Designer Data Designer


The Mauvelous Team
Stefan Gawrys
Stefan Gawrys
Adam Abdelaziz
Adam Abdelaziz
Vincent Chan
Vincent Chan
Kevin Lui
Kevin Lui
Lead Programmer Project Manager Lead Designer Data Designer


The Metallic Seaweed Team
Ruzin Wadhwa
Ruzin Wadhwa
Pranjal Natu
Pranjal Natu
Priyanka Khante
Priyanka Khante
Sanoussy Sangary
Sanoussy Sangary
Lead Programmer Project Manager Lead Designer Data Designer


The Screamin' Green Team
Kalon Cheong
Kalon Cheong
Krisjanis Gaidis
Krisjanis Gaidis
Allen Fung
Allen Fung
Rahul Sarna
Rahul Sarna
Lead Programmer Project Manager Lead Designer Data Designer


The Sunburnt Cyclops Team
Serge Ostrowski
Serge Ostrowski
Phillip Ninan
Phillip Ninan
Brendan Rivers
Brendan Rivers
Asher Kaufman
Asher Kaufman
Lead Programmer Project Manager Lead Designer Data Designer




SBU CS

Web page created and maintained
by Richard McKenna