Author Topic: Version Control and shared packages (Read 5033 times)

protput · « **on:** July 23, 2009, 07:07:27 am »

In the EA User Guide about version control, there's a brief explanation about 4 ways in which this facility might be used:
Single shared model, Multiple private models, shared packages and standard packages.
Is there somewhere a doc or guide that explains those 4 ways thoroughly?

thanks in advance.

«Midnight» · « **Reply #1 on:** July 23, 2009, 08:03:33 am »

Check the Sparx Resources page. Use the link near the top left of any forum page. There should be at least one tutorial and white paper, and perhaps a walkthrough or two.

If you still need help search the forum. Use the search button just below the upper forum menu on the left, not the 'quick' search text box on the right. You should find some posts with links to resources you might have missed.

Paul Lotz · « **Reply #2 on:** July 24, 2009, 05:04:42 am »

Right! There is a version control white paper available in the White paper Repository http://www.sparxsystems.com/resources/whitepapers/index.html.

RoyC · « **Reply #3 on:** July 24, 2009, 08:42:19 am »

There is a reference to the Version Control white paper in the Version Control & Team Deployment Help topic. However, I have added another reference to it underneath the table that Protput talks about.

protput · « **Reply #4 on:** August 05, 2009, 04:53:40 am »

Hi (sorry for bumping this thread again),

I browsed through most of the papers but didn't really find what I'm looking for. I was hoping to find some more info about do's and don'ts when sharing/reusing packages.
Like e.g does one should adhere to CCP,REP,CRP principles and all other OO related stuff?

Does anyone have some more insight about this matter?

Thanks in advance 8-)

Geert Bellekens · « **Reply #5 on:** August 05, 2009, 04:46:38 pm »

I'd love to help, but I don't know what you mean by

Quote

CCP,REP,CRP principles and all other OO related stuff?

Care to elaborate?

Geert

protput · « **Reply #6 on:** August 05, 2009, 06:32:29 pm »

Quote

I'd love to help, but I don't know what you mean by
Quote
CCP,REP,CRP principles and all other OO related stuff?
Care to elaborate?

Geert

Hi Geert, these are a few principles of the package design principles:

CRP = common reuse principle which means all classes in a package should be reused together i.e packages should be focused
CCP = common closure principle which means classe that change together belong together i.e changes are confined within a few pacakges

I'm wondering if anyone using SparxEA are using the OO package design principles when designing packages, or in case he/she doesn't, made his/her own set of rules when designing pacakges.

«Midnight» · « **Reply #7 on:** August 05, 2009, 08:21:38 pm »

Quote

...
I'm wondering if anyone using SparxEA are using the OO package design principles when designing packages, or in case he/she doesn't, made his/her own set of rules when designing pacakges.

Can you please elaborate on the "the" you use to prefix the set of "package design principles" you reference? Are these principles part of the UML specification?

protput · « **Reply #8 on:** August 05, 2009, 10:00:15 pm »

Quote

Quote
...
I'm wondering if anyone using SparxEA are using the OO package design principles when designing packages, or in case he/she doesn't, made his/her own set of rules when designing pacakges.
Can you please elaborate on the "the" you use to prefix the set of "package design principles" you reference? Are these principles part of the UML specification?

Sorry for the confusion: "the" should be "those package design principles"

I don't think they are part of the UML specifications, but merely a set of guidelines for OO package design in general.
However, I've stumbled across those principles already a few times in books about UML: "pragmatisch modelleren in UML", "The elements of UML 2.0",... and some other books I don't remember by name.

Geert Bellekens · « **Reply #9 on:** August 05, 2009, 10:27:32 pm »

I think you are mixing up two entirely different concepts:

Package design
EA's version control mechanism.

I think those concepts have nothing in common.
In general you will not find much documentation about things like design best practices or guidelines on the Sparx websites.
Most of the documentation is (understandably) about how to use/configure EA.

Geert

protput · « **Reply #10 on:** August 05, 2009, 10:44:59 pm »

Quote

I think you are mixing up two entirely different concepts:
Package design
EA's version control mechanism.
I think those concepts have nothing in common.

Geert

No, I'm not mixing things up. I'm pretty much aware what version control is

However, if one doesn't design his packages well, sharing packages will be a pain i.e when it comes to the maintainabilty of the packages.

Sparx Systems Forum

News: