New Whitepaper: Managing requirements across Analysis and Design phases using System Architect & DOORS
kellypuffs 06000168YK Visits (3424)
Managing requirements across Analysis and Design phases using System Architect & DOORS
This document describes why requirements need to be tracked and also explains how tracking can be setup and managed.
The IBM Rational System Architect DOORS integration helps users create abstract views in System Architect based on the user requirements in IBM Rational DOORS. Having this integration will enable users to synchronize the model with the ever changing requirements. This document can be used as a reference for users who would like to map their requirements captured in DOORS to a modeling tool Rational System Architect. Also, there would be an information flow between DOORS to System Architect and vice-versa.
Using the document provided, users can map the requirements in
DOORS to the System Architect project encyclopedia and vice versa. As a
summary, this document can prove effective as a start point for new
users who are in the process of exploring this integration and its
Many thanks to authors Rajesh Avanthi and Praveen Sreenivasan!
kellypuffs 06000168YK Visits (3394)
We have several new IEA modules available:
How to configure the RRC-RequisitePro integrationMany thanks to Steven Ma, Virgil Titarenco, Leila Ezeddin, and Gregory Kong for their work creating these modules!.
And, as always, we'd love to hear from you. Is there a topic you'd like to see in a future IEA module? Leave a comment and let us know!
Saurabh.Tyagi 270005CY2K Visits (3391)
IBM Rational Jazz token license configuration on Jazz team server
Token based licensing is an option, along with floating and authorized user licensing, within the Rational portfolio. Technically, the basis of token licensing is on the traditional floating license mechanism and process. However, when it comes to how the license check out (consumption) works, it has a different behavior.
In a token environment, each product consumes a predefined token value, not a predefined quantity as it does in a traditional floating licensing environment. The license key has a pool of tokens from which the license server automatically calculates the tokens being checked in and out across users and products.
Lets discuss how a token based licensing model can be implemented for Jazz-based products.
Jazz-based products use IBM Rational Common Licensing (RCL) token service provider, which is an extension of the Jazz Team Server (JTS) that forwards token requests to an IBM Rational License Key Server (RLKS). Jazz-based products and non Jazz-based products can share tokens from same pool of tokens.
How to generate Jazz tokens?
Log into the Rational license key center and follow the below steps to get the required Jazz tokens
You can also refer to the technote links below which will guide you in accomplishing this task:
To configure these Jazz based licenses, from a licensing perspective pre-requisites are:
The following picture shows a high level single server topology deployment of RTC using token licensing.
Once you have successfully configured your flexlm license server with token file, you downloaded from IBM Rational license key center (license.dat), Import the Jazz Keys (Jazz.Token.zip file) on the Jazz team server.
Post successful import of Jazz keys on the Jazz team server you will find an entry very similar to the below diagram
The above screen confirms that the Jazz tokens are successfully imported on the Jazz team server and we can now proceed to configure this Jazz Team Server to communicate with the Rational License Key Server that you installed and configured earlier.
In the Floating License Server section of the License Key Management page of your Jazz team server click the radio button next to IBM Rational Common Licensing Token Service to enable the service.
Hover over the icon in the Actions column until you see the edit hover. Click the icon to view the Server Configuration dialogs shown in following picture.
Configure the following two properties in the above dialog:
If the Jazz Team Server is able to connect to the Rational License Key Server, you'll see a green checkmark on the IBM Rational Common Licensing Token Service line as shown in following picture.
IBM Rational Rhapsody family provides a collaborative design, development and test environment for systems engineers and software engineers. It uses Systems Modeling Language (SysML) and Unified Modeling Language (UML) to enable rapid requirements analysis and visual, model-based design.
The UML diagrams are views into the underlying semantic system model; each kind of diagram emphasizes some aspect of the model.
Example - Dynamic aspects is represented by behavior diagram - State chart.
Statecharts define the behavior of objects by specifying how they react to events or operations. The reaction can be to perform a transition between states and possibly to execute some actions. When running in animation mode, IBM Rational Rhapsody highlights the transitions between states.
The discussion covers few modeling challenges with state chart using Rational Rhapsody and how to over come those challenges:
1) Evaluation of condition connector in state chart
A scenario where a variable (count) is decremented before the condition connector and is expected to terminate if value of variable is 9 (count==9).
However, on executing you observe that the condition doesn’t take the change in the variable on the transition. Instead it takes the initial value of the variable for comparison.
The work around here is to have an additional dummy state in between to get the desired output.
2) Multicasting with rapid ports in layered structure
Currently, the multicasts of event via rapid ports (ports that have no provided/required interfaces) are supported only from a direct invocation.
Example - One sender object and two receiver objects
Consider a scenario where the event is first sent from the Class A's object(itsA) and then it reaches the Class B's object(itsB), from where it is delegated to its 2 inner parts(itsB1 and itsB2
No multicasting is available on having multi layered structure.
The Workaround is to add an additional state chart and MULITCAST_GEN() macro in class B.
3) Working of Reaction in State
In a single state for a Reactive class, you would expect to continuously print a statement after elapse time of tm (1000). However, upon execution it prints only once instead of continuous timer.
Using a tm (1000) as a trigger for a reaction in state means that 1 second after you enter the state you'll be triggered. It's not a continuous timer.
To restart the timer you have to exit the state and re-enter it. It needs a design change as below.
4) Combining Junction Connector and Condition Connector in a state chart
You would like to have several events from a state and a condition to determine the other state.
You cannot join several transitions into a condition connector neither you can have a transition from a junction connector to a condition connector.
However, you can model to add a dummy state in between that will further evaluate for condition connector.
kellypuffs 06000168YK Visits (3385)
Various discussions with customers and questions in the forums indicate that new Projects starting to use Rational Team Concert often struggle to understand how Work Items, Planning, Build and SCM integrate. However, these fundamentals of RTC are needed to bootstrap and customize a project. This article on Jazz.net provides a basic introduction of the underlying fundamental concepts of Rational Team Concert:
An Overview of Project Fundamentals in Rational Team Concert 3.0
(photo credit: (cc) flickr user ogimogi)