Revised 2/4 - updated reading assignments
Revised 3/26 - updated schedule
||GH 118 /
or by arrangement
|Class Times||Section 01: MWF
Section 02: MWF 9:00-9:50
This course describes the software development process in detail, including the software life cycle and models of software development; requirements analysis and software design techniques, such as SADT and Jackson Design Methodology; techniques for software quality assurance, including design reviews, testing, metrics, and an introduction to program verification; and software project planning, organization, and management. Students will be expected to participate in a team-programming project.
CS 200 or IFS 201
Kent Beck and Cynthia Andres, Extreme
Programming Explained, 2nd ed.
Martin Fowler, UML Distilled, 3rd ed.
Brett D. McLaughlin, Gary Pollice, and David West, Head First Object-Oriented Analysis & Design
The overall goals of this course are to explore the issues surrounding "real world" software development, and to learn how to work effectively with the people involved in a software project.
The course will heavily emphasize discussion and participation. As such, I expect you to attend class and participate fully in the in-class activities. Repeated absences or failure to participate will negatively affect your grade.
By the end of the course, you will be able to:
Grades are assigned on a 100-point scale:
Your overall grade for the course will be determined as follows:
Please check the course web page, http://faculty.ycp.edu/~dhovemey/spring2008/cs320/, regularly for important announcements.
Assignments and labs will be posted as zip files on the course
web page, http://faculty.ycp.edu/~dhovemey/spring2008/cs320/.
Assignments will be submitted using the server https://camel.ycp.edu:8443.
You will receive an email containing the username and password you
should use for this server.
The following policy pertains to individual
All individual homework assignments and programming assignments are to be completed on your own. I encourage you to discuss high level concepts with other students, but any work you submit must be yours alone.
Direct copying of code or other work from other students, web sites, or other sources is absolutely forbidden under any circumstances.
Any sources (books, websites, articles, fellow students, etc.) that you consult in completing an assignment must be properly acknowledged. In general, I strongly discourage you from using any resource not explicitly listed in the course syllabus or on the course web page. When you work on an individual assignment, it must be your work, not your adaptation of someone else's work.
You are allowed to (and expected to) work with the members of your team on team project(s).
Quizzes and exams must be completed individually.
Late assignments will be marked down 5% per day late. No credit is given for assignments turned in after grading has taken place.
No make-up exams will be given without approval of the instructor prior to class unless proof of extreme emergency or illness is provided.
I expect you to attend class and participate regularly in
discussions. If you miss a class, please notify me in
advance. You are responsible for all material covered in
regardless of whether or not you were present. If you attend
and participate in class regularly, you can expect to receive full
credit (10% of the course grade) for attendance and
Frequent absence and/or lack of participation in class discussions will
reduce the credit you receive for attendance and participation.
York College recognizes the importance of effective communication in all disciplines and careers. Therefore, students are expected to competently analyze, synthesize, organize, and articulate course material in papers, examinations and presentations. In addition, students should know and use communication skills current to their field of study, recognize the need for revision as part of their writing process, and employ standard conventions of English usage in both writing and speaking. Students may be asked to further revise assignments that do not demonstrate effective use of these communication skills.
This schedule may be subject to minor changes. Any changes will be announced in class and also be posted on the course web page.
Key for reading assignments: UD = UML Distilled, 3rd ed., XPE = Extreme Programming Explained, 2nd ed., HFOO = Head First Object-Oriented Analysis & Design.
|Week 1: Jan 21-Jan 24||No class Monday
||Introduction||HFOO, Appendix ii|
|Week 2: Jan 28-Feb 1||Development process||HFOO,
UD, Chapter 2
|Week 3: Feb 4-Feb 8||Requirements gathering||HFOO,
UD, Chapter 9
|Week 4: Feb 11-Feb 15||Handling changing requirements||HFOO, Chapter 3|
|Week 5: Feb 18-Feb 22||Object-oriented analysis||HFOO,
UD, Chapter 3
|Feb 25-Feb 29||Winter break, no classes|
|Week 6: Mar 3-Mar 7||OOA (cont'd)
|HFOO, Chapter 5|
|Week 7: Mar 10-Mar 14||OOD, cont'd|
|Week 8: Mar 17-Mar 21||No class Friday||OOD, cont'd|
|Mar 20-Mar 24||Spring break, no classes|
|Week 9: Mar 24-Mar 28||No class Monday||Software architecture||HFOO,
HFOO, Chapter 7
|Week 10: Mar 31-Apr 4||Team project implementation kick-off
|HFOO, Chapter 8|
|Week 11: Apr 7-Apr 11||Iterating and testing||HFOO, Chapter 9|
|Week 12: Apr 14-Apr 18||Software lifecycle
Extreme Programming (XP)
XPE, Chapters 1-5
|Week 13: Apr 21-Apr 25||Extreme Programming (cont'd)||XPE, Chapters 6-7|
|Week 14: Apr 28-May 2|
|Week 15: May 5-May 9||No class Friday||Course wrap-up|