StartUp Weekend

Y Combinator News

TechNews

Internet of Things

David Schirduan

Project Specifications

H/FOSS

Form Teams - submit contact info
Team Exercise
Testing Triangle Program

No Silver Bullet
Kode Vicious
Software Analytics

Create your blog and make linked entry on class wiki

HW1: Ex 1.3, 1.8, 1.9, 1.10
Post answers by 8:30 AM

Unit Testing Checklist

Starting with Git

Create Team Wiki in the public domain, protected, using wikispaces.com. Use the wiki to document your team and your project, including a timeline.

Get familiar with Ubuntu, Subversion, GitHub, and VirtualBox

Learn about scripts.

Socio-technical Systems

Chapter 10

HW3: Ex 10.6, 10.10 with reference to SE Code of Ethics
Post answers by 8:30 AM

Get familiar with Ubuntu, Subversion, GitHub, and VirtualBox

Learn about scripts.

Teams: Write a script myList.[script extension] for Unix that lists the top-level directory contents of its containing directory in an html file displayed in a browser. Post code to your wiki along with example outputs. Demo in class today.

Therac-25 Accidents
2010 Radiation Follies
HealthCare.gov
HealthCare.gov #2

Chapter 11

10 Serious Bugs

Get familiar with Ubuntu, Subversion, GitHub, and VirtualBox

Learn about scripts.

Spacecraft Accidents
FBI Fiasco 2005
FBI Fiasco 2010
FBI Success 2012

Chapter 11

Exercise: Create test directory [lastName] in SVN repository "playground". Post by 8:30 AM a brief experience report including the directory name.

HW5: 500+ word response to all readings from 28 Aug and 2 Sep - find common concerns in the articles and reflect upon them. Post by 8:30 AM

TERM TEAM PROJECT:

Project Specifications

Task: Evaluate H/FOSS projects and select 1st, 2nd, 3rd candidates. See Deliverable #1 for criteria. Be sure that the code base is designed to compile and run on Linux (no Windows-only projects).

Report: Document your work on the team wiki. Bring these candidates to class and be prepared to summarize why you chose each one.

Due: by 8:30 AM

Note: We will assign a project to each team during class.

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

Subversion: TBA
user/pw - see your individual work review google doc

Magical Number 7
Tire Pressure Monitoring System
Planning for Failure
Test-Driven Development

Chapter 4

HW7: response to all today's readings - find common concerns in the articles and reflect upon them. Post by 8:30 AM

Chapter 2

The Future of Programming
Rapid Development Ch 7

DELIVERABLE #1:
Task: Checkout project from repository and build it. Run existing tests and collect results. Evaluate experience and project so far.

Report: This is Chapter 1 of your project book. Report on your chosen project and your experiences executing the task above. Document progress on wiki.

Due: by 8:30 AM: [team-name]_deliverable1.PDF in team's SVN repository

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

Review StartUp Weekend

System Modeling

Blog reflections on StartUp Weekend by 8:30 AM

Chapter 3

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

SVN Details: (CougarByte is replaced with your CamelCased TeamName)

https://svn.cs.cofc.edu/repos/CSCI3622014/CougarByte

un: lastname firstinital (all lower)

pw: lastname followed by 3-digit number found in your google evaluation doc

HW10: Ex 8.7, 8.10
Post answers by 8:30 AM

Blog reflections on readings by 8:30 AM

DELIVERABLE #2:
Task: Produce a detailed test plan (see p. 209 text) for your project. As part of this plan, you will specify at least 5 of the eventual 25 test cases that you will develop for this software.

Report: This is Chapter 2 of your project book. Report on your experiences and provide the details produced in the task above. These details should also include detailed specifications of your test plan and at least 5 of the eventual 25 test cases. Document progress on wiki.

Due: by 8:30 AM: [team-name]_deliverable2..PDF in team's SVN repository. Be ready to present your testplan 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.

Dependability and Security Assurance

Blog reflections on readings by 8:30 AM

HW12: Ex 17.9
Post answers by 8:30 AM

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 Project 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. Document progress on wiki.

Due: by 8:30 AM: [team-name]_deliverable3.PDF in team's SVN repository; 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.

Distributed Software Engineering

DELIVERABLE #4:

Preparation: Make changes as directed.

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. Document progress on wiki.

Due: by 8:30 AM: [team-name]_deliverable4.PDF in team's SVN repository; 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.

Configuration Management

Deliverable #5:

Task: Design and inject 5 faults into your code that will cause at least 5 tests to fail, but not all tests to fail. Exercise your framework and analze the results.

Report: This is Chapter 5 You will provide a detailed description of exactly what you changed in the code so that I can duplicate the faults and get the same results you do. Identify the tests you are planning to have fail. Report on your experiences and lessons learned. Document progress on wiki.

Due: by 8:30 AM: [team-name]_deliverable5.PDF in team's SVN repository; 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.