Application combined v12

Pini Cohen and Einat Shimoni’s work Copyright@2015
Do not remove source or attribution from any slide, graph or portion of graph
Enterprise applications & development
for the new-generation employee
1
Winning the applications game

2
Welcome your new-generation employees
N

3
Their expectations are no less than consumers’!
Where can I find the
enterprise app-store?
What do you mean
“we don’t have
enterprise search”?
I prefer self service than
calling the help desk
I need a dropbox for
my documents
I need whatsapp for
collaboration
Apps should know
me better
I want smart apps that will
help me determine my
next best step
I am mobile, why
aren’t my apps?
N

4
Don’t try to give them “old-style” applications
Same application for all
No personalization, no context
It’s complicated!
Are you kidding me?
N

UI/UX
Mobile first
Micro-peronalization
Enterprise app-store Next gen.
employees apps
5
Mapping employee journeys
The road to create ‘next-generation employees’ apps
New productivity apps
N

6
Your winning hand?
New-generation employees
don’t necessarily require NEW technologies and tools
but a different packaging, delivery, design and HATMAA
Which cards can you use?
N

7
Card #1: Mapping employee journeys
Employee
journey design
N

Card # 2: UI, UX & Micro-personalization
•USER INTERFACES of today: are all about being as simple as
possible in order to work for as many different people as
possible
•Next generation of USER INTERFACES:
•massively complex algorithms that will micro-personalize
•They will meet individual needs, it won't ask needs are
and it's going to anticipate them, based on data it has
•How will “tools” need to change?
• move from tools that require us to learn how they work, to natural tools that learn to work
the way we do
• move from tools that wait for us to act, to tools that understand context in order
to anticipate and prioritize what matters most
• move from a world where time and place dictate what we can do to a truly mobile world
that revolves around us so that any device can become your device
8
UX & UI
Personalization
N

9
Card #3: New productivity and email experience
New apps for
Productivity
N

Which CIO type are you? Your winning hand for employee engagement is…
10
Conservative CIO
Add UI improvements
to apps
Operational portals or
mobile apps for
specific functions
Modern CIO
Mobility strategy
New email tools
Enterprise appstore
Early adopter CIO
Employee journeys
mapping
Everything is
personalized &
contextual
N

Emotion-Oriented Systems: Magic Moments
11P

Check for suitable process
Select HUB technology
Build initial IoCT based on Hub
Utilize fog computing for critical processes Magic
moments
12
Robust ESB infrastructure
The road to developing magic moment apps
Use HUB in relevant projects
P

State Model
Card # 4: “The hub” basic technology – states and time based BRMS
13
New
Order
New
Order
New
Order
Condition /
TimeEvent
State 1 State 2
Source: Tibco
“The Hub”
P 13

The Hub conceptual architecture
14
Central state machine
that keeps status of
each object and
process events
Example * : If I get 4 ‘bad milkis’ calls from the same area in 4 hours retrieve tracks data. if
you get more 3 ‘bad milki calls in 3 hours send inspection right away. If get 10 in less than
5 hours more calls – report ceo
Management and
monitoring console
Events are
arriving to the
Hub from
outside
Give actions/alerts to other
systems
Rules and patterns* that
change the state,
aggregates, kill/create
events etc according to
events, objects and time.
Input from other
system regarding
rules, patterns
and objects
P

Two ways to look at the current interest in IoCT
We always had sensors connected to IT - in production floors. However:
• Effordable, capable
new sensors
• Better communications
• Big Data analytics and
cloud
Enterprise ‘got envious’ of
consumer IoT capabilities
(“re-Enterprise”)
P

Card # 5: IoT basic layers – the sensor
16Source: http://www.in-jet.dk/en/print.php?type=A&item_id=24
IoT tools and
technologies
P

IoT basic layers – the gateway/aggregator
17Source: http://www.in-jet.dk/en/print.php?type=A&item_id=24
Sends the data from sensor (or many sensors) to the central hub
P

