ADM + The Ball + OIP Session with Aalto Global Impact

- Brief history of ADM to The Ball - Basics of The Ball

- Now and near future & business cases

Acronyms to be used

• Open Innovation/Collaboration Platform = OIP

• Aalto Global Impact = Aalto

• Finnish Public Sector = ”JulkICT”

Incremental + Disruptive Innovation = Rare Breed

• No compromises

• Side-by-side with today’s way of doing – ADM is a method, not a tool, framework nor library

• If you compare with existing – stay focused – It sounds so familiar, its easy to forget the

breakthrough that makes the difference

ADM TO CREATE THE BALL History summary of ADM to create ”The Ball”

ADM Was Born to solve software developer interchangeability

• Practical solution in place applicable required

– No additional tooling allowed, no additional anything – Everywhere available: XML + T4 Template Code Generator

• Strict technical and business constraints to meet

– Had to match the reference code as if it was ”human created” – Had to justify itself with close-to-immediate ROI

• Solved by raising the level of abstraction and using incomplete automation (= no compromise) – Replacing manual code guidances with manually maintaned

automation – driven from higher level of abstraction

Automation was always there

• Today’s software development makes simple things

complex – when trying to reduce manual labor – Various libraries, frameworks, even treated as separate

”ecosystems” with zero real reusability – Technical ”binary-level” constraints kill the reusability

• Example: Crossplatform mobile development

– Identical interfaces (buttons with meanings and screens) – Identical application logic – Why the same app has to be rewritten multiple times?! – Why is it so difficult to apply user centered design?!

History summary

• July 2009 – Control by manual guidance for code structures – data separate from logic – Effectively in action by the end of 2009 – Clear results

• August 2010 – Tooling Breakthrough – Cross Platform Targeting Enabled – ”This will change everything” realization

• Spring 2011 – Concrete concept structures – Multiplatform tooling, demonstrations, modular distribution implemented

• Fall 2011 – Starting to go public, connections to research – TechInd, Microsoft, connections to various groups

• Dec 2011 – Jan 2012 – ”The Ball” technically built (sparred by TIVIT Cloud Software Program)

• Spring 2012 – the final realization of ”We’re done” – ”The Ball” name – ”The Ball” growing to full ecosystem model cover everything

THE BALL BASICS What is The Ball, Theoretical Fundamentals, Incremental Disruption

Basics

• What is The Ball?

– It’s abstract concretization – digestible explanation

• Information Theoretical Fundamentals – Don’t think of ICT, nor data – Real world work and doing is processes the relevant

results are information

• Current ICT Incremental and Disruptive Aspects – ADM justifies itself in most ICT investments – “Pay what you eat for” – You’re in “The Ball”!

... For Software Development

• Information in the ball is of different levels of abstraction

– Software production is based on ”normal people input” – Think autogenerated reports vs. manual documents – Think combinating same base data in different ways in reports

• Modules can be complete or incomplete – Think of API/SDK/Framework guidance vs. complete features,

applications and systems

• Platform dependencies disappear, openess is required – It is inavoidable, technical and business (buyer) requirement

Incremental Step Justification

• Any SDK/API/Library reference benefits greatly

– Developer experience, cross platform

– Think of existing ”ecosystem” drive to lure developers

– In-house proprietary as well

• Buyers (no ICT-core business) have no reason not to require ADM-implementation

– Requiring open-source for joint orders

• It looks like ”normal” development

– ... but it’s ”The Ball” right from beginning

NOW AND NEAR FUTURE Business opportunities, role requirements

Role definitions

• Software Architect = Architect

• Software Requirements Designer = Designer – UCD works here

• Technical Software Developer (Coder) = Developer

• Information Architect = Modeler – UCD works also here

– Information architects are of key value in ”The Ball”

Immediate Big Case

• Aalto OIP instance opportunities

– Development of the instance and its clones

• Build new business on top of the OIP instance

Incremental (ADM) Cases

• ”The Ball” instance cases • JulkICT Joint Open-Data (co-op with jhsmeta.fi) • JulkICT Advanced Joined Architectures

– Concrete interest in Ministry of Finance

• Application Lifecycle Management – Co-operation with Microsoft, built case for JulkICT

• Cross-platform mobile/game development • User Interface/Information Modeling

– For UCD and for real world process and product modeling

• Embedded Systems Development Control – Integration with back-end systems => market to stay

• Easy-catch opportunities: 3D CAD automation to AR, 3D Printing

YOUR BUSINESS in the ecosystem

• What service do you provide? – How does it fit in, how do you differentiate? – Non – ICT applies here as well; OIP is all about non-ICT – Combination of Infrastructure (software library) and usage (information model), such as

OpenStreetMap

• Above ”The Ball” services – Information management, UCD, processes

• Instance Services – Connection knots, coordination of businesses/intresses – Integration services between the instances

• Below ”The Ball” services – (Hardware) Infrastructure

• Lot of opportunities open for interest group coordination in The Ball!

Foreseeable Instances

• Aalto OIP clones – Focus on cross-organizational collaboration

• Caloom – Focus on local services of any kind – ”Cyberspace” applies here as well

• ”UBIM” Instances – each for every organization (JulkICT and Private)

• Finnish Software Enterpreneurship instance(s) • Embedded software instance(s) • Open-source associations’ instance(s)

Crisis Collaboration Platform

What do you need for a new instance?

• Cloning existing is simple as-is – Much easier than cloning an os project today

• For fresh tech platform – developers – Can add new tech platform backdated

• If there is not existing one it needs to be built – All reusability applies, only the missing parts need

to be built

Incremental Roadmap Exists

• Example: UCD to replace Use Cases

• From ADM-abstractions to ecosystem

• How do you differentiate now, how do you differentiate tomorrow?

Example: UCD to replace Use Cases in an ONGOING project

Collaboration

Value Chains in P2P Development

Thank You!

• Email: kalle.launiala@citrus.fi,

jeroen@caloom.com • Coordination in LinkedIn Open Groups:

– ”The Ball – The Information Ecosystem” – ”Inclusive Business” - for Aalto Concrete Instance

• ADM Tech Blog (not structured, contains technical details and facts) – http://abstractiondev.wordpress.com – Better to start from LinkedIn Groups!