The benefits of using RDF to define document content, and the generation of well formatted documents. 1 page version.

1. We have a workable method for creating presentable documentation that accurately and consistent
portrays architecture with defined semantics, in diagrams and text, under version control. Once content
is structured, we can easily create alternative extracts and presentations, and they will be consistent.
The problem with documents Inferencing can be useful to complete
relationships, saving considerable time in entry;
The normal approach to delivering large and likewise to highlight any logical gaps and
programmes and projects is document-centred. inconsistencies (which are less likely in this
Ensuring consistency across a set of documents approach).
is ridiculously hard. Our models are kept in a Subversion repository,
Finding any accurate representation of a live allowing full version control with history, and
architecture is also hard. The conventional can be transferred as text files if necessary.
representation of (solution & enterprise)
architecture as Visio diagrams embedded in Documents, reloaded
Word documents is woeful; the diagrams are
semantically weak and rely on the support of We create documents in stages: first we make an
thousands of words in the surrounding HTML template for the document type, then we
document, often inconsistent. populate the template with content from the
model (this is also done by the inference
Life is better with models engine), finally we process the HTML with
PrinceXML, applying corporate styles to create a
paginated, formatted PDF. Thus we can create
many documents in the same style, and many
styles of document from the same content.
Diagrams are generated by some relatively
simple bespoke code that queries the model and
uses a layout program to create diagrams that
conform acceptably with the Archimate style
and notation; the graphic styles are also defined
by a model and hence reusable.
We defined the BI solution architecture not as a
document, but as an ontology that defines all the
elements following the Archimate approach:
Actors, Roles, Business Services, etc.
Each element has attributes such as the Entry
Criteria for a service, or the Recommendation for a
technology choice. With this structure in place,
defining the architecture elements becomes
much easier, as you are filling in a template, and
can easily navigate to other elements.