cs 599 – project discussion
DESCRIPTION
CS 599 – Project Discussion. Nenad Medvidovic [email protected] Marija Mikic-Rakic (T.A.) [email protected]. Available Troops Repository. Map Repository. Strategy Analyzer. Troops Deployer. Map Display. Background Implementation Infrastructure. Java JVM, Java KVM, C++, EVC++, Python. - PowerPoint PPT PresentationTRANSCRIPT
1
CS 599 – Project DiscussionCS 599 – Project Discussion
Nenad Medvidovic
Marija Mikic-Rakic (T.A.)
2
BackgroundBackgroundImplementation InfrastructureImplementation Infrastructure
Java JVM, Java KVM, C++, EVC++, Python
ICom ponent
IArchitecture
Connector
IConnector
Component
#top
#bottom
Architecture ArchitectureAdapter
ComponentThread
ConnectorThread
Message
Serializable
(f rom io)
Notification Reques t
ArchitectureEventCons tants
Address(f rom C3.util)
IScaffold
Brick
+topId+bottom Id
#scaffold
MapDisplay
MapRepository
AvailableTroops
Repository
StrategyAnalyzer
TroopsDeployer
3
BackgroundBackgroundSpecial-Purpose ConnectorsSpecial-Purpose Connectors
Border connectors, MVC, IR, XML
4
BackgroundBackgroundTDS ApplicationTDS Application
n
Component
RequestNotification
Notification()Notification()
ListIterator
Thread(f rom lang)
ConnectorThread
Object(f rom lang)
Object(f rom lang)
Hashtable(from uti l)
Message
source
param etersFIFOPort
SimpleArchitecture
Sim pleArchitecture()Sim pleArchitecture()
ComponentThread
Object(f rom lang)
C2Object
myself
BinarySemaphor
available : boolean
Connector
bottom top
WorkerThreadSemaphor
localSem
waitingSem
LinkedList
top
bottom
Architecture
0..*
1
+workerThreads
0..*
+arch 1
sem
SynchronizedFIFO
FIFO
messageFIFO
componentFIFO
Brick
messageFIFO
r
MapDisplay
MapRepository
AvailableTroops
Repository
StrategyAnalyzer
TroopsDeployer
AdminComponent
ICom ponent
IArchitecture
Connector
IConnector
Component
#top
#bottom
Architecture ArchitectureAdapter
ComponentThread
ConnectorThread
Message
Serializable
(f rom io)
Notification Reques t
ArchitectureEventCons tants
Addres s(f rom C3.util)
IScaffold
Brick
+topId+bottom Id
#s caffold
ICom ponent
IArchitecture
Connector
IConnector
Component
#top
#bottom
Architecture ArchitectureAdapter
ComponentThread
ConnectorThread
Message
Serializable
(f rom io)
Notification Reques t
ArchitectureEventCons tants
Addres s(f rom C3.util)
IScaffold
Brick
+topId+bottom Id
#s caffold
ICom ponent
IArchitecture
Connector
IConnector
Component
#top
#bottom
Architecture ArchitectureAdapter
ComponentThread
ConnectorThread
Message
Serializable
(f rom io)
Notification Reques t
ArchitectureEventCons tants
Address(f rom C3.util)
IScaffold
Brick
+topId+bottom Id
#scaffold
ICom ponent
IArchitecture
Connector
IConnector
Component
#top
#bottom
Architecture ArchitectureAdapter
ComponentThread
ConnectorThread
Message
Serializable
(f rom io)
Notification Reques t
ArchitectureEventCons tants
Address(f rom C3.util)
IScaffold
Brick
+topId+bottom Id
#scaffold
MapDisplay
AdminComponent
MapDisplay
AdminComponent
MapDisplay
AdminComponent
MapDisplay
AdminComponent
M M M
M M M M M
M M
M
StrategyAnalyzer`
StrategyAnalyzer
5
BackgroundBackgroundPrismPrism
Visio-based software modeling and deployment environment
6
BackgroundBackgroundDRADELDRADEL
Textual architectural modeling
Static analysis
7
BackgroundBackgroundMobility and Disconnected OperationMobility and Disconnected Operation
Theoretical model (mostly) worked out
Tool support pending
8
Class projects (1)Class projects (1)DRADEL
Extend it to support peer interactionsExtending the spec with dependency tag associated with each provided service of a componentExtending the spec with degraded mode tag associated with each provided service of a component
Utilize this information at the level of implementation
µDRADELHow much can be deployed on devices?Under what circumstances?
Border connectorsExtending them to monitor message frequencies and report the frequencies on demand
Must be highly efficientMeasure the penalty
Supporting reconnection
9
Class projects (2)Class projects (2)
PrismExtend it with automated discovery of network nodes and software components on those nodesAdd peer supportAdding source parameter to the component descriptionPing attached devices and visually depict disconnection
Disconnected operationSuggest ways to construct a dependency graph of components so that benefit can be calculated preciselyDetect the disconnectionCalculate the probability of sudden disconnection
10
Class projects (3)Class projects (3)
Extensions to TDS applicationMake it really cool
Implement a novel PitM applicationIntegration with SoftwareDockExtend PitM communication model
Provide real-time guaranteesIR/wireless connectorsSecure connectors
CM support for PitM application developmentResource analysis of PitM architectures
11
EquipmentEquipmentType of Device Quantity Description
Serial Docking Cradle 1 For connecting a Visor Handspring to a PC via serial port
Handspring Visor 11 Memory 2 MB, IR, Palm OS, Cradle to USB
Home Director 1 Lamp module, PC connection module, Remote module - used to control most lights and appliances
Eye Module 4 Digital camera module for Handspring
USB Infrared Adapter 1 Infrared port for PC via USB
Handy GPS 2 Data: time, latitude, longitude, speed, distance to the next waypoint (up to 100 waypoints can be stored), up to 10 routes may be stored, playback reports the actual trace, quick buttons
Wristband Thin Modem 1 Modem for Handspring (33.6Kbps)
Intel Web Cam 1 Connects via USB port
Wireless PC Card 2 BayStack 650 Wireless
Additionally (instructor’s research equipment, but can be used for the class if needed by a project):two Palm Pilot 5x with docking cradles (serial port)one Palm Pilot VIIx with docking cradle (serial port)one Compaq iPAQ with docking cradle (USB port) + serial cableone USB to six serial port converter