service-oriented architecture for mobile applications
DESCRIPTION
TRANSCRIPT
Service-Oriented Architecture for Mobile Applications
Yuri Natchetoi, Viktor Kaufman, Albina Shapiro
SAM@ICSE 2008, V. Kaufman & Y. Natchetoi SOA for mobile applications
Hit or hype?
on mobile phones – purchasing, communications, information and
entertainment – are finally reaching “critical mass”. (iTWire)
Wireless Technology for Social Change... (UN & Vodafone Group)
...99% characterized the contribution made by the use of mobile tech as a positive one (UN survey)PhonepayPlus reveals 40% rise in mobile
complaints (for premium services)
Subscriptions for mobile Internet on the rise, usage low. (Taipei Times)
mobile office and productivity apps will see their market consolidate with few survivors remaining...
premium enterprise-device uses will remain limited. (The 451 Group)
"the future of the mobile handset business will primarily depend on software influence
rather than hardware.“ (CEO S. Ballmer)
enterprise mobile solutions market is relatively new,
companies have yet to realize strong ROI benefits from their spending. (Reuters)
providers are beginning to offer innovative and functionally superior and contemporary solutions. (Reuters)
SAM@ICSE 2008, V. Kaufman & Y. Natchetoi SOA for mobile applications
Think along
OUR SCOPE:
Business mobile applications
Focus on TCO
Focus on Software
OUR MOTIVATION:
What‘s behind the controversial discussion of enterprise mobility?
How much is mobile business software development different from traditional business software development?
Can we „port“ traditional or „mold“ new business onto mobile devices?
OUR AGENDA:
Chosen „mobile“ topics flow into a general picture.
SAM@ICSE 2008, V. Kaufman & Y. Natchetoi SOA for mobile applications
Mobile Peculiarities Reminder
USER EXPECTATIONS = high
BUSINESS USER EXPECTATIONS = higher
MOBILE DEVICES =
limited processing power
occasional connections
limited bandwidth and storage capacity
expensive communication
OUR AGENDA:
Can we leverage existing business solutions? -> PREPRODUCT ANNOUNCEMENT!
Can we overcome listed limitations?
Do we have to invest a fortune in development?
SAM@ICSE 2008, V. Kaufman & Y. Natchetoi SOA for mobile applications
Leverage Existing Business Solutions
We recommend:
Identify business value prior to porting functionality onto mobile devices.
Consider back-end connectivity as one of the most complex and important tasks.
Software life-cycle has to be much more agile than traditionally.
SAM@ICSE 2008, V. Kaufman & Y. Natchetoi SOA for mobile applications
We recommend:
Not to forget a single major requirement
Smart connection management
Efficient compression of transmissions
Information entropy reduction
Pro-active upload of information
Asynchrounous communication
Overcome Device Limitations
SAM@ICSE 2008, V. Kaufman & Y. Natchetoi SOA for mobile applications
We recommend:
Service-Oriented architecture both on the client and on the middleware server
Lightweight services composition
In particular, collaborative services as core and composite services
Descriptive approach to the user interface
Using existing web standards
Low-Cost Serviceability of the Applications
SAM@ICSE 2008, V. Kaufman & Y. Natchetoi SOA for mobile applications
Advantages
<?xml version="1.0" encoding="Unicode"?><scema:root> <schema:tag schema:attribute1=“First text” schema:attribute2=“12”> <subtag xml:lang=“eng”> Another text </subtag> <subtag xml:lang=“fra”>Autre texte </subtag> </schema:tag></scema:root>
Attr.names dictionary:1:schema:attribute12:schema:attribute2
English Dictionary:1:First text2:Another text
French Dictionary:1:Premier texte 2:Autre texte
German Dictionary:1:Erster Text2:Anderer Text
Tags dictionary:1:schema:tag2:schema:subtag3:schema:root
SAM@ICSE 2008, V. Kaufman & Y. Natchetoi SOA for mobile applications
Compressed form
5 1 3 1 4 A 1 2 2 2
In total, 5 bytes; compare to 566 bytes for the example above (in Unicode)
Compression ratio = 50 ~ 100 times
DTD Dictionaries are pre-loaded
only required language dictionary will be sent
It means 50 times more objects could be transferred and stored in cache
root (5)
tag (1)
subtag (2)
Another text(2)
attribute1(3)attribute2(4)
First text(1)12
SAM@ICSE 2008, V. Kaufman & Y. Natchetoi SOA for mobile applications
ECOSPACE SOA-based collaboration
ConferencingShared
workspacesInstant
messagingPresence
Content management
Service Integration (SOA, P2P, client-server)
Activity-based composite collaboration services
Cooperationawareness
Semantic integration
Interoperability
Collaborationservices
BCM voice calls,presence
MS Exchange email, tasks
calendar
Active DirectoryIdentityservice
SAM@ICSE 2008, V. Kaufman & Y. Natchetoi SOA for mobile applications
Examples of Services UI
SAM@ICSE 2008, V. Kaufman & Y. Natchetoi SOA for mobile applications
Can we leverage existing business solutions?
Can we overcome known device limitations?
Do we have to invest a fortune in development?
Some Answers and Outlook
We can do better than that: aggregate the most important information,
provide support on the move, use mobile camera etc.
We can do even more: navigation analysis etc. to pro-actively load and customize data. This is on top of the central business system.
Application development is still more convenient on a desktop computer...
Since the limitations are known, the issues can be largely solved once. Then,
it is a question of flexibility and usability level of the mobile architecture, and
of expertise.
Again, flexible design of all life-cycle phases and lightweight approach significantly reduce efforts of developing new applications.
User expectations will not be fully met, there will be some disappointments: mobile is different.
