Cover image for Process-based software project management
Title:
Process-based software project management
Personal Author:
Publication Information:
Boca Raton, FL : Auerbach Publications, 2006
ISBN:
9780849373046

Available:*

Library
Item Barcode
Call Number
Material Type
Item Category 1
Status
Searching...
30000010121056 QA76.76.D47 G66 2006 Open Access Book Book
Searching...
Searching...
30000010207869 QA76.76.D47 G66 2006 Open Access Book Book
Searching...

On Order

Summary

Summary

Not connecting software project management (SPM) to actual, real-world development processes can lead to a complete divorcing of SPM to software engineering that can undermine any successful software project. By explaining how a layered process architectural model improves operational efficiency, Process-Based Software Project Management outlines a new method that is more effective than the traditional method when dealing with SPM.

With a clear and easy-to-read approach, the book discusses the benefits of an integrated project management-process management connection. The described tight coupling of the process world to the SPM world provides a high degree of completeness and accuracy necessary for effective project management. The author shows you that this process-based approach to SPM increases product quality, shortens time-to-market, reduces life cycle costs, facilitates short system test times, and increases developmental supply chain management (SCM) controls and total repeatability. This underlying process approach also actively involves SCM, software quality assurance (SQA), engineering, and accounting as part of your integrated SPM team for total success.

Through examples and detailed explanations, Process-Based Software Project Management illustrates how this novel SPM approach is more profitable and time-efficient when compared to traditional SPM methods. The software manager, along with the support team, will finally all be on "the same page" to achieve SPM/engineering success.


Author Notes

Goodman, F. Alan


Table of Contents

List of Figuresp. xi
List of Tablesp. xv
About the Authorp. xvii
Prefacep. xix
Introductionp. xxi
Section I Essence of Software Project Management
1 The Software Project Management Big Picturep. 3
Introductionp. 3
Pre-execution Efforts for Government Contractorsp. 5
Pre-execution Efforts for Commercial Companiesp. 12
Execution Efforts for Bothp. 13
2 Planning and Tracking: The Big Picturep. 17
Introductionp. 17
Proposal-Time Planningp. 19
The Software Project Schedulep. 21
The Project Management Plan (PMP) Documentp. 26
Planning the Software Projectp. 27
Traditional Conversion of Planning Packages to Work Packagesp. 28
Tracking the Software Projectp. 30
Section II Process Framework Architecture
3 Process Overviewp. 37
Introductionp. 37
The Software Process Framework Model Overviewp. 46
4 Life-Cycle Mappingp. 51
Introductionp. 51
Life-Cycle Web Representationp. 53
Life Cycle/Schedule Connectionp. 59
Life-Cycle/Event-Driven Procedure Connectionp. 61
5 The Process Activityp. 63
Introductionp. 63
Activity Implementationp. 67
6 Special Process Activities for Software Project Managementp. 77
Introductionp. 77
SCM Actionsp. 79
Accounting Actionsp. 83
Engineering Development Actionsp. 85
SPM Actionsp. 87
Section III Institutionalization Considerations
7 Process Framework Model Institutionalizedp. 91
Introductionp. 91
Process Repository Institutionalizedp. 92
Script Programming Institutionalizedp. 96
Inspection Procedure Institutionalizedp. 98
Inspection Checklists Institutionalizedp. 102
Activity Estimations Institutionalizedp. 104
8 Work Breakdown Structure and Charge Numbers Institutionalizedp. 107
Introductionp. 107
WBS Institutionalizedp. 108
Charge Number Institutionalizedp. 116
9 Software Project Management Role Partners Institutionalizedp. 125
Introductionp. 125
Engineering Role Partner Institutionalizedp. 128
Accounting Role Partner Institutionalizedp. 129
SCM Role Partner Institutionalizedp. 130
SPM Role Partner Institutionalizedp. 131
SQA Role Partner Institutionalizedp. 132
Section IV Pre-Execution Segment
10 Preproposalp. 135
Introductionp. 135
Using the Process for Pre-execution Directionp. 139
11 Proposalp. 143
Introductionp. 143
Proposal Repositoryp. 149
Requirementsp. 150
Other Considerationsp. 157
Section V Execution Segment
12 Project Setupp. 167
Introductionp. 167
Process Basisp. 168
Repositoriesp. 172
Charge Numbersp. 174
Planning Schedulep. 179
13 Planning up to Designp. 185
Introductionp. 185
Contract Schedule Items Planningp. 186
Target-System Schedule Items Planningp. 186
14 Planning after Designp. 191
Introductionp. 191
Planning "Design Down (System)"p. 191
Planning "Design Down (Subsystem A)"p. 196
Planning "Update Integration Plan (Subsystem A)"p. 200
Planning "Design Down (Subsystem B)"p. 201
Planning "Update Integration Plan (Subsystem B)"p. 203
Other Planning Considerationsp. 206
15 Project Trackingp. 213
Introductionp. 213
Planning Packagesp. 214
Activity Trackingp. 216
SCM-Based Trackingp. 219
Rework Trackingp. 220
16 Project Closedownp. 223
Introductionp. 223
Repositories on Closedownp. 224
Metrics Collection on Closedownp. 225
Post Mortem on Closedownp. 229
Indexp. 235