Book a Demo

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 - radle

Pages: [1]
1
General Board / Re: Subversion Integration revisited ...
« on: May 10, 2008, 01:53:18 am »
Hi SwissSteve,

we used an easier way i think. For example we didnt give ids to each model package but rather for the whole project. I dont know whether it is the right way. And we dont have much experience in it. We just tried it out. But, it seemed to work.

Though we were a little bit disappointed about some points:
- we could not really edit the models parallel. You can work parallel when you switch to Offline and afterwards merge the xml files with an subversion client. I dont know how good this works.
- i dont see a way to update packages (in my working copy) recursively with sub-packages.

Well, here is what we did:

1. Create an empty new folder in repository using a subversion client.
2. Check out a working copy of this empty folder.
3. Start EA.
4. Create a new project in EA and save it in the working copy.
5. From the top package in the tree in EA choose 'Package Control' and 'Version Control Settings'. We gave an id for the whole project.
6. Make 'Add branch to version control' for each package in the tree. EA generates automatically folders where it keeps the xml-files.

For the *.eap file, either it was checked in automatically as we checked in the model packages or we checked it in 'manually' in a subversion client. I dont know any more. But it is in the repository and i think you need it in the repository for some not model related changes. I needed it for template packages (See the help). As i checked in the template package, it wasnt a template package in other developers working copy until i checked in the *.eap and they checked it out.

New developers had to check out the whole in an ordinary subversion client. Then start EA and open the EA-project. EA asks then to complete the version control configuration.

I hope, i could help you,
radle

2
General Board / Re: Format Text in Requirements / Use Case
« on: May 10, 2008, 02:28:12 am »
Hi,

i prefer using linked documents for describing scenarios and extension scenarios. The facilities of EA to write textual use cases are not enough ,i think. Besides the textual scenarios we want to have additional use case properties which are not supported by EA as goal level, minimum and maximum guarantees etc. as recommended in the book of Alistair about "Writing effective use cases". In a linked document you can add all this information to a use case.

We have discussed that it would be even better if it would be possible to use another editor than the built in rich text editor for linked documents. Does anybody know if this is possible?

Regards,
radle




3
Hi,

could somebody tell me how i get the 'note' of the properties window wider on the diagram? The matter is, i would like to use these built-in notes to describe an actor. Such a built in note would appear in the diagram as well as in a rtf-report. But unfortunately the note is displayed very narrow and long in the diagram. And i don't find a way to resize it. After reading your discussion, i also tried Alt+Z. But this makes it even narrower.

Regards,
radle

Pages: [1]