Transformation approach Zachman

Good time to read, dear members habrahabr.ru

In a 2001 article Leonid Chernyak - Systems Architecture by Zahman
http://www.osp.ru/os/2001/12/180711/
is a quote:

For more than forty years, the use of technology to solve corporate problems has become something of a search for the Holy Grail.

and the architecture of Zachman is now considered an interesting search direction https://msdn.microsoft.com/ru-ru/library/ee914379.aspx

An analysis of the Zachman model for 2013 can be found at http://ailev.livejournal.com/951732.html

other approaches are published in http://www.intuit.ru/studies/courses/995/152/lecture/4236?page=2

I tried to perform the first attempt of analysis in the article http://habrahabr.ru/post/176935/ based on the terminology of the book Danilin A., Slyusarenko A. Architecture and strategy. “Yin” and “Yang” of information technology of an enterprise: Internet-Inform. Technology, 2005
')
The 6 by 6 Zachman scheme is deservedly respected, but from the point of view of tunnel modeling, it is advisable to convert it into an expandable system.

This topic offers a coordinate system for modeling an enterprise.

Time measurement is spread throughout the model from the standpoint of tunnel modeling http://habrahabr.ru/post/259291/

The upper part assumes the area of ​​the future or abstract, at the bottom - the past or concrete.

The perception of cyclical time is also recommended: product life cycle, PDCA quality management cycle, direct execution time of the Gant project, time axis for describing historical events.

Below is a diagram of the Ontology of the Zakhman enterprise with reference to the symmetric tunnel model.

It is assumed that time participates in all manifestations of the modeled area, although I will not undertake to completely deny the possibility of taking time into a separate vertical, as Zachman suggests :)

		ways	purpose	activity	equipment	staff
one	future
2	logics	negation	market	study	voting	accounts
3	maths	function	yield	capital	information	delivery
four	philosophy	Attention	Spread	compensation	materials	criticism
five	culture	the science	products	buyers	office	ethics
6	politics	training	sales	protection	production	transport
7	management	scenario	control	planning	directions	frames
eight	marketing	competition	trade	satisfaction	advertising	recruiting
9	competition	correction	finance	repairs	accessories	service
ten	technology	competence	reliability	quality	network	design
ten	a responsibility	regulations	leadership	regulations	regulation	directorate
9	synergy	marketing	application campaign	bargaining	technology	environmental protection
eight	economic	sales	purchases	contracts	modes	insurance
7	social	reporting	distribution	control	dispatch control	social payments
6	processes	taxes	consumption	accounting	exploitation	occupational Safety and Health
five	systems	income	expenses	balance	work	staff list
four	structures	receipts	write-off	orders	technical places	workplaces
3	items	finance	warehouses	need	equipment	employees
2	messages	property	materials	plans	faults	report card
one	past
		ways	purpose	activity	equipment	staff

Please evaluate the applicability of this coordinate system.

Upd. 05/25/2016 Analysis Sequence Options - Quick Analysis



Upd. 11/13/2016 - added notation for resource types



Upd. 07/21/2017 - added aspects of the enterprise in terms of levels of complexity and types of resources

Literature:

Leonid Chernyak: Systems Architecture by Zahman

A.I. Levenchuk: Zachman lived, Zachman alive, Zachman will live - version 3.0 of his approach, organizational ontology (tm)

Danilin A., Slyusarenko A. Architecture and strategy. “Yin” and “Yang” of information technology of an enterprise: Internet-Inform. Technology, 2005
Tunnel modeling - version 1.0