• Skip to main content
  • Skip to primary sidebar
  • Skip to secondary sidebar
  • Skip to footer

Computer Notes

Library
    • Computer Fundamental
    • Computer Memory
    • DBMS Tutorial
    • Operating System
    • Computer Networking
    • C Programming
    • C++ Programming
    • Java Programming
    • C# Programming
    • SQL Tutorial
    • Management Tutorial
    • Computer Graphics
    • Compiler Design
    • Style Sheet
    • JavaScript Tutorial
    • Html Tutorial
    • Wordpress Tutorial
    • Python Tutorial
    • PHP Tutorial
    • JSP Tutorial
    • AngularJS Tutorial
    • Data Structures
    • E Commerce Tutorial
    • Visual Basic
    • Structs2 Tutorial
    • Digital Electronics
    • Internet Terms
    • Servlet Tutorial
    • Software Engineering
    • Interviews Questions
    • Basic Terms
    • Troubleshooting
Menu

Header Right

Home » Software Engineering » Quantitative Process Management (QPM)
Next →
← Prev

Quantitative Process Management (QPM)

By Dinesh Thakur

Quantitative Process Management (QPM) aims to control the process performance (the actual output accomplished by following the software process) of the software project quantitatively. The quantitative process management establishes goals for the performance of the project’s software process. It involves measuring the performance of software process, analyzing these measurements, and making adjustments in maintaining the performance of the process. After the performance of the process is stable and within acceptable limits, the software process of the project and the associated measurements are established as a baseline. This results in controlling the performance of the software process quantitatively. The goals of quantitative process management are listed below.

  1. To plan the activities for quantitative management
  2. To control the process performance of the project’s defined software process quantitatively
  3. To identify the process capability of the organization standard software process in quantitative terms.

For QPM to work effectively and efficiently, various entry and exit criteria are defined. These, along with the tasks involved, are shown in Table.

                                       Table Quantitative Process Management

Entry

Tasks

Exit

  1. Policy for measuring and quantitatively controlling the performance of project-defined process.
  2. Policy for analyzing the process capability of the organization standard software process.
  3. Group exists for coordinating QPM.
  4. Adequate resources and funding.
  5. Training for individuals implementing or supporting QPM activities.
  6. Training for participants.
  7. Support for collecting, recording and analyzing data.
 

  1. Develop Project QPM plan.
  2. Perform the QPM plan.
  3. Determine a strategy for data collection and quantitative analysis based on project process.
  4. Collect measurement data to control project process.
  5. Prepare and distribute reports of QPM results.
  6. Establish and maintain the process capability baseline for the organization standard software process.
  7. Analyze the project’s process to bring it under quantitative control.
  1. QPM activities are planned.
  2. Project’s process performance is controlled quantitatively.
  3. Process capability of organization standard software process is known quantitatively.

After the outputs from the tasks are available, verification is done on the following basis.

  1. Reviews with senior management and project management
  2. Reviews/audits by software quality assurance
  3. Measurement of the status of QPM activities.

The organization follows a written policy for evaluating and quantitatively controlling the performance of the software process of the project. For this, various steps are followed, which are listed below.

  1. Each project implements a documented plan to bring the software process of the project under a quantitative control. The quantitative control refers to the quantitative technique, which is appropriate to analyze the software processes. It identifies a specific condition or a specific group of individuals performing in an unexpected manner.
  2. The sensitive data related to an individual’s performance is protected and access to this data is controlled. The measurement data is used to evaluate the individuals who intentionally affect the correctness and usefulness of the reported data.

You’ll also like:

  1. Explain Various Phases of Process Management
  2. Process Change Management (PCM)
  3. Explain Software Configuration Management Process
  4. Requirements Management Process in Software Engineering
  5. What are the Matrices, Measurements and Models of Project Management Process
Next →
← Prev
Like/Subscribe us for latest updates     

About Dinesh Thakur
Dinesh ThakurDinesh Thakur holds an B.C.A, MCDBA, MCSD certifications. Dinesh authors the hugely popular Computer Notes blog. Where he writes how-to guides around Computer fundamental , computer software, Computer programming, and web apps.

Dinesh Thakur is a Freelance Writer who helps different clients from all over the globe. Dinesh has written over 500+ blogs, 30+ eBooks, and 10000+ Posts for all types of clients.


For any type of query or something that you think is missing, please feel free to Contact us.


