Process-Based Software Project Management

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, Pr...

Mô tả đầy đủ

Đã lưu trong:
Chi tiết về thư mục
Định dạng: Sách
Ngôn ngữ:English
Được phát hành: CRC Press 2009
Truy cập trực tuyến:http://scholar.dlu.edu.vn/thuvienso/handle/DLU123456789/1470
Các nhãn: Thêm thẻ
Không có thẻ, Là người đầu tiên thẻ bản ghi này!
Thư viện lưu trữ: Thư viện Trường Đại học Đà Lạt
id oai:scholar.dlu.edu.vn:DLU123456789-1470
record_format dspace
institution Thư viện Trường Đại học Đà Lạt
collection Thư viện số
language English
description 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.
format Book
title Process-Based Software Project Management
spellingShingle Process-Based Software Project Management
title_short Process-Based Software Project Management
title_full Process-Based Software Project Management
title_fullStr Process-Based Software Project Management
title_full_unstemmed Process-Based Software Project Management
title_sort process-based software project management
publisher CRC Press
publishDate 2009
url http://scholar.dlu.edu.vn/thuvienso/handle/DLU123456789/1470
_version_ 1757668676578836480
spelling oai:scholar.dlu.edu.vn:DLU123456789-14702009-12-02T09:17:33Z Process-Based Software Project Management 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. SECTION I: ESSENCE OF SOFTWARE PROJECT MANAGEMENT THE SOFTWARE PROJECT MANAGEMENT BIG PICTURE Introduction Pre-Execution Efforts for Government Contractors Pre-Execution Efforts for Commercial Companies Execution Efforts for Both PLANNING AND TRACKING: THE BIG PICTURE Introduction Proposal-Time Planning The Software Project Schedule The Project Management Plan (PMP) Document Planning the Software Project Traditional Conversion of Planning Packages to Work Packages Tracking the Software Project SECTION II: PROCESS FRAMEWORK ARCHITECTURE PROCESS OVERVIEW Introduction The Software Process Framework Model Overview LIFE-CYCLE MAPPING Introduction Life-Cycle Web Representation Life Cycle/Schedule Connection Life-Cycle/Event-Driven Procedure Connection THE PROCESS ACTIVITY Introduction Activity Implementation SPECIAL PROCESS ACTIVITIES FOR SOFTWARE PROJECT MANAGEMENT Introduction SCM Actions Accounting Actions Engineering Development Actions SPM Actions SECTION III: INSTITUTIONALIZATION CONSIDERATIONS PROCESS FRAMEWORK MODEL INSTITUTIONALIZED Introduction Process Repository Institutionalized Script Programming Institutionalized Inspection Procedure Institutionalized Inspection Checklists Institutionalized Activity Estimations Institutionalized WORK BREAKDOWN STRUCTURE AND CHARGE NUMBERS INSTITUTIONALIZED Introduction WBS Institutionalized Charge Number Institutionalized SOFTWARE PROJECT MANAGEMENT ROLE PARTNERS INSTITUTIONALIZED Introduction Engineering Role Partner Institutionalized Accounting Role Partner Institutionalized SCM Role Partner Institutionalized SPM Role Partner Institutionalized SQA Role Partner Institutionalized SECTION IV: PRE-EXECUTION SEGMENT PREPROSAL Introduction Using the Process for Pre-Execution Direction PROPOSAL Introduction Proposal Repository Requirements Other Considerations SECTION V: EXECUTION SEGMENT PROJECT SETUP Introduction Process Basis Repositories Charge Numbers Planning Schedule PLANNING UP TO DESIGN Introduction Contract Schedule Items Planning Target-System Schedule Items Planning PLANNING AFTER DESIGN Introduction Planning "Design Down (System)" Planning "Design Down (Subsystem A)" Planning "Update Integration Plan (Subsystem A)" Planning "Design Down (Subsystem B)" Planning "Update Integration Plan (Subsystem B)" Other Planning Considerations PROJECT TRACKING Introduction Planning Packages Activity Tracking SCM-Based Tracking Rework Tracking PROJECT CLOSEDOWN Introduction Repositories on Closedown Metrics Collection on Closedown Postmortem on Closedown 2009-12-02T09:17:33Z 2009-12-02T09:17:33Z 2006 Book http://scholar.dlu.edu.vn/thuvienso/handle/DLU123456789/1470 en application/rar CRC Press