The slide gives an overview about operations models (IaaS, SaaS, PaaS), compares different software modes (OOTB, Low Code, Custom Solutions) and explains the building blocks of software projects.

1. Textmasterformat durch Klicken bearbeiten
Lorem ipsum Textmasterformat durch Klicken bearbeiten
Zweite Ebene
Dritte Ebene
Vierte Ebene
Fünfte Ebene
1 2 3
Software operations models
Different software approaches
How to implement software
How to choose the right software

2. Textmasterformat durch Klicken bearbeiten
Lorem ipsum Textmasterformat durch Klicken bearbeiten
Zweite Ebene
Dritte Ebene
Vierte Ebene
Fünfte Ebene
Popular “IT as a Service” models
IaaS PaaS SaaS
Infrastructure as a Service Platform as a Service Software as a Service
IaaS delivers remote physical
datacenter infrastructure that
allows users to rent the usage of
infrastructure instead of buying
physical hardware.
IaaS providers typically offer
physical Infrastructure as well as
virtualization for servers, storage
and networking.
Users if IaaS-Services have to
manage the software stack on top
themselves (Operating systems,
middleware, applications,
desktops).
PaaS delivers remote application
development infrastructures and
application environments that allow
developers to build scalable and
hybrid solutions.
Applications built on PaaS inherit the
benefits of cloud architectures, like
scalability or the access to services
that require massive computing
power, like machine learning, IoT or
BigData.
PaaS allows micro-service based
development to help developers
focus on functional enhancements
SaaS represents the ‘classic’ cloud
market that offers managed ready to
run applications.
SaaS applications are likely to be
usable via browser and often do not
require local client installations.
Samples for SaaS are Office365,
Salesforce, Evernote and many other
for almost any purpose.
As everything (operations, storage,
maintenance, support) is managed by
the SaaS vendors it is easy to use this
kind of offering.

3. Textmasterformat durch Klicken bearbeiten
Lorem ipsum Textmasterformat durch Klicken bearbeiten
Zweite Ebene
Dritte Ebene
Vierte Ebene
Fünfte Ebene
Azure as flexible IaaS + PaaS + SaaS platform for SME
AppTier
Availability Set
DataTier
Availability Set
IdentityTier
SQL Server
LOB
Application
Domain
Controllers
SQL AlwaysOn availability group
. . .App 2
VM
App 2
VM
Azure
VirtualNetwork
. . .
VM VM
Availability Set
VM VM
Additional drawing symbols available at http://aka.ms/AzureSymbols
1
2
3
Identity
Tier
Enterprise
DataTier
Active Directory
AppTier
. . .
. . .
To App1
local
OR
=
VPN
Point-to-Site or
Site-to-Site
ExpressRoute
Enterprise
Internet
SQL Server
Windows Server
App1
Dedicatedline
Run two virtual machines as Active Directory
(AD) domain controllers and DNS servers in
Azure and synchronize these services with your
on-premises AD domain controllers. The
application can then authenticate users without
the added latency of connecting to the on-
premises Active Directory.
Connect all your virtual machines in the cloud
into an Azure Virtual Network.
Connect on-premises to the cloud with VPN
over the Internet. For a lower latency dedicated
line use ExpressRoute.
On-premises users now access their
applications in the cloud with no changes to the
user experience.
Package your application into a virtual machine
and deploy it into Azure. Run at least two
copies to provide redundancy in case of failure
or add more to scale out.
Move your data layer to the cloud for the lowest
latency. Take advantage of the SQL Server
2014 AlwaysOn feature to provide redundancy
and failover.
The applications in the cloud and on-premises
can securely communicate and exchange data.
1
2
3
4
5
6
7
Azure connects OnPremise and Cloud
and allows the free decision about the
preferred operation platform for
services.
Even though MS Azure is provided by
Microsoft it is an excellent OpenSource
application stack.

