Spring Semester 2007
Instructor: Chris Lüer, PhD
Office hours: Tu 1:30 - 3:30 or by appointment
Graduate assistant: Tai-Lin Han, MS
Section I: Tu, Th 9:30 - 10:45, RB 122
Section II: Tu, Th 3:30 - 4:45, RB 122
Description - Materials - Policies - Schedule - Teams and Projects
Catalog description:
498 Software Engineering 2--Design and Development. (3)
Studies the design and development phases of the software life cycle. Introduces the latest appropriate structured methods and applies them to a software project. This project will take a system specification and develop software from it.
Prerequisite: CS 497.
First part of the course sequence:
CS 497 Fall 2006
Required Textbooks:
Additional Readings:
Tools:
Argo/UML. Freeware UML tool.
JUnit. Freeware Java test framework.
UnitTest++. Same thing for C++.
Cocomo. Cost estimation tool.
WinCVS. Client tool for the
CVS configuration management system.
Web site: http://www.cs.bsu.edu/homepages/chl/498-07S/
Mailing List: http://www.bsu.edu/archives/cs497-l.html
You can post questions and comments
about this class to the mailing list. For private questions, please email
the instructor or the teaching assistant directly.
Assignments. Assignments are due Tuesdays at the beginning of class. Homework assignments (HW) are to be performed individually -- no team work is allowed. Milestones (MS) and Milestone Drafts are part of the team projects. Late assignments will be subject to a deduction of 10% of the maximum credit per late day. Write your name on the top of page 1; if an assignment has more than one page, please staple them. Type your answers and include printouts of diagrams.
Readings. Readings are due on the Thursday of the week they are listed for. Occasional quizzes will cover the readings. Each quiz is worth half as much as a homework assignment.
Grading.
Final Exam 25%
Midterm Exam 10%
Project 50%
Homework and quizzes 15%
If you receive 93.3% of the total course credit, you will get an A. If you receive 90.0%, you will
get an A- or better. If you receive 86.7%, you will get a B+ or better, and so on. The grading
scale will be shifted so that the median grade is at least a B+.
Peer Evaluations. The instructor gives one grade for each project team for each milestone. It will be divided up among the team members as follows. Each team member divides up 100 percent among all members of the team, giving him- or herself 1/n, where n is the number of team members. The number of points each team member gets for a milestone is the instructor's grade multiplied with the sum of the team member's peer evaluations. In this way, your team members have a significant influence on your grade.
Team Web site. Each team has a Web site, where it publishes all documents related to the project. The team may choose to make the Web site password-protected.
Status reports. Each team has to publish weekly status reports on their Web site. Here is a template.
Extra credit. Extra credit is available for additional oral presentations. Contact me if you are interested. The credit for a 15 min presentation is up to 2%.
Cheating. Consequences of cheating in this class: the course grade is lowered, possibly to F. No team work is allowed on homeworks unless it is explicitly stated. Material that is copied from books or Web pages needs to be quoted and the source must be given. Be aware of the Ball State University Student Academic Ethics Policy.
Students with special needs or disabilities. If you need course adaptations or accommodations because of a disability, if you have emergency medical information to share with me, or if you need special arrangements in case the building must be evacuated, please make an appointment with me as soon as possible.
| Week | Topic | Readings due | Assignments due |
|---|---|---|---|
| 1 | Intro; Design | ||
| 2 | Design | P9-10 | |
| 3 | Design Review; Unit Testing; Refactoring | P11 | HW1: Design Review |
| 4 | Reuse; Lab | HW2: Unit Tests | |
| 5 | MS 4; Quality Assurance | MS 4 | |
| 6 | Quality Assurance | P13-14 | HW3: Refactoring |
| 7 | Quality Assurance; Exam | Midterm Exam (Th) | |
| 8 | ETS Test | HW4: Project Summary | |
| 9 | Human-Computer Interaction | P12, handouts | |
| 10 | MS 5; In-class test | MS 5 | |
| 11 | Project Management | P21,22,25 | HW5: Usability Test |
| 12 | Project Management; Résumé Review | HW6: Bug tracking system | |
| 13 | Code Review; Intellectual Property Law | HW7: Code Review | |
| 14 | Intellectual Property Law; In-Class Test | ||
| 15 | Public Demonstration; Exam Review | MS 6 (finished project) |
P: chapters in Pressman; F: chapters in Fowler. Schedule is subject to change.
Final Exam Section I: Thursday, May 3, 9:45 am - 11:45 am
Final Exam Section II: Friday, May 4, 2:15 pm - 4: 15 pm