Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Understanding ISO/IEC 14143-6-14:2019: Functional Size Measurement for Real-Time and Embedded Systems
A detailed guide to the scope, technical requirements, and compliance of the latest extension to the ISO/IEC 14143 series
Scope of ISO/IEC 14143-6-14:2019
ISO/IEC 14143-6-14:2019 is an extension within the ISO/IEC 14143 series that provides specific guidelines for applying functional size measurement (FSM) to real-time and embedded systems. This standard addresses the unique challenges of measuring functional size in systems where time constraints, concurrency, and hardware-software interactions are critical. It builds upon the general framework established in ISO/IEC 14143-1 and aligns with the principles of COSMIC (ISO/IEC 19761) and other FSM methods.
The standard covers systems ranging from automotive engine control units (ECUs) to industrial automation controllers and medical device firmware. It defines rules for identifying functional user requirements (FUR) in environments where operations are triggered by external events, sensors, or timing functions. The scope explicitly excludes batch-oriented or purely data-centric systems, focusing instead on event-driven and reactive architectures.
Key Benefit: By standardizing size measurement for real-time and embedded domains, this part enables more accurate project estimation, benchmarking, and productivity analysis across critical industrial sectors.
Technical Requirements
The standard mandates several key technical adaptations to traditional FSM methods:
Identification of Functional Processes
Event-Based Decomposition: Instead of using data movement as the sole criterion, ISO/IEC 14143-6-14 requires analysts to identify functional processes based on external events. Each event triggers a sequence of data movements, control flows, and timing constraints that must be measured as a single unit.
Handling of Real-Time Behavior
The standard introduces temporal subprocesses for periodic tasks, watchdog resets, and interrupt service routines (ISRs). These are measured using modified counting rules that account for:
- Event occurrence frequency (e.g., periodic vs. aperiodic)
- State-dependent behavior (e.g., mode changes)
- Hardware interaction layers (sensors, actuators, buses)
Implementation Note: Avoid double-counting temporal subprocesses when the same event triggers multiple threads. The standard specifies linking rules to aggregate these into a single functional process.
Measurement of Concurrency
The standard requires that parallel execution paths be treated as a single aggregated functional process if they share a common triggering event and contribute to the same functional user requirement. This prevents inflation of functional size due to parallel software architecture.
| Aspect | Standard FSM (e.g., COSMIC) | ISO/IEC 14143-6-14 Extension |
|---|---|---|
| Trigger identification | User-defined events only | Internal timing events, hardware interrupts |
| Data movement | Entry, exit, read, write | Also includes control signals, status flags |
| Subprocess boundaries | By functional user | By event and time interval |
| Hardware abstraction | Excluded or opaque | Explicit mapping of device interfaces |
| State-based behavior | Not considered | Different sizes for each operational mode |
Implementation Highlights
Applying ISO/IEC 14143-6-14 in practice requires both process and tool adaptations:
Process Integration
Organizations should integrate functional size measurement into their requirements engineering workflow. For real-time systems, the standard recommends using sequence diagrams or statecharts to identify events and their associated functional processes. Each distinct scenario (e.g., start-up, normal operation, fault recovery) should be measured separately.
Tip: Use automated tools that support the extended measurement rules for concurrency and timing. Many parametric estimation models for embedded systems now accept input in the format defined by this standard.
Measurement of Hardware-Software Interactions
A significant contribution of this part is the explicit treatment of hardware interfaces. When a sensor value is read inside an interrupt routine, the associated data movement must be counted even if the operating system abstracts the hardware. The standard provides guidelines for identifying boundaries when software and hardware portions are co-developed.
Estimation and Benchmarking
Functional size measured per this standard can be used to calibrate estimation models for development effort, test effort, and project duration. A growing database of industry benchmarks is available for embedded domains such as automotive, avionics, and industrial IoT.
Success Story: A leading automotive supplier reported a 22% improvement in effort estimation accuracy after adopting ISO/IEC 14143-6-14 for its AUTOSAR-based ECUs, compared to using generic FSM methods.
Compliance and Certification
While compliance with ISO/IEC 14143-6-14 is not typically mandated by law, it is increasingly referenced in procurement contracts for safety-critical and high-integrity systems. Conformance can be demonstrated through:
- Method Certification: Appoint an independent certifying body to validate that your FSM method complies with the counting rules in this part.
- Tool Certification: Ensure measurement tools adhere to the atomic rule set defined in the standard’s Annex B.
- Personnel Competence: Analysts should hold a certified FSM practitioner credential with specialization in real-time systems (e.g., COSMIC Certified Advanced Practitioner).
Critical Note: Non-compliance can lead to distorted size metrics, which in turn invalidate cost estimates and benchmarks. In domains like medical devices or autonomous driving, this may have legal and safety repercussions. Always perform a gap analysis against the standard before starting a new project.
Frequently Asked Questions
Q: How does ISO/IEC 14143-6-14 differ from the base COSMIC standard (ISO/IEC 19761)?
A: While COSMIC focuses on data movements from a user’s perspective, ISO/IEC 14143-6-14 extends the rules to include internal events, timing behavior, and hardware interfaces typical of real-time and embedded systems. It adds counting rules for temporal subprocesses and concurrent paths, which are out of scope in base COSMIC.
A: While COSMIC focuses on data movements from a user’s perspective, ISO/IEC 14143-6-14 extends the rules to include internal events, timing behavior, and hardware interfaces typical of real-time and embedded systems. It adds counting rules for temporal subprocesses and concurrent paths, which are out of scope in base COSMIC.
Q: Can I use this standard for legacy code retrofitting?
A: Yes, but with caution. The standard is designed for forward engineering where functional user requirements are documented. For legacy systems, reverse engineering is required to identify events and subprocesses. The standard provides guidance on deriving functional processes from source code analysis, but estimation accuracy may be lower.
A: Yes, but with caution. The standard is designed for forward engineering where functional user requirements are documented. For legacy systems, reverse engineering is required to identify events and subprocesses. The standard provides guidance on deriving functional processes from source code analysis, but estimation accuracy may be lower.
Q: What certification is available for this standard?
A: The ISO/IEC 14143 series does not have a dedicated certification. However, compliance can be assessed through third-party audits using ISO/IEC 14143-6-14 as an addendum to a broader FSM method certification. Some organizations offer “Functional Size Measurement for Real-Time Systems” certifications that verify knowledge of this part.
A: The ISO/IEC 14143 series does not have a dedicated certification. However, compliance can be assessed through third-party audits using ISO/IEC 14143-6-14 as an addendum to a broader FSM method certification. Some organizations offer “Functional Size Measurement for Real-Time Systems” certifications that verify knowledge of this part.
© 2026 International Standards Publishing. All rights reserved. The standard text is copyrighted by ISO/IEC.