Introduction to Software Engineering

CS 3302 Section A Fall 1998

General Information

CS 3302. Introduction to Software Engineering

3-3-4. Prerequisites: CS 2201 or one of the following: CS 2360, CS 2390, 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.

Up to this point, it is expected that students have primarily worked on relatively small (<= 1KLOC, i.e., individual effort) projects. Since very few successful software projects are the result of individual efforts, this class is intended to give the students a feeling for the issues involved in "group" software development efforts.

Jump to the syllabus for the quarter (download)

Jump to the class newsgroup.

Instructor: Dr. Bill McKinnon

• Office: 248 GCATT (250 14th St.)
• Phone: (404) 894-8806
• Email: b.mckinnon@ieee.org or bill.mckinnon@gtri.gatech.edu
• Office Hours: Generally open (from 9am until later than I would like to admit), but appointments are strongly recommended (I won't be held responsible if I am working somewhere else when you "drop by")

Teaching Assistant: Ms. Lily L. Pan

• Office: CoC 154
• Phone: (404) 894-2573
• Email: lipan@cc.gatech.edu
• Office Hours: Thursdays, 3:15pm-4:15pm

Textbooks

Other references

Software Engineering: A Practitioner's Approach by Pressman
Abstraction and Specification in Program Development by Liskov and Guttag
Strategies for Real-Time System Specification by Hatley and Pirbhai

Fair warning: I am a strong advocate of Object Oriented Analysis and Design techniques.  While OOA&D will not be formally covered in detail in this class, OOA&D may be helpful to groups who are familiar with OO languages and who are interested in possibly using their work in this course in the future.  The following references are recommended.

Object-Oriented Modeling and Design by Rumbaugh, et al.
Object Oriented Analysis and Design with Applications (2nd ed.) by Booch
Object-Oriented Software Engineering: A Use Case Approach by Jacobsen, et al.
Objects, Components, and Frameworks with UML: The Catalysis Approach by D'Souza & Wills

More books may be added as the course progresses.

Grade Division

There will be a group project as a part of this class.  It is currently planned that 7 teams of 7 people each (approximately) will be formulated to work together; after Drop Day, at least a minimal reorganization of teams will likely occur.  The project grades will be computed as shown in the following table.  Once a deliverable is graded once, it may be resubmitted within one week to the TA for re-grading (out of 90%).
 

	% of Project Grade	Notes
Project Completion	0%	Satisfaction of Requirements
Individual Deliverables	50%/# deliv's (1 deliv. min.)
Presentation, Demonstration, & Technical Report	25%	Must include design presentation (a deliverable for Architects) and documented source code (a deliverable for Implementers)
Peer Evaluation	25%	Mandatory; 50% of this grade is for completing an evaluation of one's peers; the remainder is based on your peers' evaluations of you
Instructor's Discretion	(+/- 20%)	Based on my judgment, I may award or penalize individuals +/- 20% of this grade.

Class attendance is not mandatory.  I do not care where you spend your time, as long as you get your work done (much as your manager will probably be in "the real world").  However, in the same breath, notice that I am not very tolerant of missed deadlines (as your manager will definitely not be in "the real world").  Prior notification of interviews and immediate notification of emergency situations will be mandatory for rescheduled events.

Syllabus