This is indeed a good book and with plenty of examples using EA (with screen shots...)
One thing about making all of your requirements external, this can become a very time consuming model to maintain.
If you are supporting requirements in an iterative development environment, it may be better to use the following rule for determining if a requirement should be "internal" or external:
If the requirement applies ONLY to this object, it's internal,
While when the requirement applies to more than just this object, make it external.
Doing it this way MAY make your requirement management easier and allow it to be linked to your iterations...
I say MAY because I am in the midst of setting up this approach for my current project. The solution should involve version control, base-lining, creation of RTF documents, and HTML publication of the model.
I am currently reverse-engineering the system's requirement baseline (once again for a project that did not/was not able to take the time to define requirements.) I am documenting the modeling “process" as a UML model of EA domain objects and process use cases...
If ANYONE else is currently trying to/or is supporting requirements for an iterative development environment, I would not mind creating a separate discussion thread
David
