cse 7315 - sw project management copyright © 1995-2002, dennis j. frailey, all rights reserved...

January 12, 2002

CSE 7315 - SW Project Management Copyright © 1995-2002, Dennis J. Frailey, All Rights Reserved

Slide 1CSE7315M00

SMU CSE 7315 / NTU SE 584-N

Planning and Managing a Software Project

Module 00• Administrative Details• Overview of the Course

January 12, 2002


Slide 2CSE7315M00

Administrative Details

CSE 7315 - SW Project Management Copyright © 1995-2002, Dennis J. Frailey, All Rights Reserved CSE7315M00

January 12, 2002

Dennis J. FraileyAdjunct Professor - SMU

Office: 972-344-8366Fax: 972-344-7701e-MAIL: [email protected] page: http:// www.seas.smu.edu/~frailey/


January 12, 2002

Dennis J. FraileyPrincipal Fellow - Raytheon CompanyPhD Purdue, 1971, Computer Science

Assistant Professor, SMU, 1970-75Associate Professor, SMU, 1975-77

(various titles), Texas Instruments, 1974-1997(now Raytheon Co. 1997-)

Adjunct Associate Professor, UT Austin, 1981-86Adjunct Professor, SMU, 1987-present

-----Areas of specialty: software engineering process,

compiler design, operating system design, real-time system design, computer architecture


January 12, 2002

Grader• The grader is: Byron Howard• Email:

[email protected]• Phone: (214) 768-2854• Fax: (214) 768-3085• Office: #300C, SIC


January 12, 2002

SMU - Department ofComputer Science and Engineering

_Secretary: Debra McDowell -- 214-768-3080e-mail: [email protected]

(handouts, paperwork, grades etc.)________________________________________________________________________________________________________________

Administrative Assistant: Beth Minton -- 214-768-3083e-mail: [email protected]

(backup)


January 12, 2002

Meeting TimesCourse Meets at SMU’s

Main Campus inCaruth Hall, Room 218

Class Time: Sat, 9:00-noonJanuary 12th - April 27thFinal Exam Due: May 4

____________________________________________________________________

Tape and NTU students add a delay equal to the delay in their receiving of the course

tapes.


January 12, 2002

Correspondence by Mail• For normal mail delivery, use:

Southern Methodist UniversityComputer Science and Engineeringattn: Grader, CSE7315P. O. Box 75275-0122Dallas TX 75275-0122• For overnight mail delivery, use:

Southern Methodist UniversityComputer Science and Engineeringattn: Grader, CSE73156425 AirlineDallas TX 75275


January 12, 2002

Course Structure• Thirteen lecture sessions plus two

examination sessions:– Midterm Exam– Final Exam

• Thirty Nine 50-minute Modules– M00 through M38– Each session covers three modules


January 12, 2002

Nominal Class PatternThree Modules per Session

Lecture 9:00-9:50 50 minBreak9:50-10:00Lecture 10:00-10:50 50 minBreak10:50-11:00Lecture 11:00-11:50 50 minTOTAL 150 minutes


January 12, 2002

Exams

Midterm Approx. March 2 25% of gradeFinal Approx. May 4 25% of grade

Assignments(see separate handouts for more details)

1 Alternative Lifecycle 2% of grade2 First draft of SDP advisory grade3 Size Spreadsheet 13% of grade4 Cost Spreadsheet 10% of grade5 Complete SDP 25% of gradeOther ~1% of grade


January 12, 2002

Course Web Site• Frailey Home Page: http://www.seas.smu.edu/~frailey/• Course Home Page: http://www.seas.smu.edu/~frailey/cse7315.html

Download all handouts, assignments, and class notes from the course web site.

Start at the home page and follow instructions.


January 12, 2002

Course Notes• Powerpoint® 97 format• Module names are:

CSE7315M00P97.ppt, CSE7315M01P97.ppt, etc. through M38– .zip versions are zip files (smaller)

• zip files with complete set of modules: CSE7315P97.zip

Powerpoint® is a trademark of Microsoft Corporation


January 12, 2002

Course Handouts• Microsoft Word 97 format• Assignment Handouts:– A “statement of work” for each assignment– “Statement of Work for Software

Development Plan” applies to assignments 2-5 and is the major assignment for the course

• General Handouts:– Syllabus, etc.


January 12, 2002

Course Notes and HandoutsDownload from Web

• connect to http://www.seas.smu.edu/~frailey/• select “CSE 7315”• select “this link” under “Registered Students”• follow instructions for this specific offering of the course

(Spring, 2002)• select an individual item to download to your computer• zip files contain groups of items and are the fastest way

to download


January 12, 2002

Download From FTP Sitevia Web Browser

• connect to:ftp://ftp.engr.smu.edu/course/cse7315/2002Spring• select items of interest• your browser may offer different options,

such as “open”, “download”, etc. –Always download and, if given a choice, select

binary–Sometimes, ppt files do not download correctly• you may need to try different methods• or download the zip files


January 12, 2002

Download Directly via FTP• From a “Dos” or “Command” prompt or

Unix system or whatever:ftp ftp.engr.smu.eduName anonymousPassword <enter your e-mail address>ftp> cd class/cse7315/2002Springftp> binaryftp> get <file name>ftp> bye


January 12, 2002

A Note about Class Notes• The files use some fonts and other

