1. ALM-PLM Requirements, Change and
Configuration Integration: Today's
Practices and a Vision of Tomorrow
Jonathan C Archer
Director of Process Management
2. 22
Todays Presentation
Today PTC provides a level of integration between PTC Integrity and
PTC Windchill PDMLink. This presentation will review current
practices supporting this integration along with presenting a vision of
the future deeper integrations.
27. 27
• Software Part
– Object in product structure to represent specific software deliverable / module / node
• Software Build
– Contains software build / deliverable, such as software library objects or executables
• Software Configuration Data
– Contains configuration file to “enable or disable” functions within a build
• Software Document
– Contains source code or link to src code in SCM system
• Software Defect
– Proxy object to remote defect tracking system defect or local Windchill defect
Current Data Model and Relationships
Software and Hardware information sharing – Windchill provides:
Software Part
Software Build
Software
Configuration
Software
Document
Hardware Part
End Item
28. 28
Hardware with Software Configuration
Compiled Software and Configuration associated to Product Structure
Create Structure
Create Document
End
Associate Source
Code Configuration
Determine Build and
Compile
Start
1.0
2.0
3.0
4.0
Create Build
Associate Binaries /
executable
5.0
6.0
Software Build developed in
Integrity Project
Software Part Added to
structure
Software build process
completed in Integrity
Build information added to
Document which is associated to
Software Part
1.0
2.0
3.0
4.0
5.0
6.0
Placeholder document added
to product
Software configuration file
added to Part with link to
Integrity
53. 53
Integrated Change and Release
Software Changes are documented within Hardware Change Processes
Define Software Issues
as WC Software Defect
Review Open and
Closed Issues
End
Compile Code and
Build
Manage Software
Issues
Start
1.0
2.0
3.0
4.0
Collect and Revise
Release Structured
Software
5.0
6.0
File Software Defects within
Integrity to support changes
Defects generates Defect in
Windchill with synchronized
states, tied to Software Build
Software build process
completed in Integrity
Revised Software Part with
compiled Code associated
1.0
2.0
3.0
4.0
5.0
6.0
Close to Release cycle,
Change information is
reviewed including Open and
Closed Defects
Software Revised / released
with reference to Defects
56. 56
Future Concepts: Integrated Change Process
Task and Workflow enabled coordinated changes between Domains
FUTURECONCEPT – subject to change
Software Change
Collect and Relate
Affected SW
Design Artifacts
Hardware Change
Collect and Relate
Affected HW
Design Artifacts
Open Domain Specific
Tasks/Activities
Associated to
Common Change
Open Tasks Related
to Specific System
Change Process
Coordinate changes to System, SW, HW