Service-Oriented Architecture for Mobile Applications Yuri Natchetoi, Viktor Kaufman, Albina Shapiro
Hit or hype? on mobile phones – purchasing, communications, information and entertainment – are finally reaching “critical...
Think along <ul><li>OUR SCOPE: </li></ul><ul><li>Business mobile applications </li></ul><ul><li>Focus on TCO </li></ul><ul...
Mobile Peculiarities Reminder <ul><li>USER EXPECTATIONS = high </li></ul><ul><li>BUSINESS USER EXPECTATIONS = higher </li>...
Leverage Existing Business Solutions <ul><li>We recommend : </li></ul><ul><li>Identify business value prior to porting fun...
<ul><li>We recommend : </li></ul><ul><li>Not to forget a single major requirement </li></ul><ul><li>Smart connection manag...
<ul><li>We recommend : </li></ul><ul><li>Service-Oriented architecture both on the client and on the middleware server </l...
Advantages <ul><li><?xml version=&quot;1.0&quot; encoding=&quot;Unicode&quot;?> <scema:root>   <schema:tag  schema:attribu...
Compressed form <ul><li>5 1 3 1 4 A 1 2 2 2  </li></ul><ul><li>In total, 5 bytes;  compare to 566 bytes for the example ab...
ECOSPACE SOA-based collaboration Conferencing Shared  workspaces Instant messaging Presence Content   management Service I...
Examples of Services UI
<ul><li>Can we leverage existing business solutions? </li></ul><ul><li>Can we overcome known device limitations? </li></ul...
Thank you! [email_address] [email_address]
Upcoming SlideShare
Loading in …5
×

Service-Oriented Architecture for Mobile Applications

1,096 views
943 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,096
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
33
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • We follow the Ecospace project approach. We talk about core and composite services. Existing Collaborative Web Services for E-mail, Instant Messaging or User Management have proprietary protocols and APIs. In our approach, we wrap them by means of proxy components, which provide the core Collaboration Web Services. The composite Web Services, which orchestrate the Core Services using workflow process scripts, facilitate more complex interactions between users.
  • If you are interested in more details or in live demonstration – leave us your business card or send an email to yuri.natchetoi@sap.com or viktor.kaufman@sap.com
  • Service-Oriented Architecture for Mobile Applications

    1. 1. Service-Oriented Architecture for Mobile Applications Yuri Natchetoi, Viktor Kaufman, Albina Shapiro
    2. 2. 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) &quot;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)
    3. 3. Think along <ul><li>OUR SCOPE: </li></ul><ul><li>Business mobile applications </li></ul><ul><li>Focus on TCO </li></ul><ul><li>Focus on Software </li></ul><ul><li>OUR MOTIVATION : </li></ul><ul><li>What‘s behind the controversial discussion of enterprise mobility? </li></ul><ul><li>How much is mobile business software development different from traditional business software development? </li></ul><ul><li>Can we „port“ traditional or „mold“ new business onto mobile devices? </li></ul><ul><li>OUR AGENDA: </li></ul><ul><li>Chosen „mobile“ topics flow into a general picture. </li></ul>
    4. 4. Mobile Peculiarities Reminder <ul><li>USER EXPECTATIONS = high </li></ul><ul><li>BUSINESS USER EXPECTATIONS = higher </li></ul><ul><li>MOBILE DEVICES = </li></ul><ul><li>limited processing power </li></ul><ul><li>occasional connections </li></ul><ul><li>limited bandwidth and storage capacity </li></ul><ul><li>expensive communication </li></ul><ul><li>OUR AGENDA: </li></ul><ul><li>Can we leverage existing business solutions? -> PREPRODUCT ANNOUNCEMENT! </li></ul><ul><li>Can we overcome listed limitations? </li></ul><ul><li>Do we have to invest a fortune in development? </li></ul>
    5. 5. Leverage Existing Business Solutions <ul><li>We recommend : </li></ul><ul><li>Identify business value prior to porting functionality onto mobile devices. </li></ul><ul><li>Consider back-end connectivity as one of the most complex and important tasks. </li></ul><ul><li>Software life -cycle has to be much more agile than traditionally. </li></ul>
    6. 6. <ul><li>We recommend : </li></ul><ul><li>Not to forget a single major requirement </li></ul><ul><li>Smart connection management </li></ul><ul><li>Efficient compression of transmissions </li></ul><ul><li>Information entropy reduction </li></ul><ul><li>Pro-active upload of information </li></ul><ul><li>Asynchrounous communication </li></ul>Overcome Device Limitations
    7. 7. <ul><li>We recommend : </li></ul><ul><li>Service-Oriented architecture both on the client and on the middleware server </li></ul><ul><li>Lightweight services composition </li></ul><ul><li>In particular, collaborative services as core and composite services </li></ul><ul><li>Descriptive approach to the user interface </li></ul><ul><li>Using existing web standards </li></ul>Low-Cost Serviceability of the Applications
    8. 8. Advantages <ul><li><?xml version=&quot;1.0&quot; encoding=&quot;Unicode&quot;?> <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> </li></ul>Attr.names dictionary: 1:schema:attribute1 2:schema:attribute2 English Dictionary: 1:First text 2:Another text French Dictionary: 1:Premier texte 2:Autre texte German Dictionary: 1:Erster Text 2:Anderer Text Tags dictionary: 1:schema:tag 2:schema:subtag 3:schema:root
    9. 9. Compressed form <ul><li>5 1 3 1 4 A 1 2 2 2 </li></ul><ul><li>In total, 5 bytes; compare to 566 bytes for the example above (in Unicode) </li></ul><ul><li>Compression ratio = 50 ~ 100 times </li></ul><ul><li>DTD Dictionaries are pre-loaded </li></ul><ul><li>only required language dictionary will be sent </li></ul><ul><li>It means 50 times more objects could be transferred and stored in cache </li></ul>root (5) tag (1) subtag (2) Another text(2) attribute1(3) attribute2(4) First text(1) 12
    10. 10. ECOSPACE SOA-based collaboration Conferencing Shared workspaces Instant messaging Presence Content management Service Integration (SOA, P2P, client-server) Activity-based composite collaboration services Cooperation awareness Semantic integration Interoperability Collaboration services BCM voice calls, presence MS Exchange email, tasks calendar Active Directory Identity service
    11. 11. Examples of Services UI
    12. 12. <ul><li>Can we leverage existing business solutions? </li></ul><ul><li>Can we overcome known device limitations? </li></ul><ul><li>Do we have to invest a fortune in development? </li></ul>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 lif e-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.
    13. 13. Thank you! [email_address] [email_address]

    ×