System Introspection for System Analysis on Mobile Devices

More documents

Recommendations

Info

List of Tables and Listings4.1 Typical stanza <strong>for</strong> a message - The message stanza holds theattributes <strong>for</strong> the sender and the recipient. The text to be sendis placed inside a body element. . . . . . . . . . . . . . . . . . . 196.1 Example of the XMPP configuration in the XML configurationfile on the probe - ServerIP and ServerPort determinethe address of the communication server. ServerAccount andPassword are used to define the account used <strong>for</strong> the probe. . . 356.2 Example of the view configuration on the client - Each componenthas a unique name, a corresponding element on the probeand a local class name. . . . . . . . . . . . . . . . . . . . . . . . 446.3 Example layout <strong>for</strong> the laser data view - Each layout uses XMLelements with attributes to create the view. . . . . . . . . . . . 4773
AppendixUse CasesUse Case 1: Connecting to the probeDescription The client connects to the probe. Once the connectionis established the status screen is displayed. If an erroroccurs the client returns an error messagePrimary Actor ClientSecondary Actor ProbeBasic Flow 1. Client initiates connection process.2. Client establishes connection to probe.3. Probe adds client to the list of connected clients.4. Probe sends acknowledge message to client.5. Client switches view to status screen.Extensions 2a. Connection error occurs, client shows error message2b. Timeout occurred, client shows error message5a. Error on switching view, client shows error message74
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 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: 6.10 Main classes of the Java clien
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

Create successful ePaper yourself

Delete template?

Save as template?