BLAISE TEAM PRESENTS

Transcription

1 BLAISE TEAM PRESENTS

2 PRESENTATIONS PRE-CONFERENCE TRAINING

3 AGENDA Why Blaise NG Project History Current State Demos Cloud Computing What s Next?

4 WHY BLAISE NG? Blaise 4.x code technically outdated: Written in Delphi, VB6, C++ Originally designed for 80 s & 90 s hardware: Data storage file-based Single machine approach Focus on low memory usage Technology push Hard to implement new features Fundamental redesign needed

5 FEBRUARY 2007 BCLUB DÜSSELDORF Blaise NG White Paper SWOT analysis Platform discussion Research areas Meta Data Layout Development Environment Compiler Runtime Environment Case Management

6 SEPTEMBER 2007 IBUC ANNAPOLIS White Paper by the BCLUB Technical Working Group on Blaise NG Use of Blaise Today Strengths of Blaise Technical Direction BCLUB involvement (Plan for Success): Documentation Testing Example datamodels Specifications Staying Engaged

7 JUNE 2008 BCLUB LILLE Research Areas Handheld devices Graphical Development Environment.NET based API Language Enhancements WPF Presentation Blaise NG prototype

8 JANUARY 2009 START OF PHASE 1

9 FEATURES New metadata XML format New control centre Third party components New approach to layout WYSIWYG New data entry programs WPF Silverlight

10 JUNE 2009 IBUC RIGA Preview of Blaise NG

11 DECEMBER 2009 CTP RELEASE Community Technology Preview Result of phase 1 User tests Positive reactions Certain items were too hard to find Solutions concept is difficult to understand

12 JANUARY 2010 START OF PHASE 2

13 FEATURES New Rules Engine New Database Storage New Runtime System Control Centre Source Editor Meta Viewer Data Entry Settings Layout Designer Template Designer

14 RULES ENGINE Most functionality present (>90%) Compatible with Blaise 4.x Must be tested extensively

15 DATABASE STORAGE Introduction of Blaise Data Interface files (bdix) Successor of boi files Introduction of a new database format (bdbx) Successor of bdb files SQLite based Support for relational databases Oracle, SQL Server, MySQL, MS Access Ideas are similar to Blaise 4.8 DataLink Trigram support for all types of database Based on n-gram algorithm

16 RUNTIME Service Oriented Architecture Based on Windows Communication Foundation (WCF) Data Entry Service Scalable Stateless Executes rules Maintains interview state Creates interview pages Data Entry Client User interface for interview Performs range checking, but does not execute rules Two versions: Windows Client (WPF) Internet plugin (Silverlight)

17 CONTROL CENTRE Ribbon interface Projects & Solutions Dockable windows Multiple documents, multiple views Translatable

18 SOURCE EDITOR Syntax highlighting Code completion Collapsible regions Code snippets Unicode support Background parser

19 META VIEWER Datamodel view Data Structure view Rules view

20 DATA ENTRY SETTINGS Replacement for Toggles Section in modelib Replacement for settings in Blaise Internet Can be overruled at runtime

21 LAYOUT DESIGNER WYSIWYG PowerPoint interface Preview different resolutions Preview different languages Layout instructions Newpage Grid Masterpage Fieldpane Styles

22 TEMPLATE DESIGNER Templates Pieces of layout XAML based New layout concepts Master pages Field panes Styles Elements Shapes (rectangle, circle, ) Controls (button, input box,...) Containers (grid, stackpanel, border, scrollviewer,...) Placeholders (title, page number, content area, )

23 DEMOS

24 CLOUD COMPUTING

25

26

27 WHAT IS CLOUD COMPUTING? Gartner: Scalable, IT-related capabilities Provided as a service on the internet.

28 WHAT IS CLOUD COMPUTING? A combination of:, A and on the internet

29 You manage You manage You manage Private (On-Premise) Infrastructure (as a Service) Platform (as a Service) Applications Applications Applications Runtimes Runtimes Runtimes Security & Integration Security & Integration Security & Integration Databases Servers Virtualization Server HW Storage Databases Servers Virtualization Server HW Storage Managed by vendor Databases Servers Virtualization Server HW Storage Managed by vendor Networking Networking Networking

30 CLOUD COMPUTING AS XAAS? Infrastructure as a service: IAAS Hardware in the cloud Management by provider Platform as a service: PAAS OS in the cloud Service hosting Relational data storage Software as a service: SAAS Salesforce.com Google Apps Windows Live

31

32 Comput e Comput e Comput e Comput e REASONS TO CONSIDER THE CLOUD On/off Explosive growth Inactivity Average Period Usage Average Usage Time Inactive periods Capacity must be available Time to market could be an issue Time Scalability is crucial Hard to keep up with growth Planning ahead is difficult Sudden peaks Predictable peaks Average Usage Average Usage Time Unexpected peaks Performance issues Anticipation to peaks is very expensive Time Short term / trends Seasonal Complex and overcapacity needed

33 ADVANTAGES OF CLOUD COMPUTING Costs Hosting up to 7 times cheaper than on-premise Reachability Cloud application mostly web(service)-based Scalability Unlimited storage space Unlimited computing power Elasticity

34 ADVANTAGES OF CLOUD COMPUTING Easy entry No initial investment needed for big applications Very low investment risk Safe data storage Backups in multiple data centers Cloud vendor dependent on customer trust Durable Consumers share energy resources Energy comes from durable resources to lower costs

35 DISADVANTAGES OF CLOUD COMPUTING Legal aspects Centralized data storage Service level agreements not always airtight Sensitive data (financial, military, etc.) Reliability No direct control over incident handling New vendors have to earn consumer trust Vendor lock-in Lack of standards makes provider switching difficult

36 Private cloud Public cloud

37 Quincy, WA Chicago, IL San Antonio, TX Dublin, Ireland Generation 4 DCs +/- 100 International Data Centers Mega DC s cost 500 mln 700 mln each Under construction

38

39 CAB CONTAINERS

40 HOW DOES BLAISE RELATE TO THE CLOUD? Web interviewing getting more popular (costs) Small surveys (<1000 respondents): Single web server Medium surveys (1000 < respondents < ): Web farm Large surveys (> respondents): In reality not possible

41 HOW DOES BLAISE RELATE TO THE CLOUD? Typical web survey patterns: On/Off Sudden peaks Com pu t e Average Inactivity Period Time Usage Inactive periods Capacity must be standby Time to market can be an issue Com pu t e Average Usage Time Sudden peaks Performance issues Hard/Expensive to anticipate on Predictable peaks Com pu t e Average Usage Time Complex capacity planning Inefficient resource usage

42 SCENARIO 1 Single machine Computer Assisted Personal Interviewing Runtime Datafile sent to office

43 SCENARIO 2 Single machine Computer Assisted Telephone Interviewing Runtime Datafile shared on network

44 SCENARIO 3 Computer Assisted Web Interviewing with Silverlight client Runtime Runtime +Data Services Customer Data Center

45 SCENARIO 4 Computer Assisted Web Interviewing in the Cloud Runtime +Data

46 SCENARIO 5 Computer Assisted Web Interviewing via hybrid cloud application Runtime Data Customer Data Center

47

48 WHAT S NEXT This year Finish Phase 2 Testing Next year Start Phase 3 Manipula or Case Management Layout Text enhancements Grouping Deployment Distributed over Server park Runtime: Data Entry Client: more functionality User-defined actions