Is there a recommended limit for cross project area relationships
Is there a recommended limit for cross project area relationships? When a client wants to embrace a product line engineering approach, there is typically a set of reusable CLM project areas (call this Platform CLM project areas) that other JAZZ CLM project areas (call them Program CLM Project areas) would reference. A platform is consumed by many different programs.
When applying this practice to CLM project areas, is there some constraint level for the number of relationships that exist from the platform project area to the program project areas?
Thinking in the 10s, 100s, 1000s sort of limits. This doesn't need to be an exact number unless an exact number exist in our product.
Comments
Ulf Arne Bister
Dec 20 '18, 4:51 a.m.