CS 30700, Fall 2016

(This page last modified Tuesday, November 15.)

Welcome to CS 30700 Software Engineering

CS 30700 meets Tuesday and Thursday, 3:00 - 4:15 pm in MATH 175

CS 30700 Website <https://www.cs.purdue.edu/homes/bxd/307>

Course Work

Project 70%
Midterm Exam 25%
Daily Quizzes 5%

Project Grade Composed of

Project Charter 5%
Product Backlog (Requirements Document) 15%
Design Document 15%
Sprint 1 Planning Document 7%
Sprint 1 Review 10%
Sprint 1 Retrospective 3%
Sprint 2 Planning Document 7%
Sprint 2 Review 10%
Sprint 2 Retrospective 3%
Sprint 3 Planning Document 7%
Sprint 3 Review (Final Project Presentation and Demonstration) 15%
Sprint 3 Retrospective 3%
Total 100%

Team Member Contributions

What you earn on the 100 team points above will be subject to a multiplier based on peer evaluation of your team members. Read more about Team Member Contributions including how we will compute them.


Any up-to-date Software Engineering book (borrowed from a friend or from a library or in electronic format) will be fine. Make sure the book covers the Agile software development process, specifically Scrum.

Here are some typical books you might choose:
Essentials of Software Engineering, Frank Tsui, Jones & Bartlett, 2014
Beginning Software Engineering, Rod Stephens, John Wiley & Sons, 2015
Essential Scrum: A Practical Guide to the Most Popular Agile Process, Kenneth Rubin, Addison-Wesley, 2013 (online access to this book is available through the Purdue University Libraries)

The slides used in the classroom contain everything you need to know. They began as slides accompanying Object-Oriented Software Engineering: Practical Software Development using UML and Java, Timothy C. Lethbridge and Robert Laganiere, McGraw Hill, 2001. But, they have been revised nearly every semester and now bear little resemblance to the original slides.

Ownership of Your CS 30700 Team Project

At the conclusion of CS 30700 you team will have full ownership of your project. It does not belong to the Department of Computer Science or Purdue University.

Purdue opens up intellectual property rules for students
(right click on this link to open in a new tab or a new window)

"Interpreted strictly, the intellectual property policy states any invention created with the use of Purdue resources is subject to university ownership. The new interpretation offers students clear ownership rights as long as the resources used were part of a course and were available to all students in the course; that the student was not paid by the university or a third party; and the class or project was not supported by a corporation or government grant or contract."

Purdue Student Intellectual Property Rules for Course-Generated Innovations
(right click on this link to open in a new tab or a new window)

"... the University claims no ownership rights to Course-Generated Intellectual Property created by Purdue students, provided that:
(A) student innovator(s) made use of resources that are (i) routinely made available by the College/Department administering the University course; and (ii) are provided to all students enrolled in the course in an equitable manner;
(B) the relevant student(s) are not paid by Purdue University, whether through internal funds or under a grant or contract with a third party; and
(C) there are no preexisting obligations for Purdue in connection with such Course-Generated Intellectual Property."

(A), (B), and (C) all apply to CS 30700.

© 2016 by Purdue University Department of Computer Science.  All rights reserved.