Each ROLE do an ACTIVITY and as a result a produce a WORK PRODUCTS...
For example Analyst [Role] Develop Vision [Activity] as a result we will have Vision [Work Product]...
Besides this RUP gives us some GUIDELINES and CHECKLIST to do right our ACTIVITY and WORK PRODUCTS...
RUP gives us templates for WORK PRODUCTS but they are just to give an idea what they may be look like...
Suppose for vision you can use RUP template but you can just use a post-it notes and just write an "elavator statement" like this:
For [target customer] Who [statement of the need or opportunity] The (product name) is a [product category] That [statement of key benefit; that is, the compelling reason to buy] Unlike [primary competitive alternative] Our product [statement of primary differentiation]
Even Work products can be simple statements that you write on your WIKI...They can be in any form...
They must not be "static written" docs... They can even be "video" . Suppose instead of writing Softaware Architecture docs [Architecture Notebook in OpenUP] you can just create a video in which your team explain main architecture on white board....
****WARNING FOR RUP WORKPRODUCTS TEMPLATES:**
DO NOT BECAME A TEMPLATE ZOMBIE.YOU SHOULD NOT FILL EVER PARTS OF IT... YOU SHOULD ASK YOURSELF, WHAT KIND OF BENEFIT WILL I GET BY WRITING THIS...IF YOU HAVE NO VALID ANSWER, DO NOT WRITE... DOCUMENTATION SHOULD HAVE REAL REASONS, DO NOT MAKE DOCUMENTATION JUST FOR "DOCUMENTATION"...**
RUP has rich set of WORK PRODUCTS...So chose minumum of them which you will get most benefit...
For a typical projects generally you will have those Requirements Work Products:
Vision : What we do and Why we do? Agrement of StakeHolders...
Suplemantary Specification [ System-Wide Requirements in OpenUP] : Generally capture non-functional [ which the term i do not like] or "quality" [ which i like"] requirements of system.
Use-Case Model : Capture function requirements as Use-Cases
Glossary : To make concepts clear...
RUP is commercial but OpenUP is not...So you can look OpenUP WORK PRODUCTS templates just to get an idea what kind of info is recorded in them...
Try the Rational Unified Process page at Wikipedia for an overview.
The core requirements should be documented in the project description. RUP tends to place a lot of emphasis on "use cases", however it is very important not to lose sight of the original requirements at all levels of detail, because these will answer the "Why?" questions. If the developers only see the uses cases, they will know What they are supposed to build (effectively the functional requirements) but not Why it is required. Unless the developers have easy access to the original analysts, this can cause very serious problems.
发布评论
评论（2）
RUP 有 3 个主要部分：
每个角色执行一项活动，并因此产生一个工作产品...
例如分析师 [角色] 开发愿景 [活动]，因此我们将有愿景 [工作产品]...
此外，RUP 还为我们提供了一些指导方针和清单，以正确执行我们的活动和工作产品...
RUP 为我们提供了工作产品模板，但它们只是为了让我们了解它们可能是什么看起来像...
假设对于愿景，您可以使用 RUP 模板，但您可以只使用便利贴并编写一个“电梯声明”，如下所示：
即使工作产品也可以是您在 WIKI 上编写的简单陈述...它们可以采用任何形式...
它们不能是“静态编写”文档 ...它们甚至可以是“视频”。
假设您可以创建一个视频，让您的团队在白板上解释主要架构，而不是编写软件架构文档 [架构笔记本 in OpenUP]
。 *RUP 工作产品模板警告：**
不要成为模板僵尸。您不应该填写其中的任何部分...
你应该问自己，写这篇文章会给我带来什么好处……如果你没有有效的答案，请不要写……
文档应该有真正的理由，不要仅仅为了“文档”而制作文档...**
RUP 拥有丰富的工作产品集...所以选择其中您将获得最大收益的最小值...
对于典型的项目，通常您将拥有这些需求工作产品：
愿景：我们做什么以及为什么要做？利益相关者协议...
补充规范 [OpenUP 中的系统范围要求]：
一般捕获非功能性的[我不喜欢这个术语]或
系统的“质量”[我喜欢"]要求。
用例模型：将功能需求捕获为用例
术语表：使概念清晰...
RUP 是商业的但 OpenUP 不是...所以您可以查看 OpenUP WORK PRODUCTS 模板，只是为了了解其中记录了什么样的信息...
从以下位置下载：
Eclipse 进程框架项目 http://www.eclipse.org/epf/downloads/configurations /pubconfig_downloads.php 并从索引页开始阅读：
...-->
...--->
--->
----->
--->
....>................................. ........
---->................................................. ...
最后，您可以在 Larman 的书《Applying UML and》中找到以敏捷方式使用这些工作产品的方法模式...
再说一遍：不要成为模板僵尸！！！
RUP has 3 main parts:
Each ROLE do an ACTIVITY and as a result a produce a WORK PRODUCTS...
For example Analyst [Role] Develop Vision [Activity] as a result we will have Vision [Work Product]...
Besides this RUP gives us some GUIDELINES and CHECKLIST to do right our ACTIVITY and WORK PRODUCTS...
RUP gives us templates for WORK PRODUCTS but they are just to give an idea what they may be look like...
Suppose for vision you can use RUP template but you can just use a post-it notes and just write an "elavator statement" like this:
Even Work products can be simple statements that you write on your WIKI...They can be in any form...
They must not be "static written" docs... They can even be "video" .
Suppose instead of writing Softaware Architecture docs [Architecture Notebook in OpenUP] you can just create a video in which your team explain main architecture on white board....
****WARNING FOR RUP WORKPRODUCTS TEMPLATES:**
DO NOT BECAME A TEMPLATE ZOMBIE.YOU SHOULD NOT FILL EVER PARTS OF IT...
YOU SHOULD ASK YOURSELF, WHAT KIND OF BENEFIT WILL I GET BY WRITING THIS...IF YOU HAVE NO VALID ANSWER, DO NOT WRITE...
DOCUMENTATION SHOULD HAVE REAL REASONS, DO NOT MAKE DOCUMENTATION JUST FOR "DOCUMENTATION"...**
RUP has rich set of WORK PRODUCTS...So chose minumum of them which you will get most benefit...
For a typical projects generally you will have those Requirements Work Products:
Vision : What we do and Why we do? Agrement of StakeHolders...
Suplemantary Specification [ System-Wide Requirements in OpenUP] :
Generally capture non-functional [ which the term i do not like] or
"quality" [ which i like"] requirements of system.
Use-Case Model : Capture function requirements as Use-Cases
Glossary : To make concepts clear...
RUP is commercial but OpenUP is not...So you can look OpenUP WORK PRODUCTS templates just to get an idea what kind of info is recorded in them...
Download it from and
Eclipse Process Framework Project http://www.eclipse.org/epf/downloads/configurations/pubconfig_downloads.php and start reading from index page:
...-->
...--->
--->
----->
--->
....>.........................................
---->.......................................
Lastly you can find usage of those WORK PRODUCTS in an agile manner at Larman book Applying UML and Patterns...
And again : DO NOT BECAME A TEMPLATE ZOMBIE!!!
请尝试 Wikipedia 上的 Rational Unified Process 页面来了解概述。
核心要求应记录在项目描述中。 RUP 倾向于非常重视“用例”，但是不要忽视各个细节级别的原始需求，这一点非常重要，因为这些将回答“为什么？”问题。如果开发人员只看到用例，他们就会知道他们应该构建什么（实际上是功能需求），但不知道为什么需要它。除非开发人员能够轻松接触到原始分析师，否则这可能会导致非常严重的问题。
Try the Rational Unified Process page at Wikipedia for an overview.
The core requirements should be documented in the project description. RUP tends to place a lot of emphasis on "use cases", however it is very important not to lose sight of the original requirements at all levels of detail, because these will answer the "Why?" questions. If the developers only see the uses cases, they will know What they are supposed to build (effectively the functional requirements) but not Why it is required. Unless the developers have easy access to the original analysts, this can cause very serious problems.