CS 30700, Fall 2016

ANNOUNCEMENTS
(This page last modified Tuesday, November 15.)

• CS 30700 Final Project Presentations and Demonstrations will be in our regular class room (MATH 175) at our regular class time Tuesday and Thursday, 3:00 - 4:15 pm. Each team will be given a maximum of 10 minutes to present their project and to demonstrate it however they like.

  You may use the computer and document camera in the class room for your presentation and demonstration or you may bring in your own equipment. I suggest that all teams drop by MATH 175 before the day they present to make sure that any laptop you plan to use can be connected to the classroom projector and that any phones you plan to use display well on the classroom document camera.

  The presentation and demo may be done by one team member, two or three, or the whole team. Start with each team member at the front introducing herself/himself clearly (no mumbling) and saying what your role was in the project.

  Every member of your team is required to be in class the day of your presentation and to remain in the class room the whole time. You are encouraged to attend other days (to see other team presentations), but are not required to do so. The rubric we will use in grading your team's Final Project Presentation and Demonstration is on both the Course Schedule page and the Grading Rubrics page.

  Regardless of the day any team does its Final Project Presentation and Demonstration, each team may keep working on its project until 11:59 pm, Friday, December 9.

  (Your team's Sprint 3 Retrospective and your individual Second Peer Evaluation are both due Monday, December 12.)

Course Work

Project Grade Composed of

Team Member Contributions

Textbook

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

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.