B LAISE T EAM P RESENTS P RESENTATIONS P RE -C ONFERENCE T RAINING - - PowerPoint PPT Presentation

BLAISE TEAM PRESENTS

PRESENTATIONS PRE-CONFERENCE TRAINING

 https://oto.cbs.nl/ibuc

AGENDA

 Why Blaise NG  Project History  Current State  Demos  Cloud Computing  What’s Next?

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

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

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

JUNE 2008 – BCLUB LILLE

 Research Areas  Handheld devices  Graphical Development Environment  .NET based API  Language Enhancements  WPF Presentation  Blaise NG prototype

JANUARY 2009 – START OF PHASE 1

FEATURES

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

JUNE 2009 – IBUC RIGA

 Preview of Blaise NG

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

JANUARY 2010 – START OF PHASE 2

FEATURES

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

RULES ENGINE

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

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

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)

CONTROL CENTRE

 Ribbon interface  Projects & Solutions  Dockable windows  Multiple documents, multiple views  Translatable

SOURCE EDITOR

 Syntax highlighting  Code completion  Collapsible regions  Code snippets  Unicode support  Background parser

META VIEWER

 Datamodel view  Data Structure view  Rules view

DATA ENTRY SETTINGS

 Replacement for Toggles Section in modelib  Replacement for settings in Blaise Internet  Can be overruled at runtime

LAYOUT DESIGNER

 WYSIWYG  PowerPoint interface  Preview different resolutions  Preview different languages  Layout instructions  Newpage  Grid  Masterpage  Fieldpane  Styles

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, …)

DEMOS

CLOUD COMPUTING

WHAT IS CLOUD COMPUTING?

Gartner: “Scalable, IT-related capabilities Provided as a service on the internet.”

WHAT IS CLOUD COMPUTING?

 A combination of:

, A and

• n the internet

Private

(On-Premise)

Infrastructure

(as a Service)

Platform

(as a Service)

Storage Server HW Networking Servers Databases Virtualization Runtimes Applications

Security & Integration

Storage Server HW Networking Servers Databases Virtualization Runtimes Applications

Security & Integration

Storage Server HW Networking Servers Databases Virtualization Runtimes Applications

Security & Integration

You manage Managed by vendor Managed by vendor You manage You manage

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

Usage

Comput e Time

Average Inactivity Period

“On/off“

Inactive periods Capacity must be available Time to market could be an issue

Comput e Time

“Sudden peaks “

Average Usage

Unexpected peaks Performance issues Anticipation to peaks is very expensive

Average Usage

Comput e Time

“Explosive growth“

Scalability is crucial Hard to keep up with growth Planning ahead is difficult

Comput e Time

Average Usage

“Predictable peaks“

Short term / trends Seasonal Complex and overcapacity needed

REASONS TO CONSIDER THE CLOUD

ADVANTAGES OF CLOUD COMPUTING

• Hosting up to 7 times cheaper than on-premise

Costs

• Cloud application mostly web(service)-based

Reachability

• Unlimited storage space
• Unlimited computing power
• Elasticity

Scalability

ADVANTAGES OF CLOUD COMPUTING

• No initial investment needed for big applications
• Very low investment risk

Easy entry

• Backups in multiple data centers
• Cloud vendor dependent on customer trust

Safe data storage

• Consumers share energy resources
• Energy comes from durable resources to lower costs

Durable

DISADVANTAGES OF CLOUD COMPUTING

• Centralized data storage
• Service level agreements not always airtight
• Sensitive data (financial, military, etc.)

Legal aspects

• No direct control over incident handling
• New vendors have to earn consumer trust

Reliability

• Lack of standards makes provider switching difficult

Vendor lock-in

Private cloud Public cloud

• +/- 100 International Data Centers
• Mega DC’s cost 500 mln – 700 mln each
• Under construction

Quincy, WA Chicago, IL San Antonio, TX Dublin, Ireland Generation 4 DCs

CAB CONTAINERS

 Web interviewing getting more popular (costs)  Small surveys (<1000 respondents): Single web server  Medium surveys (1000 < respondents < 100000): Web farm  Large surveys (> 100000 respondents): In reality not

possible

HOW DOES BLAISE RELATE TO THE CLOUD?

 Typical web survey patterns:

HOW DOES BLAISE RELATE TO THE CLOUD?

Usage

Com p u t e Time

Average Inactivity Period

“On/Off“

Inactive periods Capacity must be standby Time to market can be an issue

Com p u t e Time

“Sudden peaks“

Average Usage

Sudden peaks Performance issues Hard/Expensive to anticipate on

Com p u t e Time

Average Usage

“Predictable peaks“

Complex capacity planning Inefficient resource usage

 Single machine Computer Assisted Personal

Interviewing

SCENARIO 1

Runtime Datafile sent to office

 Single machine Computer Assisted Telephone

Interviewing

SCENARIO 2

Runtime Datafile shared on network

 Computer Assisted Web Interviewing with

Silverlight client

SCENARIO 3

Runtime Services Customer Data Center Runtime +Data

 Computer Assisted Web Interviewing in the

Cloud

SCENARIO 4

Runtime +Data

SCENARIO 5

Runtime Customer Data Center Data

 Computer Assisted Web Interviewing via hybrid

cloud application

WHAT’S NEXT

 This year  Finish Phase 2  Testing  Next year  Start Phase 3

 Manipula or Case Management

 Layout

 Text enhancements (@A…@Z)  Grouping

 Deployment

 Distributed over Server park

 Runtime:

 Data Entry Client:  more functionality  User-defined actions