×

Warning

JUser: :_load: Unable to load user with ID: 558
Sunday, 08 November 2009 13:32

Creating marvelous EA documentation using LaTeX

Written by
Rate this item
(3 votes)
Read 9103 times Last modified on Thursday, 28 January 2016 00:06
sparxsystems

Sparx Systems


99 Albert Street
Creswick,
Victoria
3363
Australia
P: +61 3 5345 1140
F: +61 3 5345 1104
 
Sparx Systems specializes in high performance and scalable visual modeling tools for the planning, design and construction of software intensive systems. A Contributing Member of the Object Management Group (OMG), Sparx Systems is committed to realizing the potential of model-driven development based on open standards. The company’s flagship product, Enterprise Architect, has received numerous accolades since its commercial release in August, 2000. Enterprise Architect is the design tool of choice for over 740,000 registered users worldwide.

community.sparxsystems.com

3 comments

  • Comment Link Archimetes Friday, 10 February 2017 17:49 posted by Archimetes

    Hello,
    do not know if this is still actual, but we've made an add-in capable of producing LaTeX documentation.
    The template is fully customizable, plain text, and may produce other formats as well.
    Have a look at http://www.archimetes.com/introducing-repodoc.html if interested.
    Regards,
    Jan

  • Comment Link beginner Tuesday, 18 June 2013 09:40 posted by beginner

    Hi John,
    Sorry for the late reply, but I got not informed about new posts.

    Well, in the time since publishing this article I have introduced a LaTeX based documentation for one customer. And it works really good. However, as it was a dedicated development I an not publish details. But basically it started with the framework published here.

    You may ask me details via PM.

    Thomas

  • Comment Link John Daragon Thursday, 23 May 2013 13:01 posted by John Daragon

    We're looking quite seriously at the idea of using LaTeX for technical documentation. My day job is in a large organisation which makes heavy use of Microsoft Word templates, which don't seem to be a very good fit for our problem domain. I'm keen to see our programming documentation sit in the same source control system as our code, and LaTeX seems to fit this model really well.

    I wonder if you've published anything on the EA end of this operation - guidelines on the extraction of model data?

    jd

Login to post comments