The course introduces students to principles, concepts and techniques associated with team-based development of large, complex software systems. Major topics include teamwork, configuration management, project management, requirements engineering, and systematic testing techniques. Students will learn to use software tools in the context of a Scrum-based Agile development project. It is assumed that students know how to program and debug using the Java language.
Piazza: Use Piazza for getting help fast and efficiently from classmates and the teaching staff (TAs and instructors). Rather than emailing questions to the teaching staff, we encourage you to post your questions on Piazza so that others may also benefit. Piazza can be accessed from the Module tab on Canvas as well as directly from the piazza website. Make sure you accept the email invitation to join Piazza at the beginning of the semester.
Email: For questions that are more personal in nature (e.g., grades, absences, etc), email the course account email@example.com. The email will be received by the entire course staff, and the appropriate person will respond.
Office hours: The course staff will keep office hours. Feel free to stop by to discuss your projects or ask questions. You can also bring your team to these meetings.
CS253 and all the prerequisites for CS253 including CS160, CS161, and CS200.
|First day of classes||Aug 21|
|Deadline to add without override||Aug 27|
|Deadline to drop||Sep 06|
|Midterm 1||Sep 22|
|Last day to withdraw||Oct 16|
|Midterm 2||Oct 27|
|Last day of classes||Dec 08|
|Final Exam||Dec 14|
An overall course grade will be awarded based on your performance on the following items.
Grades will be assigned according to the following table. The actual cutoffs may be adjusted lower depending on the performance of the entire class. After the midterm exam and before the final, we will announce the "approximate" cutoffs so that you know where you are. You must achieve at least 60% average across the midterm and final exams to receive a passing grade in this course.
Here is a short description of the formally graded elements of the course:Product Increments
You will work in teams of four to iteratively develop a mobile application and server during the semester. Product Increments refer to the software delivered at the end of each 3 week development cycle. Individual grades depend on the contribution of each team member to the Product Increment.Process Activities
Your team will follow an iterative process to develop your Product Increments during each development cycle. Individual grades depend on the participation in the process activities for each development cycle.Classroom/Homework
There will be small individual and team activities completed during class or assigned as homework.Midterm and Final Exams
There are two midterm exams and a final exam. The midterm exams will be held in class during the regular class period.Regrading
We will be glad to re-grade the same submission if you feel that there was a mistake in grading. Contact us by email firstname.lastname@example.org within 4 calendar days for a re-grade. Work will be re-graded in its entirety, and may result in an increase, decrease, or no change in the grade. Note that, once we have graded an assignment, we will not allow you to re-do and re-submit it for grading.
No late submissions are accepted for Scrum Projects or Scrum Activities. If you miss an exam, you will recieve a score of zero.
If there are reasons that are unexpected and beyond your control (e.g., illness) or university sanctioned trips, short extensions will be granted on a case-by-case basis and are more likely when permission is sought in advance.
All students are expected to conduct themselves professionally. We (the instructors and teaching assistants) assume you are familiar with the policies in the student information sheet for the department and the department conduct code. Additionally, you are computing professionals, albeit perhaps just starting. You should be familiar with the code of conduct for the primary professional society, ACM. You should read the ACM Code of Conduct.
This course will adhere to the CSU Academic Integrity Policy as found in the Student Conduct Code. At a minimum, violations will result in a grading penalty in this course and a report to the Office of Conflict Resolution and Student Conduct Services.
Students not already familiar with the CSU Honor Pledge should review this clear and simple pledge and always adhere to it. Academic dishonesty will be dealt with severely. The first instance of cheating will result in negative credit. The second instance will result in a failing grade and other penalties dictated by departmental and university policies.
We work to maintain an environment supportive of learning in the classroom and laboratory. Towards that end, w require that you be courteous to and respectful of your fellow participants (i.e., classmates, instructors, teaching assistants and any tutors). In particular:
We require you to follow the guidelines listed below for postings on Canvas: