You are on page 1of 120

2012 .

1
1 - 3

,
, 24
,
www.fostas.ru,
EZinder@fostas.org +7(495) 601-2049
-1-



?

?
?!


-
.

-2-

:
2005-2011 ..
(Forrester research, Gartner .),
- ,


- - ,

(
)
-
Enterprise Architecture 80%
,

-

-3-

,


(
).


.
-4-


1.

1. ()
2. .

3.
4. . (EAP)
5. (Change management)
,
.
6. . 3- .

1.
===============================
-5-

2.

7. .


8. /

-
.
9. 2000
2005 2009 .
10.

11. 15704
GERAM
==========================

-6-

3.

12. .
, - CIO
13. 3D- nD-
,
14.
(
).
15. .
16. TOGAF v. 8.1 v.9.

17.
.
.
-
(SOE SOA). .
.

-7-


, , , , , , ?
,

(
)
( , )
,
,


-8-

.

1960-: - . (
)
,
( !!),
, (
- ?!)
,
,
/
, ( ?!)
,

,
, ,
, , .
,
.
,
.
-9-

:

?


ISO 15704?

-10-


. Enterprise Architecture Framework ( 1987 1992/3
2001 2004 2011 )
. Enterprise Architecture Planning (1992/3)
GERAM, 3D-, ISO 15704 (1997 1999 2000 2010
2011 )
FEAF, FEA,
(1999 2001 )
TOGAF v.8 (2004) TOGAF v.9 (2009)

(CaseWise, ARIS Toolset, 1990s 2010)
SOE SOA ( 2000 2010 )

,
(2005 2011 )
Cloud computing
(,
Enterprise Architecture - Open
Group)
-11-

1-
1.

1. ()

1.1 ? 1.2 ? 1.3


?

1.4 ,

1.5
2. .

2.1 1987-1992
- IBM ( , , BSP, )

2.2 92
2.3 1992

3.

3.1 3.2

3.3
3.4
==========================
4. . (EAP)

4.1 EAP

4.2 EAP
4.3

4.4 , EAP
5. (Change management) ,
.

5.1. 5.4.
.
6.

(2002 2003 )


1.

-12-

1.
()
1.1 ?
1.2 (
)?
1.3
?
1.4
,

1.5
-13-

1.1 ?

-14-

( , ?)

-15-


-
-





-



NOKIA

.

-16-

(, )
-

(, )
(, , )
(, , )
??
? (, , , )
? (, ,
)
? (, )
?
??! /
??
?? ( ,
, , ,
.)
-17-

,

,
. ( ISO
15704:2000, ISO/IEC 15288:2002, PMBOK Guide .)

,
,
.
(
NOKIA.)

-18-

1.2 .

,

(ISO/IEC 15288:2002 )
( () ,
; () .
- ,
, )

,
, ,
.
:
, ,
-

,
,
,
.

..,
, !

-19-

-20-


(, ,
)
( ):
( ,
)
( ,
- )


( ,
,

-
, , , ,
,
.
-21-


:
- ,
,
- .
, ,
/

:
- / ,
-
,
.

:
:

-22-

/ 15288
, ISO 14258, ISO 15704

ISO/IEC 15288
. -

/ :
,
,
, ,


, ,
,
, .

ISO/IEC JTC 1, Information technology,


Subcommittee SC 7, Software and system engineering.

ISO 15704
.

. , (enterprise designers
), /

ISO 14258 ISO 15704 ISO/TC 184, Industrial automation


systems and integration, Subcommittee SC 5, Architecture,
communications, and integration frameworks

-23-

1.3

:
1)

,

,
,

.
2)

.
( , 2-08.
, ).
-24-



( :
construct build.)

Lessons from the oldest industry of the world -- "construction" -have always separated architecture from building. IT needs to
ensure this lesson is applied intelligently to its industry.

( -.)
,

. ,

.

, :

top down, architectural-driven approach yields the kind of consistency that results in a
portfolio of software assets that can be cross-leveraged. This saves money but perhaps
more importantly improves time to market and makes it easier for folks to come up with
innovative approaches to achieving business goals
When application development teams resist an architectural approach, the result is an overly
complex and misaligned IT organization that is poorly positioned to serve the needs of
the business.
(Tony Bishop, InfoWorld's The Real-Time Enterprise blogs author )

-25-

?
- ?


:
1) , ("Big
picture")

-26-

:
?
.
:
,
!

-

, ,
,

-27-

:
?
?
?
?

-28-


():
2)
3)

4)

5)
6)

7)



(, , ,
, , . ,
, "" ,
,
)



,






-29-

,
:
,
.


.
,
,

( )
,
( )
.
-30-

-31-

-32-

( )

-33-

-,

,
( )
( )

,
.

!
-34-

1.4
,


-
-

()
() ()
()

BPR

-35-



. http://dic.academic.ru/dic.nsf/bse/132746/
-
,

. http://dic.academic.ru/dic.nsf/bse/132725/
:
-
-


-
: ,


(
)!
..
, .
, .. ,

..
-36-

:
-

,
- ,
-
,
..
-37-


-
(Enterprise),

,
,

(Enterprise Systems), , ,
-
(Enterprise
Architecture)

,
,
, ,
- ,
-
,
-
-38-

,

, ,

,
( : ,
),
,
( ,
, ,
,
, .)
,
,
, ,

-39-


(

):


?
?

?

?

-40-

1.5

,

( )

[
]
(

)



( )
-41-

(MBA/MBI, Kiiv, 2009):


MBI


.

,

-42-

(MBA/MBI, Kiiv, 2009):




,
,
,

,


.



,
.
-43-

(INCOSE)


(DCD)



(MSV)

MSV
DCD


(Graphic courtesy of BAE Systems and INCOSE )

-44-



( , ,
,)
(
, ,
-, ,
)

( ,
, , )
(
,
, , )
- (
,
, -,
-, -, )
(-
, ,
, )
-45-

CIMOSA Association, Kurt Kosanke


Deliverable Standardisation Final Report D 5.3.2. Date May 16, 2003
(mfg - abbreviation for manufacturing)

-46-

:
. ?
?

/
?

-47-

2. .

2.1 (John A.
Zachman) 1987-1992

- IBM ( , ,
BSP, )
- ,

-
2.2 92
2.3
1992
-48-

2.1
1987-1992

-49-


TQM,

Marketing management

Business & IT alignment"

CMM

CPI

89 95

70 89
55 75
IBM BSP


(,
)

80

92

EAP .

c
.
(3*6)


.
(6*6)

-50-

N
: IBM BSP
(Dewey Walker),

1960-
. , ,
"Business
Systems Planning BSP, .

BSP
. . , BSP,
. , EAP


:
( :

-, , .)

:
1 14 .

-51-

. . , ., 1992 :
The architecture process begins with an understanding of the enterprise and
the data that constitute its information infrastructure. To be most useful,
information systems must be derived from this base of knowledge about the
enterprise. Even if we could document the business strategy a
fundamental remained: how to get from those [I.S.] strategy to
implementation Over the years, the strategy matrices and the
implementation have remained separated by cavernous, conceptual black
hole


,
. ,
,


,
-
:
,
(.: BSP!)
,

-52-

1) ,
BSP,
. EAP,
.
2) . -
XXI .)
3) ,
BSP,

.
BSP



, ,

(,
).
-53-

BSP - "Business Systems Planning,


IBM, 70-e 80-e

BSP: " ,
,
" (
! . ..).
BSP ,

BSP :

,
.
:
, .

