1. INF5210 Overview & summary

2. Shaping the Evolution of Information Infrastructures: Architecture, Governance Regime, Process Strategy

3. Towards a Theory of Information Infrastructures A Theories of Information Infrastructures (Evolution & Design) Process Strategies Architecture Governance Assemblage Theory Complexity Science Actor Network Theory Reflexive Modernisation

4. Design theory Kernel theory Design principles and guidelines

5. II Shared, open heterogeneous, evolving installed base. Complexity – Emergence, path-dependence, non-liearity – Interactions between and propagation of side- effects – Self-reinforcing – Reflexivity

6. Infrastructure evolution Evolution – Adoption – Scaling – Innovation – Harmonization/restructuring/consolidation – Crumbling/fragmentation

7. Innovation Of, in, on W. Brian Arthur – The nature of technology. What it is and how it evolves Out of a material (re-)combination Structural deepening Re-domaing

8. Design = installed base cultivation Successful information infrastructures = Generative information infrastructure

9. Saturday, February 27, 2016Department of Informatics9 Generative Technology ”.. A technology’s overall capacity to produce unprompted change driven by large, varied, and uncoordinated audiences.” – Capacity for leverage – Adaptability – Ease of mastery – Accessibility – Computers – PC & Internet – Opposite: Appliances Telecom: intelligent network + appliances

10. Saturday, February 27, 2016Department of Informatics10 Generative Technology ”.. A technology’s overall capacity to produce unprompted change driven by large, varied, and uncoordinated audiences.” – Capacity for leverage – Adaptability – Ease of mastery – Accessibility – Computers – PC & Internet – Opposite: Appliances Telecom: intelligent network + appliances

11. Generative infrastructure = Generative architecture Generative governance regime Generative process strategy Generative fit

12. Requirements to II architectures Bootstrapable, i.e. the architecture needs to make it possible to build the II in the first place. To achieve this, the solutions need to be simple and the architecture needs to enable the II to be developed by a small organization of low (organizational) complexity. Aligned with the structures of an appropriate organization responsible for the operations of the II, i.e. the architecture needs to be operationable. Flexible to enable experimental architecting and adaptable to new requirements as the II matures and scales. Extensible to allow for new innovations extending the II.

13. Requirements to II architectures Bootstrapable, i.e. the architecture needs to make it possible to build the II in the first place. To achieve this, the solutions need to be simple and the architecture needs to enable the II to be developed by a small organization of low (organizational) complexity. Aligned with the structures of an appropriate organization responsible for the operations of the II, i.e. the architecture needs to be operationable. Flexible to enable experimental architecting and adaptable to new requirements as the II matures and scales. Extensible to allow for new innovations extending the II.

14. (Process) Strategy Specification driven or evolutionary Bootstrapping Anticipatory standardization Integrated applications Flexible generification

15. Architecture Loose or tight couplings/integration Centralized or decentralized (end-2-end) Platforms INA/ACA SPA/CSCA

16. Governance regime Hierarcical organization, project management tools Federated, distribution of decision rights Digital commons, communication tools – Open source, wikipedia, …

17. Cases Aims? (Harmonization, innovation,,) Process strategy, governance regime & archtecure changes over time – Bootstrapping, architectural innovation – Scaling, adoption, innovation