IoT basic layers – Fog computing
18Source: http://www.in-jet.dk/en/print.php?type=A&item_id=24 Srouce: https://www.linkedin.com/pulse/20140822065109-246665791-fog-computing-from-the-center-to-the-edge-of-the-cloud
P

IoT basic layers – the center – Hub, Big Data Analytics
19
Srouce http://www.techrepublic.com/article/datameer-4-0-enables-instant-visualization-in-big-data-analytics/

IoT communication – from sensors to gateway to hub
• Wifi
• Cellular
• Zigbee
• Bluethuth
LE
• More
arriving
20
Srouce:http://www.slideshare.net/aviiandevil7/security-protocols-platform-for-wsn-based-medical-applications-37863943
P

IoT standards
•Why having different standards?
•Different needs: Airplane vs. Street light
•Who is involved:
• Governments
• Industries
• Commercial vendors
21P

Which CIO type are you? Your winning hand for Magic moment technologies is…
22
Conservative CIO
Not sure if there are
appropriate business
processes
Modern CIO
Implementing hub
and IoT in initial
projects
Early adopter CIO
Many business processes are
based on central Hub and IoT
Systems of
engagement
Systems of
Immersion
P

Enforce DevOps metrics
Test Micro-Services
architecture. Increase
agile development
Deploy microservices
vis APaaS
continuous deployment
for web and mobile apps
Next gen.
development &
architecture
23
Build Devops
team. Tests
automation
The road for next generation development & architecture
Utilize APaaS for new projects
All Web Development
P

Card # 6: Modern Web Development – short history
24
Static web
pages
Web server is
“printing”
dynamic html
pages (cgi,
asp, jsp)
Some Ajax
but still web
server is
doing most
of the job
All is done at
the browser
level with JS
frameworks
Communicati
on to
backend via
Rest api
Web
development
Airbnb : how did we get there ?
P

Card # 6: Modern Web Development – short history
25
Static web
pages
Web server is
“printing”
dynamic html
pages (cgi, asp,
jsp)
Some Ajax but
still web server
is doing most of
the job
All is done at
the browser
level with JS
frameworks
Communication
to backend via
Rest api
Web
development
P

The thing with modern Web applications
26
Image processing in the cloud
Because it is REST
Web development is becoming the standard – even for internal PC applications
P

DBMS, Identity,
Messeging
APaaS
IDE, Source Control
Built in processes:
dev to test to prod
Public or private
clouds
Devops
Add ons
components:
BRMS, CEP, IoT
Card # 7: APaaS
APaaS
P 27

28
APAAS
Source: openshift redhat
Source: cloud foundry
P

29
Software development and deployment should be very smooth:
P

30
But in reality:Source:http://dltj.org/article/software-development-practice/
this without mentioning: build the environment, data
refresh, middleware updates, infrastructure updates,
different setup between dev/test/stage/prod etc.
P

Card # 8: Devops: continuous deployment
Enables the business:
Source: http://notafactoryanymore.com/tag/continuous-deployment/
Devops
31

Devops process example:
32
Srouce:https://programmaticponderings.wordpress.com/2013/11/13/building-a-deployment-pipeline-using-git-maven-jenkins-and-glassfish-part-2-of-2/
P

Special care: Devops and test automation
•Test automation is a must for complete DevOps
implementation and it is currently (with internal
politics) the main barrier to DevOps adoption.
•Testing automation ROI is tricky
• # of testing cycles
• Type of test (UI, none UI)
• Changes in the test cases during time. How does the testing automation
technology can support these changes without new coding
• Type and complexity of validation needed
• # of test cases, # of executions per cycle, test coverage,
• Cost of manual tester, automation programmer, tools, servers
Source: http://www.precisetestingsolution.com/wp-content/uploads/automated-300x283.gif
P 33

Card # 9: Microservices architecture: a different point of view
34
Source: http://martinfowler.com/articles/microservices.html
Micro-
services
P