.
:
, "" (, ,
.)
.
(. . " ". "
", 1984)

-54-

BSP:

,
,
;
,
,
,
;

,
;

,
;


,
;
(),
,
.
-55-

BSP:

-
- BSP
- , BSP
- , ,
- ()
- BSP
-
-
-
- :

( 1
.)
-56-

2.2 92
. :
Sowa J. F., Zachman J. A. Extending and Formalizing
the Framework for Information System Architecture
// IBM S. J. 1992. V. 31. 3.
ISA
Information System (IS) Architecture
,
()
(EA - ENTERPRISE ARCHITECTURE)

-57-

?
. -
90-


XXI .
(
, . 1992
.
,
)
-58-

1970-198

1987-1992
1992-1999
2000-2004

2005-2011

-59-

. :

- ,
ISA (1992 .)


,
,


,

, ,

.
-60-

()

()


!


, - !

-61-

. :

:
, ,
( ) ,
,
.
,

.
,
,
" ".
,

.
, ,

, ,
.
-62-

ENTERPRISE ARCHITECTURE - A FRAMEWORK


DATA

What

FUNCTION

How

NETWORK

Where

PEOPLE

Who

TIME

When

MOTIVATION

Why

SCOPE
(CONTEXTUAL)

List of Things Important


to the Business

List of Processes the


Business Performs

List of Locations in which


the Business Operates

Planner

ENTITY = Class of
Business Thing

Function = Class of
Business Process

Node = Major Business


Location

People = Major Organizations

Time = Major Business Event

Ends/Means=Major Bus. Goal/


Critical Success Factor

e.g. Semantic Model

e.g. Business Process Model

e.g. Logistics Network

e.g. Work Flow Model

e.g. Master Schedule

e.g. Business Plan

ENTERPRISE
MODEL
(CONCEPTUAL)

Owner

List of Organizations
Important to the Business

List of Events Significant


to the Business

TM

List of Business Goals/Strat

(CON

(CON

Ent = Business Entity


Reln = Business Relationship

Proc. = Business Process


I/O = Business Resources

Node = Business Location


Link = Business Linkage

People = Organization Unit


Work = Work Product

e.g. Logical Data Model

e.g. "Application Architecture"

e.g. "Distributed System


Architecture"

e.g. Human Interface


Architecture

SYSTEM
MODEL
(LOGICAL)

Time = Business Event


Cycle = Business Cycle

e.g. Processing Structure

End = Business Objective


Means = Business Strategy
e.g., Business Rule Model

Ent = Data Entity


Reln = Data Relationship

Proc .= Application Function


I/O = User Views

Node = I/S Function


(Processor, Storage, etc)
Link = Line Characteristics

People = Role
Work = Deliverable

Time = System Event


Cycle = Processing Cycle

End = Structural Assertion


Means =Action Assertion

TECHNOLOGY
MODEL
(PHYSICAL)

e.g. Physical Data Model

e.g. "System Design"

e.g. "System Architecture"

e.g. Presentation Architecture

e.g. Control Structure

e.g. Rule Design

Builder

Ent = Segment/Table/etc.
Reln = Pointer/Key/etc.

Designer

DETAILED
REPRESENTATIONS
(OUT-OFCONTEXT)
SubContractor
FUNCTIONING
ENTERPRISE

EN

TEC
CON

e.g. Data Definition

Proc.= Computer Function


I/O = Screen/Device Formats

Node = Hardware/System
Software
Link = Line Specifications

e.g. "Program"

e.g. "Network Architecture"

People = User
Work = Screen Format
e.g. Security Architecture

Time = Execute
Cycle = Component Cycle
e.g. Timing Definition

End = Condition
Means = Action
e.g. Rule Specification

Ent = Field
Reln = Address

Proc.= Language Stmt


I/O = Control Block

Node = Addresses
Link = Protocols

e.g. DATA

e.g. FUNCTION

e.g. NETWORK

Zachman Institute for Framework Advancement - (810) 231-0531

Time = Interrupt
Cycle = Machine Cycle

People = Identity
Work = Job

e.g. ORGANIZATION

e.g. SCHEDULE

End = Sub-condition
Means = Step
e.g. STRATEGY

FU
E

-63Copyright - John A. Zachman, Zachman


Intern


--
:
A) -- /;
B) -- /;
C) , -- ;
D) -- , ;
E) -- ;
F) -- ,
.
-- :
1) -- -,
2) -- ,
3) -- () ,
4) -- () ,
5) -- , -
,
6) --
, .
-64-

2:
. 2008 :
http://www.youtube.com/watch?v=b5ncVbj4OPM
, :
-
- (
,
).

3- .

!
,
.
,
.

-65-

2.3
1992



.
:
,
( ),


-66-

. 1992
--:
Basic Model = Entities and Relationships

Relationship
Entity

Entity

(

.. ,
.)
-67-

1.

-68-

2. ,

:
, , , ,
( , ..)

