<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
	<channel>
		<title><![CDATA[Latest posts for the topic "How to use UML diagrams correctly?"]]></title>
		<link>http://forums.visual-paradigm.com/posts/9.html</link>
		<description><![CDATA[Latest messages posted in the topic "How to use UML diagrams correctly?"]]></description>
		<generator>JForum - http://www.jforum.net</generator>
			<item>
				<title>How to use UML diagrams correctly?</title>
				<description><![CDATA[ Hello,<br> <br> I am new here. I have read many articles and tutorials about UML diagrams. I have created few test diagrams as well.  From the point of view of developing a software system, which diagram we should develop first and which later?  I mean if I have to design a system, how should I start building and finalize the requirement?<br> <br> ]]></description>
				<guid isPermaLink="true">http://forums.visual-paradigm.com/posts/2311#18514.html</guid>
				<link>http://forums.visual-paradigm.com/posts/2311#18514.html</link>
				<pubDate><![CDATA[Sun, 15 Jul 2007 15:27:02]]></pubDate>
				<author><![CDATA[ Anonymous]]></author>
			</item>
			<item>
				<title>Re:How to use UML diagrams correctly?</title>
				<description><![CDATA[ Start with use case diagram, from developer view. If you are somehow involved in requirement analysis, then you will also need to understand requirements, they may defined as use cases from customer view! Then you can specify your workflows (if they are not very complex) using activity diagrams. <br> Ask me again, as soon as you have finilized above tasks. :) <br> ]]></description>
				<guid isPermaLink="true">http://forums.visual-paradigm.com/posts/2311#18898.html</guid>
				<link>http://forums.visual-paradigm.com/posts/2311#18898.html</link>
				<pubDate><![CDATA[Wed, 15 Aug 2007 20:27:44]]></pubDate>
				<author><![CDATA[ Guruli]]></author>
			</item>
	</channel>
</rss>