Y Combinator News

TechNews

Internet of Things

David Schirduan

H/FOSS

Joye's Blog

Sparc Hackathon

Read this:

Team Term Project Specifications

Why SE Blogging?

Chapter 1

No Silver Bullet

Kode Vicious

Google Code Repo

HW0: Create your blog and blog to introduce yourself. Create a GitHub account.

Blog SubTitle = "HW0: Introduction"

Make linked entry on class wiki to your blog.

HW1: Ex 1.3, 1.8, 1.9, 1.10

Blog SubTitle = "HW1: Chapter 1"

Learn Git

Git videos (short):
What is VC,
What is Git,
Start Git,
Win with Git

Unit Testing Checklist

Form Teams - submit contact info including GitHub account names - via email to bowringj@cofc.edu: names, emails, github account names, etc.; Team names?

Team Exercise
Testing Triangle Program : Test Case Definition

Get familiar with Ubuntu, Subversion, GitHub, Slack, and VirtualBox

Learn about scripts, beginner bash, advanced bash.

Dependable Systems

ACM Code of Ethics

ACM SE Code of Ethics

SE Ethics in a Digital World

Spirit of Engineering

Chapter 10

HW2: 500+ word response to No Silver Bullet, Kode Vicious, and Google Code Repo taken together - find common concerns in the articles and reflect upon them.

Blog SubTitle = "HW2: Responses"

HW3: Ex 10.6, 10.10 with reference to SE Code of Ethics

Blog SubTitle = "HW3: Chapter 10"

Charleston Digital Corridor

Speaker:

Alex Castelli, CODEcamp Coordinator
Charleston Digital Corridor slides

Customize Team repository at GitHub.com.

Create Team Wiki in your team GitHub repository. Use the wiki to document your team and your project, including a timeline. Place a link to your team's github repository on the class wiki.

Learn about scripts, beginner bash, advanced bash.

Therac-25 Accidents

2010 Radiation Follies

FBI Auto Warning

Chapter 11

Chapter 12

HW4: Ex 11.4, 11.7, 11.9, 12.5

Blog SubTitle = "HW4: Chapters 11 & 12"

10 Serious Bugs

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.

Note: Each team will make their choice bythe end of this class.

NOTE: You are required to use GitHub team repository to store and track your team deliverables and for your team wiki.

Spacecraft Accidents

FBI Fiasco 2005
FBI Fiasco 2010
FBI Success 2012 FBI NotDone 2014

Chapter 13

Chapter 14

HW5: 500+ word response to all readings from 1 Sep and 6 Sep including Chapters 13 and 14 - find common concerns in the articles and reflect upon them.

Blog SubTitle = "HW5: Reflections"

Bugs

Software Failures

Keep Out

Team Exercise:

All team projects will be built using an open source unix operating system such as Ubuntu. Your first project is to collaborate as a team using the github repository to 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 a link to your code in your team wiki along with example outputs. Demo in class today - be sure you have a laptop and required cables.

Magical Number 7

Tire Pressure Monitoring System

Spy Car Act of 2015

Planning for Failure

Test-Driven Development

Chapter 4

HW6: Ex 4.5, 4.6, 4.7

Blog SubTitle = "HW6: Chapter 4"

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

Blog SubTitle = "HW7: Reflections"

Meter Reader Hacks

Hacked Home

Software Processes

Team Presentations - work in progress

Chapter 2

Rapid Development Ch 7

The Future of Programming

HW8: Ex 2.1

Blog SubTitle = "HW8: Chapter 2"

HW9: 500+ word essay on where you think programming and software engineering are headed; do you agree with the Future of Programming - why or why not?

Blog SubTitle = "HW9: Reflections"

Hackathons

Corporate Hackathons

DELIVERABLE #1:
Task: Checkout or clone project from its repository and build it - if you do not know how to compile the code, ask! Run existing tests and collect results. Evaluate experience and project so far.

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

Due: [team-name]_deliverable1.PDF in team's GitHub repository

Chapter 5

HW10: Ex 5.3, 5.5, 5.7, 5.8

Blog SubTitle = "HW10: Chapter 5"

Architectural Design

Chapter 6

HW11: Ex 6.4

Blog SubTitle = "HW11: Chapter 6"

Chapter 3
Ch 1 - 4 of: Mythical Man Month

Agile Manifesto
Agile Methods

HW12: 500+ word response to MMM(1-4)

Blog SubTitle = "HW12: Mythical Man Month"

Software Testing

Team Presentations - work in progress

Chapter 8

Intro to Testing

HW13: Ex 8.7, 8.10

Blog SubTitle = "HW13: Chapter 8"

HW14: Blog reflections on readings.

Blog SubTitle = "HW14: Testing Reflections"

Software Analysis

Mutation Testing

DELIVERABLE #2:

Task: Produce a detailed test plan (see p. 217 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 Final Report. 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: [team-name]_deliverable2.PDF in team's GitHub repository. Be ready to present your testplan in class.

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

Software Reuse

HW15: Ex 15.10

Blog SubTitle = "HW15: Chapter 15"

Making Reuse Work

HW16: Ex 9.8, 9.10
Blog SubTitle = "HW16: Chapter 9"

HW17: Ex 16.9

Blog SubTitle = "HW17: Chapter 16"

HW18: Ex 18.4
Blog SubTitle = "HW18: Chapter 18"

HW19: Blog reflections on team progress.

Blog SubTitle ="HW19: Team Progress I"

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 Final Report. 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: [team-name]_deliverable3.PDF in team's GitHub repository; Be ready to demonstrate your framework in class.

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

HW20: Ex 19.3
Blog SubTitle = "HW20: Chapter 19"

Distributed Software Engineering

HW23: CANCELLED

HW24: Ex 22.6
Blog SubTitle = "HW24: Chapter 22"

HW25: Blog reflections on team progress.

Blog SubTitle = "HW25:Team Progress II"

DELIVERABLE #4:

Preparation: Make changes as directed.

Report: This is Chapter 4 of your Final Report. 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 deliverable. Document progress on wiki.

Due: [team-name]_deliverable4.PDF in team's GitHub repository; Be ready to demonstrate your framework in class.

Note: As you are incrementally building a coherent Final Report 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 the code you are testing that will cause at least 5 tests to fail, but hopefully not all tests to fail. Exercise your framework and analyze the results.

Report: This is Chapter 5 of your Final Report. 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: [team-name]_deliverable5.PDF in team's GitHub repository; Be ready to demonstrate your framework in class.

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