Introduction

This is the home page for CS681-682-683, the graduate capstone course in software engineering. CS681 is for software engineering theory (2004 Fall). CS682 and 683 are for the year long team project (2004 Fall and 2005 Spring). In CS682 and 683, each team of 4 or 5 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 development at the annual alumni party.

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

1. Course Scheduling Software (customer: Jed Lippard, Prospect Hill Academy Charter School)
2. Math Tutoring Online Registration System (customer: Cynthia Jahn, Math Resource Center, UMass Boston)
3. SSFT-RFE (Scansoft Reporting Front End) (customer: Bob Haverty, ScanSoft, Inc.)
4. UML Virtual Machine (customer: Jun Suzuki, UMass Boston)

Student Roster and Project Assignments

Here is a list of 16 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. David Frankel, Model Driven Architecture: Applying MDA to Enterprise Computing, Wiley, 2003, ISBN: 0471319201. $40.00.

2. Stephen J. Mellor, et al., MDA Distilled: Principles of Model-Driven Architecture, Addison Wesley, 2004, ISBN: 0201788918. $34.99

3. Jos Warmer and Anneke Kleppe, The Object Constraint Language: Getting Your Models Ready for MDA, Second Edition, Addison Wesley, 2003, ISBN: 0321179366. $39.99.

Recommended (but not required)textbooks:

1. Frank Budinsky et al., Eclipse Modeling Framework, Addison Wesley, 2003, ISBN: 0131425420. $49.99.

2. Kent Beck, Test Driven Development: By Example, Addison Wesley, 2002, ISBN: 0321146530. $34.99.

Reading Assignments

1. B. Bruegge and A. Dutoit, "What is Software Engineering?," In Object-Oriented Software Engineering: Using UML, Patterns and Java, Chapter 1.2, 2004.
2. D. Frankel, "Software Industrialization and the New IT," In D. Frankel (ed.), MDA Journal, Business Process Trends, Sept 2003.
3. G. Booch, A. Brown, S. Iyengar, J. Rumbaugh, B. Selic, "An MDA Manifesto," In D. Frankel (ed.), MDA Journal, Business Process Trends, May 2004.
4. M. Henning, "Computing Fallacies or: What is the World Coming To?," Object Management Group, omg/01-07-02, 2001.
5. P. A. Bernstein, “Middleware: A Model for Distributed System Services,? In Communications of the ACM, vol. 39(2), pp. 87-99, February 1996.
6. The Internet2 Project, Middleware FAQ
7. K. Taylor, What is Middleware?, 2004.
8. S. Vinoski, "Is Your Middleware Dead?," In IEEE Internet Computing, No. 5, September/October, 2004.
9. J. Lukkien, Middleware: Survey, 2004.
10. G. Cernosek and E. Naiburg, "The Value of Modeling," white paper, IBM Rational, June 2004.
11. Alex E. Bell, Ryan W. Schmidt, "UMLoquent Expression of AWACS Software Design," In Communications of ACM, Vol 42 No 10, October 1999.
12. Jim Conallen, "Modeling Web Application Architectures with UML," Communications of ACM, Vol 42 No 10, October 1999.
13. Alex E. Bell and Grady Booch, "Death by UML Fever," In ACM Queue Magazine, Volume 2, Issue 1, March 2004.
14. Jan J?rjens, "Secure Java Development with UML," In Proc. First International IFIP TC-11 WG 11.4 Working Conference on Network Security, November 2001.
15. Jim Conallen, "Modeling Web Application Design with UML," 1999.
16. L. Baresi, F. Garzotto and P. Paolini, "Extending UML for Modeling Web Applications," In Proc. 34th Annual Hawaii International Conference on System Sciences, January 2001.
17. Eric Braude, "Identifying and Retiring Risks," In Software Engineering: An Object-Oriented Perspective, Chapter 2.4, Wiley, 2001.
18. Bertrand Meyer, "Applying Design by Contract," In IEEE Computer, vol. 25, no. 10, October 1992.
19. Eiffel Software, Building bug-free O-O software: An introduction to Design by Contract.
20. Nicolas Serrano and Ismael Ciordia, "Ant: Automating the Process of Building Applications," In IEEE Software, Vol. 21, No. 6, November/December 2004.

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.