HANDLED BY
Ms.k.CHITHARTHANI L/IT
Aim: To present the concept regarding how the sotware projects are
planned, monitored and controlled.
Objective:
To introduce the basic concepts regarding the software project.
To give the students an idea about the concept of conventional
software project management and modern software project
management.
To study the lifecycle phases and workflow of the software process.
To train the students in the concepts of how the defects are analysis
and how we prevent such defects.
To study the concept of software quality management.
To familiarize the students with the ideas COCOMO cost estimation
model.
CS1021 – SOFTWARE PROJECT MANAGEMENT
LTPC
3003
UNIT I FUNDAMENTALS 9
Conventional software management − Evolution of software economics -Improving
software economics − Conventional versus modern software project management.
UNIT II SOFTWARE MANAGEMENT PROCESS FRAMEWORK 9
Lifecycle phases − Artifacts of the process − Model based software architectures
−Workflows of the process − Checkpoints of the process.
UNIT III SOFTWARE MANAGEMENT DISCIPLINES 9
Iterative process planning − Organisation and responsibilities − Processautomation
−Process control and process instrumentation − Tailoring the process.
UNIT IV MANAGED AND OPTIMIZED PROCESS 9
Data gathering and analysis − Principles of data gathering −
Data gathering process −Software measures − Data analysis −
Managing software quality − Defect prevention.
UNIT V CASE STUDIES 9
COCOMO cost estimation model − Change metrics −
CCPDS-R.
TEXT BOOKS
1. Walker Royce, “Software Project Management - A Unified
Framework”,Pearson Education, 2004.
2. Humphrey Watts, “Managing the Software Process”, Addison
Wesley, 1989.
REFERENCES
1. Humphrey Watts, “Managing the Software Process”,
Addison Wesley, 1989.
2. Ramesh Gopalaswamy, “Managing Global Projects”, Tata McGraw
Hill,2001.
3. Bob Hughes and Mikecotterell, “Software Project
Management”,3rd Edition, Tata McGraw Hill, 2004.
The Old Way (Conventional SPM)
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 through Software Environments
Achieving Required Quality
Peer Inspections: A Pragmatic View
The Old Way and the New
The Principles of Conventional Software Engineering
The Principles of Modern Software Management
Transitioning to an Iterative Process
Life-Cycle Phases
Engineering and Production Stages
Inception Phase
Elaboration Phase
Construction Phase
Transition Phase
Artifacts of the Process
The Artifact Sets
Management Artifacts
Engineering Artifacts
Pragmatic Artifacts
Model-based software Architectures
Architecture: A Management Perspective
Architecture: A Technical Perspective
Workflows of the Process
Software Process Workflows
Iteration Workflows
Checkpoints of the Process
Major Milestones
Minor Milestones
Periodic Status Assessments
Iterative Process Planning
Work Breakdown Structures
Planning Guidelines
The Cost and Schedule Estimating Process
The Iteration Planning Process
Pragmatic Planning
Project Organizations andResponsibilities
Line-of-Business organizations
Project Organizations
Evolution Organizations
Process Automation
Tools: Automation Building Blocks
The Project Environment
Project Control and Process Instrumentation
The Seven Core Metrics
Management Indicators
Quality Indicators
Life-Cycle Expectations
Pragmatic Software Metrics
Metrics Automation
Tailoring the Process
Process Discriminants
Example: Small-Scale Project Versus Large-scale Project
Data gathering and analysis
COCOMO CASE STUDY
CHANGE METRICS CASE STUDY
CCPDS-R CASE STUDY
1.http://www.fairdene.com/picalculus/wor
kflow-is-just-a-pi-process.pdf
2.http://www.softstarsystems.com/overvie
w.htm
3.http://www.sei.cmu.edu/library/abstract
s/reports/94tr024.cfm
4.http://www.industry.siemens.com/topics
/global/en/process-
automation/Pages/Default.aspx
