Sparx Systems Forum

Enterprise Architect => General Board => Topic started by: timoc on August 12, 2019, 11:48:53 pm

Title: Managing Model Overlap, and submodel lifecycles.
Post by: timoc on August 12, 2019, 11:48:53 pm

Hi,

I'm considering splitting out a model repository into separate model repositories as they have their own lifecycle. The models are interrelated, and i would like to be able to pull them together occasionally to manage the relationships between them. I want to keep the model meta-information (users, roles, element states etc) aligned too.

Is there a best practice or advice (for or against) this approach?
e.g. specific model design, submodels as root or view? Or baseline/merge policies?

As i understand it, if i want to go this route, it is usually done with exports - an XML (project settings) and XMI (submodel).

Tim.

Title: Re: Managing Model Overlap, and submodel lifecycles.
Post by: qwerty on August 13, 2019, 01:35:32 am

You could just use controlled packages (plus security) if you need r/o access for a modifiable part against other parts. Instead you can use version control in similar ways.

q.