1 Design a Simple Two Telephone System Concentrating on the control aspects (not data). Requirements Each phone has a handset that may be picked up and.

Slides:

Advertisements

Similar presentations

Hosted VoIP Service Special Calling Features Flash Services Feature Access Codes.

Advertisements

The business phone system for the next 100 years Call Manager Personal Desktop Call Management.

IP Communications Training 8961 Series. Getting to Know Your Phone Message Waiting LCD Screen Soft Keys Speakerphone Navigation Pad Line or Speed Dial.

PROTOCOL VERIFICATION & PROTOCOL VALIDATION. Protocol Verification Communication Protocols should be checked for correctness, robustness and performance,

CS6133 Software Specification and Verification

IP Communications Training Getting to Know Your Phone 1.Phone Screen 2.Phone Model 3.Soft Key Buttons 4.Navigation Button 5.Applications Menu Button.

IP Communications Training 6900 Series. Getting to Know Your Phone LCD Screen Line Buttons Soft Keys Transfer, Conference, Hold Keys Headset Button Speakerphone.

IP Communications Training 7900 Series. Getting to Know Your Phone Message Waiting LCD Screen Soft Keys Footstand Adjustment Speakerphone Navigation Button.

Using Ericsson Phone Features

Meridian M2008 & 2616 Please press the F5 key on your PC to begin the presentation Press the space bar or arrow keys to advance 1 IT Support Center

1 © 2005 Cisco Systems, Inc. All rights reserved _04_2005 Cisco Confidential Cisco Unified Communications Solutions End User Training Facilitated.

Basic Features Voic message indicator

Nortel Meridian M3903 Telephone Training San Diego County Office of Education.

Ready to begin. Buttons Phone basics Handling calls Making Pages Additional features.

● DIGITAL KEY TELEPHONE / Quick Reference Guide KD, KD/E, LKD Series Fixed Feature Buttons ● FLASH button is used to terminate an outside call and re-seize.

Network Protocols Dr. Eng Amr T. Abdel-Hamid NETW 703 Winter 2006 Finite State Machines (FSMs)

ESI Phone System Training Adcom/Valentine Systems

Busy Lamp Field User Guide for Polycom Soundpoint Phones

Eric Kelsey Class Outline: 1)Phone Features 2)Call Communicator 3)Call Handling Modes and Call Forwarding.

Voic message indicator This will light up if you have a message in your voic box It will flash when you receive a call Line Buttons #22 is the.

The Telephone Instrument

Summary Class responsibility cards can be used to help allocate responsibilities between different classes. The use of stereotype classes, such as entity,

PRESENTED BY NASIR ABBAS. FLOW CHART CONTENTS What is a flow chart? Flow chart symbols.

1 © Wolfgang Pelz UML2 UML Part Two. 2 © Wolfgang Pelz UML2 Chapters Four & Twelve Interaction Diagrams.

Mainly OK & ready FSMs: 1. Discuss good examples and bad examples of state names: (bad preparing 1, preparing 2, …)

Slide 1 MSC and SDL. Slide 2 Relationship of MSC to SDL An MSC describes one or more traces of an SDL system specification. An entity in MSC may map to.

- A subscriber on switch A places a call to a subscriber on switch B - Switch A analyzes the dialed digits and determines that it needs to send.

VoIP - Implementing Trunk for PSTN Switch and VoIP Gateway An Examination Ricardo Estevez CS 522 / Computer Communication Fall 2003.

SE-565 Software System Requirements More UML Diagrams.

Call Manager - Quick Reference Guide Initiate a Call 1.Select a Phone List. Click Tab to expose list. 2.Select a phone number. Click phone number to populate.

Welcome u How to use your Phone Effectively u Telephone Features u Voice Messaging Features.

Telephone Training M3904 Telephone Set IT Support Center

Welcome u How to use the new NCAR telephone system u Telephone Features u Voice Messaging Features.

1.Take holster off phone if applicable 2.Verify antenna is completely inserted 3.To insert antenna slot: 1.Hold antenna button atop phone while inserting.

ELC 524E Monday, 20th February 2012

State and Sequence Diagrams Modelling dynamic information So far we have seen: Use Case Diagrams – requirements capture, interface.

