Academia.eduAcademia.edu

Figure 23 – uploaded by Duda Matos

See full PDFdownloadDownload figure
Figure 6.4: Ml-Information Broker Engine State Machine

Figure 6 4: Ml-Information Broker Engine State Machine

Related Figures (48)

|| Gathering and Unifying Data
|| Gathering and Unifying Data
List of Figures
List of Figures
Figure 1.1: Example of the client’s received information
Figure 1.1: Example of the client’s received information
e Manual System - Creation, modification and maintenance of contents will be made . The core informa-
e Manual System - Creation, modification and maintenance of contents will be made . The core informa-
Figure 2.1: Google Earth’s tremendous amount of available information in London,UK
Figure 2.1: Google Earth’s tremendous amount of available information in London,UK
Figure 2.3: Simple schematic for a Data Warehouse
Figure 2.3: Simple schematic for a Data Warehouse
Figure 2.4: Simple schematic for a Wrapper Mediator
Figure 2.4: Simple schematic for a Wrapper Mediator
Table 3.1: RSS Versions and Recommendations [1]
Table 3.1: RSS Versions and Recommendations [1]
[28], Microsoft .NET Remoting [29], Facebook’s Thrift [30] and CORBA [81]. Figure 3.1: Remote Procedure Calling Mechanism Other RPC analogues found elsewhere are the Java’s Java Remote Method Invocation [27], XML-RPC
[28], Microsoft .NET Remoting [29], Facebook’s Thrift [30] and CORBA [81]. Figure 3.1: Remote Procedure Calling Mechanism Other RPC analogues found elsewhere are the Java’s Java Remote Method Invocation [27], XML-RPC
Table 3.2: Information gathering technologies comparison 3.4 Technologies Comparison
Table 3.2: Information gathering technologies comparison 3.4 Technologies Comparison
Figure 4.1: Main Actors of the Edition Process
Figure 4.1: Main Actors of the Edition Process
Figure 4.4: An example of a content instantiation: two content instances Note that the "Weather Lisbon" is a "pseudo-screen", this is, it’s internal structure is screen-like but it is used as an overlay’. Figure 4.6 presents the usage of the "Weather Lisbon" screen inside a LO screen.
Figure 4.4: An example of a content instantiation: two content instances Note that the "Weather Lisbon" is a "pseudo-screen", this is, it’s internal structure is screen-like but it is used as an overlay’. Figure 4.6 presents the usage of the "Weather Lisbon" screen inside a LO screen.
4.5 Fast Screen Creation/Edition To speed up the production process, the macro template concept was created. A macro template can be
4.5 Fast Screen Creation/Edition To speed up the production process, the macro template concept was created. A macro template can be
The MI-Editor/Ml-Manager is an important separation of concepts: while MlI-Editor serves the editio! properties that are used in various parts of the production line (website, screens and payments). Therefor
The MI-Editor/Ml-Manager is an important separation of concepts: while MlI-Editor serves the editio! properties that are used in various parts of the production line (website, screens and payments). Therefor
Figure 5.5: Using Ml-Manager to modify an editor’s values A screenshot of this application is portrayed in Figure 5.5, where a manager is editing an editor’s proper-
Figure 5.5: Using Ml-Manager to modify an editor’s values A screenshot of this application is portrayed in Figure 5.5, where a manager is editing an editor’s proper-
Figure 6.1: Ml-Information Broker's GUI nformation Broker runs as a background service, being its only visible part a small GUI6.1 and it’s transactions
Figure 6.1: Ml-Information Broker's GUI nformation Broker runs as a background service, being its only visible part a small GUI6.1 and it’s transactions
The usage of these classes are demonstrated ahead, in section 6.5.
The usage of these classes are demonstrated ahead, in section 6.5.
Figure 6.7: Data Set/Output Screen relation of the Broker Service Weather Implementation
Figure 6.7: Data Set/Output Screen relation of the Broker Service Weather Implementation
Figure 6.8: Data Set/Output Screen relation of the Broker Service Events Implementation
Figure 6.8: Data Set/Output Screen relation of the Broker Service Events Implementation
Figure 7.6: Lx1 Screen Production Time Graph Table 7.1 presents the measurements obtained for Lx1 screen production times, and Figure 7.6 presents the
Figure 7.6: Lx1 Screen Production Time Graph Table 7.1 presents the measurements obtained for Lx1 screen production times, and Figure 7.6 presents the
Figure 7.7: Lx2 Screen Production Time Graph Table 7.2 presents the measurements obtained for Lx1 screen production times, and Figure 7.6 presents the Conclusions Lx2 Screens Clearly, on both Lx1 and Lx2 screen measures, the MI-Editor with Macro Template wins over the other two
Figure 7.7: Lx2 Screen Production Time Graph Table 7.2 presents the measurements obtained for Lx1 screen production times, and Figure 7.6 presents the Conclusions Lx2 Screens Clearly, on both Lx1 and Lx2 screen measures, the MI-Editor with Macro Template wins over the other two
Table 7.3: Time consumed when using the developed broker implementations
Table 7.3: Time consumed when using the developed broker implementations
Figure A.1: Thesis Work Planning done at 8/Jan/2008
Figure A.1: Thesis Work Planning done at 8/Jan/2008
B.1 Edition Process Workflow Figure B.1: Edition Process Workflow Diagram
B.1 Edition Process Workflow Figure B.1: Edition Process Workflow Diagram
Figure B.2: Use Cases Diagram on the Edition Process The main responsibilities of the following roles in the Edition Process are (Figure B.2):
Figure B.2: Use Cases Diagram on the Edition Process The main responsibilities of the following roles in the Edition Process are (Figure B.2):
Figure C.1: The DataSet object model A Broker Implementation uses Data Sets (Figure C.1) [42] to output it’s information to the Broker Engine.
Figure C.1: The DataSet object model A Broker Implementation uses Data Sets (Figure C.1) [42] to output it’s information to the Broker Engine.
which, in this case, is the city of Lisbon.
which, in this case, is the city of Lisbon.
Related topics:
Consistency ManagementMultiplayer GamesIiiIlocality awareness
580 California St., Suite 400
San Francisco, CA, 94104
© 2025 Academia. All rights reserved