A predominant obstacle of model based software · PDF fileA predominant obstacle of model...
Transcript of A predominant obstacle of model based software · PDF fileA predominant obstacle of model...
A predominant obstacle of model based software
development – is communication
Karsten Holm,
Head of Consultancy Division, Soft Design A/S
The challenge – the human aspect
• Generating code and applications from models leaving all
the artifacts of the machine language to the machines is
daily life to me. We model databases. We model screens.
We model code structures, and we populate the
structures with logic.
• The challenge is understanding the customer needs,
documenting these, fixating these in time, and securing
that the customer knows what we are doing and what he
gets as the final product.
The challenge – the human aspect
• How do we communicate our model to the originator of
the problem/project? This is a vital point. Without
communication we can not have our model validated nor
extended by the information we might have missed but is
clearly seen by the business stakeholders.
Biography
Karsten Holm
– Bch. Sc. EE
– Head of department at Soft Design A/S
• Soft Design
• Bonnier Publications
• Zürich Financial Services / Center of Excellence Copenhagen
• Soft Design
Soft Design A/S
• Founded 1985.
• Vision of using CASE to create unique competitive software solutions.
• Specifically the CASE tool 2E from Synon - one of the founders, John Leadbetter, found the tool unique and with a huge future potential.
• Slow but steady growth - Today staff of 40+
In traditional approaches, 80% of the time is dedicated to the infrastructure of the application and 20% only to its business dimension (Source: IDC)
The history of 2E and Plex
• Started in 1984 with Synon/2E- a tool dedicated to IBM
System 38.
• 1987 Synon/2E was launched with the IBM AS/400
platform generating Cobol and/or RPG source and DDS
for the database objects.
• 1993 the 2E successor was released as Obsydian.
• 1998 the tools were acquired by Sterling Software and
renamed COOL:2E / COOL:Plex.
• 2000 Sterling was acquired by Computer Associates, CA
and the products were renamed CA2E and CA Plex.
Our contribution: Websydian
• 1998 Soft Design release the first version of Websydian,
adding a runtime element, patterns and abstracts to the
Plex product allowing it to define the client as a browser
using HTML.
• A WML version was also included allowing the
development of WAP applications.
• Patterns for SOAP, XML are also offered.
• Latest we have released patterns and objects for the
development of RIA applications based on the script
libraries of Sencha (Ext JS).
First assumption
Originally we believed model based development was a key
selling point.
We did so for 10 to 15 years.
When selling cars, carbon fiber, aluminum and high tech
materials are busswords and good selling points.
When developing software, ARAD and model based
development are NOT. We are the few believers
My point is:
Model based development will not have a major
breakthrough in main stream industry before we have
convinced opinion makers of its value.
International – Tools (Websydian) America
ADA County
AFG
Angel Works Enterprises
Caraustar
Computer Arts, Inc.
Conn's Appliances, Inc
County of NY
CSC
Data Specialists
Datamatics
Extol Group Inc.
First Data Corp.
Goodyear Tire & Rubber
Gulfstream Aerospace
Hubbell Power Systems
IBM Global Services
Interamericana
Knovalent
Lincoln Investment Planning
Louisiana-Pacific Corporation
Marianas Information Technology
Corporation
McLanes Advanced Technologies
Medical Mutual Liability Insurance
Mennonite Mutual Aid
North American Stainless
Patient Focus Systems
ReadyPac Produce
RFID
Silocaf of New Orleans
State of Illinois Capital Development Board
Texas A & M University
United Heritage Mutual Life
Austria
Birner
Hannover Insurance
NIIT Technologies
Silhouette
Belgium
IBS
Bermuda
BF&M Insurance Group
Canada
Royal Bank of Canada
Winnipeg Transit
Chile
Distribucion Y Servicios
Mutual de Seguros de Chile
Croatia
DUKAT
Denmark
Bonnier Magazine Data A/S
FDC
De forende Dampvaskerier A/S
Dana
Dania Trucking A/S (Mærsk)
Danpot A/S
Dansikring A/S
Dansk Shell A/S
DHL
Euler Hermes
KODA
Kommunekemi
Lærerstandens Brandforsikring
Nomeco
Nordfrim
Novasol
Sanistål
Ecuador
Diners
Seguros Equinoccial
Finland
Iptor Oy
NCC Rakennus OY
OY Karl Fazer
Yrittäjäin ATK palvelu
France
Alain Manoukian
BCBG Max Azria Group Inc.
Gessi/Gecina
IN Concept
Le Club Createurs De Beaute
Peugeot - Sofira
Prudence Creole
Germany
All About Software Gmbh
Carat
Chrysler
Euronics Deutschland eG
Harry Brot
NBV UGA
NIIT Technologies
Praktiker
Straton IT-Consulting
T-Systems
Hong Kong
Chinese Estate Limited
Iceland
Vigor
India
NIIT Technologies
Israel
Maccabi Healthcare Services
Italy
Bennet SPA
COMUNE DI BAGNO A RIPOLI
Mondo Software
Licosa
Nova System Engineering
Isle of Reunion
Foucque
Jamaica
Computer Infinity
Japan
BCC
HI Technology
Takaya Corp.
Mexico
AMUCSS
IDEE
New Zealand
ISA
MCK Metals Pacific
Netherlands
Alcredis
Docra Management & Agency
Dutch Missing Persons Web Site
Koninklijke Gazelle BV
LeasePlan (NL)
Synobsys
Vereniging Kamers van Koophandel
Norway
Apollo
Oslo Forsikring
TONO
Poland
Bank Zachodni WBK
Softbank
Portugal
Maeil Consultores
Puerto Rico
Efco
Slovenia
ZRC d.d. Trbovlje
South Africa
Axiom
Columbus Stainless
SPAR
Spain
APEMSA
Sweden
Agria
Aller
Datakonkret AB
Iptor Konsult
Kappa Kraftliner AB
KP Pension
Resurs Bank
Stim
Sydved
Switzerland
ANTARES Informatik AG
CM First AG
Delta Logic AG
Electrolux
F+L/ASC
Hapimag Verwaltungs-und
Vertriebsgesellschaft HAVAG AG
Karger
NIIT Technologies
PanGas
United Kingdom
Anglia Regional CO-OP Soc
Domestic & General
Flying Start Computing
Mortgage Trust
Paragon Group
Platform Home Loans limited
PricewaterhouseCoopers UK
Saga Holding Limited
Salvesen Logistics
Suttons
Touchstone Housing Association
Zurich Financial
Applications
Sanistål - webshop
• 175,000 Items
• > 100,000 Items on stock
• 20,000 recurrent customers
Lærestandens Brandforsikring
• 2,000 millions DKR premium
• 800,000 policies
Until model based development becomes a ”buzzword”
We will stick to ”What we deliver”
- leave the ”How” until asked.
The second assumption
Business analysts, accountants, test and conformity staff…
• We did ER-Diagrams.
• We did Data Flow Diagrams.
• We did Web Flow Diagrams.
They did not “get it”
– and they reverted to the text processing adding even more text to make sure we understood.
The specifications
For many end-users the GUI is the application!
Use cases often describe the how not the what.
Daily rules are described – exceptions come after testing.
Tests are targeting weaknesses of the current system, not
validating concepts and foundation of the new system
Word and Excel persist.
Third assumption – the professionals
Motivation factors
• Modern tools
• Multi layer
• Multi platform
• Current technologies; HTML, XML, SOA, etc.
• Less manual code
• More ’business’, less ’binaries’
Polarized community
Many opponents
• Closed and proprietary
• Inefficient code
• Impossible to maintain
• Generators do not work
Ekkard Kindler was interviewed to Version/2 and received
40+ responses. They were not actually pro.
Our own medicine
Webshops and self-service solutions connect our customers,
clients and members to our applications.
The cloud forces us take the same medicine because now
our applications are no longer locally hosted and
controlled.
There are differences but the big picture remains unchanged.
Trend
• Local development and execution:
Requirements -> Software / Service windows
• IaaS, Hosting: Maintained environment
• PaaS, Platform as a Service
• SaaS, Software as a Service
Requirements > Solutions architecture > Identify provider(s)
SLA Service Level Agreement
• Personalized Software as a Service
Integration
1970 – ’80
Local isolated systems, custom-written for the business
1990 - 2000
On platform integration
Cross platform integration (EDIFACT (’96), XML )
2000 – 2010
Standardization and consolidation on application level (e.g. SAP)
Today
Cloud!
Replication of data (e.g. LDAP), Federation (trusted partners)
Integration
No matter what you model, you need to interact with other
systems.
An easy way of publishing services is required.
An easy way of consuming services from others is required.