我认为这实际上取决于您比较的流程/方法。没有细节，只能提及 UP 的一般特征。 它是一种迭代增量方法，具有明确描述的角色和活动，在面向对象的分析和设计中使用建模技术。它被垂直（时间）地划分为阶段和迭代阶段，水平地划分为涉及软件开发不同方面的活动组，例如需求、分析、设计、测试部署等......
I think it really depends against what process/methodology you compare. Without details, only general characteristics of UP can be mentioned. It is iterative incremental methodology with well described roles and activities, using modeling techniques in object oriented analysis and design. It is vertically (time) divided in phases and those in iterations and horizontally into groups of activities concerning different aspects of software development, such as requirements, analysis, design, testing deployment etc...
作为我们是一个团队，成员可以根据项目扮演不同的角色，我们只需导航到角色，并检查手头的项目需要哪些产品。根据项目的重量/复杂性，我们将选择有助于我们日常工作的产品。 UML 是我们高度依赖的资产，并且是 OpenUP（或其他 UP 化身）中的一项优势。
Although we are not practitioners of the full UP processes, we use it frequently to see what type of products we need and which roles will have the responsibility to perform the activities for that product. We like it, because it details the various aspects from design until the deployment phase and comes with various templates, guidelines and processes which help out in the development life-cycle.
As we are a team where members can play different roles depending the projects, we simply navigate to the role, and check what products are needed for the project at hand. Depending the weight/complexity of the project we will choose the products that will help us in our daily duties. UML is an asset which we highly depend upon and comes as a benefit within OpenUP (or other UP incarnations).
我获得了 RUP 认证和 Scrum Master。大多数团队发现没有一种“现成的”流程是完美适合的。话虽如此，统一流程的重点是尽早消除项目中的风险。然而，我见过许多实现，其中 UP 仅仅因为过于复杂而引入了一定程度的风险。根据项目的性质、组织结构以及合规性和规模等其他因素，UP 提供了一组可以轻松定制的实践。
I am certified in RUP and a Scrum Master. Most teams find that no process "off the shelf" is a perfect fit. That being said, the Unified Process focuses on driving risk out of a project early. However, I have seen many implementations where UP introduces a level of risk simply by being overly complex. Depending on the nature of the project, organizational structure, and other factors such as compliance and scale, UP offers a set of practices that can be easily tailored.
发布评论
评论（3）
我认为这实际上取决于您比较的流程/方法。没有细节，只能提及 UP 的一般特征。
它是一种迭代增量方法，具有明确描述的角色和活动，在面向对象的分析和设计中使用建模技术。它被垂直（时间）地划分为阶段和迭代阶段，水平地划分为涉及软件开发不同方面的活动组，例如需求、分析、设计、测试部署等......
I think it really depends against what process/methodology you compare. Without details, only general characteristics of UP can be mentioned.
It is iterative incremental methodology with well described roles and activities, using modeling techniques in object oriented analysis and design. It is vertically (time) divided in phases and those in iterations and horizontally into groups of activities concerning different aspects of software development, such as requirements, analysis, design, testing deployment etc...
尽管我们不是完整 UP 流程的实践者，但我们经常使用它来查看我们需要什么类型的产品以及哪些角色将负责执行该产品的活动。我们喜欢它，因为它详细介绍了从设计到部署阶段的各个方面，并附带了有助于开发生命周期的各种模板、指南和流程。
看一下： http://epf.eclipse.org/wikis/openup/
作为我们是一个团队，成员可以根据项目扮演不同的角色，我们只需导航到角色，并检查手头的项目需要哪些产品。根据项目的重量/复杂性，我们将选择有助于我们日常工作的产品。 UML 是我们高度依赖的资产，并且是 OpenUP（或其他 UP 化身）中的一项优势。
Although we are not practitioners of the full UP processes, we use it frequently to see what type of products we need and which roles will have the responsibility to perform the activities for that product. We like it, because it details the various aspects from design until the deployment phase and comes with various templates, guidelines and processes which help out in the development life-cycle.
Take a look at : http://epf.eclipse.org/wikis/openup/
As we are a team where members can play different roles depending the projects, we simply navigate to the role, and check what products are needed for the project at hand. Depending the weight/complexity of the project we will choose the products that will help us in our daily duties. UML is an asset which we highly depend upon and comes as a benefit within OpenUP (or other UP incarnations).
我获得了 RUP 认证和 Scrum Master。大多数团队发现没有一种“现成的”流程是完美适合的。话虽如此，统一流程的重点是尽早消除项目中的风险。然而，我见过许多实现，其中 UP 仅仅因为过于复杂而引入了一定程度的风险。根据项目的性质、组织结构以及合规性和规模等其他因素，UP 提供了一组可以轻松定制的实践。
I am certified in RUP and a Scrum Master. Most teams find that no process "off the shelf" is a perfect fit. That being said, the Unified Process focuses on driving risk out of a project early. However, I have seen many implementations where UP introduces a level of risk simply by being overly complex. Depending on the nature of the project, organizational structure, and other factors such as compliance and scale, UP offers a set of practices that can be easily tailored.