You are on page 1of 3

SYLLABUS

CS 6388: Software Project Planning and Management


SPRING, 2005
MW @ 7:00-8:45 pm - ES 2.410

Instructor: Joseph A. Leubitz


Office: ES 3.705 Phone: (972) 883-2854
Hours: MW 3:30-5:30 pm
E-mail: jleubitz@utdallas.edu Web Site: www.utdallas.edu/~jleubitz

Course Description
Techniques and disciplines for successful management of software projects. Planning, scheduling,
tracking, cost and size estimation, configuration management and version control. Benefits and pitfalls of
both conventional and emerging technologies.

Course Objective
In this course students will learn how to:
• Develop a software project plan.
• Estimate the cost of a software project.
• Plan and control a software project.
• Define or use the right software process.
• Establish and monitor an Quality Assurance program
• Understand software contracts.
• Perform a risk analysis.

Grading: Assignments ................................................ 10%


Project ......................................................... 30%
Midterm Exam............................................. 30%
Final Examination........................................ 30%
• Highest student score in each test will become the divisor to determine individual score; final class
weighted score, and class grade curve.
• Any missing scores will be given a zero grade in the calculation of a course grade. Late
homework or project reports will get half credit. Incomplete grades will not be issued.

Student Responsibilities
• You are responsible for checking your UTD e-mail box, WebCT, and my web site on a weekly
basis. If you do not receive a notice or an assignment that I place there, you must suffer any
resulting consequences.
• Although I do not regularly take attendance, regular class attendance and participation are
expected. Students are responsible for lectures and announcements they miss. Quizzes may not
be made-up.
• Teamwork & collaboration are encouraged, but identical homework is not acceptable. Cheating
will be prosecuted through UTD’s disciplinary procedures.
• Student IDs will be required for the exams.
• All UTD student conduct policies and standards will be in effect.

Revised 2/24/2005 Page 1


CS 6388: Software Project Planning and Management Page 2

Textbook:
• Harold Kerzner, Project Management: A Systems Approach to Planning, Scheduling and
Controlling, 8/e (John Wiley & Sons, 2003), ISBN: 0471225770.

Web Sites:
• IEEE Std 1058-1998, IEEE Standard for Software Project Management Plans:
http://shop.ieee.org/store/product.asp?prodno=SH94690
• Chambers & Associates Pty, Concept: Work Breakdown Structure
http://www.chambers.com.au/Sample_p/wbs_cncp.htm
• PERT/CPM/Crashing:
(Lindo Systems) http://www.lindo.com/pertcpm4.pdf
• CoCoMo II.2000
http://sunset.usc.edu/research/COCOMOII/docs/C2ASE_submijtted.pdf
http://www.softstarsystems.com/overview.htm
• International Function Point Users Group: http://www.ifpug.org
• Software Configuration Management:
(Estublier) http://www.cs.ucl.ac.uk/staff/A.Finkelstein/fose/finalestublier.pdf
http://www.sei.cmu.edu/legacy/scm/
http://www.merant.com/PVCS/
http://www-306.ibm.com/software/rational/offerings/scm.html

Additional Readings:
• Barry Boehm, Software Cost Estimation with COCOMO II (Prentice Hall, 2000),
ISBN: 0130266922.
• Carl S. Chatfield & Timothy D. Johnson, Microsoft Project Version 2002 Step by Step (Microsoft
Press, 2002), ISBN: 073561301X.
• Roy J. Lewicki, David M. Saunders, Bruce Barry, & John W. Minton, Essentials of Negotiation,
3rd Ed. (McGraw-Hill/Irwin, 2004), ISBN: 0-07-254582-8.
• Project Management Institute, Guide to the Project Management Body of Knowledge, 2000 Ed.
(PMI, 2001), ISBN: 1880410230
• Joc Sanders and Eugene Curran, Software Quality: A Framework for Success in Software
Development and Support (Addison Wesley, 1994) ISBN: 0201631989.

Revised 2/24/2005 Page 2


Schedule
CS 6388: Software Project Planning and Management

Text Readings
Class Date Topics Kerzner unless noted
1 Jan. 10 Introduction Ch. 1
Outline of Course Activities and Events.
2 Jan. 12 Defining the Software Process
Jan. 17 MLK Day (NO CLASS)
3 Jan. 19 Team formation and team building In class Exercise
4 Jan. 24 Organization & Structure Ch. 3-4
5 Jan. 26 Management Functions/Movitation Ch. 5
Homework #1*
6 Jan. 31 Planning Ch. 11
Homework #2*
7-8 Feb. 2-7 Network Scheduling Techniques Ch. 12
Homework #3*
9-10 Feb. 9-14 Pricing and Estimating Ch. 14
Boehm, Ch. 5 (Opt.)
Homework #4*
Microsoft Project Microsoft (Optional)
11 Feb. 16 Review Project Report #1 Due
12 Feb. 21 Midterm Exam
13 Feb. 23 Group Status Meetings
14 Feb. 28 Project Control and Status Reporting Ch. 15
Homework #5*
15 March 2 Risk Management Ch. 17
March 7-9 Spring Break – NO CLASS
16 March 14 Software Quality Assurance Ch. 20
Sanders & Curran,
Section 3 (Optional)
Software Configuration Management Estublier (Optional)
17 March 16 Concurrent Engineering (Crashing, Fast Track, RAD) Lindo (Optional)
Homework #6*
18 March 21 Contracting & Procurement Ch. 21
19 March 23 Conflict Management Ch. 7
Project Report #2 Due
20 March 28 Negotiations Lewicki (Optional)
21 March 30 How to Give a Great Presentation Using PowerPoint
22 April 4 TBA
23 April 6 PMI, PMP, CAPM PMBOK (Optional)
24-27 April 11-20 Project Presentations
28 April 25 Review
May 2 @ 7:00 pm Final Exam

Schedule is subject to change and additional material may be added in class as time permits.

* Homework assignments are due at the next class.

Revised 2/24/2005 Page 3

You might also like