arhitektūru orientēta prasību inženierija
Post on 13-Jan-2016
42 Views
Preview:
DESCRIPTION
TRANSCRIPT
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)
http://www.trafford.com/robots/03-1984.html
How to Survive in the Jungle of Enterprise Architecture Frameworks: Creating or Choosing an Enterprise Architecture Framework by Jaap Schekkerman
http://www.zifa.com/
Based on work by John A. Zachman
VA Enterprise Architecture
DATAWhat
FUNCTIONHow
NETWORKWhere
PEOPLEWho
TIMEWhen
MOTIVATIONWhy
DATAWhat
FUNCTIONHow
NETWORKWhere
PEOPLEWho
TIMEWhen
MOTIVATIONWhy
SCOPE(CONTEXTUAL)
Planner
ENTERPRISEMODEL(CONCEPTUAL)
Owner
SYSTEM MODEL(LOGICAL)
Designer
TECHNOLOGYMODEL(PHYSICAL)
Builder
DETAILEDREPRESENTATIONS(OUT-OF-CONTEXT)
Sub-Contractor
FUNCTIONINGENTERPRISE
SCOPE(CONTEXTUAL)
Planner
ENTERPRISEMODEL
(CONCEPTUAL)
Owner
SYSTEM MODEL(LOGICAL)
Designer
TECHNOLOGYMODEL
(PHYSICAL)
Builder
DETAILEDREPRESENTATIONS(OUT-OF-CONTEXT)
Sub-Contractor
FUNCTIONINGENTERPRISE
Things Important to the Business
Entity = Class of Business Thing
Processes Performed
Function = Class of Business Process
Semantic Model
Ent = Business Entity Rel = Business Relationship
Business Process Model
Proc = Business Process I/O = Business Resources
Business LogisticsSystem
Node = Business Location Link = Business Linkage
Work Flow Model
People = Organization Unit Work = Work Product
Master Schedule
Time = Business Event Cycle = Business Cycle
Business Plan
End = Business Objectiv e Means = Business Strategy
ImportantOrganizations
People = Major Organizations
Business locations
Node = Major Business Locations
Ev ents Significantto the Business
Time = MajorBusiness Event
Business Goalsand Strategy
Ends/Means =Major Business Goals
Logical DataModel
Ent = Data Entity Rel = Data Relationship
Application Architecture
Proc = Application Function I/O = User Views
Distributed SystemArchitecture
Node = IS Function Link = Line Characteristics
Human InterfaceArchitecture
People = Role Work = Deliv erable
ProcessingStructure
Time = System Event Cycle = Processing Cycle
Business RuleModel
End = Structural Assertion Means = Action Assertion
Physical DataModel
Ent = Segment/Table Rel = Pointer/Key
SystemDesign
Proc = Computer Function I/O = Data Elements/Sets
TechnologyArchitecture
Node = Hardware/Softw are Link = Line Specifications
PresentationArchitecture
People = User Work = Screen Format
ControlStructure
Time = Ex ecute Cycle = Component Cycle
RuleDesign
End = Condition Means = Action
DataDefinition
Ent = Field Rel = Address
Program
Proc = Language Statement I/O = Control Block
Netw orkArchitecture
Node = Addresses Link = Protocols
SecurityArchitecture
People = IdentityWork = Job
Timing Definition
Time = InterruptCycle = Machine Cycle
RuleDesign
End = Sub-Condition Means = Step
Data
Ent = Rel =
Function
Proc =I/O =
Netw ork
Node = Link =
Organization
People = Work =
Schedule
Time = Cycle =
Strategy
End = Means =
Based on work by John A. Zachman
VA Enterprise Architecture
DATAWhat
FUNCTIONHow
NETWORKWhere
PEOPLEWho
TIMEWhen
MOTIVATIONWhy
DATAWhat
FUNCTIONHow
NETWORKWhere
PEOPLEWho
TIMEWhen
MOTIVATIONWhy
SCOPE(CONTEXTUAL)
Planner
ENTERPRISEMODEL(CONCEPTUAL)
Owner
SYSTEM MODEL(LOGICAL)
Designer
TECHNOLOGYMODEL(PHYSICAL)
Builder
DETAILEDREPRESENTATIONS(OUT-OF-CONTEXT)
Sub-Contractor
FUNCTIONINGENTERPRISE
SCOPE(CONTEXTUAL)
Planner
ENTERPRISEMODEL
(CONCEPTUAL)
Owner
SYSTEM MODEL(LOGICAL)
Designer
TECHNOLOGYMODEL
(PHYSICAL)
Builder
DETAILEDREPRESENTATIONS(OUT-OF-CONTEXT)
Sub-Contractor
FUNCTIONINGENTERPRISE
Things Important to the Business
Entity = Class of Business Thing
Processes Performed
Function = Class of Business Process
Semantic Model
Ent = Business Entity Rel = Business Relationship
Business Process Model
Proc = Business Process I/O = Business Resources
Business LogisticsSystem
Node = Business Location Link = Business Linkage
Work Flow Model
People = Organization Unit Work = Work Product
Master Schedule
Time = Business Event Cycle = Business Cycle
Business Plan
End = Business Objectiv e Means = Business Strategy
ImportantOrganizations
People = Major Organizations
Business locations
Node = Major Business Locations
Ev ents Significantto the Business
Time = MajorBusiness Event
Business Goalsand Strategy
Ends/Means =Major Business Goals
Logical DataModel
Ent = Data Entity Rel = Data Relationship
Application Architecture
Proc = Application Function I/O = User Views
Distributed SystemArchitecture
Node = IS Function Link = Line Characteristics
Human InterfaceArchitecture
People = Role Work = Deliv erable
ProcessingStructure
Time = System Event Cycle = Processing Cycle
Business RuleModel
End = Structural Assertion Means = Action Assertion
Physical DataModel
Ent = Segment/Table Rel = Pointer/Key
SystemDesign
Proc = Computer Function I/O = Data Elements/Sets
TechnologyArchitecture
Node = Hardware/Softw are Link = Line Specifications
PresentationArchitecture
People = User Work = Screen Format
ControlStructure
Time = Ex ecute Cycle = Component Cycle
RuleDesign
End = Condition Means = Action
DataDefinition
Ent = Field Rel = Address
Program
Proc = Language Statement I/O = Control Block
Netw orkArchitecture
Node = Addresses Link = Protocols
SecurityArchitecture
People = IdentityWork = Job
Timing Definition
Time = InterruptCycle = Machine Cycle
RuleDesign
End = Sub-Condition Means = Step
Data
Ent = Rel =
Function
Proc =I/O =
Netw ork
Node = Link =
Organization
People = Work =
Schedule
Time = Cycle =
Strategy
End = Means =
www.va.gov/oirm/architecture/EA/theory/tutorial.ppt DEMO
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
Based on work by John A. Zachman
VA Enterprise Architecture
DATAWhat
FUNCTIONHow
NETWORKWhere
PEOPLEWho
TIMEWhen
MOTIVATIONWhy
DATAWhat
FUNCTIONHow
NETWORKWhere
PEOPLEWho
TIMEWhen
MOTIVATIONWhy
SCOPE(CONTEXTUAL)
Planner
ENTERPRISEMODEL(CONCEPTUAL)
Owner
SYSTEM MODEL(LOGICAL)
Designer
TECHNOLOGYMODEL(PHYSICAL)
Builder
DETAILEDREPRESENTATIONS(OUT-OF-CONTEXT)
Sub-Contractor
FUNCTIONINGENTERPRISE
SCOPE(CONTEXTUAL)
Planner
ENTERPRISEMODEL
(CONCEPTUAL)
Owner
SYSTEM MODEL(LOGICAL)
Designer
TECHNOLOGYMODEL
(PHYSICAL)
Builder
DETAILEDREPRESENTATIONS(OUT-OF-CONTEXT)
Sub-Contractor
FUNCTIONINGENTERPRISE
Things Important to the Business
Entity = Class of Business Thing
Processes Performed
Function = Class of Business Process
Semantic Model
Ent = Business Entity Rel = Business Relationship
Business Process Model
Proc = Business Process I/O = Business Resources
Business LogisticsSystem
Node = Business Location Link = Business Linkage
Work Flow Model
People = Organization Unit Work = Work Product
Master Schedule
Time = Business Event Cycle = Business Cycle
Business Plan
End = Business Objectiv e Means = Business Strategy
ImportantOrganizations
People = Major Organizations
Business locations
Node = Major Business Locations
Ev ents Significantto the Business
Time = MajorBusiness Event
Business Goalsand Strategy
Ends/Means =Major Business Goals
Logical DataModel
Ent = Data Entity Rel = Data Relationship
Application Architecture
Proc = Application Function I/O = User Views
Distributed SystemArchitecture
Node = IS Function Link = Line Characteristics
Human InterfaceArchitecture
People = Role Work = Deliv erable
ProcessingStructure
Time = System Event Cycle = Processing Cycle
Business RuleModel
End = Structural Assertion Means = Action Assertion
Physical DataModel
Ent = Segment/Table Rel = Pointer/Key
SystemDesign
Proc = Computer Function I/O = Data Elements/Sets
TechnologyArchitecture
Node = Hardware/Softw are Link = Line Specifications
PresentationArchitecture
People = User Work = Screen Format
ControlStructure
Time = Ex ecute Cycle = Component Cycle
RuleDesign
End = Condition Means = Action
DataDefinition
Ent = Field Rel = Address
Program
Proc = Language Statement I/O = Control Block
Netw orkArchitecture
Node = Addresses Link = Protocols
SecurityArchitecture
People = IdentityWork = Job
Timing Definition
Time = InterruptCycle = Machine Cycle
RuleDesign
End = Sub-Condition Means = Step
Data
Ent = Rel =
Function
Proc =I/O =
Netw ork
Node = Link =
Organization
People = Work =
Schedule
Time = Cycle =
Strategy
End = Means =
Based on work by John A. Zachman
VA Enterprise Architecture
DATAWhat
FUNCTIONHow
NETWORKWhere
PEOPLEWho
TIMEWhen
MOTIVATIONWhy
DATAWhat
FUNCTIONHow
NETWORKWhere
PEOPLEWho
TIMEWhen
MOTIVATIONWhy
SCOPE(CONTEXTUAL)
Planner
ENTERPRISEMODEL(CONCEPTUAL)
Owner
SYSTEM MODEL(LOGICAL)
Designer
TECHNOLOGYMODEL(PHYSICAL)
Builder
DETAILEDREPRESENTATIONS(OUT-OF-CONTEXT)
Sub-Contractor
FUNCTIONINGENTERPRISE
SCOPE(CONTEXTUAL)
Planner
ENTERPRISEMODEL
(CONCEPTUAL)
Owner
SYSTEM MODEL(LOGICAL)
Designer
TECHNOLOGYMODEL
(PHYSICAL)
Builder
DETAILEDREPRESENTATIONS(OUT-OF-CONTEXT)
Sub-Contractor
FUNCTIONINGENTERPRISE
Things Important to the Business
Entity = Class of Business Thing
Processes Performed
Function = Class of Business Process
Semantic Model
Ent = Business Entity Rel = Business Relationship
Business Process Model
Proc = Business Process I/O = Business Resources
Business LogisticsSystem
Node = Business Location Link = Business Linkage
Work Flow Model
People = Organization Unit Work = Work Product
Master Schedule
Time = Business Event Cycle = Business Cycle
Business Plan
End = Business Objectiv e Means = Business Strategy
ImportantOrganizations
People = Major Organizations
Business locations
Node = Major Business Locations
Ev ents Significantto the Business
Time = MajorBusiness Event
Business Goalsand Strategy
Ends/Means =Major Business Goals
Logical DataModel
Ent = Data Entity Rel = Data Relationship
Application Architecture
Proc = Application Function I/O = User Views
Distributed SystemArchitecture
Node = IS Function Link = Line Characteristics
Human InterfaceArchitecture
People = Role Work = Deliv erable
ProcessingStructure
Time = System Event Cycle = Processing Cycle
Business RuleModel
End = Structural Assertion Means = Action Assertion
Physical DataModel
Ent = Segment/Table Rel = Pointer/Key
SystemDesign
Proc = Computer Function I/O = Data Elements/Sets
TechnologyArchitecture
Node = Hardware/Softw are Link = Line Specifications
PresentationArchitecture
People = User Work = Screen Format
ControlStructure
Time = Ex ecute Cycle = Component Cycle
RuleDesign
End = Condition Means = Action
DataDefinition
Ent = Field Rel = Address
Program
Proc = Language Statement I/O = Control Block
Netw orkArchitecture
Node = Addresses Link = Protocols
SecurityArchitecture
People = IdentityWork = Job
Timing Definition
Time = InterruptCycle = Machine Cycle
RuleDesign
End = Sub-Condition Means = Step
Data
Ent = Rel =
Function
Proc =I/O =
Netw ork
Node = Link =
Organization
People = Work =
Schedule
Time = Cycle =
Strategy
End = Means =
MIT Enterprise Architecture DeliverablesCurrent State
System ContextDiagram
Key SystemsInventory
System Logical andPhysical Architecture
DiagramsContext
Services Matrix
Integration Inventory Systems on a Page
Business Process Flowsand Scenarios
Future State
Technology Standards Business Strategy Future State ServicesMatrix
Future State Logical Architecture Vision
Road Map
List of Initiatives
Prioritization Model
Architecture MigrationMaps
Short Term Roadmap
Long Term Roadmap
Timeless/ Evolutionary
Enterprise Data Model
Architectural ReviewProcess
IT Governance Process
ArchitecturalPrinciples
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
Service
Corresponds to ? Is a part of ? Is eaqual to ?
Business process
Service
Business process
Service
Arhitektūru vietas
TOGAFhttp://www.opengroup.org/architecture/ togaf7/presents/togaf_ovu.ppt
MIT arhitektūrahttp://www.stonesoup.org/Meetings/0409/mtg.pres/grochow.ppt
Zachman architecturewww.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
top related