The reason for describing it as a separate scenario is because it is different from an application design point of view.
将其作为一种单独的场景进行描述的原因是，从应用程序设计的角度来看，它有所不同。
Hence, the development approach that is followed is not the classic "waterfall" scenario, where requirements gathering is followed by analysis and design, leading to the implementation of the system.
因此，随后的开发方法不是典型的“瀑布”方案，在瀑布方案中，收集需求之后进行分析和设计，并进行系统的实现。
Figure 6 depicts the application design flow for this scenario.
图6描述了该场景的应用程序设计流程。
The overall design goal is not to complicate the scenario by providing unnecessary flashy screens on the client tier.
总的设计目标是不要让场景复杂化，所以在客户端上不提供不必要的浮华的屏幕。
By now, you should have a good idea about the high-level design goals of this scenario.
现在，您应该对这个场景的高层设计目标有了清晰的认识。
In this scenario, the developer is abdicating much of the responsibility for the design and for code quality.
在这种情况下，这个开发者实际上是放弃了很多在设计和代码质量上的责任。
This scenario aligns the modeling of business design and IT solution design through a set of roles, methods, and artifacts.
该场景通过一组角色、方法和构件，使业务设计与IT解决方案设计的建模工作趋于一致。
Figure 4 depicts the application design flow for this scenario.
图4描绘了用于该场景的应用程序设计流。
This scenario was built step by step in the first article in this series; this section discusses the key design considerations for the scenario.
此场景是在本系列的第一篇文章中分步构建的；本部分将讨论此场景的关键设计注意事项。
These websites incorporate many design elements, a perfect scenario in which to use a fixed layout.
这些网站无不融合了大量设计元素，利用固定布局创建出完美的场景。
This design to separate the services is what we will implement for our scenario.
分离服务的设计正是我们的场景所要实现的。
Although the design had been tested through a number of scenario diagrams, coding continued to uncover inaccurate or missing details over the following weeks and months.
虽然设计已经通过众多的场景图被测试过了，但是在接下来的数周和数月的编码中将发现设计中不正确的地方或者或者遗漏的细节。
In this scenario, however, it is still likely the team will be dependent on external design documents that may not be generated until later in the project lifecycle.
然而，在这种情景下，这个团队很可能依靠于那些直到在项目生命周期的晚期才生成的外部设计文档。
There is one particular scenario, however, where I can refactor the design one step further for optimum results.
不过，还有一个特殊的场景，我可以再进 一步努力，以得到最佳的结果。
In this transformation scenario, it's imperative that you consider careful implementation design for the SOA it infrastructure.
在此转换场景中，必须仔细考虑SOAIT基础设施的实现设计。
Invite customers to participate in your design and scenario definition efforts; ask them to engage directly with the development teams.
邀请客户参与你的设计；要求他们直接到开发团队。
Try modeling this scenario using the Chain of Responsibility Design Pattern in Rational Software Architect.
尝试在RationalSoftwareArchitect 中使用责任链设计模式为该情境建模。
Eric Evans, author of "Domain Driven Design", once asked what the difference was between a scenario and a use case.
“领域驱动开发”的作者EricEvans有一次被问到，场景和用例之间有什么分别。
Benefits of Unified Scenario-Based design.
统一的基于场景的设计的好处。
The UML 2.0 Profile for Unified Scenario Based design.
用于基于统一场景设计的UML 2.0规范。
The integration scenario follows these design principles.
集成场景遵循以下设计原则。
The simplest scenario for Editor level users is when no changes are made to the template and the template's design elements still have the signature of "Lotus Notes template Developers."
针对编辑者权限级别用户最简单的场景是当没有对模板做任何更改并且模板的设计元素仍然具有“LotusNotesTemplate Developers”签名的时候。
The scenario considers a RIA accessing a database without transferring any sensitive data by using a 3-tier design.
在场景中，要求通过一种3层设计，使RIA能够访问数据库，同时又无需传输任何敏感数据。
This article described a scenario and the design of a custom event handler that integrates IBM WebSphere ILOG JRules with Content Manager.
本文描述了一个场景和一个定制的事件处理器的设计，这个定制的事件处理器整合了IBMWebSphereILOGJRules和Content Manager。
In this business scenario, IBM Rational Asset Manager was an integral part of development throughout the research, design, implementation, review, and deployment phases of this project.
在这个业务场景中，IBMRationalAssetManager贯穿于项目的研究、设计、实施、复审和部署和开发各个阶段。
This scenario illustrates how using WebSphere Developer teamed with TXSeries can help you rapidly design, code, and deploy complex CICS applications.
此方案说明了如何将WebSphereDeveloper和TXSeries结合使用，以帮助快速设计、编码和部署复杂的CICS应用程序。
The scenario described in this article uses operational data stored in DB2 pureXML as input to the extract, transform, and load (ETL) job that you'll design to populate a DB2-based data warehouse.
本文描述的场景使用DB2pureXML中存储的操作型数据作为提取、转换和装载（ETL）任务的输入， 这些任务用于填充一个基于DB2 的数据仓库。
In this scenario, unless the developer has an understanding of how the data is to be used by downstream products, she will not be able to properly design the persistence strategy for the data.
在这种情况下，除非开发人员知道这些数据在下游产品中的用途，否则他不可能很好地为这些数据设计出持久性策略。
A more realistic scenario is that a new requirement is introduced to a project that requires a design change.
还有一种现实一些的情况是项目中加入了新的需求，需要对设计进行修改。
You'll learn more about the operational data and the data warehouse design as you step through each scenario.
学习这些场景时，您将更多地了解运营数据和数据仓库设计。
应用推荐