CORAS Risk Assessment Platform

File Release Notes and Changelog

Release Name: CorasTool-2.0.3

Notes:

                              CORAS Tool 2.0.3

   If upgrading from a beta version of the CORAS Tool 2.0, please read
   the section below on upgrading!

CONTENTS

    1. What's new in CORAS Tool 2.0.3
    2. Requirements
    3. Installation
    4. Upgrading from older versions
    5. Running the CORAS Tool
    6. Stopping the CORAS server
    7. Users and passwords
    8. Creating a backup of the database
    9. User forums and contact info

1. What's new in CORAS Tool 2.0.3

   Changes in 2.0.3 (November 27th 2005):
     * Fixed some relationships in CORAS UML editor which were not
       working properly
     * Fixed bug in risk matrix generation caused by hidden columns in
       value definitions table

   Changes in 2.0.2 (November 23rd 2005):
     * Fixed disappearing icons in CORAS UML editor diagrams
     * Fixed a crash related to web browser in Linux
     * Fixed Linux/Unix startup scripts
     * Various other minor bugfixes

   Changes in 2.0.1 (October 29th 2005):
     * Added workaround for a problem with storing files from the CORAS
       UML editor in the internal XML database
     * Fixed issue which prevented hiding of table columns in table
       editor
     * Various other minor bugfixes

   Changes in 2.0 (September 26th 2005):
     * New and improved user interface, replacing the old web-based
       client
     * Updated CORAS risk analysis methodology and table formats based on
       usage experience and feedback
     * Integrated editor for CORAS UML models, enabling documentation of
       risk scenarios using the CORAS UML language without the need for a
       separate UML tool
     * Added support for UML use case and sequence diagrams, e.g. for
       HazOp analysis
     * Major improvements to table editor, e.g. auto-completion of
       content as you type and the ability to add, delete, hide and show
       columns
     * Support for import and export of risk analysis projects and
       experience packages, including import from CORAS Tool version 1.0
     * Versioning of information, making sure the whole change history of
       your data is available
     * A number of other bugfixes and enhancements
     * Databases from beta versions of the CORAS Tool 2.0 require
       conversion, please read the section below on upgrading!

2. Requirements

   To run the CORAS Tool, you need Java version 1.4.2 or newer. If you do
   not have Java installed, downloads and installation instructions are
   available at http://java.sun.com/j2se/. The CORAS Tool is
   developed and tested using Java SDK 1.4.2, which is available at
   http://java.sun.com/j2se/1.4.2/download.html.

   Make sure the JAVA_HOME environment variable is set up properly,
   otherwise you may be unable to run the CORAS Tool. On Windows 2000/XP,
   this can be done in

     Control Panel -> System -> Advanced tab -> Environment variables

   Click 'New' to create a new environment variable. In the field
   'Variable name' enter JAVA_HOME, and in 'Value' enter the Java
   installation location, e.g. C:\j2sdk1.4.2.

3. Installation

   To start the installation, run the command 'java -jar
   CorasTool-2.0.3-installer.jar' in a command window (without the
   quotes). In Windows, you should be able to run the installer by
   double-clicking on the installer jar file.

   Follow the instructions in the installer program. Select a location
   where you wish to install the CORAS Tool, and which elements of the
   tool to install. By default, both the client and server will be
   installed. You may also choose to install a prepackaged set of
   reusable risk analysis experiences as well as tools to convert
   databases created with beta versions of the CORAS Tool 2.0.

   The installation will create a directory which contains a number of
   subdirectories, depending on which elements you chose to install:

   bin
          scripts to run the CORAS Tool client and server

   client
          the CORAS Tool client

   server and lib
          the CORAS Tool server and database

   admin
          tools to perform administrative tasks, e.g. database backup and
          restore

