In the late 90's I worked on a modeling and transactional coding (just pre-EJB) framework that started with use case patterns tied to BCE analysis patterns on the front end. But there were then two more levels of architectural models before you had worked out all the implementation decisions! Not to mention the possibility of recursing into analysis of the subsystems of a large system.
In order to be able to flexibly handle changes in architectural and implementation decisions, you need to have an explicit record for what those decision were. To me, "agile" really requires being able to quickly and efficiently move back and forth between all these levels between requirements and code.
E-mail addresses are not publicly displayed, so please only leave your e-mail address if you would like to be notified when new comments are added to this blog entry (you can opt-out later).