Design choices and implementations that address security requirements often have an adverse impact on a solution's performance.
满足安全性需求的设计选择和实现通常会对解决方案的性能有不利的影响。
Reasons for this include cost, requirements that change as the project progresses, and organizational opposition by stakeholders of the current implementations.
这其中的原因包括所带来的成本、项目进行过程中会变化的要求以及当前实现的干系人的反对。
As an organization's requirements and complexity grow, it might need to combine applications and components that have disparate underlying implementations into an integrated solution.
随着企业的需求和复杂性的增长，可能需要把拥有完全不同底层实现的应用程序和组件组合成一个集成的解决方案。
SAM defines the SCSI systems model, the functional partitioning of the SCSI standard set, and the requirements applicable to all SCSI implementations and implementation standards.
sam定义scsi系统模型、SCSI标准集的功能性分区，以及适用于所有scsi实现和实现标准的需求。
In follow-on articles in this series, we'll create service specifications and implementations that fulfill those requirements with an architecture that enables future reuse and business agility.
在本系列文章接下来的部分中，我们将会创建能够满足这些需求的服务规格和执行，能够满足的需求支持未来的重复使用和业务敏捷性。
Both specifications provide conformance and interoperability requirements for vendors' implementations.
两个规范提供了厂商的实现的一致性和互操作性需求。
You can describe the sharing of implementations in terms of requirements and capabilities.
你可以根据需求和功能共用实现。
Implementations: These are used to identify the service's authority and express its requirements for a transactional environment.
Implementations：这些用于识别服务的权限，并向业务环境传达其需求。
For security implementations there are both explicit and implicit requirements.
对于安全实现，既有显式需求，也有隐式需求。
Most GC implementations interfere with an RT application's latency goals to the point where only tasks with larger scale and loose timing requirements can afford to rely on GC technology.
多数GC实现将妨碍RT应用程序实现其延迟目标，只有同步需求宽松的大型任务才承受得起 GC 技术引起的延迟。
Most of the complexities that requirements impose on today's software products are behavioral and functional, resulting in component implementations with complex business logic.
要求施加在当今软件产品上的大多数复杂性是行为和功能方面的，从而导致组件实现具有复杂的业务逻辑。
Once a set of business directives have been harvested, and business requirements for agility have been captured, the architectural level is responsible for harvesting the choices for implementations.
收集业务指示并捕捉敏捷性业务需求之后，架构师负责收集可供选择的实现方法。
In this thesis, we attempt to research security requirements, physical security and implementations for embedded system from algorithm and architecture levels respectively from an end-user.
从终端用户的角度，本文针对嵌入式系统的安全需求、安全实现分别从算法级和体系结构级两个层次进行重点研究。
In this thesis, we attempt to research security requirements, physical security and implementations for embedded system from algorithm and architecture levels respectively from an end-user.
从终端用户的角度，本文针对嵌入式系统的安全需求、安全实现分别从算法级和体系结构级两个层次进行重点研究。
应用推荐