VI.1 Introduction and Goals
The need to deliver an arc42 solution architecture in different formats was the primary driver that gave birth to docToolchain. As a technical person, I saw the value of text-based documentation. However, other stakeholders wanted to have the documentation:
- "Where all other documentation is"—in a wiki
- "How we always document"—with MS Word
- "In a revision-safe format"—as PDF
Soon, after fulfilling these needs, I noticed that it's quite hard to update changing UML diagrams. "Couldn't this be automated?," I thought to myself and created the exportEA task as a simple Visual Basic Script.
I didn't plan docToolchain on a drawing board. Instead, it evolved in an agile way; that is, through the requirements of the users.
Together with Dr. Gernot Starke, I gave a talk about this approach, and received some interesting feedback from the audience, such as "… but I don&apos...
