Maisqual Quality Model

From Maisqual Private Wiki

Jump to: navigation, search

Contents

[edit] Introduction: Why a model?

[edit] Different quality models for different projects

Software projects cannot be compared all together. The attributes of quality we observe will definitely depend on many criteria: application domain, criticality of the service offered, or targeted public. For that reason, a single quality model would be misleading. We will rather consider sort-of specific profiles that mask some components of a generic quality model.

Published and internal software projects cannot be compared, because their model


[edit] Existing Quality Models

Several models exist for product quality and process performance.

Note that for project quality there is a real gap in the litterature, as observed by Stephen H. Kan[1].


[edit] The Maisqual Quality Model

Maisqual Quality Model architecture.png

[edit] Product Quality

This model targets the release outcome of the project: software and documentation.

It is mainly inspired from the ISO 9126 and ISO SQuaRE standards, but also from research papers on quality models.

[edit] Process Performance

This model evaluates the performance of the project process, as defined in the following Key Process Areas:

  • Project Management
    • Contracts Management
    • Integrated Project Management
    • Project Monitoring and Control
    • Project Planning
    • Risk Management
  • Communication
    • Developer mailing list of forum
    • User mailing list or forum
    • User involvement
    • User reporting
    • Management reporting
  • Build & Release Management
  • Configuration Management
  • Change Management
  • Developer Base
  • Measurement & Analysis
  • Requirements Management
  • Test Management

[edit] Charisma

We define charisma as the attributes of quality that are directly related to the user context. They are clearly distinct from product or process characteristics and rather measure how the world around has received the software. It includes usage (do people use it?) and popularity (do people like it?).

These characteristics are not easy to measure, as they heavily rely on human interactions and personalities.

[edit] Community

We define community as the attributes of quality that are neither part of the product or the process and still play an important role for users satisfaction. It includes support (how users requests regarding information, enhancements and defects are handled), communication (are users well informed of the evolution of product, etc.), learnability (are there a lot of resources on the world wide web, are there customer customisations or themes available, etc.), and continuity (is there a lot of users, is there some kind of guarantee that the software will be supported, etc.).


[edit] References

  1. See section "16.2, Software Process Maturity Assessment and Software Project Assessment", pp. 415, in the Metrics and Models in Software Quality Engineering book on the maisqual wiki.
Personal tools