3b - Complexity and Design principles

Question 1

What is objective complexity (give examples)?

Answer 1

Complexity can be objective when is has many elements and many links that are subject to change.
Examples:
- # of components (applications)
- # of interfaces
- # of functions (FPA)

Question 2

How can you reduce objective complexity?

Answer 2

• Reduce #components per system & portfolio
• Reduce #interfaces between systems
• Reduce #functions
• Reduce # of people dealing with the system(s)

Question 3

What is subjective complexity?

Answer 3

The effort perceived by actors involved that is required to understand and cope with a system (portfolio).

Question 4

How can you reduce subjective complexity?

Answer 4

• Improve communication between the actors involved, aiming for shared views on the system complex. By using a Group Support System for example.
• Visualize main parts & relations from managerial + IT perspectives.

Question 5

What are some internal drivers for EA?

Answer 5

• Audit (systems, processes, data etc.) / evaluating IST situation
• Specify management information: which data are needed to do business?
• Manage IT system portfolio: which are our core applications?
• Manage (out)sourcing relationships: which IT-services must be internal?
• Guide systems development: specify IST & SOLL
• Preparing a merger or acquisition: planning, due diligence (risks? value?)
• Reducing complexity: of the IT portfolio, applications, and processes.
• Reducing time to market
• Clarifying relationship between business & IT
• Common language, common principles, open discussions etc….

Question 6

What is Design Debt?

Answer 6

The architectural debt that is accumulated by applying a quick fix without proper refactoring. The debt accumulates interest over time.

Question 7

What happens when the # of quick fixes increases over time?

Answer 7

The complexity increases non-linearly.

Question 8

How many principles are proposed in the 2013 paper by Haki and Legner?

Answer 8

152 proposed principles

Question 9

How should EA principles be used?

Answer 9

To limit design space,
guide design decisions.
In order to harmonize IT projects towards predefined goals.

Question 10

What are design principles?

Answer 10

Principles used to govern architectural design and evolution.

Question 11

What are the two nonprinciple types?

Answer 11

Confusion of principles and EAM Goals (benefits) + practices

Question 12

What do Haki & Legner suggest for further investigation (involving the use of principles)?

Answer 12

To turn principles into EA capabilities (thus increasing EA quality), and then increasing EA benefits.