4. Textmasterformat durch Klicken bearbeiten
Lorem ipsum Textmasterformat durch Klicken bearbeiten
Zweite Ebene
Dritte Ebene
Vierte Ebene
Fünfte Ebene
Different software approaches
Out-of-the-Box (OOTB) No Code & Low Code Custom coded solutions
Standard-Software Configuration Frameworks Software-Engineering
Standard-Software Solutions promise
to deliver answers for standard
problems, fair pricing, low risk and
easy implementation even for
complex duties..
Traditional samples are ERP, PPS,
CRM, HR, CAD, Office, financial
systeme etc. that represent legal
standards or industry good practice.
Most of these systems go hybrid or
cloud today and add substantial
value to the PaaS stack in the cloud.
No Code or Low Code solutions try
to close the gap between Standard
Software and Custom coded
solutions.
These solutions promise more
flexibility than standard solutions
and less requirements for
programming or IT-skills than
Custom coded solutions.
Typical representatives of this type of
solution are Workflow-Tools,
Collaboration Tools or Configuration
Frameworks.
Custom coded solutions allow the
creation of everything that can´t be
covered with the left two blocks.
Current PaaS Stacks like MS Azure allow
search driven applications, Micro service
architectures, IoT, BigData, Machine
Learning and more – and it will take
several years until these technologies
will become a natural part of OOTB, No
Code or Low Code solutions.
Custom coded solutions therefore are
the right answer to innovation and
digital transformation.
Standard Frequent Changes Digital transformation

5. Textmasterformat durch Klicken bearbeiten
Lorem ipsum Textmasterformat durch Klicken bearbeiten
Zweite Ebene
Dritte Ebene
Vierte Ebene
Fünfte Ebene
More details on ‘No Code’ and ‘Low Code’
No Code Low Code Workflow & Forms
Flexible Standard Software Configuration Frameworks Rules and User Interaction
No Code solutions offer flexible
configuration options within the
given functionality.
As you can´t add things outside the
box the flexibility is limited to the
configuration options provided by
the software vendor.
A lot of cloud services offer such
abilities today.
Low code applications are built
either from application templates or
from scratch.
The underlying frameworks offer a
wide variety of controls for data
access, navigation and display
control.
To easy logic implementation most
of the frameworks allow at least the
usage of programmed Script-Code.
Workflow & Forms tools help you to
visually design technical workflows with
user interactions.
These tools are often either part of Low
Code solutions or can be combined with
No Code or Low Code solutions to
enhance the scope of capabilities.
The most frequent usage of such tools is
the digital replacement of physical forms
based processes and the controls of
application behavior.
Flexibility on Standards Programming for Non Coders Process and Rule control

6. Textmasterformat durch Klicken bearbeiten
Lorem ipsum Textmasterformat durch Klicken bearbeiten
Zweite Ebene
Dritte Ebene
Vierte Ebene
Fünfte Ebene
More details on ‘Custom coded solutions’
Extensions Integrations Solutions
Feature Enhancements Bridging the gaps Innovate and transform
Extensions enables Software developers
to enhance OOTB Software if the
architecture of the product allows that.
Depending on the underlying software-
stack these extensions can have
different names, like ‘Add-Ins’, ‘Plugins’,
‘Extensions’, ‘WebParts’ etc.
As Extensions run in an existing
Software-Ecosystem and typically focus
on small enhancements, projects are
likely to be small.
Integrating Software to close the gaps
between systems, processes and data
is complex.
To ease the pain the market provides
several integration technologies that
share all one thing: complexity.
If you use integration platform
technologies or develop custom
integrations heavily depends on the
volume and complexity of integrations
to be done.
When it comes to innovation, digital
transformation, bundling of hard- and
software or multi-platform solutions,
there is no shelf to pick the future from.
If you want to transform an idea or a
vision into reality you must become an
innovator to see results.
Custom software is exactly the fuel to
make your visions come true. And
current PaaS-stacks are an enormous
accelerator for your success.
Standard with cream whip Bringing the right things together Software of tomorrow. Today.