.

(. . 5)
, 2 :
,
, ,
ER (-).
-69-

5.
A, B, C

-
:

A
()

()

()

(Entity)

(Relationship)

-70-

Basic Model = Entities and Relationships


Entity

Relationship

Entity

3.

() ,
,

( ?!)


(.. )
.
..

( . EFFECT).
,
. ,
:

.

( )?!

-71-

?!

-72-

4. - ,

: ,
, ,
.

:
,

.

:
,

.
: ?
,
?
-73-

6.


( )

( )

( )

-74-

5.
-
A2.

A3.

-
B2.

B3.
-75-

-2

-76-

-3

-77-

-78-

6.




( )

-79-

- 4

-
-
-
-

- -
-
-
-

-80-

- 5

:
-
-
/
(
/
)

-81-


- 6


:
1)

. 2)

.
-82-


--
1

1.1

2.1

1.2

2.2

1.1.1

2.1.1

1.1.1.1

2.1.1.1

1.1.1.2
1.1.1.1.1

2.1.1.2
2.1.1.1.1

/
( )
-83-



50%
/

95%


,


2

-84-

:
)

(
!...)

)
!

-85-

-86-

3.

3.1
3.2
3.3
3.3

-87-

3.1

BSP :
(70- )

,
.
,
1) ( )

, ,
2) :
!
60- 70-
. ,

-88-



. :
"

, ,
".

-89-

BSP

. : "
" "
.

, .
" ",
,
. "
" " ",
,
.
,

."

,

( -
, ,
).
-90-

()



.
,


.
:
- ( - - . ..) .

,
.

. -
,
.
-91-


BSP:
,
,
.

,

.


."
-92-

,
,
() ,
,
, ..
,
,

-93-

Views ,
BSP
-

.
!

(-):
, ,
,
, , .

: ,

,

:
,
, ,
, ,

-94-

,
.
( - )

t > t1

TRIGGER
ALARM

read
string

on event
t > t1 . .

1. ------2. -------

1. ------2. -------

INDEX

CREATE
TABLE

BEGIN
BLOCK

C:>PING

Wait,
please

-95-



:

.

1992 .

-
(to be),
,

.
-96-

-92

-97-


1992


,
,

-98-

3.2
,
!!

:
,
,

..
(
)
?!

-99-



( . )

,


3, 4, 5

(?!...)

: ,

?

-100-

-2
:
(, ) ,
,
,

(
, )

(
-,
-
)
,
. ,
(
)
-101-

- 1
, ()
:
-- (Entity)

-- (Relationship)



()

Business
Subject Area

Groups

Business
Entity

Data
Subject Area

Groups

Data
Entity

Data base /
File

Groups

Data
Records
-102-

- 2
B, ()
:

(
)

Business
Effect
Business
Entity
process

Data
Entity

Effect

Data
Records

Effect

Function
process

( )

-
( )


Business
function

System
process

IS
process

Information
System

Stored
procedure

Application
process

Application
System
-103-

--
, ,
-
( , , )

-104-


:
,

?!


?!
NOKIA?
Linux
?!
-105-

3.3
( )

.
?!
:

( , .
3- )
(
)
- 2,3,4
ER (
)

,
,


,

-106-


. :

//


========================
, .
:

,


, ,
,
,

,

, ,

,

,

-107-


ISO/IEC 15288
ISO/IEC 12207


/ 15288 12207

,


- ,
( ),
,

- ,

-

-108-




( !)

( ,

)



(,
, ,
)


()

-109-

1 3 1-

?
-110-

BPR

BPI, BPT
Change
management

-
21

(
2005 .)

96

89 95
93 2000

DoDAF TAFIM

. (6*6)

CIMOSA ISO14258

FEAF,
FEA
3D-
GERAM

ISO15704 TOGAF

-111-

3- . .
:
-
2001
- , 3-

- 3-
- . .
,
3-
-112-

Inventory

Process

Distribution

Responsibility

Timing

Motivation

ENTERPRISE ARCHITECTURE - A FRAMEWORK


DATA
SCOPE
(CONTEXTUAL)

What

FUNCTION

How

NETWORK

Where

PEOPLE

