Note this page is under construction
From the Core extensions:
Need for versioning with the target scenario
Consistent versioning support is necessary for OSLC to be able to support the target PLM scenario A systems engineer responds to a change in requirements.
The scenario begins with a product (or system) and associated requirenents and their associated, satisfying, implementations at some definied state; a change request is applied (i.e changes are made to relevant and impacted items) and their version identification are updated to signal completion of the change, with approvals. Version handling of the OSLC resource used in the scenario is needed, namely CM, AM and RM resources plus the new proposed PM resource that supports Products, Product Versions and Product Views.
OSLC PLM main scenario overview
Fig1: Overview of the need for versioning in the target scenario
Additional notes on the scenario:
Typically all items are under version control including the Change Request which may evolve during its evolution and approval.
The system or product context is the prevailing configuration, including variants.
The state of requirements and implementation is simplified as multiple constituents will go through various and multiple revisions before State 2 is achieved.
Open issues
Issue 3: Actual resource behaviour. Propose to show examples - not include as part of the Spec
Materials to promote to Cfg Mngmnt WG
Diagrams of resource relationships. Edits to meet revised vocabulary > provenance
From the Draft Product Definition specification:
Moitivation section to the Charter (using the model of the Cfg Mgmnt WG
Standards reference can be linked to (not in main part
Diagram can be updated (reference model structure
(includes heterogeneous resources
Usage of the LDP Aggregation needs to be included
Table of terms > prune the Version, View
Discussion OSLC Short ID is active in Core as a common property human readable unique label
Use Automation Spec as the latest model
Examples to update and attached files
Examples to update and attached files
Appendix A - Sample versioned OSLC Resources
Resource type OSLC Ref model example Scenario version Usage example Relationships Example
AM AMG60104 POWERSUBSYSTEM Base
Base AM Implementation Resource
Optional
hasVersion UR2(Non-preferred property)
AMG60104
AM
AMG60104/004-POWERSUBSYSTEM
004
AM Implementation Version Resource
isVersionOf URI1
AMG60104_004-POWERSUBSYSTEM
CM ECR-000031 Base Base Change Request Resource Optional
hasVersion UR2 (Non-preferred property) ECR-000031
CM ECR-000031/A-US and EU 2016 ULEV standards A Change Request Resource isVersionOf URI1 ECR-000031A-US_and_EU_2016_ULEV_standards
RM REQ-20188 Base Requirement base resource Optional hasVersion (Non-preferred property) REQ -20188
RM REQ-20188 - A A Requirement version resource isVersionOf REQ20188 REQ -20188 - A
RM REQ-20188 - B B Requirement version resource
isVersionOf REQ-201188
replacesREQ-20188-A
REQ -20188 - B
