企业、系统和应用程序架构(最佳实践?) [英] Enterprise, Systems and Application Architecture (Best Practice?)

问题描述

我目前的任务是为软件开发创建一个文档化的、一致的架构指南.我们有很多聪明人都在做正确的事情，但只是不一致和可重复.

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.

我们使用 Microsoft 的应用程序架构指南 2.0 作为起点.因此，提出一个应用程序架构是相当(我不会说容易的)直截了当的.可能是因为我有几年的开发经验，所以我对这个领域有很好的理解，而且还有很多例子和指导.

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.

根据我对这一切的(有限的 - 清楚的)理解，系统架构是一个或多个应用程序架构的抽象，描述了它们如何协同工作以形成一个系统.此外，企业架构是一种进一步的抽象，展示了您的系统如何融入组织企业，以及它如何与业务流程、IT 战略交互以及它如何集成到企业中的其他系统中.

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.

• 我完全错了吗?
• 是否有任何标准(以及在哪里可以找到)?
• 是否应该有标准，或者一个好的"系统架构只是采用任何格式的任何文档，可以清晰易懂且对读者有用?
• 经验丰富的建筑师会如何看待这种方法?

我不想简单地列出一组可能有用的 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 企业架构框架——虽然自称为框架，但实际上更准确地定义为分类法
• 开放组架构框架 (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屋！