LEADER 05668nam 2200745 a 450 001 9910138863803321 005 20200520144314.0 010 $a1-118-60220-X 010 $a1-118-60217-X 010 $a1-118-60211-0 010 $a1-299-18774-9 035 $a(CKB)2550000001005906 035 $a(EBL)1124669 035 $a(SSID)ssj0000831873 035 $a(PQKBManifestationID)11440099 035 $a(PQKBTitleCode)TC0000831873 035 $a(PQKBWorkID)10881378 035 $a(PQKB)10594886 035 $a(Au-PeEL)EBL1124669 035 $a(CaPaEBR)ebr10660617 035 $a(CaONFJC)MIL450024 035 $a(PPN)177993715 035 $a(CaSebORM)9781118602171 035 $a(MiAaPQ)EBC1124669 035 $a(OCoLC)828424574 035 $a(EXLCZ)992550000001005906 100 $a20110524d2011 uy 0 101 0 $aeng 135 $aur|n|---||||| 181 $ctxt 182 $cc 183 $acr 200 10$aCommunicating systems with UML 2$b[electronic resource] $emodeling and analysis of network protocols /$fDavid Garduno Barrera, Michel Diaz 205 $a1st edition 210 $aLondon $cISTE ;$aHoboken, N.J. $cWiley$d2011 215 $a1 online resource (276 p.) 225 1 $aISTE 300 $aDescription based upon print version of record. 311 $a1-84821-299-2 320 $aIncludes bibliographical references and index. 327 $aCover; Title Page; Copyright Page; Table of Contents; Preface; Chapter 1. Why Use UML to Model Network Protocols?; 1.1. Modeling network protocols; 1.1.1. The complexity of communication protocols; 1.1.2. Traditional modeling; 1.1.2.1. Basic models and formal description techniques; 1.1.2.2. Automata and state machine models; 1.1.2.3. Petri Net models; 1.1.2.4. Formal and semi-formal languages; 1.1.2.5. Towards a new modeling language; 1.1.3. Traditional validation; 1.1.4. Need for a unified language for description, validation and simulation; 1.2. UML as a common language; 1.2.1. Overview 327 $a1.2.2. The beginning1.2.3. Brief review; 1.2.3.1. Class diagram; 1.2.3.2. Package diagram; 1.2.3.3. Object diagram; 1.2.3.4. Component diagram; 1.2.3.5. Composite structure diagram; 1.2.3.6. Deployment diagram; 1.2.3.7. Sequence diagram; 1.2.3.8. Profile diagram; 1.2.3.9. Activity diagram; 1.2.3.10. Communication diagram; 1.2.3.11. Interaction overview diagram; 1.2.3.12. Timing diagram; 1.2.3.13. Use case diagram; 1.2.3.14. State machine diagram; 1.2.4. UML for network protocols; 1.2.5. Some general UML tools; 1.3. Chapter summary; 1.4. Bibliography; Chapter 2. Simple Transmission 327 $a2.1. Introduction2.2. Echo; 2.2.1. Requirement specification; 2.2.2. Analysis; 2.2.2.1. Sequence diagram; 2.2.2.2. Concerned classes; 2.2.2.3. Signals list definition; 2.2.3. Architecture design; 2.2.4. Detailed design: class behavior; 2.2.4.1. Client class; 2.2.4.2. Server class; 2.2.5. Echo: validation and simulation; 2.2.5.1. Simulating the model; 2.2.5.2. Model validation; 2.3. Unidirectional: simple data sending; 2.3.1. Requirement specification; 2.3.2. Analysis; 2.3.2.1. Sequence diagram; 2.3.2.2. Signals list definition; 2.3.3. Architecture design; 2.3.4. Detailed design 327 $a2.3.4.1. First variation: protocol notation (transition oriented)2.3.4.2. Second variation: behavior notation (state oriented); 2.3.5. Validation and simulation; 2.3.5.1. Simulating the model; 2.3.5.2. Model validation; 2.4. Full duplex: simple data sending; 2.4.1. Specification; 2.4.2. Analysis; 2.4.2.1. Sequence diagram; 2.4.2.2. Concerned classes; 2.4.3. Architecture design; 2.4.4. Validation and simulation; 2.4.4.1. Simulating the model; 2.4.4.2. Model validation; 2.4.5. Different ways of doing the same thing; 2.4.5.1. A single machine; 2.4.5.2. Interruption 327 $a2.4.5.3. Composite states with concurrent regions2.4.5.4. Parallel threads; 2.5. Chapter summary; 2.6. Bibliography; Chapter 3. Simple Chat Application; 3.1. Introduction; 3.2. Requirements; 3.3. Analysis; 3.3.1. Sequence diagrams; 3.3.1.1. Splitting the system up; 3.3.1.2. Open session; 3.3.1.3. Timeout; 3.3.1.4. Refuse; 3.3.1.5. Accept; 3.3.1.6. Close; 3.3.1.7. Send data; 3.3.2. Concerned classes; 3.3.3. Signal list definition; 3.4. Architecture design; 3.5. Detailed design; 3.5.1. Open session; 3.5.2. Timeout; 3.5.3. Refusing the session; 3.5.4. Accepting session; 3.5.5. Closing session 327 $a3.5.6. Sending data 330 $aThis book gives a practical approach to modeling and analyzing communication protocols using UML 2. Network protocols are always presented with a point of view focusing on partial mechanisms and starting models. This book aims at giving the basis needed for anybody to model and validate their own protocols. It follows a practical approach and gives many examples for the description and analysis of well known basic network mechanisms for protocols.The book firstly shows how to describe and validate the main protocol issues (such as synchronization problems, client-server interactions, layer 410 0$aISTE 606 $aComputer network protocols 606 $aTelecommunication systems 606 $aUML (Computer science) 615 0$aComputer network protocols. 615 0$aTelecommunication systems. 615 0$aUML (Computer science) 676 $a004.6 686 $aTEC041000$2bisacsh 700 $aGarduno Barrera$b David$0995919 701 $aDiaz$b Michel$f1945-$0870845 801 0$bMiAaPQ 801 1$bMiAaPQ 801 2$bMiAaPQ 906 $aBOOK 912 $a9910138863803321 996 $aCommunicating systems with UML 2$92282154 997 $aUNINA