Objecteering/UML Version 5.3.0
– P07280 –
Objecteering/UML: Readme
1. Introduction......................................................... 3
3. Developments and technical problems corrected 6
This document provides you with all the information necessary for your first steps with the Objecteering/UML tool. It does not, in any way, replace the documentation provided with Objecteering/UML, but does provide important information, which will help you get off to a good start. We strongly recommend that you read this document before using Objecteering/UML.
Objecteering/UML SP3 patch P07280 has been tested on the following platforms:
· Windows NT4 SP6a (x86)
· Windows 2000 SP4 (x86)
· Windows XP SP2 (x86)
· Linux Red Hat 9 (x86)
· Linux SuSE 9.2 (x86)
The Objecteering/UML P07280 patch requires that Objecteering/UML 5.3.0 SP SP3 already be installed.
· Close all Objecteering/UML programs.
· Double-click on the "ObjecteeringUML_530_P07280_WIN.exe" file.
· A window summarizing what is to be installed then appears. Click on the "Next" button to install the patch.
· Click on "Finish" to complete the installation.
This patch deploys the following files:
· Binaries:
o baseadm.exe
o libObjecteering.dll
o objing.exe
o objingcl.exe
o wbaseadm.exe
· Resources:
o tpf/ascii.fmt
o tpf/html.fmt
o tpf/winword.fmt
o tpf/WINWORD/word.bot
o tpf/WINWORD/word.top
o tpf/HTML/html.bot
o tpf/HTML/html.top
· Modules:
o DOORS_V2.0.t.prof
o GenDocModule_V4.8.d.prof
o RequirementsAdmin_V2.0.t.prof
o RequirementsManager_V2.0.t.prof
o XMIModule_V2.2.h.prof
· UML Model Types:
o Default.ofp
o DefaultCpp
o DefaultCSharp
o DefaultJava
o DefaultRequirements
The Objecteering/UML P07280 patch requires that Objecteering/UML 5.3.0 SP3 already be installed.
· Close all Objecteering/UML programs.
·
Open a shell and decompress the
"ObjecteeringUML_530_P07280_LINUX.tgz" file and run the installation
using the following commands:
$ tar xzf
ObjecteeringUML_530_P07280_LINUX.tgz
$ cd
ObjecteeringUML_530_P07280_LINUX
$ ./SETUP
· If the Objecteering/UML variables have not been initialized, the installation procedure will ask you to specify the Objecteering/UML installation directory that is to be updated.
· An installation summary then appears, asking you to confirm deployment of the Objecteering/UML.
This patch deploys the following files:
· binaries:
o baseadm
o baseadmcl
o objing
o objingcl
· Resources:
o tpf/ascii.fmt
o tpf/html.fmt
o tpf/winword.fmt
o tpf/WINWORD/word.bot
o tpf/WINWORD/word.top
o tpf/HTML/html.bot
o tpf/HTML/html.top
· Modules:
o DOORS_V2.0.t.prof
o GenDocModule_V4.8.d.prof
o RequirementsAdmin_V2.0.t.prof
o RequirementsManager_V2.0.t.prof
o XMIModule_V2.2.h.prof
· UML Model Types :
o Default.ofp
o DefaultCpp
o DefaultCSharp
o DefaultJava
o DefaultRequirements
· It is now possible to run a check-out in command-line mode on requirements and dictionaries.
· Correction of a crash when running successive calls to the Object:objectMap.values and Object:objectMap.get() J methods.
· Correction of a problem causing diagrams to appear empty.
· Correction of a crash that may occur upon running the 'Check Model' command on sequence diagrams.
· Correction of a crash occuring when removing tagged values on AssociationEnd
· AssocationEnd identifiers are now taken into account by the “Check a database’s identifiers” command.
· Correction of an issue concerning "document link insertions" during RTF file generation.
· Deletion of useless "<BR>" markers during HTML file generation.
· Improvement in RTF format sublist generation.
Note: This
improvement concerns the use of the following tags:
"\NLIST n\", "\LIST n\", "\LITEM n\" and
"\NLITEM n\" where "n" is an integer ranging from 1 to 9.
"n" is used to determine the level of the current list (or sublist).
Every sublist must end with "\END_SLIST\".
The main list must end with "\END_LIST\".
Each item in the list must be an "\LITEM n\" where "n" corresponds to the opening "\LIST n\". (same for the "\NLITEM n\" with "\NLIST n").
Note: "\NLIST 1\" corresponds to an "\NLIST\" and "\LIST 1\" to a "\LIST\".
· Improvement in HTML format list generation, in accordance with the W3C standards.
Note: This
improvement concerns the use of the following tag:
"\END_LITEM\" is used to correctly close a list line (ordered or not)
during HTML generation.
This allows the generation of "</LI>" in HTML documentation.
· Correction of a regression in the description notes generation.
· Corrections in the consistency check on ‘use’ links and elements impacted by modifications made to 'use' links during Diff/Merge operations.
· Correction of a problem concerning the naming of operations during the automatic merge of ‘SequenceMessages’ .
· Links are now created after the elements they depend on during the automatic merge.
· Errors occurring during an automatic merge are now displayed in an end of session report.
· Correction of a crash when importing packages that contain diagrams not properly closed in J.
· Correction of crashes which happen when navigating on the merged browser.
· Control added to the check model to verify the presence of multiples communication links on an element.
· Correction of a crash concerning Sequences Diagrams during MultiUser import.
· There is no more subsistent confirm windows during automatic merge.
· Update of the version in accordance with DOORS 2.0.t
· It is now possible to import DOORS modules containing utf-8 characters.
· Improvement in the management of user rights during export operations.
· General improvement in the import operation.
· Carriage returns are no longer systematically added at the end of lines in imported notes.
· Tagged values and stereotypes belonging to dependency and implementation links are now correctly imported.
· The parameters of tagged values belonging to associations are now correctly imported.
· Constraints on qualifiers are now exported.
· Improvement of export performances.
· The complete generation paths should be defined to avoid the generation of files in the hierarchy of the Objecteering/UML server (the directories '.' and '..' of a PC correspond to the directory from where the binaries are launched).
· After documentation generation in EMF format, only Word 97 (or upper versions) can correctly open the generated document. Previous versions of Word cannot read the format of the images.
· If step 4 of documentation generation is not carried out properly, you must check and correct the settings of the "Editors" module parameters.
· Note formats are retained (blank lines are no longer removed).
· The integrated explorer in the HTML documentation generated by Objecteering/UML only works in Microsoft Windows and with recent browsers (IE 5.5, Mozilla 1.2 or upper versions). It does not function with Opera.
· The earlier version of the module authorized the existence of two elements with the same name within the same parent element. This is no longer possible with the RequirementsManager module.
· If the traceability editor is hidden and another editor is closed (diagram, requirement, ...), the traceability editor reappears but may not function correctly. To correct this, you should close and re-open Objecteering/UML.
· To retain traceability links between the UML model and requirements during an XML import, the UML model should be imported first and then the requirements and dictionaries.
· For documentation generation, the "Xml Export" template must not be used, as it will not work. It is used internally for XML exports.
· Requirement and dictionary editors
o The sort by date function works correctly in the English format.
o If the sort function in an editor appears to be inactive, you should simply close and re-open the editor.
o Enumeration order is taken into account when sorting properties typed by enumerations. You should order your properties according to this strategy.
o In the requirements or dictionary spreadsheet editors, after validating a multi-line field using the TAB or ENTER keys, you should press the TAB key again to be able to continue browsing using the keyboard. This is also true after canceling using the ESCAPE key.
o To validate the edition of a multi-line field, the CTRL-TAB key combination must be used (or click outside the field).
· Tips
o The shrink/expand function (activated through the "+", "-", "/"and "*" keys and the buttons on the bottom right of the editor) are used to display either the entire contents of term and requirement fields, or simply the first line.
o To insert carriage returns and tabulations, use the SHIFT-ENTER keys for carriage returns and the SHIFT-TAB keys for tabulations.
o To create (or delete) lines, you should simply use the INSERT (or DELETE) key. Use of the TAB key on the last line and last column automatically adds a new line.
o In the editor, if you wish to select the equivalent of an element in the hierarchy, you should use the CTRL-LEFT CLICK on the line in question.
· The "Edit and Reverse documentation" command will only be operational if Microsoft Word is installed.
· We recommend against:
o Running an XMI reverse via objingcl.
o Annotating state machines, as this can lead to problems during the file parsing phase.
· State machines and states are not correctly reversed, and their names can be lost, which can lead to the failure of consistency checks.
· An XMI import operation containing C++ or Java code, which has characters likely to be interpreted as markers, interrupts the import operation.
· If your Objecteering/UML server installation directory has been indicated using a UNC path instead of a mapped network drive letter, the import command of the XMIModule will not run. To make this work, you will have to map a network drive letter on your Objecteering/UML server installation directory and modify: RevXMI_NT.bat located on <Objecteering server installation directory>\modules\XMIModule\2.2\bin\Windows\Nt\ as follows:
o Original file:
@SET SP_CHARSET_FIXED=YES
@SET SP_ENCODING=XML
cd /D %4
SET SGML_CATALOG_FILES=.\bin\Windows\xml.soc
.\bin\Windows\parser %1 %2 %3
o Modified file:
@SET SP_CHARSET_FIXED=YES
@SET SP_ENCODING=XML
cd /D <Objecteering server installation directory mapped
network drive letter>\modules\XMIModule\2.2.g
SET SGML_CATALOG_FILES=.\bin\Windows\xml.soc
.\bin\Windows\parser %1 %2 %3