Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
ISO/IEC 29110-1-2:2011 — Software Engineering — VSEs — Part 1-2: Standards and Profiles
Mapping International Standards to the VSE Lifecycle Profile Framework
Standards and Profiles for Very Small Entities
ISO/IEC 29110-1-2:2011 defines the relationship between the VSE lifecycle profiles and the international base standards from which they are derived. While Part 1-1 provides the conceptual overview of the VSE approach, Part 1-2 delivers the technical mapping — a detailed catalog showing exactly which clauses and requirements from ISO/IEC 12207 (software lifecycle processes) and ISO/IEC 15288 (system lifecycle processes) are included, excluded, or adapted in each VSE profile. This mapping is essential for VSEs that need to demonstrate compliance with the broader international standards ecosystem while operating with a reduced process footprint.
The technical mapping in 29110-1-2 is what distinguishes the 29110 series from generic “lightweight” methodologies like Agile or Scrum. It provides a traceable bridge between standard engineering processes and small-team practices, enabling VSEs to claim compliance with ISO/IEC 12207 without implementing every clause.
The document begins by establishing the process categorization framework. ISO/IEC 12207 defines over 40 processes organized into four categories: Agreement (acquisition, supply), Organizational Project-Enabling (lifecycle model management, infrastructure management, etc.), Project (planning, assessment, control, risk management, configuration management, etc.), and Technical (stakeholder requirements, requirements analysis, architectural design, implementation, integration, verification, validation, etc.). For each profile in the 29110 series, Part 1-2 specifies which of these processes are mandatory, recommended, or optional. The selection criteria are based on the VSE’s project characteristics: criticality, size, and complexity.
Profile Taxonomy and Standard Selection Methodology
The core contribution of ISO/IEC 29110-1-2 is the profile taxonomy, which classifies VSE profiles along two dimensions: profile group (Entry, Basic, Intermediate, Advanced) and profile category (generic, sector-specific, organization-specific). The generic profiles are the standard profiles defined by the 29110 series itself. Sector-specific profiles are extensions developed by industry consortia for regulated domains (e.g., medical device software, automotive, aerospace). Organization-specific profiles are customizations developed by individual VSEs for their own use. The taxonomy ensures that all profiles, regardless of their origin, share a common structure and can be assessed using the same conformity framework.
| Base Standard | Process Category | Entry Profile | Basic Profile | Intermediate Profile |
|---|---|---|---|---|
| ISO/IEC 12207 | Agreement Processes | Excluded | Supply only | Acquisition & Supply |
| ISO/IEC 12207 | Project Processes | PM (subset) | PM (full) | PM + Risk + CM |
| ISO/IEC 12207 | Technical Processes | SI (7 tasks) | SI (15 tasks) | SI + Validation |
| ISO/IEC 15288 | System Lifecycle | Excluded | System req. mapping | System architecture |
| ISO/IEC 12207 | Organizational Processes | Excluded | Excluded | Infrastructure + Improvement |
A critical detail in the standard selection methodology is the treatment of the Agreement processes. The Entry profile deliberately excludes Acquisition and Supply processes because a single-project VSE working on internal products does not need formal supplier management. However, as soon as the VSE engages in client-contract work, the Basic profile’s Supply process becomes mandatory. Part 1-2 provides explicit decision criteria to help VSEs determine when to adopt each agreement-related process.
The standard selection methodology also addresses the relationship between software processes (ISO/IEC 12207) and system processes (ISO/IEC 15288). For VSEs developing pure software products, the 12207-derived profiles are sufficient. For VSEs developing embedded systems, hardware-software combinations, or cyber-physical systems, Part 1-2 provides additional guidance on incorporating system-level processes from ISO/IEC 15288 while maintaining the lightweight character of the VSE approach. This dual-standard coverage is a unique feature of the 29110 series that is often overlooked by adopters who focus solely on the software dimension.
Engineering Design Insights for Standard Adoption
From a process engineering perspective, ISO/IEC 29110-1-2 provides a master class in standard subsetting and composition. The key engineering challenge is: given an international standard with hundreds of clauses, how do you select a coherent subset that (a) covers the essential lifecycle needs of small projects, (b) maintains internal consistency, and (c) preserves upward compatibility with the full standard? The answer, as demonstrated by Part 1-2, involves three techniques: outcome-based selection, dependency-graph pruning, and capability staging.
When tailoring any standard for a small team, use the dependency-graph approach demonstrated in 29110-1-2: map all clauses as nodes in a directed graph where edges represent “requires” relationships. Remove all nodes that are not strictly necessary for your project type, then verify that the remaining graph is fully connected (i.e., every process has its prerequisites satisfied). This technique prevents the common mistake of cherry-picking individual practices without ensuring that the supporting infrastructure exists.
The second design insight is the explicit treatment of tailoring rationale. For every clause from ISO/IEC 12207 that is excluded from a VSE profile, Part 1-2 documents the rationale (e.g., “Excluded because a 3-person team does not have dedicated roles for configuration management; configuration identification is handled informally by the lead developer”). This rationale documentation serves two purposes: it prevents well-intentioned auditors from demanding that excluded clauses be reinstated, and it provides a template for VSEs that need to develop their own organization-specific customizations for domain-specific standards (e.g., ISO 13485 for medical device software or DO-178C for avionics).
Third, the standard introduces the concept of profile equivalence levels to facilitate cross-recognition between different profile schemes. A VSE that achieves ISO/IEC 29110 Basic profile conformance is considered to have process capability equivalent to Level 2 on the ISO/IEC 15504 (SPICE) scale. This equivalence mapping enables VSEs to participate in global supply chains where prime contractors require SPICE assessments — the VSE can achieve Basic profile conformance at a fraction of the cost of a full SPICE assessment while providing substantively equivalent process assurance.
Frequently Asked Questions
Q1: Can a VSE combine 29110 profiles with Agile methods?
Yes, and this is actively encouraged. Many VSEs implement the 29110 Basic profile processes using Scrum or Kanban as the execution framework. The 29110 series specifies WHAT processes should be performed (the lifecycle outcomes), while Agile methods specify HOW the work is organized (the management framework).
Yes, and this is actively encouraged. Many VSEs implement the 29110 Basic profile processes using Scrum or Kanban as the execution framework. The 29110 series specifies WHAT processes should be performed (the lifecycle outcomes), while Agile methods specify HOW the work is organized (the management framework).
Q2: Does 29110-1-2 cover domain-specific standards like ISO 26262 (automotive)?
Not directly. Part 1-2 focuses on the mapping between VSE profiles and the generic lifecycle standards (12207, 15288). Sector-specific mappings are developed as separate technical reports or international standards by the relevant domain committees (e.g., ISO/TC 22 for automotive, IEC/SC 62A for medical devices).
Not directly. Part 1-2 focuses on the mapping between VSE profiles and the generic lifecycle standards (12207, 15288). Sector-specific mappings are developed as separate technical reports or international standards by the relevant domain committees (e.g., ISO/TC 22 for automotive, IEC/SC 62A for medical devices).
Q3: How often are the standard selection mappings updated?
The mappings are reviewed as part of the systematic review process for the 29110 series (typically every 5 years). Updates reflect changes in the base standards (ISO/IEC 12207 and 15288 are also periodically revised) and lessons learned from VSE adoption experiences worldwide.
The mappings are reviewed as part of the systematic review process for the 29110 series (typically every 5 years). Updates reflect changes in the base standards (ISO/IEC 12207 and 15288 are also periodically revised) and lessons learned from VSE adoption experiences worldwide.
Q4: What is the smallest VSE that has successfully adopted a 29110 profile?
Case studies in the ISO/IEC 29110 adoption literature document successful implementations by single-developer teams (1 person). The Entry profile is specifically designed for this scenario, and the documented adoption effort for a solo developer is approximately 2–3 weeks of process setup followed by 2–3 months of pilot project execution.
Case studies in the ISO/IEC 29110 adoption literature document successful implementations by single-developer teams (1 person). The Entry profile is specifically designed for this scenario, and the documented adoption effort for a solo developer is approximately 2–3 weeks of process setup followed by 2–3 months of pilot project execution.