7. Textmasterformat durch Klicken bearbeiten
Lorem ipsum Textmasterformat durch Klicken bearbeiten
Zweite Ebene
Dritte Ebene
Vierte Ebene
Fünfte Ebene
How to implement Software
General
Demand
Definition
Business Case
Engineering
Detailed
Requirements-
Engineering
Change-
Management
Technical Engineering
Alternative
Solution
Benchmark
Budget
Allocation
Supplier
Benchmark
Non-functional
Functional
Techn. Tests
Integration
Deployments
Org. /Process
Change
Data
Migration
User
Training
Enduser
Rollout
Operations
Handover
Techn.
Rollout
Helpdesk
Support
Improvement
Process
Enduser
Tests
Building blocks of any Software project (OOTB, No or Lo Code, Custom Development
Prepare
Rollout
Implement

8. Textmasterformat durch Klicken bearbeiten
Lorem ipsum Textmasterformat durch Klicken bearbeiten
Zweite Ebene
Dritte Ebene
Vierte Ebene
Fünfte Ebene
What is inside the functional part?
OOTB No or Low Code Custom development
Aligning standard to reality Prototyping and improving Agile orchestration
Standard-Software delivers 1000% of
features and processes out-of-the box
so you have to carve out the 25- 40%
that you need by configuration or
customizations, if possible.
As you may need 8-10% of features
from outside the standard, you have to
add this by customizations, too.
Typically, you have to integrate and
connect your existing systems, too, so
you need integration work on top.
Business templates in such solutions
are typically not too sophisticated.
You typically start to configure new
things according to your needs very
early.
Major efforts done in such solutions
are dedicated to data modelling,
reporting and charting.
Integrations with other systems are
typically an important part in these
projects, too
Modern software is built in small bricks
that orchestrate small services out of a
huge PaaS stack called hybrid Cloud.
Major efforts done in such solutions are
dedicated to data modelling, algorithms,
forms, rules, reporting and charting as
theses solutions typically start from
scratch.
This kind of projects require massive
knowledge, agile methods, strict
organization and continuous integration
for deployments.
For Vendor Partners only For non-coding IT-Experts For coding IT-Experts

9. Textmasterformat durch Klicken bearbeiten
Lorem ipsum Textmasterformat durch Klicken bearbeiten
Zweite Ebene
Dritte Ebene
Vierte Ebene
Fünfte Ebene
Risk comparison for software projects
OOTB No or Low Code Custom development
Understanding the needs Organizational maturity Business to IT Aligment
A lot of standard software comparisons
end with product feature benchmarks
and miss to identify the real needs and
realistic organizational change
capabilities.
Another major risk are procurement
driven software benchmarks that omit
the fact that the implementation
partners experience, mindset and
ability to collaborate with the internal
project members plays a major role in
success.
With No Code or Low Code solutions
you built solutions exactly like your
organization required it.
Poor requirements engineering often
results in poor software-systems.
Easy configuration lets customers
underestimate the complexity of
software projects and try to let business
people do complex engineering work.
Custom development is about creating
the future, so top of Nodge knowledge
is required.
A frequent risk and fault is staffing
innovation projects with old school
developers.
This kind of projects require massive
knowledge about agile methods, micro
services and continuous integration to
succeed.
Overestimation of Standard Underestimation of complexity Fear of the ‘unknown’

10. Textmasterformat durch Klicken bearbeiten
Lorem ipsum Textmasterformat durch Klicken bearbeiten
Zweite Ebene
Dritte Ebene
Vierte Ebene
Fünfte Ebene
Why standard software is no guarantee for success – important statements
60-80% of all OOTB features
are never used.
30-50% of the 20% used are
customized or custom coded.
Standard software fails to deliver
the “in between” that is mission
critical.
We think that our processes are
pretty standard on a global level.
The details make it difficult to use
OOTB-Software
We couldn´t find a single
OOTB system that covered our
processes in detail. Even
though we are pretty standard.
It it easy to find a solution for a
single pillar. But the challenge is
to build an information network.
Collaboration is no longer limited
to our own employees. We need
solutions that bridge the gaps.
We spent 80 TCHF in consulting to
compare standard software. Finally
we developed the whole thing with
Low Code for less.
OOTB does not reduce the risk
of project failure.
OOTB
Understanding the needs
Standard-Software is great if your
organization is able to use the software
“as is”.
Changing your organization to match
Standardsoftware can make sense if
you implement software apart from
your company USPs.
Once you need to customize standard
software to your needs it is likely that it
is worth to compare the project efforts
with custom solution development.

11. Textmasterformat durch Klicken bearbeiten
Lorem ipsum Textmasterformat durch Klicken bearbeiten
Zweite Ebene
Dritte Ebene
Vierte Ebene
Fünfte Ebene
Which approach fits my needs?
There is no general answer to that question.
Each case has to be investigated carefully as each software choice has heavy influence
on your future working model and your abilities to use, connect and analyze data .
We are here to help you. Ask us.
Rüdiger Gros
CEO EFEXCON AG
T: + 41 44 586 5018
r.gros@efexcon.com
www.efexcon.com
@efexcon