在许多的情况下，我们按照RUP中描述的从业务建模和需求分析开始。
In most cases, we would have started with business modeling and requirements analysis, as outlined in the RUP.
从业务需求到分析模型，再到实现代码的转换过程的可跟踪能力不足。
This transition from business requirements to analytic models to an implementable code isn't traceable enough.
本文提供了一些SOA架构技巧以用于从业务工件包中发现错误处理的需求以及在整个SOA分析和设计阶段如何分析这些需求。
This paper provides SOA architects techniques to discover error handling requirements from the business artifacts package and how to analyze these while going through SOA analysis and design phase.
应用推荐