Week 

Monday 

Wednesday 

Week 1

09/27/2004 
Introduction -- the software process, Software Capability Maturity Model

Reading:
The Software Engineering Institute at Carnegie-Mellon Univ. Read this intro
More than you care to know about the Capability Maturity Model (try skimming chap. 4 of the Continuous version of CMMI-SW 1.1)
Standish Group's top 6 reasons for software project failure

Introduction notes (in RTF, so you may have to download them to view them)

Project: form and organize teams of 3-4 by Wednesday, pick a team leader and choose a topic (due next Wednesday) 
Turn in your "type" via Blackboard -- take a brief Briggs-Meyers test and share it with your teammates

09/29/2004 
More on the software process and Project management
Programming: coding standards, style, metrics, documentation
Customer Requirements, use cases
Project management notes (in RTF, so you may have to download them to view them)
Customer requirements notes (in RTF)

Readings:
13 arguments against user requirements analysis and responses
Alan Holub's simple case study (Read up to "Submit a mockup to a real user")

Project
1. Suggestions regarding topics
2. Grading guidelines
3. Randy Pausch's advice on teamwork in a class
4. Software Requirements Specification assignment (due October 13, 4pm, via digital drop box)
Note that individual logs will be due at the same time

Week 2

10/04/2004 
Testing 

Reading:
Paper on designing effective test cases
Adapted version of IEEE Standard 829 (Applied Computer Technology) (IEEE standards homepage requires subscription)
Eric Raymond's "The Cathedral and the Bazaar" The whole article is enjoyable and informative, but at least read the first 5 sections, then "Necessary Preconditions", "Management and the Maginot Line", and the Epilog

10/06/2004 
Software Architecture I, software layers
2nd half of class: project meeting period

End of Add/Drop period is Oct. 7

Week 3

10/11/2004 
Software Architecture II, Model-View-Controller architectural pattern
Reading:
Steve Burbeck's original article on the Model-View-Controller architecture

10/13/2004 
Object-oriented analysis, UML class diagrams, class diagram lab
Reading:
James Martin on UML class diagrams in C++ Report
Holub's example (read the rest)
Project:
SRS due via drop box, 4pm, sharp -- make sure to send a copy to your reviewers

Week 4

10/18/2004 
More on class diagrams, collaboration diagrams, sequence diagrams
Reading:
James Martin on UML collaboration diagrams in C++ Report
James Martin on UML sequence diagrams in C++ Report

10/20/2004 
1st half of class: midterm review
2nd half of class for group meeting
Project:
Review of SRS due via drop box-- make sure to send a copy of the review to the team you are reviewing

Week 5

10/25/2004  Midterm

10/27/2004 
Object-behavior model, UML state transition diagrams
Reading:
James Martin on UML finite state machine diagrams in C++ Report
Project:
Test plan due at 4pm sharp via digital drop box

Week 6

11/01/2004 
Prototyping
Reading:
Sommerville, ch. 8 slides
Data flow diagrams
2nd half -- review
Reading: Data flow diagram article

11/03/2004 
Project:
Review of test plan due by Friday, 4pm, via drop box-- make sure to send a copy of the review to the team you are reviewing

Last day to withdraw without approval is Thursday Nov. 4

Week 7

11/08/2004 
Risk management

Reading: Introduction (for students, from Arizona State U.)

User interface design/user guide

Reading:
Deborah Mayhew on usability (if you have trouble opening this one, try IE 6.0)
Alternate article on usability
2nd half -- project group meeting

11/10/2004 
Data design, entity-relationship model
Reading:
The sections explaining the Entity-relationship model and the relational model and normal forms
http://www.geekgirls.com/menu_databases.htm keeps things simple and practical while still hitting the important issues -- try the tutorials in the righthand column. This is just for the relational model,
but it helps show why normalization is helpful.

Week 8

11/15/2004 
Inheritance of interface (continued)
UML example
Reading: Example from Martin and Newkirk
Project:
Software Design Specification due at 4pm sharp via digital drop box

11/17/2004 
Introduction to design patterns
2nd half -- project group meeting

Week 9

11/22/2004 
Law, ethics
Project:
Review of SDS due via drop box-- make sure to send a copy of the review to the team you are reviewing

11/24/2004 
Maintenance
Reviewing/revising the software process

Week 10

11/29/2004 
Presentations

12/01/2004 
Presentations
Project:
Code due, 4pm, via drop box

Week 11

12/06/2004 
Final exam, 4 PM-5:50 PM

This webpage's layout is originally from Bill Parkinson, who used to teach in the evening program at St. Joseph's University. Much of the content is lifted from Steve Cooper's version of this course -- in particular, the project documents have been adapted from his assignments, though parts are adapted from elsewhere.