M3902 Basic Telephone This is the standard University of Alberta phone. The M3902 brings the display-based interface and handsfree capability to this basic,

Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 8: Modelling Interactions and Behaviour.

1 Object-Oriented Modeling Using UML (2) CS 3331 Fall 2009.

Your New Cisco Phone.

Mukesh N. Tekwani Elphinstone College Mumbai

10/17/01H-1 © 2010 T. Horton CS 4240: Principles of SW Design Interaction Diagrams Examples of Collaboration and Sequence Diagrams Phone modeling exercise.

Introducing The IP550 IP Telephone. What to expect from your new IPitomy IP telephone system The IPitomy system has many of the same features of traditional.

1 Modeling interactions and behavior Lecturer Dr. Mai Fadel.

● GHX KEY TELEPHONE SYSTEM / SLT User Guide GHX-308A/616/36/46 SLT User Guide for GHX System Call Forward ● Lift handset. ● Dial ● Dial the desired.

1 The UAX13 - Dialling the First Digit The UAX13 Group Selector is seized by a calling earth from the associated linefinder and returns a holding earth.

Dialling the Last Two Digits The final selector, although large, is a fairly straightforward piece of equipment with straightforward facilities much as.

Discovering object interaction. Use case realisation The USE CASE diagram presents an outside view of the system. The functionality of the use case is.

Course Instructor: Kashif Ihsan 1. Chapter # 3 2.

Welcome u How to use the new NCAR telephone system u Telephone Features u Voice Messaging Features.

UNIFIED MODELING LANGUAGE(UML) BY Touseef Tahir Lecturer CS COMSATS Institute of Information Technology, Lahore.

Nortel Contact Center Symposium ACD Agent Press F5 to begin presentation Click on your mouse or use the spacebar or arrow keys to advance to the next slide.

Dynamic Models. Outline Dynamic Models Statecharts –States –Transitions –Composite states Interaction Diagrams –Sequence Diagrams The time order of interactions.

Welcome u How to use the new NCAR telephone system u Telephone Features u Voice Messaging Features.

CS212: Object Oriented Analysis and Design Lecture 34: UML Activity and Collaboration diagram.

Dynamic Models Sequence Diagrams Collaboration Diagrams Activity Diagrams.

Using UC500 IP Phone System. Line Call Feature Flashing Green : call placed on hold by you Steady Green: line in use by you Flashing Red: Call is placed.

1 Introduction to Your Norstar Telephone System IT Support Center or

Dynamic Models - Page L M.E. Fayad Lesson 30: Dynamic Models Object- Oriented Modeling & Application s.

1 Chapter 11 Global Properties (Distributed Termination)

 One of the simplest devices we have in our house.  very simple because the telephone connection to our house has not changed in nearly a century. Introduction.

More on UML 1. 1.Use-case diagram 2.Class diagram [Object diagram] (static) 1.1 Domain/analysis model – of reality 1.2 Design model – of decisions 3.

School Exercises: A Component-based Model of a Phone  Components use and implement interfaces  Protocol statecharts model the accepted orderings of incoming.

Introducing The IP550 IP Telephone

UML State Diagrams.

Object Oriented Design Model

Protocol Basics.

Call Manager - Quick Reference Guide

6402D Voice Terminal Guide.

Presentation transcript:

1 Design a Simple Two Telephone System Concentrating on the control aspects (not data). Requirements Each phone has a handset that may be picked up and replaced, a button that can be used to alert the other the other telephone of the desire to communicate, and a bell that alerts a user of an incoming call. A call be terminated by either party. Suggested States Idle - handset is down, there is no connection. Dial- ready to dial Ringing - handset is ringing Calling - call has been placed, but not yet connected Talk- connection is established.

2 Informal Description of Tel. Behaviour Idle 1. Pickup handset(become caller); proceed to Dial. or 2. Phone rings; proceed to ringing. Dial 1. Replace handset; proceed to Idle. or2. Press button; proceed to Calling. Calling 1. Abandon call-replace handset; proceed to Idle. or2. Called party picks up; proceed to Talk. Ringing 1. Pickup handset(become called); proceed to Talk. or 2. Caller rings out - receive signal; proceed to idle. Talk 1. Replace handset; proceed to Idle. or 2. Other party disconnects - receive signal; proceed to Dial.

