Informasjonsinfrastrukturer - teori og begreper. Gruppetime 21. oktober Kristin Brænden

Transkript

1 Informasjonsinfrastrukturer - teori og begreper Gruppetime 21. oktober Kristin Brænden

2 Design theory for dynamic complexity in information infrastructures: the case of building internet A design theory that tackles dynamic complexity in the design for Information Infrastructures (IIs) Tension between two design problems: (1) the bootstrap problem and (2) the adaptability problem (Hanseth & Lyytinen, 2010)

3 Definisjon på kompleksitet Definisjon på kompleksitet: Complexity can be defined here as the dramatic increase in the number and heterogeneity of included components, relations, and their dynamic and unexpected interactions in IT solutions (Hanseth & Lyytinen, 2010)

4 The bootstrap problem The bootstrap problem: IT-løsninger i en II får sin verdi av å ha mange brukere, noe som krever en rask vekst i antall brukere. Men hvordan få de første personene til å bruke løsningen din? - Må raskt komme opp med løsninger som dekker behovene til de første brukerne, samtidig som man må tenke på helheten = problem (Hanseth & Lyytinen, 2010)

5 The adaptability problem The adaptability problem: Når IIen utvides som et resultat av stadig flere brukere går den inn i en periode med rask vekst. Designet må være tilpasset mange ulike behov, både teknisk og sosialt. Dette krever stor fleksibilitet i IIen. Problem å balansere bootstrapping og adaptability (Hanseth & Lyytinen, 2010)

6 Classes of IT solutions IT capabilities (e.g Text editor) Applications (e.g Web browser) Økende kompleksitet Platforms (e.g MS office, Unix) IIs (e.g Internet) (Hanseth & Lyytinen, 2010)

7 Defining an II A shared, open (and unbounded), heterogeneous and evolving sociotechnical system (which we call installed base) consisting of a set of IT capabilities and their user, operations and design communities (Hanseth & Lyytinen, 2010)

8 Defining an II Shared across multiple communities in a myriad and unexpected ways Open: - New components can be added and integrated with them in unexpected ways and contexts - No clear boundaries between those that can use the II and those that cannot IIs become increasingly heterogeneous as the number of different kinds of technological components are included, but first of all because IIs include (an increasing number of) components of very different nature: user communities, operators, standardization and governance bodies, design communities, etc. (Hanseth & Lyytinen, 2010)

9 Defining an II Evolving: Because IIs are open, they evolve. IIs are never built in a green field, nor do they die. - Vokser inkrementelt The evolution is both enabled and constrained by the installed base, that is the existing configuration of II components. - Whatever is added needs to be integrated and made compatible with this base (Hanseth & Lyytinen, 2010)

10 Design theory Bootstrap problem Design goal: Generate attractors that bootstrap the installed base Design principles: 1. Design initially for usefulness 2. Build upon existing installed bases 3. Expand installed base by persuasive tactics to gain momentum (Hanseth & Lyytinen, 2010)

11 Design theory Adaptability problem Design goal: Make the system maximally adaptive and variety generating as to avoid technology traps Design principles: 1. Make the IT capability as simple as possible 2. Modularize the II (Hanseth & Lyytinen, 2010)

12 Large-Scale Complex IT Systems The reductionism behind today s softwareengineering methods breaks down in the face of systems complexity Coalitions of systems Systems engineering focuses on developing systems as a whole - vanskelig i systemer av systemer (Sommerville et al., 2012)

13 System complexity Complexity stems from the number and type of relationships between the systems s components and between the system and its environment When the elements in a system involve many dynamic relationships, complexity is inevitable Inherent VS epistemic complexity (Sommerville et al., 2012)

14 Sosio-Technical Systems To reflect the fact they involve evolving and interacting communities that include technical, human, and organizational elements, they are sometimes also called socio-technical ecosystems though the term socio-technical systems is more common. Socio-technical systems include people and processes, as well as technological systems (Sommerville et al., 2012)

15 Reductionist assumptions VS reality (Sommerville et al., 2012)

16 Design as Bootstrapping. On the Evolution of ICT Networks in Healt Care Telemedicne is expected to enable huge improvements of health care services through radically new and improved ways of collaboration and organizing within the healt care sectors. Lots of prototypes have been made and demonstrated. Unfortunately, it has proved to be very hard to bring the prototypes into regular use, or at least beyond use by very small networks of users - they do not seem to take off. The aim of this paper is to discuss this take off problem - in particular strategies for overcoming it. (Hanseth & Aanestad, 2003)

17 The Logic of Networks - Their value for each user increases with the total number of users that are using the technology - As the number of users grows, the technology tends to get momentum and it starts growing through a self-reinforcing process - Critical mass - No user wants to be the first one (Hanseth & Aanestad, 2003)

18 Bootstrapping A design process taking as its starting point the challenge of enrolling the first users and then drawing upon the existing base of users and technology as a resource to extend the network To promote or develop by iniative and effort with little or no assistance (Hanseth & Aanestad, 2003)

19 Bootstrapping Eksempler fra virkeligheten Vellykket: Overføring av kirurgi, Telemedisin i ambulanser - Startet i det små, med stor verdi for brukerene Ikke vellykket: EDI - Stort standardiseringsprosjekt - Top-down (Hanseth & Aanestad, 2003)

20 Bootstrapping Tenk på: - Brukernes motivasjon og kunnskaper - Bruksområder og brukssituasjoner - Aspekter ved teknologien (Hanseth & Aanestad, 2003)

21 How to Infrastructure We seek to explore the development and design of infrastructure; our main argument will be that a social and theoretical understanding of infrastructure is key to the design of new media applications in our highly networked, information convergent society. Infrastructure: - It is that upon which something else rides, or works, a platform of sorts - Is not absolute, but realtive to working conditions (Star & Bowker, 2012)

22 How Infrastructure Happens - We need standards - At both the technical and the social level, there is no guarantee that the best set of standards will win - E.g QWERTY - Network externalities: - Eksempel: Telefonen din blir mye mer verdt om det er mange mennesker du kan ringe til (positive) - Én VS mange standarder (Star & Bowker, 2012)

23 How Infrastructure Happens - Vi må ha en relativt stabil teknologi - Vi må fokusere på kommunikasjon - IIen må være fleksibel - Etiske og politiske hensyn (Star & Bowker, 2012)

24 Kompleksitet Fra Hanseth og Lyytinen: Complexity can be defined here as the dramatic increase in the number and heterogeneity of included components, relations, and their dynamic and unexpected interactions in IT solutions Fra Sommerville et al.: Complexity stems from the number and type of relationships between the systems s components and between the system and its environment

25 Sosio-teknisk Fra Hanseth og Lyytinen: Involves both technical and social elements and their relationships. Fra Sommerville et al.: To reflect the fact they involve evolving and interacting communities that include technical, human, and organizational elements, they are sometimes also called socio-technical ecosystems though the term socio-technical systems is more common.