开发治理模型的流程基于一个具有三个步骤的方法。
The process you can use to develop a governance model is based on a three-phase approach.
可能的工具包括带集成开发环境(IDE)、制图工具的接口构建包,甚至基于模型的自动生成的接口。
Possible tools include interface builders packaged with integrated development environments (IDEs), diagramming tools, all the way up to auto-generated interfaces based on models.
这个说明将描述如何根据场景设计、开发这个原型模型并描述将用于评估的指标,“基于场景的poc评估”小节将详细介绍这个说明。
The description on how the prototype model is to be designed, developed based on scenario and metrics to be evaluated are presented in the section, "scenario based PoC evaluation".
同时我们看到开发人员对基于容器的技术感到痛苦,并转而求助于象Spring或Mule这样的更轻量级编程模型。
At the same time we have seen developers being burned by container based technologies and turned to lighter weight programming model such as Spring or Mule.
附带的WebSphereIntegrationDeveloper基于Eclipse,并且为开发和组装服务或构建业务流程模型提供了通用的集成环境。
Companion WebSphere Integration Developer is based on Eclipse and provides a common integrated environment to develop and assemble services or build business process models.
在Win32系统中开发的C++代码是基于ILP32模型的,在该模型中,int、long和指针类型都是32位的。
C + + code developed in Win32 systems is based on the ILP32 model, where int, long, and pointer types are 32 bits.
随着象Windows这样基于GUI操作系统的出现,GUI开发平台依靠复杂事件模型来设计和构建单个应用。
With the arrival of GUI-based operating systems like Windows, platforms for GUI development relied on complex event models to design and build standalone applications.
基于NoSQL数据库的应用程序开发模型也面临挑战,因为它增加了实现的复杂性。
Their application development model is challenging, adding to the complexity of the implementation.
本系列第1部分描绘出模型驱动和基于模式的开发范例的全景。
Part 1 of this series lays out the picture of the model-driven and pattern-based development paradigm.
随着设计决策被制定下来,记录它们的特性是重要的,包括它们对未开发完的产品及其基于模型的表现会有什么效果。
As design decisions are made, it is important to capture their essence, including what effects they will have on the product under development and its model-based representation.
到目前为止,模型驱动的开发(MDD)以及与其相关的、基于UML的工具已经存在了十多年。
Model Driven Development (MDD), together with its associated UML-based tools, has been around for more than a decade now.
值得提到的是在此工作中的用例模型所扮演的重要角色与在任何基于RUP的软件开发项目中一样。
It is worth mentioning the central role played by the use-case model in this work as in any RUP-based software development project.
开源开发打破了这种束缚。基于源代码,测试者和开发者可以很容易建立一个统一的模型,并借此有效沟通。
Open-source development breaks this bind, making it far easier for tester and developer to develop a shared representation grounded in the actual source code and to communicate effectively about it.
RMC支持基于不同开发方法的过程,并可用于定义不同的生命周期模型,例如瀑布,递增,或迭代生命周期模型。
RMC supports processes based on different development approaches and can be used to define different lifecycle models such as waterfall, incremental, or iterative lifecycles.
对于敏捷开发,开发人员团队在一定的时间期限内完成大量力所能及的事情,该时间期限支持基于时间的支付模型。
With agile development, a team of developers does as much as they can in a certain time frame, which supports a time-based payment model.
在此,我使用的术语,基于模型的系统开发是非常广义的,基本上覆盖了系统分析和设计工作流。
I use the term model-based systems engineering in a very broad sense here, basically covering the systems Analysis and Design workflows.
IBM已经开发了一个新的MDD和基于模式的工程(PBE)过程,以及相关的工具,它简化并自动化了模型中约束的使用。
IBM has developed a novel MDD and pattern-based engineering (PBE) process, along with associated tooling, which simplifies and automates the use of constraints within a model.
MDA在一个基于标准的、模型驱动开发方法的框架内完成整个开发生命周期。
MDA addresses the development life cycle from within a framework of a standards-based, model-driven development approach.
早期的远程过程调用(rpc)是基于一种编程模型的,开发人员编写专门的过程调用。
Earlier remote procedure call (RPC) standards were based on a programming model where a developer wrote specific procedure calls.
您必须针对您自己的XDE技巧和个人的偏爱决定在过程的哪一点将基于XDE的模型转移到纯j 2ee开发。
You must rely on your own XDE skills and personal preferences to determine at what point in the process you should move from XDE-based modeling to pure J2EE development.
这些开发人员可以从转向基于SOAP或基于XML -RPC的通信模型中获益匪浅。
These developers could gain a lot from moving to a SOAP-based or XML-RPC-based communication model.
这些抽象层让开发人员可选择是使用基于特性标记的声明语法,还是使用基于嵌套控件的命令模型来开发。
These abstraction layers give developers the option to use a declarative syntax based on attributes or an imperative model based on nested controls.
然而,MDD所使用的基于代码生成的方法有它不利的方面,这是由于例如所生成代码中的约束、技术不强的开发人员和与模型的紧耦合等因素造成的。
However, the code generation-based approach used by MDD has its own downside, due to things like constraints in generated code, insufficiently skilled developers, and tight coupling to the model.
即使不考虑通过由模型驱动的开发和基于SOA的服务管理所提高的效率,业务应用程序仍须保护信息。
Irrespective of the efficiencies brought by model-driven development and SOA-based service management, business applications must continue to secure information.
所开发用于指定基于SOA的解决方案的功能的流程模型应该遵循图2中所示的分解结构。
Process models developed to specify functions of an SOA-based solution should follow the decomposition structure in Figure 2.
基于模型的方法能实现更好的业务-技术一致性,为新解决方案的设计和开发提供所需资产(服务和流程)。
The model-based approach enables better business-technical alignment and provides assets (services and processes) for the design and development of new solutions.
这些标准使得工程师和软件设计师可以通过将基于代码的开发进程转化为模型驱动的开发(MDD),来极大地改进效率。
These standards enable engineers and software designers to significantly improve their productivity by transitioning from a code-based development process to model-driven development (MDD).
与此同时,芝加哥商品交易所开发了一种基于场景的模型,设计它的目的时计算系统风险和异常风险。
CME, meanwhile, has developed a scenario-based model designed to take into account systemic and idiosyncratic risk factors.
与此同时,芝加哥商品交易所开发了一种基于场景的模型,设计它的目的时计算系统风险和异常风险。
CME, meanwhile, has developed a scenario-based model designed to take into account systemic and idiosyncratic risk factors.
应用推荐