System Introspection for System Analysis on Mobile Devices

More documents

Recommendations

Info

6 ImplementationThis chapter gives an introduction to the implementation of the probe andthe client. The first part describes the implementation of the communicationinterface used on all systems developed in the scope of this thesis. The secondpart introduces the implementation of the probe. The last part is split intotwo sub-parts, showing the implementation on the mobile device and on thecommon computer (e.g. laptop or desktop PC). Figure 6.1 gives an overviewof the implemented systems.Figure 6.1: Overview of the system - In this thesis the probe and theclient were implemented. The communication betweencomponents of the robot with elements of the probe isrealized by using the BonSAI interface.Programming LanguageThe programming language of choice is Java 1 programming language. Javaallows object oriented programming, supports threading and is plat<strong>for</strong>m independent.By integrating threading the designed component threads can runin parallel and plat<strong>for</strong>m independence allows to run the client on differentsystems. The different components of the ToBI plat<strong>for</strong>m can be accessed byintegrating the BonSAI interface (see chapter 4.2) which is written in Java.Another benefit is a Java implementation of the library used <strong>for</strong> the XMPPcommunication.1 http://www.webcitation.org/5wuOWGp5I - Java Technology Network by Oracle33
6.1 The Communication InterfaceThe communication interface is essential <strong>for</strong> the transfer of in<strong>for</strong>mation betweenthe probe and the client. All systems must receive and send data thesame way to assure an identically understanding and processing of data exchanged.This means each application must provide the same functionalities<strong>for</strong> the communication with the corresponding systems. Figure 6.2 shows howthe interface is realized and generalized by a concrete implementation. TheCommunicationInterface defines several methods to be implemented by aconcrete communicator used <strong>for</strong> the communication with the communicationserver. The Communicator class is a base class that implements the CommunicationInterfaceand extends the Observable class. The base class holdsessential elements <strong>for</strong> the communication. The attribute sender keeps thename of the sender of an incoming message. The recipientTag is extractedfrom a received message and stored to make a reference <strong>for</strong> the componentthe message is send to. The receivedProperties map holds all propertiesextracted from an incoming message. Extending the Observable class allowselements to observe the communicator <strong>for</strong> incoming messages. On receivinga new message the concrete implementation must trigger a notify-process toallow observers to access the message.Figure 6.2: The communication interface with example implementation- The CommunicationInterface defines theneeded methods <strong>for</strong> the communication with the communicationserver. The Communicator is a base classwith several parameters needed. XMPPCommunicator isa concrete implementation of the interface using XMPPfunctionalities.The XMPPCommunicator is a concrete implementation of the Communicatorclass. To use XMPP <strong>for</strong> the communication, probe and client integrate theSMACK library (see chapter 4.4). The SMACK API offers methods <strong>for</strong> connectingto an XMPP server, login with given credentials and sending messages34
Page 1: Bringing System <s
Page 5 and 6: AbstractSystem <st
Page 7 and 8: output, so each component is offeri
Page 9 and 10: of the system and the decisions mad
Page 11 and 12: created a telelaboratory where two
Page 13 and 14: Like the telelaboratory there is a
Page 15 and 16: with a very high frequency which ma
Page 17 and 18: Due to improving technology the use
Page 19 and 20: Figure 4.1: ToBI platfor</s
Page 21 and 22: Figure 4.3: The architecture behind
Page 23 and 24: Figure 4.5: Typical instant messagi
Page 25 and 26: 5 System DesignThe
Page 27 and 28: Figure 5.2: Message exchange betwee
Page 29 and 30: Figure 5.4: Beacon running between
Page 31 and 32: Figure 5.5: Reading and processing
Page 33 and 34: data and only forw
Page 35 and 36: For example a developer can select
Page 37: Figure 5.13: Principle of tabbed na
Page 41 and 42: 6.2 The Probe - Implementation of t
Page 43 and 44: stop all active processes of the co
Page 45 and 46: is received containing the TAG of t
Page 47 and 48: The selected sensors give a good im
Page 49 and 50: 1 2 4 6 8 Listing 6.2: Example of t
Page 51 and 52: TabConfig - The Status ViewThe TabC
Page 53 and 54: Each view adds a listener to the co
Page 55 and 56: LoginController which also observes
Page 57 and 58: tends the JPanel class. The templat
Page 59 and 60: 7 EvaluationIn the previous chapter
Page 61 and 62: Name Description CharactersSingleli
Page 63 and 64: Figure 7.1: Latency of receiving da
Page 65 and 66: For this thesis only a rough estima
Page 67 and 68: Laptop CPU load without Probe CPU l
Page 69 and 70: 8 ConclusionsIn the context of this
Page 71 and 72: 9 OutlookGiven this new tool its no
Page 74: BibliographyBurrell, A. and A. Soda
Page 77 and 78: 6.10 Main classes of the Java clien
Page 79 and 80: AppendixUse CasesUse Case 1: Connec
Page 81 and 82: Use Case 4: Disconnect from compone
Page 83 and 84: Use Case 9: Sending beacon to keep
Page 85 and 86: Figure 9.4: Latency of receiving da

System Introspection for System Analysis on Mobile Devices

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?