CSE584
is the University of Washington Department
of Computer Science & Engineering Professional
Masters Program course in software engineering.
This is a challenging class to teach, since I've had less experience in
developing software in the field than any of you. What I'll
focus on is to try to convey a collection of research results, with two
objectives. First, it is intended to provide an insight into some of
the hot topics being addressed by the software engineering research
community, which may over time come to change (to some degree) the way you
develop software. Second, I hope that one or two of the ideas that you
see can quickly and concretely improve some aspect of your own work in
software development. The introductory lecture will be more precise
about these objectives and about my own prejudices about software
engineering and software engineering research.
- Lectures
(archive)
- Tuesdays 6:30-9:30PM (we'll generally take a brief break sometime
around 8PM)
- EE1
003 on UW campus
- This is a distance learning course, with students at three sites:
UW, Microsoft's Redwest, and a site at Intel Dupont
- This makes interaction a bit more difficult; especially at the
remote sites, you should be aggressive about interrupting and
asking questions
- Mailing
list (archive)
- To subscribe, send email to majordomo@cs.washington.edu
with the body: subscribe cse584
- See the bullet under assigned work for the importance of
the mailing list to the course
- Reading
assignments
- There is a required course pack of papers (copy
of message from Dave Rispoli about buying the course packs)
- It is important that each student gets a copy by the second
lecture, since there will be assigned readings starting that
week.
- I will certainly add a few assigned papers here and there
during the quarter.
- There are two recommended (but not required) books
- F.P. Brooks, Jr. The Mythical Man-Month, Anniversary
Edition. Addison-Wesley, 1995.
- Everyone should read this book. Really. Not
only does the original book (chapters 1-15) give a set of
insights that still often provide genuine value, but the new
chapters put the work in a modern context.
- M. Jackson. Software Requirements &
Specification: A Lexicon of Practice, Principles and Prejudices.
Addison-Wesley, 1995.
- Assigned
work
- There will be four assignments, each worth 23% of the course
grade. There will be no midterm nor final examination.
Each assignment will be structured differently. For
example, one will be in the form of a usual homework assignment,
with problems to solve and questions to answer, another one will be
a paper that distills a set of research papers, another one will
require the use of a research prototype tool of some sort, and the
other is yet to be defined.
- Assignment
1: Assigned 9 January 2001; Due 30 January 2001 at
6PM.
- Assignment
2: Assigned 30 January 2001; Due 13 February 2001
at 6PM. [Extended two days; if you turn it
in by the original due date, you get one extra "free late
day."]
- Assignment
3: Assigned 13 February 2001; Due 27 February 2001
at 6PM.
- Assignment
4: Assignment 27 February 2001; Due 13 March 2001
at 6PM.
- All assignments must be turned in electronically, ideally in the
form of a web page; even if you do write parts of your assignments
by hand, I'll need you to scan them in to submit them.
- An assignment is considered to be submitted based on the timestamp
of the email sending the assignment to the TA. (His email is taoxie@cs.washington.edu.) You have
two "free" late days during the quarter. That is,
you can turn in two assignments one day late, or one assignment two
days late, without penalty. Every late day beyond the second
will cost 10% of the grade on that assignment per day.
- The remaining 8% of the grade will be based on your interaction in
class and, even more so, on the class mailing list. It
is the responsibility of the class to generate discussions on the
papers we read, on the lecture materials, and on other software
engineering topics of interest to you. The TA and I will be
part of the discussions, but we are not generally responsible for
generating discussions topics.
|