Architecture language ArchiMate - Architecture perspective (Viewpoint) Classification Framework

Original link: http://www.cnblogs.com/zhoujg/archive/2010/02/19/1669126.html

This article has been moved to a newer version http://www.zhoujingen.cn/blog/4105.html

---------------------------------------

　　Implement and maintain a consistent architecture is a very complex task, because the architecture will involve a lot of people from different backgrounds, they use different markers. To deal with this complexity, researchers began to focus on how to clear all the different definitions related infrastructure described herein, this tell us about some of the conceptual framework and perspective views, after you understand these basic concepts, the next I will the basic perspective of ArchiMate introduced.

Conceptual model of architectural description

　　We all know that there are 4 + 1 view model, there are several other industry software architecture representation, such as an ISO standard RM-ODP , as well as Platform-Independent MDA in Model (PIM) and Platform-Specific Model (PSM ) from these models, we can infer that the software architecture, architecture description carried out through the perspective of (ViewPoint) and architecture is a conceptual view has been accepted by everyone. In the enterprise architecture - how to describe the enterprise architecture in perspective and view also of some description.

　　The figure below shows the conceptual model of architectural description, the figure lists some key concepts:

System (System): a component to meet specific functions
Architecture (Architecture): The basic organizational structure of the system, including components and relations between them and the environment, the architecture of the system will guide the design and evolution
Description architecture (Architecture Description): a description of the architecture of the workpiece. In TOGAF, the architecture is the main view of the workpiece depicted architectures.
Stakeholders (Stakeholder): assume a role in the system, or focus on certain aspects of the human system, such as users, developers, managers, and so on. Different stakeholders have different concerns, stakeholders can be individuals, groups or organizations.
Focus (Concern): local stakeholders interested in the system, is an important factor in determining whether the system is acceptable. Concerns may make the system function, development, all aspects of operations, performance, and security.
Angle of view (Viewpoint): an abstract model defines the performance of enterprise architecture, each model is aimed at a particular type of stakeholder of particular concern .
View (View): View of a specific performance , it is an object of the information delivery framework good way.

Architecture perspective Classification Framework

　　Architecture perspective classification framework is mainly carried out around perspective view and stakeholders. At the beginning talked about the complexity of the architecture described from different stakeholder needs, ArchiMate is a flexible architecture description language, it advocates architects and other stakeholders can define your own enterprise architecture view, it presents a view angle and view definition and classification framework. This framework is based on two dimensions: purpose ( Purpose ) and content ( Content ) .

　　The purpose and content of the FIGS exemplary dimensions and stakeholders on a graph represented as follows, next we will often see the blog this FIG:

Objective ( Purpose )

设计（Designing）: 支持架构师和设计师从概要设计到详细设计，UML就是常用的一种设计描述语言
决策（Deciding）: 帮助管理者作出决策
通知（Informing）: 为了获得认可、同意，与涉众沟通企业架构

内容（content）

详细（Details）: 考虑ArchiMate框架的一层或者一层的一个方面
一致（Coherence): 考虑ArchiMate框架的多层或多个方面，支持负责IT服务和业务流程的中层管理员
概括（Overview）: 考虑ArchiMate框架的多层和多个方面，可以支持CEOs和CIOs进行决策

分类示例

目的

	典型涉众	目的	示例
Designing	架构师、软件开发人员、业务流程设计人员	navigate, design, support design decisions, compare alternatives	UML、BPMN 、flowchart、ER
Deciding	高层管理者	决策	cross-reference table, landscape map, list, report
Informing	职工、客户	讲解、达成一致和认同	animation, cartoon, process illustration, chart

内容

	典型涉众	目的	示例
Details	软件工程师、流程负责人	设计、管理	UML class diagram, BPMN process diagram
Coherence	中层管理者	分析依赖性	views expressing relations like “use”, “realize”, and “assign”
Overview	企业架构师、高层管理者	变更管理	landscape map

开源信息系统开发平台之OpenExpressApp框架 1.1 春节飞虎版发布

欢迎转载，转载请注明：转载自周金根 [ http://zhoujg.cnblogs.com/ ]

转载于:https://www.cnblogs.com/zhoujg/archive/2010/02/19/1669126.html