3 Informal Description of Tel. Behaviour Idle 1. Pickup handset (become caller); proceed to Dial. or 2. Phone rings; proceed to Ringing. Dial 1. Replace handset; proceed to Idle. or2. Press button; generate signal to called party; proceed to Calling. Calling 1. Abandon call-replace handset; generate a signal to called party; proceed to Idle. or2. Called party picks up - receive signal; proceed to Talk. Ringing 1. Pickup handset(become called); generate a signal to caller; proceed to Talk. or 2. Caller rings out - receive signal; proceed to Idle Talk 1. Replace handset; generate a signal to other party; proceed to Idle. or 2. Other party disconnects - receive signal; proceed to Dial.

4 Process Diagram (generic) channelsignal handset{up,down} button{press} bell{ring} link{alert,answer, cutoff} Phone 1 Phone 2 bell1 button1 bell2 button2 handset1handset2 link21 link12

5 Parameterised Description of Tel. Behaviour of Phone n Call link from phone n to phone m linkout. Call link from phone m to phone n linkin.

6 Idle 1. Pickup handset; proceed to Dial. or 2. Phone rings on receipt of alert on linkin; proceed to Ringing. Dial 1. Replace handset; proceed to Idle. or2. Press button; generate alert on linkout; proceed to Calling. Calling 1. Abandon call-replace handset; generate a cutoff on linkout; proceed to Idle. or2. Called party picks up - receive answer on linkin; proceed toTalk. Ringing 1. Pickup handset(become called); generate answer on linkout; proceed to Talk. or 2. Caller rings out - receive cutoff on linkin; proceed to Idle Talk 1. Replace handset; generate cutoff on linkout; proceed to Idle. or 2. Other party disconnects - receive cutoff on linkin; proceed to Dial.

7 Message Sequence Charts Describe communication in a particular scenario. vertical axis defines ordering of events indication of state horizontal axis defines message/signal occurrences

8 Message Sequence Charts Example: Call setup and clear down (1 to 2) Phone 1 Phone 2 Idle Idle handset1.up Dial button1.press link12.alert bell2.ring Calling Ringing handset2.up link21.answerTalk handset1.down link12.cutoff IdleDial handset2.down Idle

9 Message Sequence Charts More Examples: Call setup and clear down (2 to 1) 1 calls 2, but rings out before 2 answers. 1 picks up handset, but puts down handset before dialing. Call setup and clear down (1 to 2) but 2 terminates call. 1 calls 2 and 2 calls 1.

10 Message Sequence Charts Example: 1 calls 2 and 2 calls 1 Phone 1 Phone 2 Idle Idle handset1.up handset2.up DialDial button1.press button2.press link12.alert link21.alert Calling DEADLOCK ! (except to return to Idle)

11 A Solution: Communication Protocol When a process needs to output a control signal, then it does so in parallel with receiving a response. When a process receives an unsolicited signal, it must eventually acknowledge it. Why? To prevent infinite blocking of signal sender.

12 Telephone Process Specification Assume all sends on linkout, all receives on linkin. Idle choosehandset.up:Dial linkin.alert :send ack; ring bell; Ringing Dial choosehandset.down : Idle button.press : || send alert || receive response; if response is ack then Calling else if response is alert then Talk Calling choosehandset.down : || send cutoff || receive response; Idle linkin.answer: send ack; Talk

13 Ringing choosehandset.up: || send answer || receive response; if response is ack then Talk else if response is cutoff then Dial linkin.cutoff:send ack; Idle Talk choosehandset.down : || send cutoff || receive response; Idle linkin.cutoff : send ack; Dial

14 Message Sequence Charts Examples with Acks: Call setup and clear down (2 to 1) 1 calls 2, but rings out before 2 answers. 1 picks up handset, but puts down handset before dialing. Call setup and clear down (1 to 2) but 2 terminates call. 1 calls 2 and 2 calls 1.

15 Inadequacies of FSA/Transition Systems Inherently sequential no representation of concurrency. No outputs no explicit way to deal with the generation of events. No state variables e.g. “remembering” the number dialled. No depth/hierarchy/modularity needed for structuring large systems. State and edge explosion no way to deal with “interrupts”, common behaviour.