wk 1
Tues
3/30

Project:
Project expectations and deliverables;
team advice.

wk 1
Thurs
4/1

• Join/create a project team either before/in/right after class.

Review:

• Lifecycle Planning, Chapter 7 of Rapid Development, by Steve McConnell, Microsoft Press, 1996, p. 133-161.
  (Check out the guidelines for writing and submitting reviews.)

• Reverse Engineering and Design Recovery: A Taxonomy, Elliot J. Chikofsky, James H. Cross II, IEEE Software, Vol. 7, No. 1, Jan. 1990, pp. 13-17

wk 2
Tues
4/6

• Choose a project for your team
• Submit Project Selection document

Review:

• Software Risk Management: Principles and Practices, Barry W. Boehm, IEEE Software, Vol. 8, No. 1, Jan. 1991, pp. 32-41.

• Putting Risk Management into Practice, Ray C. Williams, Julie A. Walker, Audrey J. Dorofee, IEEE Software, Vol. 14, No. 3, May-June 1997, pp. 75-82.

wk 2
Thurs
4/8

Project:
Scenario expectations

Lecture Slides

• Submit Software Architecture document
• In-class Project Outline presentation (5 minutes each)

• Chapter 3 (Requirements Elicitation and Analysis) (sections 3.1, 3.2 only),
  Requirements Engineering: Processes and Techniques, Gerald Kotonya, Ian Sommerville, John Wiley & Sons, 1998, pp. 53-73.

• Chapter 1 (Introduction) and Chapter 4 (Requirements Validation) (section 4.1 only),
  Requirements Engineering: Processes and Techniques, Gerald Kotonya, Ian Sommerville, John Wiley & Sons, 1998, pp. 3-23, 87-100.

wk 3
Tues
4/13

Homework:
Hand out Homework #1

Lecture Slides

• Submit Scenarios document

Review:

• Prototyping for Tiny Fingers, Mark Rettig, Communications of the ACM, Vol. 37, No. 4, April, 1994, pp. 21-27.

wk 3
Thurs
4/15

• Create a DForge site for your project
• Submit Configuration Control document

Review:

• Budget Tracking, from Object-Oriented Project Management with UML, Murray Cantor, Wiley 1998 pp. 304-311

wk 4
Tues
4/20

• Submit Requirements document

Homework: Turn in Homework #1 at beginning of class

• What is Software Architecture?, Chapter 1 of Evaluating Software Architectures: Methods and Case Studies, by Paul Clements, Rick Kazman, Mark Klein, Addison-Wesley, 2002, pages 1-16.

• Evaluating a Software Architecture, Chapter 2 of Evaluating Software Architectures: Methods and Case Studies, by Paul Clements, Rick Kazman, Mark Klein, Addison-Wesley, 2002, pages 19-42

wk 4
Thurs
4/22

• Submit Time estimate & risk analysis document

Review:

• Fundamentals of Software Engineering, Sections 2.1, 2.2 (pp 17-36, Software: Its Nature and Qualities) and Chapter 3 through Section 3.5 (pp. 43-53 Software Engineering Principles), Carlo Ghezzi, Mehdi Jazayeri, Dino Mandrioli, Prentice-Hall, 1991.

wk 5
Tues
4/27

Presentations:
Project overview
Black Diamond
WINAG
Ricochet
Pardon our French(not yet)
L8 Buffet
Dyve

LAB (TA):(Mon/Tues/Wed)
Exam #1 review session

• In-class Project Overview presentation (~10 minutes each)

Read:

• Development Process, Chapter 2 and Class Diagrams, Chapter 3 of UML Distilled, Martin Fowler, Addison Wesley 2004

wk 5
Thurs
4/29

Guest Lecture:
Raymie Stata on the Architecture of Bloomba

Exam: Hand out home Exam #1

• User manual

Review:

• On the Criteria to be Used in Decomposing Systems into Modules, David Parnas, Communications of the ACM, December 1972, pp. 1053-1058

wk 6
Tues
5/4

• Chapters 4,6,7, and 8 (just 22 pages!) of UML Distilled, Martin Fowler, Addison Wesley 2004

wk 6
Thurs
5/6

Project:
ATP expectations

• Design document

Read:

• Software Inspections: An Effective Verification Process. A. Frank Ackerman, Lynne S. Buchwald, and Frank H. Lewski, IEEE Software, May 1989, pp. 31-36

wk 7
Tues
5/11

Project:
Software Inspections expectation

• A Fault Model to Guide Software Testing, Chapter 1 of How to Break Software: A Practical Guide to Testing, James A. Whittaker, Addison-Wesley, 2003, pp. 3-16.
• Testing from the User Interface: Inputs and Outputs, Chapter 2 of How to Break Software: A Practical Guide to Testing, James A. Whittaker, Addison-Wesley, 2003, pp. 19-55

wk 7
Thurs
5/13

• Acceptance test plan

Read:

• "The Back of the Envelope" and "The Envelope is Back", Programming Pearls, Column 7, Jon Bentley

wk 8
Tues
5/18

• Software inspections will be run this week

Review:

• Software Aging, D.L. Parnas, Proc. 16th International Conference on Software Engineering, Sorrento, Italy, May 16 - 21 1994, pp. 279-287.

wk 8
Thurs
5/20

• Rules and Tools for Software Evolution Planning and Management, M. M. Lehman, Proc. FEAST 2000 Workshop, Imperial College, London, July 10-12, 2000

wk 9
Tues
5/25

Exam:
Hand out EXAM #2 (due 6/3)

• AOP Interview

wk 9
Thurs
5/27

• The New Methodology, Martin Fowler, Web site, http://www.martinfowler.com/articles/newMethodology.html (You may skim "The Methodologies" section.)

• All I Really Need to Know About Pair Programming I Learned in Kindergarten. Laurie Williams and Robert Kessler, Communications of the ACM, Vol. 43, No. 5, May 2000, pp. 108-114

wk10
Tues
6/1

Lecture slides

WINAG slides

Black Diamond slides

Pardon Our French slides

• In-class Final Project presentations (~20 minutes each)
• Acceptance Test Performance this week

wk10
Thurs
6/3

Ricochet slides

L8 Buffet slides

DYVE 2 slides

• In-class Final Project presentations (~20 minutes each)
• Acceptance Test Performance this week
• Submit Final project notebook

Exam: Turn in take home Exam #2 at beginning of class

• No Silver Bullet: Essence and Accidents of Software Engineering, Frederick Brooks, IEEE Computer, April 1987, pages 10-19