Introduction

This is the home page for CS681-682-683, the graduate capstone course in software engineering. CS681 is for software engineering theory (Fall 2005). CS682 and 683 are for the year long team project (Fall 2005 and Spring 2006). In CS682 and 683, each team of 3 or 4 students will work on a project for a real customer. Students will apply what they have learned in CS681 to the production of a real software (product). Each project team will present its software product at the annual alumni party in May 2006.

Course goals

• Study software engineering methodologies, techniques and tools
• Learn the current trends in software engineering
• Work in a software development team for a full year
• Obtain a working knowledge of object-oriented analysis, design, implementation and testing
• Master presentation and documentation skills
• Effectively communicate with a customer
• Develop a software product for a customer

Course Work

• Paper/book readings (CS681)
• Student presentations and discussions of assigned readings (CS681)
• Study of software engineering tools (CS681)
• Written and programming homeworks (CS681)
• Student presentations and discussions of homeworks (CS681)
• Guest lectures (CS681)
• Presentations by prospective customers (CS682/683)
• Meetings and discussions with customers (CS682/683)
• Software development for customers (CS682/683)
• Documentation and presentations on project progress (CS682/683)

Projects

Student Roster and Project Assignments

Here is a list of students.

Project Deliverables

Each project team will deliver the following artifacts to the instructor over the year:

• Project summary document
• Project requirements specification
• Project plan
• Progress reports
• Minutes of the meetings with a customer
• Installation and maintenance document
• source/binary code and supporting resources
• Project wrap-up document

Course Schedule

Stay tuned on the schedule page.

Textbooks

Required textbooks:

1. Jack Greenfield and Keith Short, Software Factories: Assembling Applications with Patterns, Models, Frameworks and Tools Wiley, 1st edition, ISBN: 0471202843.

2. Stephen J. Mellor, Kendall Scott, Axel Uhl and Dirk Weise, MDA Distilled Addison Wesley, 1st edition, ISBN: 0201788918.

3. Geri Schneider and Jason P. Winters, Applying Use Cases: A Practical Guide Addison Wesley, 2nd edition, ISBN: 0201708531.

Recommended (but not required) textbooks:

1. David Frankel, Model Driven Architecture: Applying MDA to Enterprise Computing, Wiley, 2003, ISBN: 0471319201.

2. B. Bruegge and A. Dutoit, Object-Oriented Software Engineering: Using UML, Patterns and Java, 2004, ISBM: 0130471100.

3. Kent Beck, Test Driven Development: By Example, Addison Wesley, 2002, ISBN: 0321146530.

Reading Assignments

1. B. Bruegge and A. Dutoit, Object-oriented Software Engineering, Preface and Chapter 1 (Introduction to Software Engineering), second edition, Pearson, 2004.
2. D. Frankel, Model Driven Architecture: Applying MDA to Enterprise Computing Forward and Chapter 1 (Pressure and Progress: How We Arrived at This Point), Wiley, 2003.
3. I. Sommerville, Software Engineering, 7th Edition , Chapter 1 (Introduction), Peason, 2004.
4. F. Brooks, "No Silver Bullet: Essence and Accidents of Software Engineering," In Computer, Vol. 20, No. 4, April 1987.
5. B. Cox, "No Silver Bullet Revisted," In American Programmer Journal, November 1995.
6. P. Wegner, "Research Directions in Software Technology," In Proc. of the 3rd International Conference on Software Engineering, 1978.
7. B. Bruegge and A. Dutoit, Object-oriented Software Engineering, Chapter 2 (Modeling with UML), second edition, Pearson, 2004.
8. G. Cernosek and E. Naiburg, "The Value of Modeling," white paper, IBM Rational, June 2004.
9. D. Gotterbarn, K. Miller, S. Rogerson, "Software Engineering Code of Ethics is Approved," In Communications of the ACM, Vol. 42, Issue 10, October 1999.
10. G. Booch, Object-Oriented Analysis and Design with Applications, Chapters 1 and 2, Addison Wesley, 1994.
11. R. N. Charette, "Why Software Fails," In IEEE Spectrum, September 2005.
12. CNN/Money, "Prius Hybrids Dogged by Software," May 2005.
13. Hans-Erik Eriksson, et al., UML2 Toolkit, Chapters 1 and 2, Wiley, 2004.
14. F. Hapgood, Up The Infinite Corridor: MIT and The Technical Imagination, Chapter 3, Addison Wesley, 1993.
15. C. Jones, "Patterns of large software systems: failure and success," In IEEE Computer, Vol.28, Issue 3, March 1995.
16. L. May, "Major Causes of Software Project Failures," In Journal of Defense Software Engineering, July 1998.
17. T. Love, Object Lessons: Lessons Learned in Object-Oriented Development Projects, Chapter 1, Cambridge University Press, 1993.
18. E. Gamma, R. Helm, R. Johnson and J. Vlissides, Design Patterns: Elements of Reusable Object-Oriented Software, Composite Pattern, Addison-Wesley, 1995.
19. E. Gamma, R. Helm, R. Johnson and J. Vlissides, Design Patterns: Elements of Reusable Object-Oriented Software, Chapter 2 (A Case Study: Designing a Document Editor), Addison-Wesley, 1995.
20. W3C, Document Object Model (DOM) Level 1 Specification, Chapter 1 (DOM Core Level 1), Version 1.0, 1998.
21. M. Fowler, Refactoring: Improving the Design of Existing Code, Pull up Method, Addison Wesley, 1999.
22. E. Gamma, R. Helm, R. Johnson and J. Vlissides, Design Patterns: Elements of Reusable Object-Oriented Software, Proxy Pattern, Addison-Wesley, 1995.
23. G. Booch, "UML in Action," In Communications of ACM, Vol 42 No 10, October 1999.
24. Alex E. Bell, Ryan W. Schmidt, "UMLoquent Expression of AWACS Software Design," In Communications of ACM, Vol 42 No 10, October 1999.
25. Jim Conallen, "Modeling Web Application Architectures with UML," In Communications of ACM, Vol 42 No 10, October 1999.
26. Bran Selic, "Turning clockwise: using UML in the real-time domain," In Communications of ACM, Vol 42 No 10, October 1999.
27. E. Gamma, R. Helm, R. Johnson and J. Vlissides, Design Patterns: Elements of Reusable Object-Oriented Software, Visitor Pattern, Addison-Wesley, 1995.
28. T. Meservy and K. Fenstermacher, "Transforming Software Development: An MDA Road Map," In IEEE Software, September 2005.
29. S. Mellor, A. Clark and T. Futagami, "Introduction: Model-Driven Development," In IEEE Software, September 2003.
30. B. Selic, "The Pragmatics of Model-Driven Development," In IEEE Software, September 2003.

31. B. Mayer, Object-Oriented Software Construction, Chapter 1.

Office Hours

S-3-168
M W 4:00pm-5:30pm

Grading

A separate grade will be awarded for each of CS 681, CS 682 and CS 683. The grade for CS681 will be based on the participation in class and the individual performance on homeworks and presentations. The grades for CS682 and CS683 will be based on a combination of the project team work and individual contribution to that effort.

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.

See also http://www.cs.umb.edu/~eb/honesty.html.