features that may not work on your computer–you may need to adjust fonts or copy

down material during lectures

• Hard copy can be in black and white or color. Looks OK either way.


January 12, 2002

SMU Graduate Program In Software Engineering4 core courses

–Cse 7312 : systems engineering–Cse 7313 : software requirements and design–Cse 7314 : software testing and quality assurance–Cse 7315 : software project planning & management

6 preferred electives (choose any 3)–Cse 8312 : software generation and maintenance–Cse 8313 : object oriented analysis and design methodology–Cse 8314 : software metrics and quality engineering–Cse 8315 : sw acquisition practices, legal & economic issues–Cse 8316 : user interface design–Cse 8317 : software reliability and safety–Cse 8340 : advanced topics in software engineering

3 free electives (choose any 3 approved graduate courses in CS or other related subjects)


January 12, 2002

Rules for Students in the Classroom

• Arrive on time• Select a seat away from the door so

latecomers will not distract• If you arrive late, open and close the

door quietly• Come back on time from breaks!• If you have a question, use the

microphone – Turn it on first!– Keep it off when not in use

January 12, 2002


Slide 21CSE7315M00

Overview of the Course


January 12, 2002

The Course

• The Course is focused on the PROCESS by which software is developed and managed

• The Management Principles taught are designed to work with the process

Software Risk Management

Software Project Management

Software Engineering Process


January 12, 2002

• People - Those who perform the software development

• Methods and Procedures -- How we do the work– Design methods, testing procedures,

configuration control, etc.

Other Elements of Software Project Management


January 12, 2002

• Resources - What we need to do the work– Computers, Software, Test Equipment,

Facilities, etc.• Artifacts - Things produced during the

course of the work• Communication - Within and without

Other Elements of Software Project Management


January 12, 2002

The Course Combines These Elements

• Planning what to do • Managing project execution• Improving the way we do

things


January 12, 2002

Planning What to Do• Understanding the customer &

requirements• Organizing for success• Selecting the lifecycle and the process• Work breakdown structure• Estimating the effort, size, and

schedule• Documenting the plans

The major assignment in the course is to develop a plan for a typical software project.


January 12, 2002

Managing Project Execution• Setting the right framework• Identifying and managing risk• Measuring to monitor progress and risk• Managing the configuration• Revising and updating plans

Managing execution is like piloting a ship:• Midcourse corrections to keep things

going in the right direction• Knowing how to responding effectively to

changes or adverse conditions


January 12, 2002

Improving the Way We Do Things

• Quality engineering– Building quality into the product– Minimizing the costs of poor quality

• Rework• Customer dissatisfaction• Loss of business

• Continuous process improvement– Studying how we do our jobs and

looking for better ways


January 12, 2002

Warning from Dilbert“... the biggest obstacle to the success of any project is management itself.”“... management ... will support [the project] in the following ways:

• Demand frequent status reports ... to explain why the team doesn’t have enough time to meet deadlines ...”

Adams, The Dilbert Principle


January 12, 2002

Student Assignments

# Description % of Grade1 Find an example of an alternative lifecycle model 2%2 Draft of SW Development Plan (see SOW) (*)3 Size Estimation Spreadsheet 13%4 Cost Estimation Spreadsheet 10%5 Research paper or SDP (see SOW) 25%

(*) Assignments 2 and 5 are combined into one grade.

See Assignment Delivery Schedule for your section or offering of the course for exact due dates for each assignment


January 12, 2002

SW Development Plan (SDP)• Write a SW Development Plan• For the “Mr. Television” Project– Project Organization– Software Development Process– Etc, etc.

• Goal: To apply what was learned in the course to a typical project– Identify key issues – Plan the project– Define risk management and metrics– etc.


January 12, 2002

Statement of Work (SOW)for SDP• Tasks:

– Study the topics of the course and complete corresponding portions of the Plan

– Submit a draft of the first part of the Plan (Assignment 2) by the middle of the course

– Complete major appendices to the Plan (Assignments 3 and 4)

– Complete the Plan during the remainder of the course– Submit to professor (Assignment 5) on the last day of class

• Deliverable:– Plan, in specified format


January 12, 2002

Maxim

• Start on the Plan right away• The second half of the course

involves a lot more homework assignments

The sooner you get behind, the longer you have to catch

up.


January 12, 2002

Requirements for Plan• Size: 30-50 pages for body• 1 1/2 space (leave room between lines

for comments and such)• Approach and Format: See the SOW• Number all pages


January 12, 2002

Books & Notes• This course has one textbook• And several reference books• There is no single book that covers

all of the material• You must take good notes• Preprinted class notes are not a

substitute for taking good written notes!


January 12, 2002

TextbookHumphrey, Watts. Managing the Software Process. Reading, Mass.: Addison-Wesley Publishing Company, 1989. ISBN 0-201-18095-2.

(This is the classic book on the subject. Ed Yourdon recommends as a “must buy” for software developers.)


January 12, 2002

Reference Books & PapersSee syllabus


January 12, 2002

Summary of Module• The course covers the tasks

needed to plan and manage a software project

• The course project is to develop a Software Development Plan, applying what is learned in the course


January 12, 2002

END OFMODULE 00

cse 7315 - sw project management copyright © 1995-2002, dennis j. frailey, all rights reserved...

Documents