System Introspection for System Analysis on Mobile Devices

More documents

Recommendations

Info

to the probe needs to be wireless. For example this supports remote observationwhile the robot is participating in an experiment. If possible the system mustbe available over the internet. This allows the expert to monitor changes evenif he is not at the local side of the robot.<strong>System</strong> Requirements of the RobotThough the system is attached to the software of a robot, some requirementsare given by the robot itself.Requirement 8:Minimum influence on the robot and inactive when not usedOn the robot a lot of components are executed in parallel. Many of thesecomponents consume resources which are limited by the robots system. Theprobe attached should only use a minimum of the resources available. Whilethe probe is active the normal behavior of the robot should not be influencedby any means necessary. To achieve an minimum influence, the probe shouldonly be active whenever a developer is connected to the probe and deactivatedif not used.Requirement 9:No hard coded connection between robots components and the systemprobeDue to improving technologies the components on the robot can change. Theprobe must capsule the connection reading and controlling components of therobot to make changes on on both sides possible without affecting the wholesystem.<strong>System</strong> Requirements of the ProbeThe probe publishes in<strong>for</strong>mation to observe the robot. It is attached to thesoftware of the robot and uses the resources available.Requirement 10:Observation of components must allow parallelism and multi-userobservationEach component inside the probe should be running on its own thread. Thisoffers parallelism and allows multiple users to observe different in<strong>for</strong>mationqueues.Requirement 11:Well defined communication interface <strong>for</strong> implementing different communicationframeworks11
Due to improving technology the used communication may be replaced lateron. To make the communication exchangeable an interface must be createdthat allows to change the underlying communication framework.<strong>System</strong> Requirements of the ClientThe client displays the in<strong>for</strong>mation published by the probe within differentviews.Requirement 12:Application running with minimized resource usage to save systemresourcesThe resources on a mobile device are limited. The application has to belightweight and should not block the device due to excessive resource usage.For example the battery drain should be reduced by decreasing the neededCPU usage.Requirement 13:Well defined communication interface with same structure then theprobeThe application on the client must use the same communication interface thesystem probe uses. This ensures that both systems use the same base <strong>for</strong> communication.Like the system probe this interface must be interchangeable.Requirement 14:Create different views that can be changed on request and providea good usability <strong>for</strong> the developerSwitching the views must be possible at any time. The usability of these viewsmust satisfy the experts requirements.Requirement 15:Support <strong>for</strong> extension according to changes on the probeDue to changes on the probe the views on the application must be extensible.12
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: with a very high frequency which ma
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 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

Create successful ePaper yourself

Delete template?

Save as template?