Configuration Management & changes over time Options in Express-G, Tim Turner, 24 May 2012
As-is Model (Express-G) Does not allow to record config changes over time or across hulls
Proposed move for CI? Pointing to the relationships that may change with new or revisions of the configuration – better?
Alternative? Re-organise relationships (a) Alternative to leave CI as is but modify relationships involving Hull_applicability to include assembly relationships that might change? Replaced
Alternatives? Refine relationships (b) Perhaps better to point from Hull_applicability to these relationships than other way around – then to rename them?