CIS 422/522 (Software Methodology)


Instructor: Lloyd Madden
(Office hours TBA. By appointment, for now)

GTF: John Fiskio-Lasseter
(Office hours Tuesday 10-12, Wednesday 3-5. Drop by otherwise)

Announcements and other New Stuff

(8 March, 2000)The Final will be given out on the last day of class (Friday, 3/10), and will be due on the scheduled final exam time. We will be meeting in Deschutes 100 for Demo Day on the final exam time.

(8 March, 2000)The notes from Glen's guest lectures are available.

(8 March, 2000)For the record, here's the Version 2.0 Concept Document

(2 March, 2000) Three new topics have been added.

(15 February, 2000) A description of the deliverables for the Architecture Design Description has been added to the standards page.

(15 February, 2000) User groups have been created for each team. As it turned out, we're not the first 422 class to have this idea: we just recycled the previous group names. The group name for each team is 422gn, where n is your team number (sorry folks -- boring names, after all). These will also work as mail aliases, and I have modifed the links on the Projects page accordingly.


Class Meeting Schedule

Mon. 01/24/00:Guest Presenter: J.D. Alley (Topic:Teamwork, Leadership, Planning)
Wed. 01/26/00:Guest Presenter: Stuart Faulk (Topic: Requirements Engineering)
Fri. 01/28/00: Regular class
Mon. 01/31/00: Requirements Eng. (continued)
Mon. 01/31/00: Requirements Eng. (continued)
Fri. 02/04/00: Project Status
Mon. 02/07/00: Architectural Design
Mon. 02/21/00: Project Planning/Estimation
Wed., 2/23: User Interface Design
Fri., 2/25: Static Analysis/Evaluation (emphasis on Inspections)
Mon., 2/28: Testing
Wed., 3/1: Midterm review
Fri., 3/3: Design Patterns (Glen)
Mon., 3/6: Design Patterns continued (Glen)
Wed., 3/8: Software Engineers: Some Quality Attributes of an Effective SE
Fri., 3/10: Last day of class; open season; instructor eval.; final exam clarification/pre-view

Suggested Readings

GENERAL
As of ...
Rapid DevelopmentSW Engineering
Fri., 1/21Chapters 1 - 4, 7, 25Chapters 1, 2, 31.4
Mon., 1/2412, 13
Wed., 1/2610, 144, 5
SPECIALIZED
Project Managers (PM)5, 8, 93
Requirements Engineers (RE) 6 - 8, 17
System Architects (SA) 12 - 14, 20
Quality Assurance (QA)22 - 24, 30

At this point (03-01-00), the breakdown of readings by specialization is irrelevant. You should all have read all of this by now.


Selected Topics

Fundamentals of Software Testing
Some notes on Static Analysis
Notes on Designing User Interfaces (ASCII text only).
What exactly do we mean by "Software Quality Assurance"? Some definitions.
Some insights on the art of Software Architecture

Notes from Glen's Guest Lectures

Lecture (Ugly) HTML format MS Word format
Project Lifecycles (01-14-00)
Architecture (01-28-00)
Cherry-Oh Architecture (02-14-00)
Creational Design Patterns (02-23-00)
Behavioral Design Patterns (02-25-00)


Team Projects

As this is a course in software engineering, the team projects are the real meat-and-potatoes of this course. There is now a separate page for the Project teams, which will likely undergo constant revision throughout the term:

http://www.cs.uoregon.edu/classes/cis422/project-main.html


Other Assignments

Assignment 1.


lloyd.madden@dynamix.com
glenw@uswest.net
johnfl@cs.uoregon.edu