WWW/Internet - Portal do Software Público Brasileiro

IADIS International Conference WWW/Internet 2010NamePreferredContextsDiscoveryDOsPreferredDealingContextsTypeOfBusinessByRegion3.2.2 The TrailM/UbiTrade IntegrationTable 1. Specialized services created in TrailMDescriptionReturns a list with the dealer’s preferred contexts in a trail.Returns a list containing all deal opportunities of dealers that have a desire and/or offerin common based on trail.Returns a list with the dealer’s preferred business conclusion contexts in a trail (forexample, jewelry store, restaurant or train).Returns a list with the type of business by region based on dealers’ trails (for example,shopping).The TrailM/UbiTrade integration was based on the following changes in UbiTrade: (1) we included thesupport to the TrailM services in the Personal Assistant; (2) the Opportunity Consultant inferences became toconsider the dealers’ profiles and the services available by TrailM (described in Table 1).Figure 5 presents the dynamic of the integration. In UbiTrade, the deal opportunities are warned to thedealers according to the events occurrence based on Profile System during their trail. Location Systeminforms the context in which the dealer is to Opportunity Consultant, which identifies the occurrence of oneevent that starts the process (step 1). Opportunity Consultant uses this information, combined with dealer’sprofile and the Reference System, to filter deal opportunities according the reference grade compatible withthe dealer (step 2). For dealers who have the data compatible, Opportunity Consultant matches the profiles,trying to identify the type of opportunity that they are looking for (step 3). In this stage, UbiTrade uses theTrailM services to improve its inferences. Identifying an opportunity, Opportunity Consultant sends anotification to dealers, using the warnings service of the Service Manager component (step 4).Figure 5. Discovery of DOs guided by trails4. PROTOTYPE AND CASE STUDYThis section describes the TrailM and the UbiTrade implementations. Furthermore, it discusses the case studyused to validate the model.4.1 The TrailM and the UbiTrade PrototypesThe TrailM Server prototype was implemented through the Java programming language. The Hibernateframework was used to access the database. The TrailServices layer is based on Web services.The UbiTrade prototype (Franco et al, 2009) was implemented through the C# programming language.The Opportunity Consultant and the Reference System components were designed as Windows services.The Category Tree component and the Profile System were implemented using the Firebird relationaldatabase. The Service Manager was developed using the standard Web service technology. The PersonalAssistant module was developed with .NET Compact Framework and runs on Windows Mobile. Moreover,23