Date post: | 27-Dec-2015 |
Category: |
Documents |
Upload: | earl-patterson |
View: | 213 times |
Download: | 0 times |
23-04-19 1
• These materials are prepared only for the students enrolled in
the course Distributed Software Development (DSD) at the
Department of Computer Science and Engineering,
University of Mälardalen, Västerås, Sweden and at the Faculty
of Electrical Engineering and Computing, University of Zagreb,
Croatia (year 2003/2004).
• For all other purposes, authors’ written permission is needed!
• The purpose of these materials is to help students in better
understanding of lectures in DSD and not their replacement!
NOTICE!
23-04-19 4
• Introduction
• Current status for :– Mote network– Main Application– PDA Application– Server Application– Web Application– Web Service– Database– System demonstration
• Project status update
What we will talk about?
Mote network
• Tested and functional
• Meets (almost) every requirement– Static mote startup / shutdown support
pending
• Additional feature– Ability to increase / decrease dynamic mote
radio range
Mote network – potential problems
• Corruption of data packets sent over radio– Very rare, but present
• Considering potential solutions:– Protecting radio packets with CRC– Implementation of safe communication
protocol
Mote server
• Propagation of mote network events to the PDA server
• Three main parts:– MoteIF– PDASignaller– MoteServerGui
MoteIF
• Application – level access point to the mote network
• Receives messages from the mote network, and forwards them to listeners
• Sends messages from applications to motes in network
PDASignaller
• Listens for messages
• On message receive passes it to the PDA server– Communication realized using RPC
Mote server class diagram
PDASignaller
ISignaller IListen
+MoteIF(in commPort : string, in baudRate : int)+~MoteIF()
-ListenerManager-comm : SerialComm
MoteIFSerialComm
IListenMan
ISendMsg IBridgeControl
+MoteIF(in commPort : string, in baudRate : int)+~MoteIF()+MoteServerGui(in sender : ISendMsg, in commControl : IBridgeControl, in signaller : ISignaller)
-sender : ISendMsg-commControl : IBridgeControl-signaller : ISignaller
MoteServerGui
Form
IListen
uses uses
CommBase
uses
1*
+main(in args : string[]) : static void
-gui : MoteServerGui-mote : MoteIF-signaller : PDASignaller
Program1
*1
*
1
*
RPCClient TCP/IP
1 *
Mote server
«bind»
«bind»
Base mote
Static mote
Dynamic mote
«bind»
Mote server GUI
• Used to start / stop the mote communication bridge
• Ability to control dynamic mote radio range
• Captures raw packets for display and storing
• Simulator
• Communication with PDA server
Simulator
• Under development
• Ability to simulate mote network– Replay of previously stored messages
• Introduced because of practical reasons– Simplifying test of the rest of the system
Client & Server Overview
Mote Server
Mote ConnectorPDA Connector
Web Service Connector
Server
Web Service
PDA Application
Static Mote
Server Base
Web Application
Database
Client
PDA Application
• Windows Mobile 5 Version– Will be implemented by using the Windows NT/XP
version code
• Windows NT/XP Version– Server connectivity– Supports XHTML content
• To Do– Implement the rest of the required functionalities– Implement video streaming if possible
Server Application
• PDA Connector– Supports XHTML content– Supports multiple clients
• Mote Connector– Currently supports Enter messages from
motes (not Leave messages)– Will be rebuild as a Windows Service
Server Application cont.
• Web Service Connector– Supports some Web Service methods
• To Do– Implement the rest of the required
functionalities– Implement video streaming if possible
Web Services
• Exposes methods to create and update database
• Takes care of Database Caching – (Applications should still cache returned
values as well, to preserve network bandwidth)
• Can manage security– Encryption (SSL)– Authorization and Authentication
Database
• Only allows execution of Stored Procedures, to be able to enforce data integrity (no Ad Hoc)
• Changed from MySQL 5.0 to Sql Server Express 2005– Also free to use– Long support for Stored Procedures
WS / DB State
• Current State of Web Services– All (43) current methods implemented and
undergoing extensive testing– May be extended if new information is needed
• Current State of the Database– All (46) Stored Procedures implemented and
deep in testing phase– Database populated with test data
Project Status
• Communication– Group skype meetings – twice a week
• Last week Monday and Thursday• This week Tuesday for now
– Individual meetings (any time, any day)– CVS server : up and running
• Gradually adjusting to it• Transferred all data from SVN server
Project Status
• Communication– General info
• Communication between team members is good and regular
– Also : Starting to use virtual machine• SQL server is installed
Project Status
• Comments / Experiences / Problems– Switched from MySQL to Microsoft SQL
Server 2005 Express Edition – No problems
• For now – hope it will stay in that way
– We are pleased to say that everything is going as planned
Project Status• Project Cost
– A bit outside planned
Current Planned Cost 9350 €
Current Actual Cost 11850 €
Planned Project Cost 16750 €
Forecasted Project Cost 20250 €
Project Status
• Overall project status: on track
• Time schedule: on track
Finished week Forecast Id
Milestone Description
Responsible Dept./Initials Plan
Week +/- Actual
Metr Rem
M-001 Project Plan W45-06 W45-06 0 W45-06 M-002 Requirement Definition
Approved W46-06 W46-06 0 W46-06
M-003 Design Description Approved
W47-06 W47-06 0 W47-06
M-004 Product Prototype W51-06 W51-06