Micros Services advantage and disadvantages
•Benefits:
• Small, easy to understand code base.
• Easy (and efficient) to scale
• Easy to throw away
• Easy to Deploy (goes with continuous
integrationsdeployment)
• Ability to use a different technology stack
• System resilience
•However –
•monitoring a complete process might be a
challenge,
•httpinvoking the service is a waste
•Conclusion – the debate on microservices is
on!!
35
Source: http://eugenedvorkin.com/seven-micro-services-architecture-advantages/ stki modifications
P

36
Agile development reminder
“Best fit” for first agile project:
Total staff of about 6-7 people
End users of project that can be approached once in 2-3 weeks
Not a new area (business and technology)
Bonus: incremental delivery is viable
P

Which CIO type are you? Your winning hand for modern dev&architecture is…
37
Conservative CIO
Only considering APaaS
Just build Devops team
Starting test automation
Agile development few
projects
Modern CIO
First steps in APaaS
mainly on premise
Several auto. tests
Many agile projects
Devops several
processes
Early adopter CIO
All agile development
Utilizing APaaS both on
premise and in cloud
Advanced Devops
processes based on
complete auto. tests
Standardized on
microservices
architecture
P

Use standard best practices
New ongoing
HATMAA tools
Measure HATMAA
“Longtail” apps strategy Assured &
complete
delivery
38
“Cloud-ready” your apps
The road to assure complete delivery of enterprise applications
Super users
N

39
Vanilla – Cloud ERP, anyone?
But it’s not really Vanilla…
There are 30
different “flavors” of
ERP manufacturing
SaaS, specific to
different processes
and verticals

ERP is headed for disruption
•“ERP in a box”:
• Organizations will prefer cloud or cloud-ready applications, even if it means the application is not
tailored to their specific needs
•User interface, easy mobile delivery and employee-engaging applications will be preferred
•Best practices will continue to be used
•ERP cost and staffing will eventually drop!
•3rd maintenance support (i.e, Rimini Street) will be considered for more static and stable
ERP implementations
•Large players are late for the “Core ERP” cloud game (SAP, Oracle, Microsoft) but are
entering NEW applications areas (marketing, CRM, procurement) with cloud-only models
•Smaller players (Netsuite) are growing fast
•Workday (HR and Financials)
40

ERP SaaS???
41
Does hosted ERP = SaaS ERP? No!
• Can you customize it?
• Can you chose when to upgrade?
If the answer is yes, it’s not SaaS

Card # 10: Use Best Practices - Standardize processes
• Use of applications best practices
• “Cloud-ready”
• Innovate in delivery, not in code!
42
Best practices

Rethink
HATMAA
New
HATMAA
Card # 11: NEW HATMAA

Digital Technological
Ongoing Measurable
Engaging

SAP WPB (EPSS)
EPSS
Classroom training EPSS
“On the job”
training

46
The long tail of enterprise applications
Apps get smaller and more modular.
“As organizations push for greater operational
agility, there is a sharp shift toward simpler,
more modular apps”.
Accenture
Most popular topic for STKI clients in 2014
ERP
CRM
KM
Vertical apps
“Others”: Niche apps
Strategy for
“niche
apps”

47
STKI Inquiries 2014

Which CIO type are you? Your winning hand is…
48
Conservative CIO
Use standard best
practices
Modern CIO
Implement SaaS for
suitable processes
For others, “Cloud-
ready” your apps
Define super users to
be used as
benchmark
Early adopter CIO
Almost no major
customizations to code
(effort moves to UX)
Ongoing HATMAA as a CIO
concern
Source: appdynamics

49
So easy to learn, no
need for any training!
Everything is
contextual and
relevant!
Amazing! It’s like the
app knows what I
need to do
Finally – apps that
work the way I do
Nice!
Like
Cool. Easy.
Natural.

50

Application combined v12

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (20)

Andere mochten auch

Andere mochten auch (20)

Ähnlich wie Application combined v12

Ähnlich wie Application combined v12 (20)

Mehr von Einat Shimoni

Mehr von Einat Shimoni (19)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

Application combined v12