Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - OldEm

Pages: [1]
1
General Board / Re: Model change notice
« on: February 20, 2008, 03:59:33 am »
Quote
Quote

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?

2
General Board / Re: Model change notice
« on: February 14, 2008, 10:56:25 am »
Quote
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.

3
General Board / Re: Model change notice
« on: February 14, 2008, 07:42:05 am »
Quote
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...)



4
General Board / Re: Model change notice
« on: February 14, 2008, 07:29:58 am »
Quote
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.

5
General Board / Re: Model change notice
« on: February 13, 2008, 07:02:55 pm »
Quote
 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...

6
General Board / Model change notice
« 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?

7
General Board / Re: Export Analysis Diagram in Use Case Documentat
« on: February 15, 2008, 04:00:23 am »
If you don't need RTF, Select the HTML documentation; select the use case package under which you have the analysis diagram; generate. You will get your use case with analysis diagram (robustness?) and sequence diagram - everything in the package including a listing of all the elements.

8
General Board / Re: subversion source control check in error
« on: February 11, 2008, 06:14:42 pm »
Thanks Thomas, Do you have any idea why EA locks the package when it's put under version control? Tortoise doesn't lock the subversion repository - locking is not something you have to do in subversion usually. I'm wondering if there is some way to tell EA to just use check in and checkout without locking.

9
General Board / subversion source control check in error
« on: February 11, 2008, 07:30:42 am »
I'm using subversion
svn --version
svn, version 1.4.6 (r28521)
  compiled Dec 20 2007, 16:19:22

and trying to get packages controlled using EA 7.0 build 818.

Here are the steps to test subversion acc. to the EA whitepaper.

2. Open a command prompt in DOS.
3. Navigate to the directory that will hold your Working Copy directory.
4. Add and commit the temporary file to the repository using the following
commands:
svn add <fileName>
svn lock <fileName>
5. Now, update the file from the repository, lock the file. To do this use the
following commands:
svn update <fileName>
svn lock <fileName>
6. Edit and save the file using an editor.
7. Now commit the file once more using the following command:
svn commit <fileName> -mA meaningful comment.

Here is what I had to do to get subversion to work from the command line.

4. insert a "svn commit <fileName>" between the add and lock
7. insert a "svn unlock <fileName>" before the last commit.

Without this unlock, I get an authorization failed error message.
This is the same error message I get from EA
when I try to perform a "check in" operation on a controlled package.
I have no trouble putting a package under control and keeping it checked out.
I just can't ever check it back in.

Is there some subversion or EA configuration that allows one to commit a locked file?

Thanks,

10
Bugs and Issues / Re: baseline notes
« on: February 19, 2008, 01:19:09 am »
Quote
The functionality does not exist, so you have to define what you want and submit a feature request.

OK

Keep the timestamp but take it out of the note field. Make it a non-editable attribute somewhere else; Why edit the creation date anyway?

Let users type a string (no carriage return) in the Note field. You can keep the Note name. It's a one-line note.

11
Bugs and Issues / Re: baseline notes
« on: February 18, 2008, 02:18:18 pm »
An added Note - i've got millions to share around - When I click on create baseline, I would like a small place to enter a comment about what this baseline represents - other than a time stamp.

Not a big deal but when I click in the text field and the cursor goes to the end of the time stamp, my reflex is to hit return to enter my $0.02 note - but that just generates the baseline. So then I have to write a paper note which the Wascally Wabbit takes and runs away.

12
Bugs and Issues / baseline notes
« on: February 15, 2008, 04:16:35 am »
Typing a carriage return while entering notes on a create baseline dialog executes baseline creation. There's no way to type a carriage return into the note - though the presence of the scroll bars on the right of the text entry box certainly suggest that was the intent.

Pages: [1]