Well, your intrepid adventurers have 3 days of Working Outside the Inbox under our belts and I thought this a would be a good time to discuss in a little more depth about how we are doing this.
Lets start with Step 1: Stop replying to email. This step would really be more accurately described as Mindful Processing of Email but that doesn't sound nearly as provocative and attention-grabbing, and wouldn't make nearly so many people's heads explode, which wouldn't be nearly as much fun.
So listen: this is what we are really doing.
Think of this as stopping the reflexive knee-jerk reaction of working in your inbox, simply reading and replying. We've all become very well trained by our inboxes: receive an email, send an email. Read your incoming email and then...
Stop. Think. Ask yourself a few questions along these lines:
Change begins with us (and you!)
Here are some wild and crazy ideas on how you can work effectively and openly and without being chained to your inbox:
Use the content repository or content management system of your choice as long as it's NOT YOUR MACHINE. Don't become the bottleneck, or the single point of failure. Put your stuff where people can find it and get it. When people email and ask you for that information, give them a link to the information where you've posted it.
Use wiki pages for knowledge capture and on-demand access. One example, instead of keeping your project status or metrics in a spreadsheet on your machine, think open and transparent and provide that data on a wiki page. if your manager expects a weekly status report, put it there.
discussion forums for collaboration, idea sharing and brai
Use the community blog for news, announcements, and community-wide communications. Why blog? To take advantage of all the technology that allows us to share knowledge more widely ... tags, RSS feeds, aggregators, search.... the list goes on. Rather than sending an 800mg email that immediately plunges 20% of your unsuspecting audience into "mail jail", try blogging your news. Oh, the 80% who aren't in mail jail? I posit that 40% will not read it anyway, either deliberately or by accident when it scrolls "below the fold" amidst a barrage of other people sending news, asking questions, and, worst of all, sharing files.
Besides, I bet a couple of weeks from now, someone's going to ask you for the information again anyway.
Speaking of sharing files.... There are better ways. Instead of mailing a slide deck to 10 people for review and comments, use Connections and if you MUST send an email, send a link to where you have posted the file (or the wiki page from which you are working) so that it can benefit the greatest number of people, who can then bookmark it / subscribe to it / grab the RSS feed, or otherwise self-serve when they need the information. Which means the doc owner doesn't need to send the updated file out to a cast of thousands either.
Oh, it all just makes so much SENSE.
So no, we're not giving up email entirely, and there will be times that we will (gasp!) send an email. We're just going to be mindful in our work and aim to get the maximum value from each interaction.
So, stop and think.
Just because a conversation starts in email doesn't mean it belongs there.
kellypuffs 06000168YK Visits (5017)
During August and September IBM Rational Client Support will be conducting a Customer Orientation Webcast series, geared specifically for our new Green Hat clients, but open for anyone to attend.
We are inviting you and your clients to attend our August/September Customer Orientation Webcast series, and to help ensure that you get the maximum utlization out of your IBM products.
During this informative 45 minutess presentation and Q&A, we'll explain how to:
If you know any people in your organization that are involved in administration or utilization of any Green Hat products, please let them know about this webcast that can be helpful in introducing them to IBM Support.
We look forward to meeting you at our next webcast!
kellypuffs 06000168YK Visits (4999)
From the IBMJazz channel on YouTube:
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.
AcdntlPoet 2700019V2G Visits (4930)
The new Rational License Key Administration and Reporting tool has released! Download the tool for free today, and start reporting against your usage of IBM Rational Products.
The reporting feature of the new Rational License Key Administration and Reporting tool generate license usage reports for IBM Rational Products using Flexlm and Jazz (CLM) licensing technologies. It provides reports on the use of floating and token licenses, including:
Some of the new administration features of the tool include:
For more information on downloading, installing, configuring, and using the new Rational License Key Administration and Reporting tool, see: