|
===================================== 〔語彙分解〕的な部分一致の検索結果は以下の通りです。 ・ ー ： [ちょうおん] (n) long vowel mark (usually only used in katakana) ・ ワーク ： [わーく] 【名詞】 1. work 2. (n) work
Zachmanフレームワークは、ビュー･モデル (View model )の公式で高度に構造化された方法を提供し、事業体を定義する、事業体仕組 (EA )のための事業体仕組フレームワーク (Enterprise Architecture framework )である。 それは、6つのコミュニケーション（何を、どこで、なぜ、誰が、及びどのように）の質問と6つの変換の具体化 (Reification )に対応する行とが交差する2次元の分類マトリックスから成る。 Zachmanフレームワークは、それが記述する情報を収集し、管理し、使用するための特定な手法やプロセスに欠けることから、方法論ではない。 そのフレームワークは、1980年代にIBM にてその概念を最初に開発した、その創作者John Zachman を後に命名された。それは、それから数回改訂がされている。〔John Baschab, Jon Piot, Nicholas G. Carr (2007). ''The Executive's Guide to Information Technology''. p. 84.〕 Zachmanの『フレームワーク』は、成果物はだれのため（例えば、事業オーナーと構築者）とどんな特定課題（例えば、データ及び機能性）が取り扱われるかの両方の記事にかかる、仕組的生成物（別の言葉で、設計文書、仕様、及びモデル）のための分類体系 (Taxonomy )である。〔''A Comparison of the Top Four Enterprise Architecture Methodologies'' , Roger Sessions, Microsoft Developer Network Architecture Center,〕 == 全貌 == The term "Zachman Framework" has multiple meanings. It can refer to any of the frameworks proposed by John Zachman: * The initial framework, named ''A Framework for Information Systems Architecture'', by John Zachman published in an 1987 article in the IBM Systems journal. * The ''Zachman Framework for Enterprise Architecture'', an update of the 1987 original in the 1990s extended and renamed .〔The Open Group (1999–2006). "ADM and the Zachman Framework" in: ''TOGAF 8.1.1 Online''. Accessed 25 Jan 2009.〕 * One of the later versions of the Zachman Framework, offered by Zachman International as industry standard. In other sources the Zachman Framework is introduced as a framework, originated by and named after John Zachman, represented in numerous ways, see image. This framework is explained as, for example: * a framework to organize and analyze data,〔William H. Inmon, John A. Zachman, Jonathan G. Geiger (1997). ''Data Stores, Data Warehousing, and the Zachman Framework: Managing Enterprise Knowledge''. McGraw-Hill, 1997. ISBN 0070314292.〕 * a framework for enterprise architecture.〔Pete Sawyer, Barbara Paech, Patrick Heymans (2007). ''Requirements Engineering: Foundation for Software Quality''. page 191.〕 * a classification system, or classification scheme〔Kathleen B. Hass (2007). ''The Business Analyst as Strategist: Translating Business Strategies Into Valuable Solutions''. page 58.〕 * a matrix, often in a 6x6 matrix format * a two-dimensional model〔Harold F. Tipton, Micki Krause (2008). ''Information Security Management Handbook, Sixth Edition, Volume 2''. page 263.〕 or an analytic model. * a two-dimensional schema, used to organize the detailed representations of the enterprise.〔O'Rourke, Fishman, Selkow (2003). ''Enterprise Architecture Using the Zachman Framework''. page 9.〕 Beside the frameworks developed by John Zachman numerous extensions and or applications have been developed, which are also sometimes called Zachman Frameworks. The Zachman Framework summarizes a collection of perspectives involved in enterprise architecture. These perspectives are represented in a two-dimensional matrix that defines along the rows the type of stakeholders and with the columns the aspects of the architecture. The framework does not define a methodology for an architecture. Rather, the matrix is a template that must be filled in by the goals/rules, processes, material, roles, locations, and events specifically required by the organization. Further modeling by mapping between columns in the framework identifies gaps in the documented state of the organization.〔James McGovern et al. (2003). ''A Practical Guide to Enterprise Architecture''. p. 127-129.〕 The framework is a simple and logical structure for classifying and organizing the descriptive representations of an enterprise. It is significant to both the management of the enterprise, and the actors involved in the development of enterprise systems.〔Marc Lankhorst (2005). ''Enterprise Architecture at Work''. p. 24.〕 While there is not order of priority for the columns of the Framework, the top-down order of the rows is significant to the alignment of business concepts and the actual physical enterprise. The level of detail in the Framework is a function of each cell (and not the rows). When done by IT the lower level of focus is on information technology, however it can apply equally to physical material (ball valves, piping, transformers, fuse boxes for example) and the associated physical processes, roles, locations etc. related to those items. 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「Zachmanフレームワーク」の詳細全文を読む スポンサード リンク
|