SE-2811 Software Component Design Winter 2016-2017 Dr. Mark L. Hornick

Description     Syllabus     Policies     Quizzes/Homework     Grading

Revision History

 Links removed for all labs after Christmas - modifications in progress will be completed after Christmas break.

This page was last updated on 02/10/2017.

Class Schedule

Lectures are on Monday, Thursday, and Friday in L100 from 9:00am to 9:50am.

Labs are on Wednesday in L014 from 8:00am to 9:50am.

Email me when you foresee yourself to be absent. As stated in my general course policies, attendance is mandatory for all lectures and labs.  Be sure to read the entire document for all relevant policies that apply to this course.

Course Description

This course deals with the design and implementation of software subsystems. The concept of design patterns is introduced and common patterns are applied to the development of software components. Laboratory projects provide an opportunity for teams of students to implement components and to integrate them into complete systems.

Please consult the this page for detailed learning objectives you can use as a study guide.

Textbook

Head First Design Patterns, Freeman et al, O'Reilly, 2004.

Syllabus

Course policies

My general course policies apply to this course.

Quizzes and labs

Quizzes and labs will be given or assigned each week.

You are encouraged to work with your classmates on labs, so that you can more fully understand the problem and discuss approaches to solution. However, you should work out the solutions to assignments individually.

Quizzes will be given weekly. No quiz will be given the week of the Exams. No make-up quizzes will be given in case of absences from class.

Grading algorithm

Note that this algorithm indicates how a grade will be determined for students who have successfully demonstrated mastery of the course objectives. An acceptable level of success in meeting all course objectives is a prerequisite for a passing grade in the course.

Documentation Standard

All source code submitted must use JavaDoc commenting conventions and meet the minimum documentation standards outlined below.

• The beginning of each source file should contain:
  • The name of the file.
  • A short description of the purpose of the class contained in the file.
  • The date it was originally written.
  • The original author.
  • A modification log (when appropriate) which describes:
    • What modifications were made.
    • When the modifications were made.
    • Who made the modifications.

• Each class method should contain the following documentation:
  • Explanatory notes regarding the overall usage of the method; that is, what the method does.
  • The parameters passed in the formal argument
  • What the method returns (if anything)
  • Any sources other than the author (Web URL, fellow student, etc.) that aided in the design of the method (and what aid was provided).
  • Explanatory notes regarding the internal workings and coding whose purpose is not immediately obvious to someone with your current level of programming knowledge
     

.