|
Date in 2012
|
Topic | Readings due | Assignments due | Team Project Milestones |
|
T 21 Aug
|
Introductions |
Chapter 1 |
||
| R 23 Aug | Overview of Software Engineering | Rugaber: How to Read a Research Paper |
HW1: Ex 1.3, 1.8, 1.9, 1.10 Drop by NOON [last_first]_HW1.pdf |
Get familiar with Ubuntu, Subversion, and VirtualBox |
|
T 28 Aug
|
Ethical Issues in Software Engineering
Socio-technical Systems |
ACM Code of Ethics ACM SE Code of Ethics SE Ethics in a Digital World ACM Licensing Position Chapter 10 |
HW2: 500+ word response to No Silver Bullet, Chimera of Software Quality, and Errant Trades taken together Drop by NOON [last_first]_HW2.pdf HW3: Ex 10.6, 10.10 |
|
|
R 30 Aug
|
Socio-technical Systems Dependability and Security |
Chapter 11 |
HW4: Ex 11.4, 11.7, 11.9 Drop by NOON [last_first]_HW4.pdf |
|
|
T 04 Sep
|
Dependability and Security | Therac-25 Accidents 2010 Radiation Follies Tire Pressure Monitoring System Spacecraft Accidents FBI Fiasco 2005 Sentinel Apple Account Hack |
Exercise: Practice using your Subversion repository
|
Get familiar with Ubuntu, Subversion, and VirtualBox |
| R 06 Sep | Requirements Engineering Dependability and Security Specification |
Chapter 4 Magical Number 7 Chapter 12 |
HW6: Ex 4.5, 4.6, 4.7 Drop by NOON [last_first]_HW6.pdf HW7: Ex 12.5, 12.6, 12.7 |
Subversion:
https://svn.cs.cofc.edu/repos/CSCI3622012 user = cougars' id pw = last 6 digits of cwid |
|
T 11 Sep
|
Software Processes | Chapter 2 The Future of Programming (google) Rapid Development Ch 7 |
HW8: 500+ word essay on where you think programming and software engineering are headed; do you agree with the Future of Programming article - why or why not? Drop by NOON [last_first]_HW8.pdf |
Get familiar with Ubuntu, Subversion, and VirtualBox |
|
R 13 Sep
|
Agile Software Development | Chapter 3 |
HW9: 500+ word response to MMM(1-4) Drop by NOON [last_first]_HW9.pdf |
|
| T 18 Sep | System Modeling | Chapter 5 On Visual Formalisms |
HW10: Create test directory [lastName] in SVN repository "playground". Drop by NOON a brief experience report including the directory name [last_first]_HW10.pdf (place both in svn and google drive) |
NOTE: You are required to use Subversion to store and track your team deliverables. |
|
R 20 Sep
|
Software Testing | Intro to Testing | Form Teams Team Exercise Triangle Test |
|
| T 25 Sep | Software Testing | Chapter 8 Software Analysis |
TERM TEAM PROJECT: Evaluate 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). Bring these candidates to class and be prepared to summarize why you chose each one. We will assign a project to each team during class. |
|
| R 27 Sep | Software Testing
Dependability and Security Assurance |
Chapter 15 |
Project Specifications | |
| T 02 Oct | Software Evolution |
Chapter 9 Legacy Systems |
DELIVERABLE #1: Note: This report will become Chapter 1 of your final project report. |
|
| R 04 Oct | TEST | |||
| T 09 Oct | Software Reuse |
Chapter 16 |
DELIVERABLE #2: Note: This report will become Chapter 2 of your final project report. |
|
| R 11 Oct | Component-Based Software Engineering |
Chapter 17 |
||
| T 16 Oct | Distributed Software Engineering |
Chapter 18 |
||
| R 18 Oct | Service-Oriented Architecture |
Chapter 19 |
||
| T 23 Oct | Aspect-Oriented Software Engineering |
Chapter 21 |
||
| R 25 Oct | Open | |||
| T 30 Oct | Team Presentations - work in progress |
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 NOON: [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. |
||
| R 01 Nov | Project Management |
Chapter 22 |
||
| T 06 Nov | Project Planning |
Chapter 23 |
ELECTION DAY = NO CLASS BUT YES READINGS AND PROJECT | |
| R 08 Nov | Quality Management |
Chapter 24 |
||
| T 13 Nov | Team Presentations - work in progress | 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 NOON: [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. |
||
| R 15 Nov | Configuration Management | Chapter 25 | ||
| T 20 Nov | Process Improvement | Chapter 26 | ||
| R 22 Nov | T H A N K S G I V I N G | |||
| T 27 Nov | Team Project Presentations | Teams 6, 7, 5, 4 | DELIVERABLE #5: |
|
| R 29 Nov | Team Project Presentations | Teams 3, 1, 2 | ||
| T 11 Dec | Noon - 03:00 PM FINAL EXAM | |||