Software Product - Quality and Metrics

ISO/IEC 25000, 9126, 14598 - Software Product Quality

As normas ISO/IEC 9126 - Engenharia de Software - Qualidade de Produto de Software; e ISO/IEC 14598 - Engenharia de Software - Avaliação da Qualidade de Produto de Software estão sendo integradas na nova Série ISO/IEC 25000 SQuaRE - Software Product Quality Requirements and Evaluation.

ISO/IEC 14598 - Engenharia de Software - Avaliação da Qualidade de Produto de Software:

  • Part 6: Documentação para Módulos de Avaliação

Architecture for ISO/IEC 25000 Series SQuaRE - Software Product Quality Requirements and Evaluation:

ISO/IEC 25000 Series: Systems and software engineering -- Systems and software [product] Quality Requirements and Evaluation (SQuaRE):

  • ISO/IEC 2500n - Quality Planning and Management:
    • ISO/IEC 25000:2014 (revision of 2008 version), Guide to SQuaRE
    • ISO/IEC 25001:2014 (revion of 2007 version), SQaRE -- Planning and management
      Replaces ISO/IEC 14598-2:2000 - Product evaluation -- Part 2: Planning and management.
  • ISO/IEC 2501n - Quality Models:
  • ISO/IEC 2502n - Quality Measurement:
  • ISO/IEC 2503n - Quality Requirements:
  • ISO/IEC 2504n - Quality Evauation:
    • ISO/IEC 25040:2011, SQuaRE -- Evaluation process
      Replaces ISO/IEC 14598-1:1999 - Software product evaluation -- Part 1: General overview.
    • ISO/IEC 25041:2012, SQuaRE -- Evaluation guide for developers, acquirers and independent evaluators
      Replaces the following parts of ISO/IEC 14598 - Product evaluation: Part 3:2000 - Process for developers, Part 4:1999 - Process for acquirers, Part 5:1998 - Process for evaluators.
    • ISO/IEC 25045:2010, SQuaRE -- Evaluation module for recoverability
  • ISO/IEC 2505n:
    • ISO/IEC 25051:2014, SQuaRE -- Requirements for quality of Ready to Use Software Product (RUSP) software product and instructions for testing
      O termo RUSP anteriormente era referenciado como "Commercial Off-The-Shelf" (COTS).
  • ISO/IEC 2506n:
    • ISO/IEC TR 25060:2010, SQuaRE -- Common Industry Format (CIF) for usability: General framework for usability-related information
    • ISO/IEC 25062:2006, SQuaRE -- Common Industry Format (CIF) for usability test reports
    • ISO/IEC 25063:2014, SQuaRE -- Common Industry Format (CIF) for usability: Context of use description
    • ISO/IEC 25064:2013, SQuaRE -- Common Industry Format (CIF) for usability: User needs report
    • ISO 25065:2019 - SQuaRE -- Common Industry Format (CIF) for Usability: User requirements specification
    • ISO/IEC 25066:2016, SQuaRE -- Common industry Format for Usability -- Evaluation Report

Related ISO Standards

ISO Standards and projects under the direct responsability of JTC 1/SC 7 Secretariat. ISO/IEC Joint Technical Comitee JTC 1: Information technology, Subcomitee SC 7: Software and systems engineering.

IEEE Std 1061 - IEEE Standard for a Software Quality Metrics Methodology

