Home » Solutions » By Industry » Automotive

Management Summary – ISO 26262 support by codeBeamer

solutions-automotiveIntland’s Application Lifecycle Management platform codeBeamer is suited to create safety-related systems developed in processes according to ISO/DIS 26262 and IEC 61508 and therefore helps being compliant with important standards in the automotive world. The various disciplines supported by codeBeamer enable automotive engineering organizations in developing safety-related embedded systems up to ASIL-D or SIL3.

codeBeamer also supports companies in improving their productivity. Automating otherwise manual and error-prone activities can be enhanced through workflows, real-time reporting and metrics. Therefore, systemic errors can be significantly reduced if not avoided and greater release readiness visibility will be achieved.

codeBeamer acts as a central repository and avoids media breaks. It also represents a single source of truth for the development of software-intensive products. Audit preparation and product documentation is automatically provided when codeBeamer is applied throughout the development process. The risk of non-compliance will be largely decreased.

Due to its single repository architecture, codeBeamer delivers traceability of the full lifecycle between hazard and risk management to requirements management to test management all the way down into source configuration management more easily. Collaboration between distributed organizations is achieved and representatives can concentrate on accelerating product development and innovation while handling a high turnover of requirements and other artifacts and cope with constant change. Integrations with other engineering authoring tools can be achieved through respective applications programming interfaces, e.g. for company-specific test automation, to enhance overall productivity.

Furthermore, Intland’s codeBeamer site provides customers with the ability to view current and release-specific problem reports. Customers can find relevant information about defects and similar worki tems as well as possible workarounds which are already detected in the specific releases which might have impact on their own development. Of course, customers can report problems. Reported information there can also be shared in public with other users.

ISO 26262 related chapters

The ISO 26262 standard “Road vehicles – Functional Safety” contains 10 parts. The table below shows topics related to the different parts. These topics provide a rough overview on how codeBeamer helps you comply with ISO 26262.

codeBeamer ISO 26262 related Product Overview


codeBeamer is an adaptable and configurable enterprise application lifecycle management platform that coordinates and manages all activities and artifacts associated with developing software as part of an embedded product or as a standalone application.

Risk Management is not specifically addressed in this picture as it is technically similar to the Requirement Management discipline and can be achieved by deriving so called trackers (work item containers) from the requirements tracker.

The following parts try to elaborate on these topics to provide some basic overview.

Issue and Tracker Concept


The issue and tracker concept allows the free definition of artifact types and collections of artifacts in containers or documents as required by an organization; ISO 26262 is not prescriptive in a way that it tells which attributes have to belong to specific artifact types (from now on called tracker according to the codeBeamer terminology).

Tracker types are made up of different fields which can be freely defined as well. This concept enables e.g. the existence of different kind of requirements related to hardware or software, functional or safety-related requirements and basically all other artifacts for change and defect management.


Important features like workflows with role-specific status transitions enable processes for approval and enforcement of mandatory fields etc., therefore support for different kind of processes in general.

Relationship between issues plus reporting over these enable all kind of required reports according to ISO 26262.

Impact, Traceability and Coverage Analysis

As just mentioned, traces between issues allow different kinds of analysis like requirements test coverage where requirements are linked to executed test cases.

Another scenario is deriving technical requirements from stakeholder requirements or deriving safety requirements from related hazards and keeping overview how issues are related to others. This is a major feature supporting functional safety.


codeBeamer’s capability of marking related issues as suspect becomes important when change occurs. If a requirement is changed, it is important to notify a collaborating test engineer about the change which might have great impact on the related test cases.

The figure above can be thought of as a rough template which data structures need to be defined inside codeBeamer.

Document & Release Management

Everything stored in codeBeamer can be viewed as documents or tables and can be associated to releases or subreleases. Binary file-based documents can be stored as attachments as well. Everything stored in codeBeamer is indexed for a flexible search.

Of course, access rules and dependencies are respected and versioning on all issues is taking place automatically in the background, so traceability into the past is guaranteed as well.

Requirements Management


Requirements management offers import and export capabilities, manual capturing and management of requirements. It can be viewed as a module which is handling those trackers and issues which are relevant for requirements in ISO 26262.

Everything is treated as data or documents and can be assigned to releases. Requirements can also be linked to test cases to prove that requirements are met. This is especially important for safety-related requirements which are of high importance to ISO 26262. Capturing of requirements and linking to test cases can occur in a document-centric-style as shown above.

Test Management


Test management offers import and export capabilities, manual capturing and management of test cases, test sets and test runs and their results. It can be viewed as a module which is handling those trackers and issues which are relevant for verification and validation in ISO 26262.

The figure shows test results and metric for the quality management aspects of product development.

Further features in test management are about creating and linking defects during test execution, organizing test cases for re-use in different scenarios, integration with test automation.

Change Management


codeBeamer supports an integrated change management which provides such benefits as:

  • Collecting, managing and tracking change requests
  • Linking change requests to their related requirements
  • Suspect management which assists in propagating changes
  • Plan changes together with requirements to next release
  • Effort estimation and time tracking
  • Release readiness visualization and work assignment
Configuration Management

codeBeamer supports various configuration management systems as CVS, Subversion, Git and Mercurial. Next to the out-of-the-box functionality of these version control system, codeBeamers adds repository management and access control plus traceability of code changes on top. When using Git for example, distributed source code development is supported by specific workflows.

Most important for ISO 26262 is the feature to relate defects, change requests or tasks to source code changes when committing source code into the repository. Issue relation can be enforced upon commit so no uncontrolled changes occur on the software level and the traceability between processes and development is guaranteed.


Team collaboration was already mentioned in different places in the chapters above. As a summary we can define that stakeholders on all levels can communicate directly or indirectly in various ways.

Indirect communication and collaboration occurs when the suspect linkage flags become active to indicate change on related issues. Other communication is taking place when using the commenting feature in codeBeamer where threads of discussion are started.

The workflow transitions of certain issues like tasks indicate that somebody has started working which is useful and automatic input for a project manager who is controlling the change process and distributing the work among developers.

Risk management

codeBeamer can assist in risk management by its tracker and issue configuration feature for safety goals, hazards and related requirements of differing types, see previous figures.

As reporting and workflows are available for various trackers the necessary risk reports required by ISO 26262 can be created individually.

One example of extended risk management is doing an Excel-like failure modes and effects analysis inside a codeBeamer tracker. When certain risk priority numbers are calculated they can be compared against thresholds which would require a mitigation through newly created safety requirements.

Top codeBeamer benefits in the ISO 26262 context

  • Configurable access and security management for all process artifacts and source code
  • Configurable risk capturing and management
  • Configurable requirements import/export, capturing and management
  • Test management vor verification and validation, execution and coverage
  • Managed source code repositories
  • Traceability between arbitrary artifacts throughout all artifacts and disciplines and real-time reporting capabilities. Traceability as the base for safety-related reports and more
  • Support for distributed development and collaboration enhancement, automated workflows, escalation management
  • Versioning of all artifacts, baselining of projects
  • Integrated document management and full text search
  • Cross-project management and workload distribution planning and visualization
  • Configurable change management issues and workflows