CS 599 – Project DiscussionBackground Implementation InfrastructureBackground Special-Purpose ConnectorsPowerPoint PresentationBackground PrismBackground DRADELBackground Mobility and Disconnected OperationClass projects (1)Slide 9Slide 10Slide 111CS 599 – Project DiscussionCS 599 – Project DiscussionNenad [email protected] Mikic-Rakic (T.A.)[email protected] InfrastructureImplementation InfrastructureJava JVM, Java KVM, C++, EVC++, PythonICo m ponentIArchitectureConnectorICo nnectorCom ponent#top#bottomArchit ecture ArchitectureAdapterCom ponentThreadConnectorThreadMessageSerializable(f rom io)Notification Reques tArchitectureEventC ons tantsAddres s(f rom C3.util)IScaffoldBrick+topId+bottom Id#s caffoldMapDisplayMapRepositoryAvailableTroopsRepositoryStrategyAnalyzerTroopsDeployer3BackgroundBackgroundSpecial-Purpose ConnectorsSpecial-Purpose Connectors Border connectors, MVC, IR, XML4BackgroundBackgroundTDS ApplicationTDS ApplicationnCompon entRequestNotific ationNoti fica tion ()Noti fica tion ()List IteratorThread(f rom lang)ConnectorThreadObjec t(f rom lang)Objec t(f rom lang)Hasht able(from ut il)Mes sageso urcepa ram etersFIFOPo rtSimpleA rchi tec tu reSim pleArch ite cture ()Sim pleArch ite cture ()ComponentThreadObjec t(f rom lang)C2Objec tmys elfBinary S emaphoravail able : bo ole anConnec torbottomtopW orkerThreadSem aphorlo ca lSe mwait ing Se mLinke dLis ttopbo ttomArchitec ture0..*1+wo rke rThr ead s0..*+arch1se mSync hroniz edFIFOFIFOme ss ag eFIFOcom pon entFIFOBric kme ssa g eFIFOrMapDisplayMapRepositoryAvailableTroopsRepositoryStrategyAnalyzerTroopsDeployerAdminComponentICom po nen tIArchi te ctureC onne ctorICo nnec torCo m p on en t#to p#b ottomArch itect ure Archi tectu reAdapte rCo m po ne n tThr eadCo nne c torTh rea dMessa g eSe riali zab le(fro m io)N otifica tio n Re ques tArchi tecture Eve ntCon stan tsAddr ess(f rom C3.util)ISc affoldBric k+top Id+bo ttomId# scaffo ldICo mp onen tIArchite ctureCon nec torICo nnec torCom p on e nt#to p#b ottomArch itec ture Archi tecture Adapt erC om p one ntThrea dC onne ctorThre a dMess ag eSe rializa ble(fr om io)N otifica tio n R eque stArchi tectu reEve ntCon stan tsAddr ess(from C3.ut il)ISc affoldBr ick+topId+bo ttomId# scaffo ldIC ompo nentIArchitec tureCo nnectorICon necto rCo m pon en t#top#bo ttomArch ite cture Archite ctureAda pterCo mp one nt Thre adCo nne ctor Thre adMess ageSer ializa ble(f rom io)No tification Reque stArchi tec ture EventC ons tantsAddres s(fr om C3. util)ISc affoldBr ick+top Id+bo ttomId#s caffoldICo mpo nentIArchite ctureCo nnec torICon necto rC omp o n ent#top#b ottomArc hite ctu re Arch itectur eAda pterCo m po ne ntTh rea dCo n nec tor Thre adMes sag eSeri aliza ble(f rom io)Not ificatio n Re que stArchite ctureE ven tCo ns tant sAddre ss(f rom C 3.util )IScaffo ldBri ck+to pId+bott omId#s caffol dMapDisplayAdminComponentMapDisplayAdminComponentMapDisplayAdminComponentMapDisplayAdminComponentMMMMMMMMMMMStrategyAnalyzer`StrategyAnalyzer5BackgroundBackgroundPrismPrism Visio-based software modeling and deployment environment6BackgroundBackgroundDRADELDRADELTextual architectural modelingStatic analysis7BackgroundBackgroundMobility and Disconnected OperationMobility and Disconnected Operation Theoretical model (mostly) worked out Tool support pending8Class projects (1)Class projects (1)DRADELExtend 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 componentUtilize 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 demandMust be highly efficientMeasure the penaltySupporting reconnection9Class 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 disconnectionDisconnected operationSuggest ways to construct a dependency graph of components so that benefit can be calculated preciselyDetect the disconnectionCalculate the probability of sudden disconnection10Class projects (3)Class projects (3)Extensions to TDS applicationMake it really coolImplement a novel PitM applicationIntegration with SoftwareDockExtend PitM communication modelProvide real-time guaranteesIR/wireless connectorsSecure connectorsCM support for PitM application developmentResource analysis of PitM architectures11EquipmentEquipmentType of Device Quantity DescriptionSerial Docking Cradle 1 For connecting a Visor Handspring to a PC via serial portHandspring Visor 11 Memory 2 MB, IR, Palm OS, Cradle to USBHome Director 1 Lamp module, PC connection module, Remote module - used to control most lights and appliancesEye Module 4 Digital camera module for HandspringUSB Infrared Adapter 1 Infrared port for PC via USBHandy 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 buttonsWristband Thin Modem 1 Modem for Handspring (33.6Kbps)Intel Web Cam 1 Connects via USB portWireless PC Card 2 BayStack 650 WirelessAdditionally (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
View Full Document
Unlocking...