usage

[nfactorial]

Are there any tutorials available that demonstrate examples of applying EA to a project.

The documentation only discusses the various options available rather than how the features may be applied to produce a package.

Currently (as a programmer) I'm just laying out some classes and their interfaces but finding, although the view is nice enough, it's actually quicker to design without it. Which must mean I'm not using it properly?

I do realise the package is meant for more than just class\interface design, there is use-case and requirements analysis as well (amongst other things) but these I am not as familiar with, and the lack of a good intro means I'm currently ignoring ithem.

Thanks,
n!

[mbc]

You are entering the exciting world of development processes , a field which have as many opinions as there are developers.
EA does not force you to use a specific process. In that way it is (wisely) very flexible.
Personally, I use an adaptation of the Unified Process. If you are interested in that, I recommend the book "Applying UML and Patterns" by Craig Larman.

UML is just a notation. Without a process it isn't very useful.

Mikkel

[nfactorial]

Ok, I currently write my analysis\design reports with Word. It works ok, but some things are bit difficult to describe in words rather than code. I was hoping EA would provide a better way of presenting such information, instead of struggling with the flat document format

I will take a look at the book you recommended, thanks!

n!