Primary Sidebar

Software Engineering

Software Engineering

  • SE - Home
  • SE - Feasibility Study
  • SE - Software
  • SE - Software Maintenance Types
  • SE - Software Design Principles
  • SE - Prototyping Model
  • SE - SRS Characteristics
  • SE - Project Planning
  • SE - SRS Structure
  • SE - Software Myths
  • SE - Software Requirement
  • SE - Architectural Design
  • SE - Software Metrics
  • SE - Object-Oriented Testing
  • SE - Software Crisis
  • SE - SRS Components
  • SE - Layers
  • SE - Problems
  • SE - Requirements Analysis
  • SE - Software Process
  • SE - Software Metrics
  • SE - Debugging
  • SE - Formal Methods Model
  • SE - Management Process
  • SE - Data Design
  • SE - Testing Strategies
  • SE - Coupling and Cohesion
  • SE - hoc Model
  • SE - Challenges
  • SE - Process Vs Project
  • SE - Requirements Validation
  • SE - Component-Level Design
  • SE - Spiral Model
  • SE - RAD Model
  • SE - Coding Guidelines
  • SE - Techniques
  • SE - Software Testing
  • SE - Incremental Model
  • SE - Programming Practices
  • SE - Software Measurement
  • SE - Software Process Models
  • SE - Software Design Documentation
  • SE - Software Process Assessment
  • SE - Process Model
  • SE - Requirements Management Process
  • SE - Time Boxing Model
  • SE - Measuring Software Quality
  • SE - Top Down Vs Bottom UP Approaches
  • SE - Components Applications
  • SE - Error Vs Fault
  • SE - Monitoring a Project
  • SE - Software Quality Factors
  • SE - Phases
  • SE - Structural Testing
  • SE - COCOMO Model
  • SE - Code Verification Techniques
  • SE - Classical Life Cycle Model
  • SE - Design Techniques
  • SE - Software Maintenance Life Cycle
  • SE - Function Points
  • SE - Design Phase Objectives
  • SE - Software Maintenance
  • SE - V-Model
  • SE - Software Maintenance Models
  • SE - Object Oriented Metrics
  • SE - Software Design Reviews
  • SE - Structured Analysis
  • SE - Top-Down & Bottom up Techniques
  • SE - Software Development Phases
  • SE - Coding Methodology
  • SE - Emergence
  • SE - Test Case Design
  • SE - Coding Documentation
  • SE - Test Oracles
  • SE - Testing Levels
  • SE - Test Plan
  • SE - Staffing
  • SE - Functional Testing
  • SE - Bottom-Up Design
  • SE - Software Maintenance
  • SE - Software Design Phases
  • SE - Risk Management
  • SE - SRS Validation
  • SE - Test Case Specifications
  • SE - Software Testing Levels
  • SE - Maintenance Techniques
  • SE - Software Testing Tools
  • SE - Requirement Reviews
  • SE - Test Criteria
  • SE - Major Problems
  • SE - Quality Assurance Plans
  • SE - Different Verification Methods
  • SE - Exhaustive Testing
  • SE - Project Management Process
  • SE - Designing Software Metrics
  • SE - Static Analysis
  • SE - Software Project Manager
  • SE - Black Box Testing
  • SE - Errors Types
  • SE - Object Oriented Analysis

Other Links

  • Software Engineering - PDF Version

Footer

Basic Course

  • Computer Fundamental
  • Computer Networking
  • Operating System
  • Database System
  • Computer Graphics
  • Management System
  • Software Engineering
  • Digital Electronics
  • Electronic Commerce
  • Compiler Design
  • Troubleshooting

Programming

  • Java Programming
  • Structured Query (SQL)
  • C Programming
  • C++ Programming
  • Visual Basic
  • Data Structures
  • Struts 2
  • Java Servlet
  • C# Programming
  • Basic Terms
  • Interviews

World Wide Web

  • Internet
  • Java Script
  • HTML Language
  • Cascading Style Sheet
  • Java Server Pages
  • Wordpress
  • PHP
  • Python Tutorial
  • AngularJS
  • Troubleshooting

 About Us |  Contact Us |  FAQ

Dinesh Thakur is a Technology Columinist and founder of Computer Notes.

Copyright © 2025. All Rights Reserved.

APPLY FOR ONLINE JOB IN BIGGEST CRYPTO COMPANIES
APPLY NOW