Software Platform Ecosystems - Universitetet i oslo · • Example: creditcard, Vipps, cool...
Transcript of Software Platform Ecosystems - Universitetet i oslo · • Example: creditcard, Vipps, cool...
![Page 1: Software Platform Ecosystems - Universitetet i oslo · • Example: creditcard, Vipps, cool photofilters •-> from productsto services –clientsto web-basedservices, softwarebasedmapsin](https://reader033.fdocuments.us/reader033/viewer/2022050213/5f5f2ca17dca993cee7ddf10/html5/thumbnails/1.jpg)
SoftwarePlatformEcosystems
INF57502017
Unless noted,alltables,citations,andfigures are taken fromorare facsimiles from:Tiwana,Amrit.Platformecosystems:aligningarchitecture,governance,andstrategy.Newnes,2013.
Fromchapters 1,2and5
![Page 2: Software Platform Ecosystems - Universitetet i oslo · • Example: creditcard, Vipps, cool photofilters •-> from productsto services –clientsto web-basedservices, softwarebasedmapsin](https://reader033.fdocuments.us/reader033/viewer/2022050213/5f5f2ca17dca993cee7ddf10/html5/thumbnails/2.jpg)
Contentsandlearning outcome of the lecture
• What platforms are,andtheir core components• Difference between software platforms andother typesof platforms• Drivers towards software platforms• Some important concepts• Some important principles• Important aspects of platform architecture• Platformlifecycles• Howdoes allthis relate toyour group assignments andthe DHIS2?
![Page 3: Software Platform Ecosystems - Universitetet i oslo · • Example: creditcard, Vipps, cool photofilters •-> from productsto services –clientsto web-basedservices, softwarebasedmapsin](https://reader033.fdocuments.us/reader033/viewer/2022050213/5f5f2ca17dca993cee7ddf10/html5/thumbnails/3.jpg)
Why software platform ecosystems?
• Softwareplatform ecosystem «logics»increasingly plays amoredominantrole incompetition inadiversesets of markets• Competitionmigratingtorivalplatforms• potentmixofspecializedexpertisewiththediscipliningpowerofplatformmarketscanfosterinnovationatapacethatcantrumpeventhemightiestproductandservicebusiness,e.g.BlackberryvsAppleandGoogle;Cameraproducesvsmobilephones.
• Why inthe open source development course?
![Page 4: Software Platform Ecosystems - Universitetet i oslo · • Example: creditcard, Vipps, cool photofilters •-> from productsto services –clientsto web-basedservices, softwarebasedmapsin](https://reader033.fdocuments.us/reader033/viewer/2022050213/5f5f2ca17dca993cee7ddf10/html5/thumbnails/4.jpg)
Maincomponents of asoftware platformiOS Android Nokia
![Page 5: Software Platform Ecosystems - Universitetet i oslo · • Example: creditcard, Vipps, cool photofilters •-> from productsto services –clientsto web-basedservices, softwarebasedmapsin](https://reader033.fdocuments.us/reader033/viewer/2022050213/5f5f2ca17dca993cee7ddf10/html5/thumbnails/5.jpg)
Evolutionof platform ecosystems
• Architecture:Structure
• Governance:Process andrules
• Evolution:«…the interplay betweenitsirreversiblearchitectureandhowitisgoverned.”
![Page 6: Software Platform Ecosystems - Universitetet i oslo · • Example: creditcard, Vipps, cool photofilters •-> from productsto services –clientsto web-basedservices, softwarebasedmapsin](https://reader033.fdocuments.us/reader033/viewer/2022050213/5f5f2ca17dca993cee7ddf10/html5/thumbnails/6.jpg)
FocusinTiwana (2013):software platforms:
• Platformswhere third partycomplementors add toplatform capabilities andfunctionality• Possibilities forhundreds orthousands of actors toadd functionality tothe sameecosystem
• Upstreamvaluechaintheplatformitself.Downstreamappdevelopers.Enduserscanuniquelymix-and-matchdownstreamcomplements– makingtheinnovationandadoptioninthedownstreamcentralforsuccessoffailure• Trueplatformsmustbeatleasttwo-sidedandspanatleasttwodistinctgroupsappdevelopersandend-usersthatinteractthroughtheplatform.• Mostsuccessfulplatformsbeganasstandaloneproductsorservices:iOS,Windows,Facebook,Amazon,eBay,Google,Firefox,Salesforce,andDropbox
• What does that imply andmean?
![Page 7: Software Platform Ecosystems - Universitetet i oslo · • Example: creditcard, Vipps, cool photofilters •-> from productsto services –clientsto web-basedservices, softwarebasedmapsin](https://reader033.fdocuments.us/reader033/viewer/2022050213/5f5f2ca17dca993cee7ddf10/html5/thumbnails/7.jpg)
Driverstowards platformization
![Page 8: Software Platform Ecosystems - Universitetet i oslo · • Example: creditcard, Vipps, cool photofilters •-> from productsto services –clientsto web-basedservices, softwarebasedmapsin](https://reader033.fdocuments.us/reader033/viewer/2022050213/5f5f2ca17dca993cee7ddf10/html5/thumbnails/8.jpg)
Moreabout drivers
• Deepening specialization:• Softwarecode grow larger andbecome morecomplex (morefunctionality)->morespecializationneeded forfurther growth.
• ->Morefocus needed forcompanies• ->Need forintegration of distributed knowledge fromothers• ->Moreeffort tocompete against successful platform owners
• Packetization:• Digitalization of anactivity,process,product orservice
• ->Enables transportation of information through the Internet – high speed,low cost – Removeslocationconstraints towork ->new possible businessmodels
• ->Deepening specialization• Example:globalradiology serviceinIndia(e.g.https://www.outsource2india.com/services/radiology.asp)
![Page 9: Software Platform Ecosystems - Universitetet i oslo · • Example: creditcard, Vipps, cool photofilters •-> from productsto services –clientsto web-basedservices, softwarebasedmapsin](https://reader033.fdocuments.us/reader033/viewer/2022050213/5f5f2ca17dca993cee7ddf10/html5/thumbnails/9.jpg)
Moreabout drivers
• Softwareembedding:• Making software of businessprocesses andactivities
• Example:credit card,Vipps,coolphoto filters
• ->fromproducts toservices– clients toweb-based services,software based maps incars• ->physical – digitalboundary -• ->convergence across industries – gaming consoles andcameras into phones,Amazonkindle
• Internet of things:• Cheap sensorsonlineandnetworked
• Example:Sensorstomonitorpatients athome,door sensorstellingif you forget tolock your door
• ->Fromstock of datatostreams of data• ->Communication of contextual data• Examples:OneTeslacar tellingabout humpinthe road – allother cars get the information andadjust car configuration totake lessimpact when drivingthrough the sameplace.
• Optimalization of resources inahospital,dynamic prize regulations
![Page 10: Software Platform Ecosystems - Universitetet i oslo · • Example: creditcard, Vipps, cool photofilters •-> from productsto services –clientsto web-basedservices, softwarebasedmapsin](https://reader033.fdocuments.us/reader033/viewer/2022050213/5f5f2ca17dca993cee7ddf10/html5/thumbnails/10.jpg)
Moreabout drivers
• Ubiquity:• Precence of Internet «everywhere»– lower prices – fasternetwork
• ->locationindependence of tasks andservices• ->networks of firms• ->crowdsourcing
• Example:Googlemaps traffic information
• Thecombination of the drivers• Pushing innovation ecosystems towards growing number of industries,like:
• mortgage,finance,drug development,software,automotive,healthcare,banking,foodservices,andenergy
![Page 11: Software Platform Ecosystems - Universitetet i oslo · • Example: creditcard, Vipps, cool photofilters •-> from productsto services –clientsto web-basedservices, softwarebasedmapsin](https://reader033.fdocuments.us/reader033/viewer/2022050213/5f5f2ca17dca993cee7ddf10/html5/thumbnails/11.jpg)
Platformconcepts
• Platformlifecycle:
![Page 12: Software Platform Ecosystems - Universitetet i oslo · • Example: creditcard, Vipps, cool photofilters •-> from productsto services –clientsto web-basedservices, softwarebasedmapsin](https://reader033.fdocuments.us/reader033/viewer/2022050213/5f5f2ca17dca993cee7ddf10/html5/thumbnails/12.jpg)
Lifecycle
![Page 13: Software Platform Ecosystems - Universitetet i oslo · • Example: creditcard, Vipps, cool photofilters •-> from productsto services –clientsto web-basedservices, softwarebasedmapsin](https://reader033.fdocuments.us/reader033/viewer/2022050213/5f5f2ca17dca993cee7ddf10/html5/thumbnails/13.jpg)
Platformconcepts
• Platformproperties:
![Page 14: Software Platform Ecosystems - Universitetet i oslo · • Example: creditcard, Vipps, cool photofilters •-> from productsto services –clientsto web-basedservices, softwarebasedmapsin](https://reader033.fdocuments.us/reader033/viewer/2022050213/5f5f2ca17dca993cee7ddf10/html5/thumbnails/14.jpg)
Properties
![Page 15: Software Platform Ecosystems - Universitetet i oslo · • Example: creditcard, Vipps, cool photofilters •-> from productsto services –clientsto web-basedservices, softwarebasedmapsin](https://reader033.fdocuments.us/reader033/viewer/2022050213/5f5f2ca17dca993cee7ddf10/html5/thumbnails/15.jpg)
Platformconcepts
• Platformdynamics:
![Page 16: Software Platform Ecosystems - Universitetet i oslo · • Example: creditcard, Vipps, cool photofilters •-> from productsto services –clientsto web-basedservices, softwarebasedmapsin](https://reader033.fdocuments.us/reader033/viewer/2022050213/5f5f2ca17dca993cee7ddf10/html5/thumbnails/16.jpg)
Platformguiding principles
• Platformstartup principles:
![Page 17: Software Platform Ecosystems - Universitetet i oslo · • Example: creditcard, Vipps, cool photofilters •-> from productsto services –clientsto web-basedservices, softwarebasedmapsin](https://reader033.fdocuments.us/reader033/viewer/2022050213/5f5f2ca17dca993cee7ddf10/html5/thumbnails/17.jpg)
Platformguiding principles
• Platformdesignprinciples:
![Page 18: Software Platform Ecosystems - Universitetet i oslo · • Example: creditcard, Vipps, cool photofilters •-> from productsto services –clientsto web-basedservices, softwarebasedmapsin](https://reader033.fdocuments.us/reader033/viewer/2022050213/5f5f2ca17dca993cee7ddf10/html5/thumbnails/18.jpg)
Platformguiding principles
• Platformevolution principles
![Page 19: Software Platform Ecosystems - Universitetet i oslo · • Example: creditcard, Vipps, cool photofilters •-> from productsto services –clientsto web-basedservices, softwarebasedmapsin](https://reader033.fdocuments.us/reader033/viewer/2022050213/5f5f2ca17dca993cee7ddf10/html5/thumbnails/19.jpg)
Some key points• Thelifecycleofatechnologysolutionhasthree-dimensions:
• pre- orpost-dominantdesignstage(frommanytoone)• maturity trajectory (the S-curve)• proportionofthetotalprospectiveuserbaseadoption
• Multisidedness offers:same-sideandcross-sidenetworkeffects,lock-ins(coerciveandvalue-driven),prospectsofswallowingorbeswallowed
• Architecturesprovideblueprintformasscoordination.Conventionalcoordinationandcontrolmechanismscostlyandimplausibleinlargeecosystems
• Governancecanamplifyordiminishtheadvantagesofgoodarchitecture.Governanceandarchitecturemustbeco-designedandcoevolved
• Evolutionarypaceofaplatformisrelativetoitsrivals(theRedQueeneffect).• Emergentinnovationcanonlybefacilitated,notplannedbyaplatformowner.
• Spontaneouslyarisefromtheselfishpursuitofself-interestbyindividualecosystemparticipants.• Chicken-or-eggproblemandthepenguinproblemtogetofftheground- unattractiveforeithersidetojoinunlessthereisacriticalmassontheotherside.Uncertaintyaboutwhetherotherswilljointheplatformecosystemcanstallinitialadoption,creatingthepenguinproblem
• Balanceautonomywithintegration(theseesawproblem)separablebutre-integratable (HumptyDumpty).Organizedtomirrorthearchitectureandthe“microarchitecture”(themirroringprinciple).
![Page 20: Software Platform Ecosystems - Universitetet i oslo · • Example: creditcard, Vipps, cool photofilters •-> from productsto services –clientsto web-basedservices, softwarebasedmapsin](https://reader033.fdocuments.us/reader033/viewer/2022050213/5f5f2ca17dca993cee7ddf10/html5/thumbnails/20.jpg)
Platformarchitectures
• Thearchitecture enable (ornot)participation among potential andactual third partyinnovators• Thirdpartyinnovators mustbeable andmotivated toparticipate• Abilitythrough architecture• Motivation through governance
• Mainarchitecture parts(andtheir interconnectedness)• Platformcore• Platforminterfaces• «Apps»
![Page 21: Software Platform Ecosystems - Universitetet i oslo · • Example: creditcard, Vipps, cool photofilters •-> from productsto services –clientsto web-basedservices, softwarebasedmapsin](https://reader033.fdocuments.us/reader033/viewer/2022050213/5f5f2ca17dca993cee7ddf10/html5/thumbnails/21.jpg)
Managing complexity
• What iscomplexity?• Afunction of the number of parts,typesof parts,andnumber andtypesofconnections between the parts.• Structural (difficult todescribe)• Behaviorally (difficult tocontrol andpredict)
• Toohigh complexity will leadtoatleast• Incomprehensibility• Gridlock
• ->lossof predictable outputfrominput– ripple effects• ->co-innovation risk(80%x80%x80%=51%)– need toreduce dependencies atthe rightplace
![Page 22: Software Platform Ecosystems - Universitetet i oslo · • Example: creditcard, Vipps, cool photofilters •-> from productsto services –clientsto web-basedservices, softwarebasedmapsin](https://reader033.fdocuments.us/reader033/viewer/2022050213/5f5f2ca17dca993cee7ddf10/html5/thumbnails/22.jpg)
Managing complexity
• Inaplatform ecosystem with numerous actors,complexity mustbecontrolled somehow toreduce riskof gridlocks,unpredictable rippleeffects andco-innovation problems
• ->Architecture• Balancing between control andautonomy• Keeping transaction costs andcoordination cost aslow aspossible
![Page 23: Software Platform Ecosystems - Universitetet i oslo · • Example: creditcard, Vipps, cool photofilters •-> from productsto services –clientsto web-basedservices, softwarebasedmapsin](https://reader033.fdocuments.us/reader033/viewer/2022050213/5f5f2ca17dca993cee7ddf10/html5/thumbnails/23.jpg)
Architecturesolutions toorchestrate
• Partitioning (modularization)– core <->apps - degrees• Creating «autonomous»subsystems
• Tocognitively manageable parts• Blackboxing
• Visibleinformation:what they doandhow tointeract with them• Hidden information:how they work
• Systemsintegration• Developmentactivities coordination between platform owner andapp developers
• Managing dependencies• Minimizing need forcoordination
• Apps mustbeintegrated tothe platform toenable value toend-users• Platform– app integration – uneven development,platform changes – ongoing effort• App – app integration
![Page 24: Software Platform Ecosystems - Universitetet i oslo · • Example: creditcard, Vipps, cool photofilters •-> from productsto services –clientsto web-basedservices, softwarebasedmapsin](https://reader033.fdocuments.us/reader033/viewer/2022050213/5f5f2ca17dca993cee7ddf10/html5/thumbnails/24.jpg)
Architecturesolutions
• Relatively stablecore• Platformarchitecture• Visiblepart:Shared sets of assetsthrough defined interfaces• Hidden:inner functions of theplatform core tomakeinterfaceswork andbehave asthey do
• Dynamicsandvariability inapps->innovation• Microarchitecture
![Page 25: Software Platform Ecosystems - Universitetet i oslo · • Example: creditcard, Vipps, cool photofilters •-> from productsto services –clientsto web-basedservices, softwarebasedmapsin](https://reader033.fdocuments.us/reader033/viewer/2022050213/5f5f2ca17dca993cee7ddf10/html5/thumbnails/25.jpg)
App architecture (microarchitecture)
![Page 26: Software Platform Ecosystems - Universitetet i oslo · • Example: creditcard, Vipps, cool photofilters •-> from productsto services –clientsto web-basedservices, softwarebasedmapsin](https://reader033.fdocuments.us/reader033/viewer/2022050213/5f5f2ca17dca993cee7ddf10/html5/thumbnails/26.jpg)
Possible partitioning of layers
![Page 27: Software Platform Ecosystems - Universitetet i oslo · • Example: creditcard, Vipps, cool photofilters •-> from productsto services –clientsto web-basedservices, softwarebasedmapsin](https://reader033.fdocuments.us/reader033/viewer/2022050213/5f5f2ca17dca993cee7ddf10/html5/thumbnails/27.jpg)
Many possibilities forpartitioning the app
![Page 28: Software Platform Ecosystems - Universitetet i oslo · • Example: creditcard, Vipps, cool photofilters •-> from productsto services –clientsto web-basedservices, softwarebasedmapsin](https://reader033.fdocuments.us/reader033/viewer/2022050213/5f5f2ca17dca993cee7ddf10/html5/thumbnails/28.jpg)
Many possibilities forpartitioning the app
![Page 29: Software Platform Ecosystems - Universitetet i oslo · • Example: creditcard, Vipps, cool photofilters •-> from productsto services –clientsto web-basedservices, softwarebasedmapsin](https://reader033.fdocuments.us/reader033/viewer/2022050213/5f5f2ca17dca993cee7ddf10/html5/thumbnails/29.jpg)
App architecture choices haveconsequences
• Hard,or,impossibletomaximize allpositiveconsequences;always trade-offs between partitioning inside the platform andacross the Internet• Early architecture choices are hardtochange later
• ->creating path dependencies inarchitectures• Some characteristics showupimmediately:
• speed,security,reliability,scalability,testability,andusability• Someatlaterstages:
• maintainability,extensibility,evolvability,andthecapacitytomutateandenvelopadjacentappmarketsegments
• Developersneedknowledgeaboutwhichtypesofapparchitecturesgiveswhichtypesoftrade-offsandadvantages• ->design,notexperiencetoolate
![Page 30: Software Platform Ecosystems - Universitetet i oslo · • Example: creditcard, Vipps, cool photofilters •-> from productsto services –clientsto web-basedservices, softwarebasedmapsin](https://reader033.fdocuments.us/reader033/viewer/2022050213/5f5f2ca17dca993cee7ddf10/html5/thumbnails/30.jpg)
Platformarchitecture
• Inpractice,irreversible• ->havetostick with early choices andtheir consequences
• Desirableproperties• Simple;defined interfaces,functionlity etc.• Resilient;notbreaking the ecosystem upon app failure• Maintainable;minimizing consequences of local changes• Evolvable;balancing between stability/control of interfaces andautonomy ofinnovation
• But also here,trade-offs.
![Page 31: Software Platform Ecosystems - Universitetet i oslo · • Example: creditcard, Vipps, cool photofilters •-> from productsto services –clientsto web-basedservices, softwarebasedmapsin](https://reader033.fdocuments.us/reader033/viewer/2022050213/5f5f2ca17dca993cee7ddf10/html5/thumbnails/31.jpg)
Moreon modularization andamount ofmodularity• Monolithic versusmodular• Noteither or– rather acontinuum between the two extremes,wheremostliesinbetween
• Some important aspects:• Division of work among several organizations/actors
• Emergent properties• Dependencies among modules isrestricted todefined interfaces• Need tobecompliant only tointerface specifications• Possible performance sacrifications
![Page 32: Software Platform Ecosystems - Universitetet i oslo · • Example: creditcard, Vipps, cool photofilters •-> from productsto services –clientsto web-basedservices, softwarebasedmapsin](https://reader033.fdocuments.us/reader033/viewer/2022050213/5f5f2ca17dca993cee7ddf10/html5/thumbnails/32.jpg)
Balancing needs andimplications
![Page 33: Software Platform Ecosystems - Universitetet i oslo · • Example: creditcard, Vipps, cool photofilters •-> from productsto services –clientsto web-basedservices, softwarebasedmapsin](https://reader033.fdocuments.us/reader033/viewer/2022050213/5f5f2ca17dca993cee7ddf10/html5/thumbnails/33.jpg)
Balancing needs andimplications
![Page 34: Software Platform Ecosystems - Universitetet i oslo · • Example: creditcard, Vipps, cool photofilters •-> from productsto services –clientsto web-basedservices, softwarebasedmapsin](https://reader033.fdocuments.us/reader033/viewer/2022050213/5f5f2ca17dca993cee7ddf10/html5/thumbnails/34.jpg)
What isin,what isout?
• High-reusability functionality• Generic functionality• Stablefunctionality• Interfacesintegralpartsof the platform
• Highuncertainty functionality – out
• But also in:• Forattractiveness• Expectation fromend-users
![Page 35: Software Platform Ecosystems - Universitetet i oslo · • Example: creditcard, Vipps, cool photofilters •-> from productsto services –clientsto web-basedservices, softwarebasedmapsin](https://reader033.fdocuments.us/reader033/viewer/2022050213/5f5f2ca17dca993cee7ddf10/html5/thumbnails/35.jpg)
Theinterfaces
• Standardization• Stability• Versatility• flexibility instandards• highly dependentfunctionality stays inthe platform
• Openness• who can participate
![Page 36: Software Platform Ecosystems - Universitetet i oslo · • Example: creditcard, Vipps, cool photofilters •-> from productsto services –clientsto web-basedservices, softwarebasedmapsin](https://reader033.fdocuments.us/reader033/viewer/2022050213/5f5f2ca17dca993cee7ddf10/html5/thumbnails/36.jpg)
DHIS2asaplatform ecosystem?
• Howdoyour developed apps relate toplatform architectures asdescribed?• Dothe architectural choices inyour app (together with the DHIS2)imply anything forfurther development andevolvement of your app,andinrelation tothe DHIS2core• Dependencies – loose coupling• Modularization• Usage of APIs• Placement of functionality andlayers
![Page 37: Software Platform Ecosystems - Universitetet i oslo · • Example: creditcard, Vipps, cool photofilters •-> from productsto services –clientsto web-basedservices, softwarebasedmapsin](https://reader033.fdocuments.us/reader033/viewer/2022050213/5f5f2ca17dca993cee7ddf10/html5/thumbnails/37.jpg)
Platformvs application vs Informationinfrastructure