4. Upgrading from older versions

   Please note that as the table formats changed in the final 2.0 version
   of the CORAS Tool, tables from old versions of the CORAS Tool (2.0
   beta versions) may not work fully in this version of the CORAS Tool.

  4.1 Upgrading from CORAS Tool 2.0 beta version

   Note: Conversion of databases from beta versions of the CORAS Tool 2.0
   is currently only supported in Windows.

   Install the CORAS Tool 2.0.3 as described above, and make sure to
   include the 'Convert' module which contains tools to convert the old
   database format.

   *** IMPORTANT: Choose a different installation directory than the old
   CORAS Tool to avoid overwriting the existing data files!

   The database files from the old CORAS Tool are located in the
   subdirectory

     server\default\data\exist\data\

   of the old CORAS Tool installation directory. After installing the new
   CORAS Tool version, copy the contents of this directory (*.dbx) to the
   corresponding subdirectory of the new CORAS Tool installation. Then
   run the convert.bat script located in the admin directory.

  4.2 Upgrading from CORAS Tool version 1.0 (web interface)

   To export data from the CORAS Tool version 1.0, you need the "Export
   Extension" (see the coras.sourceforge.net Download page). To export a
   risk assessment package (not project!) or experience package, open the
   package in the web interface, click the 'Export' link and save the
   resulting XML to file.

   To import the data into the CORAS Tool 2.0.3, select File->Import and
   either 'Import risk analysis project' or 'Import experience package'.
   Select the file you saved earlier and click Open. This will create a
   new risk analysis project or experience package with the imported
   data, which you can then open in the regular fashion.

5. Running the CORAS Tool

   The bin directory contains the scripts needed to start the CORAS
   server and client. To run the CORAS server under Windows, run the
   start-server.bat file in the bin directory, e.g. by double-clicking on
   it in File Explorer. To run the server under Linux/Unix, go to the bin
   directory and type sh start-server.sh.

   If Java is installed properly, the CORAS server should now be up and
   running. The CORAS server will print out status messages in a console
   window. Wait until the server is ready - it will print out a line
   similar to:

     13:51:33,551 INFO [Server] JBoss (MX MicroKernel) [4.0.2 (build:
     CVSTag=JBoss_4_0_2 date=200505022023)] Started in 11s:513ms

   Once the server is ready, you can launch the CORAS client application.
   To run the CORAS client under Windows, double-click on the client.bat
   file in the bin directory. To run the client under Linux/Unix, go to
   the bin directory and type sh client.sh.

   Log in to the CORAS Tool with username default, password default.

   *** IMPORTANT: *** Please change the password of the users
   immediately! See the section on users and passwords below.

6. Stopping the CORAS server

   When you are done using the CORAS Tool, stop the server by hitting
   Ctrl+C in the CORAS server console window.

7. Users and passwords

   Users, passwords and roles are defined in the files users.properties
   and roles.properties, which are located in the subdirectory
   server\default\conf of the CORAS Tool installation.

   To add a user, add a line on the form

     username=password

   to users.properties, and a line on the form

     username=user

   to roles.properties.

   The only supported roles are user and administrator, however currently
   the administrator role does not offer any additional functionality.

8. Creating a backup of the database

   The database files for the CORAS Tool are located in the subdirectory

     server\default\data\exist\data\

   To make a backup, first ensure that the server is not running (see the
   section on stopping the CORAS server above). Then run the
   backup.bat script (Windows only) located in the admin directory, or
   just copy the *.dbx files from the database directory to a safe
   location.

9. User forums and contact info

   You can subscribe to the coras-users mailinglist or read the
   mailinglist archives at:
   http://lists.sourceforge.net/lists/listinfo/coras-users.

   For updates and news about the CORAS Tool and other CORAS-related
   events, please visit the CORAS webpage at
   http://coras.sourceforge.net/.

   Fredrik Vraalsen
   SINTEF Information and Communication Technology
   Pb 124 Blindern
   N-0314 Oslo, Norway
   E-mail: fredrik.vraalsen@sintef.no
   Phone: (+47) 22 06 73 45 (office)


Changes: