New Features and Enhancements for Rational System Architect 11.4

Product documentation


Abstract

This document contains "What's New" information for the IBM Rational System Architect 11.4.

Content

Table of Contents:



Rational System Architect 11.4.3

Rational System Architect 11.4.3 released June 6, 2014

Major improvements provided in Rational System Architect 11.4.3

The following enhancements have been added in Rational System Architect 11.4.3.

Rational System Architect extension to Design Management

Rational System Architect extension to Design Management adds Jazz server-based capabilities to Rational System Architect allowing you to collaborate, trace, review, search, and document architecture designs.

The extension allows diagrams to be imported into the Design Management server, setup reviews to collaborate on the diagrams, and create reports. Reports can be displayed in a variety of formats, such as tables and bar charts. They can contain combined data from System Architect, Focal Point and Collaborative Lifecycle Management (CLM). Teams can collaborate with peers and stakeholders, and review models by using the dashboard. Teams can also use the linked data capabilities to establish lifecycle traceability between design artifacts and other lifecycle artifacts, such as requirements and work items.

See the Known Problems section in the Download document for limitations and known issues.

TOGAF 9 improvements

Rational System Architect now includes full support for TOGAF 9.1. Included are new diagram types, definitions, and relationships.

New diagram types
TRM Hierarchy
The TRM Hierarchy diagram is a hierarchical diagram that shows the classification of Technology Components by TRM Areas, and TRM Areas by TRM Domains. The definitions whose symbols appear on the diagram and the relationships among them are:

  • TRM Hierarchy comprises
  • TRM Domain comprises
  • TRM Area comprises Technology Component

The relationship between TRM Area and Technology Component is restricted to logical Technology Components, for example the “Is Physical” property is False.

The TRM Hierarchy diagram is data-centric, meaning that symbol relationships are synchronized with the underlying definition relationships.

Cross-domain Relationships
The Cross-domain Relationships diagram is a network diagram that is intended to show end-to-end relationships of definitions across every architecture domain. Definitions whose symbols appear on the diagram include:

  • Actor Application Component
  • Business Service
  • Data Component
  • Driver
  • Event
  • Function
  • Goal
  • Location
  • Objective
  • Organization Unit
  • Physical Application Component Version
  • Physical Technology Component Type
  • Platform Service
  • Process
  • Product
  • Role
  • Technology Component

The Cross-domain Relationships diagram is data-centric.

Network Infrastructure

The Network Infrastructure diagram shows deployed instances of IT assets, the relationships between them, and their relationships with those definitions (Technology Component, Data Component, Physical Application Component Version) that represent their respective types. Typically these would be configuration items imported from a Configuration Management Database.

The instance-level definitions on the Network Infrastructure diagram consist of

  • Database Instance
  • Device Instance
  • Operating System Instance
  • Physical Application Component Instance
  • Physical Technology Component Instance
  • Server Instance

Server Instance, Device Instance, and Physical Technology Component Instance can each be related to Location.

The Network Infrastructure diagram is data-centric.

New definition types
The following new definition types have been added in this release.
Physical Technology Component Instance
Represents an instance of a physical Technology Component.
CI Relationship
The CI Relationship is an explicit relationship that can link any pair of the instance definition types. It is used to qualify the nature of the relationship and to hold additional information that is often obtained from CMDB systems. An example of a CI Relationship would be to document that an Operating System Instance runs in a logical partition of a Server Instance.
CI Relationship Type
Used to classify a CI Relationship.
TRM Hierarchy
The topmost node in a TRM Hierarchy diagram. It is used to group one or more TRM Domains.
TRM Domain
TRM Domain is a high-level classification of Technology Components.
TRM Area
TRM Area is a classification of Technology Components that is between the TRM Domain and the logical Technology Component.

New relationships
The following relationship types are available in this release. In most cases, these relationships reflect the relationship names used in the TOGAF Content Metamodel.

  • has deployed instance / is deployed instance of
  • hosts / is hosted by implements / is implemented by
  • has version / is version of
  • supports / is supported by
  • produces / is produced by
  • located at / is location of
  • owns / is owned by
  • performs / is performed by
  • consumes / is consumed by
  • generates / is generated by
  • accesses / is accessed by
  • realizes / is realized by
  • encapsulates / is encapsulated by
  • supplies / is supplied by
  • resolves / is resolved by
  • participates in / involves
  • delivers / is delivered by
  • governs / is governed by
  • fulfills / is fulfilled by
  • creates / is created by
  • provides / is provided by
  • depends on / has dependent
  • requires / is required by

New DoDAF 2 SV-08 diagram

The new SV-08 Systems Evolution Description (DM2) new roadmap style diagram presents a whole lifecycle view of resources, describing how they change over time. It shows the structure of several resources mapped against a timeline.


SV-8 Systems Evolution diagram symbols
The SV-8 presents a whole lifecycle view of systems, describing how they change over time. It shows the structure of several resources mapped against a timeline.

The following symbols are used to develop the systems evolution diagram.

System
Represents a System (DM2). New systems can be created or existing systems can be used. The system symbol is shown as a horizontal bar across the diagram. A system symbol is created by selecting the System tool in the toolbar and clicking on the diagram. Systems can also be drawn by selecting Choices and dragging them onto the diagram
System Milestone
Represents System Milestone (DM2). These are created by adding them to the Milestones property of System (DM2) under the Milestones tab. They appear as circles on the system symbols and are positioned based on the milestone date. The milestone name and date are entered into the Milestone grid as below.

The milestone date controls the position of the milestone on the system line. There is no tool in the toolbar to create milestones. They appear on the system line based on the contents of the Milestone property.

Because systems often go through the same phases and milestones, system milestones can have the same name in different systems. They are individual definitions and can occur at different times and have different DOTMLPF-P States. DOTMLPF-P is short for Doctrine, Organization, Training, Materiel, Leadership & Education, Personnel, Facilities and Policy.

DOTMLPF-P states are represented as the eight sectors on the milestone circular symbols. The state of each SOFMLPF-P sector is controlled by its state which is changed by using the drop down for each sector.

Dependency
Represents System Milestone Dependency (DM2r) and appears as a line connecting two milestones. The line is drawn by selecting the Dependency symbol in the toolbar and connecting it to the depended on milestone and then to the dependant milestone. The arrow head points to the dependant milestone.
Timeline
This symbol is created during creation of a new SV-08 diagram. The symbol contains the intervals from start to finish of the specified time. The time and intervals can be set by opening the Timeline. The following properties can be set.

  • Start Date and End Date: They control the span of the time depicted on the diagram.
  • Interval Number: Controls the number of intervals between measures on the timeline.
  • Interval Unit: Selects Day, Week, Month, Quarter or Year as the measures on the timeline.
Key
Represents the key for the diagram. It shows the position for each of the DOTMLPF-P sectors, the color corresponding to each state and the project phases. The symbol is drawn by selecting the Key symbol from the toolbar and dropping it on the diagram.

Rational System Architect ERP Interface enhancements

The Rational System Architect ERP Interface has been updated to use Safyr 6.1. Safyr 6.1 adds a new feature for determining which tables contain data and extends support for ERP source environments to include systems based on Unicode database platforms.

The interface contains new usability features and improved capability for comparing data structures from more than one repository, for example:

  • There is a new navigation feature that brings together the commonly used Safyr features through a series of clickable tiles.
  • Metadata can be extracted from any SAP ERP or SAP BW system hosted on HANA.
  • The new Subject Area search capability provides an option to filter the list of Subject Areas to those that contain a specified Table/View name.

For details on using the Rational System Architect ERP Interface, see the Safyr Getting Started Guide and Safyr User Guide located in the installation_directory\IBM\Rational\System Architect Suite\SA ERP\Doc directory.


Rational System Architect 11.4.2.7

Rational System Architect Fix Pack 7 (11.4.2.7) for 11.4.2 released March 14, 2014
Major improvements provided in Rational System Architect 11.4.2.7

The following enhancements have been added in Rational System Architect 11.4.2.7.

New XML Export, BPMN Export option
There is a new option for the Export XML and Export BPMN Export statements: Include
related items and subordinates. The purpose is to allow items which reference items in the list produced by the use of the existing check boxes to be included along with their subordinates. Such items would not have been included by using the existing subordinate options because these follow outgoing relationships.

Meta Model Objects: Assign Owning Diagram Type to Symbol
A new property was added to the User Symbol Type definition. The new Owning Diagram Type property can be used to specify which diagram type the symbol is used on.

The following example causes generation of the IN clause of the SYMBOL statement:

    RENAME DIAGRAM "User 1" TO "My Diagram"

    DIAGRAM "My Diagram"
    {

    }

    SYMBOL "Process" IN "Business Process"
    {
    ...
    }


Meta Model Objects: Renaming Existing Definitions
You can now rename an existing object type using meta model objects.
    1. When renaming a default object the rename statements will be done in a File Fragment and placed at the top of usrprops.txt.
    2. Create a User Definition Type using the new object type name.
    3. In the User Definition Type set the "UserProp Rename Number" property to 0. In this case 0 means do not generate a rename statement for this object.

This will allow you to generate usrprops like this:
    RENAME Definition "Use Case" to "My Use Case" >>> from file fragment

    DEFINITION "My Use Case" >>> from user definition type
    {
    ...
    ...
    }



Rational System Architect 11.4.2.6

Rational System Architect Fix Pack 6 (11.4.2.6) for 11.4.2 released December 13, 2013

Major improvements provided in Rational System Architect 11.4.2.6
In addition to the enhancements described in the Information Center What's new topic, the following enhancements have been added in Rational System Architect 11.4.2.6.

Support of FEAF2 modules
The FEAF2 implementation includes the six reference models described by the Office of Management and Budget.

    Application Reference Model (ARM)
    Business Reference Model (BRM)
    Data Reference Model (DRM)
    Infrastructure Reference Model (IRM)
    Performance Reference Model (PRM)
    Security Reference Model (SRM)
The reference models are intended for use in working with TOGAF9 and DoDAF2. In this release, the reference models can be hierarchically represented. And the representational consistency features in System Architect keep the diagrams and the
underlying definitions synchronized.

Assets can be categorized using FEAF2 and included categorization feature. Asset categorization matrices exist for TOGAF9 and DoDAF2. These can be used to quickly categorize or review asset categorization.

Included in the FEAF2 support is collaborative planning methodology (CPM), which allows for collecting data needed for the first three phases of CPM.

Removal of GUIDS from DoDAF 2
The GUIDS for DoDAF2 support have been removed.

Addition of OV-05B BPMN diagram
The OV-05b is a new BPMN style diagram designed for use with DoDAF2 elements. The Lanes represent Performer and subtypes and Processes represent Activity and subtypes.

An ActivityPerformedByPerformer (APBP) is supposed to exist between any Process and the containing Lane or Pool.
The new Auto-create/update ActivityPerformedByPerformer definitions on moving symbols OV-05b BPMN diagram property controls whether the APBP definitions are created or updated on moving symbols. Where there are multiple options on placing a Process inside a Lane or Pool then the user is asked to confirm which should be used.

There is a reference to Location in the APBP called 'Where' which can be populated based on the ‘Related Locations’ references in the containing Lane or Pool.
The new Auto-populate Where of ActivityPerformedByPerformer definitions on moving symbols OV-05b BPMN diagram property controls whether the Location of the APBP is updated and this is turned on by default.
    • The APBP can reference one Location where Performer can reference multiple, so user must select which one to use.
    • When the Pool and Lane (Performers) have different Locations, the Lane takes precedence.
    • When only one of the containing Pool or Lane contains a Location, that Location is used.
    • If neither Pool nor Lane contains Location, the Location should be cleared in the ActivityPerformedByPerformer.


Rational System Architect 11.4.2.5

Rational System Architect Fix Pack 5 (11.4.2.5) for 11.4.2 released September 13, 2013

Major improvements provided in Rational System Architect 11.4.2.5
The following enhancements have been added in Rational System Architect 11.4.2.5.

Enhancements to DoDAF2



Auto generation of system exchanges
Functionality has been added to allow you to automatically generate System Exchanges.System Exchange definitions are computed from System Data Flow definitions and Systems that have been assigned to System Functions through the ActivityPerformedbyPerformer relationship definition.

You can generate System Exchange definitions or create a Preview Report. In either case, a grid shows the log of what is generated or will be generated. The log also shows what is not generated and a reason why it is not generated. If you generate System Exchanges, you can open the System Exchange definitions directly from the grid.



How to Review
In a DoDAF 2 encyclopedia, select Tools, DoDAF 2 Utilities
  • Generate System Exchanges (Preview), or
  • Generate System Exchanges

Auto generation of system resource flows
Functionality has been added to allow you to automatically generate System Resource Flows. System Resource Flow definitions are computed from System Exchange definitions.

You may generate System Resource Flow definitions or create a Preview Report. In either case, a grid shows the log of what was (or will be) generated or not generated and why. If you generate System Resource Flows, you may open the System Resource Flow definitions directly from the grid.



How to Review:
In a DoDAF 2 encyclopedia, select Tools, DoDAF 2 Utilities and select one of the following:
  • Generate System Resource Flows (Preview)
  • Generate System Resource Flows
Rules Check reports for BPMN 2.0/DoDAF 2 architectures
For the BPMN version of the OV-5b, you cannot relate an Activity to the Performer performing it by simply dropping it in a swimlane. The ActivityPerformedbyPerformer relationship is an Explicit join, and you can have more than one. System Architect needs to know to create and name the relationship and present other relationships between the Activity and Performer if they existed. This is unlike other areas of DoDAF 2 support where "box-in-box" data centricity is enabled for implicit relationships. For example, when one system is part of another system, you can drop one system inside another and the definitions are automatically updated.

Similarly, you can auto-build a PartofPerformer or PartofSystem relationship between a Lane and a Pool that you drop it on. You must relate them through the appropriate definition, through the Explorer browser, on a pertinent diagram, or throught a pertinent matrix.

In this release, reports are provided that run off the Reports, DoDAF 2 menu. A list of areas on a BPMN diagram where a relationship or definition is missing are automatically provided:
  • If an Activity is drawn in a Lane or Pool (representing a Performer) but the two have not been related by an ActivityPerformedbyPerformer relationship
  • If a Pool or Lane is shown, and any of its constituent Activities are not shown
  • If a Lane is drawn in a Pool and you have not related the two Performers with a PartOfPerformer or PartOfSystem relationship
This enables you to quickly draw a BPMN diagram with Pools, Lanes and Activities, and then relate them at your leisure.

How to Review:
  • OV_05b BPMN Missing ActivityPerformedByPerformer Rules Check
    1. Create a BPMN diagram, draw a Pool or Lane, and drop an Activity in it but do not relate it.
    2. Select Reports, DoDAF 2 Reports, OV_05b BPMN Missing ActivityPerformedByPerformer Rules Check. You will receive the following kind of grid report.

  • OV-05b BPMN Missing Activity Rules Check
    1. For an encyclopedia where ActivityPerformedbyPerformer relationships have been created between Performers and Activities, create a BPMN diagram, and drag some of those Performers from the Explorer browser onto the diagram to visualize them as Lanes or Pools.
    2. Select Reports, DoDAF 2 Reports, OV-05b BPMN Missing Activity Rules Check. Below is an example of the grid report.
    3. Drag-and-drop the Activities from the grid onto the pertinent Pools or Lanes to complete visualization of the architecture.
  • OV-05b Missing Part Of Pool Rules Check
    1. Create a BPMN diagram, drag a Performer onto the diagram as a Pool/Lane.
    2. Drag a second Performer onto the first Performer.
    3. Select Reports, DoDAF 2 Reports, OV-05b Missing Part Of Pool Rules Check. You will receive the following kind of grid report.


Other miscellaneous enhancements

The Rational System Architect 11.4.2.5 service pack contains fixes to the customer issues (APARs) and implementation of the Requests for Enhancements (RFEs) below. For the complete list of updates, see the
Rational System Architect Fix List .



Rational System Architect 11.4.2.4

Rational System Architect Fix Pack 4 (11.4.2.4) for 11.4.2 released June 14, 2013

Major improvements provided in Rational System Architect 11.4.2.4

The following enhancements have been added in Rational System Architect 11.4.2.4.

Browser support
Internet Explorer 10 is now supported.

Enhancements to TOGAF 9


Infrastructure-Level Modeling: Enabling capture of versions and instances of applications and technologies

The following new definition types have been added to the TOGAF 9 metamodel to enable modeling versions and instances of Physical Application Components and Physical Technology Components:

Definition Type Meaning Examples Comments
Configuration Item -- {Abstract} A physical device or executable software that is part of an enterprise’s current infrastructure. IBM Power Server 780 S/N 12345, deployed instance of MS Windows Server 2008 R2, deployed instance System Architect 11.4.3 CIs are identified by discovery tools, such as IBM Tivoli Application Dependency Discovery Manager.
Attributes that are common to all CIs may include Effective Date and Evergreen Date. The Configuration Item definition serves as a template for the definitions that represent deployed instances of hardware or software.
Database Instance A deployed instance of a physical Technology Component of type “Database”. A running instance of DB2 v9.7 A type of Configuration Item. A Database Instance can link to a physical Technology Component whose Technology Component Type property is set to “Database”. Properties that are specific to the deployed database are in the Database Instance, and properties that apply to the type of database reside in the physical Technology Component.
A Database Instance can also link to any number of physical Data Component definitions.
Operating System Instance A deployed instance of a physical Technology Component of type “Operating System”. A running instance of Red Hat Enterprise Linux Server 6 A type of Configuration Item.
An Operating System Instance can link to a physical Technology Component whose Technology Component Type property is set to “Operating System”. Properties that are specific to the deployed operating system are in the Operating System Instance, and properties that apply to the type of operating system reside in the physical Technology Component.
Device Instance A deployed instance of a physical Technology Component of type “Device” Acme Wireless Router S/N 1234 A type of Configuration Item.
A Device Instance can link to a physical Technology Component whose Technology Component Type property is set to “Device”. Properties that are specific to the deployed device are in the Device Instance, and properties that apply to the type of device reside in the physical Technology Component.
Physical Application Component Instance An installed instance of a Physical Application Component Version. System Architect v11.4.2.4, copy 3 A type of Configuration Item.
A Physical Application Component Instance can link to a Physical Application Component Version. Properties and relationships that are specific to the deployed application are in the Physical Application Component Instance, and properties that apply to the version of the application reside in the Physical Application Component Version.
Physical Application Component Version System Architect 11.4.3, Rational Team Concert 4.0.1, Drupal 7 A PACV is version-specific.
Physical Technology Component Type A vendor-provided or open source product or family of products. A PTCT is not deployable, but its versions (PTC) are. MS SQL Server, Oracle Database Server, IBM Jazz Foundation, Eclipse, MS Windows Server, IBM z/OS, IBM Power System, SOAP, REST, Red Hat Enterprise Linux Server
Server Instance A deployed instance of a Physical Technology Component of type “Server”. A running instance of SQL Server 2008. A type of Configuration Item.
A Server can link to a physical Technology Component whose Technology Component Type property is set to “Server”. Properties that are specific to the deployed server are in the Server Instance, and properties that apply to the type of server reside in the physical Technology Component.





Streamlining of TOGAF 9 metamodel

The following changes were made to the out-of-box TOGAF 9 metamodel to make it more streamlined and easier from a usability standpoint:
  • Prior to version 11.4.2.4 there are two sets of the same Realizes relationship between a Logical Application Component (LAC) and a Physical Application Component (PAC) as shown below. Now, only one set is needed, remove the highlighted statements shown below.
      LAC Realized by Application PAC (this is in the Technology tab)
      PAC Realizes Logical Components LAC (this is in the Technology tab)

      LAC Is realized by PAC (this is in the Implementation tab)
      PAC Realizes LAC (this is in the Implementation tab)

No conversion has been added, however; you can retrieve the deleted property using the TOGAF9 Extension: Deprecation property set.
  • A filter has been added to show Physical Technology Components (PTC) for the following relationship:
      Physical Application Component Realized By General Component PTC or LTC (in Technology tab)
      Physical Technology Component Realizes Physical Application Components PAC (in Application Support tab)

This enables end users to create relationships between Physical App Components (PAC) and Logical Technology Components (LTC), which is contrary to the TOGAF 9 metamodel. Any stored non-valid references will remain. When the reference is removed from the PAC, the relationship between the PAC and the LTC will be removed.
  • The relationship Platform Service Supplied By Logical Application Component (see Technology tab, Supplies Platform Service) has been removed. Symbols have been removed from Platform Decomposition diagram, The symbols can no longer be drawn or edited but can be removed where they are shown on a diagram.
  • Application Components can be related to each other through the Application Component to Application Component matrix. There should be an "is part of" relationships with both Application Components, but it does not. The is part of, comprises properties been added in to the Decomposition chapter, relations can only be made from logical to logical or from physical to physical.
  • In the Application Component definition, there is a property for Interface Definition. This property has been removed.
  • The relationship between the Physical Application Component and Business Service (Realizes Business Service) has been removed. The result is that the Application Component disappears from Data Dissemination and Application User Location, Application Component diagrams. Use the Explorer Relationship reports to view the relationships between these items.
  • The relationship IS Service Is Realized through Physical Application Component has been removed. The results is that the Business Service to Application matrix is not visible
  • The references allowed between the Application Component and Data Component have been corrected. The Logical Application Component choice has been removed from the Resides within Physical Application Components property. This property is located on the Physical Application Component > Application Components tab.

      RE Data Component, when Is Physical=F: Application Components chapter: "Resides within Logical Application Components" references Application Components which have Is Physical=F
      RE Data Component, when Is Physical=T: Application Components chapter: "Resides within Logical Application Components" references Application Components which have Is Physical=T
      RE Application Component, when Is Physical = F: Information chapter: “Encapsulates Logical Data Components” references Data Components which have Is Physical=F
      RE Application Component, when Is Physical = T: Information chapter: “Encapsulates Physical Data Components” references Data Components which have Is Physical=T
  • The Vendor definition type is now related to the Physical Application Component and the Physical Technology Component.
  • TOGAF9 in System Architect does not provide Physical Technology Component to Physical Technology Component Mapping. See properties in Decomposition chapter.
  • The following properties have been changed to not reference a matrix:
    • Logical Technology Component: Realization: Is Realized By
    • Physical Technology Component: Realization: Realizes

Enhancements to DoDAF2

Automatic generation of Operational Exchanges and Needlines

  • The following definitions are now automatically generated:
    • Operational Exchange definitions are from ActivityResourceOverlap definitions.
    • Need Line definitions are from Operational Exchange definitions.





You may generate the Operational Exchanges and Needlines or create a Preview Report. In all cases, a grid shows the log of what was generated or not generated and why; you may open the Operational Exchanges or Needlines directly from the grid.

How to r eview
In a DoDAF 2 encyclopedia, select Tools > DoDAF 2 Utilities
    Generate Operational Exchanges (Preview)
    Generate Operational Exchanges
    Generate Needlines (Preview)
    Generate Needlines

BPMN 2.0 for DoDAF 2 OV-5, SV-4, and SvcV-4

A new OV-05b BPMN diagram type has been added to allow DoDAF2 elements to be modeled using BPMN notation. The following BPMN 2.0 notations represent the following DM2 types:

  • Process = Activity
  • Sequence Flow drawn between Activities = defined by ActivityResourceOverlap
    • Note that to show simple sequence flow, don't put Resources in the ActivityResourceOverlap line
    • Data Object changed to Resource Object, contains list of Resources
  • Pool = Performer and subtypes
  • Lane = Performer and subtypes
  • Message Flow = when drawn between Pools or Lanes it is a Needline (or System Resource Flow or Service Resource Flow)
  • Message Flow when drawn between an Activity and a Pool = Not allowed
  • Message Flow when drawn between Activities in different Pools (which it has to be) is an ActivityResourceOverlap.
  • Gateway = (ActivityResourceOverlap with Rule) for each passage thru Gateway. This line (Sequence Flow or Message Flow as ActivityResourceOverlap) is depicted as a line with a gateway diamond in it for ActivityResourceOverlaps containing a rule. The line is not depicted as a line with a gateway diamond in it when the rule property is null.
  • Event = Event (DM2x) -- a subtype of Activity, with stereotype (Event, cancelEvent, compensationEvent, escallationEvent, exceptionEvent, linkEvent, messageEvent, multipleEvent, ruleEvent, signalEvent, terminateEvent, timerEvent) are labeled OV-06c/SV-11c/SvcV-11c and elements now have references to DoDAF2 equivalents.



BPMN 2.0 Reference to DM2 for Usage in OV-6c and SV-10c

The existing BPMN 2.0 diagram type is now available in DoDAF 2, labeled OV-06c/SV-11c/SvcV-11c, with appropriate references from BPMN 2.0 artifacts to DM2 equivalents, as follows:

  • BPMN Process -- points at one or more Activity (DM2)
  • Sequence Flow -- points at one or more ActivityResourceOverlap (DM2)
  • Message Flow -- points to one or more ActivityResourceOverlap and/or Needline, System Resource Flow, and/or Service ResourceFlow
  • Pool -- points at one Performer (or subtypes)
  • Lane -- points at one Performer (or subtypes)
  • Gateway -- points at ActivtyResourceOverlap
  • Event -- points at Event (DM2)

New SV-6 Report
A new SV-6 report has been provided, superceding the previous SV-6 reports. The report is available in the DAF2.rpt file. It is titled SV-6 Activity Resource Overlap.

How to review
Select Reports, Report Generator, and in the Reports dialog, select File, Open Report File. Browse to the DAF2.rpt file and open it. Select the SV-6 Activity Resource Overlap report and select Generate.

Change Requests and Requests for Enhancements implemented in Rational System Architect 11.4.2.4

Review the Fix list for Rational System Architect to see a list of the client-reported issues (APARs) and requests for enhancements resolved in this release.




Rational System Architect 11.4.2.3

Rational System Architect Fix Pack 3 (11.4.2.3) for 11.4.2 released March 15, 2013

Major improvements provided in Rational System Architect 11.4.2.3

Rational System Architect 11.4.2.3 features the following improvements to existing functionality:

1. Added Firefox 17 ESR Support.
2. The encyclopedia schema checker is now only run when an encyclopedia is upgraded to a later version of System Architect. Previously, the schema checker was run every time anyone opened the encyclopedia. This change will help to improve the time taken to open an encyclopedia. Additionally, when upgrading an encyclopedia you are now prompted to confirm the schema upgrade.

Change Requests and Requests for Enhancements implemented in Rational System Architect 11.4.2.3

Review the Fix list for Rational System Architect to see a list of the client-reported issues (APARs) and requests for enhancements resolved in this release.




Rational System Architect 11.4.2.2

Rational System Architect Fix Pack 2 (11.4.2.2) for 11.4.2 released December 21, 2012

Major improvements provided in Rational System Architect 11.4.2.2

Rational System Architect 11.4.2.2 features the following improvements to existing functionality:

IMPORTANT: This release fixes multiple security vulnerabilities with the IBM JRE 6. For more information, review technote 1620037: IBM Rational System Architect Security Vulnerability: Multiple security vulnerabilities in IBM JRE 6 (CVE-2012-1531, CVE-2012-1532, CVE-2012-1533, CVE-2012-3143, CVE-2012-3159, CVE-2012-3216, CVE-2012-5068, CVE-2012-5069, CVE-2012-5071, CVE-2012-5072, CVE-2012-5073, CVE-2012-5075, CVE-2012-5079, CVE-2012-5081, CVE-2012-5083, CVE-2012-5084, CVE-2012-5089) for details.

DoDAF 2.0 Enhancements

In previous product versions, you could only show one relationship between a given pair of items. With this release, all relationships are now shown in matrices based on explicit relationship definitions, with the option to add more via the matrix editor. This mechanism of relating objects enables more than one relationship between a single pair of items, in the same direction. This affects a selection of DoDAF2 matrices, one MoDAF matrix and one NAF3 matrix.

The following changes were made to the DoDAF 2.0 metamodel:

  • The 'desiredEffectOfCapability' relationship between 'DesiredEffect' and 'Capability' is now supported.
  • There is a new 'Capability View' product, the 'CV-01 Blueprint' diagram, which supports the following elements:
    • DesiredEffect Directs Activity (line)
    • DesiredEffect - Future Resource State (line)
    • Capability - DesiredEffect (line)
    • Milestone - Capability (line)
    • Project - Milestone (line)
    • CapabilityOfPerformer (line)
    • Organization Owns Project (line)
    • Desired Effect Node
    • Milestone
    • Project
    • Organization
    • Capability
    • Resource and subtypes
    • Activity and subtypes
    • The following box-in-box behavior has been introduced with the new 'CV-01 Blueprint' diagram:
      • Project within Project: 'Project Part Of Project' reference
      • Capability within Capability: 'Parent Capability' reference
      • System Function within System Function: 'Part of Function' reference
      • Service Function within Service Function: 'Part of Function' reference
      • Activity within Activity: 'activityPartOfActivity' reference
  • New DoDAF2 Explorer Relationship Reports with supporting text and html based reports:
    • 'SV-01z and SV-10c' and 'SvcV-01z System Data Flow' and 'Service Data Flow Generation' - Draws lines between ActivityPerformedByPerformers that are linked to System or Service Functions based on their being linked by System or Service Data Flows.
    • 'OV-02z' and 'OV-06c activityResourceOverlap Generation' - Draws lines between Activities based on their being linked by 'ActivityResourceOverlaps.'
    • 'OV-02' and 'SV-01' and ;SvcV-01 Operational Exchange' and 'System Exchange Generation' - Draws lines between Performers based on their being linked through 'ActivityPerformedByPerformers' by 'Operational' or 'System Exchanges.'
  • The following NAF3 Explorer Relationship reports are now provided:
    • 'NPV-1 Organisational Resource to System Entity'
    • 'NPV-1 Acquisition Project to System Entity'
    • 'NAF3 Explorer Object Reports' added - 'capabilities related to Acquisition Projects as related via System Entity
    • 'Acquisition Projects where Disposal Date < Given Date'


Other miscellaneous enhancements
  • The Information Center home page now contains an RSS feed that fetches the most current information from the Rational System Architect Support website.


Change Requests and Requests for Enhancements implemented in Rational System Architect 11.4.2.2

Review the Fix list for Rational System Architect to see a list of the client-reported issues (APARs) and requests for enhancements resolved in this release.




Rational System Architect 11.4.2.1

Rational System Architect Fix Pack 1 (11.4.2.1) for 11.4.2 released September 28, 2012

Major improvements provided in Rational System Architect 11.4.2.1

Rational System Architect 11.4.2.1 features the following improvements to existing functionality:

DoDAF 2.0 Enhancements

Metamodel Enhancements and New Fit-for-Purpose Diagram Types

The following changes were made to the DoDAF 2.0 metamodel:

  • Introduction of Operational Exchange: A new definition type, Operational Exchange, is added to the DoDAF 2 metamodel in System Architect. It is an explicit join of two ActivityPerformedbyPerformers, enabling you to specify precisely what Performer performing what Activity interacts with what other Performer performing what other Activity. This enables you to model two or more Performers performing the same Activity. An Operational Exchange points at one ActivityResourceOverlap. A Needline contains a listof Operational Exchanges.
    • A new diagram type, fit-for-purpose OV-2z Operational Exchanges, is introduced. On it you can model Operational Exchanges -- you add ActivityPerformedbyPerformer definitions to the diagram as node symbols, and draw Operational Exchanges as lines between them.
  • A new set of Explorer Relationship reports are provided on Developer Works that you can use to provide automatic guidance on:
    • The forming of Operational Exchanges on an OV-2z diagram, and what ActivityResourceOverlap to point them at.
    • The forming of Needlines on an OV-2, and what Operational Exchanges to put in them.
    • The forming of System Exchanges on an SV-01z diagram, and what System Data Flows to point them at.
    • The forming of System Resource Flows on an SV-01 diagram, and what System Exchanges to put in them.
  • A technical paper is provided on Developer Works that describes how to use the Explorer Relationship Reports (above) to build Operational Views and System Views.
  • Introduction of System Exchange: A new definition type, System Exchange, is added to the DoDAF 2 metamodel in System Architect. It is an explicit join of two ActivityPerformedbyPerformers, enabling you to specify precisely what System performing what System Function interacts with what other System performing what other System Function. This enables you to model two or more Systems performing the same System Function. A System Exchange points at one System Data Flow. A System Resource Flow contains a listof System Exchanges.
    • A new diagram type, fit-for-purpose SV-1z System Exchanges, is introduced. On it you can model System Exchanges -- you add ActivityPerformedbyPerformer definitions to the diagram as node symbols, and draw System Exchanges as lines between them.
  • SV-2 diagram now has a Physical Resource Flow relationship provided to specify physical links between Systems. The new Physical Resource Flow relationship is described in the technical paper provided on Developer Works.
  • Measures -- a new regimen for adding Measures to the tool has been enacted in 11.4.2.1, and the existing Measurement definition types were deprecated. The new way to do measures is described in the technical paper provided on Developer Works.
  • New matrices are provided:
    • SV-03 System to System with System Resource Flow at the cell join
    • SV-05a System Function to Activity
How to Turn Older Metamodel Back On

If you do not wish to adopt the new metamodel changes described above, you can turn the old metamodel back on through two encyclopedia switch (sadeclar.cfg) settings.

Getting back System Resource Flow

  1. Select Tools, Customize Method Support, Encyclopedia Configuration, and in the Rational System Architect Property Configuration dialog, select Advanced.
  2. In the Advanced tab, in the bottom left field of the dialog, (Available, Property Sets) find DoDAF 2 Deprecations - Deprecate Resource Flow, and move it from the Available Property Sets to the Selected Property Sets field.
  3. Click OK to close all dialogs, and reopen the encyclopedia. System Resource Flow will be added back to the metamodel and reappear on all diagram types it used to be on (such as the SV-1, OV-2, etc).

Getting back Needline's ListOf ActivityResourceOverlap, and Resource Flow's List Of System Data Flow
  1. Select Tools, Customize Method Support, Encyclopedia Configuration, and in the System Architect Property Configuration dialog, select Advanced.
  2. In the Advanced tab, in the bottom left field of the dialog, (Available, Property Sets) find DoDAF 2 Deprecations, and move it from the Available Property Sets to the Selected Property Sets field.
  3. Click OK to close all dialogs, and reopen the encyclopedia. A list of ActivityResourceOverlaps will again be in the Needline and Resource Flow (if also turned on, see above) definitions -- on page 2 of the Exchanges tab, and a list of System Data Flows will be added back to the System Resource Flow definition (on page 2 of the System Data Exchange tab) and Resource Flow if turned back on (see steps in section above).

Change Requests and Requests for Enhancements implemented in Rational System Architect 11.4.2.1

Review the Fix list for Rational System Architect to see a list of the client-reported issues (APARs) and requests for enhancements resolved in this release.




Rational System Architect 11.4.2

Rational System Architect 11.4.2 released June 15, 2012

Major improvements provided in Rational System Architect 11.4.2

Rational System Architect V11.4.2 features the following improvements to existing functionality:

  1. DoDAF 2.0 enhancements
  2. TOGAF 9.0 enhancements
  3. Updated Business Motivation Model (BMM)
  4. Improved OSLC Workflows and Rich Hovers
  5. Improved Workspace Merge
  6. Analytics improvements
  7. Usability enhancements
  8. Installer consolidation
  9. New Out-of-Box Content
  10. Integration and platform version updates
  11. Availability of Rational System Architect in additional languages -- Portuguese (Brazilian) and Czech
  12. Over 50 Change Requests and Requests for Enhancement implemented

1. DoDAF 2.0 Enhancements

Description: The following improvements have been made to DoDAF 2:

Additional Viewpoints

Added the following viewpoints:

  • CV-3
  • CV-4
  • PV-1
  • PV-2
  • SV-10b
  • SV-10c
  • AV-2
  • SvcV-5
  • SvcV-6

Box-in-Box Data Centricity for Implicit Relationships

Added representational consistency support for the following box-in-box relationships on diagrams:

OV-2 Alternative:

Capability embedded in Performer will have "capabilityOfPerformer" reference

Materiel embedded in Performer will have "materielPartOfPerformer" reference

SV-1, SV-1 Alternative:

System embedded in Performer will have "Related Performers" reference

SV-1:

System embedded in System will have "Part of System" reference

Performer embedded in Organization will have "MemberOfOrganizations" reference

SV-2:

Interface (Port) embedded in Performer will have "portPartOfPerformer" reference

System embedded in Performer will have "Related Performers" reference

System embedded in System will have "Part of System" reference

SV-2 alternative:

System embedded in Performer will have "Related Performers" reference

SvcV-1:

Performer embedded in Organization will have "MemberOfOrganizations" reference

ServiceInterface embedded in Service will have "interfacePartOfService" reference

Service embedded in Performer will have "Related Performers" reference

SvcV-2:

Service Interface embedded in Service will have "interfacePartOfService" reference

Graphical Metafiles for symbol depictions

Graphical symbol depictions have been provided for all DoDAF symbol types (for example, Capability, Resource, Organization, and so on) have their own graphical depictions on diagrams (previously these were rectangles so all symbol nodes looked alike). You now have the option to show each symbol as the conventional rectangle or using an alternate depiction.

Metamodel adjustments

The following metamodel adjustments were made to DM2 support:

  • Added Measure references to all non-Measure definition types.
  • Made the Value property available in the Measure definition type, to allow users to store Measure values referenced from types and not just from instances.
  • Made System Function and Service Function instantiable, and neatened the Advanced Edit presentation wherever definitions support references to these items
  • Made System Function and Service Function subtypes of Activity so they can be referenced in many places where Activities already are. There are exceptions where this is not allowed. Properties of Activity not appropriate for the subtypes were hidden.

2. TOGAF 9.0 Enhancements

Description: Previously, the TOGAF 9.0 content metamodel was supported in Rational System Architect, visualized through a set of stereotype Explorer diagrams. This support has now been augmented by a set of representationally consistent (or data centric) standard diagrams:

  • Business Architecture
  • Business Footprint
  • Business Service Information
  • Event
  • Goal/Objective/Service
  • Data Dissemination
  • Data Entity/Data Component
  • Application Communication
  • Application and User Location
  • Platform Decomposition
  • Software Distribution
  • Technical Architecture

The advantage is that now you may use these diagrams for information capture (drawing architectures) as well as visualizing relationships in the architecture.

Note: Only direct relationships between items can be drawn on these data centric diagrams. Users can continue to use explorer relationship reports to show indirect relations. An example would be the Application Component to Application Component relationship on an Application Communication diagram -- the relationship is an explicit join (the definition Application Interface). So to show the relationship lines between Application Components, you need to run an Explorer Relationship Report that traverses Application Component to Application Interface to Application Component.

Note also that the old Business Architecture and Technical Architecture diagram types will be marked as deprecated but will still be available by default.

In order to make TOGAF 9.0 less confusing to users, the following diagram types are now disabled when using TOGAF 9. These diagrams can be re-enabled should you wish to continue using them.

  • Process Hierarchy
  • Process Map
  • Process Decomposition
  • Relationship Map,
  • Functional Hierarchy
  • Structure Chart
  • System/Subsystem Structure
  • State Transition Ward and Mellor
  • State Transition
  • Node Tree
  • Flow
  • Flow Chart
  • IDEF0
  • IDEF3 Object State Transition,
  • IDEF3 Process Flow
  • Data Flow Gane & Sarson
  • Data Flow Ward & Mellor
  • Data Flow Yourdon/DeMarco

3. Updated Business Motivation Model (BMM)

Description: The Business Motivation Model (BMM) is a more elaborate implementation of the “Enterprise Direction” diagram already in System Architect. BMM assists a business in modeling where it wants to go and how it will get there. System Architect’s implementation is based on the OMG publication “Business Motivation Model – Version 1.1” dated May 2010.

Rational System Architect’s implementation of BMM includes two representational consistent diagrams: BMM Business Motivation and BMM Hierarchy.

The BMM metamodel can be classified as follows:

At the top: BMM Motivation Element

1. BMM Classifier

2. BMM Assessment

3. BMM End


    3.1 BMM Desired Result

      3.1.1 BMM Goal

      3.1.2 BMM Objective


    3.2 BMM Vision

4. BMM Potential Impact

    4.1 BMM Risk

    4.2 BMM Potential Reward


5. BMM Means

    5.1 BMM Course Of Action

      5.1.1 BMM Strategy

      5.1.2 BMM Tactic


    5.2 BMM Mission

6. BMM Influencer

    6.1 BMM Regulation

7. BMM Directive

    7.1 BMM Business Policy

7.2 BMM Business Rule

In addition, the BMM metamodel also includes the Organization Unit definition type.

How to Review: The Business Motivation Model is disabled by default. To enable BMM select Tools, Custom Method Support, Encyclopedia Configuration. Select the Business Motivation Model (BMM) checkbox and reopen the encyclopedia.

4. Improved OSLC workflow and Rich Hovers

Description: The following workflow improvements have been made when using Rational System Architect as an OSLC consumer:

1. You can now easily reuse recently created links:

2. You can now create links to multiple symbols in one action:

3. The Show More feature can be used to show the diagram preview:


The following workflow improvements have been made when using Rational System Architect as an OSLC provider:

1. The Show More feature can be used to show the diagram preview:

2. The picker dialog allows for filtering of Rational System Architect objects by name and type. You can now also create multiple links in one action where previously you could only create one link at a time:

See the following link for details on how to setup Rational System Architect as an OSLC provider and/or consumer:

http://publib.boulder.ibm.com/infocenter/rsysarch/v11/topic/com.ibm.sa.process_integ.doc/topics/c_oslc_overview.html

5. Improved Workspace Merge

Description: When merging workspaces you now have the option to merge directly into the source and target workspaces. When using this option intermediate or staging workspaces are not created and do not need to be manually deleted after the merge.

Workspace view before merge:

Select the option to Merge directly into source and target workspaces:

Workspace view after merge is complete:

Known Issues and Limitations:

Since baselined workspaces cannot be modified, the ‘Merge directly into source and target workspaces’ option cannot be used when the source or target workspace is baselined.

6. Analytics improvements

Description: Previously when applying an analytic you could set the symbol fill color or apply an analytic depiction icon. In addition to these options, an analytic can now set any combination of the following:

  • Font color
  • Font style
  • Pen color
  • Pen style
  • Fill color
  • Depiction icon

An analytic can now also be used to select the applicable symbols.

To create a new analytic, open the desired diagram, go to the View menu and select Heat Map Manager. Start the Analytic Builder Wizard and in step 3 set the desired depiction options.

7. Usability improvements

7a. Drag and Drop from Search, Reports, and References Windows

Description: It’s now possible to multi-select items in the references window, report result window, and search result window and drag those items onto a diagram.

You can now drag and drop from the References window tree view:

You can now drag and drop from the References window grid view

You can now drag and drop from the Search result window:

You can now drag and drop from the Report result window:

Known Issues and Limitations:

In the report and search result windows, you have to hold Shift or Ctrl, select, and drag as one operation. If you multi-select, then drag, it clears the multi-selection before beginning the drag operation, so you only drag a single item.

7b. Copy Symbol Styles

Description: A set of symbol style tools has been added which will allow users to easily reuse the style of the selected symbol. Once the current style is set, you can apply the copied styles to other symbols.

The following commands are now available on the symbol styles toolbar:

  • Copy Styles: Sets the current styles from the selected symbol
  • Apply Styles: All styles applied
  • Apply Width: Only symbol width applied
  • Apply Height: Only symbol height applied
  • Apply Size: Both symbol width and height applied
  • Apply Fill Color: Only symbol fill color applied
  • Apply Pen: Only pen style and color applied
  • Apply Font: Only font style (including font color) applied

Symbol Style Toolbar

Known Issues and Limitations:

If multiple symbols are selected, only the styles from the first symbol will be copied.

7c. Selecting Symbols

Description: A set of symbol selection tools has been added which will allow users to easily select related symbols. The following commands are now available on the symbol select toolbar:

Symbol + Next: Select the currently selected symbols plus the symbols connected to them.

Symbol + Next + Next: Select the currently selected symbols plus the symbols connected to them, plus the symbols connected to them.

Related Symbols: Select the node symbols connected to the selected symbols. Intermediate line symbols are not selected. The symbols originally selected remain selected.

Unrelated Symbols: Select the node symbols not connected to the selected symbols. Intermediate line symbols are not selected. The symbols originally selected remain selected.

Related Connectors: Select the line symbols connected to the selected node symbols. The symbols originally selected are de-selected. Any line symbols that are selected are ignored and de-selected.

Embedded Symbols: Select the symbols completely embedded within the selected symbols (1 level down). The symbols originally selected are de-selected.

Symbol Select Toolbar

7d. Line-Routing improvements

Description: There are now two modes of auto line routing: retain and assign connections.

Auto line routing with Assign Connections: Lines will be re-routed through the shortest path while assigning new connections

Auto line routing with Retain Connections: Lines will re–routed while keeping the existing connection points

To set the line routing mode for the current diagram go to the Format | Diagram Auto Routing menu.

The auto routing setting is saved on per diagram basis. The default setting for all diagram types is off.

7e. Property Window goups

Description: Property groups will now be reflected in the Property Window. Previously property groups were only reflected in the classic definition editor.

For example, consider the following usrprops.txt snippet:

Group “Interfaces”

{

Property “Application Interfaces” {Edit ListOf…}

Property “Interface Definition” {Edit OneOf…}

}

7f. Multi-Property Driven Chapters

Description: It is now possible to hide chapters based on the values of multiple properties. Consider the following usrprops.txt snippet.

DEFINITION "Rod"

{

PROPERTY "Type of Influence" {EDIT TEXT LISTONLY LIST "Influence Type" INITIAL USER REQUIRED CAUSESAPPLY }

PROPERTY "Other Influence" {EDIT TEXT LISTONLYCOMBO LIST "Influence Type" INITIAL USER REQUIRED CAUSESAPPLY }

CHAPTER "One" LABEL "OneX"

{TESTPROC TestPropertyValue TESTPROPERTY "Type of Influence" TESTSTRING { "Internal Influence" } AND TESTPROPERTY "Other Influence" TESTSTRING { "Another" }}

PROPERTY "Rainbow" { EDIT TEXT LENGTH 1000 }

PROPERTY "Rainbow2" { EDIT TEXT LENGTH 1000 }

Here’s another example showing the use of NOT and OR.

DEFINITION "Rod"

{

PROPERTY "Type of Influence" {EDIT TEXT LISTONLY LIST "Influence Type" INITIAL USER REQUIRED CAUSESAPPLY }

PROPERTY "Other Influence" {EDIT TEXT LISTONLYCOMBO LIST "Influence Type" INITIAL USER REQUIRED CAUSESAPPLY }

PROPERTY "Under the Influence" {EDIT TEXT LISTONLYCOMBO LIST "Influence Type" INITIAL USER REQUIRED CAUSESAPPLY }

PROPERTY "Influence4" {EDIT TEXT LISTONLYCOMBO LIST "Influence Type" INITIAL USER REQUIRED CAUSESAPPLY }

PROPERTY "Influence5" {EDIT TEXT LISTONLYCOMBO LIST "Influence Type" INITIAL USER REQUIRED CAUSESAPPLY }

CHAPTER "One" LABEL "OneX"

{TESTPROC TestPropertyValue TESTPROPERTY "Type of Influence" TESTSTRING { "Internal Influence" } AND

(TESTPROPERTY "Other Influence" NOT TESTSTRING { "External Influence" "Another" } OR TESTPROPERTY "Under the Influence" TESTSTRING { "Another" }) AND

(TESTPROPERTY "Influence4" TESTSTRING { "Internal Influence" "Another" } OR TESTPROPERTY "Influence5" TESTSTRING { "External Influence" })}

PROPERTY "Rainbow" { EDIT TEXT LENGTH 1000 }

PROPERTY "Rainbow2" { EDIT TEXT LENGTH 1000 }

Known Issues and Limitations:

Nested parenthesis such as (A and (B or C) and D) are not supported.

8. Installer consolidation

Description: In version 11.4.1 of Rational System Architect, four previously charged add-on's were provided with Rational System Architect as part of the base price -- SA Compare, SOA Add-on, XML Architect, and SA/Process Integrator (BPMN Integration with Microsoft Visio).

In this version of the software, the Rational System Architect installer was improved so that the Rational System Architect for SOA and Rational System Architect Process Integrator add-on installers are now consolidated into the main Rational System Architect installer (the other add-on's already were part of the main install and are activated via licensing). All add-ons appear as optional install components.

Optional install components will be enabled by default. The Rational Rational System Architect Process Integrator option will only be present if Microsoft Visio 2007 is also installed.

You must still request new license keys to enable these four add-ons. Please contact your account manager.

Note: Customers who previously purchased these items will no longer need to pay maintenance on them.

9. New Out-of-Box Content

Description: Two new example encyclopedias have been provided with the product -- JK Enterprises, which is an example of the TOGAF 9 architecture, and Search and Rescue (SAR), which is an example of the DoDAF 2.0 architecture.

10. Integration and Platform Version Updates

Description:

Category Synopsis
OSLC Add support for Rational Clear Quest 8.0.0.3
OSLC Add support for Rational Requirements Composer 4.0
OSLC Add support for Rational Team Concert 4.0
OSLC Add support for Rational DOORS Web Access 1.5
Deployment Add support for Firefox 10 ESR
Deployment Add support for Citrix XenApp 6.5
Deployment Add support for VMware ESX 5.0
Deployment Add support for Oracle/IBM JRE 1.7
Reporting Add support for Rational Publishing Engine 1.1.2.2
Reporting Add support for Rational Insight 1.1
Rational System Architect Presentation Integration Add support for Microsoft PowerPoint 2010 for Rational System Architect Presentation Integration
Rational System Architect - DOORS Add support for Rational DOORS 9.4

11. Availability of Rational System Architect in Additional Languages

Description:

Category Synopsis
Globalization Add Czech translation
Globalization Add Portuguese (Brazil) translation

Change Requests and Requests for Enhancements implemented in Rational System Architect 11.4.2

Review the Fix list for Rational System Architect to see a list of the client-reported issues (APARs) and requests for enhancements resolved in this release.

For more information on trials, demos, or purchasing Rational System Architect, go to the following URLs:




Rational System Architect 11.4.1.2

Rational System Architect 11.4.1.2 released March 16, 2012

The Rational System Architect 11.4.1.2 Service Pack contains fixes for the client issues below. It also contains the following enhancements:

  • Support for Mozilla Firefox 10 ESR.
  • Refined the Verify and Repair feature to suppress unnecessary warnings when it finds incorrect DGX record sizes. Users no longer need to open, edit and save diagrams to correct the DGX record sizes, which makes it easier to run Verify and Repair on encyclopedias with hundreds of diagrams (RFE #16266).
  • A new ‘usrdeclar.cfg’ file for users to declare encyclopedia property sets and to enable or disable diagrams. This enhancement prevents edits to the ‘sadeclar.cfg’ file that users may have made from being overridden (RFE #14581).
  • Improved the performance of the help system by making topics load faster. The improvements in your environment might vary depending on network and internet connection speeds, and other factors, such as VPN connections.
  • A new ‘accumulate references’ collision option for XML import. This option appends any new references to a ListOf property instead of replacing the property with the new values. The option was added to improve the migration of DoDAF 1.5 model assets to DoDAF 2, however it is a generic change and is not specific to DoDAF (RFE #13724).
  • The Heat Map Manager now retains selected symbols after diagrams are reopened. This enables Analytics that rely on a symbol being selected to work as designed (RFE #14953).

Change Requests and Requests for Enhancements implemented in Rational System Architect 11.4.1.2

Review the Fix list for Rational System Architect to see a list of the client-reported issues (APARs) and requests for enhancements resolved in this release.




Rational System Architect 11.4.1.1

Rational System Architect 11.4.1.1 released December 16, 2011

Rational System Architect 11.4.1.1 is a service pack, and therefore only contains fixes to client issues and to existing functionality.

Rational System Architect 11.4.1.1 introduces support for Microsoft Internet Explorer 9.

Change Requests and Requests for Enhancements implemented in Rational System Architect 11.4.1.1

Review the Fix list for Rational System Architect to see a list of the client-reported issues (APARs) and requests for enhancements resolved in this release.




Rational System Architect 11.4.1

Rational System Architect 11.4.1 released October 28, 2011

Rational System Architect 11.4.1 features the following improvements to existing functionality:

  1. Four Add-ons Now Provided at No Charge; Must Request License Keys
  2. Usability Improvements
  3. Jazz/OSLC Integrations
  4. BPMN 2.0 Interchange
  5. DoDAF 2.0 Enhancements and Additional Viewpoints
  6. Improved Workspace Merge with Workspaces
  7. Access Control Improvements
  8. SA/ERP Enhancements
  9. Support for Cognos 10.1 (in addition to previous support for 8.4)
  10. Support for Microsoft Office 2010
  11. Additional Session Options and Other Options
  12. Over 140 Change Requests and Requests for Enhancement Implemented

1. Four Add-ons Provided At No Charge; Request License Keys

Description

In this version of the software, the following add-on's are now provided as part of the base price of Rational System Architect -- you no longer need to purchase them separately:

  • Rational System Architect Compare
  • SOA Add-On
  • XML Architect design
  • Rational System Architect Process Integrator (BPMN integration with Visio)
  • You must request new keys to enable these four add-ons. Please contact your account manager.

Note: Customers who previously purchased these items will no longer need to pay maintenance on them.


2. Usability Improvements

a. Aesthetically Pleasing Symbols

Description

The following enhancements were made to Rational System Architect to make diagrams more aesthetically pleasing to view:

  • The venerable three-bullet icon that appeared in the upper left corner of symbols to denote a parent-child relationship, or addressable attached, or a graphic comment, has been replaced by icons that give a more visual indicator of the intent -- a down arrow denotes a child diagram attached, for example. The icons can be replaced with user-supplied wmf images (Rational System Architect looks for the following wmf files in an encyclopedia's files table: images\Indicator_Comment.wmf, images\Indicator_Child.wmf, Images\Indicator_Addressable.wmf, and images\Indicator_Truncation.wmf. You may also revert to the old indicators via an sa2001.ini file setting -- GrafficEffectsNewIndicators = N).
  • The four-bullet truncation indicator that appeared at the bottom of a symbol to denote that not all displayable items were displayed, has been replaced by a down-chevron icon (note: truncation indicators will appear when necessary, if you have selected Tools, Preferences, Draw Truncation Indicator).
  • New symbols have been provided for Enterprise Direction diagrams.
  • Some new symbols have been provided for Network Concept diagrams.
  • Stylesheet preview and easy selection is now provided at the bottom of the Property Configuration dialog (opened by selecting Tools, Customize Method Support, Encyclopedia Configuration). The new option enables you to browse to folders to select a stylesheet for the encyclopedia, and browse how it will look on a representative diagram.
  • Several features that first appeared in 11.4.0.3 but needed to be turned on via sa2001.ini file settings, are now available out of the box -- see details in the 11.4.0.3 What's New:
    • Symbols on diagrams may now be visualized with gradient color fill.
    • Line and metafile smoothing with anti-aliasing is available.
    • For DoDAF 2.0, better drawing icons are provided in the Draw menus.

Values and Benefit:
These changes are all intended to make the models built in Rational System Architect more aesthetically pleasing to view and more readably deliverable to your consumer -- whether that be upper management or the general public.

How to Review:
You can review these enhancements as follows:
  • Open the Samples encyclopedia and view the Enterprise Direction diagrams (for new symbols), Network Concept diagrams (for new symbols).and Business Process diagrams (for truncation indicators), among others.
  • See help on Working with stylesheets.
  • See help on Symbol icon indicators.


b. Improvements to Line Drawing

Description

Rational System Architect has many line drawing algorithms available, which can be turned on through a variety of choices. One powerful algorithm is Auto Line Routing, which is turned on globally for all diagram types via the Tools, Preferences menu choice. The choice makes sure that a drawn line never crosses over a symbol, and will auto-route itself so that this does not happen. There are some diagrams that you would want this behavior on, and others that you would not.

In 11.4.1, there is a new choice in the Format menu -- Format, Diagram Auto Routing -- that is available when you have a diagram open. This allows you to turn on Auto Routing for a particular diagram instance. The choice to turn on/off Auto Routing remains in the Tools, Preferences menu. If either Auto Routing choice is turned on (in Tools, Preferences or Format, Diagram Auto Routing), then Auto Routing is on for a diagram.

What this means is that if you want to have Auto Routing turned on for a particular diagram or set of diagrams, then turn it off in Tools, Preferences and enable it for the selected diagram(s). However, beware that if you turn off Auto Routing for a particular diagram by deselecting Format, Diagram Auto Routing -- auto routing may still be on for the diagram if it is set to be on globally via Tools, Preferences.


Values and Benefit:
Auto line routing is a powerful feature to make drawing with the tool easy, but at the same time there are certain diagram types where you don't want it. You now have the option to turn it on/off on an individual diagram basis.

How to Review:
See help on Routing lines automatically on a diagram.

c. Improvements to Reporting Output

Description
A new style sheet is available for nicely formatting HTML based output reports.


Values and Benefit:
The native report system enables you to easily create and customize reports, much more easier than Word reports (that use VBA macros) and other reporting options. Improved look of output provides wider usage of these reports.

How to Review:
Select Reports, Report Generator. Click Add to create a new report and set the Report Type to HTML. In the Style Sheet field select HTML Tables.xsl from the drop down.

New Stylesheets for Report Engine Output

The reporting engine has been improved to support better stylesheets on output, so that the report views produced are more aesthetically pleasing.



3. Jazz/OSLC Integrations

Description

Rational System Architect now supports Open Services Lifecycle Collaboration (OSLC) technology. This allows ready integration and linking of information between other tools that support OSLC, to a specific domain OSLC specification (http://open-services.net/specifications/).

Rational System Architect can consume artifacts from the following products:

  • IBM Rational Doors Web Access (DWA) 1.4.0.3 (OSLC Requirements Management (RM) spec 1.0)
  • IBM Rational Requirements Composer 3.0.1 (RM 1.0)
  • IBM Rational Change 5.3.0.2 (OSLC Change Management (CM) spec 2.0)
  • IBM Rational Team Concert (RTC) 3.0.1 (OSLC CM 2.0)
  • IBM Rational Design Manager (DM) 3.0 (OSLC Architecture Management (AM) spec 2.0) -- Design Manager is the Jazz-enabled version of IBM Rational Rhapsody and IBM Rational Software Architect (https://jazz.net/projects/design-management/?ref_content=ribbon)
  • System Architect can provide data so that the following products can consume it:
  • IBM Rational Team Concert (RTC) 3.0.1 (OSLC CM 2.0 )
  • IBM Rational Design Manager (DM) 3.0 (OSLC AM 2.0)

Using OSLC, you can 'see' into the data in another tool, and create traceability links to/from it. OSLC link indicators will appear in System Architect on symbols in diagrams, in artifacts in the Explorer (browser), and on Explorer diagrams (which are essentially visual reports). You may hover over an OSLC link indicator to see a summary of the link target, and click on a "Details" icon in the rich hover to bring up the target data of the link in its native tool.

Values and Benefit:
The OSLC linking is the beginning of a leap forward in integration amongst multiple tools instead of building a myraid of point-to-point integrations between tools. For example, you may now have traceability between models in Rational System Architect and Rational Software Architect and/or Rational Rhapsody (via Rational Design Management tool), and amongst Rational DOORS, Rational Team Concert, and Rational Change. Manage your work with Rational Team Concert (it offers lifecycle management capabilities, a mechanism to inform specific users by email about changes on particular diagrams and definitions, and a more sophisticated audit trail track changes), and trace through high-level architecture in Rational System Architect to design models in Rational Rhapsody or Rational Software Architect, with integration to requirements in Rational DOORS, and change requests managed in Rational Change.

How to Review:
To use this feature, the service provider of the products listed above needs to be configured. This is done through the Tools, Service Provider Configuration menu option in Rational System Architect. For more information, see help on Open Services for Lifecycle Collaboration.


4. BPMN 2.0 Interchange

Description
You may now generate and import BPMN 2.0 interchange .bpmn files from and into System Architect's BPMN 2.0 support. The BPMN 2.0 interchange format (.bpmn) is an industry standard advocated by the BPMN 2.0 specification.

This enables .BPMN interchange between System Architect and:

  • IBM Process Designer 7.5 (formerly Lombardi) -- Export from Rational Sytem Architect into Process Designer
  • IBM Rational Software Architect (RRational System Architect) -- Bidirectionally
  • IBM Blueworks Live, IBM WebSphere Business Compass, and WebSphere Business also support the importation and exportation of BPMN 2 interchange files, which should work with Rational System Architect.
    • IBM Blueworks Live can both import and export BPMN 2 interchange files.
    • IBM WebSphere Business Compass can both import and export BPMN 2 interchange files.
    • WebSphere Business Modeler can export BPMN interchange files. Since WebSphere Business Modeler has a two-way interchange of models with WebSphere Business Compass, you should be able to bring BPMN 2 interchange files into WebSphere Business Modeler by bringing them into Business Compass first, then going from Business Compass to Business Modeler.

Values and Benefit:
This capability enables exchange of BPMN process models to best-of-breed tool for execution of process models.

How to Review:
In System Architect's Explorer (browser), right-mouse click on a Business Process diagram, and select Export BPMN or Import BPMN. For more information, see help on Importing and exporting BPMN 2.0 model information.
.

5. DoDAF 2 Improvements

Description
A number of enhancements have been provided for DoDAF 2.0 support, as follows:

Data Centric Hierarchy Diagrams

Description
Hierarchical diagram types in System Architect’s DoDAF 2.0 support have data centric relationship lines. However, these lines were rudimentary to draw in the initial release of 11.4 -- they did not feature the easy-hookup of the traditional System Architect hierarchical diagram type. In this release, System Architect now has data centric hierarchy diagrams that also feature Rational System Architect's easy-attach drawing method, where you bring a symbol under and near a parent symbol, and it automatically attaches -- and what's more, due to data centricity, the definitions become related appropriately.

This feature is instantiated in the following DoDAF 2 diagram types:

  • CV-2 Capability Taxonomy
  • OV-5a Operational Activity Decomposition
  • SV-4 Systems Functionality Decomposition
  • SvcV-4 Services Functionality Decomposition

If you have created these diagram types in previous versions of Rational System Architect 11.4, then when you open the existing diagram, the data centric easy hookup line drawing will automatically be put in place -- there is no need to convert or redraw the diagram.

Note that this feature is also now available for any hierarchical diagram type across the tool, although it has only been implemented so far in DoDAF 2.0. The feature is enabled by a USPROPS keyword -- HIERARCHICAL -- so you may make custom hierarchy diagram, or make an existing hierarchical diagram data centric with easy hookup, providing your overall metamodel supports the capture of the data centric information.

Values and Benefit:
Hierarchical diagrams are now easy to draw and have data centric lines; this feature is enabled for DoDAF 2.0 but can be implemented generically across the tool for any hierarchical diagram type.

How to Review:
You may draw any of the diagram types listed above. For more information on the keyword HIERARCHICAL to enable data centric hierarchical diagrams, see help topic DoDAF 2.0 overview.

Support for Additional DoDAF 2.0 Models, Reports, and Matrices

Description
Rational System Architect 11.4 supported the entirety of the DM2 metamodel, and many of the most-used views. In subsequent minor releases, Rational System Architect has been supporting a fuller set of the DM2 models, matrices, and reports (via native report system with new stylesheets).

In 11.4.1, the following additional DoDAF 2.0 views are now supported:

  • CV-02 Capability Taxonomy (DM2)
  • OV-03 reports (previously supported OV-3 through a matrix)
  • OV-04 PerformerSupportsPerformer Network (DM2)
  • SV-01 Systems Interface Description Alternative (DM2)
  • SV-02 Systems Resource Flow Description Alternative (DM2)
  • SV-03 (report by definition and by diagram)
  • SV-06 Systems Resource Flow (report)
  • SV-06b (report)
  • SV-07 (report by definition and by diagram)
  • StdV-01 Standards Profile (report)
  • StdV-02 Standards Forecast (report)
  • SvcV-01 Services Context Description Alternative (DM2)
  • SvcV-04 Services Functionality Description Alternative
  • PV-3 Projects and Capabilities (report)

The following changes were made to some views:
  • Swim Lane, Data Store and System Data Flow have been added to SV-04 Systems Functionality Description Alternative
  • Swim Lane, Data Store and System Data Flow have been added to SvcV-04 Services Functionality Description Alternative
  • System Function has been added to SV-04 Systems Functionality Description Alternative
  • Part of System Function has been added to SV-04 Systems Functionality Description Alternative
  • Service, ServiceInterface, and ServiceInterfacePartOfService have been added to SvcV-02 Services Resource Flow Description Alternative
  • Service Resource Flow has been added to SvcV-01 Services Context Description and SvcV-02 Services Resource Flow Description Alternative
  • CapabilityOfPerformer has been added to CV-01 Vision
  • PerformerSupportsPerformer has been added to OV-04 Organizational Relationships and OV-04 PerformerSupportsPerformer Network
  • Need Line has been added to OV-02 Operational Resource Flow and OV-02 Operational Resource Flow Alternative
  • System Resource Flow has been added to SV-01 Systems Interface Description and SV-02 Systems Resource Flow Description

How to Review:

See help on What's new for DoDAF 2.0 modeling.


DoDAF 2.0 Templates for Rational System Architect/Publisher and Rational System Architect XT

Rational System Architect/Publisher and Rational System Architect XT now provide DoDAF 2.0 templates.

Metamodel Changes

Description

Several changes were made to the DoDAF 2.0 metamodel to make it easier to build architectures:

  • ActivityPerformedbyPerformer now includes Location
  • The "Need Line" and "System Resource Flow" definitions were added as extended features of DM2.
  • Needline includes properties performerSource, performerTarget, Operational Data Exchanges, Realized by Service Resource Flows, and Realized by System Resource Flows
  • System Resource Flow includes properties performerSource, performerTarget, System Data Exchanges, and Realizes Need Line
  • ActivityAbleToPerformCapability was re-labeled ActivityPartOfCapability
  • Service Resource Flow now includes properties Services Data Exchanges and Realizes Need Line
  • Many nodes now have displayable properties

DoDAF 1.5 to DoDAF 2.0 Migration Toolkit

Description
A DoDAF 1.5 to DoDAF 2.0 Migration Toolkit is provided. This toolkit enables you to migrate your architecture built with DoDAF 1.5 ABM or DoDAF 1.5 standard, to DoDAF 2.0. The toolkit provides you with the capability to migrate your architecture following basic steps:

  1. Prime the DoDAF 1.5 Encyclopedia
  2. Create and Run Report Generator Reports
  3. Create DoDAF 2 Definitions by importing generated XML
  4. Create DoDAF 2 Data Centric Diagrams

Values and Benefit:
DoDAF 2.0 and the DM2 provide great advantages with a data centric approach -- improved ability to exchange information between tools, for example. Users need an ability to migrate their existing DoDAF 1.5 architectures to DoDAF 2.0.

How to Review:
See help on Migrating from DoDAF 1.5 to DoDAF 2.0.


6. Improved Workspace Merge with Workspaces

Description
A new front end for merging workspaces using the object history window is provided. It allows the user to review and select the changes to be merged. You can baseline the workspace and create child merge workspaces.


Values and Benefit:
Managing the architecture work of multiple users in different encyclopedias or workspaces is one of the most important aspects of a team of users using an architecture tool. Previously, the workflow to perform a cross workspace merge was difficult and the story was not complete -- it required the user to note the items to merge while differencing, then re-select the items in a different UI while merging.

How to Review:
See help on Merging Workspaces.


7. Access Control Improvements

Description
A number of changes have been made to access control for this release:

Instance-Level Access Control (ILAC): Defaults for Groups

It is now possible to allocate the Default ILAC Read/Write settings to a Group. This is in addition the previous behaviour of setting the defaults to a User. So the settings are now available in the following two locations:

  • \Users and Groups\<User (or Group)>\ILAC Group Defaults
  • \Encyclopedias\<ency>\Users and Groups\<User (or Group)>\ILAC Group Defaults for Encyclopedia
If there is a setting made at this point, either for the active user or for a group the user is a member of, then this is used in preference.

Values and Benefit:
This makes the ILAC Group Defaults feature more useful as it can be used with user groups in addition to individual users.

How to Review:
See help on Setting Default Permissions for New Items.

Access Control: Instance Level Access Control (ILAC) Group Restriction

A new setting has been introduced for an encyclopedia, "ILAC Group Restriction". When this is set, the groups the active user is a member of will become restricted down to the list of groups that were involved when granting access to the selected encyclopedia or workspace. So for example, if a user (User 3) has been assigned to two groups -- Team 1 and Team 2 -- if they log into a Workspace or encyclopedia that is only authorized for Team 1, they will be seen to be a member of Team1 but not Team2. Similarly, the default permissions applied to new items (ILAC Defaults) will be filtered by the list of groups that were involved when granting access to the selected encyclopedia or workspace. So when logged into Team1's encyclopedia or Workspace, User 3 will be seen to have ILAC Group Defaults of Team1.

Values and Benefit:
There had been a concern when a user was a member of two groups that they had the ability to change items they were not expected to change through use of permissions that were not appropriate to the Workspace or encyclopedia. There could also be seen to be a problem when the same user created a new item, as the defaults would be set, such that both teams had permission to read and write to the item.

How to Review:
See help on Setting ILAC group restrictions for encyclopedias.


8. Rational System Architect/ERP Improvements

Description
Rational System Architect/ERP now allows reversal into Rational System Architect of Application Components and Transaction information (previously, you could look up Rational System Architect tables by these elements, but not port them into Rational System Architect).

In Rational System Architect, the following changes have been made to the metamodel to capture this information:

  1. Introduced a new definition called Rational System Architect Transaction Code (which encapsulates the mnemonics in the Rational System Architect Transaction).
  2. Created a relationship between Application Component (or Application if TOGAF is turned off) to Rational System Architect Transaction.

Values and Benefit:
The transaction is the tie that binds the Rational System Architect/ERP solution (which focuses on data architecture of Rational System Architect) with the IntelliCorp LiveCapture solution (which focuses on business processes). You may use these two solutions to look into the 'black box' that is your Rational System Architect implementation, for Rational System Architect redocumentation and transaction planning.

How to Review:
Install the IBM Rational System Architect for ERP Interface add-on, and review the improvements as described above. Documentation for the add-on is provided by Silwood Technology LTD. The ‘Saphir Metadata Explorer User Guide’ and the ‘Saphir Metadata Explorer Getting Started Guide’ are installed with the add-on at the following subfolder: C:\Program Files\IBM\Rational\System Architect Suite\SA ERP\Doc.


9. Rational System Architect Now Supports IBM Cognos 10.1

Description
Rational System Architect and IBM Cognos integration now supports IBM Cognos 10.1 in addition to IBM Cognos 8.4.1. While IBM Cognos 8.4.1 is still bundled with Rational System Architect at no extra charge, the Rational System Architect and IBM Cognos integration can be used with IBM Cognos 10.1.

Values and Benefit:
IBM Cognos 10.1 provides many new features over IBM Cognos 8.4.1, including some of the following:

  • Cognos 8.4.1 does not support Microsoft SQL Server 2008 R2; IBM Cognos 10.1 does -- specifically Cognos 10.1 supports Microsoft SQL Server 2005, Microsoft SQL Server 2008, and Microsoft SQL Server 2008 R2.
  • IBM Cognos 10.1 supports a new type of report called an Active report, which can be viewed either offline or online.
  • IBM Cognos 10.1 has superior report interactivity -- ability to interact between and highlight different sections of the report.
  • IBM Cognos 10.1 has a nice UI, making it easier to build reports.


10. Support for Microsoft Office 2010

Description
Rational System Architect now supports Microsoft Office 2010 for Word and Excel based reports and utilities.

Note that Rational System Architect is not yet supporting Microsoft PowerPoint 2010 for the SA Presentation Integration (live synch between Microsoft PowerPoint 2010 and SA -- only supported in Microsoft PowerPoint 2007), nor Microsoft Visio 2010 for SA Process Integrator (the add-in that enables you to draw BPMN diagrams in Microsoft Visio using that product’s drawing engine but Rational System Architect’s rules engine, and store info in Rational System Architect's repository).


11. Additional Session Options and Other Options

Description
Rational System Architect offers users a rich set of customizable options. Many times a useful preference is turned off and/or not readily available to the end user. The following improvements have been made to the default options.

Session Option Description Old Default Default in 11.4.1
ChoicesShowPackage
Hierarchy
? is Y or N (default). Y specifies that only top level Packages are shown when Packages are being presented in the choices list. Subordinate Packages can be found by expanding the tree. N Y
IncludeJPEGinRAM ? is T or F (default). T specifies that the selected diagram(s) JPEG(s) will be published in the Rational Asset Manager asset. F T
MaxDrawArea Horizontal size and vertical size are the maximum number of horizontal and vertical inches (centimeters in
European style) available for any given diagram.
64 x 60 640 x 640
GraphicEffectsOn ? is Y (default) or N. Y specifies that diagrams should be drawn using enhanced graphical effects. These
effects are line smoothing and gradient fills.
N Y
Session Option Description Old Default Default in 11.4.1
ShowProperties Show properties window on startup. N Y
Locale Option to enable different locale/translation 409 (English) 409 (English) Can now be set in Session Options
AllowRenameFromEnglishType Option to refer to objects using their English names even when using a non-English locale. N N - Can now be set in Session Options

Option Description Old Default Default in 11.4.1
Diagram grid
display
To set it, select Format, Diagram Format, Grid Display. Off On
Symbol shadowing To set it, select Format, Diagram Format, Symbol Shadowing Off On for node symbols
Default style sheet To select it, choose Tools, Customize Method Support, Encyclopedia Configuration. This is the style sheet for diagrams and symbols. Autoexec.sty If no user specified style sheet is set then Autoexec.styis used, which is a duplicate of Ocean_blue.sty.
Undo file size Max data to store in undo file. To set it, select Tools, Preferences. 524,288 Now simply on by
default
Allow in place name edit for new symbols When you place a new symbol, the name is highlighted
in the symbol to edit, rather than a popup dialog asking
for name. . To set it, select Tools, Preferences.
Off On
Command Line Option Description Old Default Default in 11.4.1
log Used by IBM Support to get more information for troubleshooting. Enabled via command line Added to Session Options as VerboseLog with a default of N
suppressundosizedialog Used to suppress prompts to increase undo file size. Enabled via command line Undo is now turned on or off in preferences. You will no longer be prompted to increase to undo file size


12. Change Requests and Requests for Enhancements implemented in Rational System Architect 11.4.1

Review the Fix list for Rational System Architect to see a list of the client-reported issues (APARs) and requests for enhancements resolved in this release.

For more information on trials, demos, or purchasing Rational System Architect, go to the following URLs:




Rational System Architect 11.4.0.3

Rational System Architect 11.4.0.3 released April 29, 2011

I. Removal of Certain Third-Party ActiveX Controls to Address Security Vulnerability

Description
There is a high-risk security vulnerability with the ActiveBar ActiveX controls used by Rational System Architect. It is possible for an attacker to compromise the ActiveBar ActiveX controls (actbar.ocx and actbar2.ocx) used within Rational System Architect to execute arbitrary code by instantiating these controls from Microsoft Internet Explorer Web browsers.

There are two solutions to address the security vulnerability: 1) upgrade Rational System Architect or 2) implement a workaround. The product upgrade to the specified version should be implemented as soon as practical and your business needs dictate.

Please see detailed information in the following Technote:

http://www.ibm.com/support/docview.wss?uid=swg21497689

Benefit:
Applying the applicable fixpack will reduce the risk of a remote attacker exploiting a security vulnerability in ActiveBar ActiveX controls used by Rational System Architect.


II. Improvements Provided In Rational System Architect 11.4.0.3

Rational System Architect V11.4.0.3 features the following improvements to existing functionality:

DoDAF 2 Drawing Icons and Drop-Down Functionality
Description
New icons have been added to the Draw toolbars of DoDAF 2 diagrams, each representing a DoDAF 2 type. In addition, the Draw toolbar of DoDAF 2 diagrams now offers a drop-down for types and their subtypes (previously users had to choose a type (example, Performer), and then after drawing the symbol choose what specific type it represented (example, Performer or any of its subtypes such as Person, Organization, System, Service, etc). (PS: The toolbar drop-down of types was previously available only for stereotyped choices off a value list; this functionality is for a super/sub-type chain.)

IBM policy exists to ensure that a fix pack does not change anything in the product to ensure customers have no impediments (for example, new training costs) preventing them from moving to the latest fix pack; hence this new functionality must be turned on by ini file settings; in the next release it will be available by default. To turn on this feature, do the following:

  1. In your sa2001.ini file (typically located in the <C>:\Documents and Settings\Administrator\Local Settings\Application Data\Telelogic\System Architect directory) specify the command in bold below (under the [SystemArchitect] section:

    SA2001.INI Switches:
    [SystemArchitect]
    CommandLine= -dodaf2plus 3
  2. In the main System Architect software directory (<C>:\Program Files\IBM\Rational\System Architect Suite\System Architect, do the following:
    a. Delete the file called 'ExplorerIconBitmaps.zip'
    b. Rename the file 'DM2_ExplorerIconBitmaps.zip' to 'ExplorerIconBitmaps.zip'
  3. (Re)start System Architect.

Upgrading Existing Encyclopedias:

If you are upgrading an existing encyclopedia you will also need to import the new 'ExplorerIconBitmaps.zip' into your encyclopedia and replace the existing one. You may use SAEM to do this, or by selecting Tools, Encyclopedia File Manager.

Benefit:
Ease of use for users – being able to quickly distinguish a type based on its iconic representation on the Draw toolbar, and ability to easily select a subtype from a drop-down list. Also, the icons put into use have been brought in from the IBM graphics library also used by the Rational Software Architect (RSA) tool. So common icons to represent DoDAF 2 themes are now shared across these two modeling tools.

Before:


After:



Before:


After:



Symbols with Gradient Fill
Description
New functionality to enable symbols on diagrams to be displayed with gradient fill is now available.

IBM policy exists to ensure that a fix pack does not change anything in the product to ensure customers have no impediments (for example, new training costs) preventing them from moving to the latest fix pack; hence this new functionality must be turned on by ini file settings; in the next release it will be available by default. To turn on this feature, do the following:

  1. Select Tools, Session Options, and for the choice GraphicsEffectsOn, type in Y

    Note: Alternatively, you may also apply this change directly to your sa2001.ini file (typically located in the <C>:\Documents and Settings\Administrator\Local Settings\Application Data\Telelogic\System Architect directory) by specifying the command in bold below (under the [SystemArchitect] section:
    SA2001.INI Switches:
    [SystemArchitect]
    GraphicEffectsOn=Y
  2. (Re)start System Architect.
  3. Open or create a new diagram.
  4. Select Edit, Diagram Properties (or right-mouse click on the diagram workspace and select Diagram Properties from the popup window).
  5. In the Diagram Properties dialog, toggle on the Use Automatic Gradient Fills choice.
  6. Reopen the diagram to see the gradient fill effect on symbols.

With GraphicEffectsOn, another session option enables you to control the gradient fill:
o GraphicEffectsGradientScale enables you to specify the scaling factor used to generate the end gradient color. The lightness of the fill color in the HLS (Hue, Lightness, Saturation) color space is multiplied by this scaling factor to produce a lighter color. The valid range for this setting is 1 to 500. Values less than 100 will result in a darker end color. The default value is 300.

Once GraphicEffectsOn is set to yes, all new diagrams will have gradients enabled by default. Existing diagrams will need to be opened and have the Use Automatic Gradient Fills checkbox selected. Then the diagram must be reopened.

Benefit:
Gradient fill of symbols can be used to provide a more aesthetically pleasing view of a diagram. A diagram with Gradient Fill turned on for symbols is shown below.




Line and Metafile Smoothing with Anti-Aliasing
Description
New functionality enables you to specify that lines and shapes are drawn using anti-aliasing, resulting in smoother looking lines and symbols.
  • GraphicEffectsLineSmoothingOn enables you to specify that lines and shapes are drawn using anti-aliasing, resulting in smoother looking lines. It is defaulted on.
  • GraphicEffectsLineSmoothingWMFOn specifies that embedded WMFs in diagrams should be drawn using line smoothing.

To use this functionality:
  1. Select Tools, Session Options, and find the respective commands in the list.
  2. Set the value to Y or N to turn them on or off.

Benefit:
Smoother lines and symbols can be used to provide a more aesthetically pleasing view of a diagram.

Removal of GUIDS from Report Output
Description
As of 11.4.0.3 there is a new reporting keyword, NAMEONLY, that is used to hide GUIDS and Hetero prefixes of reference properties in report output. This is presently available for any reports generated by the native report generator or report output accessed via SA/XT in 'Updater mode'.

Note: A current limitation is that SA/XT’s Optimized Reader and SAREST do not yet support this functionality. That said, the reporting XML has been extended, so that NAMEONLY is presented in the standard properties for references; so smart use of stylesheets or coding could extract this information, even in REST or SA/XT Optimized Reader mode.

The new NAMEONLY report keyword is not yet supported in the Reporting GUI. You must Text Edit the report to apply the keyword, as follows:
  1. Create the report in the native reporting tool (select Reports, Report Generator, and then select Add in the Reports dialog to start building the report; refer to the online help for more details).
  2. Once finished, in the Reports dialog, select Report, Text Edit.
  3. Add the following to the top of the report: SETTING {NAMEONLY}

An example follows:

REPORT "Activity Changes Report"
ID 6358
{
SETTING { NAMEONLY }
FIELD "Activity <-- Activity" { SOURCE PROPERTY "Activity" LENGTH 1200 TYPE MEMO LEGEND "Activity" }
FIELD "Resource <-- Resource" { SOURCE PROPERTY "Resource" LENGTH 1200 TYPE MEMO LEGEND "Resource" }
TABULAR 1
{
SELECT "Name" LEGEND "ActivityResource", "Activity <-- Activity" LEGEND "Activity",
"Resource <-- Resource" LEGEND "Resource"
WHERE Class = Definition
WHERE "Type Number" = 1379
ORDERBY "Activity <-- Activity"
}
}

Benefit:
In DoDAF 2, all items are keyed by their own GUID, which enables powerful functionality and flexibility, however, the GUIDS of each item to this point are included in the report output, which causes sub-optimal output. You may now specify that your reports do not generate these GUIDS. When combined with new data centric behavior in DoDAF 2, and removal of GUIDS, the native report generator becomes even more powerful as a tool to generate DoDAF workproducts – enabling you to change the names of column headers, specify what goes into the report, apply stylesheets to make the report look good, and, in SA/Publisher output, regenerate the report directly to Word or Excel.

Before:


After (No GUID):


In SA/Publisher Output with Different Stylesheet Applied:
In SA/Publisher output, users may click on the Word or Excel buttons in the upper right-hand corner of each published page to automatically save the report to Microsoft Word or Excel.


III. Change Requests and Requests for Enhancements implemented in Rational System Architect 11.4.0.3

Review the Fix list for Rational System Architect to see a list of the client-reported issues (APARs) and requests for enhancements resolved in this release.




Rational System Architect 11.4.0.2

Rational System Architect 11.4.0.2 released March 25, 2011

I. Improvements Provided in Rational System Architect 11.4.0.2

Rational System Architect 11.4.0.2 features the following improvements to existing functionality:

Support for Oracle 11g (Release 2) as Backend Repository
Description
You can now create encyclopedias on Oracle11g (Release 2). This is in addition to previous support for creating encyclopedias on Oracle 10g, Microsoft SQL Server 2008 R2, Microsoft SQL Server 2008 Express, Microsoft SQL Server 2005, and Microsoft SQL Server 2005 Express.

Benefit:
Support for Oracle 11g as an underlying repository helps with System Architect deployment, as many users may have the latest version of the DBMS in their company and do not want to also support an earlier version just for SA. You are also indirectly provided with the benefits gained from the latest version of the DBMS.

Merge/Extract of Workspace Deletions
Description
The Merge/Extract utility now supports merging of deletions from one workspace to another. To facilitate this functionality, a new checkbox is available in the Merge/Extract dialog, named ‘Delete items from target where they were deleted in the source.' Also if verbose logging is turned on, the output report will specify which items were deleted.

Benefit:
This is an important piece of functionality for successful management of workspaces, which themselves enable the building and maintaining of ‘as is’ and ‘to be’ architectures, and side-by-side alternative architectures.

Quick Compare
Description
In the Object History pane (opened by selecting View, Object History), you may now select a single object and click the Compare button to view the object against all of its prior versions. This feature is not enabled by default. To enable it, see the 'Property Comparison Overview' help topic.

Benefit:
Comparison of versions of an object in an encyclopedia, or between versions in different workspaces of an encyclopedia, is an important aspect of understanding change and maintaining an enterprise architecture. Previously with Object History, you had to find all prior versions, select them, and click the Compare button. In a long list it might be difficult to locate previous versions of an object to compare. Also, in a large encyclopedia, the object history window might not show all versions of an object unless you specify a high number for the MaxObjectHistoryRecords sa2001.ini file setting. However, a high value for that setting could lead to slower load times for object history. The new feature provides much ease of use of object history.


II. Change Requests and Requests for Enhancements implemented in Rational System Architect 11.4.0.2

Review the Fix list for Rational System Architect to see a list of the client-reported issues (APARs) and requests for enhancements resolved in this release.




Rational System Architect 11.4.0.1

Rational System Architect 11.4.0.1 released December 17, 2010

Rational System Architect 11.4.0.1 is a service pack, and therefore only contains fixes to existing functionality in the tool. However, often times fixes to functionality can be interpreted as enhancements or improvements. For this reason, we highlight in this section fixes that a typical user might interpret as new functionality that they would want to be aware of.

This version introduces the following new features, enhancements, and fixes:

Representational Consistency Additions

Matrix Support
Matrices have been enabled to support the new representational consistency technology introduced in 11.4, enabling explicit as well as implicit relationships to e modeled in a matrix, and have a bidirectional effect on definitions and lines drawn on diagrams. This capability is available across the product, and has been implemented for DoDAF 2 matrices.

Line End Support
Added line end support (crows feet, multiplicity indicators) to representational-consistency based diagrams. This uses a property of the explicit relationship as a list-only to signify the type of line end desired.

Bug fixes

  • Many fixes were made to internally-reported (by Quality Assurance) representational consistency issues.
  • Fixed some internally-reported line routing and line style issues having to do with lines automatically drawn by representational consistency.

DoDAF 2.0 Additions
DoDAF 2.0 support, first released in 11.4, has had further functionality additions, as follows:

Matrices Added
  • CV-05 Capability to Organization matrix
  • CV-06 Capability to Activity - CapabilityAbleToPerformActivity represents a cell, cell text represents cell name.
  • CV-07 Capability to Service matrix
  • OV-03 Operational Resource Flow: cell is a Resource Flow, cell text represents cell name.
  • SV-03 System to System: cell is a Resource Flow, cell text represents cell name.
  • SvcV-03a Systems - Services matrix: cell is a Resource Flow, cell text represents cell name.

Definitions Added
  • “Service Data Flow (DM2rx)"
  • "System Data Flow (DM2rx)"
  • "Service Function (DM2x)"
  • "Service Resource Flow (DM2rx)"
  • "System Function (DM2x)"
  • "StdV-01 Standards Profile (DM2)"

Diagrams Added
  • "SvcV-04 Services Functionality Description (DM2)"
  • "SvcV-01 Services Context Description (DM2)"

Properties Changed
  • Diagram and definitions have had properties added, based on feedback from customers and field experts.
  • Service and Standards definitions were added as references to many areas of the meta model.
  • Renamed "Data Flow (DM2rx)" to "System Data Flow (DM2rx)"
  • Renamed "Function (DM2x)" to "System Function (DM2x)“

Default Stylesheet
  • Stylesheets have been supplied including the default color sets (e.g. burnt orange, ocean blue etc) for DoDAF2 diagrams

Bug Fixes
  • Made some usability improvements to duplicate name detection in diagrams.

MODAF 1.2 Improvements
A number of improvements were made to MODAF 1.2 support:
  • We are moving away from using UML solutions for lower-level MoDAF diagrams (such as SV-2, SOV-2, etc). New diagram types have been provided to replace the following UML based diagrams: SV-02a, SV-02b, SV-02c, SOV-02, SOV-05. The existing functionality for UML-based implementation of these diagrams remains in the tool, but turned off by default. UML is no longer selected by default for new MoDAF encyclopedia configurations.
  • The SV-01 diagram type now provides representationally consistent behavior.
  • A new SV-12 diagram type has been provided, which provides representationally consistent behavior. The older SV-12 diagram is turned off by default (it can still be used if preferred).
  • Changes were made to the metamodel in the area of Resource and Service definition types, to implement the MODAF 1.2 metamodel (the M3) more closely.

These improvements are delineated below in the client issues section, specifically Change Requests (CR’s) 56749, 56757, 56838, 57339, 57343, 57388, and 57389.

Support for Chinese Language – Traditional and Simplified
System Architect 11.4.0.1 adds support for Chinese language, both Simplified and Traditional. System Architect is now translated to these languages in addition to the others already supported (English, German, French, Japanese, and Spanish).

The System Architect installation and the help detect the language of the operating system in which it is being run, and displays the language accordingly.

For the help, you may also run it in any of the supported languages manually, with the command below that you can execute from a command prompt, or via Start, Run. The sample below is for Traditional Chinese. For the other languages, substitute the ‘zh_TW’ with these values: Simplified Chinese = zh_CN, French = fr, German = de, Japanese = ja, Spanish = es.

"C:\Program Files\IBM\Rational\System Architect Suite\help\help.exe" -nl zh_TW

Change Requests and Requests for Enhancements implemented in Rational System Architect 11.4.0.1

Review the Fix list for Rational System Architect to see a list of the client-reported issues (APARs) and requests for enhancements resolved in this release.




Rational System Architect 11.4

Rational System Architect 11.4 released September 17, 2010

Rational System Architect 11.4 contains cumulative fixes, enhancements, and new features -- meaning that it includes all fixes, enhancements, and new features from earlier releases.


DoDAF 2

Description:

In this release, System Architect provides support for the US Department of Defense Architecture Framework (DoDAF) version 2.0 (DoDAF 2), featuring a direct implementation of the DoDAF 2 metamodel (DM2). System Architect provides a data-centric implementation of DoDAF 2, as mandated by the DoDAF 2 specification, where views reflect the model, and model views are consistent between diagrams. Diagrams offer templates for data-based input to the model. Three new technological features have been added to the tool to enable DoDAF 2 support:

  • Data centricity, or model-based behaviour, featuring new ‘Explicit’ and ‘Implicit’ relationship types.
  • Meta-model Inheritance
  • Instance Modeling

DoDAF 2 support also provides capture of data for Capability, Service, Project, Operational, System, Technology, and Data views.

Support for DoDAF 1.5 and DoDAF 1.5 ABM (the Activity Based Method of MITRE Corp) continues in the product – you have the option of using DoDAF 1.5, DoDAF 1.5 ABM, or DoDAF 2 in an encyclopedia. The DoDAF 1.5 and DoDAF 2 metamodels are kept separate.

Benefit:

DoDAF is a widely used framework for building architectures in the US DoD, US civilian agencies, and governmental and commercial organizations around the globe. System Architect is the most widely used DoDAF tool. DoDAF 2 brings many new features to the table, including the data centric metamodel, which will make analysis and architecture exchange easier going forward, and support for new views such as Capabilities, Services, and Projects (for tracking acquisition).  

How to Review:

Please review the DoDAF 2 help.

BPMN 2.0 Support

Description:

Full analytical support for the Business Process Modeling Notation (BPMN) version 2.0 is provided, including notation, metamodel, and rules. The core BPMN 2.0 views are supported, including Process and Collaboration. The BPMN 2.0 support enhances and extends the previous BPMN 1.1 support. New functionality enables you to choose from three toolbars for BPMN drawing – Simple, Descriptive, and Analytic.

Support for BPMN 2.0 is provided in all three modeling interfaces – System Architect, SA/XT, and SA/Process Integrator.

Benefit:

Business Process Modeling and Analysis is a core endeavor of enterprise architecture. System Architect was the first modeling tool to support BPMN. BPMN is one of the most widely used models by users.

How to Review:

Make sure that BPMN is selected for an encyclopedia (Tools, Customize Method Support, Encyclopedia Configuration – select BPMN, and reopen the encyclopedia). The new BPMN 2.0 primitives will appear on the diagram toolbar. Note that there is now a drop-down choice for what toolbar to choose – Simple, Descriptive, and Analytic.


Model-Based Behavior

Description:

A new style of diagram behavior that offers representational consistency is now available in the tool. It is specified for use in diagram types using the metamodel language, saprops/usprops. It has been implemented throughout the DoDAF 2 support. This functionality will be implemented in other frameworks, methodologies, and diagram types in the tool in future releases.

With model-based behavior, lines between symbols on diagrams are represented by a relationship – either an Explicit Relationship, an Implicit Relationship, or an Inferred Relationship.

  • Explicit Relationships – Relationships between definitions that are supported by a definition. Explicit Relationships can be used in diagrams to represent lines. Lines will automatically use this knowledge to render themselves where model relationships exist. An Explicit Relationship is equivalent to the joining definition of a Text-in-Cell matrix. A new keyword phrase in the saprops/usprops metamodel language enables you to specify a relationship type as Explicit – REPRESENTS EXPLICIT RELATIONSHIP. You may also use the new AND_SUBTYPES keyword to specify that relationship types that inherit from a relationship type also are Explict.
  • Implicit Relationships – Reference properties in definition can be described as an implied relationship to another definition. For example, an Activity has a list-of Resources. In System Architect this is captured via a ListOf or OneOf property, and/or an ‘x-in-cell’ matrix. This relationship has no definition to actually support it. An Implicit Relationship can now be used in diagrams to represent lines. Lines will automatically use this knowledge to render themselves where model references exist. If you draw an Implicit type relationship line between two symbols, then the appropriate ListOf or OneOf property(ies) in their definitions will be populated accordingly. A new keyword phrase in the saprops/usprops metamodel language enables you to specify a relationship type as Implicit – REPRESENTS IMPLICIT RELATIONSHIP. You may also use the new AND_SUBTYPES keyword to specify that relationship types that inherit from a relationship type also are Explict.
  • Inferred Relationships – An inferred relationship is one that is discovered by running a report that traverses two or more definitions. For example, if a Tactic implements a Goal that supports an Objective, then the Tactic is related to the Objective. You have been able to visualize inferred relationships by running Explorer Relationship Reports on an Explorer diagram in this and prior releases. Now, you may also run Explorer Relationship Reports on any diagram type in System Architect.

Benefit:

Model-based behavior enables tighter metamodel implementations, easier analysis, and provides a pathway for easier integrations – the diagram always reflects the model, and therefore exchange of model information delivers the architecture without the need to navigate and pull information from diagrams. Model-based behavior, added to System Architect’s extremely customizable metamodel, and customizability with VBA, makes System Architect an extremely rich architecture tool.

How to Review:

  • Review the REPRESENTS EXPLICIT RELATIONSHIP, REPRESENTS IMPLICIT RELATIONSHIP, and AND_SUBTYPES keyword phrases in the help.
  • Review the DoDAF 2 help file for information on an implementation of these relationship types.

Running Explorer Relationship Reports on Any Diagram Type

Description:

You may now run Explorer Relationship Reports on any diagram type in System Architect. Explorer Relationship Reports visualize inferred relationships, discussed above for Model-Based Behavior.

Benefit:

You may add descriptive information to diagrams, including inferred relationships that are the result of navigating (or ‘hopping’) a series of related definitions. In DoDAF 2, ‘fit for purpose’ views enable you to add ancillary information to a diagram for presentation purposes. This functionality enables that on any diagram type, as long as the related symbol is allowed to be placed on the diagram.   

How to Review:

  • On an existing diagram, such as an Enterprise Direction Diagram, build an Explorer Relationship Report to relate two definitions represented by symbols on the diagram. Drag the Explorer Relationship Report onto the non-Explorer diagram type (ie, Enterprise Direction diagram). Note how Explorer Relationship Reports may now be run on any diagram type.


Meta-Model Inheritance

Description:

Definition types in the meta model can now inherit from a parent definition type. This includes Relationship definitions. Multiple levels of inheritance are possible. Definition types can inherit properties from other definition types, and also behavior in terms of relationships that can be drawn to the symbols representing other definition types on a diagram.

 Benefit:

Inheritance enables many usability improvements to modelling in the tool. For example in DoDAF 2, Person inherits Performer, which inherits from Resource. On an OV-2 Alternative diagram, you can draw an ActivityChangesResource line from an Activity to a Resource, or to a Performer, or to any of Performer's subtypes, such as Person.

How to Review:

For an implementation of inheritance, see the DoDAF 2 support and DoDAF 2 help. To understand how to customize the metamodel to implement inheritance, see the help concerning the keyword phrases SUBTYPE OF and AND_SUBTYPES.


Instance Modeling

Description:

Definition types may now be specified as “instantiatable” in the metamodel. This means they can have instances created from them, with instance values and instance references. For example, a Person definition type may have a property such as Height. An instance of the Person definition may be named Fred, who has a value for Height -- 5'11". Once you create a definition for a definition type, you may create an instance by right-clicking on the definition in the Explorer (browser) and selecting Create Instance. An instance object is aware of the model object that it was created from.

Benefit:

Instance modeling enables you to capture specific information about parts of your architecture. It plays an especially important role when specifying measures of things.  

How to Review:

For an implementation of instance modeling, review the DoDAF 2 support and DoDAF 2 help. To understand how to customize the metamodel to implement inheritance, see the help concerning the keywords INSTANTIABLE and SHOW_ON_INSTANCES.


TOGAF 9 Updates

Description:

The following matrices have been renamed or changed:

  • “Business Interaction Matrix” was renamed to “Business Ownership matrix”
  • Rename “Org Unit to Function” was renamed to “Org units own Functions”
  • Rename “Org Unit to Business Service” was renamed to “Org units own Business Services”
  • Rename “Business Service to Function” was renamed to “Business Service provides access to Function”
  • Stakeholder to Stakeholder Position Matrix was changed so that “position Held by stakeholder”, which was OneOf, is now ListOf (many to many).

Additional TOGAF 9 based reports are available in the Rational Publisher Engine (RPE) add-in to System Architect. The following new reports are available in RPE:
  • Stakeholder management report -- provides an understanding of the most important stakeholders and their views.
  • Technology Architecture report – you may select the Workspaces to report on, to generate Baseline and Target Architectures reports.

The following TOGAF reports have been available in Word format (by selecting Reports, TOGAF 9), and are now available in RPE:
  • Request for Architecture Work
  • Approved Statement of Architecture Work
  • Technical Architecture report
  • Architecture Building Block
  • Solution Building Block
  • Business Architecture

Benefit:

TOGAF is a widely used, open-standard framework and method for Enterprise Architecture that provides a guide for users doing EA. System Architect is a TOGAF certified tool. TOGAF 9 provides a Content Framework which has a ‘content metamodel’ -- a loose, conceptual metamodel for information capture, and Viewpoints that specify deliverables for each phase, including Catalogs (or reports), matrices, and diagrams). RPE is a tool for cross-Rational-product reporting, easy customization of reports, and generation to Microsoft Office products such as Word and Excel. TOGAF support in System Architect continues to be augmented with each release.

How to Review:

  • Select View, Matrix Browser to view the renamed or changed matrices.
  • To view and use the RPE-based TOGAF 9 reports, you need to purchase and install the RPE add-in.


Microsoft PowerPoint 2007 Live Integration

Description:

A new no-extra-charge add-in is available that enables you to create live linkages between Microsoft PowerPoint 2007 and information in the System Architect repository (or ‘encyclopedia’). You may create Active Areas in PowerPoint consisting of Definition lists and Diagrams that can be updated from SA repository. You may populate Active Areas by workspace, and present side-by-side comparisons of information (for as-is and to-be analysis, for example). The SA/XT tool is used to browse information in the repository, so an SA/XT reader license is needed to create Active Areas in PowerPoint. To synchronize a PowerPoint already created that has Active Areas, a license of SA/XT is not required – you may do this with System Architect and PowerPoint installed on your machine – the synchronization uses SA’s REST interface.

Note: This integration is only for Microsoft PowerPoint 2007.

Benefit:

With this integration, PowerPoint becomes a window into enterprise architecture information stored in SA’s encyclopedia. You can easily and effectively communicate EA information in a favorite presentation medium – PowerPoint. The presentation content is easily made up-to-date and accurate. The interface provides freedom of expression combined with the rigor of architecture. It also expands the audience of contributing participants in the EA community.

How to Review:

The Powerpoint Add-in is provided as a no-extra-charge add-in to System Architect. It is provided as a separate installation on the Passport Advantage download site. Again, you must have Microsoft PowerPoint 2007 installed to use the add-in.


Landscape-Style Explorer Diagrams

Description:

Explorer diagrams now have an additional “Landscape” style, enabling you to show visual relationships between artefacts as nested rectangles, versus the ‘Classic Style’ of lines drawn between artefacts to show direct or inferred relationships.

Benefit:

Landscape-style Explorer diagrams give you a powerful method for visually expressing relationships between artefacts in the architecture, for analysis. Landscape-style diagrams work hand-in-hand with analytics, enabling you to easily build Heatmaps of the architecture (running reports that color the symbols based on the output of an analytic report – for example, coloring red all applications that sit on servers who are being put out of service by a certain date.  

How to Review:

  1. Create an Explorer diagram (for example, select File, New Diagram and select Explorer as the type).
  2. In the Explorer Diagram Type property of the Name dialog, choose Landscape Style (the default is Network Style).
  3. Start building the Explorer diagram by running one or more Explorer Object reports (or by dragging appropriate objects from the browser) to create the symbols that will be the containers – for example, drag all the Servers of an architecture onto the diagram.
  4. Run appropriate Explorer Relationship reports to add items into the existing symbols on the diagram – for example, run an Explorer Relationship report to show, for definition type Server, the Applications it Uses.
  5. Continue to run Explorer Relationship reports to add additional objects to the diagram – for example, run an Explorer Relationship report to show, for definition type Application, the Business Processes it Uses.


Explorer Diagram General Enhancements

Description:

A number of general enhancements have been made to the Explorer Diagram:

  • Explorer Complex report – this new definition type, which may be run against an Explorer diagram, enables you to execute object and relationship reports together
  • Duplicate check setting is now optionally honored on Explorer diagrams
  • The API now has a function to Refresh Explorer diagram

Benefit:

These improvements offer ease of use and better expressiveness of Explorer diagrams, one of the most popularly used diagrams in the toolset. The Explorer Complex Report functionality makes it easy to build a diagram (instead of, for example, reporting what databases there are, then what applications there are, then what applications are related to what databases, you can build one report and run it), and remember what reports were run to build a diagram.

How to Review:

For Explorer Complex Report:

  1. Create a new definition of type Explorer Complex Report (by selecting Dictionary, New Definition or via the Explorer (browser)).
  2. Fill in the property "Explorer Reports" – which is a heterogeneous list of Explorer Object Report and Explorer Relationship Report definitions – appropriately.
  3. Run the Explorer Complex Report on an Explorer diagram – the reports listed in its Explorer Reports property are executed in order.

For the Duplicate Check functionality:
  1. Open an Explorer diagram.
  2. With the diagram open and in focus, select Tools, Preferences, and toggle off (or on) the Duplicate Check property.


Improvements to Property Dialog

Description:

The Property dialog – which is a modern and alternative dock-able dialog to edit definitions, symbols, and diagrams (and is opened by selecting View, Properties) – continues to be enhanced to provide all of the capabilities that you have with the ‘classic’ edit dialog. In this release, the Property dialog now allows:

  • Editing of OneOf and ListOf properties (including ParmOneOf, ParmListOf, Hetero one of, and Hetero ListOf properties) via a new ‘…’ choices button
  • Editing Symbol properties
  • Editing Diagram properties
  • Editing colors, using a standard color grid (color properties are available on certain definition types, for example in an Explorer Relationship Report or Analytic definition type). (Note: the standard color grid has also been added to the ‘classic’ edit dialog as well.)
  • Editing of reference documents and ability to specify URLs or files from the Files table of the current encyclopedia
  • Editing ASGRID properties via a new property grid in the Properties window – available on any property which uses the ASGRID command such as Entity attributes, Class attributes, and so forth.

Benefit:

The more modern Properties window enables much quicker access to definition properties, providing tremendous efficiency and ease-of-use over the ‘classic’ edit dialog.  

How to Review:

  1. Select View, Properties to open the Properties dialog – it may be docked any where on the frame, usually it is placed in the lower left-hand corner under the Explorer (browser).
  2. Select a definition in the browser – notice that the definition is highlighted in the Properties dialog.
  3. In the Properties dialog, click the Edit button at the top of the window to make the window editable.
  4. Notice that you can click on a “…” button for any ListOf or OneOf definition property, including the Referenced Documents property, and add or remove definitions from the list.
  5. Notice all of the other capabilities now available, based on the information provided above (and based on definition type – for example, an Entity definition now has a grid for attributes; an analytic definition now has a color grid, etc).


Improvements to References Window

Description:

The References window (opened by selecting View, References) has an improved tree view, and has had an alternative grid view added. The tree or grid view may be toggled back and forth by clicking the appropriate button at the top of the References window. The grid view enables you to sort and filter the referenced items.

Benefit:

The References window is an important vehicle for easily touring the repository to see what is related to what. In recent releases, starting with V11.3, more and more functionality has been added to the window at user request.  

How to Review:

  1. Select View, References to open the References window.
  2. Select a definition in the browser, or a symbol on a diagram, to show related information to that artefact in the References window.
  3. Notice the way the tree view now looks – it has been updated from the previous release.
  4. Click on the Grid View button at the top of the window, to view the referenced items in a grid.
  5. Select an item in the grid, and click on the Filter By Selection button (at the top of the window) to only show that type of item, or the Filter Excluding Selection button to exclude that type of item from the list. To remove the filter and show all related items, click on the Remove Filter button.

Access Control for Workspaces

Description:

Role-based access control now applies to workspaces in an encyclopedia. Using SA/Catalog Manager, you can set up role-based permissions at the workspace level. A workspace inherits the permissions set on its parent workspace.

Benefit:

Workspaces address the need to manage versions of enterprise architectures, enabling you to build as-is (baseline) and multiple to-be (target) architectures. Users have been asking for the functionality to specify role-based access based on the workspace of an encyclopedia (or repository).    

How to Review:

Use the same workflow to grant access to the objects in an encyclopedia.


Improvements to Compare Models Function

Description:

The Compare diagrams feature in System Architect and SA/XT, which enables you to visually compare two or more diagrams, has new features:

  • You may now do a time comparison of diagrams based on any date-type property in the definitions represented by symbols, using the date slider. Previously you were only allowed to do a date comparison on the properties In-Service Date and Effective Date. If you had different date-type properties in your metamodel introduced by usrprops, they were ignored for the date comparison.
  • New opacity controls are provided on the comparison output web page.
  • Opacity controls on the output web page enable you to toggle between comparing two diagrams with one overlayed on the other, or the two diagrams placed side by side. Side-by-side comparison is only provided if you are comparing two diagrams; it is not provided when you are comparing three or more.

Benefit:

Visual comparison of diagrams is an important aspect of analysis, and also of managing your enterprise architecture. In some cases an architecture may have changed simply by the symbols on a diagram moved or rearranged.

How to Review:

  1. Open a diagram, for example a BPMN diagram, and select File, Save As. Name the new diagram. On the new copy of the diagram, move a few symbols.
  2. Select Tools, Compare Diagrams, In Encyclopedia (or Across Workspaces, if you have an encyclopedia with Workspaces enabled) to open the Diagram Compare dialog.
  3. Select the two diagrams referenced in step 1, and move them into the Compare these Diagrams field.
  4. Click Compare to compare the diagrams.
  5. In the Compare Diagram Output dialog, toggle Disabled for the Time based compare choice, and click Continue. Output will be produced and opened in your default browser. Note: in IE 8, you may receive messages asking you to block an SVG Viewer Applet from loading. Click NO for the Applet to load.


Property Set Normalization

Description:

SAPROPS.CFG now split into subsets – there is a separate .cfg file for each of the frameworks or methods that are supported, and there are no dependencies between the files. A Core.cfg file holds all unresolved properties. The master set of all .cfg files are stored in <C>:\Program Files\IBM\Rational\System Architect Suite\System Architect\Property Set.

Benefit:

The master metamodel file, SAPROPS.cfg, had become difficult to navigate, with inconsistent formatting, and many complex #ifs and #endifs. This clean up and normalization makes it easier to read and understand the metamodel in place for frameworks and methods shipped out of the box.

How to Review:

The files may be viewed in the <C>:\Program Files\IBM\Rational\System Architect Suite\System Architect\Property Set directory. Note: when you create an encyclopedia, the files in that directory are populated into its Files table.


Help on Information Center

Description:

The System Architect and System Architect XT help format has been changed from .chm compiled help, to a new Eclipse-based web format and is now available online at an Information Center on IBM’s website. When you click Help, Help in the product, you view a home page that is a portal-like entry into all information about System Architect, with links to ibm.com, DeveloperWorks, RSS feeds, and so forth.

Benefit:

The Information Center will be updated independent of SA releases allowing users instant access to the latest resources. A commenting pane at the bottom allows you to provide feedback on any topic or view comments from others; comments go to writers who own the topics. You may also send top-level table of contents books to your printer or to your Adobe distiller, to generate PDF files.

Note: For secure environments, a System Admin can download the help to a local server so it can be distributed to local Rational System Architect installations. The instructions for setting up the help in secure environments are provided here:
http://publib.boulder.ibm.com/infocenter/install/v1r2/index.jsp?topic=/com.ibm.im.articles.doc/topics/t_setup_intrnet_help_content.htm

How to Review:


SA-RAM Integration

Description:

An integration between System Architect and Rational Asset Manager (RAM) is now available. You may publish and consume diagrams and definitions to/from RAM reusing the ‘Export/Import XML’ feature. The export/import is accomplished on an existing or new asset in RAM. A new definition type is available in System Architect named RAM Asset.  

Benefit:

Without an Asset approach to the EA, it becomes very hard to share, reuse, enforce, and govern the published EA. Solution Assets propagate with no compliance or association to the EA Assets, resulting in technical solutions that may not solve business problems. The integration provides governance of Assets and Enterprise Architecture. The Referenced Doc field in System Architect enables you to relate files with EA assets, but not govern the files.

The SA-RAM Integration enables you to:

  • Relate the solution assets to the enterprise assets
  • Perform EA Governance by giving all the necessary stakeholders input into the decision making; reviews, approvals, lifecycle, policies, audit trail
  • Establish Lifecycles to manage reviews and approvals
  • Enforce Policies to ensure solution architectures comply with EA

RAM enables you to govern files and collections of files (assets):
  • Build a library of assets in the organization -- Solution Assets such as Test Plans, Intent Reviews, Specifications, Training Plans, etc -- based on the published/baselined assets
  • Discover the assets of the organization through advanced search
  • Manage permissions, communities of users, reporting and metrics
  • Publish and Consume assets in context

How to Review:

Review the SA-RAM integration section of the help file.


Improved Pre-Built SA-Cognos Report Templates

Description:
Improved SA-Cognos report templates have been provided. Starting with 11.3.1.1, Cognos is now integrated and bundled with SA at no charge. The example report templates are provided on the EA myDeveloperWorks wiki (see How to Review section below). The report templates are written against a metamodel and sample data provided in an example encyclopedia that is furnished with the report templates.

Benefit:
The example report templates are provided as a convenience for sample Cognos output. Cognos reporting provides powerful Business Intelligence reporting capabilities on SA data.

How to Review:

  1. If you have not yet installed Cognos, refer to the SA-Cognos Installation and Configuration Instructions, located here: https://www.ibm.com/developerworks/mydeveloperworks/wikis/home?lang=en_US#/wiki/Rational%20Enterprise%20Architecture%20Wiki/page/SA-Cognos%20Stuff
  2. To get the new Example Report Templates, go to https://www.ibm.com/developerworks/mydeveloperworks/wikis/home?lang=en_US#/wiki/Rational%20Enterprise%20Architecture%20Wiki/page/Cognos%20Reports and click on Attachments.
  3. Download the document Instructions_for_Using_Cognos_Report_Templates_with_System_Architect_11.3-11.4.pdf, and review it for instructions on how to use the example templates.
  4. Download the SA-Cognos OOTB 11.4.zip file to get the new templates.


SA-DOORS Out-of-Box Reports for Rational Publishing Engine (RPE)

Description:

The Rational Publisher Engine paid add-on now provides out-of-box reports across System Architect and IBM Rational DOORS requirements management tool.

Benefit:

The tight integration between System Architect and DOORS is used by a large amount of customers. The new RPE cross-product reports enable easy, tailor-able output to Office products such as Word and Excel. 

How to Review:

An installation of RPE, DOORS, and SA is required.


SA/XT Improvements

SA/XT (eXtended Team) is the thin-browser sister product for System Architect, enabling you read and write access to the repository through supported browsers (IE and Firefox).

SA/XT Improvements – Visual Update

Description:

  • Restyling: SA/XT has been restyled to look and feel like a Rational Jazz web application. There are new toolbars, layout, fonts, and styles. It remains backward compatible with standard SA/XT customizations.
  • Matrix Viewer: A new read-only matrix viewer is provided in SA/XT that supports: single-click navigation to the column/row definitions, sorting, colored matrix cells, matrix cell images, and printing or export to Microsoft Office products such as Word or Excel.
  • Select Workspace in SA/XT: You may now select Workspaces in SA/XT.
  • Diagram Undo and Redo: Undo and redo is now available in SA/XT’s diagram editor (for BPMN and Org Chart drawing) via new toolbar icons. The default undo/redo size is limited to 20 operations and configured in web.config.
  • Reuse of Definitions on Diagrams: You may now reuse existing definitions when drawing in diagrams on SA/XT (BPMN and Org Charts) – similar to the functionality you have in System Architect by dragging and dropping existing definitions onto a diagram.
  • Definition and Diagram Rename: You may now rename Diagrams and Definitions in SA/XT.
  • Edit Reference Documents Property – you now have read-write capabilities on the Reference Document property in SA/XT, with options to open or remove existing links or documents, and options to add a URL link or a link to file stored in the current encyclopedia’s Files table.

Benefit:

SA/XT provides scalability of architecture. Additional functionality continues to be added to the product to provide features available in the thick client. Other features continue to be added that are unique to a web-based tool (providing advantages over the thick client).

How to Review:

Should all be self evident in the SA/XT user interface.

SA/XT Improvements – Stable URL’s

Multiple SA/XT connections to different sa encys during the same browser session. Server/ecy/workspace

Description:

Every SA XT page now has parameters appended to the page’s URL – database type, database server, and encyclopedia/workspace. You may bookmark any SA/XT URl and use them in external environments, such as emailing the URL to someone. An end user can access the target SA/XT page directly, bypassing login pages (if they are logged in). All URLs will start SA/XT sessions that are read only unless there is already a matching session that is read/write or the URL points to a page that requires read/write access such as the definition editor.

 Benefit:

You can send an email to someone and reference a particular part of the architecture. The url’s can be used as points of reference in other tools, so that you can create a mapping from information in the other tool (a process diagram in WBM, an artifact in RAM, etc) to a part of the architecture (served up live via SA/XT). This functionality enables you to create a bidirectional 'mapping' integration – in SA/XT, you can point to one or more external url’s within the Referenced Documents tab of any Definition or Diagram; the live architecture exposed via SA/XT can have a complete, bidirectional mapping to any external source that can hold a URL.

How to Review:

Copy and paste the URL of any SA/XT page into another medium, such as an email. Then open it.

Change Requests and Requests for Enhancements implemented in Rational System Architect 11.4

Review the Fix list for Rational System Architect to see a list of the client-reported issues (APARs) and requests for enhancements resolved in this release.

For more information on trials, demos, or purchasing Rational System Architect, go to the following URLs:



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Rational System Architect
Documentation

Software version:

11.4, 11.4.0.1, 11.4.0.2, 11.4.0.3, 11.4.1, 11.4.1.1, 11.4.1.2, 11.4.2, 11.4.2.1, 11.4.2.2, 11.4.2.3, 11.4.2.4, 11.4.2.5, 11.4.2.6, 11.4.2.7, 11.4.3

Operating system(s):

Windows

Reference #:

7019464

Modified date:

2014-06-13

Translate my page

Machine Translation

Content navigation