Condroid Remote Management Work Procedure. Download the document in http://csd.xen.ssvl.kth.se/csdlive/content/remote-management-system-analysis-design

1. !
!"#$%"&#'(')"#"(%&&
*"%&+,&,!$-".+!"&
/"!*0$(&121&
2011
!"#$%&'()%*+(,%+-%"( !"#$%&'(&#*&.(
& (
&
Lan Sun (lansun@kth.se), 15 ECTS (((((/#*&.(*01(2"#$%&'(#30%"(
Hervé Ntareme
Qing An (qinga@kth.se), 15 ECTS
/#4&#*&.(
Michel Hognerud
Jun Gao (jungao@kth.se), 15 ECTS
/.*+25#0(
Laili Aidi (aidi@kth.se), 18 ECTS
Björn Pehrson!
Yasir Ali (yasireal@kth.se), 15 ECTS
SUMMER CSD

2. Remote Management Set up Procedure V1.1
!
Revision History
Version Date Responsible Change
V1.0 2011-08-13 Jun Gao & Yasir Ali Initial version of the document
Laili Aidi Cover, Abbreviation, add Step 7, all section’s
V1.1 2011-10-07
structure and content
2

3. Remote Management Set up Procedure V1.1
!
Contents
Contents.................................................................................................................................................................................. 3
Summary ................................................................................................................................................................................. 5
Abbreviation........................................................................................................................................................................... 6
1. Introduction ....................................................................................................................................................................... 7
2. Set up Procedure ............................................................................................................................................................... 8
! Step 1 ................................................................................................................................................8
1. System architecture design .................................................................................................................................. 8
2. System requirement design.................................................................................................................................. 8
! Step 2 ................................................................................................................................................8
1. Hardware Procurement........................................................................................................................................ 8
2. Feature & GUI Design ........................................................................................................................................ 8
3. Software Architecture .......................................................................................................................................... 8
! Step 3 ................................................................................................................................................9
1. Hardware Set up ................................................................................................................................................... 9
2. Hardware Basic Test ............................................................................................................................................ 9
3. UART Test Code.................................................................................................................................................. 9
! Step 4 ................................................................................................................................................9
1. Local Control Module Development ................................................................................................................ 9
2. Setting Module Development............................................................................................................................. 9
3. Connection Information Module Development ...........................................................................................10
4. IOIO Board Connection Module Development...........................................................................................10
5. UART Module Development ...........................................................................................................................10
6. Command Commit Module Development – Part 1 .....................................................................................10
7. Command Parser Module Development – Part 1 .........................................................................................10
8. About Module Development............................................................................................................................10
! Step 5 .............................................................................................................................................. 11
1. Shortcut Module Development........................................................................................................................11
2. Shortcut Generate Module Development ......................................................................................................11
3. Command Commit Module Development – Part 2 .....................................................................................11
4. Command Parser Module Development – Part 2 .........................................................................................11
! Step 6 .............................................................................................................................................. 11
3

4. Remote Management Set up Procedure V1.1
!
1. Standby Module Development.........................................................................................................................11
2. Standby Setting Module Development ...........................................................................................................11
3. Daemon Module Development........................................................................................................................11
4. SMS Communication Module Development .................................................................................................12
! Step 7 .............................................................................................................................................. 12
1. Java Doc Documentation..................................................................................................................................12
2. Installation Guide & User Manual ...................................................................................................................12
3. Verification Test ................................................................................................................................................ 12!
4

5. Remote Management Set up Procedure V1.1
!
Summary
This document describes the complete procedure to set up the Condroid Remote Management application.
5

6. Remote Management Set up Procedure V1.1
!
Abbreviation
Abbreviations used in this document:
Abbreviation Description
UART Universal Asynchronous Reception and Transmission
API Application Program Interface
GUI Graphical User Interface
Minicom Text-based modem control and terminal emulation program for Unix- like OS
UART Universal asynchronous receiver/transmitter
IOIO A USB I/O breakout board for Android
SMS Short Message Service
6

7. Remote Management Set up Procedure V1.1
!
1. Introduction
This document contains the development procedure for the ConDroid Remote Management application
development. It is designed to be used by the Condroid team in order to get the fully functioned ConDroid
Remote Management software and hardware environment.
7

8. Remote Management Set up Procedure V1.1
!
2. Set up Procedure
• Step 1
The first task is to identify the stage for the future development. After the detailed study into this field, we have
got our basic idea of the whole system and how to achieve it. However, we need to clarify the whole system
and define each part of the system, hardware and software identification. We divided this Step into 2 parts:
1. System architecture design
In this part we will clarify the whole system and its components. This will become reference for coming
developing teams and user to get the basic idea of the project.
2. System requirement design
As the project has specific requirement of the hardware, we need to provide this requirement for
procurement as well as it will be needed by user to set up the system.
Deliverable:
System architecture and Requirement document
• Step 2
The second phase is to make more detail design for the software after committing the hardware procurement
and waiting it arrive. This step is divided into 3 parts:
1. Hardware Procurement
After deciding the hardware environment in Step 1 and clarify the requirement, thus the first thing in this
step need to be done is to commit the hardware procurement according to the requirement. We should
make a detailed document for every component and submit to Champion and Project Owner to be
purchased.
2. Feature & GUI Design
During hardware delivery, the first thing we should do is the Feature and GUI design. We need to clarify
all the functions that should be provided based on the system requirement. Moreover, according to the
function design, we can then design the GUI. This design will be reference for the following step and
coming developing teams
3. Software Architecture
Software architecture is needed for software development. We should design the software architecture
according to the Feature and GUI design. Since Java will be the development language for the software,
the architecture will mainly define how many classes we will have to implement, their functions, behavior,
8

9. Remote Management Set up Procedure V1.1
!
and interaction with each other, etc. The design should be recorded into document and will be reference
for the following step and coming developing teams
Deliverable:
1. USB-To-Serial Converter Board for Android Procurement Document
2. Feature & GUI Design Document
3. Software Architecture Document
• Step 3
Step 3 will be the preparation and test stage before the software development. Thus, we assume all the required
hardware has arrived during this step.
1. Hardware Set up
First thing we should do after got the hardware is to set up the hardware environment for our system. In
this part, the main work will be soldering component.
2. Hardware Basic Test
After hardware setup, we need to do the basic test. We will have to test the hardware with the example
code provided by its manufacturer. By using this way, we can check the basic state of the hardware and its
API.
3. UART Test Code
As we mainly use the UART module of the hardware, we should make a test code to test this hardware as
well as getting familiar with its API.
• Step 4
The rest of tasks from here will be the development part and mainly according to the software architecture.
1. Local Control Module Development
The software will be developed so it provides a console-like feature to user to communicate with the
device and software itself through typing command. This subtask may need further device, which might
be unable to be identified in previous steps, due to lack of information.
2. Setting Module Development
Setting activity class is used by user to interact in order to get devices connection information, thus Its
help topic activity class provides help information for its setting.
9

10. Remote Management Set up Procedure V1.1
!
3. Connection Information Module Development
This class is designed to generate, modify or get the information from the connection information file,
which will be used by IOIOThread class (will be mentioned later) to connect to the devices. It will interact
with Setting activity or other classes.
4. IOIO Board Connection Module Development
As we will use the IOIO board, we need to get the board instant first in an individual thread and check its
availability in a loop and generate all the UART channels.
5. UART Module Development
Getting the input from UART module and sending output through UART should be in different thread,
as these 2 channels are separated and can be used at the same time.
6. Command Commit Module Development – Part 1
This class is designed to be used to commit command, thus it will use the ComParser class (will be
mentioned later) to parse command first and after parsing, then commit it according to the parsing. In this
task, we will only achieve the outer command commitment.
7. Command Parser Module Development – Part 1
This class is designed to be used to distinguish the inner command, which is the command for Remote
Management app software and outer command, which is the command that will be sent to devices
directly. This class will return parsed command to ComCmit class to be committed. In this task, we will
achieve only the outer command part. We also need to provide the command format and inner command
list document in this subtask, to be put in the User Manual and Installation Guide later.
8. About Module Development
This is a simple class to display information about the software and project.
Deliverable:
1. Console-like module implemented
2. Setting module implemented
3. Connection Information module implemented
4. IOIO board connection module implemented
5. UART module implemented
6. About module implemented
10

11. Remote Management Set up Procedure V1.1
!
• Step 5
In this step we will have to achieve the shortcut functions.
1. Shortcut Module Development
Shortcut activity and relevant help topic activity classes achieve. Shortcut activity class is for user to
interact in order to read and edit the shortcut command list. Its help topic activity class is to provide help
information for its setting.
2. Shortcut Generate Module Development
This class will generate, modify or get the information from the shortcut command list file. It will interact
with Shortcut activity or other classes.
3. Command Commit Module Development – Part 2
Realize the inner command commitment.
4. Command Parser Module Development – Part 2
We need to finish the inner command part in this task and upgrade the command format and inner
command list document.
Deliverable:
1. Shortcut module implemented
2. Command module (commit and parser) implemented
• Step 6
In this task, we will have to achieve part of the remote control functions. The remote control method we will
achieve in this task is control via SMS. The other remote methods (dialing and internet connection), will be as
secondary priority or should be provided in later versions.
1. Standby Module Development
Standby activity class is for user to interact in order to set security information for remote control. Its help
topic activity class is to provide help information for its setting.
2. Standby Setting Module Development
This class will generate, modify or get the information from the standby setting file. It will interact with
Standby activity or other classes.
3. Daemon Module Development
ConDroid daemon class will run as a daemon after standby setting committed. It will monitor the
incoming SMS, calling and keep and monitor Internet connection. In this project, we will prioritize to
achieve the SMS communication module.
11

12. Remote Management Set up Procedure V1.1
!
4. SMS Communication Module Development
The class will deal with the control via SMS. It will check the coming short message according to standby
setting, commit the command and send back the response.
Deliverable:
1. Standby module implemented
2. Daemon module implemented
3. SMS Communication module implemented
• Step 7
In this task, we will have to make complete documentation, which is devided into parts:
1. Java Doc Documentation
In this task, we will provide the complete Java doc for every methods and classes that are used in the
code. This document can be reference to the coming developers.
2. Installation Guide & User Manual
In this task, we will provide the complete guidance on how to install the hardware and software and to use
the application
3. Verification Test
In this task, we will do the verification test for all the features in the application and then documenting the
result into verification test document.
Deliverable:
1. Java Doc of the Remote Management App
2. Installation Guide & User Manual document of the Remote Management App
3. Remote Management App Verification Test document
12