System Introspection for System Analysis on Mobile Devices

More documents

Recommendations

Info

present the data and <strong>for</strong> the control of the GUI the Model/View/Controllerpattern (see Freeman et al. (2004), pages 529-546) is integrated. The mainelements are the login view and the overview panel. The overview containspanels <strong>for</strong> in<strong>for</strong>mation about the connection, a list of all available componentthreads and their states and a panel containing the tabbed navigation. Forcontrolling the interaction all windows are using controller classes handlingthe communication in background. Figure 6.10 gives an overview of the mainclasses implemented. For the communication with the probe the communicationinterface is integrated using a concrete implementation of the XMPPcommunicator. Each element of the Java client can observe the communicationinterface and receives incoming messages on notify triggered by the communicator.The ComponentMapper is used <strong>for</strong> matching component threads of theprobe with corresponding views on the client.Figure 6.10: Main classes of the Java client - On successful connectall needed panels are created. The TabHolder createsand controls all panels <strong>for</strong> presenting the componentthreads and the logging cycle.LoginController and Login WindowThe LoginController and the Login view handle the initialization of theconnection to the probe. The Login class creates the GUI with input <strong>for</strong>the communication parameters. Events of the Login view are observed by the49
LoginController which also observes the communication interface <strong>for</strong> incomingmessages. By executing the login process, the LoginController connectsto the communication server and per<strong>for</strong>ms the login with the provided parameters.When the connection is successfully established, the LoginControllersends a connect command to the probe. While waiting <strong>for</strong> the acknowledgmentof the probe a timer checks a flag presenting the state of the connection to theprobe. If the connection to the probe is successfully established the flag isset to be connected and the view gets switched to the Overview. When theacknowledgment is not returned within a defined period, an error message isdisplayed. Figure 6.11 shows the login view.(a) Login <strong>for</strong> the common computer(b) Login executed(c) Message if probe is not reachableFigure 6.11: Starting the Java client - Image a shows the login windowwith the parameters <strong>for</strong> the communication interface.After executing the login process the GUI is inactivatedshown in image b. Image c shows the messagedisplayed when the probe is not reachable.When the connection is successfully established the LoginController createsan instance of the Beacon class. This class uses a timer to send beacons tothe probe with a given frequency. The Beacon listens to the communicationinterface <strong>for</strong> incoming beacons. just like the probe it counts the missing beaconsand stops the client on connection loss. If new beacons are received the beaconcounter is reseted to zero.OverviewController and the Overview WindowThe main part of the Java client is the overview window which presents in<strong>for</strong>mationfrom the probe using different panels. The Overview class creates theTabHolder and the helper panels. Events on the overview window are controlledby the OverviewController. The OverviewController observes the50
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 and 38: Figure 5.13: Principle of tabbed na
Page 39 and 40: 6.1 The Communication InterfaceThe
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: Each view adds a listener to the co
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
show all

System Introspection for System Analysis on Mobile Devices

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

Delete template?

Save as template?