﻿<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/"><channel><title>C++博客-weiyan-随笔分类-软件项目经验/UML</title><link>http://www.cppblog.com/weiyan/category/2133.html</link><description /><language>zh-cn</language><lastBuildDate>Fri, 23 May 2008 05:20:51 GMT</lastBuildDate><pubDate>Fri, 23 May 2008 05:20:51 GMT</pubDate><ttl>60</ttl><item><title>UML 主要的几种图</title><link>http://www.cppblog.com/weiyan/archive/2006/07/06/9497.html</link><dc:creator>will</dc:creator><author>will</author><pubDate>Thu, 06 Jul 2006 10:21:00 GMT</pubDate><guid>http://www.cppblog.com/weiyan/archive/2006/07/06/9497.html</guid><wfw:comment>http://www.cppblog.com/weiyan/comments/9497.html</wfw:comment><comments>http://www.cppblog.com/weiyan/archive/2006/07/06/9497.html#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.cppblog.com/weiyan/comments/commentRss/9497.html</wfw:commentRss><trackback:ping>http://www.cppblog.com/weiyan/services/trackbacks/9497.html</trackback:ping><description><![CDATA[
		<p>
				<img alt="" src="http://p.blog.csdn.net/images/p_blog_csdn_net/iright/209851/o_class.JPG" />
		</p>
		<p>
				<span lang="EN-US" style="FONT-SIZE: 9pt; COLOR: #424542; FONT-FAMILY: Verdana; mso-fareast-font-family: 仿宋_GB2312; mso-bidi-font-family: 'Times New Roman'; mso-font-kerning: 1.0pt; mso-ansi-language: EN-US; mso-fareast-language: ZH-CN; mso-bidi-language: AR-SA">
						<strong>Class Diagrams<br /></strong>
				</span>
				<span lang="EN-US" style="FONT-SIZE: 9pt; COLOR: #424542; FONT-FAMILY: Verdana; mso-fareast-font-family: 仿宋_GB2312; mso-bidi-font-family: 'Times New Roman'; mso-font-kerning: 1.0pt; mso-ansi-language: EN-US; mso-fareast-language: ZH-CN; mso-bidi-language: AR-SA">Class diagrams are the backbone of almost every object oriented method, including UML. They describe the static structure of a system.</span>
		</p>
		<p>
				<span lang="EN-US" style="FONT-SIZE: 9pt; COLOR: #424542; FONT-FAMILY: Verdana; mso-fareast-font-family: 仿宋_GB2312; mso-bidi-font-family: 'Times New Roman'; mso-font-kerning: 1.0pt; mso-ansi-language: EN-US; mso-fareast-language: ZH-CN; mso-bidi-language: AR-SA">
				</span>
		</p>
		<p>
				<img alt="" src="http://p.blog.csdn.net/images/p_blog_csdn_net/iright/209851/o_object.JPG" />
		</p>
		<p>
				<strong>Object Diagrams</strong>
				<br />Object diagrams describe the static structure of a system at a particular time. They can be used to test class diagrams for accuracy.<br /></p>
		<p>
				<img alt="" src="http://p.blog.csdn.net/images/p_blog_csdn_net/iright/209851/o_use-case.JPG" />
				<br />
				<strong>Use Case Diagrams<br /></strong>Use case diagrams model the functionality of system using actors and use cases.</p>
		<p>
				<br />
				<img alt="" src="http://p.blog.csdn.net/images/p_blog_csdn_net/iright/209851/o_activity.JPG" />
				<br />
				<strong>Activity Diagrams<br /></strong>Activity diagrams illustrate the dynamic nature of a system by modeling the flow of control from activity to activity. An activity represents an operation on some class in the system that results in a change in the state of the system. Typically, activity diagrams are used to model workflow or business processes and internal operation. </p>
		<p> </p>
		<p>
				<img alt="" src="http://p.blog.csdn.net/images/p_blog_csdn_net/iright/209851/o_sequence.JPG" />
				<br />
				<strong>Sequence Diagrams</strong>
				<br />Sequence diagrams describe interactions among classes in terms of an exchange of messages over time.</p>
		<p>
				<br />
				<img alt="" src="http://p.blog.csdn.net/images/p_blog_csdn_net/iright/209851/o_collaboration.JPG" />
				<br />
				<strong>Collaboration Diagrams</strong>
				<br />Collaboration diagrams represent interactions between objects as a series of sequenced messages. Collaboration diagrams describe both the static structure and the dynamic behavior of a system. </p>
		<p> </p>
		<p>
				<img alt="" src="http://p.blog.csdn.net/images/p_blog_csdn_net/iright/209851/o_statechart.JPG" />
				<br />
				<strong>Statechart Diagrams</strong>
				<br />Statechart diagrams describe the dynamic behavior of a system in response to external stimuli. Statechart diagrams are especially useful in modeling reactive objects whose states are triggered by specific events.</p>
		<p> </p>
		<p>
				<img alt="" src="http://p.blog.csdn.net/images/p_blog_csdn_net/iright/209851/o_component.JPG" />
				<br />
				<strong>Component Diagrams</strong>
				<br />Component diagrams describe the organization of physical software components, including source code, run-time (binary) code, and executables.</p>
		<p> </p>
		<p>
				<img alt="" src="http://p.blog.csdn.net/images/p_blog_csdn_net/iright/209851/o_deployment.JPG" />
				<br />
				<strong>Deployment Diagrams<br /></strong>Deployment diagrams depict the physical resources in a system, including nodes, components, and connections. </p>
		<p> </p>
		<img alt="" src="http://p.blog.csdn.net/images/p_blog_csdn_net/iright/209851/o_package.JPG" />
		<br />
		<strong>Package Diagrams<br /></strong>Package diagrams are a subset of class diagrams, but developers sometimes treat them as a separate technique. Package diagrams organize elements of a system into related groups to minimize dependencies between packages<img src ="http://www.cppblog.com/weiyan/aggbug/9497.html" width = "1" height = "1" /><br><br><div align=right><a style="text-decoration:none;" href="http://www.cppblog.com/weiyan/" target="_blank">will</a> 2006-07-06 18:21 <a href="http://www.cppblog.com/weiyan/archive/2006/07/06/9497.html#Feedback" target="_blank" style="text-decoration:none;">发表评论</a></div>]]></description></item></channel></rss>