1 / 13

Two-Way Sequence Diagram

Two-Way Sequence Diagram. TIM. NCAP. Codec::encodeCommand( ) inArgs  OctetArray. Codec::decodeCommand( ) OctetArray  inArgs. OctetArray. Codec::encodeResponse( ) OctetArray  outArgs. Codec::decodeResponse( ) outArgs  OctetArray. OctetArray. Command Encode/Decode Architecture.

penney
Download Presentation

Two-Way Sequence Diagram

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Two-Way Sequence Diagram TIM NCAP Codec::encodeCommand( ) inArgs  OctetArray Codec::decodeCommand( ) OctetArray  inArgs OctetArray Codec::encodeResponse( ) OctetArray  outArgs Codec::decodeResponse( ) outArgs  OctetArray OctetArray

  2. Command Encode/Decode Architecture Codec CommandCodec header TestCase ReadStatusCodec Cmd Specific data ReadServiceRequestCodec ReadStatusCodecTestClass

  3. Next Steps / Oct 23 • Bug fix on example “readStatus” command • Zip & send to Stan & Vesper • Stan check-in • Jeff getting started doc • Loopback TIM • IO for Cygwin

  4. Registration Class Diagram Singletons Multiple Instances owns N Registration RegInfo P2pRegInfo NetRegInfo P2pRegistration NetRegistration Comm P2pComm NetComm NetBlueTooth P2pCommFifo P2pRs232Comm

  5. NCAP / TIM Communication Styles Codec P2pReceive Registration N 1 Dot0Core P2pCommFifo P2pCommFifo P2pTimReceive Dot0 / Dot X Interface Chapter 11 Command Processor Interface Chapter 11 Remote Interface NCAP Initiated Cmd / Rsp: inArgs  outArgs TIM Initiated Cmd / Rsp outArgs  inArgs TIM Initiated One-Way inArgs

  6. TIM Class Diagram Receive Singleton Comm P2pReceive P2pComm uses IO P2pTimReceive uses 2 P2pCommFifo owns FifoIO “owns” TimCommandProcessor

  7. NCAP Class Diagram Registration Receive P2pRegistration Multiple Instances Comm P2pReceive uses P2pComm IO P2pNcapReceive uses 2 P2pCommFifo registers FifoIO uses

  8. NCAP & TIM Relationship Diagram P2pCommFifo txFifoIO P2pCommFifo P2pNcapReceive P2pTimReceive rxFifoIO NCAP TIM Thread boundary

  9. TIM Relationship Diagram Thread boundary txFifoIO P2pCommFifo P2pTimReceive rxFifoIO TimCommandProcessor Thread boundary

  10. Next Steps 11/20/2009 • Complete P2pCommFifo • Add unit tests • Check in • Enhancements • Add support to encode/decode more commands (Both) • Add support to process more commands (TIM) • Implement P2pCommRs232

  11. P2pTimTest P2pTimTest commandProcessor p2pReceiveTestNcap p2pReceiveTim rxFifo p2pCommFifoTim p2pCommFifoNcap txFifo

  12. Next Steps 4/8/2010 • Help everyone with build issues • Try configuring Eclipse to use the external Makefiles from the configure • Complete MCastIO • Fix unit tests • Enhancements • Add support to process more commands in TimCommandProcessor • Implement P2pCommRs232

  13. Agenda • Email comments • Who owns the Makefiles? • How to build form Eclipse with “external” Makefiles • Eclipse or config? • Questions • P2pTimTest architecture • IO architecture

More Related