Department of Computer Science
School of Engineering
and Applied Science
Washington University in St. Louis
times and places
Message of the day
Final exam from last year is here
Documents are marked up and returned to you here.
Here are the sections I will evaluate in your SRRD
Resources for Literate Programming:
- 13 Nov 2006 -- use case demos
- 16/17 Nov 2006 -- team meetings, prepare for code review
- 20 Nov 2006 -- team code review, lecture on literate programming
turn in SRRD for feedback on this day, to be returned to you after Thanksgivng
- 27 Nov 2006 -- lecture on unit testing, testing frameworks, team status reports
- 4 Dec 2006 -- Team reports, demos
- 11 Dec 2006 -- Final class demos
Software you might find useful:
Useful Links (with thanks to Oren Melzer):
- 30 October 2006
- First demo with stubs as needed
- 13 November 2006
- Second demo with use cases
- 4 December 2006
- Third demo with testing
- 11 December 2006
- Final project demonstration
- 18 December 2006
- All work products (documentation, everything) due
CSE436 is a course on software engineering. While it is primarily a workshop,
students are exposed to fundamental software engineering approaches, tools, and disciplines
This is a capstone course, meaning that you will draw from all your experiences
in other courses to complete the work in this course. As such, this course involves
a substantial amount of
It is likely that coming into this class, you are strong at some of the aspects listed
above and weak at others. The goal is for you to help others where you have strength,
and to strengthen yourself in areas where you are weak, by interaction with the instructor
and the other students.
- Design skills, to arrive at a clean, effective design for your project.
- Coding skills, to implement your project in the best way possible.
- Programming language skills, as all projects will involve Java, C++, and JNI to
connect the pieces.
- Collaboration skills, as the course involves real-world projects
performed in teams, scaled to fit in the timeframe of the semester.
- Debugging skills, to find and fix bugs.
- Testing skills, to search for the presence of bugs.
- Theory skills, to prove the absence of bugs.
- Writing skills, to develop clean, effective prose describing requirements and
- Presentation skills, to communicate the important aspects of your project at
different levels (management, customer, team)
See the CSE 436
Course Description and the CSE 436
Lecture Highlights for more information on what this course is about.
These web pages are used extensively throughout CSE 436. Most information
is accessible through the menu bar at the left. Read Navigating
the CSE 436 Web Pages to find out what is available. The CSE 436 Home Page
(this page) contains the following administrative information.
Times and Places:
See the Help
Page for times when help is available.
Course Policies and Announcements:
- Reference Books
These web pages are based on, adapted from, and otherwise
borrowed with permission from
Professor Ken Goldman,
who is the designer of this version of CS 101.
However, any mistakes on these pages are the fault of the undersigned.
Last modified 09:08:17 CST 15 December 2005
by Ron K. Cytron