Tristan Mitchell: Tracking Critical Changes
23
TRACKING CRITICAL CHANGES ARE YOU REGULATORY COMPLIANT? PROVE IT! PRESENTED BY TRISTAN MITCHELL
-
Upload
jack-molisani -
Category
Leadership & Management
-
view
9 -
download
1
Transcript of Tristan Mitchell: Tracking Critical Changes
TRACKING CRITICAL CHANGESARE YOU REGULATORY COMPLIANT?
PROVE IT!PRESENTED BY TRISTAN MITCHELL
Identification
Representation
Management
of XML Change
OBVIOUS TRUTH #1
Content Changes
“Everything changes and
nothing remains still”
“Change is the only constant”
“To improve is to change, so to be
perfect is to have changed
often.”
OBVIOUS TRUTH #2
Stakeholders want to see the changes
Authors
Editors
SMEs
Reviewers
CustomersAuditors
OBVIOUS TRUTH #3
Change must first be identified before you can show it
Revision log
Version control
Change tracking
Comparison
Native Markup(e.g. DITA)
Processing instructions
Identification
@rev attribute
@status attribute
Release management domain
Representation
LESS OBVIOUS TRUTH #1
Structured content presents opportunities
around change
LESS OBVIOUS TRUTH #2
Identified change can be published
Demo
MAKING IT WORK
Provide stakeholders with changes relevant
to their needs
Authors
Editors
SMEs
Reviewers
CustomersAuditors
Tracked changesTracked changes
Published changes
Change summaryPublished changes
Change summaryTracked changes
Published changes
Change summaryPublished changes
MAKING IT WORK
Molina HealthCareCase Study
MOLINA HEALTHCARE
• Word-based solution using change tracking
• Redline PDF ‘printed’ from Word
• Content moved to DITA-based system
• Conditional processing supports alternate requirements
• Change-tracking is no longer possible due to reuse
• Comparison used to create DITA source for redline publishing
SUMMARY
@TristanDeltaXML
• Content changes, constantly
• Think about who your change stakeholders are
• Build a mechanism for identifying and representing change
• Remember why you chose XML
• Provide changes in a way that meets stakeholder needs
