86661
Enterprise Architecture
- Where it is applicable
- public/private
sector
organisation
- Entire
business/corporation
- Part of a
larger
enterprise
- multiply
outsourced
business
operation
- public/private
sector
organisation
- What is it?
- coherent whole of
- Principles
- Methods
- Models
- used in
the design
and
realisation
of
- organisational
structure
- information
systems
- infrastructure
- organisational
structure
- Principles
- coherent whole of
- Why consider it
- Information
systems
must keep
pace with
those
changes
- Information
systems
must keep
pace with
those
changes
- Key
Concepts
- Linking
Business
Goals with
Information
System
- "as is" to the "to be"
- Used to
capture
significant
representations
of the
architecture
- Used to
enhance
communication
- Linking
Business
Goals with
Information
System
- EA Frameworks
- Zachman
Framework
- Federal
Enterprise
Architecture
Planning
- Enterprise
Architecture
Planning
- TOGAF
- Architecture
Development
Method
(ADM)
- Architecture
Development
Method
(ADM)
- Zachman
Framework
- ADM Phases
- 1.
Preliminary
- outling
''as-is"
and
"to-be
- outling
''as-is"
and
"to-be
- 2. Business
Architecture
- Business
Strategy
- Governance
- Organisation
- Business
Processes
- Business
Strategy
- 3. Data
and
Application
Domains
- Architecture
of IT
applications
deployed
- Architecture
of IT
applications
deployed
- 4.
Technology
Architecture
- Describes
software
and
hardware
capabilities
- Describes
software
and
hardware
capabilities
- 5.
Opportunities
and Solutions
- 5.
Migration
Planning
- 6.
Implementation
Governance
- 7.
Architecture
Change
Management
- 1.
Preliminary
- Potential Pitfalls
of EA modelling
- Lack of
senior
managment
commitment
- Lack of
governance
- "Overscoping"
the projects
- Failure to
establish good
communication
mechanisms
- Lack of
senior
managment
commitment
Want to create your own Mind Maps for free with GoConqr? Learn more.