Date: Tue, 14 Jan 1997 23:17:17 GMT Server: NCSA/1.4.1 Content-type: text/html Last-modified: Tue, 27 Aug 1996 18:52:32 GMT Content-length: 8802 CS 404/504 Software Project Management

CS 404-01/504-01

NTU SE-580-S

Software Project Management

Fall 96-97

http://www.cs.uidaho.edu/~billjunk/courses/cs482/cs482.html
Last updated: August 27, 1996

Computer Science Home Page Univ. of Idaho Home Page

Course Overview

Proposed Catalog Description:

Software Project Management (3 cr). Techniques for planning, organizing, scheduling, and controlling complex software system development and support projects.

Instructor:

William S. Junk, Computer Science Dept., University of Idaho, Moscow, ID 83844-1010
Telephone: 208-885-7530 / 800-824-2889
Fax: 208-885-6165 (alternate: 208-885-9052)
E-Mail: billjunk@cs.uidaho.edu

Prerequisites:

Undergraduates: CS 381 Software Engineering or CS 480 Individual Design Project or permission

Graduates: CS 581 Software Engineering Analysis or permission May be taken by non-computer science majors who have a basic understanding of how software should be developed.

Resources: Students must have the ability to communicate with the instuctor via e-mail and must have facilities to access the World Wide Web.

Goals:

Upon completion of this course participants should:

Textbooks:

Grading:

     Participation                10%
     Readings                     10%
     Exercises                    50%
     Individual Project           20%
     Final Exam                   10%

Undergraduate and graduate sections of the course are graded separately. Due to slightly different schedules, off-campus and on-campus sections are graded separately. The difference between the undergraduate and graduate versions is in the expected level of accomplishment. Because of additional academic study and work experience, graduate students should be able to provide greater insight and depth of discussion in all phase of their course work. Just as an example, my expectations for the amount of effort put into the individual project is substantially higher for graduate students: 5-10 pages for undergraduates, versus 15-20 pages for graduates.

Participation

All students are expected to make a regular contribution to the class. On-campus students should be prepared to offer their comments regarding material presented, ask interesting questions during class, and respond with good answers to questions asked in class. Calling to my attention a high quality article on a topic discussed in class, pointing out an interesting WWW site, relating a personal experience, etc. are encouraged. Off-campus students should also do these things and communicate with me on a regular basis using e-mail, fax, telephone, or mail. I'm particularly interested in hearing your perspective as practitioners. A meaningful contribution each week is considered a satisfactory level. A portion of some class sessions will be devoted to discussion and feedback based on questions and comments supplied from off-campus.

Term Project

The course also requires an approved term project that should be a practical application of some concept(s) studied in the coruse. The project is expected to be more extensive for graduate students than for undergraduates. For example you might base your project around preparation of a Software Project Management Plan that follows IEEE standards, review published literature on software risk assessment and prepare a report, or study software process metrics from your organizztion. You are expected to propose a topic and receive my approval before starting. Additional guidelines will be provided.

Assignment (exercises)

Several exercises will be assigned during the semester. Most of these will be individual assignments, however, one group assignment is anticipated.

Topical Outline

Computer Science Home Page Univ. of Idaho Home Page


WWW: http://www.cs.uidaho.edu/~billjunk/
e-mail: billjunk@cs.uidaho.edu