Course Title
Informatics 122
Software Design II
Winter 2014
Professor
Emily Navarro
http://www.ics.uci.edu/~emilyo
emilyo@uci.edu
Office Hours
By appointment (generally before or after class)
Reader
Mattias Giorgio
http://www.ics.uci.edu/~mgiorgio/
mgiorgio@uci.edu
Office: DBH 5209
Logistics
Location: DBH 1300
Day and time: Tuesday and Thursday, 5:00-6:20pm
Catalogue Description
122 Software Design II (4). Introduction to implementation design: designing the internals of a software application. Topics include design aesthetics, design implementation, design recovery, design patterns, and component reuse. Includes practice in designing and case studies of existing designs. Prerequisite: Informatics 121.
Book
Design Patterns: Elements of Reusable Object-Oriented Software (Addison-Wesley Professional Computing Series, Hardcover), Erich Gamma, Richard Helm, Ralph Johnson, John Vlissides, 1995
Grades
All students enrolled in the course will earn a letter grade based upon: (a) class attendance and participation, (b) assignments, (c) the final class project, and (d) team evaluations.
Grade distribution will be as follows (as suitably adjusted with team evaluations):
Course Mailing List
To send mail: 37060-W14@classes.uci.edu
To view the archive: https://eee.uci.edu/classmail/w14/37060/
Students with Disabilities
Any student who feels he or she may need an accommodation based on the impact of a disability should contact me privately to discuss his or her specific needs. Please also contact the Disability Services Center at (949) 824-7494 as soon as possible to better ensure that such accommodations are implemented in a timely fashion.
Copyright
The documents below are included to ensure timely dissemination of scholarly and technical work on a non-commercial basis and are for the sole use of students enrolled in Informatics 122. Copyright and all rights therein are maintained by the authors or by other copyright holders, notwithstanding that they have offered their works here electronically. It is understood that all persons copying this information will adhere to the terms and constraints invoked by each author's copyright. These works may not be resposted without the explicit permission of the copyright holder.
Schedule
|
Week |
Date |
Topic |
Slides |
Assignments |
|
1 |
January 7 |
Review and Preview |
|
|
|
|
January 9 |
Design Aesthetics |
Assignment 1, part 1 out (individual, moderate) |
|
|
2 |
January 14 |
Design Aesthetics |
Assignment 1, part 1 due Assignment 1, part 2 out (individual, moderate) |
|
|
|
January 16 |
Design Aesthetics Reflection |
Assignment 1, part 2 due |
|
|
3 |
January 21 |
Design Aesthetics Reflection |
Assignment 1, part 3 due Assignment 2 out (individual, heavy) |
|
|
|
January 23 |
Design Aesthetics |
|
|
|
4 |
January 28 |
Design Patterns |
|
|
|
|
January 30 |
Design Patterns |
|
|
|
5 |
February 4 |
Design Patterns |
Assignment 2 due Assignment 3, part 1 out (individual, moderate) |
|
|
|
February 6 |
Refactoring |
Assignment 3, part 2 out (individual, moderate) |
|
|
6 |
February 11 |
Design Recovery |
Assignment 3 (parts 1 and 2) due Assignment 4 out (team, heavy) |
|
|
|
February 13 |
Design Recovery |
... |
|
|
7 |
February 18 |
Design Recovery Presentations |
... |
Assignment 4 due |
|
|
February 20 |
Reuse |
Assignment 5 out (team, moderate) |
|
|
8 |
February 25 |
Design in the Large |
|
|
|
|
February 27 |
Reuse Presentations |
Assignment 5 due Final Design Project out (team, heavy) |
|
|
9 |
March 4 |
Final Design Project |
"Plan of attack" presentations (15 min. per team) |
|
|
|
March 6 |
Final Design Project |
Preliminary design presentations (20 min. per team) |
Preliminary design documents due |
|
10 |
March 11 |
Final Design Project |
Detailed design presentations (20 min. per team) |
Detailed design documents due |
|
|
March 13 |
Final Design Project |
First demos (20 min. per team) |
Updated design documents due |
|
Finals week |
March 20, 4:00 - 6:00pm |
Final Design Project |
Final design and retrospective on design presentation (15 min. per team) Final demo (15 min. per team) |
Final Design Project due: Updated design documents Code (via a CM repository) |
|
|
|