<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: RMC 7.5 released today</title>
	<atom:link href="http://blog.haumer.net/rational-method-composer/61/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.haumer.net/rational-method-composer/61</link>
	<description>Process engineering with the Eclipse Process Framework and Rational Method Composer</description>
	<lastBuildDate>Tue, 28 Sep 2010 11:39:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Peter</title>
		<link>http://blog.haumer.net/rational-method-composer/61/comment-page-1#comment-1688</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Thu, 30 Oct 2008 00:13:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.haumer.net/?p=61#comment-1688</guid>
		<description>Thanks for your feedback Marc. 

(1) Yes, we are going to release the Method Authoring Method (MAM) as a download for customers soon (I will announce it here in the blog, once it comes online). This is a method framework that our team created to document exactly what you are asking for: our practices for designing, managing, and authoring method content and processes with RMC. It has a particular focus on the Practices library that ships with 7.5 as it represent the current reference architecture that we also recommend to clients for their own content. Actually, if you follow the design guidelines described there you would be able to easily combine your content with content from any of the practices that we ship.

(2) I agree with you. This is one of the downsides working in a large organization such as IBM: some design decisions for shared components are not made by the product teams. Hence, we had to live with the way RAM contributes its content. I actually filed this as a defect against the RAM client, as it really a supplementary tool that should not take over the online help like that.  I hope this can be fixed in the near future. Same with the Glossary. It was an IBM mandate that we had to link to the global IBM glossary and add our terms to it there. Of course, with a 300k organization like IBM you get a very large corporate glossary and you now have to sift through hundreds of terms that you are not interested in. I do not understand the rationale behind that decision myself, but this is just my personal view on this.</description>
		<content:encoded><![CDATA[<p>Thanks for your feedback Marc. </p>
<p>(1) Yes, we are going to release the Method Authoring Method (MAM) as a download for customers soon (I will announce it here in the blog, once it comes online). This is a method framework that our team created to document exactly what you are asking for: our practices for designing, managing, and authoring method content and processes with RMC. It has a particular focus on the Practices library that ships with 7.5 as it represent the current reference architecture that we also recommend to clients for their own content. Actually, if you follow the design guidelines described there you would be able to easily combine your content with content from any of the practices that we ship.</p>
<p>(2) I agree with you. This is one of the downsides working in a large organization such as IBM: some design decisions for shared components are not made by the product teams. Hence, we had to live with the way RAM contributes its content. I actually filed this as a defect against the RAM client, as it really a supplementary tool that should not take over the online help like that.  I hope this can be fixed in the near future. Same with the Glossary. It was an IBM mandate that we had to link to the global IBM glossary and add our terms to it there. Of course, with a 300k organization like IBM you get a very large corporate glossary and you now have to sift through hundreds of terms that you are not interested in. I do not understand the rationale behind that decision myself, but this is just my personal view on this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marc Hoffmann</title>
		<link>http://blog.haumer.net/rational-method-composer/61/comment-page-1#comment-1686</link>
		<dc:creator>Marc Hoffmann</dc:creator>
		<pubDate>Wed, 29 Oct 2008 21:49:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.haumer.net/?p=61#comment-1686</guid>
		<description>Hello Peter,

I am EmeriCon&#039;s Chief Methodologist and have only recently used RMC to better document our methodologies. I have enjoyed browsing through your blog, which provides very helpful and very insightful information for a beginner like me.

I have two questions/comments for you:
1. Do you have any documentation, white papers, forum threads that discuss &quot;best practices&quot; on how to structure your method plug-ins? For example, what should be the granularity of tasks, activities, and processes? What are recommended ways to structure plug-ins, to allow a lot of reuse at a &quot;base&quot; plug-in level?

2. I started using RMC 7.5 today after having worked in RMC 7.2 for a few weeks. I am a little concerned about the Help section. It seems that an awful lot of RAM information is included and it seems to confuse me. The RMC 7.2 Help included a very useful Glossary, which seems to have been removed from 7.5. Do you have any idea where it went?

Thank you again for sharing your knowledge with the RMC user community.

Marc</description>
		<content:encoded><![CDATA[<p>Hello Peter,</p>
<p>I am EmeriCon&#8217;s Chief Methodologist and have only recently used RMC to better document our methodologies. I have enjoyed browsing through your blog, which provides very helpful and very insightful information for a beginner like me.</p>
<p>I have two questions/comments for you:<br />
1. Do you have any documentation, white papers, forum threads that discuss &#8220;best practices&#8221; on how to structure your method plug-ins? For example, what should be the granularity of tasks, activities, and processes? What are recommended ways to structure plug-ins, to allow a lot of reuse at a &#8220;base&#8221; plug-in level?</p>
<p>2. I started using RMC 7.5 today after having worked in RMC 7.2 for a few weeks. I am a little concerned about the Help section. It seems that an awful lot of RAM information is included and it seems to confuse me. The RMC 7.2 Help included a very useful Glossary, which seems to have been removed from 7.5. Do you have any idea where it went?</p>
<p>Thank you again for sharing your knowledge with the RMC user community.</p>
<p>Marc</p>
]]></content:encoded>
	</item>
</channel>
</rss>

