Problem workarounds

Possible workarounds and help with some problems are described below.

Log files

Information is logged in three log files.

  • Application errors are logged in ~/Library/Logs/rCoach One.error.log. Open the Console window to view the file.
  • Application information and events are logged in ~/Library/Logs/rCoach One.info.log. Open the Console window to view the file.
  • XML validation errors and messages are logged in ~/Library/Application Support/rCoach One/validationMsgs. The log file can be opened from the application main menu, Editor > Open XML Validation Log.

Unable to analyze a Specification due to problems with the DTD

In order to analyze a Specification, the application must have access to a Document Type Definition (DTD) on the computer. The DTD was installed with the application.

  • Check that the Document Type Definition (DTD) rCoach.dtd exists in the directory /Library/Slingblade/rCoach. Check that the file has the right permissions, a user must be able to read the file. Open the System Information window for rCoach.dtd and check the read permissions. A new DTD is installed by executing the rCoach One installation package. The Data Repository is unaffected.
  • Open the Specification rules view in the application main window. Check that the DTD-versions textfield value is identical to the value found in the rCoach.dtd statement <!ATTLIST rc:dtd-version id CDATA #FIXED "1.2">. The correct value is usually "1.2" or above.

Unable to plot graphs for attributes

A Specification must be stored into the Repository in order for a user to plot attribute graphs. This is the natural workflow for releasing new versions of a Specification. When a new version of a Specification is stored into the Repository, there are no attached attributes. Attach attributes to a new version by:

  • Make sure that the attributes and their values are defined in Settings… > Attributes.
  • Analyze the new Specification revision and store the revision into the Repository.
  • Load the new Specification revision from the Repository.
  • Open the attributes table by Navigate > Attributes in the main window toolbar. All requirements should be listed in the table without attributes. Click the Option > Inherit button to select which revision (usually the previous one) to inherit from. This operation cannot be undone, but attribute values can be changed for all requirements.
  • Open the graph view through Navigate > Graph. Select which attribute to plot by the Graph button in the main window toolbar. There should be submenus that contain attributes attached to the requirements.

Related Topics

Define requirement attributes

Legal and illegal characters

Contents