rmtoo-art-oopricing

NAME
DESCRIPTION
DETAILS
CONFIGURATION
LIMITATIONS
SEE ALSO
AUTHOR
COPYRIGHT

NAME

rmtoo-art-oopricing - requirements management tool: pricing table in ODF format

DESCRIPTION

The rmtoo requirement management tool has the ability to output all requirements which directly or indirectly depend on topic as a commercial used pricing / bid spreadsheet. The spreadsheet is outputted in ODF - which can be read by e.g. OpenOffice.

DETAILS

rmtoo output pricing module is designed for the following procedure of commercial bidding:

Requirement Specification
The first step is to write down the requirements. During writing and organizing requirements remember to put requirements in topics that one topic including subtopics form understandable and complete set of requirements.

Create spreadsheet
Based on one topic (and of course all it’s depended child-topics) run rmtoo which outputs the spreadsheet in ODF format.

Send out spreadsheet
Send out the spreadsheet to all possible vendors. They can fill the following things for each requirement: compliance (fully, partial and non-compliant), price (broken down to dayrate, number of days and material) and the chosen (commercial) link to the dependent requirement.

Example: The Documentation for Training depends on training and documentation. At vendor A the (whole) documentation is done inside the documentation department while at vendor B the training documentation will be done by the training department. Therefore there is the need to reflect the different dependencies a vendor might implement a requirement. In case of vendor A the documentation for training is included in the documentation budget while for vendor B the training documentation is included in the documentation budget.

Collect spreadsheets
After a while, collect the filled in spreadsheets from the vendors. It is now easy to compare the prices and dependencies. There are additional modules for supporting the evaluation. Please consult rmtoo.7 for a full list of available and planned modules.

CONFIGURATION

The configuration for this output module goes (as all other output module’s configuration) in the output section of the configuration file.

The first element (the key) must be oopricing1. This must be followed by output_filename (without the suffix).

Example

"oopricing1": [
{
"output_filename": "artifacts/reqspricing"
}
],

LIMITATIONS

Currently the output module can handle at maximum 702 requirements which covers spreadsheet columns A up to ZZ.

Some old OpenOffice versions (e.g. 2.X) limit the number of rows (which is also the number of requirements) to 256.

SEE ALSO

rmtoo(7) - overview of rmtoo including all references to available documentation.

AUTHOR

Written by Andreas Florath (rmtoo@florath.net)

COPYRIGHT

Copyright © 2010-2011 by flonatel (rmtoo@florath.net). License GPLv3+: GNU GPL version 3 or later