Transcript Arhitektūru veidi - Riga Technical University

Arhitektūru orientēta prasību
inženierija
Enterprise Architectures
Uzņemumu arhitektūru definīcijas
Arhitektūras
Ievads no CapGemini
Populārākās arhitektūras
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Extended Enterprise Architecture Framework E2AF
Enterprise Architecture Planning EAP
Federal Enterprise Architecture Framework FEAF
Treasury Enterprise Architecture Framework TEAF
The Open Group Architecture Framework TOGAF
Zachman Framework
Integrated Architecture Framework (IAF)
Joint Technical Architecture (JTA)
C4ISR and DoDAF
Department of Defence Technical Reference Model (DoD TRM)
Technical Architecture Framework for Information Mangement (TAFIM)
Computer Integrated Manufacturing Open System Architecture (CIMOSA)
Purdule Enterprise Reference Architecture (PERA)
Standards and Applications for eGovernment Applications (SAGA)
How to Survive in the Jungle of Enterprise Architecture Frameworks: Creating or Choosing an Enterprise Architecture Framework
by Jaap Schekkerman
http://www.trafford.com/robots/03-1984.html
http://www.zifa.com/
VA Enterprise
Architecture
DATA
What
FUNCTION
How
NETWORK
Where
PEOPLE
Who
TIME
When
MOTIVATION
Why
SCOPE
(CONTEXTUAL)
Things Im portant
to the Business
Processes
Performed
Business
locations
Important
Organiz ations
Ev ents Signific ant
to the Business
Business Goals
and Strategy
Planner
Entity = Class of
Business Thing
Function = Class of
Business Process
Node = Major
Business Locations
People = Major
Organiz ations
Time = Major
Business Event
Ends/Means =
Major Business Goals
ENTERPRISE
MODEL
(CONCEPTUAL)
Semantic Model
Business Process
Model
Business Logistic s
System
Work Flow Model
Master Schedule
Business Plan
Owner
Ent = Business Entity
Proc = Business Process Node = Business Location People = Organization Unit Time = Business Event
Rel = Business Relationship I/O = Business Resources Link = Business Linkage
Work = Work Product
Cycle = Business Cycle
End = Business Objectiv e
Means = Business Strategy
SYSTEM MODEL
(LOGICAL)
Logical Data
Model
Application
Architecture
Processing
Structure
Business Rule
Model
Designer
Ent = Data Entity
Rel = Data Relationship
Proc = Application Function Node = IS Function
People = Role
I/O = User Views
Link = Line Characteristic s Work = Deliv erable
Time = System Event
Cycle = Processing Cycle
End = Structural Assertion
Means = Action Assertion
TECHNOLOGY
MODEL
(PHYSICAL)
Physical Data
Model
System
Design
Control
Structure
Rule
Design
Builder
Ent = Segment/Table
Rel = Pointer/Key
Proc = Computer Function Node = Hardware/Softw are People = User
I/O = Data Elements /Sets Link = Line Specifications Work = Screen Format
Time = Ex ecute
End = Condition
Cycle = Component Cycle Means = Action
Program
Security
Architecture
Timing
Definition
Rule
Design
Data
DETAILED
REPRESENTATIONS Definition
(OUT-OF-CONTEXT)
Distributed System
Architecture
Technology
Architecture
Netw ork
Architecture
Human Interface
Architecture
Presentation
Architecture
Sub-Contractor
Ent = Field
Rel = Address
Proc = Language Statement Node = Addresses
I/O = Control Block
Link = Protocols
People = Identity
Work = Job
Time = Interrupt
Cycle = Machine Cycle
End = Sub-Condition
Means = Step
FUNCTIONING
ENTERPRISE
Data
Function
Netw ork
Organiz ation
Schedule
Strategy
Ent =
Rel =
Proc =
I/O =
Node =
Link =
People =
Work =
Time =
Cycle =
End =
Means =
DATA
What
FUNCTION
How
NETWORK
Where
PEOPLE
Who
TIME
When
www.va.gov/oirm/architecture/EA/theory/tutorial.ppt
MOTIVATION
Why
DEMO
Based on work by
John A. Zachman
SCOPE
(CONTEXTUAL)
Planner
ENTERPRISE
MODEL
(CONCEPTUAL)
Owner
SYSTEM MODEL
(LOGICAL)
Designer
TECHNOLOGY
MODEL
(PHYSICAL)
Builder
DETAILED
REPRESENTATIONS
(OUT-OF-CONTEXT)
Sub-Contractor
FUNCTIONING
ENTERPRISE
Tagad zem TELELOGIC karoga
Populārāko arhitektūru pārskats
Atkal Cap Gemini
Uzņēmumu arhitektūru rīki
• USA-Enterprise Architecture Management
System
• Popkin Systems Architect
• Metis – Computas
• Ptech Enterprise Framework
• Provision
Biznesa procesu vieta uzņēmumu
arhitektūras
Neatņemama
sastāvdaļa
VA Enterprise
Architecture
DATA
What
FUNCTION
How
NETWORK
Where
PEOPLE
Who
TIME
When
MOTIVATION
Why
SCOPE
(CONTEXTUAL)
Things Im portant
to the Business
Processes
Performed
Business
locations
Important
Organiz ations
Ev ents Signific ant
to the Business
Business Goals
and Strategy
Planner
Entity = Class of
Business Thing
Function = Class of
Business Process
Node = Major
Business Locations
People = Major
Organiz ations
Time = Major
Business Event
Ends/Means =
Major Business Goals
ENTERPRISE
MODEL
(CONCEPTUAL)
Semantic Model
Business Process
Model
Business Logistic s
System
Work Flow Model
Master Schedule
Business Plan
Owner
Ent = Business Entity
Proc = Business Process Node = Business Location People = Organization Unit Time = Business Event
Rel = Business Relationship I/O = Business Resources Link = Business Linkage
Work = Work Product
Cycle = Business Cycle
End = Business Objectiv e
Means = Business Strategy
SYSTEM MODEL
(LOGICAL)
Logical Data
Model
Application
Architecture
Processing
Structure
Business Rule
Model
Designer
Ent = Data Entity
Rel = Data Relationship
Proc = Application Function Node = IS Function
People = Role
I/O = User Views
Link = Line Characteristic s Work = Deliv erable
Time = System Event
Cycle = Processing Cycle
End = Structural Assertion
Means = Action Assertion
TECHNOLOGY
MODEL
(PHYSICAL)
Physical Data
Model
System
Design
Control
Structure
Rule
Design
Builder
Ent = Segment/Table
Rel = Pointer/Key
Proc = Computer Function Node = Hardware/Softw are People = User
I/O = Data Elements /Sets Link = Line Specifications Work = Screen Format
Time = Ex ecute
End = Condition
Cycle = Component Cycle Means = Action
Program
Security
Architecture
Timing
Definition
Rule
Design
Data
DETAILED
REPRESENTATIONS Definition
(OUT-OF-CONTEXT)
Distributed System
Architecture
Technology
Architecture
Netw ork
Architecture
Human Interface
Architecture
Presentation
Architecture
Sub-Contractor
Ent = Field
Rel = Address
Proc = Language Statement Node = Addresses
I/O = Control Block
Link = Protocols
People = Identity
Work = Job
Time = Interrupt
Cycle = Machine Cycle
End = Sub-Condition
Means = Step
FUNCTIONING
ENTERPRISE
Data
Function
Netw ork
Organiz ation
Schedule
Strategy
Ent =
Rel =
Proc =
I/O =
Node =
Link =
People =
Work =
Time =
Cycle =
End =
Means =
DATA
What
FUNCTION
How
NETWORK
Where
PEOPLE
Who
TIME
When
MOTIVATION
Why
Based on work by
John A. Zachman
SCOPE
(CONTEXTUAL)
Planner
ENTERPRISE
MODEL
(CONCEPTUAL)
Owner
SYSTEM MODEL
(LOGICAL)
Designer
TECHNOLOGY
MODEL
(PHYSICAL)
Builder
DETAILED
REPRESENTATIONS
(OUT-OF-CONTEXT)
Sub-Contractor
FUNCTIONING
ENTERPRISE
MIT Enterprise Architecture Deliverables
Timeless/Evolutionary
Enterprise Data Model
Current State
Road Map
System Context
Diagram
Context
System Logical and
Physical Architecture
Diagrams
Services Matrix
Business Process Flows
and Scenarios
Key Systems
Inventory
Architecture Migration
Maps
List of Initiatives
Architectural Review
Process
IntegrationInventory
Systems on a Page
Prioritization Model
Architectural
Principles
Future State
TechnologyStandards
IT Governance Process
Business Strategy
Future State Logical Architecture Vision
Future State Services
Matrix
Short Term Roadmap
Long Term Roadmap
Business processes and SOA
From an implementation of loosely coupled systems
come applications that map much more closely to the
business processes
These applications increase the enterprises'
competitiveness because they are easier to modify to
satisfy changing business conditions
Practical Guide to Enterprise Architecture by James McGovern, Scott W. Ambler, Michael E. Stevens, James Linn, Vikas Sharan, Elias K. Jo
The SOA contract specifies the
following:
Functionality provided
Required inputs and expected outputs
Preconditions
Post-conditions
Error handling
Quality of service guarantees and SLAs (optional)
“Producing services that represent a
significant business process is the
real lasting value of a SOA”
Practical Guide to Enterprise Architecture by James McGovern, Scott W. Ambler, Michael E. Stevens, James Linn, Vikas Sharan, Elias K. Jo
The SOA contract
Practical Guide to Enterprise Architecture by James McGovern, Scott W. Ambler, Michael E. Stevens, James Linn, Vikas Sharan, Elias K. Jo
BPM without services
Understanding SOA with Web Services, by Eric Newcomer, Greg Lomow
BPM with services
Understanding SOA with Web Services, by Eric Newcomer, Greg Lomow
Relationship between functionality of
business process and service
Business process
Business process
Business process
Corresponds to ?
Is a part of ?
Is eaqual to ?
Service
Service
Service
Arhitektūru vietas
TOGAF
http://www.opengroup.org/architecture/ togaf7/presents/togaf_ovu.ppt
MIT arhitektūra
http://www.stonesoup.org/Meetings/0409/mtg.pres/grochow.ppt
Zachman architecture
www.va.gov/oirm/architecture/EA/theory/tutorial.ppt
http://www.enterprise-architecture.info/
http://slashdemocracy.org/cgi-bin/page.cgi?g=Enterprise_Architecture%2Findex.html;d=1
9. mājas darbs
• Uzzīmēt savas sistēmas biznesa procesa
modeli (vismaz 2 līmeņi, vismaz 20
procesi)
• Var izmantot šādas notācijas
– GRAPES BM valodu www.gradetools.com
– BPML - http://www.itp-commerce.com/pdf/flyer_general_en.pdf
– Vai kādu citu rīku vai valodu
• Obligāti jāatspoguļo 3D – process,
izpildītājs, informācijas plūsma