No Silver Bullet
Kode Vicious
Software Analytics

Create your blog and

make entry on class wiki.

HW1: Ex 1.3, 1.8, 1.9, 1.10
Post by 1:40 PM

Get familiar with Ubuntu, Subversion, and VirtualBox

Learn about scripts.

Socio-technical Systems

Chapter 10

HW3: Ex 10.6, 10.10
Post by 1:40 PM

Get familiar with Ubuntu, Subversion, and VirtualBox

Learn about scripts.

Extra Credit: Write a script myList.[script extension] that lists the top-level directory contents of its containing directory in an html file displayed in a browser. Demo in class.

Therac-25 Accidents
2010 Radiation Follies
Medical Device Recalls

Chapter 11

Get familiar with Ubuntu, Subversion, and VirtualBox

Learn about scripts.

Spacecraft Accidents
FBI Fiasco 2005
Sentinel

Chapter 11

Exercise: Create test directory [lastName] in SVN repository "playground".

Post by 1:40 PM a brief experience report including the directory name

HW5: 500+ word response to all readings from 29 Aug and 3 Sep
Post by 1:40 PM

https://svn.cs.cofc.edu/repos/CSCI362201302/playground

user/pw - see your work review google doc

NOTE: You are required to use Subversion to store and track your team deliverables.

Magical Number 7
Tire Pressure Monitoring System
Planning for Failure

Chapter 4

HW7: response to all TODAY's readings
Post by 1:40 PM

Chapter 3
Ch 1 - 4 of: Mythical Man Month
Agile Manifesto
Agile Methods

Blog reflections by 1:40 PM

We will assign a project to each team during class.

DELIVERABLE #1:
Team experience report:
summary of chosen project; checkout project from repository and build it; run existing tests and report results; evaluate experience and project so far; present report to class; Submit report by saving document into your SVN Team repository and name it [team-name]_deliverable1.pdf

Note: This report will become Chapter 1 of your final project report.

Dependability and Security Assurance

DELIVERABLE #2:
produce a detailed test plan (see p. 209 text) for your project. As part of this plan, you will identify at least 5 of the eventual 25 test cases that you will develop for this software. Submit [team-name]_deliverable2.pdf.

Note: This report will become Chapter 2 of your final project report.

DELIVERABLE #3:

Preparation: For those teams that have been instructed to re-work their test plans, do so and resubmit with this deliverable.

Task: Design and build an automated testing framework that you will use to implement your test plan per the specifications document.

Report: This is chapter 3 of your project book. Report on your experiences and provide the details produced in the task above. These details should also include an architectural description of your framework, full how-to documentation, a set of at least 5 of the eventual 25 test cases.

Due: by 1:40 PM: [team-name]_deliverable3.pdf; Be ready to demonstrate your framework in class.

Note: As you are building a coherent document with each deliverable as a chapter, you may submit the completed document-to-date with the above-specified name.

DELIVERABLE #4:

Preparation: Make changes as directed.

Task: Complete the design and implementation of your testing framework as specified in Deliverable #3. You are now ready to test your project in earnest. You will create 25 test cases that your framework will automatically use to test your FOSS project.

Report: This is chapter 4 of your project book. Report on your experiences and provide the details produced in the task above. This is your opportunity to get your report organized into a professional-quality document.

Due: by 1:40 PM: [team-name]_deliverable4.pdf; Be ready to demonstrate your framework in class.

Note: As you are building a coherent document with each deliverable as a chapter, you may submit the completed document-to-date with the above-specified name.