INDT315

CPTR560

Software Engineering

Winter 2000

Instructor:

Bill Wolfer Office: Located in Harrigan Hall, ph# 6024,

Home: 473-1141 (Please no calls after 9pm)

Introduction:

Advanced Software Engineering
A study of applied software product development issues, including requirement analysis, systems and software design methodologies, software-project planning models (e.g., COCOMO), implementation, testing and reuse, language, tool and hardware selection, software economics, productivity measurement, risk management, statistical process evaluation, and control.

Text Books

Pressman, Roger; Software Engineering a Practitioner's Approach, Fourth Edition; McGraw Hill
Gilb, Tom; Principles of Software Engineering Management Addison-Wesley Publishing Company
Brooks, Frederick; The Mythical Man-Month Addison-Wesley Publishing Company
Humphrey, Watts; introduction to the Personal Software Process Addison-Wesley Publishing Company

Class:

Attendance required (Refer to University Policies, To many missed classes could result in failure)
Participation in class expected, and recorded
Cheating (don't do it) refer to the University policies.

Topics:

Upon successful completion of this class, the student should be familiar with:

Interviewing (Analysis)

Design (ER diagrams, Data Flow diagrams, etc...)

Evolutionary model (Gilb)

Mythical Man Month (Brooks)

Quality Review

Teams

Testing

Maintenance

Measurements, quality, scope, cost

Personal Software Process (Humphrey)

Grades:

Grades will be based upon a percent system as follows:

Tests MT 20% Final 25%	45%	A	95 - 100
Watts.Humphrey 10% Tom Gilb 10% Fred Brooks 10%	30%	A-	90 -94
Readings (rpts) 10%	10%	B+	85 - 89
Attendance/ Participation Keep a Log of labs	5% Required 5% 5%	B	80 - 84
Note: these are guaranteed grades. Your instructor reserves the right to adjust the percentages downward.		B-	75 - 79
		C+	70 -74
		C	65 - 69
		C-	60 - 64
		D	55 - 59
		F	0 - 54

Rules to follow:

Assignments must be submitted on the date and time due if full credit is to be awarded.
No early examinations (not for plain tickets, not for spring break, etc...)
Students are responsible for all information covered in class, and in the book.
Assignments must be typed, 12pt font, double spaced, one inch margin, include a cover sheet. NO sloppy work will be graded.

Log.

You must keep a log of the time you spend in the lab working on the assignments.

Book Reports

Book reports must have.

Cover sheet

Typed, 12pt font, double space, 1 inch margins.

     One half page per chapter for each chapter in each book. Include Two Page Critique of each book.

                    Gilb             Due:

                    Brooks:       Due:

                    Humphrey   Due:

Reading Reports:

    Reading reports must have.

     Cover sheet

    One page Typed, 12pt font, double space, 1 inch margins.

    One half page Critique of article.

                    Due Beginning of each class period

                    Must be read form Software Engineering ACM or IEEE Software Engineering periodicals ONLY. If you have a specific                         article that you would like to include it must be Approved by your instructor first..

Tests

There are no make-up exams. The mid term will be announced at the appropriate time and the Final will be during test week as published in the class schedule. .