Table of Contents
,
1.1. Solving conflicting requirements
1.2. Three periods in IS management
Chapter 2. Complexity, Simplicity,
and Abstraction
2.1. What does information theory tell us?
2.2. What does the design tell us?
3.2. Concepts of value for an IS
3.3. Are these values sufficient and independent?
Chapter 4. Promoting Value Through
Simplicity
4.1. Growing technical heterogeneity
Chapter 5. Simplicity Best Practices
5.1. Putting simplicity principles into practice
Appendix 1. Digging into Information Theory
A1.2. Shannon entropy in short
A1.4. Choosing a scale of description
A1.5. Relation to Shannon entropy
A1.6. Computing the Kolmogorov complexity
A1.7. Kolmogorov complexity in short
A1.9. Bennetts logical depth in short
Appendix 2. Two Measures of Code Complexity
A2.2. An example of a scale-invariant
complexity measure
Appendix 3. Why Has SOA Failed So Often?
A.3.1. The need for flexibility
A.3.2. First issue: no suitable enterprise architecture
A.3.3. Second issue: no data integration
A.3.4. Identifying the operating model
A.3.5. Which models are compatible with SOA?