企业，系统和应用程序体系结构（最佳实践？） [英] Enterprise, Systems and Application Architecture (Best Practise?)

问题描述

我目前正在与创建软件开发文档，一致的架构指导任务。我们有很多聪明的人做正确的事情，只是没有一致和可重复的。

I am currently tasked with creating a documented, consistent Architecture guide for software development. We have a lot of smart people doing the right things, but just not consistently and repeatably.

我们正在使用微软的应用架构指南2.0作为起点。因此想出一个应用架构是相当（我不会说的容易）直线前进。可能是因为我有几年经验作为一个开发人员，所以我有这个境界的pretty很好的了解，也有实例和悉心指导。

We are using Microsoft’s Application Architecture Guide 2.0 as a starting point. Hence coming up with an Application Architecture is fairly (I won't say easy) straight forward. Possibly because I have a couple of years experience as a developer so I have a pretty good understanding of this realm and there are also loads of examples and guidance.

由于我们的组织有两个形成1个或多个系统，我们再安装在客户端应用程序......我们认为这将是有意义的创建一个系统架构和企业架构也是如此。而这正是问题的开始。

Since our organisation has a couple of applications that form 1 or more systems which we then install "at" clients... we thought it would make sense to create a System Architecture and an Enterprise Architecture as well. And this is where the problems start.

有是那里没有统一的指导意见。如果你搜索系统架构示例，那你回来的东西是如此不同，我想知道是否有一个标准的方式来做到这一点。

There is no consistent guidance out there. If you search for "System Architecture Examples", the stuff that you get back is so different that I am wondering if there is a "Standard" way to do this.

从我的（有限 - 清楚地）这一切理解，系统架构的1个或多个应用程序体系结构描述他们是如何工作在一起，形成一个系统的抽象。此外，企业架构是显示系统（S）如何适应一个组织的企业，以及它如何与业务流程进行交互，IT战略以及它如何Integrats到企业中的其他系统的进一步抽象。

From my (Limited - clearly) understanding of it all, the System Architecture is an abstraction of 1 or more application architectures depicting how they work together to form a system. Furthermore, an Enterprise Architecture is a further abstraction showing how your system(s) fit into a organisations Enterprise and how it interacts with the Business processes, IT Strategy and how it Integrats into other systems in the enterprise.

• 请我有完全错误的？


• 是否有任何的标准在那里（我在哪里可以找到他们）？


• 如果有标准，或者说一个好的系统架构仅仅是在这显然和容易理解和读者有用吗？
任何格式的任何文件

• 你会经验丰富的建筑师认为这种做法虽则？

• Do I have it completely wrong?
• Are there any standards out there (and where can I find them)?
• Should there be standards, or would a "good" System Architecture simply be any document in any format which is clearly and easily understandable and useful to its readers?
• What would the seasoned Architects think of that approach though?

我不想简单地列出了一组SOA相关的模式，可能是有用的...我想使它成为一个小更集中到我们做什么，这是一个面向服务的构建金融解决方案架构。

I don't want to simply list a set of SOA related patterns that may be useful... I'd like to make it a little more focused to what we do, which is the build financial solutions on a Service Orientated Architecture.

更新：了解 TOGAF（9）什么。有没有人有经验，它在所有的，是值得的试图了解它的细节的工作。

Update: What about TOGAF(9). Does anyone have experience with it at all and is it worth the effort of trying to understand it in detail.

推荐答案

我提交问题的前两天，而是通过不断的研究和阅读的 littlegeek 的效应初探，我想我已经发现了一个有趣的白皮书，我发现非常丰富和有趣。

I submitted the question a couple of days ago, but by continued research and after reading littlegeek's reponse, I think I have found an interesting white paper that I found very informative and interesting.

阅读：世界前四名企业架构方法论的比较
由：罗杰会话

Read: A Comparison of the Top Four Enterprise-Architecture Methodologies By: Roger Sessions

一个片段...

- - - - - - - - - - - 8示 - - - - - - - - - - - -

-- - - - - - - - - - - 8< - - - - - - - - - - - -

许多企业架构方法来来去在过去的20个年头。此时，也许90％的字段的使用这四个方法之一：

Many enterprise-architectural methodologies have come and gone in the last 20 years. At this point, perhaps 90 percent of the field use one of these four methodologies:

• Zachman框架的企业架构，虽然自称为框架，实际上是更准确地定义为一种分类法


• 由The Open Group架构框架（TOGAF） - 虽然称为一个框架，实际上是更准确地定义为一个过程


• 联邦企业架构 - 可以被视为要么是实施企业架构或创建企业架构的方法论禁止性


• Gartner的方法论，可以形容为一个企业的建筑实践

本白皮书讨论了这四种方法的企业架构。它这样做是面临着一些非常非虚构业务问题的虚构公司的范围内。这些问题包括：

This white paper discusses these four approaches to enterprise architecture. It does so within the context of a fictional company that is facing some very nonfictional operations problems. These problems include:

• 已经变得无法管理复杂，成本越来越高，以保持IT系统。

被阻碍组织对当前的反应能力
• IT系统，以及未来市场情况及时和具有成本效益的方式。

这是一贯
• 关键任务信息外的日期和/或只是简单的错误。


• 组织的业务和技术双方之间互不信任的文化。

- - - - - - - - - - - 8示 - - - - - - - - - - - -

-- - - - - - - - - - - 8< - - - - - - - - - - - -

白皮书帮助我在几个方面。

The White Paper helped me in several ways.

1. 这让我对建筑一个很好的介绍和历史（企业架构专）


2. 这给我介绍一下笔者建议可在4领先的企业架构。


3. 然后继续他们在，我可以涉及到很好的例子逻辑和简单的方式进行比较。

我不能说我所有的问题都得到了解答，我现在准备死:-)，但要更加明确，因此我认为别人那里也可能会发现这很有用。

I cannot say that all my questions have been answered and I am now ready to die :-), but much has become clearer and thus I thought that someone else out there may also find this useful.

我依然会珍惜你可能对这个问题的其他意见，建议和问题。

I would still value any additional comments, suggestions and questions you may have on this subject.

这篇关于企业，系统和应用程序体系结构（最佳实践？）的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！