Enterprise Architect User Group - EA and version control in practice

Preview:

Citation preview

London 19 May 2017

EA and version control in practice

Dennis Geluk

ww

w.d

ivetr

o.n

l

Roadmap

• Why

• Need to know

• Configurations

• Best practices DiVetro

19/05/2017 2EA and version control in practice

ww

w.d

ivetr

o.n

l

Why

19/05/2017 EA and version control in practice 3

2. Configuration management1. Multiple users (at different locations) sharing the same model

ww

w.d

ivetr

o.n

l

Why

19/05/2017 EA and version control in practice 4

• Historical information of model

• Historical information of part(s) of the model

• Alignment with other deliverables

• Multiple users (disciplines)

• Re-use knowledge

• Personal sandbox

ww

w.d

ivetr

o.n

l

Need to know

• Enterprise Architect Project file (EAP) always needed

• EAP contains relational model

• Only “simple” merge / compare

• Only Packages can be saved as XMI file

• “meta data” stored in EAP

19/05/2017 EA and version control in practice 5

ww

w.d

ivetr

o.n

l

Most common configurations

1. Out of the box

2. DBMS

3. Version control repository

4. Combination of DBMS and version control repository

19/05/2017 EA and version control in practice 6

ww

w.d

ivetr

o.n

l

Most common configurations

1. Out of the box

2. DBMS

3. Version control repository

4. Combination of DBMS and version control repository

19/05/2017 EA and version control in practice 7

ww

w.d

ivetr

o.n

l

Out of the box

19/05/2017 EA and version control in practice 8

EAP

Baselines

Auditing

Characteristics

• Basic baseline (snapshot)

• Possibility to revert to baseline

• Standard merge / compare

• Track changes on model level

• Baseline / Changes integrated within model

• Packages can be controlled (Import / export)Control package

as XMI file

ww

w.d

ivetr

o.n

l

Out of box DBMS VC Repo Combi

Multiple users (disciplines)

Re-use knowledge

Personal sandbox

Historical information (Model)

Historical information (Parts)

Alignment other deliverables

Pros & Cons

19/05/2017 EA and version control in practice 9

Not supported

Well supported

ww

w.d

ivetr

o.n

l

1. Out of the box

2. DBMS

3. Version control repository

4. Combination of DBMS and version control repository

Most common configurations

19/05/2017 EA and version control in practice 10

ww

w.d

ivetr

o.n

l

DBMS

19/05/2017 EA and version control in practice 11

EAP

EAP

EAP

ww

w.d

ivetr

o.n

l

DBMS

19/05/2017 EA and version control in practice 12

Characteristics

• EAP file is transferred to DBMS tables

• All users use the same EAP

• DBMS locking on “row” levelDBMS

EAP

ww

w.d

ivetr

o.n

l

Out of box DBMS VC Repo Combi

Multiple users (disciplines)

Re-use knowledge

Personal sandbox

Historical information (Model)

Historical information (Parts)

Alignment other deliverables

Pros & Cons

19/05/2017 EA and version control in practice 13

Not supported

Well supported

ww

w.d

ivetr

o.n

l

1. Out of the box

2. DBMS

3. Version control repository

4. Combination of DBMS and version control repository

Most common configurations

19/05/2017 EA and version control in practice 14

ww

w.d

ivetr

o.n

l

Version control repository

19/05/2017 EA and version control in practice 15

EAP

EAP

EAP

ww

w.d

ivetr

o.n

l

Version control repository

19/05/2017 EA and version control in practice 16

Characteristics

• Model content divided into separate files

• Files are transferred to VC Repository

• All users use private EAP

• VC locking on “package” level

• VC Configuration management

VC Repo

EA “meta data” &Model structure

EAP

EAP

EAP

ww

w.d

ivetr

o.n

l

Out of box DBMS VC Repo Combi

Multiple users (disciplines)

Re-use knowledge

Personal sandbox

Historical information (Model)

Historical information (Parts)

Alignment other deliverables

Pros & Cons

19/05/2017 EA and version control in practice 17

Not supported

Well supported

ww

w.d

ivetr

o.n

l

1. Out of the box

2. DBMS

3. Version control repository

4. Combination of DBMS and version control repository

Most common configurations

19/05/2017 EA and version control in practice 18

ww

w.d

ivetr

o.n

l

Combination DBMS & Version control repository

19/05/2017 EA and version control in practice 19

EAP

EAP

EAP

ww

w.d

ivetr

o.n

l

Combination DBMS & Version control repository

19/05/2017 EA and version control in practice 20

Characteristics

• EAP file is transferred to DBMS tables

• Model content (DBMS) duplicated into separate files

• All users use the same EAP

• DBMS locking on “row” level

• VC locking on “package” level

• VC Configuration management

DBMSEAP

VC Repo

ww

w.d

ivetr

o.n

l

Out of box DBMS VC Repo Combi

Multiple users (disciplines)

Re-use knowledge

Personal sandbox

Historical information (Model)

Historical information (Parts)

Alignment other deliverables

Pros & Cons

19/05/2017 EA and version control in practice 21

Not supported

Well supported

ww

w.d

ivetr

o.n

l

Configuration of DiVetro

• Consultants work at different locations

• Consultants don’t always have connection to DiVetro network

• Re-usable knowledge across models / customers

• Quick access to work of colleague (peer review)

• Multiple users work on the same model

19/05/2017 EA and version control in practice 22

ww

w.d

ivetr

o.n

l

Best practices DiVetro

1. Don’t use the default naming settings

2. Don’t put the EAP under version control

3. Choose logical names for version control ID

4. Don’t use standard VC commands (outside EA)

5. Don’t use “Check out branch” option

6. Make the model fit for purpose

7. Look before you leap

19/05/2017 EA and version control in practice 23

ww

w.d

ivetr

o.n

l

Questions?

19/05/2017 EA and version control in practice 24

Dennis Geluk

dennis.geluk@divetro.nl

+31 (0)6 13 476 892

+31 (0)26 443 67 90ww

w.d

ivetr

o.n

l

Parkstraat 74 | 6828 JL Arnhem

Recommended