Rational SoDA script and template index

25 Jul 2005
Updated 26 Jul 2005

	Get the downloads

Scripts and templates to extend IBM Rational SoDA

SoDA CSV Generator

The purpose of the Rational SoDA CSV Generator is to generate CSV files from the basis of specific SoDA templates. It does so by generating a SoDA report in the first step. In a second step, a post-processing step is carried out where SoDA commands, superfluous blanks and new lines are stripped of the generated report. Finally, the SoDA CVS Generator saves the result as a pure text file named by the SoDA template but with a ".csv" suffix. Using this utility, it becomes possible to extract information for complex SoDA reports in several phases. In a first phase, information is extracted into the CSV file suing the CSV Generator. In a second phase, the CSV file is used as input to a real SoDA report in order to generate end user documentation. This utility works with Rational SoDA Version 2003

Contributed by Dr. Einar W. Karlsen

SoDA Report Generator

The central/affiliated document concept of Microsoft Word allows users to split large SoDA reports into a central master Word document, which in turn is made up of a number of affiliated documents. The affiliated documents are either plain Word documents or generated SoDA reports. Currently when adopting such an approach to handle large SoDA documents, each affiliated report must in principle be generated individually, i.e. the user will have to open each document template, invoke the Generate Report command of SoDA and then wait for generation to complete. To avoid such mundane work, this small utility is provided that automates the report generation task by generating all the affiliated reports in one step. This utility works with SoDA Version 2003.

Contributed by Dr. Einar W. Karlsen

SoDA and RequisitePro templates

This zip file contains some SoDA and ReqPro templates. You'll notice by looking through them that using SoDA effectively requires that guidelines are established and followed in the relevant domains. Some of the SoDA templates even report red text warnings when the template can't output what it's looking for (useful for measuring adherence to domain guidelines). The UC report templates simply report a single use case from ReqPro. The model survey and SRS templates represent complete RUP artifact generation. The model survey template has an interesting section at the end called a Baseline Description. This is designed to report the exact configuration of all relevant data extracted from all domains used to create the model survey. This is very useful in light of the fact that you are likely to produce the model survey multiple times in a single SDLC. However, the Baseline Description is absolute and does not let us know where the changes have been made since the previous version.

Compare RequisitePro baselines

The iteration1.txt (and iteration2.txt) files represent output from a (not supplied) SoDA template on the ReqPro domain. These outputs are just absolute status of all relevant data in ReqPro. You would maintain these as the raw baseline description. Then use the example provided in example template to report the differences between the two baselines. Integrate this output with the model survey (or whatever) and you have detailed listing of the deltas from a previous version. For this to work you will have to use configuration management for the raw baseline descriptions. Use ClearCase (ala labeling) to control document templates, outputs (reports), and raw baseline descriptions.

Downloads

	Information about download methods

Back to top