Section D - Spring Quarter 1999
Tuesday & Thursday 4:30 - 6:00 PM
|
INSTRUCTOR: Allison Elliott Tew |
|
|
|
|
|
|
|
|
|
TEACHING ASSISTANT: Russ Keldorph |
|
|
|
|
|
TEXT: |
|
|
|
|
|
|
|
|
|
|
|
|
OVERVIEW
|
Week |
Date |
Topic |
Reading |
Prepared Lecture |
Deliverable |
|
|
1 |
3/30 |
Course Overview Introduction to Software Engineering |
Pfleeger, Chapter 1 |
|
|
|
|
|
4/1 |
Project Planning
Project Introduction & Team Organization |
Pfleeger, Chapter 3 Brooks, Chapters 2, 3, & 7 |
|
|
|
|
2 |
4/6 |
Software Lifecycle & Process Models |
Pfleeger, Chapter 2 Brooks, Chapters 16 & 17 |
|
|
|
|
|
4/8 |
Requirements Engineering |
Pfleeger, Chapter 4 Brooks, Chapters10 & 15 |
|
|
|
|
3 |
4/13 |
Requirements Analysis: Structured Techniques |
|
|
||
|
|
4/15 |
Requirements Analysis: Object-Oriented Techniques |
|
|
|
|
|
4 |
4/20 |
Software Design Concepts |
Pfleeger, Chapter 5 |
|
|
|
|
|
4/22 |
Review for Midterm |
|
|
|
|
|
5 |
4/27 |
Midterm |
|
|
|
Midterm |
|
|
4/29 |
Return SRS and Midterms Class Reorganization |
|
|
|
|
|
6 |
5/4 |
Requirements Revisited |
|
|
|
|
|
|
5/6 |
Overview of Design Project Continued Class Reorganization |
|
|
|
SRS Regrade |
|
7 |
5/11 |
Software Architecture |
Brooks, Chapter 4 |
|
|
|
|
5/13 |
Structured Software Design Object-Oriented Software Design |
Brooks, Chapter 11 |
|
|
||
|
8 |
5/18 |
|
|
|
||
|
|
5/20 |
Program Implementation Prototyping |
Pfleeger, Chapter 6 Brooks, Chapter 13 |
|
|
|
|
9 |
5/25 |
Testing Forgotten Activities Maintenance |
Pfleeger, Chapters 7 & 8 Pfleeger, Chapter 9
Pfleeger, Chapter 10 |
|
|
|
|
5/27 |
The Mythical Man-Month Discussion Course Wrap-up |
Brooks, Chapter 19 |
View |
Download |
|
|
|
10 |
6/1 |
Project Presentations |
|
|
|
|
|
|
6/3 |
Project Presentations |
|
|
|
|
|
Finals |
6/7 |
Final Exam - 11:30 - 2:20 |
|
|
|
Final Exam |
|
6/11 |
Project Demonstrations |
|
|
|
Prototype & User Documentation |
|
GENERAL INFORMATION:
General Catalog Course Description:
Prerequisites: CS 2201 or one of the following: CS 2360, CS2390, or CS 2430; and junior standing
Introduction to current techniques used in large-scale software development. Topics include requirements analysis, functional specification, systems design, implementation, testing and maintenance.
Goals:
Individual grades for the course will be based on the following: individual homework assignments, exams, group project work, and class participation. Students taking the class on a Pass/Fail basis will be required to earn a final letter grade of C or better to receive a passing grade.
ACADEMIC HONESTY: All students are expected to maintain standards of academic integrity by giving proper credit for all work. All suspected cases of academic dishonesty will be reported and pursued.
ATTENDANCE POLICY: Unexcused absences from the midterm exam, final exam, or project presentations will result in an automatic failure (F) of the class.
All assignments are due at the beginning of class on the due date, unless otherwise specified. Assignments will be accepted up to 24 hours late, with a 10 point late deduction. No assignments will be accepted after 24 hours.
|
CATEGORY |
PERCENTAGE |
|
Homework |
20% |
|
Homework #1 - Modeling Exercise |
10% |
|
Homework #2 - Design Review Worksheet |
5% |
|
Homework #3 - Design Review Reflection |
5% |
|
Midterm Exam |
10% |
|
Project |
50% |
|
Preliminary Problem Analysis & Project Plan |
5% |
|
Software Requirements Document |
10% |
|
Design Document |
10% |
|
Prototype |
10% |
|
Presentation |
5% |
|
Individual Contribution |
10% |
|
Class Participation |
5% |
|
Final Exam |
15% |
Office: 113 College of Computing