Use Case Review

1. Use Case Review Sixth face to face meeting May 12th– 14th, 2003 SUN, Grenoble, France WSRP Technical Committee

2. Use cases covered by WSRP v1 • WSRP – Web Services for Remote Portals • WSRP – Portals Sharing Information • WSRP – Content for Portals => seamless integration depends on connection between Portlet and its related website. • WSRP – Wireless Stock Trading Service => much of this depends on the details of the portlet/portal implementations. • WSIA – Supply Chain Aggregation • WSIA – Universal Bank • WSIA – ADA Educational Studies WSRP Technical Committee

3. WSRP – Multimedia Sports Portal • Basic scenario • Aggregator seeks to integrate disparate content sources into a coherent user interface. Example: • Indy car page has sources for: • Driver cam • Driver statistics (race, this year and lifetime) • Car statistics • Course layout • Selecting a driver should: • Display that driver’s cam (if available) • Display that driver’s statistics • Display statistics for the car • Show driver’s position on the course layout • Needs Consumer coordination of portlets. • Needs transparent transient state WSRP Technical Committee

4. WSIA – Syndication of Mapping Service (similar for Travelers Cheque Syndication) • Basic scenario • Mapping service seeks to increase their control over how their maps & related controls are used on client sites such that their UI investment improves user satisfaction with their product. • Move from a URL link for a map (control parameters are in the URL) to a web service with control properties that outputs a map with controls for inclusion as a whole. • Clients desire to indicate where to add markers to the maps … need to stay even after user interactions with map controls • Needs transparent transient state WSRP Technical Committee

5. WSIA – Mortgage Calculator • Basic scenario • Producer offers a mortgage center component Consumer may easily aggregate into their web pages that: • Provides useful functionality to End-Users (e.g. mortgage payments for various parameters) • Needs link to Consumer data for optimal function (e.g. credit score) • Provides links to Producer’s web site for acquiring product information • Desire for Consumer to easily integrate into their own look and feel • Needs transparent transient state WSRP Technical Committee

6. WSIA – Beauty Boutique • Basic scenario • Consumer is an e-Commerce web site that: • Provides access to a specialized provider (cosmetics) • Provider controls branding/experience within space allocated by Consumer • Consumer potentially initializes product or product category for starting user navigation • Consumer’s shopping cart is used on provider’s content • Provider indicates to the Consumer when current user navigation/interaction is complete • Any combination of Consumer/Provider page should be bookmarkable • Needs transparent transient state • Needs Consumer resources • Needs “EndUserInteraction” event WSRP Technical Committee

7. WSIA – Product Configurator • Basic scenario • Producer (manufacturer) offers a configurator for its products • Consumers (retailers) wish to incorporate this configurator with: • Control over look & feel (CSS type control) • Ability to replace branding • Supply initial parameters (e.g. product the user just purchased) • Add price & availability as offered by the Consumer to product descriptions – both tabular and detailed descriptions • Needs ability of Consumer to identify/replace portions of the markup (?) • Needs transparent transient state • Needs logical events (product added to product list) WSRP Technical Committee

8. WSIA – Smart Buyer • Basic scenario • Consumer is an e-procurement application that: • Supports single sign-on to independent supplier systems • Controls access to products on a per product / per user basis • Searches for the lowest price/best availability across multiple suppliers on a per product basis • Suggests alternatives to lower total cost of requisition • Replaces shopping cart functionality of suppliers • Provides persistent requisitions independent of fulfilling supplier • Needs either: • Ability to locate and replace elements (shopping cart) • Consumer resources WSRP Technical Committee

9. WSIA – Financial Charting • Basic scenario • Producer currently has stock plotting software that allows clients to control various portions of the UI. Would like to move to a web service infrastructure that: • Provides for client input of parameters that control the generation of the plot • Allows client to customize look and feel of the resulting plot • Add UI elements for additional symbols • Add controls for date range, scale, etc • Needs std method of identifying places where markup can be inserted WSRP Technical Committee

10. WSIA – Adaptation of Travelers Cheques • Basic scenario • Bank resells a traveler cheque through a syndicated application • Bank would like to adapt choice of payment methods to add ability to pay using debit from the user’s bank account. • Requires collecting additional data => inserted pages into the application’s flow • Requires the ability to insert additional pages in the flow without impacting the overall Portlet operation. WSRP Technical Committee

11. Covered Use cases WSRP Technical Committee

12. WSRP – Content for Portals • Basic scenario • Content provider seeks to: • Provide aggregatable content for use on portal pages • Support user customized appearance on the portal page • Support navigation while on portal page • Support seamless navigation to related web-site • Support same user customization on related web-site • Support seamless navigation back to the originating portal page WSRP Technical Committee

13. WSRP – Wireless Stock Trading Service • Basic scenario • Telecom seeks to intermediate for users • Provide real-time, off-line and alert capabilities • Supports many device types • Provider seeks to leverage real-time and off-line capabilities • Multi-modal support important as well WSRP Technical Committee

14. WSRP – Web Services for Remote Portals • Basic scenario • Portal deployment would like to: • Integrate content without development effort • Locate available content using std directory services • Configure caching appropriate for the content provider WSRP Technical Committee

15. WSRP – Portals Sharing Information • Basic scenario • Portal deployment would like administrative control over the publishing and consumption of local portlets to remote portals. • Portlet should be unaware that its content is being sent to a remote portal. • Portlets generating multiple content types should be supported. • Portlets generating content for multiple locales should be supported. • Support for user customization of portlets WSRP Technical Committee

16. WSIA – Supply Chain Aggregation • Basic scenario • Ability to: • Aggregate data from multiple sources • Analyze it in a manner appropriate to the End-User • Generate UI appropriate for the device in use WSRP Technical Committee

17. WSIA – Universal Bank • Basic scenario • International Banking Conglomerate wishes to offer tools/services from each of its subsidiary banks when appropriate (geography, service needed, user to be serviced, …). Example: • Purchases new bank (Mountain Bank) • Mountain has a unique tool for risk analysis on tourist hotels • Universal would like all of its loan officers to use this new tool when reviewing financing for such properties WSRP Technical Committee

18. WSIA – ADA Educational Studies • Basic scenario • Public Official (Congressman) seeks all information relevant to building an argument for tax support of a project (e.g. school for the deaf). • Public information about the issues in general (ADA, deaf schools, …) • Public information about the relevant district (current support for the deaf) • Potentially private information (e.g. where deaf people live within the district) • This conflicts with privacy issues … must be able to resolve them WSRP Technical Committee