Syllabus

Since I am teaching this course for the first time, I won't really know what the syllabus is until after the course is over. I understand the difficulties that causes for you, and will try to keep this page up to date - filling in what we have covered so far, and, when possible, where I think we will be going next. I may rely on people from the class to provide notes from time to time.

Topics
Metatopics

January 24. Possible projects. (1) UMass parking system softwar (fake, technically interesting - web and parallel processing ideas - little prior familiarity since most students use T). (2) KICS. (real, technically straightforward, C# not Java, no web or time dependent constraints).
Engineering as a process. Decisions and rationales.
Presentations as part of CS capstone experience. Two minute introductions.
January 26.
- SE as modeling (UML), document transformation, process.
- Models
  Waterfall
  - Requirements elicitation (scenarios and use cases)
  - Analysis
  - System design
  - Object design
  - Implementation
  - Testing
  eXtreme Programming (XP)
  Lots more iteration (water doesn't run uphill) but not just hack away!
- Tools that support processes: transparency (wiki, web), IDE (Eclipse, JBuilder, Visual Studio), code management (CVS, RCS, Clearcase), rationale maintenance, bug tracking.
- KICS
- January 31. Requirements elicitation. Actors, scenarios and use cases. Functional and nonfunctional requirements. Examples from WISER and KICS. (Material from Bruegge, Chapter 4.)
- February 2. KICS short stories. UI design, with rationale. From short stories to use cases. Functional and nonfunctional requirements.
- February 7. Madhu discusses UML, sequence diagrams and class diagrams.
- February 9. Review use cases submitted by students:
  - AddItemsToPortfolio
  - CreateNewStudent
  - SavePortfolio
  - SelectStudent
  From use cases to sequence and class diagrams. UML.
- February 14. UML Sequence and Class diagrams. Application to KICS.
- February 15 (Wednesday), 3:00 PM. ACM Student Chapter talk on SCRUM. Attend if you can fit it into your schedule.
  Presentation skills are an important part of this course, and this talk provides two opportunities to learn about it. First, you can think about what makes Schwaber's presentation work well (and what doesn't). Second, you can learn about the content, and then prepare a presentation for the rest of the class describing it. That will count as part of your presentation work for our course. I may try to have a group of you put together a joint presentation - that may depend on how many of you attend.
- February 16.
- February 21. Pat Kinsella (KICS client) visits class. We need to be ready with questions for her.
- February 23. Feedback from Pat Kinsella visit. Discussion of one step build, KICS security.
- February 28. Team progress reports for first sprint.
- March 2. Team meetings in class, last chance for me to resolve design and API disputes for the first sprint.
- March 7. First sprint complete!
- March 9. Lessons from the first sprint, second sprint fuctionality, team reorganization.
- March 11-19. Spring break.
- March 21.
- March 23.
- March 28. Student presentations ...
- March 30. Third sprint specifications
- April 4. Second sprint complete!
- April 6. Pass/fail, withdraw deadline.
- April 11.
- April 13. Team meetings in class
- April 18.
- April 20. Final sprint specifications.
- April 25. Third sprint complete!
- April 27.
- May 2.
- May 4. Final sprint complete!
- May 9. Last class. Deliver KICS?
- May 11. Department party for alumni/ae. Demonstrate KICS. Free food.