Using eaDocX there is a need to create an as best as possible repository. This automatically leads to better contents and better and more complete and consitent models, which in the end leads to less mistakes and misunderstanding
Though working with a repository might seem to take more time to realise a deliverable the pay back is when changes and improvements have to be made. Just by generating a new set of documents (or HTML pages) all stakeholders are up to par.
I think in the future architects will collaborate more and more through a repository and only need to generate documentation because some stakeholder will never learn how to interpret data in that repository.
I hardly encountered problems. Funding is easy because the initial investment is not that high and company-styled documents are produced within hours after installation. Normally I provide my customer with the profiles he needs and instructions to make him create the documents. Training takes around half an hour.
I needed some support from eaDocX; some of them where because of misunderstanding the manual, some because of bugs and some of which I don’t know anymore. In most situations I got helpful replies the same day, or the day after. In a number of cases I have send the repository and the document to support to obtain the right answers.
- I currently use the latest version of both EA (corporate edition) and eaDocx (professional edition)
- I personally use fixed licenses but when my customer is installing the software it depends on the situation and adoption rate. It is nice to have this flexibility (fixed/floating).
- Both tools are used by functional designers, software and enterprise architects and in some situations testers.
- During the time I used EAs’ RTF generator I only used a fraction of the tools available in EA. Since making nice output required a lot of experimentation. Now I decide depending on the knowledge level of my customer which of the tools are most appropriate and for those I create a profile. This means that I have a whole nest of profiles.
I use EA and eaDocX for all kinds of documents, like audit reports, requirement documents, software architecture documents, business process documents and organisational documents (describing roles and functions). I even use EA to keep notes that I might want to reuse in documents.