CS 351 Design of Large Programs

Instructor:

Joe Michael Kniss
Ferris 301G
277-2967
jmk (at) cs.unm.edu
Office Hours: TTh 10:00am - 12:00pm

TA:

David Godinez
Ferris 301A
dgodinez (at) cs.unm.edu
Office Hours: M 11:00am - 1:00pm

Info:

Official class web page:
www.cs.unm.edu/~jmk/cs351
Class Mail List: cs351@cs.unm.edu Signup

Lab Hours
M 1:00-1:50 Pod 110
T 12:30-1:45 Pod 110

Recommended Text

The Java Programming Lanquage 4th ed Ken Arnold and David Holmes, ISBN 978-0321349804
This book is available at the bookstore.
Note: text is not required, but recommended for the class.

Design Patterns Gamma, Helm, Johnson, Vlissides, ISBN 978-0201633610

Debugging David Agans, ISBN 978-0814474570

Refactoring Fowler, Beck, Briant, Opdyke, ISBN 978-0201485677

Effective Java Joshua Bloch, ISBN 978-0321356680

The Mythical Man-Month Frederick Brooks, ISBN 978-0201835953

Description

This class is about designing big software, where big refers to projects with a scope too larde to be handled by any one person at any one time. This course primarily deals with software design, time management, and strategies for completing complex coding tasks.

Content

Grading

• 50% Design Projects. Two individual, one group.
• 20% Exams and quizzes
• 15% Labs
• 15% Participation

Late projects/assignments will recieve a 20% per day penelty. There are 3 "slack" days, which are free late days. Please use these wisely. Participation grades will be primarily based on inclass critiques. Students will be asked to present code solutions and provide feedback for the presenter. This class has 2 lab sections. Students are required to attend one lab each week and complete the lab assignments for a grade.

Cheating will not be tolerated. This includes coping code or sharing work on the design and implementation of individual projects. Students may discuss details of the project specification, but this should be limited to clarification of details. If you are in doubt, ask the instructor or TA. All student code and design on individual projects must the their own. Cheating will result in a negative score for the project and the penalty will be applied to any parties involved.

• Copy code from another person.
• Copy code from the Internet or another source. (If there's some code that you would really, really like to use, please check with us before you do it.)
• Attempt to disassemble, decompile, or otherwise reverse engineer compiled example programs.
• Read someone else's paper program listings (e.g., discarded in the trash).
• Allow another person to copy your code.
• Leaving your class files world readable. (!)
• Copy/plagiarize text from another person, the Internet, a published work, etc.
• Attempt to steal another person's code (e.g., by cracking, password sniffing, etc.)
• Use an external Java library (i.e., libraries other than those included with the JDK) without documenting it.
• Violate copyright or license agreements on external libraries. If you use external library code, it is your responsibility to understand and comply with the appropriate copyright and license issues.
• Violate the University policy on acceptable computer use

Assignment Handin

Homework, unless otherwise specified, should be submitted via email to the TA (dgodinez (at) cs.unm.edu). The subject line must include "cs351" and the assignment number (eg. Assignment 1 or Project 1 etc..). You should attach the files in the most compact form you can, for example project code should be in a .jar file and must include both .class and .java files. If your project includes many documentation files you should submit a .tar.gz (.tgz if you like) archive of the directory. Besure to include any information about running the assignment in a .txt file. Do not handin intermediate files, i.e. temporary files, unnecessary program outputs, .svn directories and administrative files, and other irrelevant material. We also advise that you test your handin by unwraping it in a fresh directory, making sure it runs, and includes all the necessary materials.

Course Syllabus **

• Week 1
  • Introduction
  • Unit testing
    • JUnit 3 in Eclipse
    • JUnit Docs
  • Assignment 1 Due Sep 3 7p
  • Lecture Slides
    Note: we discussed JUnit 3 in class, there are many changes in JUnit 4
  • A comparison of JUnit 3 and 4
• Week 2
  • Interfaces (Chapter 4)
  • Lecture Slides
  • Generics (Chapter 11) Tutorial
  • Lecture Slides
• Week 3
  • Serialization (Chapter 20.8)
  • Lecture Slides
  • Project ONE
• Week 4
  • Static and Code Design intro
  • Lecture Slides
• Week 5
  • Statics and UML Modeling
  • Lecture Slides
  • Intro to Design Patterns
  • Lecture Slides
  • Singleton Pattern
  • Adapter Pattern
  • Command Pattern
• Week 6
  • Observer Pattern
  • Strategy Pattern
  • Bridge Pattern
  • Model-View-Controller
• Week 7
  • Code Reviews
  • Exceptions
  • Lecture Slides
• Week 8
  • Midterm review
  • Lecture Slides
• Week 9
  • Miterm Oct 23
• Week 10
  • Threads Intro
  • Lecture Slides
  • More Threads
  • Lecture Slides
  • Amdahls Law
• Week 11
  • Test Redo (correct error on midterm) due Nov 18
  • Extra Credit Due Nov 18
    • Implement 4 design patterns
    • Each pattern must be separate app
    • Each pattern must be a minimal (yet sufficient) implementation
    • Each implementation must use 2 (or more) threads with key parts of pattern distributed among threads
    • Use standard out or log file to print status of pattern in operation, ex. "Thread 0: in StrategyA"
• Week 12
  • Parsing infix equations See also Mathematical Formula Decomposer, Example implementation
• Week 13
  • Final Project Specification NOTE: Updated Nov 20 3:30pm
  • Student Team Assignments
    • Team 1: William Gilson, Hsing Liu, Andrei Buium
    • Team 2: Kenneth Anderson, William Carr, Rebecca Dicharry, Paul Wowk
    • Team 3: Erich Doll, Matthew Dosanjh, Antonio Espinoza
    • Team 4: Aaron Holck, John Knowles, Daniel McDonald
    • Team 5: Michael Mellone, Hugh Mitchel, Rashid Ramsey
    • Team 6: Christian Romano, Brian Sondreal, Ling Tzu Wang, Chris White
• Week 14
  • Extreme Programming
  • Pair Programming
  • Cola: Real-time pair programming in Eclipse
  • Refactoring
• A recent GP image algorithm via Slashdot
• Final Project Summary (individual) due 12-17-08 12:00am. Please summarize your contribution to the final project in 2 pages or less. Discuss:
  • Specific modules you were responsible for
  • Intellectual contribution to the overall project
  • Other contributions (e.g. integration, bug fixes, features)
  • Include 3 images that you generated using the system

Resources

• Lab information
• UML introduction.
• Argo UML modeling tool
• Support code docs
• Crawler Support Code