The Best of Both Worlds: Agile Development and Fast Compliance

The Best of Both Worlds
Agile Development and Fast
Compliance
How to Achieve Compliance (And Still Be Agile)

2© Perforce Software Inc. All Rights Reserved.
Presenters
Nico Krüger
General Manager
Helix ALM / Hansoft
Richard Bellairs
Product Marketing Manager
Helix QAC

Here’s What We’ll Cover Today
Traceability
With Product
Agility
Coding
Standards
Compliance
Perforce Tools
Balance Compliance
With Agile

Compliance Requirements for Functional Safety
INDUSTRY STANDARDS
IEC 61508
IEC 60880IEC 62304
ISO 26262 EN 50128

• ISO 26262
• ASIL (Automotive Safety Integrity Level) with traceability
• Coding standard (such as MISRA, AUTOSAR)
Compliance in Automotive…

• DO-178C
• FTA
• IEC 61508
• MIL-SPEC 1629A
• FMECA (Failure Mode, Effects,
and Critical Analysis) with
traceability
• Coding standard (such as
JSF AV C++, MISRA)
Compliance in Military / Defense…

• IEC 62304
• ISO 14971
• 21 CFR
• FMEA (Failure Mode
and Effects Analysis)
with traceability
• Coding standard
(such as MISRA)
Compliance in Medical Device / Life Sciences…

Traceability With Product Agility

• Traceability in software engineering is the ability to trace work items across the
development lifecycle.
• Traceability is a SIL verification step.
• FDA Part 820 (Quality systems regulation) requires identification and traceability.
Why Traceability Is Important

• It should be bidirectional in nature. Requirements should be traceable from both
ends.
• It should trace the requirements in each phase/stage in which requirements are
developed/detailed.
• It should also cover the test phases in which test cases are prepared to test
these requirements.
• It should be updated as the updated/detailed information becomes available.
• It is a live document that is updated throughout the project lifecycle.
Features Of Good Traceability

• Backwards traceability is
checking (what you did) is justified
by a requirement (what you need).
• Forwards traceability is checking
(what you need) is addressed in
later lifecycle stages (what you will
do).
Traceability Types

What Do We Trace
• Requirements / risks / hazards
• Test cases / test executions
• Failures / issues / bugs / changes
• Source code

• Compliance with industry
standards
• Instant impact analysis
• Automating traceability
matrix generation
• Faster time to market
(Agility)
The Advantages

• Work broken down into smaller chunks
called a sprint or iteration.
• Break down requirements into smaller
stories or tasks.
• Ensure each work item in a sprint has
the appropriate test coverage.
• Agile embraces change, traceability
makes this easier.
Traceability in Agile Development

Traceability Requires Structure
• Traceability is all about structure — parent and child items.

Traceability Supports Impact Analysis
• Understand the impact of changes before they happen.
• Manage and mitigate risks.

Traceability Improves Development
• Use relationships between
items to mark any item as
suspect.
• Investigate suspect
dependencies using traceability
matrix.
• Create a traceability matrix
from any level, including risk
management using FMEAs.

Doing ASIL Analysis With Helix ALM (ISO 26262)

Doing FMEA Analysis with Helix ALM (DO-178C)

Creating a Traceability Matrix in Helix ALM
(IEC 62304)

What Coding Standards Do
Ensure that software is:
• Safe: It can be used without causing harm.
• Secure: It can’t be hacked.
• Reliable: It functions as it should, every time.
• Testable: It can be tested at the code level.
• Maintainable: It can be maintained, even as
your codebase grows.
• Portable: It works the same in every
environment.

1. Compliance with industry standards (e.g., ISO).
2. Consistent code quality — no matter who writes the code.
3. Software security from the start.
4. Reduced development costs and accelerated time-to-market.
Why Use a Coding Standard?

Helix QAC Server
Applying a Coding Standard in an Agile Process

Managing Deviations with Helix QAC
DeviationsDiagnostic Suppressions

Balance Compliance With Agile
Using Perforce Tools

Perforce Toolset for DevOps Teams
SOFTWARE PROJECT — AGILE
Milestones/
Releases
SCRUM
KanbanProduct Backlogs
Quality Assurance
PLANNING
HARDWARE PROJECT — WATERFALL
Milestones/
Releases
Gantt
Product Backlogs
Quality Assurance
PLANNING
CROSS-PROJECT
FEATURES
PORTFOLIO
MANAGEMENT
ISSUES + TASKS
Portfolio Backlog
(& Risk Mgmt.)
Roadmaps
Project/Design
Documents
Resource
Management
To-Do
Metrics
Visibility
Traceability
Collaboration
Compliance
Security
Reports & Dashboards
Docs
Enterprise
Administration
and Security

Perforce Toolset for DevOps Teams
Flexible End-to-End
Application Lifecycle
Management
Agile Project & Product
Management
Version Control + Swarm Code Review
and Collaboration
Stores Git Repos in Helix Core
Static Code Analysis for
C and C++
+

Serving Industry Leaders
Automotive
Embedded Systems SoftwareGaming and Animation
Banking and FinanceHealth Care

Recap
Traceability
With Product
Agility
Coding
Standards
Compliance
Perforce Tools
Balance Compliance
With Agile

Follow us for news and insights!
Visit www.perforce.com

The Best of Both Worlds: Agile Development and Fast Compliance

More Related Content

What's hot (20)

Similar to The Best of Both Worlds: Agile Development and Fast Compliance (20)

More from Perforce (20)

Recently uploaded (20)

The Best of Both Worlds: Agile Development and Fast Compliance