ISO/IEC 29110-2-1:2015 — Software Engineering — VSEs — Part 2-1: Framework and Taxonomy

Framework and Taxonomy for VSE Lifecycle Profiles

ISO/IEC 29110-2-1:2015 is the most technically detailed document in the 29110 series, providing the complete framework for defining, constructing, and assessing VSE lifecycle profiles. While Parts 1-1 and 1-2 explain WHAT the VSE profiles are and WHY they exist, Part 2-1 specifies HOW profiles are formally defined, HOW conformity is assessed, and HOW new profiles (sector-specific or organization-specific) can be constructed within the taxonomy. This framework document is essential reading for process engineers, conformity assessment bodies, and VSE support organizations that need to implement the 29110 series beyond the standard generic profiles.

The framework defined in Part 2-1 has three major components. First, the Process Reference Model (PRM) defines the complete set of process outcomes that can be included in any VSE profile, organized into process categories and groups. Unlike ISO/IEC 12207 which defines hundreds of detailed practices, the VSE PRM uses outcome-based statements — each outcome is a concise description of what must be achieved (e.g., “Software requirements are documented and approved by the customer”) without prescribing how. This outcome orientation is critical for VSEs because it provides flexibility in implementation methods while maintaining rigor in results.

Profile Definition and Conformity Assessment Methodology

The taxonomy framework in Part 2-1 defines profiles as structured selections of PRM outcomes organized into profile groups (Entry, Basic, Intermediate, Advanced) and profile categories (generic, sector-specific, organization-specific). Each profile is formally specified in a Profile Specification document that includes: the list of mandatory outcomes, the list of optional outcomes, the list of excluded outcomes from the PRM, the profile group and category identifiers, and the target VSE characteristics. The Profile Specification uses a standardized template to ensure that profiles from different sources (e.g., a medical device profile from ISO/TC 210 and an automotive profile from ISO/TC 22) can be compared and potentially harmonized.

The conformity assessment methodology in Part 2-1 defines three assessment modes: self-assessment (internal evaluation by the VSE itself), third-party assessment (independent certification body), and peer assessment (evaluation by another VSE under the coordination of a support organization). For micro-enterprises with limited budgets, self-assessment using the standardized checklist is the most practical entry point. The standard provides detailed guidance on evidence collection, including acceptable evidence types (project plans, requirements documents, test reports, meeting minutes, version control logs) and the minimum evidence set required for each profile outcome.

Engineering Design Insights for Framework Implementation

ISO/IEC 29110-2-1 embodies several sophisticated engineering design decisions that are relevant beyond the VSE domain. The first is the outcome-based PRM architecture. By defining processes in terms of outcomes (what must be achieved) rather than practices (how to do it), the framework achieves separation of concerns between process definition and process implementation. This architectural pattern is directly applicable to any standard or framework that needs to accommodate diverse implementation contexts — a principle that also appears in ISO/IEC 20000-1 (service management) and ISO 27001 (information security) but is executed with particular elegance in the VSE context due to its minimalist scope.

The second design insight is the taxonomy’s support for profile evolution. The framework explicitly defines how a VSE can transition between profiles (e.g., from Basic to Intermediate) and how profiles can be extended for specific domains. The transition path is defined as a superset relationship: the Intermediate profile includes all outcomes of the Basic profile plus additional outcomes for organizational management and infrastructure. This superset design ensures that process assets created under the Basic profile remain valid under the Intermediate profile — a critical property for protecting the VSE’s process investment.

Third, the framework introduces the concept of process outcome weighting for conformity decisions. Not all outcomes in a profile carry equal significance. Critical outcomes (typically those related to requirements agreement, product delivery, and customer acceptance) are designated as “gate” outcomes — failure to achieve any single gate outcome results in overall profile non-conformance. Non-critical outcomes allow for partial achievement with a corrective action plan. This weighted approach prevents the entire conformity determination from being invalidated by a minor documentation gap while maintaining rigor on the outcomes that directly affect product quality and customer satisfaction.

Frequently Asked Questions