ALM-PLM Requirements, Change and Configuration Integration: Today's Practices and a Vision of Tomorrow Jonathan C Archer Director of Process Management
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
ALM-PLM Requirements, Change and Configuration Integration: Today's Practices and a Vision of Tomorrow
Jonathan C Archer Director of Process Management
2 2
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.
Presenter
Presentation Notes
3
Current Traceability Methods Requirements Management–
Presenter
Presentation Notes
Takeaway: Trace requirement to ensure that requirements are met (satisfied) through relationships to downstream artifacts
4
Requirements Traceability
Trace between Requirements and Specifications to Software and Hardware development
2014
Create Traces
Update Traces
Report & Monitor Traceability
Determine Trace Strategy
Start
1.0
2.0
3.0
4.0
End
Determine Trace Strategy 1.0
Create Traces 2.0
Report & Monitor Traceability 4.0
Update Traces 3.0
Presenter
Presentation Notes
Takeaway: Trace Strategy; Flexible data mode for Requirements – decompose to manufacturing and service requirements, functions, critical parameters and even function of an IoT sensor. Create Traces; Not only between requirements objects shown here, but to other downstream artifacts as well During churns, traces become suspect. Create and Update as the development process evolves
5
Current – Requirements Tracing
2014
Presenter
Presentation Notes
Takeaway: there is a methods to trace to all Requirement types, to verification with testing, software designs as well as product content. Product content tracing is currently a one to one process method to tie them together
6
Context Based Vision of the Future Requirements Management Traceability
Future looking information Subject to change without notice © 2014 PTC
7
Future Concept: Requirements Tracing Data Model
Direct Tracing
Product Structure
Requirements
PTC Integrity PTC Windchill
Tests
Software Requirements
Tests Documents
Future looking information Subject to change without notice © 2014 PTC
8
Future Vision – ALM-PLM Requirements Traceability
System Requirements and Validation
System & Logical Engineering Val idation/ tests M anufacturing Requi rement Service
Modern UX for rich requirements authoring
Modern UX to Create and trace relationships
Create and trace relationships
Open Relationships and Related Objects
Trace Requirements to Product Information
Future looking information Subject to change without notice © 2014 PTC
Presenter
Presentation Notes
Takeaways: Modern Web enabled UX usable by all domains, support a larger set of object types to trace to, provide a UI to develop in-context relationships between requirements and other objects (Artisan already provides this function).
9 Future looking information Subject to change without notice © 2014 PTC
Presenter
Presentation Notes
User Action – Click Add from the Allocate to toolbar
10 Future looking information Subject to change without notice © 2014 PTC
Presenter
Presentation Notes
User Action – Choose Search
11 Future looking information Subject to change without notice © 2014 PTC
Presenter
Presentation Notes
User Action – Select “MAYTAG, ALPHA – ASM” Takeaway – User adds top-level End Item to allow for tracing to its downstream components that comprise the assembly to the top-level requirements document
12 Future looking information Subject to change without notice © 2014 PTC
Presenter
Presentation Notes
User Action – Choose OK
13 Future looking information Subject to change without notice © 2014 PTC
Presenter
Presentation Notes
User Action – Choose OK
14 Future looking information Subject to change without notice © 2014 PTC
Presenter
Presentation Notes
Action – Select the row Takeaway – The top level assembly has a relationship now that provides the ability to further edit tracing
15 Future looking information Subject to change without notice © 2014 PTC
Presenter
Presentation Notes
Action – Click Edit from the Satisfies toolbar
Future looking information Subject to change without notice © 2014 PTC
Presenter
Presentation Notes
Action – Click Technical Specification Takeaway – The n-view diagram shows the requirements documents requirements sections in the left column and the assemblies components in the top row. Hyperlinks show that there is additional downstream contents for either the requirement section or sub-assembly that can be further drilled down into. Selecting Technical Specification drills down to the contents of that section within the requirement.
Future looking information Subject to change without notice © 2014 PTC
Presenter
Presentation Notes
User Action – Select cell “Buttons | BUTTON MOD 1” Takeaway – The Technical Specification section is comprised of two Specifications; Buttons and User Interfaces. Selection of cells changes the context of the information provided in the lower views. Think of these ‘windows’ as the cells in a typical requirements document managed in spreadsheets but fully up to date utilizing the latest information in the system.
Future looking information Subject to change without notice © 2014 PTC
Presenter
Presentation Notes
User Action – Choose Add
Future looking information Subject to change without notice © 2014 PTC
Presenter
Presentation Notes
Action – Click Right Arrow button or key to select cell “Buttons | BUTTON MOD 2” Takeaway – The end user can add the trace between the buttons specification and the part, in the context of the other components
Future looking information Subject to change without notice © 2014 PTC
Presenter
Presentation Notes
User Action – Choose Add
Future looking information Subject to change without notice © 2014 PTC
Presenter
Presentation Notes
User Action – Click Down Arrow button or key
Future looking information Subject to change without notice © 2014 PTC
Presenter
Presentation Notes
Action – Click Display Specification Takeaway: Direct relationships between items create indirect relationships to higher level items
Future looking information Subject to change without notice © 2014 PTC
Presenter
Presentation Notes
Action – RMB click
Future looking information Subject to change without notice © 2014 PTC
Presenter
Presentation Notes
Action – Choose RMB>Add Trace Takeaway – Other methods might be to provide an RMB mouse action to select cells and add traces, still within the context of the other components
Future looking information Subject to change without notice © 2014 PTC
26
Using standard Product Structure relationships today Managing Software-Hardware Configuration
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
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
29
Hardware with Software Configuration
30
Future Concept Configuration Management – Matrix Management
Future looking information Subject to change without notice © 2014 PTC
31
Hardware with Software Configuration
To Be Process Improvement: Matrix Management Future Concept
Specify Hardware Compatibility
Review Compatibility
End
Open Matrix and Review
Open Compatibility for Software
Start 1.0
2.0
3.0
4.0
Export 5.0
For a particular Software Version, select compatible Hardware configurations
Users can now open Matrix and review
Export Matrix for edit and publishing
1.0 2.0
3.0
4.0
5.0 Review Compatibility
From Software Part, select Compatibility
Future looking information Subject to change without notice © 2014 PTC
32
Matrix Management Future Concept
UX Concept Click-through Review
Future looking information Subject to change without notice © 2014 PTC
Presenter
Presentation Notes
Takeaway – concept would provide ability to see different software versions with hardware platforms in an n-view format
Presenter
Presentation Notes
Takeaway – The end user could then select a hardware platform, the select the different design variants for that platform in which the software version is compatible
Future looking information Subject to change without notice © 2014 PTC
Presenter
Presentation Notes
The user then can select the variant
5S
Future looking information Subject to change without notice © 2014 PTC
5S, 5C
Future looking information Subject to change without notice © 2014 PTC
5S, 5C, 5
Future looking information Subject to change without notice © 2014 PTC
5S, 5C, 5, 4S
Future looking information Subject to change without notice © 2014 PTC
5S, 5C, 5, 4S, 4
Future looking information Subject to change without notice © 2014 PTC
Presenter
Presentation Notes
A different platform is selected…
Future looking information Subject to change without notice © 2014 PTC
Presenter
Presentation Notes
In this case, the user has drilled down into a the Product platform, where the variants are shown in the columns. The user can then select the compatible versions.
Future looking information Subject to change without notice © 2014 PTC
Future looking information Subject to change without notice © 2014 PTC
Future looking information Subject to change without notice © 2014 PTC
5S, 5C, 5, 4S, 4 4th, 3rd, 2nd
Future looking information Subject to change without notice © 2014 PTC
Presenter
Presentation Notes
Rolling back up the higher level view, the user can see the selected software releases
Future looking information Subject to change without notice © 2014 PTC
Presenter
Presentation Notes
The user can also drill down into a particular hardware platform and look at all the hardware variants see the compatibility matrix of software. An Action available might be to allow for external publishing and editing. Edits might be required because you may want to remove current prototype and in work product information that you would not want to expose to external customers for example.
46
Mobile Version Windchill Matrix Folder App
Future looking information Subject to change without notice © 2014 PTC
Presenter
Presentation Notes
An application using the externally exported and modified content could potentially be developed…
Future looking information Subject to change without notice © 2014 PTC
Presenter
Presentation Notes
Allowing for the ‘customer’ (either external or internal) to drill down into the details for either a software version or hardware variant
Future looking information Subject to change without notice © 2014 PTC
Presenter
Presentation Notes
Drilling down into the software version, they can drill down further…
Future looking information Subject to change without notice © 2014 PTC
Presenter
Presentation Notes
To a particular OS version
Future looking information Subject to change without notice © 2014 PTC
Presenter
Presentation Notes
And see the compatibility to a particular hardware device.
52
Current Integration Methods Cross Discipline Change
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
54
Issue Management Software Defect Tracking
2014
55
Future Concepts Cross Discipline Change
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
Presenter
Presentation Notes
Takeaway – In the future would like to have a more rich and deep integration for change management; user and task synchronization and management.
57
Don’t forget the survey
Session PTC309
l iveglobal.ptc.com
Related Documents
