[Home] [Syllabus] [Resources] [Wiki]Design and implementation of medium- and large-scale software systems. Principles of organizing and managing such designs and implementations throughout their lifetime. Designing for modularity and software reuse; use of libraries. Dynamics of working in groups. Group lab work on a substantial software project.
On this page you will find information about:
|When:||M,W,F 10:20 - 11:35am, Lab Tu 10 - 11:50am||Where:||Sci 2185, Lab in 2610 (the dungeon)|
In addition to the book I may occasionally assign extra reading material. These materials will be available at the resources page of the course web site.
In addition, you must check your UMM e-mail frequently (at least once a day). I may send clarifications for problem sets by e-mail.
|Other class participation||5%|
Official Grading Policies:
|A||achievement that is outstanding relative to the level necessary to meet course requirements.|
|B||achievement that is significantly above the level necessary to meet course requirements.|
|C||achievement that meets the course requirements in every respect.|
|D||achievement that is worthy of credit even though it fails to meet fully the course requirements.|
|S||achievement that is satisfactory, which is equivalent to a C- or better (achievement required for an S is at the discretion of the instructor but may be no lower than a C-).|
|F (or N)||Represents failure (or no credit) and signifies that the work was either (1) completed but at a level of achievement that is not worthy of credit or (2) was not completed and there was no agreement between the instructor and the student that the student would be awarded an I (see also I)|
|I||Incomplete. Assigned at the discretion of the instructor when, due to extraordinary circumstances, e.g., hospitalization, a student is prevented from completing the work of the course on time. Requires a written agreement between instructor and student.|
For policy on late problem sets please see the syllabus.
Academic dishonesty in any portion of the academic work for a course shall be grounds for awarding a grade of F or N for the entire course.
Problem set collaboration policy:
Problem sets can be done in groups. For quidelines on work in groups please see the syllabus. Discussion with students other than those in your group (or anyone not in this class) should be limited to general approaches to the problem. All such discussions as well as use of sources other than the textbook and the handouts given in class must be acknowledged in the beginning of the problem solution.
One credit is defined as equivalent to an average of three hours of learning effort per week (over a full semester) necessary for an average student to achieve an average grade in the course. For example, a student taking a four credit course that meets for three hours a week should expect to spend an additional nine hours a week on coursework outside the classroom.
It is University policy to provide reasonable accommodations to students with disabilities. This publication/material is available in alternative formats to persons with disabilities upon request. Please contact the instructor or the Disability Services office, 589-6178, Room 362 Briggs Library to discuss accommodation needs.