What does SOAD have to provide?

SOAD 必须提供什么？

SOAD for software product lines.

用于软件产品线的soad。

SOAD provides an excellent solution to these issues.

SOAD为这些问题提供了极好的解决方案。

The following requirements have been identified for soad.

已经为SOAD确定了下列需求。

They could model these issues according to the SOAD metamodel.

他们可以根据SOAD元模型来为这些问题建模。

A hybrid SOAD modeling approach is required for these reasons.

由于这些原因的存在，所以需要混合SOAD建模方法。

We will use this domain problem to illustrate the issues of SOAD.

我们将通过这个领域中的问题来阐述SOAD的观点。

Future work is certainly required to formalize the SOAD approach.

进一步的工作无疑需要形式化soad方法。

SOAD must facilitate end-to-end modeling and have comprehensive tool support.

SOAD 必须易于进行端到端建模，并且有全面的工具支持。

The SOAD movement will also have to answer the question: What is not a good service?

SOAD 活动还必须回答这样的问题：什么 不是好的服务？

Therefore, a strong link between BPM and the use case modeling activities is required for SOAD.

因此，SOAD需要BPM和用况建模活动之间的强链接。

Practicing architects have applied SOAD and the SOA guidance model successfully to more than 10 projects.

实践架构师已经在十多个项目中成功地应用了SOAD和SOA指导模型。

SOAD is an emerging field concerned with identifying and building services based on business requirements.

SOAD是一个新兴领域，它涉及到基于业务需求来确定和构建服务。

However, using SOAD to describe the issues and alternatives involves a commitment to knowledge engineering.

然而，使用SOAD描述问题和备选方案还包括对知识工程的承诺。

SOAD has to assist the SOA architect in defining a holistic, business-level view of the services landscape.

SOAD必须帮助soa架构师定义服务前景的整体业务级视图。

This leads to the notion of a service-oriented architecture (SOA), as, for example, introduced in [SOA, SOAD].

这就引出了面向服务的体系结构(SOA)的概念，例如，在[soa, SOAD]中有介绍。

Some general principles or quality factors can already be identified and act as a design baseline within soad.

一些通用原则或品质因素已经确定，并且可以作为SOAD中的设计基准。

SOAD must provide well-defined, quality factors and best practices (such as answering the granularity question).

SOAD必须提供定义良好的品质因素和最佳实践(例如回答粒度问题)。

In this section, we look at the requirements for SOAD in more detail, and start to define its themes and elements.

在这一部分中，我们将更详细地描述SOAD的需求，并且开始确定它的主题和原理。

The typical starting point in OOAD is use-case models, but the starting point in SOAD is business-process modeling.

OOAD中的典型起点是用例模型，但SOAD中的起点是业务流程建模。

SOAD enhances existing metamodels and templates,8,11 specifically by distinguishing decisions required from decisions made.

SOAD对已有的元模型和模板进行了增强8,11 ，具体说来就是将决策需求从决策制定中区分出来。

OO analysis is a very powerful and proven approach, and as such, SOAD should make use of OO analysis techniques as much as possible.

OO分析是一种非常强大且广为赞誉的方法，同样，SOAD应该尽可能多地利用OO分析技术。

SOAD doesn't claim that a decision always has the same outcome; it claims only that the issue, expressing the need for a deci-sion, recurs.

SOAD并没有声明某个决策始终会产生相同的成果；它只是表明那种对决策所需要的问题，会重现。

They saw SOAD as a supporting asset - a decision-making technique em-bedded in a general-purpose method - rather than a stand-alone method.

他们将SOAD视作一种支撑资产——一项内置在通用目标方法中的决策制定技术——而不是一种孤立的方法。

Several authors have described such SOA patterns - for example, Uwe Zdun and his colleagues.14 the SOAD framework USES the following SOA definition: 6.

有些作者已经对该SOA模式进行了描述——比如uwe Zdun和他的同事们14。

Furthermore, process modeling in SOAD must be synchronized with design-level use case modeling, and answers to the BPEL-related questions must be given.

此外，SOAD中的流程建模必须与设计层用况建模保持同步，并且必须给出与BPEL有关的问题的答案。

In addition to the combination of OOAD, BPM, and EA techniques, there are several important SOAD concepts and aspects, which have yet to be fleshed out.

除了组合ooad、BPM和ea技术之外，还有几个重要的SOAD概念和方面有待充实。

The SOAD framework lets knowledge engineers and software architects manage decision dependencies, so they can check model consistency and prune irrelevant decisions.

SOAD框架使得知识工程师以及软件架构师能够管理决策依赖，这样他们可以检查模型一致性并删除不相干的决策。

It is recognized that UML will continue to dominate as the notation of choice on the process side; enhancements will likely be required to satisfy the wider scope of SOAD.

我们还认识到，UML在流程的表示法选择方面将继续占支配地位；可能需要进行增强以满足更广泛的SOAD的要求。