Communicating Systems with UML 2 : Modeling and Analysis of Network Protocols.

Communicating Systems with UML 2 : Modeling and Analysis of Network Protocols.

This 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 pr...

Full description

Saved in:
Bibliographic Details
Main Author: Barrera, David Garduno
Other Authors: Diaz, Michel
Format: eBook
Language:English
Published: Hoboken : Wiley, 2013.
Series:ISTE.
Subjects:
Computer network protocols.
Telecommunication systems.
UML (Computer science)
telecommunication systems.
Computer network protocols
Telecommunication systems
Online Access:Click for online access
Table of Contents:
  • Cover; 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.
  • 1.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.
  • 2.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.
  • 2.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.
  • 2.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.
  • 3.5.6. Sending data.

Similar Items