Demo Videos

Videos are grouped as following (preferred to look in this order to understand the whole idea):

The Ball – Developer Tools & API

  • Ground up developer account & tooling preview
  • Focused around creating secure connections from various devices
  • Demonstrating application functionality through web template/app development

The Ball – The Solution Demos

  • Technology preview, early technical feature demonstration focused stuff
  • Starting from scratch, create your account, create categorized content, collaborate
  • Input-Output and Device Connectability for groups and between Ball instances

Smart City Ecosystem

  • The perspective change towards the information ownership of a Citizen
  • New value chains, open ideas, open innovations accelerated
  • Based on “The Ball – The Information Ecosystem” model

The Ball – The Information Ecosystem

  • Information ecosystem explained – in mostly non-technical manner
  • The basics of the ecosystem
  • The business opportunities in the ecosystem

Aalto OIP – The Ball Business Opportunities – slides

Note: This set of slides and videos above are from seminar about Aalto Global Impact’s Open Innovation/Collaboration Platform, that is based on “The Ball” model of information ecosystem.

Semantic Information Universality

  • Information universal nature in ICT
  • Demonstrating implicit semantics in program code
  • Demonstrating role-specific information in software project
  • Soon-to-include demonstrations to integrate in Visual Studio TFS

Videos for Semantics and Universal Automation – Slideset 1

Getting Started with Visual Studio T4

  • Starting from scratch with T4; Hello World and dynamic code evaluation
  • Connection with common web-technologies with template-generators for html
  • T4 back-end explanation; Generating vs. Preprocessing
  • Advanced code and class structures and include files
  • Usage of T4 Toolbox and T4 Editor for XML-Schema-Aware Intellisense
  • Update the model with immediate reflect of the change to T4 intellisense

Using Existing Abstractions

  • End-developer experience is identical regardless of the automation target
  • Developers focus on the implementation that is required, not on plumbing code that requires specific technical detail to get right
  • Reusability (and modifying + reusing) is practically 100%, which makes “using of existing abstractions” the main use case; there is no point for everyone to make their own as sharing possibility is implicit by design

Architecture/Overview of Abstractions

  • How abstractions are located in the filesystem
  • How abstractions are structured overall
  • How abstraction outcome participates in the compilation and build process

Creating New and Modifying Existing Abstractions

  • How abstractions are modified/created effectively with intellisense support on T4
  • What are the basis to modify an abstraction

Multiplatform Native Development Automation

  • Dual IDE (T4 Automation + Native IDE) usage
  • Automating (mobile) client and server from different “ecosystems”
  • Simpler client-server call layer than with traditional library or framework when supporting multiple clients in parallel that require different library each

Automating Documentation and Project Reporting

  • Automating documentation generation
  • Automating project status tracking
  • Enforcing performance requirements

Simplifying and Automating Development for non-Developers

  • Multi-level abstraction overview
  • Various simplifications for n-tier architecture with mobile and web UI clients
  • Simplifying development down to logical extreme

 

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s