Who

TIME

When

MOTIVATION

Why

List of Things Important


to the Business

List of Processes the


Business Performs

List of Locations in which


the Business Operates

ENTITY = Class of
Business Thing

Function = Class of
Business Process

Node = Major Business


Location

People = Major Organizations

Time = Major Business Event

Ends/Means=Major Bus. Goal/


Critical Success Factor

e.g. Semantic Model

e.g. Business Process Model

e.g. Logistics Network

e.g. Work Flow Model

e.g. Master Schedule

e.g. Business Plan

List of Organizations
Important to the Business

List of Events Significant


to the Business

TM

List of Business Goals/Strat

(CON

Identification
Planner
ENTERPRISE
MODEL
(CONCEPTUAL)

EN

(CON

Definition
Owner

Ent = Business Entity


Reln = Business Relationship

Proc. = Business Process


I/O = Business Resources

Node = Business Location


Link = Business Linkage

People = Organization Unit


Work = Work Product

e.g. Logical Data Model

e.g. "Application Architecture"

e.g. "Distributed System


Architecture"

e.g. Human Interface


Architecture

SYSTEM
MODEL
(LOGICAL)

Time = Business Event


Cycle = Business Cycle

e.g. Processing Structure

End = Business Objective


Means = Business Strategy
e.g., Business Rule Model

Representation
Designer
TECHNOLOGY
MODEL
(PHYSICAL)

Ent = Data Entity


Reln = Data Relationship

Proc .= Application Function


I/O = User Views

Node = I/S Function


(Processor, Storage, etc)
Link = Line Characteristics

People = Role
Work = Deliverable

Time = System Event


Cycle = Processing Cycle

End = Structural Assertion


Means =Action Assertion

e.g. Physical Data Model

e.g. "System Design"

e.g. "System Architecture"

e.g. Presentation Architecture

e.g. Control Structure

e.g. Rule Design

TEC
CON

Specification
Builder
DETAILED
REPRESENTATIONS
(OUT-OFConfiguration
CONTEXT)
SubContractor
FUNCTIONING

Instantiations
ENTERPRISE

Ent = Segment/Table/etc.
Reln = Pointer/Key/etc.

e.g. Data Definition

Proc.= Computer Function


I/O = Screen/Device Formats

Node = Hardware/System
Software
Link = Line Specifications

e.g. "Program"

e.g. "Network Architecture"

People = User
Work = Screen Format
e.g. Security Architecture

Time = Execute
Cycle = Component Cycle
e.g. Timing Definition

End = Condition
Means = Action
e.g. Rule Specification

Ent = Field
Reln = Address

Proc.= Language Stmt


I/O = Control Block

Node = Addresses
Link = Protocols

e.g. DATA

e.g. FUNCTION

e.g. NETWORK

People = Identity
Work = Job

e.g. ORGANIZATION

Time = Interrupt
Cycle = Machine Cycle
e.g. SCHEDULE

End = Sub-condition
Means = Step
e.g. STRATEGY

-113-

FU
E


. .
( 3- ):

John Zachman's Concise Definition of


The Zachman Framework
by John A. Zachman
http://www.zachman.com/about-the-zachman-framework

The Zachman Framework Evolution


by John P. Zachman
http://www.zachman.com/ea-articles-reference/54-the-zachman-frameworkevolution
-114-

-115-


Architecture Is Architecture Is Architecture
by John A. Zachman

http://www.zachman.com/ea-articles-reference/52-architecture-is-architecture-is-architecture-by-john-a-zachman

Architecture is the set of descriptive


representations that are required in order to
create an object.
There is a universal set of descriptive
representations for describing any or all
industrial products.
-116-

Abstractions :
Bills of Material - What the object is made of.
Functional Specs - How the object works.
Drawings - Where the components exist relative
to one another.
Operating Instructions - Who is responsible for
operation.
Timing Diagrams - When do things occur.
Design Objectives - Why does it work the way it
does.
-117-

out of the total set of relevant descriptive characteristics of the object, we


abstract one of them at a time for producing a formal, explicit, description

-118-

Perspectives as depicted in the Zachman Framework

-119-

___________

?
EZinder@fostas.org

-120-