Download
svn platform engineering n.
Skip this Video
Loading SlideShow in 5 Seconds..
SVN Platform Engineering PowerPoint Presentation
Download Presentation
SVN Platform Engineering

SVN Platform Engineering

100 Vues Download Presentation
Télécharger la présentation

SVN Platform Engineering

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. SVN Platform Engineering Kamal Bhattacharya Olha Danylevych Schahram Dustdar Michael zu Muehlen Stefan Tai

  2. Problem statement • Coordination of resources • Humans, business units etc. • How to design a (coordination) platform • Today, the requirements on and properties of a SVN platform are not well known • (Cp. invention of a Web Browser)

  3. Intuition behind SVNs

  4. What is required SVN Platform Programming model (Constructs of SVN; APIs) Infrastructure (Technology stack; Platform architecture)

  5. SVN Platform Dimensions • Structures • Elements and their „mapping“ to platform layers • Scope • Global: SVN around a set of independent participants • Local: SVN around one (core) participant (and its one offering) • Coordination and Control • Centralized vs decentralized / automatic, manual • Degree of coupling • Time • Lifetime of an SVN (and its parts) • „Value“ of (parts of) SVN at a given time, over time • Evolution of an SVN over time

  6. SVN API • Changes on SVNs (weighted?) • Add, remove, modify nodes • Add, remove, modify links between nodes • Delegate • Join, split of nodes • SVN formation / birth • SVN termination / death • Lifecycle of the building blocks ? SVN(t0) SVN(t1) SVN(tn) ... t0 t1 tn Time

  7. Other issues • Constraints • implied from the commitments • Implied from business rules • ... • Governance mechanisms • Compliance • Ethics • Traceability

  8. SVN Building Blocks • Nodes = participants • Goals • of single participants • of the SVN as whole ? • Capabilities of the participants • Links between the participants • Commitments • whole spectrum: not-written agreements, EULAs, SLAs etc • of different levels • SVN controlling/regulation: • metrics and incentives, rewards and penalties • Monitoring and Traceability (optional) • Delegation / referrals • To software services and human based services

  9. Towards the solution • SVN should build an overlay which wires diverse systems/platform services • Manage the state space • Relationship management • How to do that? • Efficient task management

  10. Efficient task management • Task definition (composition / decomposition) • Target selection (centralized / market-based?) • Agreement („binding“ / links) • Execution • Performance, monitoring, audit

  11. .... ?