CS680 Advanced Software Engineering (Fall 2007)

S-2-066, TTh 7pm-8:15pm

Instructor: Jun Suzuki

Introduction

This is the home page for CS680, a part of the graduate capstone sequence in software engineering. CS680 covers a series of object-oriented design principles and strategies.

Course Topics

Textbooks

  1. Grady Booch et al., Object-Oriented Analysis and Design with Applications (3rd Edition), Addison Wesley, ISBN-10: 020189551X, ISBN-13: 978-0201895513.
  2. Elizabeth Freeman et al., Head Start Design Patterns, O'Reilly, ISBN-10: 0596007124, ISBN-13: 978-0596007126.

Course Schedule and Homework Dues

Stay tuned on the schedule page.

Paper Readings

  1. I. Sommerville, Software Engineering, 7th Edition, Chapter 1 (Introduction), Addison Wesley, 2004.
  2. J. Spolsky, "The Joel Test: 12 Steps to Better Code," August 2000. (Or, J. Spolsky, "The Joel Test: 12 Steps to Better Code," In Joel on Software, Chapter 3, Apress, 2004.)
  3. J. Reeves, "What Is Software Design?," In C++ Journal, 1992.
  4. J. Spolsky, "Painless Functional Specifications - Part 1: Why Bother?," October 2000.
  5. J. Spolsky, "Painless Functional Specifications - Part 2: What's a Spec?," October 2000.
  6. J. Spolsky, "Painless Functional Specifications - Part 3: But... How?," October 2000.
  7. J. Spolsky, "Painless Functional Specifications - Part 4: Tips October 2000.
  8. B. Boehm, "Safe and Simple Software Cost Analysis," IEEE Software, September/October 2000.
  9. T. Love, "Object Lessons from 1628" Object Lessons: Lessons Learned in Object-Oriented Development Projects, Chapter 1, Cambridge University Press, 1993.
  10. T. Love, "Assessing Our Craft" Object Lessons: Lessons Learned in Object-Oriented Development Projects, Chapter 2, Cambridge University Press, 1993.
  11. J. Spolsky, "Daily Builds Are Your Friend," January 2001. (Or, J. Spolsky, "Daily Builds Are Your Friend," In Joel on Software, Chapter 10, Apress, 2004.)
  12. S. McConnell, "Daily Build and Smoke Test," In IEEE Software, Vol. 13, No. 4, July 1996.
  13. J. Spolsky, "Painless Bug Tracking," November 2000.
  14. J. Spolsky, "Painless Software Schedules," March 2000. (Or, J. Spolsky, "Painless Software Schedules," In Joel on Software, Chapter 9, Apress, 2004.)
  15. J. Spolsky, Five Worlds," May 2002.
  16. F. Brooks, "No Silver Bullet: Essence and Accidents of Software Engineering," In Computer, Vol. 20, No. 4, April 1987.
  17. B. Cox, "No Silver Bullet Revisted," In American Programmer Journal, November 1995.
  18. B. Mayer, "Software Quality," In Object-Oriented Software Construction, 2nd Edition, Chapter 1, Prentice Hall, 1997.
  19. P. Stevens and R. Pooley, "Software Engineering with Components," In Using UML, 2nd Edition, Chapter 1, Addison Wesley, 2006.
  20. G. Booch, "UML in Action," In Communications of ACM, Vol 42 No 10, October 1999.
  21. G. Cernosek and E. Naiburg, "The Value of Modeling," white paper, IBM Rational, June 2004.
  22. P. Kruchten, "The 4+1 View Model of Architecture," In IEEE Software, Vol. 12, No. 6, November 1995. (An alternative copy)
  23. M. Kontio, "Architectural manifesto: Designing software architectures, Part 5," IBM DeveloperWorks, Feb. 2005.
  24. Alex E. Bell, Ryan W. Schmidt, "UMLoquent Expression of AWACS Software Design," In Communications of ACM, Vol 42 No 10, October 1999.

Projects

Office Hours

S-3-168
T Th 5:30pm-7pm

Grading

The grades for CS680 will be based on homework (40%), project deliverables (50%) and quizzes (10%).

Accommodations

Section 504 of the Americans with Disabilities Act of 1990 offers guidelines for curriculum modifications and adaptations for students with documented disabilities. If applicable, students may obtain adaptation recommendations from the Ross Center for Disability Services, M-1-401, (617-287-7430). The student must present these recommendations and discuss them with each professor within a reasonable period, preferably by the end of Drop/Add period.

Student Conduct

Students are required to adhere to the University Policy on Academic Standards and Cheating, to the University Statement on Plagiarism and the Documentation of Written Work, and to the Code of Student Conduct as delineated in the catalog of Undergraduate Programs, pp. 44-45, and 48-52. The Code is available online at http://www.umb.edu/student_services/student_rights/code_conduct.html.