Software Metrics - Complexity and Quality

  • Software metric
    From Wikipedia, the free encyclopedia.
  • Programming Complexity
    From Wikipedia, the free encyclopedia.
  • Cyclomatic complexity
    From Wikipedia, the free encyclopedia. Cyclomatic complexity (or conditional complexity) is a software metric (measurement). It was developed by Thomas J. McCabe, Sr. in 1976 and is used to indicate the complexity of a program. It directly measures the number of linearly independent paths through a program's source code. The concept, although not the method, is somewhat similar to that of general text complexity measured by the Flesch-Kincaid Readability Test.
  • SourceMonitor
    The freeware program SourceMonitor lets you see inside your software source code to find out how much code you have and to identify the relative complexity of your modules. For example, you can use SourceMonitor to identify the code that is most likely to contain defects and thus warrants formal review. SourceMonitor, written in C++, runs through your code in a very fast (typically at least 10000 lines of code per second), single pass through source files written in C++, C, C#, VB.NET, Java, Delphi, Visual Basic (VB6) or HTML. It saves, exports (XML, CSV), displays and prints metrics in tables and charts, including Kiviat diagrams. Operates within a standard Windows GUI or inside your scripts using XML command files.

Software Estimation

  • Cost estimation in software engineering
    From Wikipedia, the free encyclopedia.
  • COCOMO II - Constructive Cost Model II
    COnstructive COst MOdel II (COCOMO II) is a model that allows one to estimate the cost, effort, and schedule when planning a new software development activity. COCOMO II is the latest major extension to the original COCOMO (COCOMO® 81) model published in 1981. It consists of three submodels, each one offering increased fidelity the further along one is in the project planning and design process. Listed in increasing fidelity, these submodels are called the Applications Composition, Early Design, and Post-architecture models.
  • Wikipedia: COCOMO
    From Wikipedia, the free encyclopedia.
    The Constructive Cost Model (COCOMO) is an algorithmic software cost estimation model developed by Barry W. Boehm. The model uses a basic regression formula with parameters that are derived from historical project data and current as well as future project characteristics.
  • Software development effort estimation
    From Wikipedia, the free encyclopedia.
    Software development effort estimation is the process of predicting the most realistic use of effort required to develop or maintain software based on incomplete, uncertain and noisy input. Effort estimates may be used as input to project plans, iteration plans, budgets, investment analyses, pricing processes and bidding rounds.
    See also: Comparison of development estimation software.
  • Software Estimating Rules of Thumb (PDF)
    Author: Capers Jones, Chief Scientist Emeritus, Software Productivity Research, Inc.
    Version 3: 2007-03-20.
  • Wikipedia: Capers Jones
    From Wikipedia, the free encyclopedia.
    Capers Jones is an American specialist in software engineering methodologies, specially software costs and sizing estimating. Jones collects data on software quality, risks, and best practices. His many computer science publications have been widely used by many organizations and educators.

Software Measurement - Functional Size




Mark II

  • UKSMA - United Kington Software Metrics Association
    Founded in 1988, UKSMA is a user group, a non-profit organisation that exists only to promote and improve the use of software measurement. They do this by facilitating communication and the sharing of expertise in various ways both within and beyond UKSMA, and launching initiatives.
    UKSMA is the Design Authority for the MkII FPA method, devised by Charles Symons and described in his book “Estimating with MkII FPA”. UKSMA members (individual membership is free) can freely download current FPA MkII Counting Practices Manual.
    UKSMA is the UK member of the ISBSG - The International Software Benchmarking Standards Group.
  • ISO/IEC 20968:2002 - Software engineering -- Mk II Function Point Analysis -- Counting Practices Manual

ISO/IEC 14143 - Functional Size Measurement

  • ISO/IEC 14143-1:2007 - Information technology -- Software measurement -- Functional size measurement -- Part 1: Definition of concepts
  • ISO/IEC 14143-2:2011 - Functional size measurement -- Part 2: Conformity evaluation of software size measurement methods to ISO/IEC 14143-1
  • ISO/IEC TR 14143-3:2003 - Functional size measurement -- Part 3: Verification of functional size measurement methods
  • ISO/IEC TR 14143-4:2002 - Functional size measurement -- Part 4: Reference model
  • ISO/IEC TR 14143-5:2004 - Functional size measurement -- Part 5: Determination of functional domains for use with functional size measurement
  • ISO/IEC 14143-6:2012 - Functional size measurement -- Part 6: Guide for use of ISO/IEC 14143 series and related International Standards