Sparx Systems Forum
Enterprise Architect => General Board => Topic started by: OldEm on February 13, 2008, 05:00:33 am
-
I'm on my 28th day of trial and at yesterday's team meeting the project managers asked, "If I add a Use case or change the scenario for already built code, how do my designers/programmers know that I just made a change and that they have to modify their code?" Anyone have a change notice process that works for their team?
-
EA has a mighty build-in model compare feature (which has even been improved with 7.1 but I could not test that). Search the help file for "baseline".
-
Anyone have a change notice process that works for their team?
Another idea (maybe used in conjunction with Thomas's): Search the help for "red triangle"...
-
Search the help file for "baseline".
We use winmerge to compare code files so Baselines and compare sounds like a good method as described in the manual.
I created a baseline package, changed some of the elements, went into manage baselines, clicked show differences - and Ea crashes.
Tried this a few times with a eap file project and with my database respository project. crash each time. bummer.
I'm off to look for red triangles...
-
Which build were you using when EA crashed?
-
Obviously the latest (trial).
-
Then a retest with 7.1 would be in order; the most recent trial would appear to be version 7.0.
-
My best practice is to set Phase globaly for new elements in any iteration of our development process and set Version the same. When we do a change, we change the version to current Phase.
That means, if you want to filter all elements changed and added in last phase, just use current phase as a version parameter.
Is it helpful and understandable?
-
Then a retest with 7.1 would be in order;
How can I get 7.1?
But "Compare baselines" should work in 7.0 build 818 without crashing EA.
-
My best practice is to set Phase globaly for new elements...
How do you set the phase globally?
This sounds like a good method for new elements. When I presented the use of EA to the team, managers asked if they could use those Phase and version fields to manage change communication to developers. I had to say I didn't know.
Here's a scenario: A Use case scenario is added in phase 1.1 and version is set to 1.1 for UC and realization model.
Later, the manager updates this UC to phase 1.2 with two new alternate paths. (not a new element) Clearly the designer/programmer can find the 1.2 version of the UC but how do they compare it to 1.1 to see that what was added was the 2 alternate paths?
(I think the answer is compare baselines using 7.1 beta release...)
-
Yes, 7.1 is only available in beta.
Due to the way that EA releases come out, 818 will be the final build of 7.0. The current beta version of 7.1 is 825.
The reason there is no trial version of 7.1 is that beta versions are only available to registered users. When 7.1 reaches production a new trial version will be released - assuming that the usual pattern is followed.
So for now, someone else will have to retest the issue on the beta if you are still using a trial version.
David
-
That's so mean... as if the current user base is going to want static code visualization or deep runtime insight.
It would be extremely helpfull to have access to early VS2k8 MDG Technologies, particularly if EA is to remain my preferred UML tool recommendation.
Guess I should just retire,
Kevin xxx
-
Then a retest with 7.1 would be in order;
The EA crash on compare occurred with the corporate version.
When I select professional version (I'm still using the trial) I can compare the current model with an XMI file. No crash! The comparison summary in the elements tree and detail listing on the right is sweet - for me only.
Even if the 'baseline compare' worked in the corporate version - how is the baseline shared by the team?! If a manager saves a baseline and then changes the use cases and requirements for the next iteration, how do I as the designer/programmer see the manager's baselines? They're saved to a directory on the manager's personal computer.
I'm feeling like it's just way too hard to use this tool in a team framework.
-
I guess it's hard with all tools. Usually you find way to accommodate with the tool. One way is to set triggers in the database that monitor changes (I faintly remember a discussion on this in the past).
-
If a manager saves a baseline and then changes the use cases and requirements for the next iteration, how do I as the designer/programmer see the manager's baselines? They're saved to a directory on the manager's personal computer.
I thought baselines were saved in the repository (Corporate ed. only) reachable for everyone. Weren't they?
-
I thought baselines were saved in the repository (Corporate ed. only) reachable for everyone. Weren't they?
This is what I was told by EA:
1. Failure on compare "is a known issue" [in the corporate trial version], "and has been fixed for the next release" [of the trial version] "( Full release doesn't have this issue)"
2. "All baselines are stored in the database, and not as external files."
I have not verified either of these claims but I purchased a license based on them and I'm looking forward to it arriving.
--RonE
PS; Jan, how do you set the phase globally?
-
Ron,
Open the Tools | Options | Objects dialog. You'll see version and phase near the top. These settings become the default for all your models until you next change them.
David
-
And in fact it is not global, it is per user and all users have to set it same.
-
To change a property (like phase) globally:
Right click on the package
Package Control --> Update package status
Here we can change the status, version and phase and modified date of the contained elements.
-
And in fact it is not global, it is per user and all users have to set it same.
Quite correct!
I've amended my misleading post.
-
Does anybody know if baseline -> show difference is working in 7.1? This function is critical for us. I have tried it with a very simple model, but it still crashes on 7.0 build 818.
When is the release of 7.1?
-
The release of v7.1 itis TODAY, but I'm not experienced any problem with the model compare in build 818...
-
The model compare worked for me in 7.0 but not on baseline. But in v7.1 it works!