Lupapiste an interactive service for citizens

Size: px

Start display at page:

Download "Lupapiste an interactive service for citizens"

Randolf McKinney
10 years ago
Views:

1 Senior Software Designer Timo Lehtonen Lupapiste an interactive service for citizens with HTML 5 JS + Clojure + MongoDB Nääsvillen oliopäivät

2 Top 100-list of Javala: Gamification - apply game-like features to a (often boring) non-game thing.

4 2012 Solita an ICT company from Nääsville Finlayson 2012: Copyright: Tampereen kaupungin kuva-arkisto Finlayson 1962: Thousands of people in manufacturing business 200 people manufacturing Online businesses, BI solutions, ERP systems,

1962: Thousands of people in manufacturing business 200

5 Solita has one value: Care

10 ERP Source: levikintarkastus.fi

11 Customer: environmental administration (Ympäristöministeriö) Released: in march 2013.

12 Aloitus

13 Aloitus Aamulehti Lupapiste handles 16 permit types in 20 pilot municipalities in the first phase

14 Keynote by Cockburn at Oliopäivät 2008

15 Haikala, I., and J. Märijärvi. "Ohjelmistotuotanto. 11. p." Jyväskylä: Gummerrus Kirjapaino Oy (2006).

16 Haikala, I., and J. Märijärvi. "Ohjelmistotuotanto. 11. p." Jyväskylä: Gummerrus Kirjapaino Oy (2006). A similar circle of do, make a theory, do (fail?) again! Pekka Abrahamsson at Oliopäivät 2012: Be ready to fail. Create a theory. Pasi Kovanen, Jarkko Järvenpää, Vincit at Oliopäivät 2012: try, measure and learn, try again

17 Keynote by Cockburn at Oliopäivät 2008

18 Keynote by Cockburn at Oliopäivät 2008

22 Application Architecture POST /rest/command: { command : add-comment applicationid : 123 text : Autotallin räys } Command MongoDB Clojure back-end MongoDB

23 Application Architecture POST /rest/command: { command : add-comment applicationid : 123 text : Autotallin räys } Command MongoDB Clojure back-end

24 Application Architecture POST /rest/command: { command : add-comment applicationid : 123 text : Autotallin räys } { ok : true } Command Clojure back-end MongoDB

25 Application Architecture POST /rest/command: { command : add-comment applicationid : 123 text : Autotallin räys } { ok : true } GET /rest/application Command Clojure back-end MongoDB

26 Application Architecture POST /rest/command: { command : add-comment applicationid : 123 text : Autotallin räys } { ok : true } GET /rest/application Command Clojure back-end MongoDB

27 Application Architecture POST /rest/command: { command : add-comment applicationid : 123 text : Autotallin räys } { ok : true } GET /rest/application Command Clojure back-end MongoDB

28 Application Architecture POST /rest/command: { command : add-comment applicationid : 123 text : Autotallin räys } { ok : true } GET /rest/application Command Clojure back-end MongoDB

30 4 Be slow design the schema first. Design it using a UI demo. A new foundation added at Oliopäivät 2012.

31 Be slow - schema first Schema - Greek word skhēma - shape, diagram, or more generally plan. Source: Uusi sivistyssanakirja freely translated 4 Be slow design the schema first. Design it using a UI demo.

32 Be slow - schema first Schema - Greek word skhēma - shape, diagram, or more generally plan. Source: Uusi sivistyssanakirja freely translated 4 Be slow design the schema first. Design it using a UI demo. Plan 1. Lupapiste data model diagram

33 Be slow - Proof the schema with real data Schema - Greek word skhēma - shape, diagram, or more generally plan. Source: Uusi sivistyssanakirja freely translated 4 Be slow design the schema first. Design it using a UI demo. Plan 1b. Data model with explanation.

34 Database schema is a service interface. The only specification that matters.

35 1. Design the schema first. Big Data

36 Then build an app on top of it JSON HTML 5 JS SPA UI Clojure back-end Big Data

37 Then build an app on top of it JSON HTML 5 JS SPA UI Clojure back-end Big Data

38 Then build an app on top of it JSON HTML 5 JS SPA UI Clojure back-end Big Data

39 Then build an app on top of it HTML 5 JS SPA UI Clojure back-end Big Data

40 Then build an app on top of it JSON HTML 5 JS SPA UI Clojure back-end Big Data

41 Then build an app on top of it JSON HTML 5 JS SPA UI Clojure back-end Big Data

42 Then build an app on top of it HTML 5 JS SPA UI Clojure back-end Big Data

43 Then build an app on top of it JSON HTML 5 JS SPA UI Clojure back-end Big Data

44 Then build an app on top of it JSON Int 1 Int 2 Int 3 HTML 5 JS SPA UI Clojure back-end BI Big Data

45 Then build an app on top of it JSON Integration 1 Integration 2 HTML 5 JS SPA UI Clojure back-end Big Data

46 Then build an app on top of it JSON Integration 1 Integration 2 Integration 3 HTML 5 JS SPA UI Clojure back-end Big Data

47 Then build an app on top of it JSON Integration 1 Integration 2 Integration 3 HTML 5 JS SPA UI Clojure back-end Big Data

48 Then build an app on top of it JSON Integration 1 Integration 2 Integration 3 HTML 5 JS SPA UI Clojure back-end Big Data

49 Then build an app on top of it JSON Integration 1 Integration 2 Integration 3 HTML 5 JS SPA UI Clojure back-end Big Data

50 Then build an app on top of it JSON Integration 1 Integration 2 Integration 3 HTML 5 JS SPA UI Clojure back-end BI Big Data

51 Then build an app on top of it JSON Integration 1 Integration 2 Integration 3 HTML 5 JS SPA UI Clojure back-end BI Big Data

52 Then build an app on top of it JSON Integration 1 Integration 2 Integration 3 HTML 5 JS SPA UI Clojure back-end BI Database Relational database has a schema. It has a plan with constraints.

53 Then build an app on top of it JSON Integration 1 Integration 2 Integration 3 HTML 5 JS SPA UI Clojure back-end BI Database Relational database has a schema. It has a plan with constraints.

54 Then build an app on top of it JSON Integration 1 Integration 2 Integration 3 HTML 5 JS SPA UI Clojure back-end BI Database Relational database has a schema. It has a plan with constraints.

55 Then build an app on top of it JSON Integration 1 Integration 2 Integration 3 HTML 5 JS SPA UI Clojure back-end BI Database Relational database has a schema. It has a plan with constraints.

56 1. The society has constraints, because people make errors You can not build a sauna everywhere, because its unsafe of would ruin the beautiful lake scenes 4 Be slow design the schema first. Design it using a UI demo. 2. Use database schema with constraints, because people make errors You cannot refactor data model field names easily, so use a schema and a validator to prevent future errors 3. Then build an app on top of it

57 Choose any technology to get from A to B - cycle or sail. or swim :) B A

58 Thank you Questions, comments? Feedback:

TDAQ Analytics Dashboard

14 October 2010 ATL-DAQ-SLIDE-2010-397 TDAQ Analytics Dashboard A real time analytics web application Outline Messages in the ATLAS TDAQ infrastructure Importance of analysis A dashboard approach Architecture