Lecture 3B - EA as a process (Method for change) Flashcards
How do you reduce objective complexity?
- Reduce # of components per system & portfolio
- Reduce # of interfaces between systems
- Reduce # of functions (through FPA)
How do you reduce subjective complexity?
- Reduce the effort to understand the portfolio (by visualizing main parts & relations from managerial + IT perspectives)
- Support (group) decision-making using AHP.
What can be internal drivers for EA?
- Audit of systems, processes, data etc.
- Specifying Management Information
- Manage IT system portfolio
- Manage sourcing relationships
- Guide system development
- Preparing a merger or acquisition
- Reducing complexity
- Reducing time to market
What is design debt?
- Architectural debt accumulated by applying a quick fix without proper refactoring ( restructuring an existing body of code)
- Interest of the debt = cost/effort to solve
- Complexity increases non-linearly each time a quick fix is applied.
- Having design debt will fuck you up in the long run.
How can you recognize design debt?
- No visible architectural champion
- Lack of balance between business and IT department
- No decommissioning strategy
- Duplicate systems
- Geological time scales required to make simple business changes (No agility)
- Lack of confidence that change will actually work
- Project over-burn budget and schedule
- IT costs erode business margins
- Brand erosion
What is meant with decommissioning strategy?
How to deal with removing/replacing/updating an old system.
What is design debt in terms of EA complexity?
The difference between the target complexity the firm aims for and the max complexity a firm can handle. (Total design debt)
Firm specific: Between your current state and your desired state
-> The more mature your firm, the more complexity it can handle and the more complexity it can reduce as well.
What can be the end goal/effect of using EA principles?
Use of principles -> improve quality of EA (Capabilities) -> EA benefits.