Hi Oliver. I'm interested in both of the things you mention. I'm a book person and prefer bound publications to reading online or printing out / stapling / cobbling documents together.
I am a book person, too, when it comes to newspapers, short stories, novels, etc. Hate to read that online.
However I believe that reading technical documents and specifications is a task which requires a lot of cross referencing between different media just because I want the information compressed and backed up with actual examples. So linking information together from various sources, at least for me, gives the better (and quicker) results.
Anyway, just a matter of personal taste.
I can not comment on books directly dealing with EA. As mentioned above the online help and Sparx site gave some good ideas. Having worked with UML tools before is of benefit though EA is just more than a simple modelling tool.
However when it comes to modelling I always tend to suggest Craig Larman, "Applying UML and patterns".
Some people hated me for doing this telling me "Hey, I know what a class is and where it belongs to", almost immediately following to fail showing how to accomplish a well thought transition from requirements to technical specs
And now to the bad news: How you will be organising your model inside EA is something which no book will tell you and will be totally left at your own taste. This is highly dependent on your requirements, aims, stakeholders, etc.
Not fair, I know, because the main part of your initial work is exactly this, but you can get nuts and bolts at least here by asking
HTH.
Oliver
