CS 4330 - Software Engineering Applications (GT)
CS 6310A - Software Architecture and Design (GT)
CS 6310Q3 - Software Architecture and Design (GT Lorraine)
CS 6310RKR - Software Architecture and Design (Korea)
Spring 2009

Meeting Times (EST): Monday, Wednesday; 7:00-8:30pm
Meeting Place: Klaus 2443

Instructor: Spencer Rugaber; Personal teaching philosophy
Office: Klaus Advanced Computing Building 2404
E-mail:
Phone: 404.894.8450
Office Hours: MW 4:30-6:00

Teaching Assistants:

Ogechi Nnadi
E-mail:
Office: Klaus 2405
Office Hours: Tuesdays and Thursdays, 2-3pm

E-mail:

Newsgroup: news:git.cc.class.cs4330 (Instructions for setting up access)

Swikis:

Descriptions

Learning Objectives

• Understand and apply object-oriented design techniques
• Develop and evaluate software architectures
• Select and use appropriate architectural styles
• Select and use appropriate software design patterns
• Express the design an application using UML
• Specify parts of the design using a formal design language
  
• Understand and perform a design review

Required Text

Grading

Class Policies

• You should familiarize yourself and conform to the Georgia Tech Honor Code (with graduate student addendum) and academic policies as specified in the Georgia Tech Catalog
• All submitted work in the class should be done individually unless explicitly stated otherwise
• All incorporated material not created by the student should be appropriately cited
  
• Assignments and projects are due before the start of class on the day listed in the assignment, NOT the day on which the assignment or project appears in the syllabus
  
• All turn-in will be made using the Swiki; do not send them via e-mail nor bring them to class
• You are not permitted to look at any other team's or individual's submittal at any time
• Readings should completed before the class for which they are listed
• Any exceptions to these rules will be announced on the newsgroup, which you are expected to read
• If you have any questions concerning a grade that you received in this course, first contact the teaching assistant who graded it. If you are still not satisfied, you may contact me about the matter.
• All documents turned in for this course should obey the following formatting rules

  • All written assignments must be prepared using a word processor

  • Each document's page count assumes a double-spaced 12 point font with the margins of 1.25" left/right and 1" top/bottom

  • Each document should clearly identify the author(s), date, and the designated assignment or project

  • Proper citation for any referenced resource (author, title, publication name, date, and page number or URL) must be included in the document

  • All assignments should be grammatical with accurate spelling. All writing assignments are expected to be spell checked and proof read

  • The following book provides excellent guidance to you in preparing your written assignments: Strunk, William. The Elements of Style, 3rd Edition, Macmillan, New York, 1979. It is also available at here.
    

Class Schedule (Due Dates for French Students)

Resources

• Ruben Prieto-Di­az and Guillermo Arango.
  Domain Analysis and Software Systems Modeling.
  IEEE Computer Society Press, 1991.
• Martin Fowler.
  UML Distilled:Applying the Standard Object Modeling Language.
  Addison Wesley, 1997.
• UML Specification v2.1.2
• OCL Specification V2.0
• James Rumbaugh, Ivar Jacobson, and Grady Booch.
  The Unified Modeling Language Reference Manual.
  Addison-Wesley, 1999.
• Grady Booch, James Rumbaugh, and Ivar Jacobson.
  The Unified Modeling Language User Guide.
  Addison-Wesley, 1999.
• David Harel.
  "On Visual Formalisms."
  Communications of the ACM, 32(5):514-530, May 1988.
• Jos Warmer and Anneke Kleppe.
  The Object Constraint Language.
  Addison-Wesley, 1999.
• Jim Woodcock and Martin Loomes.
  Software Engineering Mathematics.
  Addison Wesley, 1989.
• Gamma, Erich et al.
  Design Patterns: Elements of Reusable Object-Oriented Software.
  Addison Wesley, 1995.
• Erich Gamma and Kent Beck.
  "JUnit A Cook's Tour."
  Java Report, May 1999.
• David Garlan and Mary Shaw.
  Advances in Software Engineering and Knowledge Engineering.
  1993.
• Wolfgang Emmerich.
  "Software Engineering and Middleware: A Roadmap".
  International Conference on Software Engineering - Future of Software Engineering Track, 117-129, 2000.
• Mary Shaw and David Garlan.
  Software Architecture: Perspectives on an Emerging Discipline.
  Prentice Hall, 1995.
• Nikunj R. Mehta, Nenad Medvidovic and Sandeep Phadke.
  "Towards a Taxonomy of Software Connectors."
  Proceedings of the 22nd International Conference on Software Engineering,Limerick, Ireland, pp. 178-187, 2000.
• N. Medvidovic, D. S. Rosenblum, D. F. Redmiles and J. E. Robbins.
  
• "Modeling Software Architectures in UML."
  ACM Transactions on Software Engineering and Methodology, 11(1):2-57, January, 2002.
• N. Medvidovic and R. N. Taylor.
  " A Classification and Comparison Framework for Software Architecture Description Languages."
  IEEE Transactions on Software Engineering, 26(1):70-93, January 2000.
• P. B. Kruchten.
  "The 4+1 View Model of architecture."
  IEEE Software, 12(6):42-50, November-December, 1995.
• Robert C. Martin.
  "Heuristics and Coffee."
  Chapter 11 in UML for Java Programmers, Prentice Hall, 2003.
• Clemens Szyperski.
  Component Software, 2nd edition.
  Addison Wesley, 2002.
• Martin Fowler.
  Patterns of Enterprise Application Architecture.
  Addison Wesley, 2003.
• Krzysztof Czarnecki and Ulrich Eisenecker.
  Generative Programming: Methods, Tools, and Applications. Addison-Wesley, 2000.
• Antoine Beugnard, Jean-Marc Jezequel, Noel Plouzeau and Damien Watkins.
  "Making Components Contract Aware."
  IEEE Computer, 32(7):38-45, July 1999.
  
• Robert C. Martin.
  Clean Code / A Handbook of Agile Software Craftsmanship.
  Prentice Hall, 2008.
  
• Arthur J. Riel.
  Object-Oriented Design Heuristics.
  Addison-Wesley, 1996.
  
• Kai Qian, Xiang Fu, Linin Tao, Chong-Wei Xu and Jorge L. Diaz-Herrera.
  Software Architecture and Design Illuminated.
  Jones and Bartlett, 2010.
  

Other Resources

• Poseidon
• Tigris.org
• Octopus
• Dresden OCL parser
• IBM OCL parser
• Enterprise Architect UML modeling tool
• Patterns Home Page
• Sun Java J2EE patterns page
• Fowler enterprise patterns page
• Atlanta evaluation form
• France evaluation form
• Korea evaluation form
• Sample exam questions

Lecture Videos