rmtoo-art-html - requirements management tool: html artifact
The rmtoo requirment management tool is able to output one topic and all possible subtopics including the containing requirements as a set of HTML documents.
Each HTML page is generated out of three parts: a header, a middle part and a footer. The header and footer are files which are copied into each HTML page and are the same for all pages. The middle part is automatically generated.
The header must include the whole HTML header including the opening html, full head and opening body tags.
The header may also contain the definitions for the css tags which are used in the middle part. See section CSS for more details.
The middle part is automatically generated. The topic description is used as a base for layout, text and requirements.
The footer can contain arbritary HTML code. It is copied to the end of each page. At least closing body and html tags must be included.
Mostly each element in a requirement has a separate CSS class. Therefore it is possible to format mostly every single bit of a requirement output as wanted. Please consult doc/html/header.html for an example. Here is a list of all special rmtoo CSS classes used by the requirements output. Of course additional standard CSS classes or attributes (like h1, h2, a and so on) can be defined.
The floating text which is specified in the Text: tag in the topic description.
A separator can be defined here. This ends up a requirement.
The tag (key) of mostly all requirements keys can be defined. Example: dlt_description
The tag (key) of mostly all requirements keys can be defined. Example: dlv_description
HTML output, three mandatory fields are needed:
output_directory output directory of the HTML files.
header HTML header file name.
footer HTML footer file name.
rmtoo(7) - overview of rmtoo including all references to available documentation.
Written by Andreas Florath (email@example.com)
Copyright © 2010 by flonatel (firstname.lastname@example.org). License GPLv3+: GNU GPL version 3 or later