YCP Logo Syllabus

Instructor:David Hovemeyer
Office:KEC 113
Office Hours:M-F, 2-3 PM; or by arrangement
Class Location:KEC 119
Class Times:MWF 9:00-9:50 [Section 101],
MWF 1:00-1:50 [Section 102]

CS 320 - Software Engineering and Design

Spring 2011

Course Description

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 201 or IFS 201 with a grade of 2 or higher


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

Course Structure and Expectations

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.

Learning Outcomes

By the end of the course, you will be able to:

  • Collect software requirements and develop use cases
  • Develop analysis and design models
  • Critique analysis and design models to suggest possible improvements
  • Use analysis/design models to guide implementation
  • Assess and ensure software quality using unit tests, system tests, metrics, and static analysis
  • Understand the software lifecycle
  • Understand the issues involved in planning and estimation for a software project



Grades are assigned on a 100-point scale:

Numeric Range Letter Grade
90-100 A (4.0)
85-90 B+ (3.5)
80-85 B (3.0)
75-80 C+ (2.5)
70-75 C (2.0)
60-70 D (1.0)
0-60 F (0.0)

Your overall grade for the course will be determined as follows:

  • Individual homework assignments: 10%
  • Midterm exams: 30% (15% each)
  • Semester-long team software project: 50%
  • Attendance and participation: 10%

Course website

Please check the course web page, http://faculty.ycp.edu/~dhovemey/spring2011/cs320/, regularly for important announcements.

Reading Assignments

Reading assignments will be posted on the course web page. I expect you to do the reading before class. When I give a lecture, I will assume you have done the reading. I encourage you to use class time to ask questions about parts of the reading you did not understand to your satisfaction.

Posting and submission of assignments and labs

Assignments will be posted on the course web page, http://faculty.ycp.edu/~dhovemey/spring2011/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.

Academic Integrity

The college catalog states the following:

Academic dishonesty will not be tolerated at York College. Academic dishonesty refers to actions such as, but not limited to, cheating, plagiarism, fabrication of research, falsification of academic documents, etc., and includes all situations where students make use of the work of others and claim such work as their own.

Please refer to the college catalog for an explanation of the official college policies relating to academic integrity.

The following policy pertains to homework and graded (individual) programming assignments in this course:

All homework assignments and graded (individual) programming assignments are to be completed individually. I encourage you to discuss high level concepts and strategies 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 a programming assignment, it must be your program, not your adaptation of someone else's program.

In order to receive credit for an individual homework assignment or programming assignment, you must submit a signed attestation confirming that you completed the assignment on your own, and did not copy any code or other material from any person or source.

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.

Any violation of the course's academic integrity policy will be referred to the Dean of Academic Affairs, and could have consequences ranging from a 0 on an assignment to dismissal from the college.

Late Assignments

Late assignments will be marked down 10% per day late. No credit is given for assignments turned in more than 3 days late.


No make-up exams will be given without approval of the instructor prior to class unless proof of extreme emergency or illness is provided.

Attendance and Participation

I expect you to attend class and participate regularly in class discussions. If you miss a class, please notify me in advance. You are responsible for all material covered in class, 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 participation. Frequent absence and/or lack of participation in class discussions will reduce the credit you receive for attendance and participation.

You are responsible for keeping up with the reading assignments as described in the schedule below.


I expect you to conduct yourself as a professional in this course. Professionalism includes:

  • Respect for and courteous interaction with peers, faculty and facilities;
  • Integrity, which includes at its core honesty, responsibility and accountability for one’s own actions;
  • Sensitivity and appreciation for diverse cultures, backgrounds, and life experiences;
  • Constructive evaluation, which means that criticism is offered and accepted in a productive manner;
  • Self-reflection and identification of one’s own strengths and weaknesses;
  • Responsibility for one’s own education and learning;
  • An attitude that fosters professional behavior in colleagues and peers;
  • Punctuality at meetings and class sessions;
  • Attentive behavior during class sessions, avoiding personal or social use of cell phones, laptops, or other electronic devices;
  • Acknowledgement of the Kinsley Engineering Center as a professional workplace, and treatment of this facility as a business or office space, not as an informal space.

I reserve the right to enforce this code through the York College Code of Student Conduct.

Use of Personal Technology in the Classroom

While York College recognizes students’ need for educational and emergency-related technological devices such as laptops, PDA’s, cellular phones, etc., using them unethically or recreationally during class time is never appropriate. The college recognizes and supports faculty members’ authority to regulate in their classrooms student use of all electronic devices.

Communication Standards

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 to reading assignments:

  • UD is UML Distilled
  • XPE is Extreme Programming Explained
  • HFOO is Head-First Object-Oriented Analysis & Design
Week Note Topic Reading
Week 1: Jan 17-21 No class Mon Introduction HFOO, Appendix ii
Week 2: Jan 24-28   Elements of a Software Project HFOO, Chapter 1
UD, Chapter 2
Week 3: Jan 31-Feb 4   Requirements Gathering
Handling Changing Requirements
HFOO, Chapter 2
UD, Chapter 9
HFOO, Chapter 3
Week 4: Feb 7-11   Object-Oriented Analysis HFOO, Chapter 4
UD, Chapter 3
Week 5: Feb 14-18   Object-Oriented Design HFOO, Chapter 5
Week 6: Feb 21-25   OOD (cont'd)
GUIs, Human-Computer Interaction
Week 7: Feb 28-Mar 4 Winter break, no class
Week 8: Mar 7-11   GUIs, HCI (cont'd)  
Week 9: Mar 14-18   Team project impl.
Version Control
HFOO, Chapter 8
Week 10: Mar 21-25   Iterating and Testing
HFOO, Chapter 9
Week 11: Mar 28-Apr 1   Software Development Tools  
Week 12: Apr 4-8   Extreme Programming (XP) XPE, Chapters 1-7
Week 13: Apr 11-15   Team Project  
Week 14: Apr 18-22 No class Fri Team Project  
Week 15: Apr 25-29 No class Mon Team Project  
Week 16: May 2-6 No class Fri Team Project, Course Wrap-up