惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

月光博客
月光博客
IT之家
IT之家
Hugging Face - Blog
Hugging Face - Blog
J
Java Code Geeks
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
博客园 - 叶小钗
MyScale Blog
MyScale Blog
G
Google Developers Blog
Microsoft Azure Blog
Microsoft Azure Blog
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
大猫的无限游戏
大猫的无限游戏
博客园 - 三生石上(FineUI控件)
Google DeepMind News
Google DeepMind News
Engineering at Meta
Engineering at Meta
The Cloudflare Blog
Martin Fowler
Martin Fowler
酷 壳 – CoolShell
酷 壳 – CoolShell
N
Netflix TechBlog - Medium
MongoDB | Blog
MongoDB | Blog
I
InfoQ
WordPress大学
WordPress大学
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
H
Help Net Security

博客园 - navyliu

高成长公司诚聘Web平台开发工程师(Leader) 高成长公司诚聘.Net 互联网架构师 如何在SharePoint中Debug SharePoint开发小窍门,没事就IISReset Custom Field Type Deployment SharePoint的时间怎么和指定的时间不一样了? SharePoint中的参数nCLID Project Server 2007中项目组成员无法看到我的项目的问题解决 SharePoint 2007 SP1 Upgrade Error MOSS 2007中解决用户没有关联电子邮件的一种方法 不良的UI是对资源的极大浪费 WF中的自定义Activity(Custom Activities)(1) Local Communication Events Windows Workflow Foundation中的基本活动(Basic Activities) Workflow and the Outside world Rule Engine of Biztalk (Biztalk的规则引擎) OBA应用案例(1)--在Word 2007中填写表单(客户需求) Promoting in Biztalk Server 2006 对倪光南院士关于文档格式国际标准之争观点的不同看法
Application Platform Infrastructure Optimization Model
navyliu · 2008-03-01 · via 博客园 - navyliu

In some of the workflow scenarios, both BizTalk Server 2006 and WF satisfactorily meet the technical requirements. For these scenarios, making the right workflow-technology choice requires matching the solution to the needs of the specific organization. For the purposes of making recommendations that apply to your particular organization, we will use the Application Platform Infrastructure Optimization (APIO) model, as shown in Figure 3.

Figure 3. Application Platform Infrastructure Optimization (APIO) model

The APIO model is a technique for profiling an organization's maturity with respect to its application infrastructure, architecture, and development practices. The goal of this model is to give organizations a road map for optimizing their agility in providing IT solutions to meet the needs of the business.

The APIO model uses the following four profiles of an organization's maturity:

  • Basic—Organizations treat software as a cost. They have largely siloed applications with little integration or reuse. The applications that they do have might be on a variety of platforms. They do not have consistent standards for infrastructure or development techniques; they do not have a consistent architectural vision.
  • Standardized—Organizations still treat software as a cost, but they have taken steps to improve efficiencies. They have an architectural vision and try to consider opportunities for reuse. They have started to integrate some applications, but they are mostly point-to-point integrations.
  • Advanced—Organizations treat software as a business enabler. They have dedicated architects and a clear architectural vision. They have many services and achieve a high level of reuse. All core business processes are automated and monitored. They use a centralized, packaged integration platform.
  • Dynamic—Organizations treat software as a strategic asset. They have a very mature SOA in vision and implementation. They have clear processes for dynamically versioning and redeploying services. The can quickly adapt to business requirements changes, and can quickly integrate with new business partners.