Curiosity is enough reason to learn something new ...
First start with those articles : How people misunderstand RUP, what may wrong with it...
Larman,Kruchten,Bittner, How to Fail with the Rational Unified Process Read Online
Ivar Jacobson,Yes, RUP is my baby [“the baby needs correction"] Read Online
Then to understand a light-weight version of RUP read the following(s)
Kruchten, "A Software Development Process for a Team of One Read Online
Now you are ready to get more insight....RUP is iterative development process...Sou have to undestand iterative development first...For those read/watch followings:
Larman, Basili, Iterative and Incremental Development: A Brief History Read Online
Larman [Sample chapter from Applying UML & Patterns Chapter 2: Agile Iterative and Evolutionary ] Read Online
IJI Consulting, "Why Iterate? Understanding the Essentials of Iterative Development" Watch at Youtube
IJI Consulting, "Are you ready for Iterative Development" Watch at youtube
RUP is generally use-case driven development process [ it must not be "use case" driven,but generally it is ]...So learn about use cases...For those read followings:
Larman [Sample chapter from Applying UML & Patterns Chapter 2: Chapter 6: Use Cases ] Read Online
Ellen Gottesdiener, Top Ten Ways Project Teams Misuse Use Cases [I] Read Online
Ellen Gottesdiener, Top Ten Ways Project Teams Misuse Use Cases [II] [Read Online]10
Ellen Gottesdiener, "Use Cases: Best Practices", Read Online
Generally UML[Unified Modeling Language] is used in RUP based projects...[ you do not have to use it ]... So get some insight with UML...
Any process should be customized for your "situations". If you want to apply it you should create your own-adapted version such as OUP where O stands for "Odiseh" Unified Process :-) Take a look this:
Stefan Bergström [ Adopting the Rational Unified Process: Success with the RUP Chapter 1:How to Adopt RUP in Your Project ] Read Online
But those are "static info"...Actually we can NOT learn a proccess from books...We have to apply something see what works what does not...We should also able to understand how people behave in teams, what motivates them...etc...
"Process is only a second-order effect" ...[ should not forget]
RUP is not compiling with nowadays business and development environment due to complexion of documentation and time consumption I suggest you take a look at Agile software development method.
发布评论
评论（3）
好奇心是学习新东西的充分理由...
首先从这些文章开始：人们如何误解 RUP，它可能有什么问题...
Larman、Kruchten、Bittner，如何使用 Rational Unified Process 失败 在线阅读
Ivar Jacobson，是的，RUP 是我的宝贝 [“宝宝需要纠正”] 在线阅读
然后了解一个RUP 的轻量级版本请阅读以下内容
现在您已准备好获得更多见解...RUP 是迭代开发过程...因此您必须首先了解迭代开发...对于那些阅读/观看以下内容的人：
RUP 通常是用例驱动的开发过程 [ 它必须不是“用例”驱动的，但通常是]...所以了解用例...对于那些阅读以下内容的人：
一般来说，UML[统一建模语言]用于基于 RUP 的项目... [你不必使用它]...所以深入了解 UML...
任何流程都应根据您的“情况”进行定制。如果您想应用它，您应该创建自己的适应版本，例如 OUP，其中 O 代表“Odiseh”统一流程:-)
看看这个：
要获取更多信息，您可以从 http://www.eclipse.org/epf/downloads/configurations/pubconfig_downloads.php
但这些都是“静态信息”......实际上我们无法从书本上学习过程。 ..我们必须应用一些东西，看看什么有效，什么无效......我们还应该能够理解人们在团队中的行为方式，是什么激励他们......等等......
仅此而已！
Curiosity is enough reason to learn something new ...
First start with those articles : How people misunderstand RUP, what may wrong with it...
Larman,Kruchten,Bittner, How to Fail with the Rational Unified Process Read Online
Ivar Jacobson,Yes, RUP is my baby [“the baby needs correction"] Read Online
Then to understand a light-weight version of RUP read the following(s)
Now you are ready to get more insight....RUP is iterative development process...Sou have to undestand iterative development first...For those read/watch followings:
RUP is generally use-case driven development process [ it must not be "use case" driven,but generally it is ]...So learn about use cases...For those read followings:
Generally UML[Unified Modeling Language] is used in RUP based projects...[ you do not have to use it ]... So get some insight with UML...
Any process should be customized for your "situations". If you want to apply it you should create your own-adapted version such as OUP where O stands for "Odiseh" Unified Process :-)
Take a look this:
To get more information, you can download online-published version of OpenUP [which is a modifed version of RUP] from http://www.eclipse.org/epf/downloads/configurations/pubconfig_downloads.php
But those are "static info"...Actually we can NOT learn a proccess from books...We have to apply something see what works what does not...We should also able to understand how people behave in teams, what motivates them...etc...
That is all!
您可以在 Rational Unified Process 中找到一些介绍性文字最佳实践
一个好的起点是 IBM Rational
A few introducing words you find in Rational Unified Process Best Practices
A good starting point is IBM Rational
由于文档的复杂性和时间消耗，RUP 不适合当今的业务和开发环境，我建议您看一下敏捷软件开发方法。
RUP is not compiling with nowadays business and development environment due to complexion of documentation and time consumption I suggest you take a look at Agile software development method.