Class notes Software project management (PE)

Software Project Management

LECTURE NOTES


–




DEPARTMENT OF
COMPUTER SCIENCE AND ENGINEERING




I

, –

SOFTWARE PROJECT MANAGEMENT
( Elective-I)
Objectives:
 Understanding the specific roles within a software organization as related to project and
process management
 Understanding the basic infrastructure competences (e.g., process modeling and
measurement)
 Understanding the basic steps of project planning, project management, quality assurance,
and process management and their relationships

UNIT-I
Conventional Software Management: The waterfall Model, Conventional Software
Management Performance,
Evolution of Software Economics: software Economics. Pragmatic Software Cost Estimation.
Improving Software Economics: Reducing Software Product Size, Improving Software
Processes, Improving Team Effectiveness, Improving Automation, Achieving Required Quality,
Peer Inspections.
UNIT-II
Conventional and Modern Software Management: Principles of Conventional Software
Engineering, Principles of Modern Software Management, Transitioning to an interactive
Process.
Life Cycle Phases: Engineering and Production Stages Inception, Elaboration, Construction,
Transition phases.
UNIT-III
Artifacts of the Process: The Artifact Sets. Management Artifacts, Engineering Artifacts,
Programmatic Artifacts.
Model Based Software Architectures: A Management Perspective and Technical Perspective.
UNIT-IV
Flows of the Process: Software Process Workflows. Inter Trans Workflows.
Checkpoints of the Process: Major Mile Stones, Minor Milestones, Periodic Status
Assessments.
Interactive Process Planning: Work Breakdown Structures, Planning Guidelines, Cost and
Schedule Estimating. Interaction Planning Process, Pragmatic Planning.
UNIT-V
Project Organizations and Responsibilities: Line-of-Business Organizations, Project
Organizations, and Evolution of Organizations.
Process Automation: Building Blocks, the Project Environment.
Project Control and Process Instrumentation: Server Care Metrics, Management Indicators,
Quality Indicators, Life Cycle Expectations Pragmatic Software



II

,TEXT BOOKS:

1. Walker Rayce, “Software Project Management”, 1998, PEA.
2. Henrey, “Software Project Management”, Pearson.

Reference Books:

1. Richard H.Thayer.” Software Engineering Project Management”, 1997, IEEE Computer
Society.
2. Shere K.D.: “Software Engineering and Management”, 1998, PHI.
3. S.A. Kelkar, “Software Project Management: A Concise Study”, PHI.
4. Hughes Cotterell, “Software Project Management”, 2e, TMH. 88 5. Kaeron Conway,
“Software Project Management from Concept to D


Outcomes:
At the end of the course, the student shall be able to:
 Describe and determine the purpose and importance of project management from the
perspectives of planning, tracking and completion of project
 Compare and differentiate organization structures and project structures.
 Implement a project to manage project schedule, expenses and resource with the
application of suitable project management tools




III

, INDEX

UNIT NO TOPIC PAGE NO

Conventional Software Management 01 - 06

I Evolution of Software Economics 07 - 10

Improving Software Economics 10 - 18

Conventional and Modern Software Management 19 - 23
II
Life cycle phases 24 - 28

Artifacts of the process 29 – 39
III
Model based software architectures 40 – 42

Work Flows of the process 43 – 47

IV Checkpoints of the process 48 – 52

Iterative Process Planning 52 – 60

Project Organizations and Responsibilities 61 – 63

V Process Automation 64 – 69

Project Control and Process Instrumentation 69 - 75




IV